Mercury-Redstone 1

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Mercury-Redstone 1
Mercury Spacecraft at NASA Ames.JPG
Mercury spacecraft #2, used on both the MR-1 and MR-1A flights, on display at NASA Ames Exploration Center
Mission type Test flight
Operator NASA
Mission duration 2 seconds
Launch failure
Apogee 4 inches (10 cm)
Spacecraft properties
Spacecraft Mercury No.2
Manufacturer McDonnell Aircraft
Launch mass 1,230 kilograms (2,720 lb)[1][note 1]
Start of mission
Launch date November 21, 1960, 14:00 (1960-11-21UTC14Z) UTC
Rocket Redstone MRLV MR-1
Launch site Cape Canaveral LC-5

Mercury insignia.png


Project Mercury
Mercury-Redstone series
Mercury-Redstone 1A

Mercury-Redstone 1 (MR-1) was the first Mercury-Redstone unmanned flight test in the Mercury program and the first attempt to launch a Mercury spacecraft with the Mercury-Redstone launch vehicle. Intended to be an unmanned sub-orbital flight, it was launched on November 21, 1960 from Cape Canaveral, Florida. The launch failed in a peculiar fashion which has been referred to as the "four-inch flight".[2]

Test background and launch failure[edit]

The purpose of the MR-1 flight was to qualify the Mercury spacecraft and the Mercury-Redstone launch vehicle for the sub-orbital Mercury mission. It would also qualify the spacecraft's automated flight control and recovery systems, as well as the launch, tracking, and recovery operations on the ground.[3][4] The flight would also test the Mercury-Redstone's automatic inflight abort sensing system, which would be operating in "open-loop" mode. This meant that the abort sensing system could report a condition requiring an abort, but it would be unable to actually trigger an abort itself. Since the flight did not have a living passenger, this would not pose a safety problem, and it would prevent a faulty abort signal from prematurely ending the flight.[3]

The test used Mercury spacecraft #2 together with Redstone MR-1;[note 2] its launch location was Cape Canaveral Air Force Station's Launch Complex 5. An early launch attempt on November 7 was canceled due to last-minute problems with the capsule, so launching was rescheduled for November 21.[6][7]

On that day, following a normal countdown, the Mercury-Redstone's engine ignited on schedule at 9:00 a.m. Eastern Standard Time (14:00 GMT). However, the engine shut down immediately after lift-off from the launch pad. The rocket only rose about 4 inches (10 cm) before settling back onto the pad. It wobbled slightly, but stayed upright and did not explode. An odd series of events then took place.[4][6][8]

Immediately after the Redstone's engine shut down, the Mercury capsule's escape rocket jettisoned itself, leaving the capsule attached to the Redstone booster. The escape rocket rose to an altitude of 4,000 feet (1,200 m) and landed about 400 yards (370 m) away. Three seconds after the escape rocket fired, the capsule deployed its drogue parachute; it then deployed the main and reserve parachutes, ejecting the radio antenna fairing in the process.[4][6][8]

In the end, all that had been launched was the escape rocket. Meanwhile, a fully fueled, slightly wrinkled Redstone and its Mercury capsule sat on the launch pad, both with full batteries and live pyrotechnics. Among these pyrotechnics were the capsule's retrorockets and the Redstone's self-destruct system, which was still active. Furthermore, the capsule's main and reserve parachutes were hanging down the side of the rocket, threatening to tip it over if they caught enough wind. Fortunately, the weather conditions were favorable. Amid the panicked atmosphere in the control room, the launch team was unable to come up with quick and viable options to rectify the situation. Chris Kraft, the now-frustrated flight director rejected several unsafe interventions, including using rifle shots to puncture the Redstone's fuel and oxidizer tanks to depressurize them. He eventually took the advice of one of the test engineers to wait out the battery discharge and let the oxidizer boil off.[9] This early test failure and subsequent panic led Kraft to declare "That is the first rule of flight control. If you don't know what to do, don't do anything". Technicians therefore waited until the next morning, when the flight batteries in the rocket and capsule had run down and the Redstone's liquid oxygen had boiled off, before they could work on the rocket and render it safe.[6][10]

Causes of the failure[edit]

Investigation revealed that the Redstone's engine shutdown was caused by two of its electrical cables separating in the wrong order.[6] These cables were a control cable, which provided various control signals, and a power cable, which provided electrical power and grounding. Both cables were plugged into the rocket at the bottom edge of one of its tail fins and would separate at liftoff.[11] The control cable was supposed to separate first, followed by the power cable. However, for this launch, the control cable was longer than expected—it was one designed for the military Redstone missile rather than the shorter cable designed for Mercury-Redstone. This control cable had been clamped to compensate for its greater length, but when the vehicle lifted off, the clamping did not work as planned and the control cable separation was delayed, eventually occurring about 29 milliseconds after the power cable had separated.[4][12]

During this brief interval, the lack of electrical grounding caused a substantial current to flow through an electrical relay which was supposed to trigger normal engine cut-off at the end of powered flight. This relay tripped, causing the Redstone to shut off its engine and send a "normal cut-off" signal to the capsule. Under normal circumstances, when the capsule received this signal during a flight, it would do two things: it would jettison its escape rocket, which was no longer of any use, and after the escape rocket had flown clear, the capsule would separate itself from the expended Redstone. In the case of MR-1, the capsule did jettison the escape rocket as it was designed to, but the capsule did not separate itself from the Redstone. The capsule was designed to suspend this separation until the vehicle's acceleration had almost ceased, so that the capsule would not be hit by a still-accelerating launch vehicle. This would happen when the capsule's acceleration sensors detected an acceleration approaching 0 g, which it would normally experience after the Redstone had shut down and was entering free fall. However, in MR-1, the Redstone was not in free fall but rather sitting supported on the ground. Thus the capsule sensors detected the effect of their own supported weight, which they read as a constant "acceleration" of 1 g. Because of this apparent acceleration, capsule separation was disabled.[4][13]

The jettison of the escape rocket activated the capsule's parachute recovery system. Since the altitude was below 10,000 feet (3,000 m), this system was triggered by its atmospheric pressure sensors and followed its usual sequence, with the drogue parachute deploying first, followed by the main parachute. But because the main parachute was not supporting the capsule's weight, the parachute system did not detect any load on this chute, so it acted as if the chute had failed and deployed the reserve parachute.[4][13]

Since the Redstone's automatic inflight abort sensing system was running in open-loop mode, the engine shutdown did not trigger an abort. However, the system did report an abort condition, so it did function properly.[8][14]

Aftermath[edit]

The Redstone had suffered some minor damage from falling back on the pad, but it could still be used after refurbishment, so it was returned to Marshall Space Flight Center in Huntsville, Alabama, and was held in reserve. A new test flight was scheduled, Mercury-Redstone 1A (MR-1A), which would use a new Mercury-Redstone rocket, numbered MR-3. MR-1's Mercury spacecraft, #2, was undamaged, so it was reused for MR-1A, together with the escape rocket from spacecraft #8 and the antenna fairing from spacecraft #10.[4][15][16]

To prevent a failure like MR-1 from happening again, subsequent Mercury-Redstones added a grounding strap about 12 inches (30 cm) long to electrically connect the rocket to the launch pad. This strap was designed to separate from the rocket well after all other electrical connections to the ground had been severed.[4][13][16]

Mercury engineers were also concerned that MR-1's failure had allowed a "normal cutoff" signal to reach the capsule and trigger the premature jettisoning of the escape rocket, since in an actual emergency this would remove the only escape mechanism for the astronaut. Had MR-1 been a manned mission, the normal contingency would have been a pad abort, lifting the Mercury capsule off the booster and to safety via the escape rocket. Since the escape rocket had instead jettisoned itself from the capsule the astronaut would have been left in a very precarious situation, stuck inside the Mercury capsule atop a fully fueled, fully independently powered, yet completely untethered and partially damaged Redstone booster. To prevent a situation like this, the Mercury-Redstone was altered so that it could not send a "normal cutoff" signal to the capsule until 129.5 seconds after liftoff, about 10 seconds before the expected time of the Redstone's actual engine cutoff.[13][17]

MR-1 was never used for another flight after its return to Huntsville. It was eventually put on display at the Space Orientation Center of Marshall Space Flight Center.[14]

Current location[edit]

Mercury spacecraft #2, used in both the Mercury-Redstone 1 and Mercury-Redstone 1A flights, is currently displayed at the NASA Ames Exploration Center, Moffett Federal Airfield, near Mountain View, California.[18] A Mercury-Redstone rocket is currently on display at the U.S. Space & Rocket Center in Huntsville among other locations.

Images[edit]

Notes[edit]

  1. ^ This is the mass of the spacecraft after separation from the launch vehicle, including all spacecraft consumables. It excludes the escape tower, which would be jettisoned before spacecraft separation, and the spacecraft-launch vehicle adapter, which would remain attached to the launch vehicle. Note that Mercury spacecraft #2 lacked some of the equipment present in the spacecraft used on the manned Mercury flights.
  2. ^ NASA used the prefix "MR-" both for Mercury-Redstone flights and for launch vehicle numbers. Sometimes, as in this case, the flight and launch vehicle numbers were the same, but not always.[5] Some later sources use the prefix "MRLV-" for launch vehicle numbers, but this form does not seem to have been used by NASA.

References[edit]

 This article incorporates public domain material from websites or documents of the National Aeronautics and Space Administration.

  1. ^ Korando, R. D. (February 6, 1961). Mercury Capsule No. 2 Configuration Specification (Mercury-Redstone No. 1) (PDF). St. Louis, Missouri: McDonnell Aircraft Corporation. pp. 7–9. Report number NASA-CR-137390. 
  2. ^ "MR-1: The Four-Inch Flight", p. 293.
  3. ^ a b The Mercury-Redstone Project, p. 8-2.
  4. ^ a b c d e f g h NSSDC Master Catalog page.
  5. ^ The Mercury-Redstone Project, p. 6-3, 8-1.
  6. ^ a b c d e The Mercury-Redstone Project, p. 8-3.
  7. ^ "MR-1: The Four-Inch Flight", pp. 293-294.
  8. ^ a b c "MR-1: The Four-Inch Flight", p. 294.
  9. ^ Kranz, Gene (2000). Failure is not an Option. Simon and Schuster. 
  10. ^ "MR-1: The Four-Inch Flight", pp. 294-296.
  11. ^ The Mercury-Redstone Project, p. 4-6, 4-47.
  12. ^ The Mercury-Redstone Project, p. 8-3, 8-5.
  13. ^ a b c d The Mercury-Redstone Project, p. 8-5.
  14. ^ a b The Mercury-Redstone Project, p. 8-6.
  15. ^ The Mercury-Redstone Project, p. 8-5, 8-6.
  16. ^ a b "MR-1: The Four-Inch Flight", p. 296.
  17. ^ "MR-1: The Four-Inch Flight", p. 296-297.
  18. ^ "NASA Ames Exploration Center". NASA Ames Research Center. Retrieved 2009-05-14. 

External links[edit]