Boeing MCAS explained: what the 737 MAX system senses and moves, when it activates, how it was redesigned, and what sim pilots should expect.
Boeing MCAS (the Maneuvering Characteristics Augmentation System) is a 737 MAX flight-control software function that commands nose-down horizontal-stabiliser trim in manual, flaps-up flight at elevated angle of attack. It was added to preserve required handling qualities; it is neither an autopilot nor a stand-alone stall-prevention system.
For our Aviation & Real-World Flying readers, the key distinction is that MCAS is logic executed by the flight-control computers as part of the Speed Trim System. It is not an angle-of-attack sensor, a separate computer or a dedicated trim motor. Nor is every automatic stabiliser movement on a 737 MAX caused by MCAS.
What does MCAS mean in aviation?
In this Boeing context, MCAS stands for Maneuvering Characteristics Augmentation System, using the official American spelling of “Maneuvering”. The name describes its purpose: augmenting the aircraft’s handling characteristics during a narrow part of the flight envelope.
The system receives flight data, decides whether its activation conditions have been met and sends a command through the existing electric stabiliser-trim system. Under ordinary airline-style operation, it should remain dormant and may never produce a noticeable input.
Why did Boeing add MCAS to the 737 MAX?
Boeing added MCAS because the 737 MAX develops different pitch characteristics from earlier 737 generations at elevated angles of attack. Its larger LEAP-1B engines and nacelles are mounted farther forward and higher than the engines on previous models.
At high angle of attack, airflow around the nacelles can produce additional lift ahead of the centre of gravity. This can increase the aeroplane’s pitch-up tendency and reduce the expected increase in control-column force as the wing approaches a stall. MCAS commands nose-down stabiliser trim to restore the required force gradient and handling response.
It is misleading to describe MCAS simply as compensation for heavier engines or high thrust. Engine thrust can affect pitch, but MCAS is triggered by angle-of-attack and flight-condition logic rather than throttle position. Our explanation of the aerodynamic and system differences between the MAX and earlier 737s covers the broader design changes without reducing them to MCAS alone.
How does the revised Boeing MCAS system work?
The revised MCAS function checks several conditions before it can command stabiliser movement, then limits what it can do during one elevated-angle-of-attack event.
- Confirm the flight mode: MCAS is available in manual flight with the autopilot disengaged and the flaps fully retracted. It is not supposed to operate with the autopilot engaged or the flaps extended.
- Compare angle-of-attack inputs: The flight-control computers compare data from both angle-of-attack vanes. A disagreement of 5.5 degrees or more under the applicable conditions inhibits MCAS. Flight-deck disagreement indications are provided when their separate alert criteria are met.
- Check the activation threshold: The sensed angle of attack must exceed the threshold scheduled for the applicable flight conditions, including Mach. A nose-up attitude by itself does not activate MCAS.
- Command nose-down stabiliser trim: MCAS uses the electric trim system to change the horizontal stabiliser’s incidence in the nose-down direction. It does not directly push the control column or move the elevators.
- Limit and reset the command: The revised system makes one limited command for an elevated-angle-of-attack event. Another activation requires angle of attack to fall below the activation region and then rise into it again.
- Retain pilot authority: Pilots can oppose the revised command through the control column, use their electric trim switches to command trim and, when required by the approved checklist, remove electrical stabiliser drive with the stabiliser trim cut-out system.
The wider Speed Trim System can also command stabiliser trim during manual flight, while the autopilot uses pitch-control and trim functions of its own. Automatic trim movement therefore does not prove that MCAS is active.
Does MCAS respond to pitch attitude or angle of attack?
MCAS responds to sensed angle of attack, not simply to how high the nose appears above the horizon. Angle of attack is the angle between the wing’s reference line and the relative airflow.
An aeroplane can have a pronounced nose-up attitude without being at high angle of attack, particularly during a climb. It can also reach a high angle of attack at a less dramatic pitch attitude if its flight path is descending. This is why recreating MCAS in a simulator requires more than pulling the nose to an arbitrary pitch angle.
What part of the plane does MCAS move?
MCAS moves the trimmable horizontal stabiliser through the aircraft’s electric trim mechanism; it does not directly move the elevators. The stabiliser is the larger adjustable tailplane, while the elevators are hinged control surfaces used for the pilots’ immediate pitch commands.
Changing stabiliser incidence changes the elevator force required to maintain a pitch attitude. An unwanted nose-down trim command can therefore feel like steadily increasing back-pressure on the control column. If the aeroplane becomes severely mistrimmed, the required force can become very high even though the elevators remain connected to the pilots’ controls.
Our guide to how elevators, stabilisers and trim affect aircraft pitch explains this mechanical distinction in more detail.
MCAS also does not make the 737 MAX a full fly-by-wire aeroplane. The MAX retains conventionally arranged, hydraulically powered primary flight controls, with MCAS adding a specific automatic trim function. See our explanation of sensors, flight-control computers and full fly-by-wire control laws for the difference.
Is MCAS an autopilot or stall-protection system?
No. MCAS is handling augmentation, not an autopilot, automatic recovery mode or hard stall-protection system.
- It does not fly a selected route or altitude. The autopilot must be disengaged for MCAS to activate.
- It does not impose an angle-of-attack limit. A pilot can still stall the aircraft.
- It does not replace stall warning. Stick shaker and related warnings are separate functions, although they may use data from the same angle-of-attack sensors.
- It is not active whenever the nose rises. Flap position, autopilot status, angle of attack and other scheduled conditions determine availability.
A failed angle-of-attack sensor can consequently cause warnings or conflicting indications even when revised MCAS logic detects the disagreement and inhibits an MCAS command. Inhibition reduces one hazard; it does not make the bad sensor data disappear from every aircraft system.
How did the original and revised MCAS differ?
The original MCAS could act on one erroneous angle-of-attack input and could command trim repeatedly. The return-to-service redesign cross-checks both sensors, prevents repeated commands during one continuous high-angle-of-attack event and limits command authority.
| Feature | Original MCAS | Revised MCAS |
|---|---|---|
| Angle-of-attack input | Used one of the aircraft’s two sensors at a time | Compares inputs from both angle-of-attack sensors |
| Sensor disagreement | One erroneous active input could trigger MCAS | Disagreement beyond the defined threshold inhibits MCAS |
| Repeated activation | Could activate again after opposing pilot electric trim if the erroneous high reading remained | One command per elevated-angle-of-attack event; angle of attack must reset before another activation |
| Trim authority | Repeated commands could accumulate substantial nose-down stabiliser trim | The limited command can be countered using the control column |
| Crew information | MCAS information and training were inadequate for the failure scenario | Updated procedures and training address MCAS and related stabiliser failures |
A 737 MAX approved for service after the grounding uses the revised configuration. Simulator add-ons may deliberately reproduce the original logic for a historical scenario, but that behaviour should not be presented as the normal return-to-service system.
What went wrong in the two 737 MAX accidents?
Erroneous angle-of-attack data activated the original MCAS on Lion Air Flight 610 on 29 October 2018 and Ethiopian Airlines Flight 302 on 10 March 2019. Because the original design relied on one sensor at a time, it could treat a single false high reading as valid.
MCAS then repeatedly commanded nose-down stabiliser movement after opposing electric-trim inputs from the pilots. The crews were also dealing with stick shaker, conflicting indications, high workload and increasing control forces. Both aircraft crashed, killing 346 people.
MCAS was central to both accident sequences, but the investigations extended beyond one software function. They examined system architecture, certification and safety assumptions, information supplied to crews, training, maintenance and the expectation that pilots would recognise and respond to the stabiliser behaviour within a short period. The accidents led to the worldwide grounding, software redesign, revised procedures and additional pilot training.
Can pilots switch off or override MCAS?
There is no dedicated MCAS OFF switch. Crews respond to uncommanded stabiliser movement using the approved non-normal procedure rather than attempting to identify the particular software function while controlling the aircraft.
Pilot electric-trim commands override MCAS input. The revised system’s authority is also limited so that its command can be opposed through the control column. If the applicable procedure directs use of the stabiliser trim cut-out switches, removing electrical drive prevents MCAS, Speed Trim and other electrical sources from moving the stabiliser.
Manual stabiliser trim remains available after electrical cut-out, but it should not be described as effortless under every condition. High airspeed, aerodynamic loading and severe mistrim can make the manual trim wheel difficult to operate. Approved aircraft checklists, operator training and regulator-approved memory items take precedence over any general description.
How should MCAS behave in a flight simulator?
A correctly modelled revised MCAS should remain inactive during normal airline-style flying and should never operate with the autopilot engaged or the flaps extended. A routine take-off pitch change while take-off flap is still selected is therefore not MCAS.
Simulator aircraft vary substantially. A detailed MAX add-on may model both angle-of-attack sensors, disagreement inhibition and the one-command-per-event restriction. Another aircraft may provide only a visual MAX model, simplified nose-down trim or no functional MCAS at all. Product documentation matters more than the aircraft name painted on the fuselage.
| Simulator symptom | What it suggests | What to check |
|---|---|---|
| Nose-down trim with the autopilot engaged | Not valid MCAS behaviour | Inspect the active autopilot pitch mode, selected altitude or vertical path, trim state and add-on logic |
| Trim movement with flaps extended | MCAS should be inhibited | Confirm the indicated flap position, flap-axis calibration and whether the add-on reads the simulator’s actual flap state |
| Repeated trim during steady, low-angle-of-attack flight | More likely another system, input fault or modelling error | Check Speed Trim, autopilot modes, duplicate trim assignments, a stuck trim button, noisy hardware and enabled failure options |
AOA DISAGREE appears but MCAS continues to command trim | The add-on may use original or simplified logic | Check whether a historical mode is selected and whether dual-sensor comparison is actually modelled |
| No MCAS response during a deliberate test | The model may omit MCAS or its conditions have not been met | Verify autopilot status, flaps-up indication, angle of attack, sensor failures and the developer’s stated system coverage |
A mistake we see constantly is assigning pitch trim to more than one controller. A noisy rocker switch, joystick button or axis can then produce persistent stabiliser movement that looks like a system failure. Remove duplicate assignments and test the controls at a safe altitude before blaming MCAS.
Centre-of-gravity errors, incorrect take-off trim, aggressive assistance settings and misunderstood autopilot modes can produce similar symptoms. Our guide to baseline 737 handling, trim and automation in a flight simulator covers those fundamentals. Even a sophisticated desktop simulation is not an approved source for real-aircraft procedures or proof that certified MCAS logic behaves in a particular way.