American Airlines Christmas Eve ground stop
American Airlines requested and received a nationwide FAA ground stop for all its mainline and regional flights for about an hour on one of the year's busiest travel days, producing over 600 delayed flights.
The damage was public. The root cause was preventable.
American Airlines requested and received a nationwide FAA ground stop for all its mainline and regional flights for about an hour on one of the year's busiest travel days, producing over 600 delayed flights.
What the software actually got wrong
American attributed the outage to a 'vendor technology issue' that disabled the systems needed to formally release flights for departure; the airline did not publicly identify the specific vendor or software system involved, but confirmed the fault originated outside American's own infrastructure.
American attributed the outage to a 'vendor technology issue'...
American attributed the outage to a 'vendor technology issue' that disabled the systems needed to formally release flights for departure
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.
The airline did not publicly identify the specific vendor...
the airline did not publicly identify the specific vendor or software system involved, but confirmed the fault originated outside American's own infrastructure
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.