Protect the mission and preserve the record

NASA’s project history attributes the loss of Phobos 1 during cruise to an uploaded command sequence that disabled attitude thrusters. Without the intended solar orientation, the spacecraft lost the power needed to keep operating. This connects a command-handling problem to pointing and energy, rather than treating software and hardware as independent stories.

In an original command-review exercise, a proposed change disables an actuator that another function depends on. Useful safeguards include checking preconditions, simulating the resulting spacecraft state and verifying that power and communication remain supportable. A syntactically valid command can still be inappropriate for the current mission state; checking its characters alone is not a complete review.

Phobos 2 reached Mars orbit in January 1989 and returned scientific data before contact was lost on March 27. The planned close surface operations and lander releases did not take place. That ending must not erase the orbital observations, but it prevents the course from claiming that the full moon-exploration sequence was completed.

NASA’s project summary attributes the loss to an onboard-computer malfunction, while its HEASARC mission account also retains a radio-transmitter possibility. These summaries do not justify pretending that every detail of the failure is settled. This course treats the loss of contact and the missed deployment as established outcomes and makes the differing descriptions of the mechanism explicit.

Review a command through its physical consequences

The program helped investigate Mars and demonstrated the scientific potential of instruments such as imaging spectrometers and plasma analyzers. Its proposed surface mobility also remains part of small-body engineering history. The later Phobos-Grunt project has its own goals and outcome; a common target does not make it a continuation of the same spacecraft flight.

For an original final review, draw a dependency chain from an instrument’s observation to pointing, power, recording and communication. Mark which links were demonstrated in each mission phase and which remained planned. Then propose a test that could expose one dangerous command interaction before flight. The aim is an explainable engineering requirement, not a claim that a hypothetical test would certainly have saved the historical spacecraft.