Device: Poco X6 Pro
Operating system: Android 15
Infinite Flight Version: 25.2
While flying earlier, I noticed that there are altitude and speed discrepancy after engaging the AP+.
Here’s my screenshot before I engaged my AP+ (look at the time):
Here’s my screenshot after I engaged my AP+ and spawned at a nearby airport to check my altitude and speed
I also checked in the flight trackers (namely Infinite View and Inflight.info) and saw the same result.
Hello!
That’s interesting.
Based on what we’re seeing, you climbed up to FL350 and stayed there. You never went up to FL370 during your most recent flight.
If you check the replay for the flight, what do you see?
Is this flight on a different account or?
No, it’s still in the same account.
(However I did forget to attach the “Heavy” callsign when I logged back to this flight, which may explain the difference in callsign).
Previous callsign was Giant 8609 Heavy, now it’s only Giant 8609
Here’s my screenshot before I engaged my AP+ (my plane has just finished ascending to FL350). However, I noticed discrepancies in the flight trackers which prompted me to spawn again in a nearby airport to check my flight’s stats
When I logged back in around an hour later or so, my flight still started at FL370, despite showing that I was in FL350 earlier
Device: iPad A16 (2025)
Operating system: iPadOS 26.3
When I change FL (step-climb) and then when it’s saved turn on AP+ it’s display correctly in the AP+ interface. But recently I noticed that all the third-party trackers (this example: Infinite Horizon) are displaying that the AP+ did not save, first I didn’t have this problem and maybe it’s not an issue with the game but with the trackers. I do still wonder if the trackers are more accurate than the AP+ interface.
The arrow is pointed to the point where I turned on AP+ (jumped back to FL320.The game displayed FL340. When I join the game for a 2nd time, the FL does save in Third party trackers.
This has happened to me multiple flights, it might be a bug, but the fact that all the third party trackers display this is still a bit puzzling to me.same issue here! the speed also drops in AP+ this needs to be fixed ASAP!
I think this is a problem with all third party apps that get data from the servers. Literally every tracker I checked, had the issue and It’s not only my flights, all other flights that step-climb aswell.
Could be a bug on the extraction of the informations or smth like that
Finally, someone is noticing the problem. I also experienced this issue since several days ago but have not been able to receive an adequate solution to this issue
I checked once and it’s not the fault in the flight trackers, as a quick spawn in the nearest airport to check on your AP+ flight would result in the same altitude as reflected in the trackers.
Let’s hope it gets resolved soon!
Is this difficult to fix?
I moved everything into one topic. Easier to keep track on.
We’re going to need some time for this.
It might be due to some work that’s being done in prep for 26.1 which contains several improvements for AP+ in terms of stability.
