Aviation & Real-World Flying 7 min read 123 views

Why does an aircraft stall while climbing on autopilot?

Ian Stephens
In short

Why does an aircraft stall while climbing on autopilot? Understand V/S, MCP SPD, minimum-speed protection, prevention and stall recovery.

An aircraft can stall while climbing on autopilot because vertical-speed or pitch mode keeps commanding nose-up attitude after available thrust can no longer support both the climb and the airspeed. Speed decays, angle of attack reaches its critical value and the wing stalls; autopilot engagement by itself provides no universal stall protection.

In Aviation & Real-World Flying, this is primarily an aerodynamic and energy-management problem, not proof that the autopilot has malfunctioned. The wing responds to angle of attack regardless of whether the pilot or an automatic flight-control system moves the elevator.

What actually causes an autopilot climb stall?

An autopilot climb stall develops when the selected vertical command demands more performance than the aircraft can provide. In vertical-speed mode, the autopilot normally uses pitch to maintain the selected rate while the pilot or autothrottle manages speed with thrust.

Suppose 1,500 feet per minute is selected. If available thrust can sustain only 700 feet per minute at the required speed, a basic V/S system keeps raising the nose to obtain the missing climb rate. The extra climb energy comes from airspeed until the wing approaches its critical angle of attack.

The loss of performance may result from:

  • Excessive selected vertical speed: the commanded climb rate is unsustainable at the aircraft's weight and altitude.
  • Insufficient thrust: climb thrust was not set, autothrottle is disengaged or the engines have reached their thrust limit.
  • Altitude and temperature: reduced excess thrust makes a climb rate that worked lower down impossible to maintain.
  • Configuration: landing gear, speed brakes or unsuitable flap settings add drag.
  • Icing or contamination: drag increases and the wing may stall at a higher indicated speed than expected.
  • Turning flight: bank increases load factor and reduces the available stall margin.
  • Bad air-data input: erroneous pitot-static information can mislead the autopilot and autothrottle.

The margin can become especially narrow near the aircraft's ceiling. Our explanation of high-altitude stall margins and reduced climb performance covers that case in more detail.

If MCP SPD | HDG SEL | V/S is engaged, what happens at minimum speed?

On the Boeing 737-style system normally implied by MCP SPD | HDG SEL | V/S, a serviceable autopilot with valid air data should sacrifice the selected vertical speed as minimum-speed protection becomes active. It should not maintain the commanded climb rate all the way into a stall.

  • MCP SPD: the autothrottle is controlling thrust in an attempt to maintain the speed selected on the Mode Control Panel.
  • HDG SEL: the roll mode is turning or maintaining the selected heading. It does not manage airspeed.
  • V/S: the pitch mode is commanding the selected vertical speed.

If airspeed falls despite MCP SPD, the autothrottle normally adds thrust until it reaches the available limit. As the aircraft reaches its computed minimum manoeuvring speed, V/S speed-protection logic should reduce nose-up pitch and allow the actual climb rate to fall, potentially towards zero, rather than permit further speed decay.

The exact annunciation depends on the aircraft variant, installed software and how faithfully the simulator aircraft models the Automatic Flight Director System. The V/S indication may remain while its command is limited, or the system may present a mode reversion or other protection cue. The Flight Mode Annunciator is the authority, not the fact that a button was pressed. Our practical guide to reading and verifying Boeing 737 autopilot modes explains that workflow.

Protection may also differ when only the flight director is being followed rather than the autopilot being engaged. Basic aircraft, failed sensors and simplified simulator implementations may provide no equivalent protection. If the simulated aircraft keeps pitching up into a low-speed warning, intervene rather than waiting for an expected automatic response.

Do all minimum-speed indications mean the same thing?

A flap manoeuvre-speed bug is not necessarily the same as the minimum manoeuvring boundary or the onset of stall warning. Confusing these cues leads to incorrect expectations about when automation should react.

