AP disconnect on ILS finals
-
I made 2 flights since latest update. One with F70 and one with F100. On both I used an ILS approach, and on both approaches the AP suddenly disconnected while on final. I have checked for any key binding issues but didnt find anything. Both disconnects occurred more or less at the same stage of the approach I believe, around the time the flaps 42 callout came and I was selecting full flaps.
Anybody else had this? Is there any particular limitation for AP use om approach? Or is that a bug or what could have triggered that? Any advise would be appreciated, many thanks !
-
I'm not aware of any bugs, new or old, that'd be causing this. The only thing that comes to mind is the trim disconnect if sustained stab/elevator trim inputs by the pilot are detected, but presumably you aren't making any trim inputs?
I was flying the RNP Y approach for RWY 06 into Vitória (SBVT) today. Right in the middle of the procedure, the autopilot suddenly disconnected completely on its own, without any input from my end. Immediately following this uncommanded disconnect, the aircraft aggressively pitched down into a severe nose dive.
We are already aware of the pitch-down tendency when manually disconnecting the AP for landing, but having the autopilot drop out uncommanded and instantly throw the nose down during an RNP procedure is a critical failure...
I caught this specific behavior on video, and you may watch it here: https://www.youtube.com/watch?v=UhpcDVPt8Ak
-
I had similar on my flight earlier to Manchester ILS 05R approach. Sudden disconnect of the autopilot.
-
Hi all. As we aren't guaranteed to be able to reproduce the issue here, and didn't encounter it during our v1.2 pre-release testing, it'd be great if some of you could try this updated WASM gauge to see if it helps: WASM Download
The WASM, which has MSFS 2020 and 2024 versions, needs to replace the existing one that is found in: \justflight-aircraft-f100\SimObjects\Airplanes\Just Flight Fokker F100 Airstairs Small\panel
\justflight-aircraft-f70\SimObjects\Airplanes\Just Flight Fokker F70\panel\Thanks for your feedback and assistance, and apologies for the inconvenience.
-
Note this reverts a couple of recent changes - AP auto-trim, aimed at addressing the out of trim condition when disconnecting the AP, and the introduction of the 1.5 second manual trim input AP disconnect. Those are the most likely causes of this new issue. If the issue no longer occurs with these reversions then we can work to reintroduce those improvements without causing the issue.
-
Hey Martyn, many thanks. I´ll give it a try and report back
-
Martyn, just did an ILS into LOWW 34 and AP did not disconnect (as expected due to the mentioned reversion - when disconnecting manually close to minimums out of trim was severe)
Another item which I was wondering if with this wasm file has also reverted is the AT speed under- and overshooting - on final it overshoot App speed by at least 40kt....so quite an unstable approach altogether, but AP did hold LOL -
Martyn, just did an ILS into LOWW 34 and AP did not disconnect (as expected due to the mentioned reversion - when disconnecting manually close to minimums out of trim was severe)
Another item which I was wondering if with this wasm file has also reverted is the AT speed under- and overshooting - on final it overshoot App speed by at least 40kt....so quite an unstable approach altogether, but AP did hold LOLThanks both for confirming that fixed the issue.
I can confirm that no other changes were reverted, including the ATS logic. I've not encountered such a significant speed overshoot so hopefully that was a one off. If not, please get in touch with our support team so they can investigate.
-
I can confirm the abovementioned observations: MSFS 2024, unaltered version 0.1.2, F100 (OE-LVI from the livery installer), ILS 08L into LROP. Flaps 42, AP and AT on until the AT undershoots the V_App (138 kts in this case) by about 10 (?) knots. AP disconnects with aural alert, AT stays engaged, aircraft pitches down (probably due to the thrust increasing significantly at that moment). Looks to me like the AP disconnect was triggered by an underspeed (V_MA) protection.