Boeing 737 MAX / MCAS
About this resource · How to use it · Learning engineering connections
What is this resource?
A documented case about Boeing 737 MAX / MCAS. 346 killed in the Lion Air 610 and Ethiopian Airlines 302 crashes. The FAA grounded the fleet for twenty months and required changes to flight controls and pilot preparation.
How should I use it?
- Read the narrative and five beats, keeping the disclosures and scope limits in view.
- Compare the LE insight with the LENS approach. Identify the system condition that changed what people could do, then check the cited evidence before applying the lesson elsewhere.
How does this connect to LENS and learning engineering?
Certification depended on crews recognizing the problem and responding within seconds despite concurrent warnings and repeated trim commands. That capability needs evidence from representative crews operating the whole system under realistic conditions. The historical response combined sensor cross-checks, reduced MCAS authority, revised procedures and simulator practice. A LENS exercise would compare flight-control and preparation designs under simultaneous failure cues. Assess diagnosis, coordinated action and recovery margin, then use those results to review certification assumptions and readiness.
Impact. 346 killed in the Lion Air 610 and Ethiopian Airlines 302 crashes. The FAA grounded the fleet for twenty months and required changes to flight controls and pilot preparation.
Potential learning engineering response. The record identifies a capability gap that learning engineering could directly address. The proposed response still needs testing.
Consider the human, the science and the system
- Human
- Who gained or lost agency, opportunity or well-being? Whose experience is missing from the record?
- Science
- What evidence supports the proposed learning explanation, and what other causes could explain the outcome?
- System
- Which tools, responsibilities, interfaces or conditions enabled the result or prevented recovery?
The 737 MAX depended on crews recognizing and responding to uncommanded trim under pressure. Boeing treated avoiding simulator differences training as a design objective, and original manuals and training did not explain MCAS. In both accidents an erroneous angle-of-attack signal could trigger repeated nose-down trim. Indonesia’s investigators identified nine factors in the Lion Air crash. Ethiopia’s investigators, the NTSB and France’s BEA agreed on MCAS’s contribution to Ethiopian 302, but the NTSB disputed the electrical explanation for the sensor fault and both outside agencies called for fuller treatment of crew performance.
The FAA’s response changed what the aircraft would do as well as what crews were told and trained to do. A realistic simulator assessment can test the combined response, including whether crews can diagnose and act amid multiple alerts within the available time. The investigations cannot establish the effect simulator training alone would have had on either flight.
In brief
A single erroneous angle-of-attack input could cause the 737 MAX’s Maneuvering Characteristics Augmentation System (MCAS) to command repeated nose-down trim. Boeing sought to avoid simulator differences training, and original training and manuals did not explain MCAS. Indonesia’s KNKT identified nine contributing factors in Lion Air 610, including design assumptions, maintenance and crew workload. Ethiopia’s EAIB, the U.S. NTSB and France’s BEA agreed that MCAS contributed to Ethiopian 302 but differed on aspects of the sensor failure and the treatment of crew actions. FAA return to service required flight-control changes, revised procedures and simulator training.
The case in five beats
- Boeing sought a common type rating without simulator differences training
- Erroneous sensor input triggered repeated nose-down commands in two fatal crashes
- Investigators agreed on MCAS but differed on trigger and crew response in ET302
- Certification assumed timely crew diagnosis amid concurrent alerts and trim commands
- FAA return to service combined flight-control changes, procedures and simulator training
LE insight
Certification depended on crews recognizing the problem and responding within seconds despite concurrent warnings and repeated trim commands. That capability needs evidence from representative crews operating the whole system under realistic conditions.
LENS approach
The historical response combined sensor cross-checks, reduced MCAS authority, revised procedures and simulator practice. A LENS exercise would compare flight-control and preparation designs under simultaneous failure cues. Assess diagnosis, coordinated action and recovery margin, then use those results to review certification assumptions and readiness.
- 1 Systems Analysis
- 2 Iterative Development
- 3 Human-System Collaboration
- 4 Test & Evaluation
- 5 Sociotechnical Constraints
Problem type · PT4
- Problem type
- D1+D5/PT4
- Induced
- 1.1
- LEO
- 1, 5
Competing readings
Compare what the sources agree on, where their findings differ, and how each interpretation would change what you test or design.
- The EAIB attributed the erroneous angle-of-attack signal in Ethiopian 302 to an electrical failure. The NTSB judged a foreign-object impact, likely a bird, to be the most likely cause.
- The NTSB and BEA agreed on MCAS’s contribution and called for fuller analysis of crew actions and preparation, including the period before MCAS activated.
What this case does not show
The accident investigations do not isolate how either crew would have performed with different training, alerts, or flight controls.