An Atlas D LV-3B launching Mercury-Atlas 6
|Function||Crewed expendable launch system|
|Country of origin||United States|
|Height||28.7 metres (94.3 ft)|
|Diameter||3.0 metres (10.0 ft)|
width over boost fairing 4.9 metres (16 ft)
|Mass||120,000 kilograms (260,000 lb)|
|Payload to LEO||1,360 kilograms (3,000 lb)|
|Launch sites||CCAFS LC-14|
|First flight||29 July 1960|
|Last flight||15 May 1963|
|Engines||2 Rocketdyne XLR-89-5|
|Thrust||1,517.4 kilonewtons (341,130 lbf)|
|Burn time||135 seconds|
|Diameter||3.0 metres (10.0 ft)|
|Engines||1 Rocketdyne XLR-105-5|
|Thrust||363.22 kilonewtons (81,655 lbf)|
|Burn time||5 minutes|
The Atlas LV-3B, Atlas D Mercury Launch Vehicle or Mercury-Atlas Launch Vehicle, was a man-rated expendable launch system used as part of the United States Project Mercury to send astronauts into low Earth orbit. Manufactured by American aircraft manufacturing company Convair, it was derived from the SM-65D Atlas missile, and was a member of the Atlas family of rockets.
The Atlas D missile was the natural choice for Project Mercury since it was the only launch vehicle in the US arsenal that could put the spacecraft into orbit and also had a large number of flights from which to gather data. But its reliability was far from perfect and Atlas launches ending in explosions were an all-too common sight at Cape Canaveral. The Atlas had also been originally designed as a weapon system, thus its design and reliability did not need to necessarily be 100% perfect. As such, significant steps had to be taken to human-rate the missile and make it safe and reliable unless NASA wished to spend several years developing a dedicated launch vehicle for crewed programs or else wait for the next-generation Titan II ICBM to become operational. Atlas's stage-and-a-half configuration was seen as preferable to the two stage Titan in that all engines were ignited at liftoff, making it easier to test for hardware problems during prelaunch checks.
Shortly after being chosen for the program in early 1959, the Mercury astronauts were taken to watch the second D-series Atlas test, which exploded a minute into launch. This was the fifth straight complete or partial Atlas failure and the booster was at this point nowhere near reliable enough to carry a nuclear warhead or an uncrewed satellite, let alone a human passenger. Plans to human-rate Atlas were effectively still on the drawing board and Convair estimated that 75% reliability would be achieved by early 1961 and 85% reliability by the end of the year. Despite the Atlas's developmental problems, NASA had the benefit of conducting Project Mercury simultaneously with the Atlas R&D program which gave plenty of test flights to draw data from as well as test modified equipment for Mercury.
- 1 Quality assurance
- 2 Systems modified
- 3 Launches
- 4 Mercury-Atlas vehicles built and eventual disposition
- 5 See also
- 6 References
Aside from the modifications described below, Convair set aside a separate assembly line dedicated to Mercury-Atlas vehicles which was staffed by personnel who received special orientation and training on the importance of the crewed space program and the need for as high a degree of top-quality workmanship as possible. Components used in the Mercury-Atlas vehicles were given thorough testing to ensure proper manufacturing quality and operating condition, in addition components and subsystems with excessive operating hours, out-of-specification performance, and questionable inspection records would be rejected. All components approved for the Mercury program were earmarked and stored separately from hardware intended for other Atlas programs and special handling procedures were done to protect them from damage. The factory inspection of Mercury vehicles was performed by Convair personnel specially chosen for their experience, familiarity with the Atlas hardware, and who had demonstrated a favorable disposition and work ethic.
Propulsion systems used for the Mercury vehicles would be limited to standard D-series Atlas models of the Rocketdyne MA-2 engines which had been tested and found to have performance parameters closely matching NASA's specifications. NASA decided that the best choice of engines would be units with roughly medium-tier performance. Engines with higher than average performance were not considered acceptable because nobody could determine exactly why a given set of engines performed the way it did, and so it was considered safest to use medium-performance ones.
For the most part, NASA preferred to stay conservative with the Mercury vehicles and avoid modifying them any more than necessary. Modifications to the Atlas would largely be limited to those that improved pilot safety and the standard D-series Atlas configuration was to be retained as much as possible, so assorted enhancements made to the latest Atlas missiles would not be used. Various equipment and procedures used with Mercury vehicles, although outdated and often not the best or latest, were preferred because they were proven and well-understood. Any new equipment or hardware changes made to Mercury vehicles had to be flown on at least three Atlas R&D tests before NASA would approve them for use. Despite the conservatism and caution taken with the design of Mercury vehicles, a huge number of changes nonetheless did take place over the 4-1/2 years of the program from lessons learned and the emphasis on quality control got tighter as time went along; the last two Mercury flights were given a level of testing and preflight inspection that was unheard of when Big Joe flew in 1959.
All launch vehicles would have to be complete and fully flight-ready at delivery to Cape Canaveral with no missing components or unscheduled modifications/upgrades. After delivery, a comprehensive inspection of the booster would be undertaken and prior to launch, a flight review board would convene to approve each booster as flight-ready. The review board would conduct an overview of all prelaunch checks, and hardware repairs/modifications. In addition, Atlas flights over the past few months in both NASA and Air Force programs would be reviewed to make sure no failures occurred involving any components or procedures relevant to Project Mercury.
The NASA Quality Assurance Program meant that each Mercury-Atlas vehicle took twice as long to manufacture and assemble as an Atlas designed for uncrewed missions and three times as long to test and verify for flight.
Central to these efforts was the development of the Abort Sensing and Implementation System (ASIS), which would detect malfunctions in the Atlas's various components and trigger a launch abort if necessary. Added redundancy was built in; if ASIS itself failed, the loss of power would also trigger an abort. The system was tested on a few Atlas ICBM flights prior to Mercury-Atlas 1 in July 1960, where it was operated open-loop (MA-3 in April 1961 would be the first closed-loop flight).
The Mercury launch escape system (LES) used on Redstone and Atlas launches was identical, but the ASIS system varied considerably between the two boosters as Atlas was a much larger, more complex vehicle with five engines, two of which were jettisoned during flight, a more sophisticated guidance system, and inflated balloon tanks that required constant pressure to not collapse.
Atlas flight test data was used to draw up a list of the most likely failure modes for the D-series vehicles, however simplicity reasons dictated that only a limited number of booster parameters could be monitored. An abort could be triggered by the following conditions, all of which could be indicative of a catastrophic failure:
- The booster flight path deviated too far from the planned trajectory
- Engine thrust or hydraulic pressure dropped below a certain level
- Propellant tank pressure dropped below a certain level
- The intermediate tank bulkhead showed signs of losing structural integrity
- The booster electrical system ceased operating
- The ASIS system ceased operating
The ASIS system was deemed necessary because some flight failures of Atlas vehicles (for instance, Atlas 6B) occurred so fast that it would be nearly impossible for the astronaut to react in time manually activate the LES. Other failure modes such as a deviation from the correct flight trajectory did not necessarily pose an immediately danger to the astronaut's safety, and the flight could be aborted manually.
The rate gyro package was placed much closer to the forward section of the LOX tank due to the Mercury/LES combination being considerably longer than a warhead and thus producing different aerodynamic characteristics (the standard Atlas D gyro package was still retained on the vehicle for the use of the ASIS). Mercury-Atlas 5 also added a new reliability feature—motion sensors to ensure proper operation of the gyroscopes prior to launch. This idea had originally been conceived when the first Atlas B launch in 1958 went out of control and destroyed itself after being launched with a non-functioning yaw gyro, but it was phased into Atlas vehicles only gradually. One other Atlas missile test in 1961 also destroyed itself during launch, in that case because the gyroscope motor speed was too low. The motion sensors would thus eliminate this failure mode.
The range safety system was also modified for the Mercury program. There would be a three-second delay between engine cutoff and activation of the destruct charges so as to give the LES time to pull the capsule to safety. More specifically, if the Range Safety destruct command was sent, the ASIS system would allow the engine cutoff signal to go through, while blocking the destruct signal for three seconds. The decrease in engine performance would then be sensed by the ASIS, which would activate the LES, after which the destruct signal would be unblocked and destroy the launch vehicle. The ASIS system also could not terminate engine thrust for the first 30 seconds of flight in order to prevent a malfunctioning launch vehicle from coming down on or around the pad area; during this time only the Range Safety Officer could send a manual cutoff command.
D-series Atlas missiles carried the old-fashioned electromechanical autopilot (known as the "round" autopilot due to the shape of the containers its major components were housed in), but on Mercury vehicles, it was decided to use the newer transistorized "square" autopilot developed for the E and F-series missiles. The first three Mercury-Atlas vehicles still had the round autopilot and it was flown for the first time on Mercury-Atlas 3, but failed disastrously when the booster did not perform the programmed pitchover maneuver and had to be destroyed by Range Safety action. Afterwards, the missile programmer was recovered and examined. While the exact cause of the failure was not identified, several causes were proposed and a number of modifications made to the programmer. On Mercury-Atlas 4, high vibration levels in flight resulted in more modifications and it finally worked perfectly on Mercury-Atlas 5.
The guidance antenna was modified to reduce signal interference.
LOX boil-off valve
Mercury-Atlas vehicles utilized the boil-off valve from the C-series Atlas rather than the standard D-series valve for reliability and weight-saving reasons.
Combustion instability was an important problem that needed to be fixed. Although it mostly only occurred in static firing tests of the MA-2 engines, three launches (Missiles 3D, 51D, and 48D) had demonstrated that unstable thrust in one engine could result in immediate, catastrophic failure of the entire missile as the engine backfired and ruptured, leading to a thrust section fire. On Missile 3D, this had occurred in flight after a propellant leak starved one booster engine of LOX and led to reduced, unstable thrust and engine failure. The other two launches suffered rough combustion at engine start, ending in explosions that severely damaged the launch stand. Thus, it was decided to install extra sensors in the engines to monitor combustion levels and the booster would also be held down on the pad for a few moments after ignition to ensure smooth thrust. The engines would also use a "wet start", meaning that the engine tubes would contain an inert fluid to act as a shock damper (51D and 48D had both used dry starts, with no fluid in the engine tubes). If the booster failed the check, it would be automatically shut down. Once again, these upgrades required testing on Atlas R&D flights. By late 1961, after a third missile (27E) had exploded on the pad from combustion instability, Convair developed a significantly upgraded propulsion system that featured baffled fuel injectors and a hypergolic igniter in place of the pyrotechnic method, but NASA were unwilling to jeopardize John Glenn's upcoming flight with these untested modifications and so declined to have them installed in Mercury-Atlas 6's booster. As such, that and Scott Carpenter's flight on MA-7 used the old-style Atlas propulsion system and the new variant was not employed until Wally Schirra's flight late in 1962.
Static testing of Rocketdyne engines had produced high-frequency combustion instability, in what was known as the "racetrack" effect where burning propellant would swirl around the injector head, eventually destroying it from shock waves. On the launches of Atlas 51D and 48D, the failures were caused by low-order rough combustion that ruptured the injector head and LOX dome, causing a thrust section fire that led to eventual complete loss of the missile. The exact reason for the back-to-back combustion instability failures on 51D and 48D was not determined with certainty, although several causes were proposed. This problem was resolved by installing baffles in the injector head to break up swirling propellant, at the expense of some performance as the baffles added additional weight and reduced the number of injector holes that the propellants were sprayed through. The lessons learned with the Atlas program later proved vital to the development of the much larger Saturn F-1 engine.
Added redundancy was made to the propulsion system electrical circuitry to ensure that SECO would occur on time and when commanded. The LOX fuel feed system received added wiring redundancy to ensure that the propellant valves would open in the proper sequence during engine start.
Mercury vehicles up to MA-6 had foam insulation in the intermediate bulkhead to prevent the super-chilled LOX from causing the RP-1 to freeze. During repairs to MA-6 prior to John Glenn's flight, it was decided to remove the insulation for being unnecessary and an impediment during servicing of the boosters in the field. NASA sent out a memo to GD/A requesting that subsequent Mercury-Atlas vehicles not include bulkhead insulation.
In early 1962, two static engine tests and one launch (Missile 11F) fell victim to LOX turbopump explosions caused by the impeller blades rubbing against the metal casing of the pump and creating a friction spark. This happened after over three years of Atlas flights without any turbopump issues and it was not clear why the rubbing occurred, but all episodes of this happened when the sustainer inlet valve was moving to the flight-ready "open" position and while running untested hardware modifications. A plastic liner was added to the LOX turbopump to prevent friction rubbing. In addition Atlas 113D, the booster used for Wally Schirra's flight, was given a PFRT (Pre-Flight Readiness Test) to verify proper functionality of the propulsion system.
Mercury vehicles used a standard D-series Atlas pneumatic system, although studies were conducted over the cause of tank pressure fluctuation which was known to occur under certain payload conditions. These studies found that the helium regulator used on early D-series vehicles had a tendency to induce resonant vibration during launch, but several modifications to the pneumatic system had been made since then, including the use of a newer model regulator that did not produce this effect.
Propellant utilization system
In the event that the guidance system failed to issue the discreet cutoff command to the sustainer engine and it burned to propellant depletion, there was the possibility of a LOX-rich shutdown which could result in damage to engine components from high temperatures. For safety reasons, the PU system was modified to increase the LOX flow to the sustainer engine ten seconds before SECO. This was to ensure that the LOX supply would be completely exhausted at SECO and prevent a LOX-rich shutdown.
After MA-1 was destroyed in-flight due to a structural failure, NASA began requesting that Convair deliver Atlases with thicker skin. Atlas 10D (as well as its backup vehicle 20D which was later used for the first Atlas-Able flight), the booster used for the Big Joe test in September 1959, had sported thick skin and verified that this was needed for the heavy Mercury capsule. Atlas 100D would be the first thick-skinned booster delivered while in the meantime, MA-2's booster (67D) which was still a thin-skinned model, had to be equipped with a steel reinforcement band at the interface between the capsule and the booster. Under original plans, Atlas 77D was to have been the booster used for MA-3. It received its factory rollout inspection in September 1960, but shortly afterwards, the postflight findings for MA-1 came out which led to the thin-skinned 77D being recalled and replaced by 100D.
The vernier solo phase, which would be used on ICBMs to fine-tune the missile velocity after sustainer cutoff, was eliminated from the guidance program in the interest of simplicity as well as improved performance and lift capacity. Since orbital flights required an extremely different flight path from missiles, the guidance antennas had to be completely redesigned to ensure maximum signal strength. The posigrade rocket motors on the top of the Atlas, designed to push the spent missile away from the warhead, were moved to the Mercury capsule itself. This also necessitated adding a fiberglass insulation shield to the LOX tank dome so it wouldn't be ruptured by the rocket motors.
A common and normally harmless phenomenon on Atlas vehicles was the tendency of the booster to develop a slight roll in the first few seconds following liftoff due to the autopilot not kicking in yet. On a few flights however, the booster developed enough rolling motion to potentially trigger an abort condition if it had been a crewed launch. Although some roll was naturally imparted by the Atlas's turbine exhaust, this could not account for the entire problem which instead had more to do with engine alignment. Acceptance data from the engine supplier (Rocketdyne) showed that a group of 81 engines had an average roll movement in the same direction of approximately the same magnitude as that experienced in flight. Although the acceptance test-stand and flight-experience data on individual engines did not correlate, it was determined that offsetting the alignment of the booster engines could counteract this roll motion and minimize the roll tendency at liftoff. After Schirra's Mercury flight did experience momentary roll problems early in the launch, the change was incorporated into Gordon Cooper's booster on MA-9.
Nine LV-3Bs were launched, two on uncrewed suborbital test flights, three on uncrewed orbital test flights, and four with crewed Mercury spacecraft. Atlas LV-3B launches were conducted from Launch Complex 14 at Cape Canaveral Air Force Station, Florida.
It first flew on 29 July 1960, conducting the suborbital Mercury-Atlas 1 test flight. The rocket suffered a structural failure shortly after launch, and as a result failed to place the spacecraft onto its intended trajectory. In addition to the maiden flight, the first orbital launch, Mercury-Atlas 3 also failed. This failure was due to a problem with the guidance system failing to execute pitch and roll commands, necessitating that the Range Safety Officer destroy the vehicle. The spacecraft separated by means of its launch escape system and was recovered 1.8 kilometres (1.1 mi) from the launch pad.
A further series of Mercury launches was planned, which would have used additional LV-3Bs; however these flights were canceled after the success of the initial Mercury missions. The last LV-3B launch was conducted on 15 May 1963, for the launch of Mercury-Atlas 9. NASA originally planned to use leftover LV-3B vehicles to launch Gemini-Agena Target Vehicles, however an increase in funding during 1964 meant that the agency could afford to buy brand-new Atlas SLV-3 vehicles instead, so the idea was scrapped.
Mercury-Atlas vehicles built and eventual disposition
- 10D—Launched Big Joe 9/9/59
- 20D—Backup vehicle for Big Joe. Reassigned to Atlas-Able program and launched 11/26/59.
- 50D—Launched Mercury-Atlas 1 7/29/60
- 67D—Launched Mercury-Atlas 2 2/21/61
- 77D—Original launch vehicle for Mercury-Atlas 3, replaced by Atlas 100D after postflight findings from Mercury-Atlas 1
- 88D—Launched Mercury-Atlas 4 9/13/61
- 93D—Launched Mercury-Atlas 5 11/29/61
- 100D—Launched Mercury-Atlas 3 4/25/61
- 107D—Launched Aurora 7 (Mercury-Atlas 7) 5/24/62
- 109D—Launched Friendship 7 (Mercury-Atlas 6) 2/21/62
- 113D—Launched Sigma 7 (Mercury-Atlas 8) 10/3/62
- 130D—Launched Faith 7 (Mercury-Atlas 9) 5/15/63
- 144D—Cancelled, was planned launch vehicle for Mercury-Atlas 10