page_title: Mercury-Atlas 4
hierarchical_section_title: Mercury-Atlas 4
caption_attribution_description: English: Sketch showing location of crewman simulator for Mercury-Atlas 4 flight. Modified by Reubenbarton in Paint Shop Pro for clarification.
context_page_description: Mercury-Atlas 4 was an unmanned spaceflight of the Mercury program. It was launched on September 13, 1961 at 14:09 UTC from Launch Complex 14 at Cape Canaveral, Florida. A Crewman Simulator instrument package was aboard. The craft orbited the Earth once.
  At this time, NASA was getting increasingly frustrated with the Atlas's poor launch record. Of four Mercury-Atlas flights so far, two had been total failures. One had been a partial success and the otherwise completely successful MA-2 had experienced propellant slosh problems. In addition, the Atlas had not performed well in unmanned programs either as three Atlas-Able lunar probe launches in 1959–60 had all failed. The Air Force was also experiencing problems with military launches as a MIDAS early warning satellite and a SAMOS photoreconnaissance satellite launched with Atlas‑Agenas both failed to orbit during 1960. Only a few days before the flight of MA‑4 in September 1961, an Atlas‑Agena carrying a SAMOS satellite fell back on the launch pad at Vandenberg AFB, producing a spectacular explosion. Atlas ICBM tests at this time were still routinely failing as well.
context_section_description: Mercury-Atlas 4 was an unmanned spaceflight of the Mercury program. It was launched on September 13, 1961 at 14:09 UTC from Launch Complex 14 at Cape Canaveral, Florida. A Crewman Simulator instrument package was aboard. The craft orbited the Earth once.
  At this time, NASA was getting increasingly frustrated with the Atlas's poor launch record. Of four Mercury-Atlas flights so far, two (MA-1 and MA-3) had been total failures. One (Big Joe) had been a partial success and the otherwise completely successful MA-2 had experienced propellant slosh problems. In addition, the Atlas had not performed well in unmanned programs either as three Atlas-Able lunar probe launches in 1959–60 had all failed. The Air Force was also experiencing problems with military launches as a MIDAS early warning satellite and a SAMOS photoreconnaissance satellite launched with Atlas‑Agenas both failed to orbit during 1960. Only a few days before the flight of MA‑4 in September 1961, an Atlas‑Agena carrying a SAMOS satellite fell back on the launch pad at Vandenberg AFB, producing a spectacular explosion. Atlas ICBM tests at this time were still routinely failing as well.
  These incidents produced a series of confrontations between NASA and Convair, the builders of the Atlas. As August 1961 ended, there had been 14 Atlas space launches (SCORE, Big Joe, the three Atlas-Able flights, Midas 1-3, Samos 1-2, Mercury-Atlas 1, Mercury-Atlas 2, Mercury-Atlas 3, and Ranger 1). Of these, eight were total losses and one had been a partial failure, yielding a 30% success rate. Convair argued that many of the failed Atlas space launches were due to faults of the upper stages or payload rather than the Atlas itself and on this point were correct. Only Big Joe and MA-3 could be directly blamed on a malfunction of the Atlas and the former's problems still did not preclude the mission from carrying out most of its goals. In any case, Atlas was hardly alone in reliability issues; the other workhorse of the US space program, Thor, had a launch record that was scarcely better.
  There were a series of delays getting the Atlas and Mercury capsule ready, because the postflight findings from MA-3 had necessitated extensive modifications to the booster. Vehicle 88D did not undergo its factory rollout inspection until June 30 and delivery to the Cape waited until July 15. Moreover, the flight was not going to use Mercury capsule #9 as planned, but instead capsule #8, which had been recovered from the MA‑3 launch and refurbished. Capsule #8 was also the last of the older models with small port windows, no landing bag, and a heavy locking mechanism on the hatch.
  Further delays happened when it was discovered that the brand of transistor used in both the Atlas and Mercury were prone to forming solder balls, thus the entire last week of August was spent laboriously repairing them.
  In August, the Soviet Union orbited cosmonaut Gherman Titov in Vostok 2 for a day‑long flight, producing stunned disbelief in the US and paranoia in some quarters as Soviet premier Nikita Khrushchev proclaimed in a speech afterwards "We have launched Gagarin and Titov into space, and we can deliver a nuclear weapon to any point on the planet!"
  This flight was an orbital test of the Mercury Tracking Network and the first successful orbital flight test of the Mercury program--all previous successful launches were suborbital. The payload consisted of a pilot simulator (to test the environmental controls), two voice tapes (to check the tracking network), a life support system, three cameras, and instrumentation to monitor levels of noise, vibration and radiation. Because it was suspected that a transient voltage caused the malfunction of MA‑3's programmer (and that a similar problem had been responsible for Big Joe's failure to stage), Convair equipped the autopilot to give the engines a counteracting capability. Thus, testing this was also an objective of the flight. Also, the Atlas vehicle used to launch Midas 3 in July had experienced a programmer reset at staging, which did not have any significant effect 
caption: Simulator in spacecraft
exif: {}