{"id":16353,"date":"2015-04-29T21:56:38","date_gmt":"2015-04-29T13:56:38","guid":{"rendered":"https:\/\/wp-productionenv-bjg9h2g2bgg5b8aa.southeastasia-01.azurewebsites.net\/news\/progress-failure-probe-narrows-in-on-separation-from-rocket\/"},"modified":"2015-04-29T21:56:38","modified_gmt":"2015-04-29T13:56:38","slug":"progress-failure-probe-narrows-in-on-separation-from-rocket","status":"publish","type":"post","link":"https:\/\/starpath.global\/news\/progress-failure-probe-narrows-in-on-separation-from-rocket\/","title":{"rendered":"Progress failure probe narrows in on separation from rocket"},"content":{"rendered":"
\"File
File photo of a Russian Progress supply ship during rendezvous with the International Space Station. Credit: NASA<\/figcaption><\/figure>\n

Something went wrong with a Russian Progress resupply mission moments before the spacecraft deployed into orbit Tuesday on the way to the International Space Station, and investigators are analyzing whether the stricken supply ship may have lost control after a botched separation from its Soyuz rocket booster.<\/p>\n

Officials from the Russian space agency, or Roscosmos, gave up hopes of salvaging the Progress M-27M spacecraft Wednesday, writing off the possibility of continuing the mission to deliver more than three tons of supplies to the space station.<\/p>\n

Roscosmos said in a statement Wednesday that mission control lost communications with the Progress spacecraft 1.5 seconds before the cargo carrier\u2019s planned separation from the third stage of its Soyuz launcher.<\/p>\n

Engineers later regained intermittent telemetry from the troubled unmanned spaceship indicating it deployed from the Soyuz rocket, which also stopped sending data to ground teams around the same time, according to Roscosmos chief Igor Komarov.<\/p>\n

The U.S. military is tracking a cloud of debris around the out-of-control Progress spacecraft and the Soyuz rocket\u2019s third stage, according to a press release issued by the Joint Functional Component Command for Space\u2019s Joint Space Operations Center, or JSpOC.<\/p>\n

The military unit said Tuesday its tracking sensors indicated the Progress spacecraft was spinning once every five seconds. Video from a camera on-board the spacecraft released by NASA on Tuesday also showed the Progress in a fast rotation.<\/p>\n

\u201cAdditionally, the JSpOC has observed 44 pieces of debris in the vicinity of the resupply vehicle and its upper stage rocket body,\u201d the U.S. military\u2019s statement said.<\/p>\n

While experts were unable to verify the origin of the fragments around the Progress resupply freighter and its rocket, the detection raises the question of whether an explosion or collision may have led to the mission\u2019s failure.<\/p>\n

A NASA TV commentator said after the launch that telemetry data received from the Progress spaceship indicated its power-generating solar panels extended as planned, but ground controllers could not confirm its navigation antennas deployed or its propulsion pressurized.<\/p>\n

The mission\u2019s launch from the Baikonur Cosmodrome in Kazakhstan on Tuesday marked the second Progress spacecraft to fly aboard a modernized version of Russia\u2019s mainstay Soyuz rocket.<\/p>\n

\"The
The doomed Progress M-27M spacecraft lifted off Tuesday at 0709 GMT (3:09 a.m. EDT) on a Soyuz 2-1a rocket. Credit: TsENKI<\/figcaption><\/figure>\n

The launcher\u2019s upgraded configuration \u2014 named the Soyuz 2-1a \u2014 uses updated electronics, a digital flight control system, and can loft 300 more kilograms \u2014 about 660 pounds \u2014 to the International Space Station\u2019s orbit than previous iterations of the Soyuz rocket, according to Roscosmos.<\/p>\n

The Soyuz 2-1a\u2019s third stage uses the same kerosene-fueled RD-0110 engine flown on older versions of the rocket. The Soyuz 2-1a configuration logged 21 flights before Tuesday\u2019s launch, with no failures attributed to the basic three-stage Soyuz core booster.<\/p>\n

A report by Russia\u2019s Tass news agency Wednesday claimed the RD-0110 engine burned longer than designed during Tuesday\u2019s launch, citing a source from the engine\u2019s manufacturer.<\/p>\n

\u201cThe contingency with the Progress spacecraft might have been caused by problems with the engine control system that was giving commands,\u201d Tass said in its report.<\/p>\n

RD-0110 engines have flown on more than 1,500 launches, according to Tass.<\/p>\n

Roscosmos officials said the Progress supply ship should remain in orbit until between May 5 and May 7, when it will succumb to natural atmospheric drag and fall back to Earth. Most of the craft will burn up during re-entry, which could occur anywhere between 51.6 degrees north and south latitude.<\/p>\n

Komarov said mission controllers have not given up trying to command the spaceship to conduct a guided re-entry over the ocean \u2014 a practice normally executed at the end of Progress missions \u2014 but engineers have so far been unsuccessful in repeated attempts to wrestle control of the errant cargo craft.<\/p>\n

Some pieces of the spacecraft could hit Earth\u2019s surface after the plunge through the atmosphere, but the event\u2019s risk to life and property is very low, even if the Progress comes down uncontrolled.<\/p>\n

NASA and Roscosmos officials said the space station residents were in no danger after the accident, and the Progress spacecraft is on a trajectory far below the altitude of the research complex.<\/p>\n

The Progress mission was set to ferry more than three tons of food, supplies and experiments to the space station\u2019s six-person crew. Despite the failure, the crew has enough food and other provisions to get by until at least early September, according to data on space station consumables shared by a NASA official.<\/p>\n

A commercial Dragon cargo craft owned by SpaceX is set for launch June 19 to replenish the space station\u2019s stock of supplies, and a Japanese HTV logistics mission will head for the complex Aug. 17.<\/p>\n

The next Progress launch was set for launch Aug. 6, but that could change as a result of this week\u2019s mishap.<\/p>\n

Roscosmos managers only said Wednesday that the next two Progress missions were expected to go up in the third and fourth quarters of this year.<\/p>\n

Russian experts are also tracing any impact the Progress failure could have on the launch of the next three-person crew to the International Space Station. The trio will blast off on a Soyuz rocket similar to the booster used on Tuesday\u2019s bungled flight.<\/p>\n

The investigation board\u2019s report is due to be submitted May 13, Roscosmos said.<\/p>\n

Follow Stephen Clark on Twitter: @StephenClark1.<\/i><\/b><\/p>\n","protected":false},"excerpt":{"rendered":"

File photo of a Russian Progress supply ship during rendezvous with the International Space Station. Credit: NASA Something went wrong with a Russian Progress resupply mission moments before the spacecraft deployed into orbit Tuesday on the way to the International Space Station, and investigators are analyzing whether the stricken supply ship may have lost control […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[3790,717,1602,513,4043,234,1302],"class_list":["post-16353","post","type-post","status-publish","format-standard","hentry","category-news","tag-expedition-43","tag-international-space-station","tag-iss-cargo","tag-progress","tag-progress-m-27m","tag-roscosmos","tag-soyuz"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/16353"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=16353"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/16353\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=16353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=16353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=16353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}