Boeing 737 MAX Failure: How MCAS, Certification and Organisational Failures Contributed to Two Fatal Crashes
The Full Story of Lion Air Flight 610, Ethiopian Airlines Flight 302, and the Corporate Culture That Prioritised Profits Over Lives
This article is part of investigation PIA-INV-001: Boeing 737 MAX.
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.
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.
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.
“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
