American Airlines nationwide flight-planning system grounding
American Airlines grounded its entire fleet nationwide for about three hours, delaying hundreds of flights, after a failure in its flight-dispatch computer system.
The damage was public. The root cause was preventable.
American Airlines grounded its entire fleet nationwide for about three hours, delaying hundreds of flights, after a failure in its flight-dispatch computer system.
What the software actually got wrong
A glitch in the airline's flight-planning software prevented dispatchers from reliably calculating and transmitting flight plans to aircraft, and American opted to hold all flights on the ground rather than dispatch them without confidence in the data.
A glitch in the airline's flight-planning software prevented dispatchers...
A glitch in the airline's flight-planning software prevented dispatchers from reliably calculating and transmitting flight plans to aircraft
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.
American opted to hold all flights on the ground...
American opted to hold all flights on the ground rather than dispatch them without confidence in the data
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
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.
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.
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.