Boeing 737 MAX: Boeing 737 MAX: How MCAS, Certification and Organisational Failures Contributed to Two Fatal Crashes

Ramesh Dixit

Investigation PIA-INV-001Billion Dollar FailuresCost: $20B+6 min read

Boeing 737 MAX

Boeing 737 MAX: How MCAS, Certification and Organisational Failures Contributed to Two Fatal Crashes

Filed under: The Business Behind Megaprojects · Project Failures · Boeing · United States · Aerospace & Space

Written and edited by Ramesh Dixit·Published 2026-06-01·Last updated 2026-06-01·Last fact-checked 2 August 2026·Editorial Standards · Editorial Policy · Corrections Policy · Methodology · Source Standards · AI Disclosure

Download Executive Brief (PDF)

In October 2018 and March 2019, two Boeing 737 MAX aircraft crashed, killing 346 people. MCAS was a central factor in both crashes. Accident investigations identified MCAS design, erroneous angle-of-attack inputs, certification assumptions, training and other contributing factors. This investigation reveals how commercial pressure overrode engineering integrity and what project leaders must learn.

Boeing 737 MAX — investigative documentary thumbnail

Watch the Documentary

Watch: Boeing 737 MAX

Boeing 737 MAX — Project Insider Asia documentary video thumbnail

Prefer the episode page? Watch this investigation as a documentary episode →

Key Facts

Cost

$20B+

Date

2026-06-01

Duration

10:59

What Happened

On 29 October 2018, Lion Air Flight 610 plunged into the Java Sea 13 minutes after take-off, killing all 189 people on board. Less than five months later, on 10 March 2019, Ethiopian Airlines Flight 302 crashed six minutes after departure from Addis Ababa, killing 157 more. Both aircraft were brand-new Boeing 737 MAX 8s. Both went into the same fatal dive. The connecting factor was MCAS — the Maneuvering Characteristics Augmentation System. Boeing had installed it to compensate for the MAX's larger engines, which shifted the aircraft's centre of gravity. But MCAS relied on a single angle-of-attack sensor. When that sensor fed wrong data, MCAS repeatedly pushed the nose down into an unrecoverable dive. The most chilling part: pilots were not told about MCAS before the first crash — the system did not appear in the flight crew operations manual, according to the House Transportation Committee investigation. Congressional investigators found that Boeing sought to minimise additional pilot-training requirements and that MCAS was omitted from flight-crew manuals before the first crash. The FAA delegated certification oversight to Boeing employees. And the board of directors never asked the hard questions.

Why It Matters

The Boeing 737 MAX case redefined how regulators worldwide approach software safety in safety-critical systems. The FAA's delegation of oversight to Boeing employees — The delegation arrangement created oversight weaknesses identified by subsequent reviews. — created a structural blind spot that no individual competence could overcome. EASA subsequently demanded its own flight testing precisely because trust in the OEM-regulator relationship had been fundamentally broken. Programme directors in transport, healthcare, and energy should apply the same scepticism to any vendor claiming their proprietary system needs no external validation. The Project Failure Pyramid™ traces how a $1M pilot retraining decision cascaded into more than $20B in direct costs.

Timeline

