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

USS Fitzgerald collision

The destroyer USS Fitzgerald collided with a container ship off Japan, killing 7 sailors and causing extensive damage below the waterline.

2017-06-17
When it happened
Military / Defense
Sector
#129 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

The destroyer USS Fitzgerald collided with a container ship off Japan, killing 7 sailors and causing extensive damage below the waterline.

Military
Sector affected
2017-06-17
Date of the event
#129
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

A Navy investigation found that the ship's radar and navigation display systems presented cluttered, hard-to-interpret information about nearby vessel traffic, and watchstanders did not have an intuitive way to recognize the approaching ship's collision course in time to maneuver clear.

01Root Cause

A Navy investigation found that the ship's radar and...

What Happened

A Navy investigation found that the ship's radar and navigation display systems presented cluttered, hard-to-interpret information about nearby vessel traffic

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

Watchstanders did not have an intuitive way to recognize...

What Happened

watchstanders did not have an intuitive way to recognize the approaching ship's collision course in time to maneuver clear

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.