When the Mars Climate Orbiter left Earth on December 11, 1998, it carried a clear and substantial set of objectives. The spacecraft was designed to spend a Martian year in orbit, mapping the planet’s weather patterns and seasonal shifts in water vapor and carbon dioxide ice —data scientists needed to better understand Mars’s climate history, seasonal water vapor, dust, clouds and carbon dioxide ice. It would also serve as a communications relay for the Mars Polar Lander, due to touch down near the southern polar cap on December 3, 1999. The spacecraft had cost $125 million. Nine months of interplanetary travel and careful trajectory planning had gone into getting it to the right place at the right time.
On September 23, 1999, it reached Mars. And then it was gone.
The file that was never translated
The specific cause was narrow enough to seem almost absurd in retrospect. NASA’s Mars Climate Orbiter Mishap Investigation Board traced the loss to a segment of ground-based navigation software known as “Small Forces,” used in trajectory modeling. The software output from angular momentum desaturation events was supposed to be reported in metric units but was delivered in English units.
The cumulative error was not properly diagnosed until it was too late. When the orbiter arrived at Mars, its trajectory was approximately 170 kilometers lower than planned. NASA’s investigation concluded that the spacecraft either was destroyed in the Martian atmosphere or re-entered heliocentric space after leaving the atmosphere, never to be heard from again.
JPL’s initial peer review findings, released September 30, 1999, described the error plainly: one team had been using English units, the other metric, for a key spacecraft operation. “Our inability to recognize and correct this simple error has had major implications,” said Dr. Edward Stone, then director of JPL.
A management failure, not just a coding error
The independent review board that reported in March 2000 concluded that the project had been under-resourced. “The Mars Surveyor Program agreed to significant cuts in the monetary and personnel resources available to support the Mars Climate Orbiter mission, as compared to previous projects,” the board concluded. “More importantly, the program failed to introduce sufficient discipline in the processes used to develop, validate and operate the spacecraft, and did not adequately install a mission-success culture that would shore up the risk introduced by these cuts.”
This was the era of NASA’s “faster, better, cheaper” initiative — an agency-wide mandate to run more missions on smaller budgets. The same review concluded that, in some cases, too much emphasis had been placed on reducing cost and schedule, while too little rigor had been applied to risk management and mission assurance.
“People sometimes make errors,” Dr. Edward Weiler, NASA’s Associate Administrator for Space Science, said in September 1999. “The problem here was not the error, it was the failure of NASA’s systems engineering, and the checks and balances in our processes to detect the error. That’s why we lost the spacecraft.”
After the loss, NASA’s mishap board recommended that future Mars missions verify the consistent use of units across spacecraft design and operations, audit software interfaces for compliance, and perform complete end-to-end verification and validation of mission-critical events. The lesson was not simply to “use metric,” but to make sure the interfaces between teams and systems were tested closely enough to catch a mismatch before it reached flight operations.
The Mars Climate Orbiter has become a standard case study in aerospace engineering and software development — cited not because the underlying mistake was exotic, but because it was not. A number, passed across an interface between two groups who assumed they were speaking the same technical language, propagated undetected for nine months. What failed was not the science or the spacecraft. It was the set of processes that should have caught the discrepancy before it had anywhere to go.