SpaceX CRS-2

From Infogalactic: the planetary knowledge core
(Redirected from Falcon 9 Flight 5)
Jump to: navigation, search
SpaceX CRS-2
File:SpX CRS-2 berthing.jpg
The Dragon spacecraft being berthed to Harmony on March 3, 2013
Mission type ISS resupply
Operator SpaceX/NASA
COSPAR ID 2013-010A
SATCAT № 39115
Mission duration 25 days
Spacecraft properties
Spacecraft type Dragon
Manufacturer SpaceX
Start of mission
Launch date March 1, 2013, 15:10 (2013-03-01UTC15:10) UTC[1]
Rocket Falcon 9 v1.0
Launch site Cape Canaveral SLC-40[1][2]
Contractor SpaceX
End of mission
Disposal Recovered
Landing date March 26, 2013, 16:34 (2013-03-26UTC16:35Z) UTC[3]
Orbital parameters
Reference system Geocentric
Regime Low Earth
Perigee 212 km (132 mi)
Apogee 326 km (203 mi)
Inclination 51.66 degrees
Period 89.76 minutes
Epoch March 1, 2013, 16:55:51 UTC[4]
Berthing at ISS
Berthing port Harmony nadir
RMS capture March 3, 2013, 10:31 UTC
Berthing date March 3, 2013, 13:56 UTC[5]
Unberthing date March 26, 2013, 08:10 UTC[3]
RMS release March 26, 2013, 10:56 UTC
Time berthed 22 days, 18 hours, 14 minutes
Cargo
Mass 677 kg (1,493 lb)
Pressurised 677 kg (1,493 lb)
File:SpaceX CRS-2.png
Commercial Resupply Services
← SpaceX CRS-1 SpaceX CRS-3

SpaceX CRS-2, also known as SpX-2,[6] was the fourth flight for SpaceX's uncrewed Dragon cargo spacecraft, the fifth and final flight for the company's two-stage Falcon 9 v1.0 launch vehicle, and the second SpaceX operational mission contracted to NASA under a Commercial Resupply Services contract.

The launch occurred on March 1, 2013.[1] A minor technical issue on the Dragon spacecraft involving the RCS thruster pods occurred upon reaching orbit, but it was recoverable.[7] The vehicle was released from the station on March 26, 2013, at 10:56 UTC and splashed down in the Pacific Ocean at 16:34 UTC.[3]

History

The SpaceX CRS-2 Falcon 9 launching on March 1, 2013

The planned shipment of the Falcon 9 first stage from Texas to the Florida launch site was delayed due to the ongoing investigation of the engine failure that occurred on the previous flight.[8] In late November 2012, it was reported that the CRS-2 Falcon 9 had been transported to Cape Canaveral.[9] A static fire test occurred for the CRS-2 Falcon 9 on February 25, 2013.[10]

Firsts

The Dragon unpressurized trunk section, which allows the transport of unpressurized cargo to the ISS, had its first use on this flight.[11] This cargo consisted of two Heat Rejection Subsystem Grapple Fixtures (HRSGFs), which are essentially bars to be attached to the ISS radiators to allow for future movement work.

Payload

When launched the CRS-2 Dragon was filled with about 1,493 lb (677 kg) of cargo, 1,268 lb (575 kg) without packaging.[12] Included is 178 lb (81 kg) of crew supplies, 766 lb (347 kg) of scientific experiments and experiment hardware, 298 lb (135 kg) of hardware for the station and other miscellaneous items,[12] among them a CD copy of the song "Up in the Air" by rock band Thirty Seconds to Mars, was premiered on board the International Space Station on March 18, 2013, during a NASA TV broadcast from the station.[13] The two Heat Rejection Subsystem Grapple Fixtures (HRSGFs) had a combined weight of 487 lb (221 kg) and were transported to the ISS inside the unpressurized Dragon trunk as external cargo.[14]

