A units mismatch lost a Mars orbiter
Did you know a units mismatch made NASA lose a Mars orbiter?
· 27-sec read
In September 1999, the Mars Climate Orbiter went silent during orbit insertion and was never heard from again. One program's output files gave small thruster impulses in pound-force seconds instead of the specified newton-seconds, so navigation underestimated their effect by a factor of at least 4, adding up to a 169 km navigation error. NASA's lessons-learned record also blames process: the program was misclassified as non-mission-critical, and its interface with the navigation software was never tested.
Popular version vs. what really happened
Popular version
Popular version: 'someone forgot to convert units.'
What really happened
NASA's finding: process failures (misclassified software, an untested interface, no units in the requirements) let the bug through.
Why it matters
Put units in your types and your interface specs, and test the seams between teams.
Sources
High confidenceChecked October 20, 2026.