Emergencies and the legacy of Phase 1

In February 1997, a fire aboard Mir created an urgent crew emergency. In June, a Progress vehicle collided with the station and the Spektr module lost pressure. The two events had different initiating causes and consequences; describing both simply as a difficult year hides the engineering distinctions.

Jerry Linenger was aboard during the fire; C. Michael Foale was aboard during the collision. The people and ground teams had to respond with the hardware and information available. Their experience deserves careful description rather than a story that assumes the outcome was known in advance.

Isolating a leaking module protects the remaining pressurized volume, but connections through that boundary can also carry power or data. Emergency actions can therefore create new operational limitations while addressing the most immediate danger. System functions are connected even when equipment is spread across separate modules.

Consider a teaching model in which one damaged module supplies 30 of a station’s 100 power units. Losing it leaves 70 before any recovery work. Essential loads of 60 units leave only 10 for optional work. These invented values illustrate prioritization, not the measured Mir power budget.

Recalculate after a loss

Shuttle–Mir ended its docking phase with STS-91 in 1998, while Mir continued operating afterward. The partnership’s experience helped prepare teams for ISS work, including joint training, logistics and the demands of long stays. The end of one program phase was not the same event as the end of the station.

A safety lesson is useful when it changes equipment, training, procedures or decision-making and those changes are evaluated. Surviving an emergency does not prove that an unchanged system is safe. Studying Phase 1 means examining both its useful experience and the limits of what that experience demonstrated.