Why is A320 autopilot or autothrust not working in MSFS?
Fix A320 autopilot or autothrust problems in MSFS by checking FMA modes, FCU logic, thrust detents, MCDU setup and controller conflicts.
In Microsoft Flight Simulator, A320 autopilot or autothrust failures are usually caused by Airbus mode logic, not a broken aircraft: the aircraft is not in a valid engagement state, the wrong FCU mode is active, the flight plan is incomplete, the thrust levers miss the CL detent, or a controller input disconnects automation.
The default and third-party A320s do not model every condition identically. The reliable diagnostic is therefore the aircraft's Flight Mode Annunciator, followed by a test in simple selected modes.
Check the Flight Mode Annunciator first
The Flight Mode Annunciator, or FMA, at the top of the Primary Flight Display shows what the A320 is actually doing rather than what the FCU knobs appear to request.
- AP1 or AP2 confirms that an autopilot is engaged. Normally, use one; both are reserved for an eligible dual-autopilot approach on aircraft that model it.
- NAV, HDG and LOC identify the active lateral guidance.
- CLB, OP CLB, DES, OP DES, V/S, ALT and G/S identify the vertical mode.
- THR CLB, SPEED, MACH and IDLE describe what autothrust is commanding.
- Active modes are normally shown in green, while blue modes are armed and waiting for their capture conditions.
If a mode is blue rather than green, it has not captured yet. If the expected mode is absent, the aircraft was not given valid guidance or a capture condition has not been met. Our guide to the A320 displays, FCU and FMA indications explains where each status appears.
Why won't the A320 autopilot engage?
The A320 autopilot normally refuses to engage when the aircraft is still on the ground, has only just lifted off, lacks valid attitude or navigation data, is outside a sensible flight condition, or is receiving a manual control input.
- Wait until airborne: do not engage AP1 or AP2 during the take-off roll. Allow several seconds after lift-off and stabilise the pitch and bank first.
- Turn on both flight directors: this is the normal Airbus operating state and ensures the intended guidance is visible before AP engagement.
- Check ADIRS and instruments: after a cold-and-dark start, the inertial systems must be aligned and the PFD must show valid attitude, heading and air data. Red flags or missing navigation data point to an aircraft-initialisation problem, not an FCU problem.
- Use a valid mode: selected heading and altitude guidance can work without a complete route. Managed NAV, climb and descent need appropriate flight-plan data and capture geometry.
- Return the sidestick to neutral: deliberate sidestick input disconnects the Airbus autopilot. Axis jitter can produce the same result in the simulator.
- Check failures and assistance: enabled aircraft failures, AI piloting and control assistance can inhibit or override automation.
A useful isolation test is selected heading mode. Stabilise the aircraft, select a safe heading and altitude, pull the relevant FCU knobs for selected guidance, then engage AP1. If it holds selected modes but not the magenta route, the autopilot is working; the fault is in managed-mode selection, route validity or intercept geometry.
Why does AP1 or AP2 disengage immediately?
An A320 autopilot that engages and drops out immediately is usually receiving a control command or detecting an invalid flight condition.
Look for a noisy sidestick, rudder or trim axis; duplicate autopilot-disconnect assignments; a held keyboard command; or two devices bound to the same flight-control axis. Add a small dead zone where necessary and test with nonessential controllers unplugged. If the same problem affects several aircraft, use our cross-aircraft autopilot engagement and control-conflict checks.
Excessive pitch, bank, speed deviation or an active flight-control protection can also cause refusal or disconnection. Recover manually to a stable attitude and speed before trying again; repeatedly pressing AP1 does not correct the underlying condition.
Why is A320 autothrust armed but not controlling speed?
A320 autothrust can be armed without actively controlling speed, especially during take-off or when the thrust levers are outside the required detent.
| FMA or symptom | What it means | What to do |
|---|---|---|
| A/THR shown in blue with MAN FLX or MAN TOGA | Autothrust is armed, but the thrust levers are commanding manual take-off thrust. | At the normal thrust-reduction prompt, move both levers to CL. |
| A/THR active with THR CLB | Climb thrust is being commanded. Pitch, not changing engine thrust, controls speed in CLB or OP CLB. | Check the vertical mode and avoid demanding an excessive climb rate. |
| SPEED or MACH | Autothrust is modulating thrust to hold the managed or selected target. | Confirm that the target shown on the PFD is the one intended. |
| IDLE during descent | The system has already reduced thrust to idle; path, pitch and drag must manage excess energy. | Check the descent mode and use speed brake when operationally appropriate. |
| Virtual levers flicker around CL or disagree | The throttle axis or detent calibration is incorrect or noisy. | Calibrate the aircraft's detents where supported, adjust the controller dead zone and remove duplicate throttle bindings. |
| A.FLOOR followed by TOGA LK | Alpha-floor protection commanded high thrust because the aircraft approached an excessive angle of attack. | Correct the flight path and speed first, then use the aircraft's normal autothrust disconnect and re-engagement procedure. |
| THR LK | Thrust was locked after autothrust disconnected while the physical levers did not match the commanded thrust. | Move the levers to match the indicated thrust, stabilise the aircraft and reset autothrust if required. |
The common post-take-off mistake is leaving one or both levers in FLX/MCT or TOGA. In normal flight, the levers remain in CL so autothrust can command anything from idle up to the climb-thrust limit.
If the simulated levers will not remain in the detent, use the calibration facility provided by that aircraft, if it has one. Otherwise, adjust the Microsoft Flight Simulator throttle profile and dead zone. Test with a single throttle axis before reconnecting other hardware.
Why don't the A320 thrust levers move with autothrust?
Airbus autothrust does not physically move the cockpit or hardware thrust levers; it varies engine thrust within the limit selected by the fixed lever position.
Judge it by the FMA, commanded N1 or thrust indication, and aircraft speed. During landing, the RETARD callout is an instruction to move the levers to idle manually, not evidence that autothrust has failed.
Autopilot and autothrust are separate systems. Either can operate without the other, although without autopilot the pilot must manually follow the flight director and pitch commands needed to maintain the intended speed or path.
Does the MCDU have to be programmed for autopilot to work?
No: basic selected heading, altitude, vertical speed and speed modes can work without a complete flight plan, but normal managed navigation, climb, descent and approach guidance depend on valid MCDU data.
On the Airbus FCU, pulling a knob normally selects a pilot-entered value; pushing it requests managed guidance. Merely setting a new altitude does not always start a climb or descent. The altitude knob must be pushed for managed CLB or DES, or pulled for OP CLB or OP DES, once a valid target has been set.
If selected heading works but NAV does not, check for:
- no active flight-plan leg or a waypoint left behind the aircraft;
- an uninserted temporary flight-plan revision;
- a route discontinuity before the desired leg;
- an unsuitable intercept angle or position relative to the active leg;
- missing departure, arrival or approach data;
- an incorrectly activated approach phase or unexpected speed constraint.
Do not automatically delete every discontinuity. A manual or vectors segment may be intentional and should be handled according to the procedure or ATC instruction. For a full setup check, follow our method for programming the A320 MCDU and correcting route discontinuities.
What should I check, in order?
This sequence separates an Airbus setup mistake from a controller, aircraft-package or simulator fault.
- Identify the aircraft variant. Default and add-on A320s differ in system depth, detent calibration and failure modelling, so do not assume one aircraft's procedure applies exactly to another.
- Read the FMA. Record the active and armed lateral, vertical and thrust modes before pressing more buttons.
- Stabilise the aircraft. Use a safe attitude, speed and altitude; centre the controls; switch on both flight directors; and confirm valid PFD data.
- Test selected guidance. Try a selected heading and a modest, safe altitude command. If AP1 follows these, the basic autopilot is serviceable.
- Test managed guidance. Confirm the active route leg, clear only inappropriate discontinuities, and use the correct push action on the FCU.
- Check autothrust separately. Confirm its FMA status, put both thrust levers in CL when required, and verify that the selected or managed speed target is sensible.
- Eliminate hardware conflicts. Remove duplicate bindings, inspect axis movement for jitter and test with unnecessary controllers disconnected.
- Review the operating sequence. Our A320 flight flow from take-off through approach shows where managed modes, thrust reduction and approach arming normally occur.
When is it actually an aircraft or simulator fault?
Suspect an aircraft package or simulator fault only after selected modes also fail in a stable, correctly powered aircraft with controller conflicts ruled out.
Start a fresh flight rather than a saved cockpit state, disable AI control and configured failures, and test without nonessential Community-folder packages. If only one A320 package fails, repair or update that aircraft through its supported installation method. If every aircraft suffers the same immediate disconnection, the controller profile or simulator assistance settings are the more likely cause.