Flight time issue

[gareth]

I seem to have a new flight time issue (different from the inital one), i did a flight from LIRF to WSSS, and the game regestered 11h01min of flight time (seen in ss), when it should have been about 11h30min

As you can see in the screenshots (im Singapore 277SQ Heavy) my takeoff clearence was given at 1013z, and i reported clear of all runways at 2152z aft landing. I did use ap+, but my flight only held for about 20 mins (at the 30min ETE to dest), so given that i should have at minimum 11h20min~ of flight time (i do understand flighttime is based on wheels off to wheels on ground, not atc clearence, but im just using this for a more tangible way of giving evidence)

i did log back into my flight twice during the flight, each for about 10mins (added up tgt gives 15-20mins, as seen in the pic) for step climbs, perhaps the game did not properly rejester those period of time i logged back into the flight? It does add up if you consider that.

Also i doubt this is a case of high ground speed since i logged back in, the GS changed and matched the simbrief est ones close enough (the pic shows the GS and alt graphs until 1700+z, it dint regester aft that, but apart from that until i logged back in to land, the last GS at 502kts is shown there so no diff)

For refrence, i followed the SIngapore Airlines actual flight SQ365 and its latest routing going south of iran instead of over pakistan, which flightradar24 has also been showing 11h30min+ and simbrief gave me 11h32min (as seen)

I think what happened was the time rejestered only rejestered the

1. inital wheels off ground till first use of ap+,
2. the whole ap+ duriation only,
3. when ap+ was switched off until touchdown,
   not factoring in the inbetween timings we log back on for stepclimbs etc

i mean after all its just 30mins of time here, but im posting this (cuz my va told me to) but mainly cuz i wanna know what went wrong (if it was smth on my side), cuz at this scale when i do the 17h+ flts the flight time might be affected up to an hour or so

thanks for helping

Phone<Oppo Reno 7z>:
Andriod 13

[Ryan_and_Riona]

Known issue when in Autopilot +
Happened to me when flying from Sydney to London,
Time said 9 hours instead of 20

[Petre2026]

That’s a lot of info, and I don’t want to make light work of your effort in this post, I can see you really did your research! And I may be wrong, but I’m pretty sure this is part of the flight time bug. Now I’m not sure when this will get fixed, which is annoying, especially because I too am in a VA and not being able to check replays for flight time is bad, but at the moment, I’ll share a method I’ve found for calculating almost entirely accurate flight times, even if the time in/deflates:

Now this method requires a stopwatch or some other method of keeping time (I’ve found that a stopwatch is easiest)

First, make sure you check how much flight time you have logged right before you initiate AP+, and write it down. Then, once back at the Home Screen, write down how much time is left according to AP+, and add that to your already logged flight time. Then subtract 30 minutes. Now this is approximately how much time that will have been flown when you clock back in after AP+ has stopped your flight, with about a minute or two at most of inaccuracy. Then, as soon as you resume your flight, start your stopwatch, or jot down the time. Then stop it or jot the time down again once you land, and add the elapsed time to your previous figure, and that will be your total flight time.

Now, this method as is only works for flights without step climbs. You will have to tweak it slightly if you want to step climb, tracking the time as you go and each time you log back in to climb. But the idea still holds.

I know this is a bit tedious, but it works for me with incredibly accurate results, and as I fly for a couple strict VAs, it’s been a lifesaver. I pray it helps you too!

[gareth]

thank you!!