Progress M-27M

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Progress M-27M
Mission type ISS resupply
Operator Roscosmos
COSPAR ID 2015-024A
SATCAT № 40619
Spacecraft properties
Spacecraft type Progress-M 11F615A60
Manufacturer RKK Energia
Launch mass 7,298 kg (16,089 lb)
Start of mission
Launch date 28 April 2015, 07:09:50 (2015-04-28UTC07:09:50Z) UTC[1]
Rocket Soyuz-2.1a
Launch site Baikonur 31/6[1]
End of mission
Disposal Deorbited
Decay date 08 May 2015, 02:04 UTC [2]
Orbital parameters
Perigee 158 kilometres (98 mi)[3]
Apogee 184 kilometres (114 mi)[3]
Inclination 51.64 degrees[3]
Period 87.92 minutes[3]
Epoch 06 May 2015, 21:35:19  UTC[3]
Docking with ISS
Docking port Pirs nadir
Docking date Docking attempt cancelled[4]
Time docked N/A
Cargo
Mass 2,357 kg (5,196 lb)
Pressurised 1,393 kg (3,071 lb)
Fuel 494 kg (1,089 lb)
Gaseous 50 kg (110 lb)
Water 420 kg (930 lb)
----
Progress ISS Resupply
← Progress M-26M Progress M-28M

Progress M-27M (Russian: Прогресс М-27М), identified by NASA as Progress 59 or 59P, was a Progress spacecraft used by Roscosmos in an unsuccessful attempt to resupply the International Space Station (ISS) in 2015.[5]

Progress M-27M was launched on 28 April 2015, with a planned 6-hour rendezvous profile to the ISS. During the launch the spacecraft achieved low Earth orbit, but a malfunction occurred near the end of the upper stage burn shortly before the separation of the Progress spacecraft, generating a debris field and leaving the spacecraft spinning and unable to be fully controlled. The spacecraft was deemed to be a total loss.

On 8 May 2015 at 02:20 UTC, the spacecraft was confirmed to have undergone destructive reentry over the middle of the Pacific Ocean.[2]

Progress M-27M was the 27th Progress-M 11F615A60 spacecraft, with the serial number 426. It was built by RKK Energia and was operated by the Russian Federal Space Agency.[6] This was the second time the upgraded Soyuz-2.1a rocket was used for an ISS mission launch

Launch

The spacecraft was launched on 28 April 2015 at 07:09 GMT from the Baikonur Cosmodrome in Kazakhstan.[7]

Cargo

The spacecraft carried 2,357 kg (5,196 lb) of food, fuel and supplies, including 494 kg (1,089 lb) of propellant, 50 kg (110 lb) of oxygen, 420 kg (930 lb) of water, and 1,393 kg (3,071 lb) of spare parts, supplies and experiment hardware for the six members of the Expedition 43 crew aboard the International Space Station.[8]

Spacecraft failure

Diagram: Free fall, Altitude/Date, Progress M-27M, Object 2015-024A

After reaching low Earth orbit, but before separation of the spacecraft from the rocket,[9] communication with the vessel was lost.[10] Ground controllers only received brief telemetry shortly after that confirmed spacecraft separation as well as the deployment of the solar panels, but were not able to confirm the deployment of rendezvous antennas of the KURS system. Initially controllers tried to fall back to the plan of making a 2-day rendezvous with the ISS, but this was also abandoned after ground stations were not able to communicate with the spacecraft during the next 3 orbits.[10]

During its fourth orbit, video released from an onboard camera used for docking showed that the spacecraft was spinning wildly in space. Further efforts on that day to establish communications with the spacecraft were unsuccessful.[10][11] Two more communication sessions were attempted on 28 April to regain control of the spacecraft, but did not succeed.[12]

On 29 April, Roscosmos officially announced that the spacecraft was out of control and its orbit would eventually decay to fall back into Earth's atmosphere, with multiple systems suffering from failure and the main engine's fuel lines depressurized.[10][13][14] The spacecraft was expected to disintegrate in the Earth's atmosphere between May 7 and 11.[15] On the same day, the United States' NORAD reported that 44 pieces of debris "in the vicinity of the resupply vehicle and its upper stage rocket body" were being tracked by space tracking systems.[16] Currently, various Russian sources reported that the potential cause of the anomaly may be related to the upper stage rocket engine shutdown or with the separation of the Progress spacecraft from the upper stage.[10][16] A representative of the United States Air Force claimed that debris in the area indicated a blast.

"Given [the altitude of the debris] and the fact that Progress was found 30 to 40 kilometres above its intended orbit, we can say with confidence that there was some kind of blast at the moment of separation from the third stage of the rocket"[17]

The spacecraft underwent destructive atmospheric reentry on May 8 at 02:20 UTC between 350 to 1,300 km off the South American coast, west of Chile.[18][19]

On June 1, Roscosmos announced the results of an investigation into the cause of the failure, attributing it to a "design peculiarity" in the linkage between the Soyuz 2.1a rocket and the spacecraft.[20]

The cost of the loss of the mission was valued at 2.59 billion rubles ($50.7m US).[21]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 10.3 10.4 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. /progress-m-27m-re-entry.html#update
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.

External links