Home | Breaking News | Space crew abort flight after post-launch rocket failure
U.S. astronaut Nick Hague, right and Russian cosmonaut Alexey Ovchinin, member of the main crew of the expedition to the International Space Station (ISS), walk prior to the launch of Soyuz MS-10 space ship at the Russian leased Baikonur cosmodrome, Kazakhstan, Thursday, Oct. 11, 2018.

Space crew abort flight after post-launch rocket failure

WT24 Desk

A Russian-American space crew have been forced to make an emergency landing in Kazakhstan after their Soyuz rocket suffered a failure shortly after launching from Russia’s Baikonur cosmodrome in one of the most serious space incidents in recent years, The Guardian reports.

The launch began as a routine affair. Missions bound for the International Space Station (ISS) have been conducted every few months for the past 20 years. But 119 seconds into Thursday’s flight, mission controllers on the Nasa broadcast began to speak of a failure.

Shaky footage from the capsule’s cabin seen during the live broadcast appeared to show objects floating mid-launch. The crew told mission control they felt weightless, an indication of a problem during that stage of the flight.

Agitated voices flooding the radio link between mission control and the capsule could be heard on the Nasa broadcast. Details and the exact sequence of events remain unclear, but shortly afterwards the crew initiated an abort and ejected their capsule from the rocket.

Judging by the time at which the failure took place, it involved separation of the rocket’s second stage – just before the ship would have ignited the third stage for its final kick to exit the atmosphere.

A commentator on Nasa’s live broadcast later said that rescue teams had reached the capsule’s landing site and the two-person crew were in “good condition”. The Russian Alexey Ovchinin and the American Nick Hague had already left the capsule when rescue teams arrived.


Leave a Reply

Your email address will not be published. Required fields are marked *


%d bloggers like this: