Jump to content

Soyuz MS-10

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 12.10.222.67 (talk) at 22:35, 11 October 2018 (Remove reference to a Launch Escape System.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Soyuz MS-10
Launch of the Soyuz-FG rocket carrying the MS-10 spacecraft
OperatorRoskosmos
Spacecraft properties
Spacecraft typeSoyuz-MS 11F747
ManufacturerRKK Energia
Crew
Crew size2
MembersAleksey Ovchinin
Nick Hague
CallsignBurlak
Start of mission
Launch date11 October 2018[1][2]
RocketSoyuz-FG
Launch siteBaikonur Pad 1/5
End of mission
Landing date11 October 2018
Landing site20km East of Jezkazgan, Kazakhstan
Orbital parameters
Reference systemGeocentric
RegimeSub-orbital spaceflight
Docking with ISS
File:Soyuz-MS-10-Mission-Patch.png
Soyuz programme
(Manned missions)

Soyuz MS-10 was a manned Soyuz spaceflight which aborted shortly after launch on 11 October 2018.[1][2] MS-10 was the 139th flight of a Soyuz spacecraft. It was intended to transport two members of the Expedition 57 crew to the International Space Station. A few minutes after liftoff, the craft went into contingency abort due to a booster failure and had to return to Earth. Both crew members, NASA astronaut Nick Hague and Roscosmos cosmonaut Aleksey Ovchinin were recovered in good condition.[3] This was the first instance of a manned booster accident at high altitude in 43 years, when Soyuz 7K-T No.39 similarly failed to achieve orbit in April of 1975.[citation needed]

Crew

Position Crew member
Commander Russia Aleksey Ovchinin, RSA
Expedition 57
Second spaceflight
Flight Engineer 1 United States Nick Hague, NASA
Expedition 57
First spaceflight

Backup crew

Position[4] Crew member
Commander Russia Oleg Kononenko, RSA
Flight Engineer 1 Canada David Saint-Jacques, CSA

Launch abort

A few minutes after liftoff, which took place at 08:40 UTC, the crew reported feeling weightless and mission control declared a booster had failed. A radio call indicated "rocket failure" had occurred 2 minutes 45 seconds into flight, at an altitude of 90 miles (140 km).[5][6] Shortly after, a contingency was declared and the spacecraft carrying the crew performed an emergency seperation. It returned to Earth in a ballistic trajectory, during which the crew experienced 6.7G, followed by a successful landing.[7]

Recovery

File:Soyuz MS-10 crew wearing blood pressure cuffs in Jezkazgan.jpg
Soyuz MS-10 crew wearing blood pressure cuffs and pulse oximeters in Jezkazgan following their recovery after landing

At 08:55 UTC the search and rescue team was deployed to recover the crew and the spacecraft and crew which had landed 402 kilometres (250 mi) from the launch site and 20 kilometres (12 mi) east of Jezkazgan, Kazakhstan.[5] Approximately 25 minutes after the search and rescue team took off, NASA announced they were in contact with Ovchinin and Hague. NASA TV broadcast photographs of the crew undergoing medical tests and apparently healthy at Jezkazgan Airport at 12:04 UTC.[8] The crew flew to the Baikonur Cosmodrome to meet their families[9] before leaving for Moscow.[10]

Response

Following the anomaly, all manned Soyuz launches were suspended. Roscosmos announced that it had started a full state investigation into the incident.[11] The inquiry, referred to by Russia’s investigative committee as "a criminal investigation", came weeks after Roscosmos was forced to launch an investigation into how a hole came to be drilled into the wall of the Soyuz capsule that is now docked at the space station.[12]

The current crew of the International Space Station have been informed of the failed flight (according to NASA Live voice-over). The crew can return safely in the Soyuz MS-09 capsule, but only until about late-December, due to the limited lifespan of "about 200 days" of the capsule; they would have to leave by mid-December.[13] If the investigation concludes with the grounding of the Soyuz, the ISS may be abandoned until the Commercial Crew Program revives proper certification; this may result in the lack of maintenance of the ISS, but "ground controllers could keep it up and running for a while"[14].

See also

Mission events

References

  1. ^ a b NASA (17 September 2018). "Expedition 57". Retrieved 20 September 2018.
  2. ^ a b Pietrobon, Steven (5 February 2017). "Russian Launch Manifest". Retrieved 12 February 2017.
  3. ^ "Space Station – Off The Earth, For The Earth". blogs.nasa.gov. Retrieved 11 October 2018.
  4. ^ Spacefacts.de (20 May 2018). "Manned Spaceflight Launch and Landing Schedule". Retrieved 29 May 2018.
  5. ^ a b Bridenstine, Jim [@JimBridenstine] (11 October 2018). "@NASA astronaut Nick Hague and Russian cosmonaut Alexey Ovchinin are in good condition following today's aborted launch. I'm grateful that everyone is safe. A thorough investigation into the cause of the incident will be conducted. Full statement below: …" (Tweet) – via Twitter. anomaly with the booster and the launch ascent was aborted
  6. ^ "Soyuz MS-10 Crew Lands Safely in Kazakhstan, Following Launch Vehicle Failure". 11 October 2018. Retrieved 11 October 2018.
  7. ^ Astronauts survive Soyuz rocket emergency landing CNN, 2018-10-11.
  8. ^ NASA Live: Official Stream of NASA TV NASA TV, 2018-10-11.
  9. ^ Expedition 57 Crew Returns to Baikonur (NHQ201810110007) NASA at Flickr, 2018-10-11.
  10. ^ "*EXCLUSIVE* #SoyuzMS10 crew departs Baikonur for Moscow". {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  11. ^ "Astronauts escape malfunctioning Soyuz rocket". BBC News. Retrieved 11 October 2018.
  12. ^ Sample, Ian (11 October 2018). "Rocket launches to be grounded while mid-air failure is investigated". the Guardian. Retrieved 11 October 2018.
  13. ^ "Empty Space Station? NASA Prepares for the Worst (but Hopes for the Best) After Soyuz Abort. (other sources also available)". {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  14. ^ "NASA to look at options to keep crew on ISS while Soyuz grounded". {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)