Soyuz MS-10

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Soyuz MS-10
Expedition 57 Launch (NHQ201810110004).jpg
Launch of the Soyuz-FG rocket carrying the MS-10 spacecraft
Mission type ISS crew rotation
Operator Roscosmos
Mission duration 19 minutes, 41 seconds
Spacecraft properties
Spacecraft type Soyuz-MS (11F747)
Manufacturer RKK Energia
Callsign Burlak
Start of mission
Launch date 11 October 2018, 08:40 UTC
Rocket Soyuz-FG (U15000-064)
Launch site Baikonur Pad 1/5
End of mission
Landing date 11 October 2018, 08:55 UTC
Landing site 20 km east of Jezkazgan, Kazakhstan


Expedition 57 Crew Farewell (NHQ201810110002).jpg
Nick Hague (above) and Aleksey Ovchinin (below)
Soyuz programme
(Manned missions)

Soyuz MS-10 was a manned Soyuz MS spaceflight which aborted shortly after launch on 11 October 2018[1][2] due to a failure of the Soyuz-FG booster rocket.[3][4] 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. By the time the contingency abort was declared, the launch escape system (LES) had been ejected and the capsule was pulled away from the rocket using the back-up motors on the capsule fairing.[5] Both crew members, Roscosmos cosmonaut Aleksey Ovchinin and NASA astronaut Nick Hague, were recovered alive in good health.[3] The MS-10 flight abort was the first instance of a Russian manned booster accident at high altitude in 43 years, since Soyuz 18a failed to make orbit in April 1975.[4]


Prime 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[6] Crew member
Commander Russia Oleg Kononenko, RSA
Flight Engineer 1 Canada David Saint-Jacques, CSA


Flight crew during launch (left) and debris falling from the Soyuz-FG launch vehicle after booster separation (right).

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. According to Sergei Krikalyov of Roscosmos, the primary cause of the failure was a collision that occurred during the separation of the carrier rocket’s first and second stages. "A deviation from the standard trajectory occurred and apparently the lower part of the second stage disintegrated," he said.[7] Shortly after, a contingency was declared and the spacecraft carrying the crew performed an emergency separation, returning to Earth in a ballistic trajectory, during which the crew experienced "about six to seven times Earth's gravity" followed by a successful landing.[8] The abort occurred at an altitude of approximately 50 kilometres (31 miles)[9]; the spacecraft reached an apogee of 93 km (58 mi) then landed 19 minutes and 41 seconds after launch.[10]

The crew wearing blood pressure cuffs and pulse oximeters following their recovery (left) and later greeting their families in Baikonur (right).

At 08:55 UTC the search and rescue team was deployed to recover the crew and the spacecraft which had landed 402 kilometres (250 mi) from the launch site and 20 kilometres (12 mi) east of Jezkazgan, Kazakhstan.[11] 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.[12] The crew flew to the Baikonur Cosmodrome to meet their families[13] before leaving for Moscow.[14]


Following the aborted spaceflight, the Russian government announced that manned Soyuz launches would be suspended. Roscosmos ordered a full state commission to investigate the incident,[15] and the BBC reported that a criminal investigation is also expected.[16] A few weeks prior to the failed launch, another investigation had commenced into how a hole came to be drilled into the wall of the Soyuz MS-09 capsule that is now docked at the International Space Station.[17] After collecting the debris of the rocket, the commission started the investigation on 15 October 2018.[18] Initially a faulty cable connecting to the first stage booster was suspected, but by 17 October 2018 the commission was concentrating on the manufacture sequence of the Soyuz rocket, and set the investigation deadline to 21 October 2018.[19] By 18 October 2018, the failure to correctly mate the first stage booster with the first stage core was identified as the likely cause of the flight abort. The side booster was likely damaged and re-contacted the core during stage separation.[20].

The current crew of the International Space Station can return in the Soyuz MS-09 capsule, but due to the limited lifespan of "about 200 days" of the Soyuz capsule, under existing plans, they would have to leave by mid-December.[21] If the investigation concludes with the grounding of the Soyuz, the ISS may have to be abandoned until Soyuz launches resume; this may result in the lack of maintenance of the ISS, but "ground controllers could keep it up and running for a while".[22] Within a day of the incident Dimitry Rogozin, chief of Roscosmos, said that their plan is for Ovchinin and Hague to fly again in early 2019.[23]

See also


  1. ^ NASA (17 September 2018). "Expedition 57". Retrieved 20 September 2018.
  2. ^ Pietrobon, Steven (5 February 2017). "Russian Launch Manifest". Retrieved 12 February 2017.
  3. ^ a b Garcia, Mark (11 October 2018). "Crew in Good Condition After Booster Failure". NASA Space Station. Retrieved 11 October 2018.
  4. ^ a b Harwood, William (11 October 2018). "Soyuz crew lands safely after emergency launch abort". Spaceflight Now. Retrieved 12 October 2018.
  5. ^ "How Russia's trusty space launch escape system saved 6 lives after initial deadly start". RT. Retrieved 12 October 2018.
  6. ^ (20 May 2018). "Manned Spaceflight Launch and Landing Schedule". Retrieved 29 May 2018.
  7. ^ "Roscosmos reveals cause for Soyuz launch failure". AzerNews. 12 October 2018. Retrieved 14 October 2018.
  8. ^ Hodge, Nathan; Smith-Spark, Laura (11 October 2018). "Astronauts survive Soyuz rocket emergency landing". CNN. Retrieved 12 October 2018.
  9. ^ "Soyuz MS-10 makes emergency landing after a launch failure". Retrieved 12 October 2018.
  10. ^ Burghardt, Thomas (18 October 2018). "NASA and Roscosmos trying to avoid an empty Space Station –". Retrieved 19 October 2018.
  11. ^ 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.
  12. ^ NASA Live: Official Stream of NASA TV NASA TV, 11 October 2018.
  13. ^ Expedition 57 Crew Returns to Baikonur (NHQ201810110007) NASA at Flickr, 11 October 2018.
  14. ^ @Ruptly (11 October 2018). "*EXCLUSIVE* #SoyuzMS10 crew departs Baikonur for Moscow" (Tweet) – via Twitter.
  15. ^ "Astronauts escape malfunctioning Soyuz rocket". BBC News. 11 October 2018. Retrieved 11 October 2018.
  16. ^ "Investigation starts into dramatic Soyuz rocket breakdown". BBC News. 12 October 2018. Retrieved 13 October 2018.
  17. ^ Sample, Ian (11 October 2018). "Rocket launches to be grounded while mid-air failure is investigated". The Guardian. Retrieved 11 October 2018.
  18. ^ Роскосмос. Госкомиссия приступила к работе на РКЦ «Прогресс» 15.10.2018 10:15
  19. ^ «Роскосмос» назвал дату готовности доклада об аварии «Союза»
  20. ^ Эксперты назвали виновных в крушении "Союза МС-10"
  21. ^ Wall, Mike (11 October 2018). "Empty Space Station? NASA Prepares for the Worst (but Hopes for the Best) After Soyuz Abort".
  22. ^ Foust, Jeff (11 October 2018). "NASA to look at options to keep crew on ISS while Soyuz grounded". SpaceNews.
  23. ^ RT (12 October 2018). "Safe & sound: Soyuz crew returns to Moscow after rocket malfunction" – via YouTube.

External links