proposal 2011-08
Boeing launches the 737 MAX programme as a re-engined derivative of the 737NG to compete with the Airbus A320neo.
design 2016-03
Boeing expands MCAS authority during flight testing so it can command larger, repeated stabilizer movements at low speed; the change is not fully briefed to FAA technical staff.
approval 2017-03
FAA grants the amended type certificate for the 737 MAX 8; MCAS is omitted from flight crew manuals and differences training.
opening 2017-05
The 737 MAX enters commercial passenger service with Malindo Air.
failure 2018-10-29
Lion Air flight JT610 crashes into the Java Sea 13 minutes after takeoff from Jakarta, killing all 189 people on board; erroneous AOA data triggers repeated MCAS nose-down trim.
warning 2018-11
FAA issues Emergency Airworthiness Directive 2018-23-51 and Boeing issues an operations manual bulletin warning of uncommanded stabilizer trim from erroneous AOA input.
failure 2019-03-10
Ethiopian Airlines flight ET302 crashes six minutes after takeoff from Addis Ababa, killing all 157 people on board, again after MCAS activation from erroneous AOA data.
delay 2019-03-13
FAA issues an Emergency Order of Prohibition grounding the 737 MAX; the worldwide fleet remains grounded for roughly 20 months.
inquiry 2019-09
NTSB issues safety recommendation report ASR-19-01 criticizing the assumptions about pilot response used in the 737 MAX system safety assessment.
inquiry 2019-10
JATR publishes findings on the flawed certification of the 737 MAX flight control system; KNKT publishes its final JT610 report citing MCAS design, certification, maintenance and crew factors.
delay 2020-01
Boeing discloses that the 737 MAX crisis is expected to cost about $18.6 billion (compensation, production and abnormal costs), later commonly cited as $18.7 billion and counting.
inquiry 2020-09
U.S. House Transportation & Infrastructure Committee publishes its final investigative report documenting technical design failures, lack of transparency, and FAA oversight breakdowns.
opening 2020-11
FAA rescinds the grounding order and issues an airworthiness directive allowing the 737 MAX to return to service with mandated design changes and training.
settlement 2021-01
Boeing enters a deferred prosecution agreement with the U.S. Department of Justice over the 737 MAX fraud conspiracy, agreeing to pay more than $2.5 billion.

Root Cause Analysis

Root cause through the Project Failure Pyramid™ lens

Symptoms

The visible indicators: delays, cost overruns, quality defects, team attrition

Management Failure

Operational breakdowns: poor risk management, scope creep, inadequate resources

Governance Failure

The House Transportation Committee documented significant competitive and production pressures during the MAX programme. to compete with the Airbus A320neo, and Boeing employees raised safety concerns about the programme; the House committee found that production pressure took precedence, according to congressional investigators. A delayed project is expensive; a compromised project is fatal. When competitive pressure overrides your quality gates, you are not accelerating — you are accumulating catastrophic risk.

Root Cause

Foundational decisions: overconfidence, pressure to commit, culture that suppresses bad news

Frameworks Applied

Framework Applied

Project Failure Pyramid™

The 4-Level Diagnostic for Cascading Failures — explore the framework →

Framework Applied

Leadership Blind Spot Matrix™

Identifying What Leaders Cannot See — explore the framework →

Executive Lessons

Lessons for Leaders

Never Hide Hardware Problems with Software Patches

Boeing introduced MCAS as part of the MAX flight-control architecture following aerodynamic changes associated with the aircraft's configuration. with the MCAS software system. When physics and software collide, physics always wins. If your project has a fundamental design flaw, address it at the source — never build a workaround that end-users do not know exists.

Competitor Panic Destroys Project Governance

The House Transportation Committee documented significant competitive and production pressures during the MAX programme. to compete with the Airbus A320neo, and Boeing employees raised safety concerns about the programme; the House committee found that production pressure took precedence, according to congressional investigators. A delayed project is expensive; a compromised project is fatal. When competitive pressure overrides your quality gates, you are not accelerating — you are accumulating catastrophic risk.

Compliance Teams Must Have Veto Power

Boeing employees raised safety concerns about the MAX programme, and the House committee found that production pressure took precedence, according to congressional investigators. When the compliance function reports to the people it is supposed to police, you do not have oversight — you have theatre.

Continue Investigating

Corporate Disasters$6.2B

JPMorgan CIO Trading Loss

4 min read

Billion Dollar Failures$560M delay costs (system ~$200M)

Denver Airport Baggage System

4 min read

The Weekly Brief — one investigation, one executive lesson and one project warning sign each week.

Subscribe free

Executive Recommendations

Never mask a fundamental hardware design flaw with a hidden software workaround that end-users do not know exists.

Give compliance and safety functions independent veto power over launch and certification decisions.

Prohibit regulator-oversight structures where the regulated entity certifies its own safety-critical changes.

Treat competitive pressure as a risk register item, not a reason to compress quality gates.

Mandate disclosure of any flight-critical system to operators and crews before entry into service.

PMOS Intelligence

Preview — illustrative assessment; PMOS is in development

