AP+ Flight Time Issue

[Dragon_Gimer]

Guys, I need your help. Why isn’t my autopilot+ recording flight times? Is there a problem with it or with my device?

[BennyBoy_Alpha]

Heavily reported issue (both in the main and beta versions of the app):

Flight time not counting

Same issue occured for me. My flight between Boston and San Francisco was only recorded as 1 hour and 24 minutes.

Incorrect time when using AP+

Version Information 26.1 (15547) Device Information iPad Air 5th generation IOS 26.2 Description I appreciate that this is a small issue, but I thought I’d give it a shot. When using AP+ and returning to the flight, the timezone is totally wrong. For example, I’ll take off at 1600UTC and then, 12 hours later, return to the flight; the time is 1300UTC or whatever. It would be nice if the time you set manually also froze when you’re 30 mins from landing, the same way your flight does. That way, …

AP+ Flight time issue

I was doing a flight from JNB-ATL, and when I spawned in after 16 hours of using ap+, it said I had 16 hours of flight time, which was normal. So I left the flight and kept it paused at 30 minutes ETE, and when I came back an hour and a half later it said I had 17:30 flight time, but it was paused so it shouldn’t have added more flight time.

Flight time issues with AP+ stopping

Device: Oppo Reno 13 Operating system: android 16 Pretty much ever since beta version came out, there has been a flight time issue on the non beta version (afaik), where even when the flight stops at the 30min ETE to dest, the timer still keeps going on. Happened to me 3 times alr, once again all on the non beta version (I’ve never flown full flight on beta before so idk abt beta version). First 2 incidents I both stoped for 1hour, and my flight time was inflated by an hour each. Third incide…

Etc.

[Petre2026]

Hey there! Unfortunately, there are quite a few bugs with the AP+ system, including flight time, fuel burn, and XP earned. For me, I’ve found that if I wait more than 24 hours to resume my flight, it drops my flight time.

Are you using it in the beta or regular version?

[Dragon_Gimer]

Dear experts and officials, we kindly request that you provide us with an explanation regarding this problem, which has caused us great concern.

[Dragon_Gimer]

The problem is that I booked a flight that was supposed to be 17 hours, but when I logged in, it was only 17 minutes. What’s going on?

[Cameron]

Hi, sorry about this. We had some issues with AP+ today due to some side effects from some improvements we are working on. It should be working now for new flights.

We are working on a new behind-the-scenes stats system in 26.1 that aims to solve these issues.

[Dean_Miller]

Unfortunately its still not working. I started an 8 hour 30 min flight today and about 2 hours of it I ran on AP+ and it looks like im going to be arriving about 2 hours early.

Sorry for the bad news.

[Cameron]

If your flight is arriving early, that’s not a fault of the AP+ system from what I understand. A current limitation of the system is that we keep the flight at a constant speed and altitude, so if you planned your flight accounting for different winds, those aren’t applied at this time.

This topic is about the flight times being recorded incorrectly in your logbook, but I can see they are being recorded correctly for your flight:

[Dean_Miller]

I used the wrong verbiage, sorry. I didn’t mean I am actually arriving early relative to zulu time or local. The flight time has 2 hours unaccounted for. Thats all I meant.

[Dean_Miller]

Just confirmed again. What SIMBRIEF claimed would be an 8 hour 56 minute flight time. The flight time in IF reads 01:18. Most of it on AP+

[aviation_lover2]

today I planned a flight from doha to Chicago and left it on ap+ when I checked back in it was over north america with a flight time of just 3 hours. Is this issue still not fixed or will it be fixed in 26.1?

[BennyBoy_Alpha]

Flight time not being recorded

Small update: AP+ flight time not being recorded on the RTM version (non-beta) of the app should be resolved now. There is still an intermittent issue where flight time isn’t saved at all - unfortunately, that will remain until 26.1 is released. Our apologies for the inconvenience, but the fix requires a non-backwards compatible change that will address AP+ issues moving forward and will be included in 26.1.

[aviation_lover2]

sounds unfortunate. Thank you

[Dean_Miller]

I concur. My flight clock is never correct if I use AP+. It is correct on the logs and I think they are happy with that for now while they work on more pressing issues so I stopped pushing on this issue. It’s only a hassle when filling out my PIREP.