Autopilot when enabled, in practice fails to work at bare minimum on the new A35K, resulting in the aircraft either performing a 3000 fpm dive, or 6000 fpm nose up manuever, resulting in crashes seconds after departure from busy airports like EGLL.
Device Iphone 17 Pro Max
Operating system iOS 26.5.2
Same issue on my end, LNAV overcorrects the heading and setting a VS results in either a rapid climb or descent, i also had the aircraft level itself out to 0fpm and then within 30 seconds gradually increase to 4000+
Same here. I have a video.
I’m unable to repro here. Is there anything special about your setup? Are you using any 3rd party tools connected to the api at all?
Does a reinstall of the app help?
Persnoally not using any external device, etc, I know a couple people in the IF discord are reinstalling, I may do so too, in the coming few minutes.
@here
Which app version are you on?
I would like to hear if that helps. I made a topic on this also and had to cancel a project sunrise flight
Same problem, it can’t maintain a stable GS, it keeps increasing VS until it stalls and disengages AP
There was an in-game OTA rollout before the App Store release. That means you can get the 35K update just by restarting the game. However, this 35K build has an AP bug. The bug will be fixed once you update to version 26.3 via the App Store. This is how I resolved the issue.
Same problem, it can’t maintain a stable VS, it keeps increasing VS until it stalls and disengages AP
I just had this issue departing Sydney a bit ago, and it also manifested with the aircraft randomly turning away from the heading i had set with autopilot
Ill see if this works shortly.
I think the faulty OTA for build 35K is to blame. It’s incompatible with version 26.2, which caused the “bug”. The issue will be gone once we properly update to 26.3.
This is the solution guys, it is working properly now. Thank you
It’s all just to give everyone a better flying experience. Thanks!
update to 26.3 via your App Store.
The A35K is technically accessible on 26.2 but it’s bugged.
UPDATE the app that’s the fix.
Assuming this means we should avoid the beta for now?
