Mars Climate Orbiter: When Units Become an Interface Failure

What happened

NASA's Mars Climate Orbiter was lost in September 1999 as it arrived at Mars. The investigation found that ground software produced thruster-impulse data in pound-force seconds, while the navigation software expected metric units (newton-seconds). The spacecraft's trajectory was therefore wrong, and it approached Mars at a lower altitude than planned.

The lesson goes beyond a unit conversion. Several checks along the interface, including reviews and the navigation team's own tracking of the discrepancy, did not stop the error before it mattered.

A classroom illustration

This example is only to show the size of such a mismatch. It does not reconstruct the mission trajectory.

1. One system sends an impulse of 10 pound-force seconds.
2. The receiving system reads the number 10 as newton-seconds.
3. One pound-force is about 4.44822 newtons, so the real quantity is about 44.48 N·s, more than four times what the receiver used.

Apply the lesson

For a fictional equipment-data export, write an interface definition that states:

• The physical quantity each field represents.
• Its unit and reference convention.
• Expected ranges and how missing values are shown.
• A sample input and the result the receiving system should produce.
• The person or team who approves changes.

Then ask a reviewer to interpret the data without anyone explaining it. Every ambiguity they find is a revision to the definition.

Discussion question

Where in your own workflow could a plausible-looking number cross a boundary without its meaning being checked?

Engineering lesson: treat units and conventions as part of the data contract, and verify the interpretation at both ends.

What the independent assessment added

NASA's Mars Program Independent Assessment Team reviewed the program after the loss. Its report says the orbiter was lost as the result of a navigation error that went unresolved, which caused the spacecraft to enter the atmosphere of Mars instead of achieving orbit. It states that spacecraft operating data needed for navigation were provided by the prime contractor, Lockheed Martin, in English units rather than the specified metric units.

The report also describes a failure of the system of checks and balances. It lists multiple failures: lack of training, software testing, communication, adherence to anomaly reporting procedures, and inadequate preparation for contingencies. It says that all of these contributed, and that the team found multiple examples of ineffective risk identification and communication by both the Jet Propulsion Laboratory and Lockheed Martin.

Sources

• NASA Lessons Learned: Mars Climate Orbiter Mishap
• NASA Mars Program Independent Assessment Team report, 2000 (NTRS)