Surf Wiki
Save to docs
general/crewed-soyuz-missions

From Surf Wiki (app.surf) — the open knowledge base

Soyuz TM-5

1988 Soviet crewed spaceflight to Mir

1988 Soviet crewed spaceflight to Mir

FieldValue
nameSoyuz TM-5
insigniaSoyuz TM-5 mission patch.svg
COSPAR_ID1988-048A
SATCAT19204
mission_duration91 days, 10 hours, 46 minutes, 25 seconds
orbits_completed~1,475
spacecraftSoyuz 7K-STM No. 55
spacecraft_typeSoyuz-TM
manufacturerNPO Energia
launch_mass7000 kg
launch_dateUTC
launch_rocketSoyuz-U2
launch_siteBaikonur 1/5
landing_dateUTC
landing_site202 km SE of Dzhezkazgan
crew_size3 up
2 down
crew_launchingAnatoly Solovyev
Viktor Savinykh
Aleksandr Aleksandrov
crew_landingVladimir Lyakhov
Abdul Ahad Mohmand
crew_callsignРодни́к (Rodnik- Spring)
orbit_referenceGeocentric
orbit_regimeLow Earth
orbit_periapsis173 km
orbit_apoapsis241 km
orbit_inclination~51.6 degrees
orbit_period88.6 minutes
apsisgee
docking{{Infobox spaceflight/Dock
docking_targetMir
docking_typedock
docking_date9 June 1988, 15:57:10 UTC
undocking_date5 September 1988, 23:54:57 UTC
previous_missionSoyuz TM-4
next_missionSoyuz TM-6
programmeSoyuz programme
(Crewed missions)

2 down Viktor Savinykh Aleksandr Aleksandrov Abdul Ahad Mohmand (Crewed missions)

Soyuz TM-5 was a crewed Soyuz spaceflight to Mir. It was launched on June 7, 1988, carrying the Mir EP-2 mission's three-person crew. This week-long stay on Mir occurred during the third long-duration Mir expedition, Mir EO-3. The crew of EP-2 returned to Earth aboard Soyuz TM-4, while the TM-5 spacecraft remained docked to Mir, acting as the lifeboat for the long-duration crew. On September 7, 1988, the TM-5 spacecraft undocked from Mir, and landed Mir EP-3 mission's two-person visiting crew. The de-orbit procedures for Soyuz were revised after this flight, as multiple issues almost prevented the descent module's safe de-orbit and landing.

Crew

Launch

Main article: Mir EP-2

Soyuz TM-5 launched on 1988 June 7 and arrived at Mir on June 9 carrying the second Bulgarian in space, Alexandrov (not to be confused with the Soviet cosmonaut of the same name). He became the first Bulgarian to reach a Soviet space station (Georgi Ivanov failed to reach Salyut 6 on Soyuz 33 in 1979—Alexandrov was his backup). Their launch had been advanced by 2 weeks late in the planning stages to improve lighting conditions for the Rozhen astronomical experiment.

Landing

Main article: Mir EP-3

On September 5 cosmonauts Lyakhov and Mohmand undocked from Mir. They jettisoned the orbital module and made ready for deorbit burn to return to Earth. During descent, the spacecraft experienced a computer software problem combined with a sensor problem. This caused their landing to be delayed by a full day. The Descent Module, where they spent this 24-hour period, had no sanitary facilities. Consequently, they soiled themselves. They would not have been able to redock with Mir because they had discarded the docking system along with the orbital module. Reentry occurred as normal on September 7. Following this incident, the Soviets decided that on future missions, they would retain the orbital module until after deorbit burn, as they had done on the Soyuz Ferry flights.

References

References

  1. "Spacecraft "Soyuz TM-5"". space.kursknet.
  2. "Soyuz TM-5". Spacefacts.de.
  3. David Michael Harland. (February 2005). "The story of Space Station Mir". [[Springer-Verlag]].
  4. D.S.F. Portree. "Mir Hardware Heritage". NASA.
Info: Wikipedia Source

This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page.

crewed-soyuz-missions spacecraft-launched-in-1988 1988-in-the-soviet-union bulgaria–soviet-union-relations
Want to explore this topic further?

Ask Mako anything about Soyuz TM-5 — get instant answers, deeper analysis, and related topics.

Research with Mako

Free with your Surf account

Content sourced from Wikipedia, available under CC BY-SA 4.0.

This content may have been generated or modified by AI. CloudSurf Software LLC is not responsible for the accuracy, completeness, or reliability of AI-generated content. Always verify important information from primary sources.

Report