Friday, May 15, 2015

Roscosmos decided to make public the reasons for the accident “Progress” – SoftSraze: actual and objectively

1061789952
In Roskosmos reported that the commission investigating the causes of the accident cargo spacecraft “Progress”, life has been extended from 12 to 22 May must submit by this date a comprehensive statement. This is with reference to the representative agency RIA Novosti reported.

carrier rocket “Soyuz-2.1a” with the cargo ship “Progress M-27M “launched from Baikonur on April 28. Branch ship from the third stage carrier passed abnormally, resulting in a space truck was on neraschёtnoy orbit in the strong twist. This in turn has led to the abolition of docking with the ISS. In the future, to take control of “Progress M-27M” failed, he began to fall to Earth in the last zatonuv quiet ocean.

« Conclusion of the Commission – May 22, as stated about it on May 12 briefing the head of the State Commission for conducting flight tests of manned complexes Alexander Ivanov. Employment specialists goes to the space industry. For the final classification of the nature of the causes that led to the end of the emergency starter requires in-depth computational and theoretical studies, additional modeling and a number of experimental works. Who conducted ground experiments in order to find out what could have caused the depressurization of the oxidizer tank and fuel tank in the future of the third stage carrier rocket “Soyuz 2.1a », – said the source.

According to him, before the separation of the ship from the third stage of “Union 2.1a” start-up and separation of the space truck “Progress M-27M” took place normally. At 526 seconds into the flight there was an unintended separation of the third stage of the rocket and “progress”, with the result that the ship was in orbit with an apogee of 40 kilometers above, and the third stage – in an orbit with an apogee of 20 km below the calculated trajectory launch.

Tags: Progress-M-25M, Roskosmos

Short URL : http://softcraze.com/?p= 33707


LikeTweet

No comments:

Post a Comment