Origins
On October 4, 1957, from the Tyuratam range in the Kazakh SSR, the Soviet Union launched Sputnik 1, the world's first artificial satellite. The event, while a scientific triumph, also signified that the Soviet Union now had the capability to attack the United States with an intercontinental ballistic missile (ICBM). The R-7, the booster rocket that launched Sputnik 1 and Sputnik 2, could be loaded instead with a hydrogen bomb, bringing the threat of a surprise nuclear Pearl Harbor-style attack on the United States and Canada. To give an early warning of any Soviet sneak ICBM attack, the governments of the United States, Canada, and Denmark (with the authority over Greenland, where the main radar station was built at Thule Air Base) agreed to build the Ballistic Missile Early Warning System (BMEWS). This system would use radar to detect incoming ICBM warheads and give about 20 minutes of warning of an ICBM attack.
However, this system was hampered by the inherent limitations of radar systems and the curvature of the Earth. Due to the location of the Soviet Union on the other side of the Northern Hemisphere, the potential Soviet ICBM sites were thousands of miles over the horizon from the BMEWS radar stations that were under construction at Thule and Clear Air Force Station, Alaska (and later on, in England), and the BMEWS stations, as huge as they are, could not detect the ICBM warheads immediately after their launching. Only when the warheads had risen above the horizon could they be detected and warnings passed on by the U.S. Air Force.
Accurate calculations had already shown that the BMEWS system would give just ten to 25 minutes of warning in the case of an ICBM attack. The MIDAS system, as planned, would extend this warning time to about 30 minutes, giving the extra time needed for all of the Strategic Air Command's nuclear-armed heavy bombers to take off from their air bases, and hence proving to the Soviet government that it could not destroy these bombers in a sneak attack. Hence, the Soviets would be deterred from launching such an attack by a valid threat of nuclear retaliation. [1] In addition, the MIDAS system should have been able to confirm radar detections from BMEWS of a thermonuclear attack, hence reducing the chances of an accidental nuclear false alarm from the radar system. [1]
Development and costs
On March 16, 1955, the U.S. Air Force had ordered the development of an advanced reconnaissance satellite to provide continuous surveillance of “preselected areas of the Earth” in order “to determine the status of a potential enemy’s war-making capability.” [2] The result of this order was the creation of a then-secret USAF program known as WS-117L, which controlled the development of the first generation of American reconnaissance satellites. These included the Corona series of observation satellites and the SAMOS satellite. The company that was to become the Lockheed-Martin Corporation which had been hired to design, develop, and manufacture the two series of satellites, suggested several other satellite programs to fill supporting roles, including a satellite that would use infrared sensors and a telescope to detect the heat produced by heavy bombers and ICBMs. [3] In response to the Soviet launch of Sputnik and the appearance of the ICBM threat, Subsystem G was added to WS-117L before the end of 1957. [4] With the creation of the Advanced Research Projects Agency (ARPA), Subsystem G was taken over by that organization and given the codename MiDAS in November 1958. [3]
In February 1959, ARPA submitted an initial project development plan to the Air Force. As defined in the initial proposal, MIDAS would use infrared sensors from high above the Soviet Union to detect ICBM launches and give early warning of a thermonuclear attack. [5] The plan called for a 10-satellite research and development program between November 1959 and May 1961. After that time, a full-scale operational system would be deployed. [6]
Because the information collected by the MIDAS satellites was extraordinarily time-sensitive, the designers of the system could not use the film-canister dropping system that had been pioneered by the Discoverer/Corona/SAMOS series of reconnaissance satellites. In that system, the cameras aboard the satellites used photographic film capsules that physically re-entered the atmosphere before being retrieved mid-air by a military airplane. The MIDAS satellites would instead have to transmit their warning signals earthward via radio waves. Actual infrared images would not be transmitted due to the limited RF channel capacity that was available then. Instead, the satellite would simply send radio messages that it had detected a suspected missile launch as well as the time and location of the launch.
Multiple MIDAS satellites would be needed to provide round-the-clock coverage of the huge landmass of the Soviet Union. A booster rocket capable of sending a satellite into geostationary orbit had not yet been developed, and one or a few of these might not be able to cover all the possible ICBM launch sites within Russia, especially in the far north near the Arctic Circle. Satellites in polar orbits would be needed to detect launches from across the Soviet Union but due to the nature of the polar orbit, each would have only a brief period of time above the Soviet Union. As the planned capabilities of the satellite changed during the design process, so did the plans for their deployment. A plan completed in January 1959 recommended a constellation of twenty MIDAS satellites orbiting at an altitude of 1,000 miles while a revised plan, produced later that year, envisioned a constellation of twelve spacecraft at 2,000-mile altitudes. [7]
Implementing a complete system, estimated in 1959, was put at between $200 million and $600 million [8] (equivalent to $1.39 billion and $4.16 billion in 2020). [9] Because of this enormous cost and the fact that several "unanswered questions" remained, the scientific advisory council in charge of advising President Dwight D. Eisenhower on Early Warning systems recommended that a program of research be conducted but that final word on implementing a complete system be delayed for at least a year. [8]
In FY1959, ARPA spent $22.8 million (equivalent to $158 million in 2020) [9] on MIDAS, and in FY1960, ARPA and the Air Force spent a combined sum of $94.9 million (equivalent to $649 million in 2020). [10] [9]
Program summary and launch history
The MIDAS program commenced on February 26, 1960 when MIDAS 1 lifted off on an Atlas-Agena A booster from LC-14 at Cape Canaveral. The Atlas completed its burn successfully, but during the coasting phase prior to staging, the Atlas LOX tank pressure suddenly went to zero followed by missile tumbling while all Agena telemetry ceased. Postflight investigation proposed several causes, but the most likely one was inadvertent activation of the Agena Inadvertent Separation Destruct System (ISDS) charges. The ISDS system was redesigned after this incident, and MIDAS 2's booster did not carry an ISDS while modifications were being made. [11]
On May 24, MIDAS 2 was orbited successfully, but the attitude control system failed. Some data was returned by the infrared sensor before the telemetry system also failed. Several planned experiments such as detection of flares on the ground and a Titan I missile test were abandoned. It remained in orbit until decaying in 1974. The next launch in the series did not take place for over a year and the program now moved to the West Coast, with Point Arguello's SLC-3 1-2 being its base of operations. During this interval, two CORONA satellites also carried and tested MIDAS sensors.
MIDAS 3, the first operational model, was launched on July 24, 1961 using the new, restartable Agena B stage. The Atlas's programmer reset itself due to a malfunction during booster jettison, but the satellite reached orbit successfully. However, one solar panel failed to deploy, starving MIDAS 3 of electrical power and it died after a few orbits. MIDAS 4 (October 21) brought about further frustration when the Atlas lost roll control at T+186 seconds. The satellite was placed into an incorrect trajectory, causing the Agena B to exhaust its attitude control gas trying to compensate during its two burns. By the time MIDAS 4 reached its intended transfer orbit, there was no attitude control gas left and the satellite could not be stabilized. It did manage to detect a Titan I launch from Cape Canaveral before one solar panel failed. A week into the mission, MIDAS 4 died when its batteries ran down. A month later, a similar control problem on SAMOS 4 resulted in the satellite failing to attain orbit. Investigation into the two failures found that the retrorocket package heat shields on both Atlas had broken off during launch, exposing the gyroscope package to aerodynamic heating. A transistor used in the roll output channel was also suspected to be at fault. It was replaced by a different type of transistor and the retrorocket heat shields were redesigned.
The MIDAS program was temporarily suspended at this point when a committee headed by ARPA director Jack Ruina recommended that no attempt at an operational missile early warning system be made until the Air Force demonstrated that it was a feasible concept at all; in addition, Midas's sensors were designed to detect liquid-fueled rocket exhaust, not solid-fueled exhaust, which was now widely seen as the future of ballistic missiles (as things would have it, the Soviet Union was far behind the United States in development of solid-fueled rockets). The committee found that program management of MIDAS was "awful" and at the current rate of success, "it would take ten years to develop an operational system". In November 1961, the Defense Department issued a directive placing all DoD space programs under strict secrecy, and so MIDAS was given the cover name "Program 461". The development time of the program was also lengthened to give more space to work out problems with the hardware.
Despite these changes, the failures kept coming. After a six-month gap, MIDAS 5 orbited on April 9, 1962. The Atlas autopilot generated an insufficient pitch and roll program, resulting in excessive altitude and insufficient velocity. This prevented the normal guidance system cutoff commands from being sent so SECO was caused by propellant depletion while a backup command from the programmer performed VECO and Agena separation. MIDAS 5 reached orbit, but an improper one from what was planned. The satellite operated until orbit 7 when a battery failure resulted in insufficient power for continued operation of the satellite systems. An extensive investigation into the Atlas autopilot malfunction found that the gyroscopes had transmitted low signal gain in all three axes, but failed to determine a specific cause. Several changes to preflight procedures and improved testing of gyroscope packages resulted. [12] Eight months later, MIDAS 6 lifted off (December 17) but never made it to orbit. The flight was apparently normal until loss of flight control starting at T+77 seconds. The Atlas broke up at T+80 seconds, the Agena continuing to transmit signals until impact in the ocean approximately 4.7 minutes after launch. Investigation into the cause of the malfunction was hampered by limited flight data--the Atlas's telemetry transmitter antenna had failed during the prelaunch countdown. Tracking film revealed a puff of smoke at the Atlas's tail end at T+64 seconds, and the missile began tumbling in all three axes at T+77 seconds before breaking up at the forward end of the LOX tank. Agena T/M also registered the loss of control. The cause of the failure was not substantiated until study of liftoff film found that a heat shield designed to protect the booster hydraulic rise-off disconnect had broken off at launch. With no thermal protection from the engine exhaust, the rise-off disconnect ruptured at T+64 seconds and allowed the hydraulic fluid for the booster engines to escape. After 13 seconds, the hydraulic system was depleted of fluid and booster gimbal control was lost. Another, unrelated malfunction had occurred when the tracking beacon for the Mod II-A guidance system failed. Had the flight continued to sustainer phase, it would be impossible to transmit guidance commands to the booster and likely result in an improper orbit and failure of the mission. [13]
MIDAS 7 was orbited successfully on May 9, 1963 and detected ten different US ICBM tests in its six-week mission, making the first successful detection of a missile launch from space. Then MIDAS 8 (June 12) repeated the same failure as MIDAS 6. Once again, the rise-off heat shield failed at liftoff, the Atlas's booster engine hydraulic fluid escaped, and the launch vehicle became unstable and self-destructed at T+93 seconds. A rise-off malfunction had also caused the failure of an Atlas D ICBM test flight in March 1963, and after three occurrences of this failure mode in six months, the rise-off heat shield was redesigned. As part of the redesign effort, GD/A also added check valves to the hydraulic system on Atlas space launchers, although not missiles. [14] One month after MIDAS 8, the last in the original MIDAS series, MIDAS 9, was launched successfully. Midas 10-12 were launched during five months in mid-1966, after which the program was officially ended and gave way to its successor, the Defense Support Program.
MIDAS and its successors were declassified in 1998.
MIDAS was at best a qualified success since like many early space programs, it was overly ambitious and had goals beyond the capabilities of contemporary technology. Problems included mistaking sunlight reflected from clouds as an enemy missile launch. The W-17 infrared sensor proved unable to detect the initial heat plume of a missile through the Earth's atmosphere, and only with the introduction of the W-37 sensor was a launch detected from orbit. Even with this success, the MiDAS system was hampered by unsuccessful launches that destroyed satellites and killed any hope of round-the-clock coverage of the Soviet Union. In addition, the lack of a continuous power source such as a nuclear reactor or solar panels meant that the satellites' batteries were exhausted after a few short weeks in orbit.
Though the MIDAS program itself failed to meet expectations, it paved the way for the eventual introduction of the Defense Support Program system of satellites that were first launched in the 1970s and provide early warning of missile launches today.
