Cygnus CRS Orb-3

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Cygnus CRS Orb-3
Antares launch failure.jpg
Explosion on the launch vehicle seconds after launch
Mission type ISS resupply
Operator Orbital Sciences
Mission duration Planned: 1 month
Final: 15 seconds
Spacecraft properties
Spacecraft Cygnus 4
Spacecraft type Standard Cygnus[1]
Manufacturer Orbital Sciences
Thales Alenia Space
Payload mass 2,294 kg (5,057 lb)
Start of mission
Launch date 28 October 2014, 22:22:38 (2014-10-28UTC22:22:38) UTC[2][3]
Rocket Antares 130[1]
Launch site MARS LP-0A
Contractor Orbital Sciences
End of mission
Disposal Destroyed on launch
Destroyed 28 October 2014, 22:22:53 (2014-10-28UTC22:22:54) UTC
File:Cygnus Orb-3 Mission Emblem.jpg
Commercial Resupply Services
← Cygnus CRS Orb-2 Cygnus CRS OA-4

Cygnus CRS Orb-3,[4][5] also known as Orbital Sciences CRS Flight 3 or Orbital 3, was an attempted flight of Cygnus, an automated cargo spacecraft developed by United States-based company Orbital Sciences, on 28 October 2014. This flight, which would have been its fourth to the International Space Station and the fifth of an Antares launch vehicle, resulted in the Antares rocket exploding seconds after liftoff.[6]

Spacecraft

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Cygnus Orb-3 spacecraft integrated with Antares rocket

This would have been the third of eight flights by Orbital Sciences under the Commercial Resupply Services contract with NASA. This was the first attempted flight of the Antares 130, which uses a more powerful Castor 30XL second stage, and the last flight of the standard-sized Cygnus Pressurized Cargo Module.

In an Orbital Sciences tradition, this Cygnus spacecraft was named Deke Slayton after one of NASA's original Mercury Seven astronauts and Director of Flight Operations, who died in 1993.[7]

Launch and early operations

The mission was scheduled to launch on 27 October 2014 at 22:45 UTC from the Mid-Atlantic Regional Spaceport at the Wallops Flight Facility in Wallops Island, Virginia, with rendezvous and berthing with the ISS early in the morning on 2 November.[3] This was the first night-time launch for both the Antares launcher and Cygnus spacecraft.[3] The launch was scrubbed due to safety concerns of a sailboat entering the exclusion zone less than ten minutes before launch. A 24-hour delay was put in place, with the next launch opportunity scheduled for 22:22:38 UTC on 28 October 2014.

Launch failure

The Antares rocket carrying the Orb-3 Cygnus launched as scheduled from Launch Pad 0A on 28 October 2014. Fifteen seconds after liftoff a failure of propulsion occurred in the first stage. The vehicle began falling back to the launch pad and the Range Safety Officer engaged its flight termination system just before impact.[8][9]

The resulting explosion was felt in Pocomoke City, Maryland, 20 miles (32 km) away.[10] The fire at the site was quickly contained and allowed to burn itself out overnight.[6][11] Initial review of telemetry data found no abnormalities in the pre-launch, the launch sequence, and the flight, until the time of the failure.[8]

In a press release, NASA stated that there were no known issues prior to launch and that no personnel were injured or missing but that the entire payload was lost and there was significant damage to the launch pad.[12][13] On 29 October 2014, teams of investigators began examining debris at the crash site,[14] while a survey the same day found that there was no serious damage to the launch pad and site fuel tanks, although repairs would be required.[8][15]

Subsequent investigation found that the LOX turbopump had exploded, although a specific reason for the failure could not be determined. Possible causes were a defective pump bearing, ingestion of loose debris, or a manufacturing defect.[16]

Payload

Orb-3 carried a variety of NASA-manifested payloads, some determined fairly late in the days before the launch. The cargo module from the rocket carried 2,300 kilograms (5,000 lb) of supplies and experiments meant for the International Space Station.[14] In addition, the Arkyd-3 satellite would have been transported to the ISS on this flight.[17]

Flock-1d

