iPad Air 5 M1 Chip 8 8Gb RAM
iOS 26.5
It’s again happened twice now to me, when I returned back from AP+ that either SPD or LNAV was turned off.
I realized the loss of AP speed control late and was barely able to recover.
Hello, @Jugliar
This has happened to me a lot.
What I do to get a Temporary fix is I re-download the app, and that usually fixes it, Temporary!
Let me know if it does not fix your issue.
I don’t know, if something has changed, but now it’s like that: When I return from AP+ and open the AP UI, LNAV is turned off, but it turns on again after a few seconds by its own.
That is ok for me.
But thank you for your concern and possible solution 
That’s very interesting.
1 Like
Happened to me like 10 mins ago…
Reopened this as it’s apparently happening?
Yep, happened twice yesterday. Luckily, my flight path was pretty straightforward, but otherwise I could’ve ended up who knows where lol.
@here
Next time any of you experience this, let me know exactly which flight you had it on and what time it was when you resumed it, and noticed the issue.
A few pointers though:
1. LNAV switching off and coming back on by itself (what most of you are seeing)
This one is actually intentional, even though it looks like a bug. When you resume a flight from AP+, the app places your aircraft back into the world based on where the server flew it, but the winds around you may have changed since you left. If LNAV kicked in immediately, the autopilot could make an aggressive correction based on stale data. So on purpose, the app briefly holds the wings level for about 5 seconds to let everything stabilize, then re-engages LNAV (and VNAV) on its own. That’s the “LNAV is off but turns itself back on” behavior - the aircraft was never actually uncontrolled during those few seconds.
2. LNAV staying off and NOT coming back (the dangerous one)
This is a real issue, and thanks to this thread we’ve now pinned down at least one cause. That automatic re-engage I described above only tries once, and it can silently fail. The main way that happens: if your navigation source was set to NAV1 (for example, you’d pre-tuned the ILS for your destination before walking away, a pretty common habit), the app currently clears any tuned station that’s far away from you when the flight is restored. Your destination ILS is obviously hundreds of miles ahead at that point, so it gets wiped, which is also why some of you noticed your NAV frequency disappearing after resuming. With nothing tuned on NAV1, LNAV refuses to re-engage, the only warning is a small message that’s easy to miss right after loading in, and the aircraft just keeps flying straight ahead.
Thank you Sir, for this profound answer 