← Back to the 309 Software Failures Timeline
Case Study #121 — 309 Software Failure Events Timeline

US Airways-America West reservation system merger crash

US Airways' newly merged computer reservation system crashed for hours, stranding thousands of passengers, causing long lines and check-in failures nationwide right after the two airlines' systems were combined.

2007-09-14
When it happened
Aviation
Sector
#121 of 309
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

US Airways' newly merged computer reservation system crashed for hours, stranding thousands of passengers, causing long lines and check-in failures nationwide right after the two airlines' systems were combined.

Aviation
Sector affected
2007-09-14
Date of the event
#121
Rank in the 309 Software Failure Events Timeline
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

The rushed migration to a single shared reservation platform following the US Airways-America West merger overwhelmed the new combined system's capacity and had not been adequately load-tested for the cutover weekend.

01Root Cause

The rushed migration to a single shared reservation platform...

What Happened

The rushed migration to a single shared reservation platform following the US Airways-America West merger overwhelmed the new combined system's capacity and had not been adequately load-tested for the cutover weekend.

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.