Two crashes, 346 lives, and one question that outlasted every investigation: who was supposed to say no?
Easier version: read this lesson at A2/B1 level →
Ten items. Work through the four activities — say your answer out loud before you reveal it.
Three terms: a deferred prosecution agreement · to ground a fleet · a fix. Say the right one, then reveal.
Read each part. After it, there's a quick check (answer from memory first), then one question to discuss. The facts here follow the official investigations; 346 people died in the two crashes, and this lesson treats that as the constant weight behind every business detail.
In 2011 Boeing faced a competitive ambush. Airbus had fitted new, dramatically more efficient engines to its A320 and was taking orders at a pace that threatened Boeing's hold on the single-aisle market — including, decisively, a possible defection of American Airlines. Boeing had been debating an all-new aircraft, a decade-long project; instead, in a decision reached within weeks, it announced the 737 MAX: a fourth-generation derivative of a design first certified in 1967, with the new engines grafted on. A derivative could be certified faster, built on existing lines — and, crucially, sold to airlines with the promise that existing 737 pilots would need only minimal conversion training. That promise had a contractual edge: one major customer's deal reportedly included compensation per aircraft if simulator training turned out to be required.
The old airframe, however, sat low to the ground, and the new engines were too large to hang where the old ones had been. Moved forward and up, they changed the aircraft's aerodynamics: in certain conditions the nose tended to pitch up more than the previous model's. Rather than alter the airframe — or accept handling differences that might trigger training requirements — engineers added software: MCAS, a system that would automatically push the nose down when a sensor indicated the angle of attack was too high. In its final form, the system could act repeatedly, with substantial authority over the controls, on the reading of a single angle-of-attack sensor — and, consistent with the strategy of sameness, it was left out of the pilot manuals and the training. Most pilots flying the MAX did not know it existed.
Certification proceeded under the delegation system, in which the regulator authorises manufacturer employees to perform much of the detailed safety assessment on its behalf. Later investigations found that the FAA's own review never fully caught up with what MCAS had become as it evolved during development — the safety analysis on file described an earlier, weaker version of the system than the one that flew.
1. What commercial constraints shaped the MAX's design, and what did MCAS exist to do?
2. What two facts about MCAS's final form matter most?
1. Speed against Airbus, a derivative rather than a new design, and above all the promise of minimal pilot retraining — with contractual penalties if simulator training were required. MCAS existed to make the re-engined aircraft handle like the old one, in software.
2. It acted on a single sensor with repeated, substantial authority over the controls; and pilots were not told it existed. The certification file described a weaker version than the one that flew.
On 29 October 2018, Lion Air flight 610 took off from Jakarta with a faulty angle-of-attack sensor feeding MCAS. The system repeatedly commanded the nose down; the crew, fighting a system they had never been told about, lost the struggle thirteen minutes after take-off. All 189 people aboard died. Only in the aftermath did Boeing issue a bulletin effectively informing the world's MAX pilots of MCAS's existence, while emphasising that established emergency procedures for runaway trim were sufficient. The aircraft kept flying; a software revision was promised in due course. Within the company, documents later showed, the programme's own test pilots had exchanged messages during development describing the simulator behaviour of MCAS in alarming terms — messages the company would eventually have to hand to prosecutors.
On 10 March 2019, Ethiopian Airlines flight 302 left Addis Ababa. A sensor failed in the same way; MCAS activated in the same way; the crew followed elements of the published procedure and were nonetheless overwhelmed within six minutes. All 157 people aboard died. Two essentially identical accidents, five months apart, on a brand-new aircraft type. Regulators across the world — China first, the FAA last, days later and under visible pressure — grounded the MAX. It stayed grounded for twenty months.
What the investigations then established changed the story from tragedy to case study. Congressional investigators described a culture of concealment and cost pressure; released internal messages showed employees boasting of using "Jedi mind tricks" on regulators and one describing the aircraft, in a phrase that has entered the language of engineering ethics, as designed by clowns, who in turn are supervised by monkeys. The chief executive, Dennis Muilenburg, initially framed the accidents partly around foreign pilot performance — a framing the evidence dismantled — and was dismissed in December 2019. In January 2021 Boeing entered a deferred prosecution agreement with the US Department of Justice over deception of the FAA's training-evaluation group, paying some 2.5 billion dollars, the bulk of it to airline customers.
1. What happened between the two crashes, and why does that interval matter?
2. What did the investigations establish beyond the technical cause?
1. After Lion Air, Boeing disclosed MCAS's existence, pointed to existing procedures, promised a software revision — and the fleet kept flying. Ethiopian 302 then failed the same way five months later. The interval is the case's moral centre: the second accident occurred inside a known risk.
2. A culture problem, documented in the company's own messages — concealment toward the regulator, contempt for oversight, cost pressure on engineering — plus an initial executive framing that shifted focus to pilots until the evidence removed it. The DPA followed in 2021.
The deeper post-mortems reached past the MAX to a merger. In 1997 Boeing — historically an engineers' company, run by people who had built aircraft — absorbed McDonnell Douglas, and, in the telling of many insiders and analysts, the acquired company's finance-driven culture won the internal war. Headquarters moved away from the factories; shareholder returns became the scoreboard; outsourcing fragmented engineering knowledge; and the authority of the technical voice — the person entitled to say "not yet" to a schedule — eroded over two decades. On this reading the MAX was not an aberration but an arrival: the moment a long cultural drift finally intersected with physics.
The MAX returned to service from late 2020 with MCAS rebuilt — dual-sensor inputs, limited authority, full documentation and simulator training, the requirement whose avoidance had shaped the original design. Boeing's leadership declared the lessons learned. Then, in January 2024, a door plug blew out of a nearly new 737 MAX 9 in flight; by good fortune, no one was seriously hurt. Investigators found the panel had left the factory without its retaining bolts installed. The failure was different in kind — assembly quality, not design — but it detonated the credibility of the recovery narrative: prosecutors moved to declare the 2021 DPA breached, the chief executive announced his departure, production was capped by the regulator, and in 2024 a new CEO, Kelly Ortberg, was brought in from outside with a mandate summarised in his own early messaging: move leadership back to the factory floor, and restore the engineering voice.
The case stays open — legally, commercially and culturally — and it closes this series' arc for a reason. Nokia showed truth failing to rise; VW showed impossible targets manufacturing deception; Boeing shows what those same mechanisms cost when the product carries passengers. The question it leaves is not rhetorical, and every organisation has a version of it: when your schedule and your engineers disagree, who is required — not encouraged, required — to win?
1. What is the merger argument, and what does it claim the MAX represents?
2. What happened in January 2024, and why did it matter beyond the incident itself?
1. That the 1997 McDonnell Douglas merger shifted Boeing from an engineering culture to a finance-led one — headquarters away from factories, shareholder returns as scoreboard, technical authority eroded — making the MAX an arrival, not an accident.
2. A door plug left the factory without bolts and blew out in flight. Nobody died, but the recovery narrative did: DPA declared breached, CEO out, production capped, and an outsider brought in to restore the engineering voice.
Investigations, regulations and post-mortems run on the exact strength of duty words. "Should have" and "was required to" describe different failures with different consequences — and this case turned, repeatedly, on which one applied.
Complete each sentence with the form in brackets.
1. Under certification rules, the company (binding duty, past) to keep the safety analysis current as MCAS changed.
2. The delegated engineers (expected arrangement, past) to act as the regulator's eyes inside the company.
3. In my judgement — and this is judgement, not rule — the fleet (speaker's verdict, past passive: ground) after the first accident.
1. was required / obliged 2. were supposed 3. should have been grounded
Rewrite each idea using the formula in brackets. Write the full sentence.
1. Every passenger was owed safety by the manufacturer. (owe a duty of care) →
2. Explaining the system to pilots was the manufacturer's burden, no one else's. (the onus) →
3. The regulator answers to the public for the rigour of certification. (be accountable to… for…) →
1. The manufacturer owed a duty of care to every passenger.
2. The onus was on the manufacturer to explain the system to pilots.
3. The regulator is accountable to the public for the rigour of certification.
An investigator's summary. Fill each gap with the precise strength, then read it aloud — slowly, as findings are read.
The manufacturer (binding, past) to ensure the certification file reflected the system as flown; it did not. The delegated engineers (arrangement, past) to escalate the system's growing authority; the record shows no such escalation. Pilots (entitlement: have a right) to know of a system that could command the controls; withholding it (speaker's judgement, negative, passive: permit) by any reading of the duty of care. Training (unnecessary necessity) have been minimised at all: the constraint was commercial. Ultimate responsibility (fall to) the company's leadership, which set the schedule the design served; the regulator, in turn, remains (accountable) to the public for the oversight it delegated.
was required / obliged · were supposed · had a right · should never have been permitted · needn't · falls to / fell to · accountable
Seven duty expressions, each at its exact strength. Read it once more replacing everything with "should have" — feel the findings dissolve into opinion.
Take this scale into the Speak tab — Task B is an accountability hearing, and the verbs will be marked.
A note on the record: this account follows the congressional, NTSB-adjacent and prosecutorial findings as publicly reported; figures are rounded; legal proceedings continued for years and aspects remain unresolved. 346 people died — their families' advocacy materially shaped the investigations, and any classroom use of this case owes them its seriousness.
All of it out loud, against the clock. The register today is investigative sobriety: exact duty words, no drama the facts don't supply, and the 346 lives never used as rhetoric.
Present the case to a board whose own flagship programme is under schedule pressure. Structure it: the ambush and the derivative decision → the engines, the software, the training promise → certification under delegation → Jakarta, the five months, Addis Ababa → the grounding and what the documents showed → the merger argument → the door plug and the long repair → the required-not-encouraged question.
Use at least four duty expressions at distinct strengths and five key terms (certify, derivative, oversight, ground, corrective action, DPA, single point of failure, damning, duty of care, cut corners).
You are the company's current chief executive before a legislative committee, years on. A member asks: "Your predecessor said 'safety is our top priority' eleven times in this room while the messages we've now read called your regulator monkeys. Why should a single word your company says about culture be believed — and what is now required, rather than promised?"
Answer in findings register: concede what the record established, refuse nothing that is documented, and answer the question's exact grammar — list what is now required, by whom, enforced how. Then compress it to ninety seconds.
The scene every version of this case demands. You are the senior engineer on a programme; the launch is in six weeks; you have data suggesting a safety-relevant flaw that would take four months to resolve. Round one: make the case to stop, to a leadership team with a contract penalty clock running. Round two: you are the programme director receiving it — respond in a way you could later read aloud to an inquiry.
Prefer a listed scenario? Take one of these: