← Back to the 300 Software Failures Timeline
Case Study #127 — 300 Software Failure Case Studies

Eastern Air Lines Flight 401 crash

A Lockheed L-1011 crashed into the Florida Everglades while the crew was distracted troubleshooting a landing gear indicator light, killing 101 of the 176 people aboard.

1972-12-29
When it happened
Aviation
Sector
#127 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

A Lockheed L-1011 crashed into the Florida Everglades while the crew was distracted troubleshooting a landing gear indicator light, killing 101 of the 176 people aboard.

Aviation
Sector affected
1972-12-29
Date of the event
#127
Rank in the 300 Software Failure Case Studies
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

A slight, inadvertent nudge of the control yoke disengaged only the altitude-hold function of the autopilot, with no distinct warning to alert the crew that the aircraft had begun a slow, unnoticed descent while their attention was elsewhere.

01Root Cause

A slight, inadvertent nudge of the control yoke disengaged...

What Happened

A slight, inadvertent nudge of the control yoke disengaged only the altitude-hold function of the autopilot, with no distinct warning to alert the crew that the aircraft had begun a slow, unnoticed descent while their attention was elsewhere.

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.