Planet Labs was launching Flock-1d, its next flock of 26 Earth observation nanosatellites.[18] After the accident they stated that this would not set them back due to their approach to space involving many satellites in various constellations.[19]

Arkyd-3

Arkyd-3 was a 3U CubeSat technology demonstrator from private company Planetary Resources (PRI). PRI had packaged a number of the non-optical satellite technologies of its larger Arkyd-100 telescope satellite—essentially the entire base of the Arkyd-100 satellite model revealed in January 2013,[20] but without the space telescope—into a "cost-effective box" of Arkyd 3, or A3, for early in-space flight testing as a subscale nanosatellite. The Arkyd-3 testbed satellite was packaged as a 3U CubeSat form-factor of 10×10×30 centimetres (0.33×0.33×0.98 ft).[21] PRI contracted with NanoRacks to take the A3 to the ISS where it was planned to be released from the airlock in the Kibo module.[21][22]

The subsystems to be tested included the avionics, attitude determination and control system (both sensors and actuators), and integrated propulsion system that will enable proximity operations for the Arkyd line of prospectors in the future.[23]

This near-term attempt to validate and mature the Planetary Resources satellite technology was planned to launch in October 2014, before launch and flight test of the Arkyd-100 in 2015.[17]

Other payloads

CRS Orb-3 was carrying eighteen student experiments designed to investigate crystal formation, seed germination, plant growth, and other processes in microgravity as part of the Student Spaceflight Experiments Program.[24] It also carried the first open source ArduLab-powered student experiments.[25]

Two amateur radio CubeSats, RACE and GOMX-2, were on board, among other satellites. On board GOMX-2 were two payloads. One payload was a pathfinder experiment for the Small Photon-Entangling Quantum System [26] designed by the Centre for Quantum Technologies.[27] The other was a sail brake experiment to remove a CubeSat from orbit by increasing aerodynamic drag.[28]

Failure analysis and aftermath

With some preliminary investigation completed, Orbital cited the cause of the Orb-3 launch failure as likely being a turbopump failure in one of the AeroJet Rocketdyne AJ-26 engines, a refurbished Russian NK-33 engine.[29] A NASA report from the failure investigation was released in October 2015.[30][31]

As of January 2015, repairs to the Wallops Flight Facility are under way.[32] To meet its Commercial Resupply Services obligations with NASA, Orbital is planning to launch at least one Enhanced Cygnus cargo spacecraft via an Atlas V launch vehicle in 2015 while a new engine is selected and tested for the Antares launch vehicle. Orbital was conducting an evaluation and review of an AJ-26 replacement engine prior to the incident.[33] Orbital officially announced that the Energomash RD-181, the export version of the RD-191, would replace the AJ-26 on Antares. The Russians are using this same engine (RD-193), to replace the NK-33 engine used on Soyuz 2. The redesigned Antares launch vehicle is expected to fly again sometime in 2016.[34]

Manifest

Total cargo: 2,215 kg (4,883 lb)[35]

  • Science investigations: 727.0 kg (1,602.8 lb)
    • U.S. science: 569.0 kg (1,254.4 lb)
    • International partner science: 158.0 kg (348.3 lb)
  • Crew supplies: 748 kg (1,649 lb)
    • Equipment: 124.0 kg (273.4 lb)
    • Food: 617.0 kg (1,360.3 lb)
    • Flight procedure books: 7.0 kg (15.4 lb)
  • Vehicle hardware: 637.0 kg (1,404.3 lb)
    • U.S. hardware: 605.7 kg (1,335.4 lb)
    • JAXA hardware: 30.0 kg (66.1 lb)
  • Spacewalk equipment: 66.0 kg (145.5 lb)
  • Computer resources: 37.0 kg (81.6 lb)
    • Command & data handling equipment: 34 kg (75 lb)
    • Photography/TV equipment: 3.0 kg (6.6 lb)

Total cargo with packing material: 2,294 kg (5,057 lb)

Gallery

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 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. 6.0 6.1 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. 8.0 8.1 8.2 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. 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. 14.0 14.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  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. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Ling, Alexander. "Alexander Ling's Team Webpage"
  27. The Centre for Quantum Technologies
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.

External links