Lesson 5 of 6 · Robotic mission and software failures
Study robotic losses as failures of interfaces and checks
8 minute lesson · 3 checks along the way
Your goal for this lessonUse Mars Climate Orbiter and Mars Polar Lander to practice precise causal claims.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A unit mismatch crossed a software boundary
Mars Climate Orbiter was lost in September 1999. Its investigation identified a ground-software file that supplied thruster impulse data in pound-force seconds where the documented interface required newton-seconds. Navigation calculations interpreted the values using the expected units, introducing trajectory-estimation errors.
The important lesson is broader than memorizing two unit names. Interface requirements, software verification, team communication and checks of navigation behavior did not catch the mismatch before it became critical. The investigation examined those contributing conditions as well as the immediate data problem.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
A probable mechanism is not a directly observed replay
Mars Polar Lander was also lost in 1999. The subsequent review identified premature engine shutdown from spurious landing-leg deployment signals as the . The proposed mechanism involved software treating a transient signal as evidence of touchdown before the lander had reached the surface.
The loss of communication limited direct knowledge of the final sequence. Preserve the report’s probability language rather than present an exact observed chain. Testing a plausible mechanism can strongly support an explanation while still leaving uncertainty about what happened on the inaccessible spacecraft.
Check semantics and state across the system
Original teaching diagram. Data interface. Units and physical meaning. Sender and receiver assumptions. Control interpretation. Transient signals and mission phase. Integrated tests and evidence limits. Mars Polar Lander’s identified mechanism remains a most-probable explanation, not a directly observed replay.
Open full-size diagram in a new tab: Check semantics and state across the systemCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Practice checking meaning and operating state
For a fictional interface test, a sender labels a duration in milliseconds while a receiver interprets the number as seconds. Checking only whether a numeric value arrived would miss the error. A useful test verifies the physical meaning at both ends, including representative values and the intended conversion.
For a separate fictional landing controller, a brief sensor pulse should be interpreted in the context of mission phase and validated logic. This is a conceptual software lesson, not flight-control implementation advice. Integrated tests, traceable requirements and independent review help reveal errors that isolated component tests can miss.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.
- Read: Mars Climate Orbiter investigation: phase I, November 1999Compare the explanation and its assumptions with the worked example in this lesson.
- Read: Mars Climate Orbiter investigation: project management reportCompare the explanation and its assumptions with the worked example in this lesson.
- Read: NASA: review of recent Mars and deep-space missions, 2000Compare the explanation and its assumptions with the worked example in this lesson.