Why is A320 autopilot or autothrust not working in MSFS?
In Microsoft Flight Simulator, A320 autopilot or autothrust problems are usually caused by Airbus mode logic rather than a broken aircraft: flight directors off, missing FMS or performance data, thrust levers not in the CL detent, the wrong managed or selected mode, or a controller input that disconnects the system.
Check the FMA before touching anything else
The Flight Mode Annunciator at the top of the PFD tells you exactly what the A320 is doing.
- AP1 or AP2 means the autopilot is engaged.
- NAV, HDG, CLB, OP CLB, DES or G/S show which lateral and vertical modes are actually active.
- Thrust and speed cues such as THR CLB, SPEED, MACH or IDLE show what autothrust is doing.
If the FMA does not show the mode you expected, the system is not failing; the setup is wrong. That is a mistake we see constantly because Airbus managed and selected modes do not behave like a typical GA autopilot.
What stops the A320 autopilot from engaging?
The A320 autopilot usually refuses to engage because the aircraft is still in a take-off state, the flight directors are off, the guidance mode is invalid, or a controller is cancelling it.
- Too early on departure: the A320 autopilot is for after lift-off, not the take-off roll. Wait until the aircraft is airborne and stable.
- Flight directors off: Airbus automation expects the flight directors to be on before you ask the aircraft to fly.
- Wrong mode selected: on aircraft that model Airbus logic properly, pulling a knob gives you a selected mode and pushing it asks for managed guidance. If you expected the magenta line but the FMA shows HDG, the autopilot is obeying the selected heading you gave it.
- No valid route or approach data: NAV, managed climb or approach capture may stay unavailable if the flight plan or approach is incomplete.
- Controller conflict: a noisy stick axis, trim input or duplicate disconnect binding can kick AP straight back out. If this happens in several aircraft, start with our general autopilot troubleshooting checklist.
If the A320 can hold a selected heading and altitude but will not follow the route, the autopilot itself is working. The problem is almost always mode selection or FMS setup.
Why won't A320 autothrust arm or stay active?
In the A320, autothrust only works when the thrust levers and mode logic are in the right place, and it does not physically move your hardware levers.
| Symptom | Likely cause | Fix |
|---|---|---|
| Autothrust seems armed but airspeed is not controlled | Levers are not in CL, or there is no valid speed/thrust mode | Place both levers in CL when the aircraft expects it and confirm the FMA shows a speed or thrust mode |
| Engines stay at take-off or climb thrust | Levers were left in TOGA or FLX/MCT | Reduce both levers to CL after take-off thrust is no longer required |
| Autothrust drops out or hunts | Throttle axis noise or bad detent calibration | Check hardware calibration and test with only one throttle device connected |
| You think autothrust is broken because the levers do not move | That is normal Airbus behaviour | Watch the engine indications and FMA, not the physical position of your hardware levers |
| Managed speed on descent or approach is wrong | Arrival or approach setup is incomplete | Check the MCDU arrival data and make sure the aircraft has entered the correct approach logic |
The biggest A320-specific trap is simple: after take-off, many simmers leave the thrust levers above CL and then assume autothrust is broken. In Airbus aircraft, the levers normally stay in CL for the rest of the flight unless a procedure calls for something else.
Does the MCDU have to be programmed for autopilot and autothrust to work?
For basic selected heading, altitude and speed, no. For normal Airbus managed navigation, climb, descent and speed, yes.
If the route, performance data or approach setup is missing, NAV, managed climb/descent and managed speed may behave oddly or stay unavailable. If you need the exact order, see our walkthrough for setting up the A320 MCDU and FMS correctly and our step-by-step A320 flight flow, which make it much easier to spot where the automation setup went wrong.
What should I check in order?
This short sequence finds most A320 autopilot and autothrust faults quickly.
- Confirm which A320 you are flying. The built-in A320neo and third-party A320s do not enforce identical logic, so use the right procedure for that aircraft.
- Read the FMA first. If AP1/AP2 or the expected thrust or speed mode is absent, stop pressing buttons and fix the setup.
- Put the aircraft in a valid Airbus state. Flight directors on, airborne and stable for autopilot, and both thrust levers in CL once take-off thrust is no longer required.
- Check managed versus selected modes. Make sure you have actually armed NAV, CLB, DES or a selected heading, speed or altitude as intended.
- Verify the FMS entries. If route, weights, performance or approach data are wrong, the A320 may ignore the behaviour you expected.
- Eliminate hardware conflicts. Remove duplicate bindings, watch for jittering stick or throttle axes, and test with unnecessary controllers unplugged.
- Rule out aircraft package problems. If you use the FlyByWire A32NX and the aircraft half-loads, detents never register or modes are missing, start from a clean A32NX installation.
If the A320 can fly selected modes but not managed modes, the autopilot is not the problem. In Microsoft Flight Simulator, that almost always points to A320 setup, thrust lever position or controller conflicts rather than a failed aircraft system.