The Unit Mix-Up That Doomed a Mars Probe

What happened?

The Mars Climate Orbiter launched on December 11, 1998, on a mission to study the Martian atmosphere and climate and to relay signals from a companion lander. After a 9.5-month, 416-million-mile journey, it reached Mars on September 23, 1999, and fired its main engine to slip into orbit. Moments after the spacecraft passed behind the planet — about 49 seconds earlier than expected — radio contact was lost and never recovered.

The investigation found the cause with painful clarity. A piece of ground software built by Lockheed Martin calculated the force of the spacecraft’s thruster firings in pound-force seconds, an imperial unit. But the NASA navigation software that used those numbers expected them in newton-seconds, the metric unit — and the two differ by a factor of about 4.45. Because nobody caught the mismatch, the orbiter’s true trajectory drifted steadily off the plan. Instead of skimming the upper atmosphere at a safe altitude of around 140 miles, the probe dropped to an estimated 35 miles or so above the surface, far too low to survive. It either burned up or skipped off the thick atmosphere into deep space.

Why was it strange?

This was not a subtle, undetectable glitch. At least two navigators noticed the spacecraft’s predicted position didn’t match reality in the weeks before arrival — but their concerns were brushed aside, in part because they “did not follow the rules” about filling out the proper form to document the problem. A planned course-correction maneuver that might have saved the mission was discussed and then never executed. A hundred-million-dollar machine was lost not to the unknown, but to a known discrepancy that slipped through the cracks of process and paperwork.

What did scientists learn?

As NASA’s Edward Weiler put it: “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.” The mishap board’s conclusions reshaped how NASA handles interface standards between contractors, how it validates navigation data, and how seriously it treats junior engineers raising red flags. Underfunding and overstretched teams — the Mars Surveyor '98 program was reportedly underfunded by at least 30% — were cited as deeper contributing causes.

How does it affect us today?

The Mars Climate Orbiter is now the canonical example used in engineering schools and software teams everywhere to explain why explicit units, rigorous interface specifications, and a culture where anyone can stop the line actually matter. Its lessons echo in modern code reviews, type-checked unit libraries, and “speak up” safety cultures. The story is grimly reinforced by the fact that NASA’s Mars Polar Lander was also lost just months later — a reminder that systemic problems rarely produce just one failure. More broadly, it cemented a principle far beyond spaceflight: when two systems must talk to each other, the contract between them is as critical as either system alone.

Fun fact

The cost of the lost orbiter is often cited at around

Sources

• “Mars Climate Orbiter,” Wikipedia — https://en.wikipedia.org/wiki/Mars_Climate_Orbiter
• Mars Climate Orbiter Mishap Investigation Board, Phase I Report, NASA, Nov. 10, 1999 — https://llis.nasa.gov/llis_lib/pdf/1009464main1_0641-mr.pdf
• Robin Lloyd, “Metric mishap caused loss of NASA orbiter,” CNN, Sept. 30, 1999
• James Oberg, “Why the Mars Probe went off course,” IEEE Spectrum, Dec. 1999