Project Mercury · NASA · Uncrewed
Mercury-Atlas 3
- Apr 25, 1961, 4:15 PM
- Launch date
- 7 min
- Duration
- Failure
- Outcome
%2C_mechanical_astronaut_flight_attempt.jpg)
.jpg)
Mercury-Atlas 3 (MA-3) was the third attempt to fly a Mercury capsule on an Atlas, and the first framed as a quick test of the spacecraft-and-launcher combination in orbit. It lifted off from Launch Complex 14 at Cape Canaveral on 25 April 1961 at 16:15 UTC with no one aboard but a "mechanical astronaut", a crewman simulator installed in the pilot's place. The flight used Mercury spacecraft No. 8 and Atlas 100-D. This was the rehearsal still owed before a crewed orbital flight. The capsule had already shown, through the Little Joe aborts and through Mercury-Atlas 2, that it could survive an abort and a reentry; what remained unproven was the Atlas as a vehicle fit to carry people, after Mercury-Atlas 1 had broken up during ascent. Vehicle 100-D was the first Atlas delivered to the programme with the thickened liquid-oxygen tank skin adopted after that loss, it introduced a transistorised telemetry unit adapted from the Atlas-Centaur, and it was the first Mercury-Atlas to fly with the abort sensing system operating closed-loop and with a live escape tower. The ascent lasted less than a minute. At around twenty seconds the pitch-and-roll programme that should have tilted the trajectory out over the Atlantic failed to start, and the rocket kept climbing vertically above the Cape itself. The range safety officer allowed a few seconds for a recovery that never came and sent the destruct command: NASA places it forty seconds after liftoff, while flight director Gene Kranz's account puts it at forty-three. The escape tower fired at the moment of destruction and pulled spacecraft No. 8 clear of the debris. The capsule reached an apogee of 7.2 kilometres, came down only 1.8 kilometres downrange after a flight of 7 minutes and 19 seconds — most of it under the parachute — and was recovered from the Atlantic some twenty minutes after liftoff by a United States Marine Corps CH-37 helicopter. The launcher's failure thus became, without anyone planning it, the first real demonstration of the escape system on a Mercury-Atlas flight. The investigation pointed at the guidance system without ever closing the case: the missile programmer appeared to have shut down or restarted just after liftoff and never executed the sequence. Two months later it turned up buried in mud on a beach near the pad, and its examination exposed several serious design flaws that had to be put right. The recovered capsule was refitted as spacecraft No. 8A and flew on 13 September 1961 as Mercury-Atlas 4, the first Mercury spacecraft to reach Earth orbit.
Payload
The payload of MA-3 was the Mercury spacecraft itself, capsule No. 8, fitted out as for a crewed orbital flight but with nobody aboard: inside rode a mechanical crewman simulator — the “mechanical astronaut” — together with the normal equipment of an orbital mission, and NASA listed the flight’s crew as “unmanned, robot operations”. There was no animal and no biological experiment on board, unlike MR-2 with Ham or the later MA-5 with Enos. Spacecraft No. 8 had been delivered to the launch site on 18 November 1960 and spent twenty-three weeks in preparation before the launch of 25 April 1961; the Wikipedia infobox gives it a launch mass of 1,179 kg. It flew on Atlas No. 100-D and, for the first time on a Mercury-Atlas, with a live escape tower: Big Joe and MA-1 had flown with no tower and MA-2 with a dummy one. NASA stated the mission objective as a quick test of the spacecraft/Atlas combination in orbit. When the mission ended 43 seconds after lift-off with the destruction of the launch vehicle, that tower fired and carried the capsule to an apogee of 7.2 km and only 1.8 km downrange; the spacecraft’s own flight lasted 7 minutes and 19 seconds, and a US Marine CH-37 helicopter recovered it from the Atlantic some twenty minutes after launch. Refurbished as spacecraft No. 8A, it flew again on Mercury-Atlas 4. The programme appendix of test objectives does not list those for MA-3.
History
Why the flight was needed
By the time MA-3 reached the pad, Project Mercury had solved half of its problem and still owed the other half. The capsule had come through the Little Joe abort flights, the beach abort test and Mercury-Atlas 2, which in February 1961 had demonstrated the integrity of the structure, the ablation shield and the afterbody shingles during a reentry from a critical abort. What remained unproven was the launch vehicle. The Atlas was an intercontinental ballistic missile being turned into a crew carrier, and that conversion reached into nearly every one of its systems: a missile built to throw a warhead or an uncrewed satellite carried nothing designed to keep a passenger alive.
Mercury-Atlas 1 had been lost during ascent in July 1960, and the post-flight analysis had forced a redesign of the liquid-oxygen tank skin. Meanwhile the programme's commitment stood unchanged: put an astronaut into orbit. MA-3 was the rehearsal before that flight, with the spacecraft fitted out as though it carried an occupant and a mechanical simulator taking his place. NASA framed the objective plainly as a quick test of the spacecraft-Atlas combination in orbit.
Spacecraft No. 8
The capsule assigned to MA-3 was Mercury spacecraft No. 8, delivered to the launch site on 18 November 1960. It spent twenty-three weeks in preparation at the Cape before flying, a long stay even by the standards of those early missions, when each spacecraft arrived with systems still evolving and left the pad trailing a list of requested alterations. It carried the mechanical crewman simulator — the "mechanical astronaut" — along with the normal equipment of an orbital mission. There was no animal aboard, unlike MR-2 with Ham or the later MA-5 with Enos.
Atlas 100-D: the first thick-skinned booster
The launcher originally planned for MA-3 was Atlas 77D, which passed its factory rollout inspection in September 1960. Shortly afterwards the post-flight findings from MA-1 came out, and the thin-skinned 77D was recalled and replaced by 100D. That substitution made 100-D the first thick-skinned booster delivered to the programme: on Big Joe and MA-1 only the fuel tank had used heavier gauge skin while the liquid-oxygen tank kept the standard missile thickness, and after the loss of MA-1 NASA concluded that the standard skin was not enough. MA-2's booster, 67D, was still a thin-skinned vehicle and had to be fitted with a steel reinforcement band at the interface between capsule and booster; 100-D no longer needed it.
.jpg)
The vehicle also introduced a transistorised telemetry box in place of the vacuum-tube equipment used on earlier Atlas flights, which was bulky, drew a great deal of power and whose signal strength tended to degrade during launch. The replacement had been designed for the Atlas-Centaur and was adapted quickly for Mercury.
The escape system and ASIS, for the first time in earnest
MA-3 was the first Mercury-Atlas to fly with a live escape tower. Big Joe and MA-1 had flown without a tower — and in MA-1's case the absence was suspected of having spoiled the aerodynamic profile of the stack — while MA-2 carried a dummy tower. The launch escape system itself was identical on Redstone and Atlas flights; what differed was the abort sensing system, far more complex on the Atlas because it was a much larger vehicle with five engines, two of them jettisoned in flight, a more sophisticated guidance system and pressurised balloon tanks that collapsed if they lost pressure.
That system, the Abort Sensing and Implementation System (ASIS), watched a deliberately short list of parameters drawn from the most likely failure modes of the D-series vehicles: excessive deviation from the planned trajectory, engine thrust or hydraulic pressure falling below limits, loss of propellant tank pressure, signs that the intermediate bulkhead was losing structural integrity, failure of the booster's electrical system, or the failure of ASIS itself. Redundancy was built in by design: if ASIS died, the loss of power alone triggered an abort. It had flown on missile research flights and then, on MA-1, open loop, able to raise an abort signal but not to command engine cutoff. MA-3 was the first flight on which it operated closed-loop.
25 April 1961: the ascent that never turned
Liftoff came at 11:15 a.m. Eastern time from Launch Complex 14 at Cape Canaveral Air Force Station. The climb was normal until about twenty seconds into flight, the point at which the pitch-and-roll sequence should have begun. That manoeuvre turned the initial vertical trajectory into a flatter one carrying the Atlas out over the Atlantic. It never happened: the rocket simply kept going straight up.
In the control room the flight dynamics officer, Tec Roberts, reported that there was no roll-and-pitch programme, and the meaning was instantly clear to everyone present, as flight director Gene Kranz later recalled: an Atlas climbing vertically threatened the Cape and the surrounding communities, and the higher it flew before breaking apart, the wider the debris footprint would be. The range safety officer confirmed the missing manoeuvre, lifted the cover from the destruct button and gave the vehicle a few seconds to recover and start its track across the ocean. It did not. The destruct command went out as the Atlas converged on the limits of the safety plot; radar then reported tracking multiple targets, the unmistakable sign that the booster had come apart.
The escape tower does its job
The escape tower fired at the very moment the destruct command was sent and lifted spacecraft No. 8 away from the vehicle. The capsule climbed to an apogee of 7.2 kilometres and landed only 1.8 kilometres downrange; the whole flight lasted 7 minutes and 19 seconds, nearly all of it descending under the parachute. A United States Marine Corps CH-37 helicopter picked it out of the Atlantic about twenty minutes after liftoff.
For the Mercury team that was the single consolation of the day: the launcher's failure had turned into an unplanned test of the escape system, and the system worked. The mission itself was recorded as a failure, and the launch site summary put it bluntly — launched and aborted, mission objectives not accomplished.
The investigation: a programmer buried in mud
On 17 May 1961 an investigation board was convened to establish the cause of the MA-3 launch vehicle failure. It considered several areas and, from a review of the test data, isolated three as probable causes. Telemetry analysis had quickly placed the fault somewhere in the guidance system without pinning down its exact nature: the evidence suggested that the missile programmer had either shut down completely shortly after liftoff or suffered a power interruption, restarted, and then failed to execute the pitch-and-roll sequence.
Two months after the flight the Atlas programmer was found buried in mud on a beach not far from the pad and was examined. The examination did not settle the cause with certainty — contamination of pins inside the programmer and a transient voltage that reset it were both proposed — but it exposed something more uncomfortable: the unit as a whole had several serious design flaws that needed correcting. The practical consequence was that the uncrewed orbital qualification flight slipped by several months, to September.
Capsule 8A and the second attempt
Spacecraft No. 8, recovered from the sea, was refitted and returned to the launch site on 11 May 1961 as spacecraft 8A, by then assigned to Mercury-Atlas 4. After eighteen weeks of preparation it flew on 13 September 1961 in the same configuration, this time atop Atlas 88-D. MA-4 carried special vibration and noise instrumentation and a mechanical crewman simulator in addition to the normal spacecraft equipment, and it became the first Mercury spacecraft to reach Earth orbit, with an apogee of 123 nautical miles and a perigee of 86 according to the programme chronology. After one orbit the spacecraft's orbital timing device fired the retrorockets and the capsule splashed down. The launch site summary records it as a spacecraft refitted and flown in the same configuration, mission successful.
That the very capsule torn away from a disintegrating Atlas should reach orbit five months later says a great deal about how the programme worked: hardware was recovered, repaired and flown again, and every failure was converted into a list of corrections. MA-3 met none of its objectives, but it left the programme three things: proof that the escape tower worked under real conditions, a catalogue of defects in the Atlas programmer, and an intact capsule with which to fly the mission MA-3 could not.
Images
%2C_mechanical_astronaut_flight_attempt.jpg)
.jpg)
Elsewhere
- Flickr (NASA on the Commons)Mercury-Atlas 3 Test Launch (NASA photo NIX-61-MA3-6) ↗
- DVIDSMercury-Atlas 3 liftoff and separation of capsule (NASA photo NIX-61-MA3-10) ↗
- Space in MiniatureMA-3 recovery team approaches the capsule (NASA photo 61-MA3-7) ↗
- Wikimedia CommonsAtlas 100-D raised into the LC-14 gantry, two days before the Mercury-Atlas 3 launch attempt (NASA photo GPN-2003-00039, 23 April 1961) ↗
- Wikimedia CommonsAtlas 100-D unloaded from a USAF C-133B Cargomaster at Cape Canaveral for Mercury-Atlas 3 (NASA photo GPN-2003-00041, 23 April 1961) ↗
- Space in MiniatureMercury-Atlas 3 on the pad at LC-14, from NASA's "This New Ocean" p. 336 ↗