top of page

Aviation Case Study: When Automation Outran Human Adaptation — Lion Air Flight 610

Aug 11
2 min read

On October 29th, 2018, Lion Air Flight 610, a Boeing 737 MAX 8, took off from Jakarta bound for Pangkal Pinang.Twelve minutes later, it disappeared into the Java Sea.All 189 people on board were lost.

The cause wasn’t weather, nor pilot inattention.It was automation — doing exactly what it was programmed to do, in the wrong conditions.

A faulty Angle of Attack (AoA) sensor sent incorrect data to the aircraft’s Maneuvering Characteristics Augmentation System (MCAS) — a new, little-known software designed to automatically push the nose down to prevent stalls.But this time, the system kept firing, forcing the nose lower with every cycle until control was lost.

The pilots were fighting both the airplane and their own instruments — under crushing time pressure, with alarms blaring and no clear understanding of why the jet was behaving as it did.

What the Investigation Found

The KNKT investigation revealed that the MCAS design relied on a single AoA sensor, a single point of failure with catastrophic potential.

Boeing had not disclosed MCAS in the flight manual or pilot training syllabus.This omission meant the crew had no mental model of the system’s behavior — no way to anticipate the trim inputs or diagnose the runaway stabilizer condition in time.

Inside the cockpit, both pilots were overwhelmed by a flood of conflicting warnings: stick shaker, speed disagree, altitude disagree.The result was cognitive overload — the point where even highly skilled professionals cannot process the volume of failure cues confronting them.

ICAM Lens: How the System Failed

Absent / Failed Defences:MCAS was built without redundancy. It depended on one AoA sensor and had no cross-check against the second. When that single sensor failed, every layer of automation failed with it.

Individual / Team Actions:The crew followed the logic they were trained to trust: that automation would protect them. Under extreme workload and without awareness of MCAS, they could not complete the memory items that would have cut power to the runaway trim.

Task / Environmental Conditions:Multiple, simultaneous warnings combined with uncommanded control movements created an impossible human task— a scenario beyond normal training or recovery expectations.

Organisational Factors:Boeing’s certification and training strategy minimized the visibility of MCAS to avoid costly simulator retraining. The FAA’s oversight process failed to challenge that decision.The result was an industry-wide blind spot — a design culture that assumed the pilot would be the last line of defence for software risks they didn’t even know existed.

The Leadership Lesson

True resilience isn’t built by adding technology — it’s built by designing systems that fail safely when humans are under stress.

The Lion Air tragedy exposed a dangerous assumption: that human operators can always adapt faster than automation can fail.In reality, no one — not even the best-trained pilot — can outthink a system that hides its intentions.

Leadership in complex organizations means asking the same hard question Boeing should have asked:

“Where in our system have we introduced automation or process complexity that no one fully understands — and how will we detect and recover when it goes wrong?”

Question for Leaders:In your operation, what system still assumes the human will be the fail-safe?

Comments


bottom of page