Speed cueWhat it representsExpected automation response
Selected MCP speedThe autothrottle's commanded targetThrust changes first; reaching this speed does not itself prove that low-speed protection is active.
Flap manoeuvre speedA recommended manoeuvring or flap-schedule speedUsually no automatic pitch response merely because the bug is reached.
Minimum manoeuvring boundaryA computed lower operating margin for the present configurationAircraft-specific AFDS protection may limit the climb or command a lower pitch.
Stick shaker or stall warningAn immediate warning that angle of attack is approaching the stall regionThe autopilot may disconnect, but the pilot must not depend on an automatic disconnect or recovery.

Symbology and terminology vary between aircraft. The correct interpretation comes from that aircraft's flight manual, not from transferring one airliner's speed-tape behaviour to another.

Why does MCP SPD or autothrottle not guarantee protection?

MCP SPD does not guarantee safe airspeed because autothrottle controls thrust, while V/S controls pitch. Once maximum available thrust is reached, the engines cannot satisfy an excessive climb command.

Autothrottle may also be armed but not actively controlling speed, operating in an unexpected mode or responding to incorrect sensor data. A common simulator mistake is to read the selected speed in the MCP window without checking the active autothrottle mode and actual engine indications.

Even correctly operating protection has limits. Turbulence, icing, abrupt bank changes or invalid air data can consume the remaining margin quickly. Light-aircraft autopilots often have no minimum-speed protection at all, and some will continue holding pitch or vertical speed until disconnected.

Which autopilot mode is safest for climbing?

An indicated-airspeed or flight-level-change mode is generally preferable when maintaining airspeed matters more than holding a precise climb rate. These modes use pitch to protect the selected speed, allowing the climb rate to decrease as performance falls.

Pitch modePrimary targetBehaviour when thrust is insufficient
V/SSelected vertical speedAirspeed may decay until aircraft-specific speed protection intervenes.
IAS, FLC or FLCHSelected airspeedClimb rate decreases first; the aircraft may level if little excess thrust remains.
Pitch holdSelected pitch attitudeBoth speed and climb rate vary with thrust, drag and atmospheric conditions.
VNAV or managed climbProgrammed speed and vertical profileResponse depends on performance data, thrust mode and aircraft-specific logic.

FLC and FLCH cannot create performance that the aircraft lacks, and an unsuitable selected speed can still produce unexpected pitch. See our explanation of how FLCH uses pitch to control speed before treating it as automatic stall prevention.

How do you prevent an autopilot climb stall?

Preventing an autopilot climb stall requires monitoring the aircraft's energy state rather than assuming the selected automation mode will protect it.

  1. Read the FMA: verify the active pitch, roll and thrust modes after every selection or altitude constraint.
  2. Check actual thrust: confirm engine indications rather than relying only on lever position or an illuminated autothrottle switch.
  3. Watch the trend: falling speed combined with rising pitch and high thrust means the climb command is becoming unsustainable.
  4. Reduce the demand: lower the selected vertical speed or use the aircraft-approved airspeed-based climb mode before reaching the low-speed boundary.
  5. Check configuration: verify flaps, gear, speed brakes, anti-ice use and aircraft weight assumptions.
  6. Account for turns: avoid combining an aggressive climb command with unnecessary bank when the speed margin is small.

Autopilot trim can mask the increasing control force that a hand-flying pilot might otherwise notice. Be prepared for a trim load or pitch change when disconnecting an autopilot that has been commanding nose-up trim.

What should you do if the aircraft reaches stall warning on autopilot?

If stall warning occurs, follow the aircraft's approved stall-recovery procedure immediately; maintaining the selected altitude or vertical speed is no longer the priority.

  1. Take control: disconnect the autopilot and manage the autothrottle as specified for the aircraft.
  2. Reduce angle of attack: lower the nose enough to remove the stall warning and restore attached airflow. Adding power alone may not unstall the wing.
  3. Manage thrust and bank: apply appropriate thrust, reduce excessive bank and remove unnecessary drag without making unapproved configuration changes.
  4. Rebuild airspeed: accept the required altitude loss and avoid an abrupt pull-up that causes a secondary stall.
  5. Reassess the automation: identify the active modes, thrust limit, configuration and sensor state before re-engaging the autopilot.

These are generic priorities, not a substitute for the aircraft flight manual or operator procedure. Our detailed explanation of why reducing angle of attack comes first during stall recovery covers the aerodynamics and altitude-loss trade-off.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members