Jump to content

Soyuz TM-17

Coordinates: 49°37′N 70°07′E / 49.617°N 70.117°E / 49.617; 70.117
From Wikipedia, the free encyclopedia
Soyuz TM-17
OperatorRosaviakosmos
COSPAR ID1993-043A Edit this at Wikidata
SATCAT no.22704Edit this on Wikidata
Mission duration196 days, 17 hours, 45 minutes, 22 seconds
Orbits completed~3,070
Spacecraft properties
SpacecraftSoyuz 7K-STM No. 66
Spacecraft typeSoyuz-TM
ManufacturerNPO Energia
Launch mass7,150 kilograms (15,760 lb)
Crew
Crew size3 up
2 down
MembersVasili Tsibliyev
Aleksandr Serebrov
LaunchingJean-Pierre Haigneré
CallsignСи́риус (Sirius)
Start of mission
Launch dateJuly 1, 1993, 14:32:58 (1993-07-01UTC14:32:58Z) UTC
RocketSoyuz-U2
End of mission
Landing dateJanuary 14, 1994, 08:18:20 (1994-01-14UTC08:18:21Z) UTC
Landing site49°37′N 70°07′E / 49.62°N 70.12°E / 49.62; 70.12
Orbital parameters
Reference systemGeocentric
RegimeLow Earth
Perigee altitude388 kilometres (241 mi)
Apogee altitude397 kilometres (247 mi)
Inclination51.6 degrees
Docking with Mir
Soyuz programme
(Crewed missions)

Soyuz TM-17 was a Russian spaceflight to the space station Mir, launched on July 1, 1993. It carried Russian cosmonauts Vasily Tsibliyev and Aleksandr Serebrov, along with French astronaut Jean-Pierre Haigneré.[1] It lasted 196 days and 17 hours, making more than 3,000 orbits of the planet Earth.[2]

Crew

[edit]
Position Launching crew Landing crew
Commander Russia Vasili Tsibliyev
First spaceflight
Flight Engineer Russia Aleksandr Serebrov
Fourth spaceflight
Research Cosmonaut France Jean-Pierre Haigneré
First spaceflight
None

Mission highlights

[edit]

Soyuz TM-17 was the 17th expedition to the Russian Space Station Mir.

At 7:37:11 a.m. Moscow time (MT), on 1994 January 14, Soyuz-TM 17 separated from the forward port of the Mir station. At 7:43:59 a.m., the Mission Control Center in Korolev (TsUP) ordered Tsibliyev to steer Soyuz-TM 17 to within 15 metres of the Kristall module to begin photography of the APAS-89 docking system. At 7:46:20 a.m., Tsibliyev complained that Soyuz-TM 17 was handling sluggishly. Serebrov, standing by for photography in the orbital module, then asked Tsibliyev to move the spacecraft out of the station plane because it was coming close to one of the solar arrays. In Mir, Viktor Afanasyev ordered Valeri Polyakov and Yuri Usachyov to evacuate to the Soyuz TM-18 spacecraft. At 7:47:30 a.m., controllers in the TsUP saw the image from Soyuz-TM 17's external camera shake violently, and Serebrov reported that Soyuz-TM 17 had hit Mir. The TsUP then lost communications with Mir and Soyuz-TM 17. Intermittent communications were restored with Soyuz-TM 17 at 7:52 a.m. Voice communications with Mir were not restored until 8:02 a.m. Inspection of Soyuz-TM 17 indicated no serious damage. In this connection, the Russians revealed that they had studied contingency reentries by depressurized spacecraft in the wake of the Soyuz 11 accident. The Mir cosmonauts did not feel the impact, though the station's guidance system registered angular velocity and switched to free flying mode.

Later analysis indicated that the right side of the orbital module had struck Mir two glancing blows 2 seconds apart. The impact point was on Kristall, near its connection to the Mir base block. The cause of the impact was traced to a switch error: the hand controller in the orbital module which governed braking and acceleration was switched on, disabling the equivalent hand controller (the left motion control lever) in the descent module. Tsibliyev was able to use the right lever to steer the Soyuz past Mir's solar arrays, antennas, and docking ports after it became clear impact was inevitable.

References

[edit]
  1. ^ Pearlman, Robert Z. (2013-11-19). "Cosmonaut Alexander Serebrov, Veteran of 4 Space Missions, Dies at 69". Space.com. Retrieved 2023-11-22.
  2. ^ "Spaceflight mission report: Soyuz TM-17". www.spacefacts.de. Retrieved 2023-11-21.

49°37′N 70°07′E / 49.617°N 70.117°E / 49.617; 70.117

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy