FANDOM


Template:Blacklisted-links Template:Infobox spaceflight

SpaceX CRS-1, also known as SpX-1,[1] was the third flight for Space Exploration Technologies Corporation's (SpaceX) uncrewed Dragon cargo spacecraft, the fourth overall flight for the company's two-stage Falcon 9 launch vehicle, and the first SpaceX operational mission under their Commercial Resupply Services contract with NASA. The launch occurred on 7 October 2012 at 20:34 EDT (8 October 2012 at 00:34 UTC).[2][3][4][5]

HistoryEdit

In May 2012, it was reported that the CRS-1 Falcon 9 had been transported to Cape Canaveral.[6] The CRS-1 Dragon later arrived on 14 August 2012.[7] On 31 August 2012, a wet dress rehearsal was completed for the CRS-1 Falcon 9, and on 29 September a static fire test was completed; both of these tests were completed without the Dragon capsule attached to the launch vehicle stack.[8][9] The mission passed its Launch Readiness Review on 5 October 2012.[5]

The launch occurred on 8 October 2012 (UTC) and successfully placed the Dragon spacecraft into the proper orbit for arriving at the International Space Station with cargo resupply several days later. During the launch, one of the nine engines suffered a sudden loss of pressure about 80 seconds into the flight, and an immediate early shutdown of that engine occurred; debris could be seen in the telescopic video of the night launch. The remaining eight engines fired for a longer period of time and the flight control software adjusted the trajectory to insert Dragon into a near flawless orbit.[10]

Mission timelineEdit

Dates are listed in UTC.

Flight day 1, launch (8 October)Edit

SpaceX CRS-1 launch cropped

The SpaceX CRS-1 Falcon 9 launches on 8 October 2012.

File:SpaceX CRS-1 Launch.ogv

The mission plan, as published by NASA before the mission, called for the Falcon 9 to reach supersonic speed at one minute, 10 seconds after liftoff, and pass through the area of maximum aerodynamic pressure, "max Q"—the point when mechanical stress on the rocket peaks due to a combination of the rocket's velocity and resistance created by the Earth's atmosphere—10 seconds later. The plan called for two of the first-stage engines to shut down to reduce the rocket's acceleration at approximately 2 minutes 30 seconds into the flight, when the Falcon 9 would nominally be 90 kilometers (56 miles) high and traveling at 10 times the speed of sound. The remaining engines were planned to cut off shortly after—an event known as main-engine cutoff (MECO). Five seconds after MECO, the first and second stages separate. Seven seconds later, the second stage's single Merlin vacuum engine was projected to ignite to begin a 6-minute, 14-second burn to put Dragon into low-Earth orbit. Forty seconds after second-stage ignition, Dragon's protective nose cone, which covers Dragon's berthing mechanism, was planned to be jettisoned. At the 9-minute, 14-second mark after launch, the second-stage engine was scheduled to cut off (SECO). Thirty-five seconds later, Dragon was planned to separate from Falcon 9's second stage and reach its preliminary orbit. Dragon would, per plan, then deploy its solar arrays and open its guidance and navigation control (GNC) bay door which holds the sensors necessary for rendezvous and Dragon's grapple fixture.[11]

Flight day 2 (9 October)Edit

The mission plan called for the Dragon spacecraft to perform a coelliptic burn that would place it in a circular coelliptic orbit.[11]

Flight day 3 (10 October)Edit

SpaceX CRS-1 approaches ISS-cropped

The SpaceX CRS-1 Dragon is seen approaching the ISS

As Dragon chased the International Space Station, the spacecraft established UHF communication using its COTS ultrahigh-frequency Communication unit (CUCU). Also, using the crew command panel (CCP) on board the station, the expedition crew monitored the approach. This ability for the crew to send commands to Dragon is important during the rendezvous and departure phases of the mission.[11]Template:Failed verification

During final approach to the station, a go/no-go was performed by Mission Control Houston and the SpaceX team in Hawthorne to allow Dragon to perform another engine burn that brought it 250 meters (820 feet) from the station. At this distance, Dragon began using its close-range guidance systems, composed of LIDAR and thermal imagers. These systems confirmed that Dragon's position and velocity are accurate by comparing the LIDAR image that Dragon receives against Dragon's thermal imagers. The Dragon flight control team in Hawthorne, with assistance from the NASA flight control team at the Johnson Space Center's International Space Station Flight Control Room, commanded the spacecraft to approach the station from its hold position. After another go/no-go was performed by the Houston and Hawthorne teams, Dragon was permitted to enter the keep-out sphere (KOS), an imaginary sphere drawn 200 meters (656 feet) around the station that reduces the risk of collision. Dragon proceeded to a position 30 meters (98 feet) from the station and was automatically held. Another go/no-go was completed. Then Dragon proceeded to the 10-meter (32 feet) position—the capture point. A final go/no-go was performed, and the Mission Control Houston team notified the crew they were go for capture of Dragon.[11]Template:Failed verification

At that point, Expedition 33 crew member Akihiko Hoshide of the Japan Aerospace Exploration Agency used the station's 17.6-meter (Template:Convert/LoffAonSon) robotic arm, known as Canadarm2, reached for and grappled the Dragon spacecraft at 10:56 UTC.[12] Hoshide, with the help of Expedition 33 Commander Sunita Williams of NASA, guided Dragon to the Earth-facing side of the station's Harmony module. Williams and Hoshide swapped places and Williams gently berthed Dragon to Harmony's Common Berthing Mechanism at 13:03 UTC.[12]

The opening of the hatch between Dragon and the Harmony module, which was originally not scheduled to occur until 11 October, was moved up and occurred at 17:40 UTC.[12]

Remainder of mission (11 to 28 October)Edit

SpX CRS-1 berthed - cropped

Dragon as seen from Cupola on 14 October 2012.

Over a period of two and a half weeks, the ISS crew unloaded Dragon's payload and reloaded it with cargo for return to Earth.[11]Template:Failed verification

After its mission at the orbital laboratory was completed, newly arrived Expedition 33 Flight Engineer Kevin Ford used the Canadarm2 robotic arm to detach Dragon from Harmony, maneuver it out to the 15-meter (50-foot) release point, and release the vehicle. Dragon then performed a series of three burns to place it on a trajectory away from the station. Approximately six hours after Dragon departed the station, it conducted a deorbit burn, which lasted up to 10 minutes. Dragon's trunk, which contains its solar arrays, was then jettisoned.[11]Template:Failed verification

SpX-1 Dragon at port.1

The SpX-1 capsule seen back at port on 30 October 2012.

The landing was controlled by automatic firing of its Draco thrusters during reentry.Template:Failed verification In a carefully timed sequence of events, dual drogue parachutes deploy at an altitude of 13,700 m (Template:Convert/round ft) to stabilize and slow the spacecraft. Full deployment of the drogues triggers the release of the three main parachutes, each 35 meters (116 feet) in diameter, at about 3,000 m (Template:Convert/round ft). While the drogues detach from the spacecraft, the main parachutes further slow the spacecraft's descent to approximately 4.8 to 5.4 meters per second (Template:Convert/round to Template:Convert/round ft/s). Even if Dragon were to lose one of its main parachutes, the two remaining chutes would still permit a safe landing. The Dragon capsule is expected to land in the Pacific Ocean, about 450 km (Template:Convert/round mi) off the coast of southern California. SpaceX uses a 100-foot boat equipped with an A-frame and an articulating crane, a 90-foot crew boat for telemetry operations, and two 24-foot rigid-hull inflatable boats to perform recovery operations. On board are approximately a dozen SpaceX engineers and technicians as well as a four-person dive team. Once the Dragon capsule splashed down, the recovery team secured the vehicle and then placed it on deck for the journey back to shore.Template:Failed verification[11]

SpaceX technicians will open the side hatch of the vehicle and retrieve these time-critical items. The critical cargo items will be placed on a fast-boat for the 450-Kilometer trip back to California for eventual return to NASA that will then take care of the precious science cargo and handle post-flight analysis of the samples.[13] The rest of the cargo will be unloaded once the Dragon capsule reaches SpaceX's test facility in McGregor, Texas.[14]

PayloadEdit

Spacex dragon nasa 694332main dragon readies full

Dragon readies for flight for the CRS-1 mission

Primary payloadEdit

When launched the CRS-1 Dragon was filled with about 1,995 lb (Template:Convert/round kg) of cargo, 882 lb (Template:Convert/round kg) without packaging.[11] Included is 260 lb (Template:Convert/round kg) of crew supplies, 390 lb (Template:Convert/round kg) of critical materials to support the 166 experiments on board the station and 66 new experiments, as well as 232 lb (Template:Convert/round kg) of hardware for the station as well as other miscellaneous items.[11]

The Dragon will return 1,995 lb (Template:Convert/round kg) of cargo, 1,673 lb (Template:Convert/round kg) without packaging.[11] Included is 163 lb (Template:Convert/round kg) of crew supplies, 866 lb (Template:Convert/round kg) of scientific experiments and experiment hardware, 518 lb (Template:Convert/round kg) of space station hardware, 68 lb (Template:Convert/round kg) of spacesuit equipment and 55 lb (Template:Convert/round kg) of miscellaneous items.[11]

Secondary payloadEdit

For some months prior to the launch, a 150 kg (Template:Convert/round lb) prototype second-generation Orbcomm satellite was planned to be launched as a secondary payload from Falcon 9's second stage.[15][16]

Although the secondary payload made it to the Dragon insertion orbit, an engine anomaly on one of the nine engines on the Falcon 9 first stage during the ascent resulted in automatic engine shutdown and a longer first-stage burn on the remaining eight engines to complete orbital insertion while subsequently increasing use of propellant over the nominal mission.

The primary payload contractor, NASA, requires a greater-than-99% estimated probability that the stage of any secondary payload on a similar orbital inclination to the International Space Station will reach their orbital altitude goal above the station. Due to the engine failure, the Falcon 9 used more propellant than intended, reducing the success probability estimate to approximately 95%. Because of this, the second stage did not attempt a second burn, and Orbcomm-G2 was left in an unusable orbit[17][18] and burned up in Earth's atmosphere within 4 days after the launch.[19][20]

