← Back to the 300 Software Failures Timeline
Case Study #226 — 300 Software Failure Case Studies

USS Stark Exocet missile strike

An Iraqi fighter jet fired two Exocet missiles that struck the USS Stark in the Persian Gulf, killing 37 sailors.

1987-05-17
When it happened
Military / Defense
Sector
#226 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

An Iraqi fighter jet fired two Exocet missiles that struck the USS Stark in the Persian Gulf, killing 37 sailors.

Military
Sector affected
1987-05-17
Date of the event
#226
Rank in the 300 Software Failure Case Studies
2
Distinct root-cause clauses identified below
02 — The Root Cause

What the software actually got wrong

The ship's electronic warfare system, designed to detect and warn of exactly this kind of missile radar signature, was not being actively monitored in a configuration that would have alerted the crew in time, and the ship's defensive systems were not brought to bear before the missiles struck.

01Root Cause

The ship's electronic warfare system, designed to detect and...

What Happened

The ship's electronic warfare system, designed to detect and warn of exactly this kind of missile radar signature, was not being actively monitored in a configuration that would have alerted the crew in time

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 ship's defensive systems were not brought to bear...

What Happened

the ship's defensive systems were not brought to bear before the missiles struck

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.