Loading...
On October 29, 2018 at 6:20 AM, Lion Air Flight 610 — a two-month-old Boeing 737 MAX 8, tail PK-LQP — took off from Jakarta. Ten seconds later, the aircraft's two angle-of-attack sensors disagreed by 20 degrees, and a software system the pilots had never been told about began pushing the nose down 2.5 degrees at a time, every 10 seconds. The Maneuvering Characteristics Augmentation System (MCAS) had been added to the MAX to compensate for a pitch-up tendency caused by the larger CFM LEAP-1B engines, mounted further forward on the same fuselage Boeing had used since the 1990s. MCAS was designed around a single AoA sensor reading. There was no cross-check, no mention in the pilot manuals, and no simulator training — because requiring sim training would have triggered a $1 million-per-airc...
Popular framing: Foreign pilots could not handle a system American pilots would have managed. The crashes were tragic but recoverable with proper training.
Structural analysis: A cost constraint in the Boeing-Southwest launch contract — $1M per plane requiring sim training — made hiding MCAS the path of least resistance. The FAA delegated MCAS oversight to Boeing's self-certification arm. After Lion Air, MCAS was still not named in manuals. Two crews on two continents, separated by 132 days, with no contact between them, produced the same dive-cycle signature because they faced the same hidden bug triggered by the same single sensor.
The individual-blame framing locates the failure in cockpits thousands of miles from where it was produced. The structural framing identifies the specific decision points — contract clause, ODA delegation, OMB content — where the system was set up to produce both crashes. Replace every pilot, every engineer; the system produces the same outcome.
