mistake.club

The encyclopedia · Software & IT · Technical decision · 1999

NASA lost a $327M Mars probe because two teams used different units

Lockheed's software spoke pound-seconds, NASA's spoke newton-seconds. Nobody translated, and the spacecraft flew into the atmosphere.

NASA · Lockheed Martin · 1999-09-23

What happened

The Mars Climate Orbiter spent nine months flying 669 million kilometers, flawlessly, toward the wrong place. Lockheed Martin's ground software reported thruster impulses in pound-force seconds, the imperial unit its engineers had always used. NASA's navigation software read those same numbers as newton-seconds, the metric unit the interface spec actually required. Every course correction was therefore off by a factor of 4.45.

The errors were tiny and they compounded quietly. Navigators noticed the trajectory drifting on the way to Mars and filed concerns, but the discrepancy was never escalated to a formal review. On September 23, 1999, the orbiter began its insertion burn 170 kilometers lower than planned — inside the Martian atmosphere instead of above it — and was destroyed or skipped off into space. Signal was never reacquired.

The mishap board's finding was blunt: the root cause wasn't the unit mix-up itself but the process that let it survive — an unverified interface between two organizations, and warning signs that were noticed, discussed, and not acted on.

Why it happened

  • The software interface spec required metric; Lockheed's module output imperial. Nobody wrote or ran a check at the boundary.
  • Navigation anomalies were spotted during cruise but handled informally and never escalated.
  • End-to-end testing that would have caught the mismatch was skipped under schedule pressure.
  • 'Faster, better, cheaper' era staffing left the navigation team thin and the reviews thinner.
The bill$327M missioncostly

The lesson

Interfaces between teams fail silently. Contracts on paper mean nothing unless a machine checks the actual data crossing the boundary.

Aftermath

NASA overhauled its mission review process, made metric compliance explicit, and the incident became the canonical unit-conversion cautionary tale in every engineering curriculum on Earth — an oddly effective legacy for a spacecraft that never got to work.

Sources

spotted an error? The club wants to know.

Comments · 0

    Sign in to join the comments.

    More like this