Space Mission Failures
Mars Climate Orbiter
The nine-month mission destroyed because two software interfaces disagreed about units.
The knowledge that remained
Knowledge that outlived the failure.
- 01
Interfaces fail when assumptions are implicit, even if each team performs its own task correctly.
- 02
Units are part of the data contract and should be machine-verifiable.
- 03
Small mismatches can accumulate invisibly until recovery is impossible.
The loss remains one of engineering’s most memorable examples of interface failure: both teams could do their jobs correctly and still lose the system if their units did not match.
Timeline
The sequence of failure.
- 01Conditions9 MONTHS
The spacecraft travels
Mars Climate Orbiter crosses interplanetary space toward the red planet.
- 02DecisionGROUND OPERATIONS
Units diverge
Thruster data is produced in English units while navigation expects metric.
- 03FailureSEP 1999
The trajectory falls low
The accumulating mismatch pushes the spacecraft closer to Mars than planned.
- 04DecisionFINAL CONTACT
The mission disappears
The orbiter passes behind Mars and never communicates with Earth again.
The event.
Mars Climate Orbiter traveled for nine months toward the red planet. The mission depended on ground teams and navigation software sharing precise data.
A unit-conversion mismatch destroyed an entire interplanetary mission after nine months of travel.
The mechanism.
English-unit thruster data was interpreted as metric by navigation software.
Ground software reported thruster information in English units while navigation calculations expected metric units. The mismatch altered the predicted trajectory.
Sources & references
Trace the evidence.
Media rights record: The episode uses NASA/JPL-Caltech mission imagery recorded as public domain.
Discovery edition
The case in under one minute.
The Short introduces the failure. This archive record preserves the mechanism, evidence, and engineering lesson beyond the video.
Short ready for releaseEditorial derivatives
Editions from this case.
A portable, source-backed edition of the complete case.
The failure sequence formatted for print and classroom display.
Mechanism, consequence, and lesson in one visual system.
Discussion prompts, activities, and a structured answer guide.
The question to remember
Was this merely a small math mistake?
No. It was an interface and verification failure: each side used valid numbers, but the system never enforced a shared unit contract.
