Find why an Airbus autopilot pitches down in a flight simulator, read the FMA clues, recover safely, and fix FCU, autothrust or control issues.
An Airbus autopilot usually pitches down because the vertical mode is commanding descent or acceleration, not because the autopilot has failed. In flight simulators generally, check the Flight Mode Annunciator: OP DES, DES, negative V/S or FPA, G/S, a higher speed target, idle thrust, incorrect lever detents or conflicting controller bindings explain most sudden dives.
The autopilot is not an attitude lock. It changes pitch to satisfy the active altitude, vertical-path or speed mode, often while autothrust controls power. Labels and system depth vary between Airbus families and simulated aircraft, but we treat the FMA at the top of the Primary Flight Display as the source of truth.
What does the Airbus FMA show when the nose drops?
The FMA is the decisive clue because it shows what the automation is actually commanding, whereas the FCU only shows selected values. Read it immediately after the pitch change rather than assuming the mode you intended is the mode that engaged.
| FMA indication | What the aircraft is doing | Likely trigger |
|---|---|---|
| OP DES | Using idle thrust and pitch to maintain selected speed during an open descent | A lower altitude was selected and open descent was engaged, often by pulling the altitude selector or activating a mapped command |
| DES | Following the managed descent profile and its constraints | Managed descent was initiated near or beyond top of descent, possibly while the aircraft was already above profile |
| V/S or FPA | Flying the displayed vertical speed or flight-path angle | An unexpectedly large negative value, encoder bounce or a duplicate controller binding |
| G/S or FINAL APP | Following approach vertical guidance | Glideslope or computed approach-path capture, possibly from an unsuitable intercept |
| CLB or OP CLB with a speed increase | Lowering the nose to accelerate while climb thrust is set | A speed restriction was removed, the managed target changed or the aircraft lacks enough energy to climb and accelerate together |
| ALT remains active | Trying to hold the selected altitude | A modest correction may follow an altitude disturbance; a steep sustained descent points to conflicting controls, bad aircraft state or a simulation fault |
| AP1/AP2 disappears | The autopilot has disconnected rather than commanded a descent | Sidestick input, turbulence, protection logic, a noisy axis or a mapped disconnect command |
A mistake we see constantly is confusing selected and managed FCU actions. In standard Airbus logic, choosing a lower altitude does not by itself begin the descent; a descent mode must also be engaged. MSFS pilots can use our explanation of Airbus FCU push/pull and managed-versus-selected modes to identify the intended action.
Is a brief Airbus nose-down command normal?
A brief, shallow pitch reduction can be normal when the aircraft accelerates, captures a vertical path or corrects a small altitude deviation. The key tests are whether the FMA mode makes sense, airspeed remains controlled and the aeroplane stays on a safe flight path.
During CLB or OP CLB, pitch is commonly used to control speed while thrust remains at climb power. If the target speed rises after a restriction is deleted, the nose may lower and vertical speed may temporarily fall. During a managed or open descent, idle thrust combined with pitch-for-speed is also normal.
A sustained steep descent at cruise while ALT is displayed is not normal, particularly without a corresponding altitude error. Repeated nose-up and nose-down corrections around the target are a different fault; use our systematic altitude-oscillation fixes for trim, speed, turbulence and control-conflict checks.
Passing the calculated top of descent alone should not make a normally modelled Airbus descend. The pilot must select a lower altitude and initiate DES or OP DES. If descent starts without that action, suspect an accidental FCU command, an assistance feature, a hardware binding or an aircraft-specific bug.
On approach, check for G/S or FINAL APP capture. The autopilot will follow that path even if it is steeper than expected, so verify the runway and approach loaded in the flight plan, the guidance being received and the intercept geometry. A bad constraint can alter managed descent after DES is active, but it should not independently override an unchanged cruise altitude in standard Airbus logic.
How should I recover from an unexpected autopilot dive?
Disconnect the autopilot and stabilise manually whenever the commanded path is unsafe or unexplained. Troubleshooting the FCU while the aircraft continues towards an overspeed, stall or terrain warning only compounds the original mistake.
- Disconnect the autopilot. Use the normal autopilot-disconnect control and confirm AP1/AP2 has disappeared from the FMA. Avoid pressing several FCU buttons at random.
- Stabilise attitude and bank. Return to a controlled flight path with smooth inputs. Do not make an abrupt high-G pull simply because the vertical-speed indication is large.
- Manage speed with pitch and thrust. Add appropriate thrust if energy is low; reduce excessive thrust and recover smoothly if overspeeding. If a terrain warning is active, prioritise the aircraft’s escape guidance over mode diagnosis.
- Check the automation targets. Confirm selected altitude, speed, V/S or FPA, thrust mode and lever position before attempting to re-engage anything.
- Re-engage only when stable. Select one clear vertical mode, verify its FMA annunciation and monitor the first pitch response.
If AP1/AP2 vanished before the nose dropped, investigate the event as a disconnect rather than an autopilot dive. Our guide to repeated simulator autopilot disconnects covers noisy controls, unstable flight conditions and unwanted assignments.
How do I stop the Airbus autopilot pitching down again?
You stop repeat pitch-downs by finding the trigger shown on the FMA, then correcting the associated mode, thrust or control input. Reinstalling the aircraft should not be the first response.
- Record the evidence. Note the active and armed FMA modes, selected altitude and speed, indicated airspeed, thrust mode, flight phase and whether AP1/AP2 remained engaged. Test at normal simulation rate because acceleration can upset some add-on autopilots.
- Audit the FCU commands. Look for negative V/S or FPA, unintended OP DES, EXPED or APPR activation, and altitude or speed values changed by a mouse wheel or bouncing hardware encoder.
- Check throttle detents. On A320-family simulations, the levers normally remain in the CL detent after the take-off phase so autothrust can command the required power. Poor calibration or axis jitter may switch the aircraft into an unexpected manual-thrust state. The A320 mode, detent and autothrust checks for MSFS cover this failure pattern in more detail.
- Remove duplicate bindings. Search every connected controller for assignments to pitch, pitch trim, altitude selection, vertical speed, autopilot, autothrust, APPR and expedited climb or descent. A noisy pitch axis often disconnects the autopilot; a wrongly assigned FCU encoder may silently select a descent.
- Inspect the flight plan. Resolve discontinuities and implausible altitude or speed constraints. Around top of descent, verify that the selected altitude is appropriate before commanding DES; on approach, confirm that the correct runway and vertical guidance are active.
- Isolate simulation conflicts. Repeat the same flight in clear weather at normal rate with assistance features disabled and aircraft-related modifications temporarily removed. If the FMA shows an impossible mode change with no pilot or controller input, the remaining cause is likely aircraft or simulator logic rather than Airbus procedure.