Learn why an aircraft stalls while climbing on autopilot, which modes drain airspeed, and how pilots prevent and recover from the stall.
An aircraft stalls while climbing on autopilot when the system keeps commanding pitch or vertical speed after available thrust can no longer maintain airspeed. The speed decays, angle of attack rises beyond the wing’s critical value, and airflow separates. Autopilot controls flight path; it does not guarantee stall protection.
For Aviation & Real-World Flying, the key distinction is that this is an aerodynamic stall, not necessarily an autopilot failure. The wing responds to angle of attack, configuration, loading and airflow regardless of who or what is moving the controls. Our guide to how autopilot modes and control servos work explains that underlying division of responsibility.
What actually causes an autopilot climb stall?
The stall occurs because the autopilot increases or maintains nose-up control while the aircraft lacks enough excess thrust to satisfy the selected climb command. Airspeed falls, angle of attack rises and eventually exceeds the critical angle.
A classic example is climbing in vertical-speed mode at a fixed 1,500 feet per minute. As altitude increases, engine performance and excess thrust may decrease. The autopilot raises the nose to preserve 1,500 feet per minute instead of allowing the climb rate to fade, so airspeed becomes the variable that is sacrificed.
The same problem can occur lower down if climb thrust was never set, the aircraft is unusually heavy, icing is present, or the gear, flaps or speed brakes are not in the expected position. A climbing turn also increases load factor and therefore the indicated speed at which the aircraft may stall.
Autopilot can hide a developing problem because the pilot does not feel steadily increasing back pressure. Some systems also apply nose-up trim while trying to hold the command, leaving significant control force or an abrupt pitch change when the autopilot disconnects.
Common reasons the airspeed disappears
- Excessive selected vertical speed: the requested climb rate exceeds what the aircraft can sustain.
- Insufficient thrust: climb power was not set, autothrottle is in the wrong mode, or the engines are already at their available limit.
- High altitude, weight or temperature: reduced excess performance makes a previously safe climb rate unsustainable.
- Icing or contamination: drag increases and the wing can stall at a higher indicated airspeed than expected.
- Configuration errors: extended speed brakes, gear or inappropriate flap settings consume climb performance.
- Bad air-data information: blocked or faulty pitot-static inputs can cause the autopilot to react to an incorrect airspeed.
Which autopilot mode is most likely to cause a stall?
Vertical-speed mode presents the clearest risk because it prioritises the selected climb rate rather than airspeed. Other modes can also produce a low-energy condition when used incorrectly or without adequate thrust.
| Climb mode | What it prioritises | Low-speed behaviour |
|---|---|---|
| Vertical speed | Selected rate of climb | May increase pitch as performance falls, allowing airspeed to decay. |
| Pitch hold | Selected pitch attitude | Airspeed varies with thrust, drag and aircraft performance. |
| IAS or FLC | Selected indicated airspeed | Normally reduces climb rate first; it may level or descend if thrust is insufficient. |
| VNAV or managed climb | Programmed speed and altitude profile | Behaviour depends on aircraft logic, active thrust mode and entered performance data. |
IAS or flight-level-change mode is generally the better choice when airspeed protection matters more than holding a precise climb rate. It is not infallible: the selected speed must be appropriate, sensors must be valid and the pilot must verify which mode is actually active on the flight-mode annunciator.
A mistake we see constantly in simulators is treating a selected button or panel value as proof that the expected mode engaged. For simulator-specific causes such as incorrect modes, icing, weight and thrust settings, see our MSFS 2020 autopilot climb troubleshooting.
Why does autothrottle not always prevent the stall?
Autothrottle cannot prevent a stall if it is disengaged, operating in the wrong mode or already commanding the maximum available thrust. Autopilot and autothrottle are separate systems even when they normally work together.
No thrust system can produce performance the aircraft does not have. Near the aircraft’s ceiling, an IAS-based climb may correctly let the vertical speed fall towards zero, while a vertical-speed climb may demand increasing pitch until the speed becomes unsafe.
Some aircraft provide minimum-speed reversion, automatic thrust response, angle-of-attack protection or an autopilot disconnect near the stall. Basic general-aviation autopilots may provide none of these, and transport-aircraft protections depend on system status and control law. A warning or automatic disconnect is not a substitute for monitoring the energy state.
How can pilots prevent and recover from it?
Pilots prevent an autopilot climb stall by selecting a sustainable climb command, setting the required thrust and continuously monitoring airspeed and mode annunciations. The exact speeds, power settings and procedures must come from the aircraft’s approved documentation.
- Verify actual engine indications rather than assuming thrust followed the lever or autothrottle command.
- Confirm the active pitch and thrust modes on the flight-mode annunciator.
- Use an airspeed-based climb mode when performance margin is uncertain, unless the aircraft procedure specifies otherwise.
- Reduce the selected vertical speed as altitude increases instead of forcing the original rate.
- Watch the airspeed trend, pitch attitude and thrust limit together. Rising pitch, maximum thrust and falling speed are an immediate warning.
- Check gear, flap, speed-brake and anti-ice configuration before blaming the autopilot.
For a light-aircraft reference, our Cessna 172 flying and climb procedure shows the climb-speed, configuration and checklist discipline that should still be followed when automation is used.
Generic stall recovery sequence
- Take control: disconnect the autopilot and deal with autothrottle according to the aircraft-specific stall procedure.
- Reduce angle of attack: lower the nose enough to unstall the wing. Preserving altitude is secondary.
- Control bank: bring the wings towards level using coordinated inputs without creating another excessive angle of attack.
- Manage thrust and drag: apply thrust as required, retract speed brakes if appropriate and avoid abrupt configuration changes not called for by the procedure.
- Recover smoothly: rebuild airspeed, return to the desired flight path without causing a secondary stall, then identify why the automation allowed the energy loss.
These are generic principles rather than a substitute for the aircraft flight manual, quick-reference handbook or operator procedure. Stall characteristics and automated protections differ substantially between a basic piston aircraft and a fly-by-wire airliner.