Governance WeaknessFAA certification oversight was delegated to the very Boeing employees being overseen, and Boeing's board never interrogated MCAS design assumptions, leaving safety-critical decisions structurally unreviewed.

Escalation FailureInternal Boeing employees raised safety concerns about the MAX programme, but the House committee found production pressure took precedence, so the concerns never reached a decision-making forum with authority to act.

Decision DelayMCAS authority was expanded in flight testing in 2016 and pilots were never told, yet no forum revisited the certification basis before entry into service in 2017.

Leadership Blind SpotLeadership treated a hardware flaw (engine placement shifting the centre of gravity) as a software problem to be hidden, prioritising a ~$1M-per-aircraft pilot-training rebate commitment over engineering integrity.

Risk VisibilityMCAS depended on a single angle-of-attack sensor and did not appear in flight crew manuals, so the catastrophic single-point failure mode was invisible to pilots, regulators and, apparently, the board.

Evidence QualityWarning indicators existed but did not result in timely corrective action.: Boeing test pilots' messages about MCAS behaviour and the 2016 expansion of MCAS authority were not fully briefed to FAA technical staff, as the DOJ deferred prosecution agreement later established.

Assurance MaturityAssurance was captured, not independent: delegated certification, sales-driven schedule and a compliance function without veto power meant quality gates were theatre.

Suggested InterventionAn independent PMO with safety-veto authority would have forced MCAS into flight crew manuals and differences training at the 2016 design change, and halted certification in 2017 until the single-AOA-sensor dependency was engineered out or trained for.

“Executives often believe they can shortcut the planning process to beat the competition without consequences. Boeing assumed they could mask a physical hardware reality with a hidden software system just to avoid pilot training costs — Boeing had agreed a rebate of about $1 million per aircraft to Southwest Airlines if simulator training became mandatory. But physics and human operators do not care about your stock price. When you prioritise your sales timeline over your engineering integrity, you are not saving time — you are just delaying a catastrophe that will cost you more than $20 billion in direct costs, roughly $55 billion in market capitalisation at the crisis's depth, and 346 innocent lives.”Ramesh's Insider Take — opinion

Evidence

Documentary Evidence

official-accident-investigation-report

Aircraft Accident Investigation Report KNKT.18.10.35.04 (Lion Air JT610 final report)

KNKT (hosted by U.S. House Committee Repository) · 2019-10-25

Establishes that MCAS relied on a single AOA sensor, that Boeing's pilot-response assumptions during design and certification were flawed, and that the absence of MCAS from manuals and training contributed to the crash.

View document →

official-accident-investigation-report

Investigation Report on Accident to the B737-MAX8 Reg. ET-AVJ, Report No. AI-01/19 (Ethiopian Airlines ET302 final report)

Ethiopian Aircraft Accident Investigation Bureau (hosted by French BEA) · 2022-12-23

Establishes repetitive uncommanded nose-down MCAS inputs from erroneous AOA data as the probable cause of the ET302 crash; NTSB and BEA publicly contested the report's exclusion of crew factors.

View document →

congressional-investigation-report

Final Committee Report: The Design, Development & Certification of the Boeing 737 MAX

U.S. House Committee on Transportation & Infrastructure · 2020-09

After an 18-month investigation, documents Boeing's production pressures, concealment of MCAS information from pilots and regulators, and FAA delegation and oversight failures that permitted two preventable crashes.

View document →

regulator-order

FAA Emergency Order of Prohibition, 13 March 2019

U.S. Federal Aviation Administration · 2019-03-13

Primary legal instrument grounding the 737 MAX fleet, recording the wreckage and satellite data that linked ET302 and JT610 and the safety rationale for the 20-month grounding.

View document →

deferred-prosecution-agreement

Deferred Prosecution Agreement, United States v. The Boeing Company

U.S. Department of Justice · 2021-01-07

Establishes that Boeing, through two 737 MAX technical pilots, conspired to defraud the FAA's Aircraft Evaluation Group about MCAS, and quantifies the >$2.5 billion resolution including a criminal penalty and airline-customer compensation.

View document →

Asset Hub