[SOLVED]Landing rates on performance page and aircraft page do not match

[Penny93]

Hello, I noticed on one of my flights that on the performance page, my actual landing on -240FPM is recorded, yet on the aircraft page, it is showing as -726,000fpm. The 726,000fpm landing DID happen, but it was a bug with the plane that sent it flying around in the air AFTER my initial landing of 240fpm. I am wondering why on the aircraft page it is showing 726,000 but on the performance page for the flight, it is showing 240fpm. It should show my first landing, I believe? 

 

Edited May 25 by Penny93

[Mr Rizqs]

Hey,

 

Please can you send a picture of the flight route, you can see this when you click on the flight.

 

Kind Regards,

George

[Penny93]

3 hours ago, Mr Rizqs said:

Hey,

 

Please can you send a picture of the flight route, you can see this when you click on the flight.

 

Kind Regards,

George

Here is the photo you requested.

[Mr Rizqs]

Thankyou,

 

Please can you zoom into the landing phase so i can see how many touchdowns you did, and what may have triggered a double reading

 

Kind Regards,

George

[Penny93]

13 hours ago, Mr Rizqs said:

Thankyou,

 

Please can you zoom into the landing phase so i can see how many touchdowns you did, and what may have triggered a double reading

 

Kind Regards,

George

I put it in my original message, it's the 787 that is buggy on 2024. When touching down, and extending spoilers, the plane gets sent into a frenzy and flips upside down and around and around all over the place. I touched down initially at -240fpm and then it did a few hundred backflips and landed at -726,000fpm. 

[Penny93]

Any info?

[Tim]

On 6/1/2025 at 4:30 AM, Penny93 said:

Any info?

The logic we use is to take the latest landing and use that as the "final" landing rate. This is to prevent a bounce on takeoff showing as a landing rate. Further, we will implement a feature where you can remove your landing rates, that will help in situations like this. Thanks for reporting this and sorry for it happening.

[Tim]

This topic has been solved, and will now be locked.