Both SpaceX and Orbcomm were aware, prior to the mission, of the high risk that the secondary payload satellite could remain at the lower altitude of the Dragon insertion orbit, and that was a risk that Orbcomm agreed to take given the dramatically lower cost of launch for a secondary payload.[19]

Launch attemptsEdit

Template:LaunchAttempt

Falcon 9 engine anomalyEdit

During the ascent, an engine anomaly occurred with one of the nine engines on the Falcon 9 first stage. SpaceX has emphasized for several years that the Falcon 9 first stage is designed for "engine out" capability, with the capability to shut down one or more malfunctioning engines and still make a successful ascent.[21] In the event, the SpaceX CRS-1's first stage shut down engine no. 1, and as a result continued the first-stage burn on the remaining eight engines longer than usual at a somewhat reduced thrust to insert the Dragon spacecraft into the proper orbit.[22] SpaceX referred to the event as a "Rapid unscheduled disassembly"[23] which, although unintended, was the first inflight demonstration of Falcon 9's "engine out" design,[10][24] and "provides a clear demonstration of the engine out capability."[23][25]

In response to the anomaly, NASA and SpaceX jointly formed the CRS-1 Post-Flight Investigation Board.[26] Preliminary information from the post-flight review board indicates that the Engine no. 1 fuel dome, above the nozzle, ruptured but did not explode. The burning fuel that exited before the engine was shut down caused the fairing rupture, as seen in the flight video recordings.[27] Subsequent investigations revealed in a Congressional hearing pinpointed the issue as an result of an undetected material flaw in the engine chamber jacket, likely introduced during engine production. During flight, the data suggests this material flaw ultimately developed into a breach in the main combustion chamber. This breach released a jet of hot gas and fuel in the direction of the main fuel line causing a secondary leak and ultimately a rapid drop in engine pressure. As a result, the flight computer commanded shutdown of engine 1 and Falcon 9 continued on its path to ensure Dragon’s entry into orbit for subsequent rendezvous and berthing with the ISS.[28]

GalleryEdit

ReferencesEdit

  1. Cite error: Invalid <ref> tag; no text was provided for refs named HARTMAN
  2. Cite error: Invalid <ref> tag; no text was provided for refs named NASA_EH
  3. Cite error: Invalid <ref> tag; no text was provided for refs named NASAsept20
  4. Template:Cite news
  5. 5.0 5.1 Clark, Stephen (5 October 2012). "Commercial resupply of space station blasts off Sunday". SpaceFlightNow. http://www.spaceflightnow.com/falcon9/004/121005preview/. Retrieved 6 October 2012. 
  6. Cite error: Invalid <ref> tag; no text was provided for refs named Clark_18_May_2012
  7. Cite error: Invalid <ref> tag; no text was provided for refs named Clark_24_August_2012
  8. Cite error: Invalid <ref> tag; no text was provided for refs named AugustChris
  9. Cite error: Invalid <ref> tag; no text was provided for refs named Sept29
  10. 10.0 10.1 Template:Cite news
  11. Cite error: Invalid <ref> tag; no text was provided for refs named Presskit
  12. Cite error: Invalid <ref> tag; no text was provided for refs named SPACENOW10
  13. "Dragon CRS-1 Mission Updates". SPACEFLIGHT101. http://www.spaceflight101.com/dragon-crs-1-mission-updates.html. Retrieved 2013-10-08. 
  14. "Dragon Mission Report | Return of the Dragon: Commercial craft back home". Spaceflight Now. http://spaceflightnow.com/falcon9/004/121028splashdown/. Retrieved 2013-10-08. 
  15. Cite error: Invalid <ref> tag; no text was provided for refs named Orbcomm_25_May_2012
  16. Cite error: Invalid <ref> tag; no text was provided for refs named Hartman_23_July_2012
  17. Clark, Stephen (11 October 2012). "Orbcomm craft falls to Earth, company claims total loss". Spaceflight Now. http://www.spaceflightnow.com/falcon9/004/121011orbcomm/. Retrieved 11 October 2012. 
  18. Template:Cite news
  19. 19.0 19.1 Template:Cite news
  20. Orbcomm craft falls to Earth, company claims total loss
  21. Template:Cite news
  22. Template:Cite news
  23. 23.0 23.1 Template:Cite news
  24. Template:Cite news
  25. Template:Cite news
  26. Template:Cite news
  27. Template:Cite news
  28. "SpaceX: Engine Anomaly Overview". Aviationweek.com. http://aviationweek.com/blog/spacex-engine-anomaly-overview. Retrieved 2013-10-08. 

External linksEdit

Template:Dragon spaceflights

Template:Unmanned ISS resupply flights

This page uses Creative Commons Licensed content from Wikipedia (view authors). Smallwikipedialogo.png
Community content is available under CC-BY-SA unless otherwise noted.