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

2003 Iraq war Patriot missile fratricide incidents

US Patriot missile batteries shot down a British Tornado and a US Navy F/A-18 during the early days of the 2003 Iraq invasion, misidentifying them as enemy missiles and killing all three aircrew.

2003-03
When it happened
Military / Defense
Sector
#193 of 309
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

US Patriot missile batteries shot down a British Tornado and a US Navy F/A-18 during the early days of the 2003 Iraq invasion, misidentifying them as enemy missiles and killing all three aircrew.

Military
Sector affected
2003-03
Date of the event
#193
Rank in the 309 Software Failure Events Timeline
2
Distinct root-cause clauses identified below
02 — The Root Cause

What the software actually got wrong

A GAO review found that the Patriot system's software for automatically classifying and identifying radar tracks had unresolved deficiencies in distinguishing friendly aircraft from threats, especially in the unfamiliar operating environment, and the system's high degree of automation left operators little time to override incorrect classifications.

01Root Cause

A GAO review found that the Patriot system's software...

What Happened

A GAO review found that the Patriot system's software for automatically classifying and identifying radar tracks had unresolved deficiencies in distinguishing friendly aircraft from threats, especially in the unfamiliar operating environment

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.

02Root Cause

The system's high degree of automation left operators little...

What Happened

the system's high degree of automation left operators little time to override incorrect classifications

How Requs AI Catches This

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.

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.