The Dragon returned 3,020 lb (1,370 kg) of cargo, 2,668 lb (1,210 kg) without packaging.[12] Included is 210 lb (95 kg) of crew supplies, 1,455 lb (660 kg) of scientific experiments and experiment hardware, 884 lb (401 kg) of space station hardware, 84 lb (38 kg) of spacesuit equipment and other miscellaneous items.[12]

Dragon thruster pods anomaly

Shortly after second stage separation, at 15:45 UTC on March 1, 2013, the Dragon spacecraft encountered technical problems involving its Propulsion System. "When priming its four Draco Thruster Pods, the vehicle detected insufficient pressurization on the oxidizer (Nitrogen Tetroxide) system" of three of the pods which "caused the Flight Computers to place the vehicle in Passive Abort Mode." In this mode, Dragon is not executing any more orbital operations. Its thruster system was disabled and the solar arrays were not deployed since the vehicle had not achieved its proper solar array deployment attitude. "Dragon is programmed not to open its arrays outside its proper attitude configuration to avoid contact with the second stage. This rule is in place for scenarios in which Dragon is not properly separated from the Falcon 9 Booster. As time progressed, teams working at SpaceX Mission Control, MCC-X in Hawthorne, California, started assessments of the issue."[15]

During the early minutes and hours of the mission, the mission progress news came in bits, some of it over social media. An update from Elon Musk on Twitter clarified:

"Issue with Dragon thruster pods. System inhibiting three of four from initializing. About to command inhibit override."[16]

At 16:12 UTC, Elon Musk announced that a "command inhibit override" would be issued as the Dragon module was "about to pass over Australia ground station."[17]

Initially solar array deployment was held "until at least two thruster pods are active."[18] SpaceX Mission Control decided to proceed with solar deployment due to array temperatures while the spacecraft was not in active attitude control[15] at 16:40 UTC: "Thruster pod 3 tank pressure trending positive. Preparing to deploy solar arrays."[19] At 16:50 UTC, solar arrays had successfully been deployed on the Dragon spacecraft.[20]

Three of the four thruster pods on the Dragon spacecraft must be operational for berthing to be allowed with the International Space Station. After making corrections, SpaceX regained control of all four thruster pods and would be able to correct its course to the ISS. According to Elon Musk, "All systems green."[21] NASA officials said that the spacecraft would not rendezvous with the ISS on March 2 as was originally planned. It would instead rendezvous on March 3.[5][22]

Dragon was grappled with Canadarm2 by NASA Expedition 34 commander Kevin Ford and NASA flight engineer Tom Marshburn at 10:31 UTC on March 3, and was berthed to the nadir (Earth-facing) docking port of the Harmony module at 13:56 UTC.[23]

Remainder of mission (March 3 to 26)

File:SpaceX CRS-2 capsule at docks.1.jpg
The Dragon capsule after being transported to shore on March 27, 2013

On March 6, 2013, the space station's Canadarm2 removed the grapple bars from Dragon's trunk. This event marked the first delivery of unpressurized cargo from a commercial spacecraft to the ISS.[24]

The spacecraft's return to Earth was postponed to March 26 from its originally scheduled date of March 25 due to inclement weather developing near its targeted splashdown site in the Pacific Ocean. The additional day spent attached to the orbiting laboratory did not affect science samples scheduled to return aboard the spacecraft.[25][26]

On March 26, Dragon was unberthed from the Harmony node by the Canadarm2 at 08:10 UTC by commands from ground controllers. Its release from Canadarm2 occurred at 10:56 UTC; the Expedition 35 crew then commanded the spacecraft to slowly depart from the International Space Station. The SpaceX Dragon fired its engines for the last time at 15:42 UTC sending it through the Earth's atmosphere for a splashdown in the Pacific Ocean at 16:34 UTC. A team of SpaceX engineers, technicians and divers recovered the vehicle and its scientific cargo off the coast of Baja, California, for the journey back to shore which took about 30 hours.[3]

References

  1. 1.0 1.1 1.2 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 3.3 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. 5.0 5.1 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.[full citation needed]
  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. 12.0 12.1 12.2 12.3 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. 15.0 15.1 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. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.

External links