Schedule a Software Walkthrough Free Trial
← Back to Software Failure Events Timeline
Case Study #03 — 329 Software Failure Events Timeline

Mars Climate Orbiter loss

$327.6 million spacecraft was lost, likely disintegrating in the Martian atmosphere.

1999-09-23
When it happened
Aerospace / Space
Sector
#3
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

$327.6 million spacecraft was lost, likely disintegrating in the Martian atmosphere.

Aerospace
Sector affected
1999-09-23
Date of the event
#3
Rank in the 329 Software Failure Events Timeline
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

The spacecraft navigation software output thruster data in imperial units (pound-seconds) while NASA's ground software assumed metric units (newton-seconds), sending the craft too close to Mars.

01Root Cause

The spacecraft navigation software output thruster data in imperial...

What Happened

The spacecraft navigation software output thruster data in imperial units (pound-seconds) while NASA's ground software assumed metric units (newton-seconds), sending the craft too close to Mars.

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.

See real failures this would have caught

Failures like this one can be found before release. See how Requs AI finds them early: