In 1999, NASA lost the Mars Climate Orbiter after a unit mismatch went undetected. I'm Kendra from The Writing Studio, and this is Paper Trail — where I go back in time to show you exactly what happens when the docs fail. Let's get into it.
So NASA launched the Mars Climate Orbiter in December of 1998, and it traveled 416 million miles in 9 months. Its whole job was to study Martian weather and act as a communication relay for future missions. This was not a test run.
The day it was supposed to enter Mars orbit, the flight team watched it drift off course and disappear behind the planet. Except it never came back around.
What Happened
NASA's November 1999 Phase I investigation report identified the root cause: ground software supplied thruster impulse data in pound-seconds instead of the Newton-seconds required by the Software Interface Specification. The navigation software interpreted those values as metric, underestimating the effect of the thruster firings by a factor of 4.45 and calculating an incorrect trajectory.
Source: NASA — Mars Climate Orbiter Mishap Investigation Board Phase I Report, sections 4–5 (PDF)
The board also identified failures in verification, training, and communication. Navigation concerns were not communicated effectively, and teams relied on email rather than the formal Incident, Surprise, Anomaly reporting process. The report says failing to use that tracking process helped the problem slip through the cracks.
Source: NASA — Phase I Report, contributing causes 5, 7, and 8 (PDF)
The Real Lesson
The standard was written down — but it wasn't followed or adequately verified. That's the documentation lesson here: publishing a specification is not enough. Teams also need to check that their implementations match it and make sure concerns reach the people who can act on them.
If your team is passing work between departments and just assuming everyone's on the same page — where is that actually written down? Because 'we just know' is not a standard. That's just a mistake waiting to happen.