← Back to the 100 Software Failures Timeline
Case Study #63 — Top 100 Software Failures

JetBlue Valentine's Day operational meltdown

An ice storm stranded JetBlue passengers on the tarmac for hours and led to more than 1,000 flight cancellations over 6 days; JetBlue introduced its Customer Bill of Rights and paid millions in compensation.

2007-02-14
When it happened
Aviation
Sector
#63 of 100
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

An ice storm stranded JetBlue passengers on the tarmac for hours and led to more than 1,000 flight cancellations over 6 days; JetBlue introduced its Customer Bill of Rights and paid millions in compensation.

Aviation
Sector affected
2007-02-14
Date of the event
#63
Rank in the Top 100 Software Failures
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

JetBlue's crew-scheduling process relied on a small team manually re-booking crews by phone with no robust software system to reassign thousands of crew members quickly, so the airline could not recover once the schedule was disrupted at scale.

01Root Cause

JetBlue's crew-scheduling process relied on a small team manually...

What Happened

JetBlue's crew-scheduling process relied on a small team manually re-booking crews by phone with no robust software system to reassign thousands of crew members quickly, so the airline could not recover once the schedule was disrupted at scale.

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.