Delta Air Lines' prolonged CrowdStrike-outage recovery
While most airlines recovered from the global CrowdStrike outage within a day, Delta continued cancelling thousands of flights for nearly a week, the worst and longest recovery of any major carrier, drawing a DOT investigation and lawsuits.
The damage was public. The root cause was preventable.
While most airlines recovered from the global CrowdStrike outage within a day, Delta continued cancelling thousands of flights for nearly a week, the worst and longest recovery of any major carrier, drawing a DOT investigation and lawsuits.
What the software actually got wrong
Delta's crew-tracking and scheduling software could not efficiently re-match tens of thousands of displaced crew members to aircraft once the underlying Windows-based systems came back online, a software recovery limitation that other airlines with more modern crew-scheduling tools did not share.
Delta's crew-tracking and scheduling software could not efficiently re-match...
Delta's crew-tracking and scheduling software could not efficiently re-match tens of thousands of displaced crew members to aircraft once the underlying Windows-based systems came back online, a software recovery limitation that other airlines with more modern crew-scheduling tools did not share.
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.
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.