Mercury-Scout 1, or MS-1, was a United States spacecraft intended to test tracking stations for Project Mercury flights.[1][2] It grew out of a May 5, 1961 NASA proposal to use Scout rockets to launch small satellites to evaluate the worldwide Mercury Tracking Network in preparation for crewed orbital missions. The launch of Mercury-Scout 1 on November 1, 1961, was unsuccessful, and the satellite failed to reach orbit.
Background
The Mercury Tracking Network was a series of U.S.-owned and operated ground stations and tracking ships, positioned around the world under the flightpath of Mercury spacecraft. When the spacecraft came within several hundred miles of a ground station, it could have line-of-sight voice and telemetry communications by HF (shortwave), VHF or UHF radio and C-band and S-band radar. These communications passes would only last a few minutes, until the ground station disappeared over the horizon. Between ground stations, Mercury spacecraft were out of communications, except for an occasional unreliable HF message. In the early 1960s there were no synchronous communications satellites. The ground stations were linked back to NASA's Mercury Control in Florida through land lines, undersea cables and in some cases HF radio.
The concept was approved on May 24. On June 13 the NASA Space Task Group issued requirements for a modified Scout rocket and small communications satellite that became known as Mercury-Scout. The satellite would simulate a Mercury spacecraft, allowing testing of and training with the Mercury Tracking Network.
Satellite
The 67.5 kg MS-1 communications satellite was shaped like a small rectangular box. Within the box, electronics consisted of two command receivers, two minitrack beacons, two telemetry transmitters, an S- and C-band beacon, and antennas; all powered by a 1500 watt-hour battery.[3]
Also attached was the fourth stage instrument package. The battery could power the electronics for 18½ hours before running down. To extend the satellite life, the equipment would be powered off by a ground command after the first three orbits (5 hours). During power-down, data results would be analyzed. The satellite would then be powered up for another three orbits (5 more hours). This process would then be repeated a third time. Mercury planners thought that by shutting down and powering up the satellite, the Mercury Tracking Network would get data and experience from the equivalent of three Mercury orbital missions.
Mission
NASA decided to modify a USAF Blue-Scout II, # D-8, for the first Mercury-Scout mission. The U.S. Air Force was already launching Blue Scout rockets from Cape Canaveral and launched this one as well.
Mercury-Scout 1 was readied for launch on October 31 from LC-18B. The prelaunch countdown proceeded normally, but the engine failed to ignite. Pad crews checked out and repaired the ignition circuits and the flight was reattempted the next day. Control started failing only seconds after liftoff and at T+28 seconds, the first stage started to disintegrate. Range Safety issued the destruct command at T+43 seconds. The failure was traced to a technician who had accidentally transposed two wiring connectors in the guidance system, causing pitch errors to be interpreted as yaw errors and vice versa.[1]
NASA canceled further Mercury-Scout missions. By the time Mercury-Scout 1 was launched, the MA-4 mission had already orbited. MA-5 followed MS-1 by 28 days. MA-4 and MA-5 checked out the Mercury Tracking Network making further Mercury-Scout missions unnecessary.
Payloads are separated by bullets ( · ), launches by pipes ( | ). Crewed flights are indicated in underline. Uncatalogued launch failures are listed in italics. Payloads deployed from other spacecraft are denoted in (brackets).
.jpg)
