Orbiting Nuclear Weapons During The Cold War

nukes In 1961, a major aerospace company produced a secret report on orbiting nuclear weapons for attacking the Soviet Union. The details of that report have never been made public until now. (credit: Chesley Bonestell) Nuke the site from orbit: American orbiting nuclear weapons during the Cold War by Dwayne A. Day and Hans Dolfing Monday, September 28, 2026 In Robert Heinlein’s 1948 novel Space Cadet, the protagonist is tasked with the mission of maintaining a constellation of “rocket bombs” in orbit around the Earth, capable of being called down on a city at a moment’s notice and destroying it. In the immediate post-World War II era, when nuclear weapons, rockets, and satellites looked like the future of warfare, the idea seemed obvious. Yet it was never developed and deployed, and scholars of Cold War nuclear history have not mentioned it. What has now been revealed with the declassification of several documents is that in the early 1960s, an Air Force contractor evaluated an “Earth Satellite Weapon System (ESWS)” that would have placed three dozen nuclear bombs in polar orbits so that they could be commanded to reenter and destroy targets primarily within the Soviet Union. This concept, the analysts discovered, had many problems. nukes Putting offensive weapons in orbit made them vulnerable to enemy attack or interference. The study analyzed how to make them less vulnerable. (credit: Douglas Aircraft Company) Nukes in space Starting in the late 1950s, the United States Air Force began studying the prospect of putting nuclear weapons in space to extend America’s strategic forces to the ultimate high ground. Several of these efforts have been known for decades, such as studies for placing nuclear missiles on the Moon aimed at Earth, and insane proposals for the Orion space weapons system, propelled into and through space by detonating nuclear bombs behind it while carrying additional nuclear explosives for attacking targets on Earth. But until now, the most likely concept for space weapons—placing nuclear bombs in low Earth orbit for attacking the Soviet Union—has remained secret. There were senior government advisors who did not believe that weapons in space made much sense, although the subject was being evaluated during the late 1950s and early 1960s. James Killian, who was the president of MIT and a senior advisor to President Eisenhower, later wrote in his 1977 autobiography that he believed that space weapons were “clumsy and ineffective ways of doing a job.” In June 1958, the National Security Council considered a range of national security satellites, including bombardment satellites and a manned lunar base. The RAND Corporation studied bombardment satellites from 1958 to 1960, but due to continued classification, much of these deliberations remain secret. The report’s authors made clear that establishing and maintaining an orbital weapons system would be a major task with many difficulties. In May 1961, Douglas Aircraft produced a multi-volume report titled “Earth Satellite Weapon System Study.” Also given the more generic designation Special Report (SR) 79821, it was apparently one of several contractor studies of this subject, but the only one now available. It was a comprehensive report that addressed all aspects of an orbital nuclear weapons system, from the launch site to launch vehicles to the orbiting vehicles, their command and control, to operations, and finally reentry and recovery of weapons at the end of their operational lifetime. The report referred to “Satellite Bombs” that could be brought down on Soviet cities during wartime. Douglas’ analysts evaluated the population distribution of the 150 largest Soviet cities and selected 36 targets in the Soviet Union. The specific targets remain classified, but they likely were the same highest priority targets for the US Air Force’s Strategic Air Command. The report’s authors made clear that establishing and maintaining an orbital weapons system would be a major task with many difficulties. The report devoted substantial effort to subjects like the security necessary to make sure that the Soviet Union could not interfere with the weapons, particularly by taking over their electronic systems. Because the weapons would spend much of their orbits not over the United States and in fact over adversary territory, there would be opportunities for Soviet interference that were unavailable to the Soviets with other American strategic forces securely held on military bases, and/or within American borders. nukes The satellite bombs would operate in polar orbits, which meant that nearly every part of the Earth would be reachable by a weapon. (credit: Douglas Aircraft Company) Satellite bombs The satellite bombs would be placed in circular polar orbits at an altitude of approximately 525 nautical miles (970 kilometers). The 36 weapons would be randomly spaced, although their orbits would be adjusted somewhat to achieve a more even distribution. This spacing would eliminate the need to communicate with more than one weapon at a time. Each satellite bomb would tumble in orbit, only commanded to stabilize when necessary, such as before reentry. Each weapon would be accompanied in its orbit by 5 to 20 “decoy units” intended to make identification and destruction of the weapons more difficult. Each weapon would be launched unarmed and without targeting information loaded into its electronic systems. The report devoted significant discussion to survivability, which included protecting its command system from interference as well as protecting the weapons from physical attack. Interference could include sending false signals from the ground to the weapons, interfering with their communications systems on the ground, or physically attacking them. This would require careful selection of communications frequencies, encryption of command links, and other design parameters. Because the weapons would spend most of their orbit out of range of American communications systems and much of their time over Soviet territory, it was vital that they be highly secure. nukes United States for only a small portion of their orbits. This limited communications time, while exposing the weapons to interference over Soviet territory. (credit: Douglas Aircraft Company) The “decoy units” would consist of inflatable Mylar balloons of the same size and shape as the actual weapons. They would have to accurately mimic the visual, radar, and infrared appearance of the satellite bombs. They too would tumble like the satellite bombs. Although the report mentioned the effects of “solar pressure,” it is unclear how a lightweight inflatable decoy could maintain the same orbit as a heavy spacecraft that was less susceptible to drag effects. The vehicle would be conical, with a base diameter of ten feet (3 meters), the same as the launch vehicle, tapering down to 2.75 feet (0.84 meters). It would weigh 8,000 pounds (3,630 kilograms) in orbit with a de-orbit weight of 3,500 pounds (1,590 kilograms). The entry vehicle would be 886 pounds (402 kilograms). The satellite bomb would likely be assembled and handled on the ground in a horizontal orientation, because assembling it vertically would create handling problems. nukes The satellite bombs would have a lifetime in orbit of approximately one year. To prevent them from falling into enemy hands or causing radioactive pollution if destroyed in the atmosphere or in the ocean, the study proposed recovering them over White Sands, New Mexico. With 36 weapons in orbit, this meant that nuclear weapons would be reentering over the United States several times a month. (credit: Douglas Aircraft Company) Satellite bomb disposal Because the satellites would have a mean lifetime of only one year, they would have to be replaced on a regular basis. But even more problematically, they would also have to be recovered. The United States could not leave dead nuclear weapons flying overhead in low Earth orbit. Because they were designed to reenter the atmosphere, a dead nuclear weapon would fall intact, and nobody could predict where. Because the satellites would have a mean lifetime of only one year, they would have to be replaced on a regular basis. But even more problematically, they would also have to be recovered. The report discussed the various problems associated with leaving the bombs in orbit, destroying them in orbit, and recovering them, determining that recovery was the best option. Dropping them in the ocean was a possible solution but risked enemy recovery. “If the enemy were to recover one of these, our warhead state-of-the-art would be revealed. Detonation of the warhead by high explosives under water would distribute the radioactive debris in the ocean,” the report stated. Even burning them up in the upper atmosphere would result in the distribution of plutonium around the Earth. “Several hundred occurrences of this sort may present a distinct health hazard.” Before a satellite failed, it would be commanded to reenter over the continental United States. As it descended into the lower atmosphere, it would deploy a parachute and be recovered in midair by a specially equipped aircraft. This technique was already in use for the CORONA reconnaissance satellite and had been proven reliable. However, the CORONA reentry capsules with their reels of exposed film were relatively lightweight, in part because the reentry vehicle ejected its heat shield over the ocean. A nuclear reentry vehicle with its reentry shield attached would weigh significantly more. nukes Bringing the weapons back from orbit to hit their targets would subject them to intense heating during reentry. (credit: Douglas Aircraft Company) After the satellite bomb was stored in the recovery aircraft, the aircraft would land at a secure facility, the satellite bomb would be removed and then transported to a secure processing facility. This would have to occur on a nearly weekly basis: nuclear weapons reentering over the United States regularly, hopefully without incident. The designers had to assume that a reentering satellite bomb might not be caught by an aircraft and it therefore had to survive landing on the ground. It would include systems for aiding in this effort, such as a “package of scatter mirrors” made of polished aluminum that would be fired from the vehicle at an altitude of 5,000 feet (1,500 meters) and scatter over the ground near the landing point. The vehicle would also have a smoke generator to create smoke to serve as a post-landing aid. The parachute would be attached in such a way as to land the vehicle nose up, so that the back, with the used retrorocket, and not the nuclear weapon, would take the impact with the ground. nukes Although several California launch sites were possible for the satellite bombs, the study determined that an operational system should not be launched from the same complex as R&D flights, such as Vandenberg Air Force Base. An additional problem was that Vandenberg included a commercial railway that ran through much of the base and interrupted flights. (credit: Douglas Aircraft Company) Launch site The authors of the report selected a new, dedicated launch site for the weapons. San Clemente Island is located 60 miles (100 kilometers) west of San Diego. As they noted, the Atlantic Missile Range was not suited to polar launches. Point Arguello and Vandenberg Air Force Base, which were then adjacent but administratively separate, already had Atlas launch facilities operating or planned. But those locations were less than ideal. As the authors explained, further expansion of research and development facilities at those locations would be prevented by an operational satellite weapons system, and R&D and operations would be occurring at the same base “thereby presenting complex security and safety problems.” But a third reason was a mundane one that had already plagued launch operations on the West Coast: “A federal contract with the Southern Pacific Railroad restricts launching schedules when trains are in the vicinity of the base.” nukes The study looked at several possible launch sites for the satellite bombs and determined that San Clemente Island, off the California Coast, was the best location. (credit: Douglas Aircraft Company) San Clemente was the site of an abandoned military facility, but all new facilities would be required, including a new 10,000-foot (3,000-meter) runway, housing and other facilities, and up to five or more launch pads along the west side of the narrow island. nukes Artist impression of the Atlas-Centaur rocket at its A-frame gantry. (credit: Douglas Aircraft Company) Atlas-Centaur The Douglas study assumed that the satellite bombs would be placed in orbit atop Atlas-Centaur rockets. At the time, the Atlas-Centaur was expected to be operational by 1964. To attain high reliability for launch, the authors recommended having two vehicles undergoing simultaneous countdown. Atlas was derived from an existing ICBM, but Centaur was a new and unprecedented project, unlike any rocket in development by the military. It was a high-energy upper stage using liquid hydrogen as fuel. Liquid hydrogen was difficult to handle and its physical properties and behavior, particularly in a space environment, were not well understood. Centaur development had been assigned to NASA in 1959. nukes The Atlas-Centaur suffered some problems during its development. (credit: Peter Hunter Collection) The requirements and the difficulty of using liquid hydrogen meant that Centaur development was experiencing problems from the start. It was becoming clear to military leadership by January 1961 that the Atlas-Centaur would be a major pacing issue for planned military projects, like the Advent communications satellite. Pratt and Whitney was then working on development of the Centaur’s LR-119 engines. By summer 1961, the problems with Centaur were increasingly apparent even outside of NASA. By summer 1962, Centaur had fallen two years behind schedule. Had the Earth Satellite Weapon System entered into development, Centaur would have presented problems within a year. nukes The Centaur upper stage was under development in the early 1960s. It used liquid hydrogen, a remarkably persnickety fuel. Centaur began running into substantial problems around the time the Douglas study that recommended its use was delivered. (credit: Douglas Aircraft Company) In spring 1961, when the study was completed, the United States had only been launching rockets into space for three and a half years. Launch vehicles were still a new and immature technology. The study assumed a 20% launch failure rate. But considering that even decades later launch vehicles had failure rates of approximately 5–10%, the safety aspects of launching nuclear weapons into orbit were substantial. Simply establishing a constellation of 36 orbiting Satellite Bombs would result in multiple accidents that would destroy nuclear weapons in the atmosphere, dropping their radioactive wreckage into the ocean, possibly right off the California coast. nukes nukes nukes The launch vehicle would be vertically assembled at the launch pad. (credit: Douglas Aircraft Company) Cost and schedule Douglas also estimated the costs and schedules for the Earth Satellite Weapons System. The company assumed that the launch complex would be similar to pad 36 at Cape Canaveral, with six “soft” launch pads—meaning not capable of withstanding attack. These six pads would conduct four launches per month. The Atlas-Centaurs would be vertically assembled at the pad. The mean lifetime to failure of the satellites would be one year, with 36 satellites maintained in orbit. Approximately two thousand personnel would be required to support the launch operation. The satellite bomb recovery site would be based in the American southwest, and although the company calculated the cost of the recovery operations, it noted that facilities would probably be provided by the government, not the contractor, and would most likely consist of existing facilities in someplace like the Nellis Air Force Base in Nevada. Recovery operations would require approximately one thousand personnel. The Earth Satellite Weapon System never progressed beyond the study phase. The details of whether it was seriously evaluated at senior Pentagon levels are unavailable. Assuming that authority to proceed was granted by the last quarter of 1961, the first test vehicle launch using an interim booster could take place by the end of 1963, with the first test vehicle launch using an Atlas-Centaur occurring by the middle of 1964. Launch site construction would start at the beginning of 1963, with the site becoming operational by spring of 1965. The first launch of an operational vehicle would take place by summer 1967, with the system becoming operational by summer of 1968. Based upon these assumptions, Douglas estimated that the research and development would cost $424.2 million by the end of fiscal year 1964, with an operational cost of $2.569 billion by the end of fiscal year 1973. A year later, the RAND Corporation produced an estimate that an orbital nuclear bombardment system would cost five times a terrestrial-based system. nukes The Earth Satellite Weapon System would likely have been under control of the US Air Force’s Strategic Air Command. (credit: Columbia Pictures) No nukes in space During the time that the Earth Space Weapons System was being studied, the Air Force was also developing the X-20 Dyna-Soar, a winged spacecraft to be launched atop a Titan rocket and piloted by a single military astronaut. The X-20 was an ambitious and complicated program. But it lacked a clear justification. The Air Force and contractors proposed various missions that the X-20 could accomplish, one of which was “orbital bombardment.” But this mission made little sense when closely evaluated. There was no need to put an astronaut in a vehicle to drop a single nuclear weapon from orbit when that same weapon could simply be placed atop an ICBM. Dyna-Soar added tremendous complexity and cost to the mission, not any versatility. There were other proposed missions for Dyna-Soar, but none of them made much sense or justified the cost. By late 1963, Dyna-Soar was canceled. The Earth Satellite Weapon System never progressed beyond the study phase. The details of whether it was seriously evaluated at senior Pentagon levels are unavailable, although the Douglas study was prepared at a time when the new Secretary of Defense Robert McNamara was canceling many of the Air Force’s more complicated and expensive weapons systems such as the XB-70 Valkyrie bomber, the Skybolt air-launched ballistic missile, and later the X-20 Dyna-Soar. It was thus an expensive and complicated solution in search of a problem. During the next several years, a series of negotiations on the placement of nuclear weapons in space took place in the United Nations. On October 17, 1963, the United Nations General Assembly Resolution 1884 (XVIII) called on states “to refrain from placing in orbit around the earth any objects carrying nuclear weapons or any other kinds of weapons of mass destruction or from installing such weapons on celestial bodies.” The resolution was formalized in the 1967 Treaty on Principles Governing the Activities of States in the Exploration and Use of Outer Space, including the Moon and Other Celestial Bodies, aka the Outer Space Treaty. However, even while early negotiations were ongoing, the United States continued studying orbital nuclear weapons programs. They will be discussed in a future article. Special thanks to JB. Dwayne Day can be reached at zirconic1@cox.net. Hans Dolfing is an independent computer scientist with a passion for spaceflight, software, and history and can be contacted at beta_albireo@protonmail.com.

Starship Finally Makes It To Orbit

Falcon 9 launch Starship lists off September 28 on Flight 14, its first orbital mission. (credit: SpaceX) Starship (finally) reaches orbit by Jeff Foust Monday, September 28, 2026 On September 28, a SpaceX rocket reached orbit for the first time. Again. On September 28, 2008, Falcon 1 successfully reached orbit for the first time on the vehicle’s fourth launch. The first three had failed, all for different reasons, and the company’s future was at stake. Another failure could have meant the end of the company. As Huot finished the explanation of the revised flight, he paused as contollers deliberated on communications loops not aired on the public webcast. “So, we are not giving up yet on orbit.” “I think my nervous system almost got fried watching that flight,” SpaceX CEO Elon Musk said on the company’s webcast of the launch shortly after Falcon 1’s upper stage and its inert payload reached orbit. “I don’t know what else to say. It’s so fricking awesome my mind is blown.” (See “A sign of progress”, The Space Review, September 29, 2008.) On September 28, 2026, it was Starship’s turn. This was the 14th flight of Starship/Super Heavy; the first 13 had all been intentionally suborbital, albeit with varying degrees of success. While some of those earlier flights had gone almost all the way to orbit, this time SpaceX planned to place Starship’s upper stage in orbit and deploy 26 Starlink V3 satellites, larger next-generation spacecraft for the company’s broadband constellation. It almost didn’t happen. While Starship lifted off at 8:48 am EDT from Starbase, Texas, after a smooth countdown, one of the six Raptor engines in the ship shut down prematurely during its ascent. SpaceX previously said they would only proceed with a brief orbit insertion burn and payload deployment if the vehicle was healthy. “We did have one of those engines go out on the way uphill, and because of that, we are not going to do the additional burn that will send us into orbit. So definitely not the outcome we were all hoping to hear today,” SpaceX Dan Huot said on the webcast. He explained that Starship would instead complete a suborbital flight like previous ones, splashing down in the Indian Ocean without deploying its Starlink payload. But as finished the explanation of the revised flight, he paused as contollers deliberated on communications loops not aired on the public webcast. “Teams continue to look at everything, so you're getting this in real time as I’m starting to see it,” he said, followed by another pause. “So, we are not giving up yet on orbit.” The engine that shut down, he explained, was one of three vacuum-optimized engines that would not have been used for the rest of the mission. If the other engines were healthy, controllers could agree to continue the flight, including performing the orbit insertion. About ten minutes later, Huot came back with good news. “All right, so the go/no-go poll for orbit has finished, and we are go for orbit,” he announced. One Raptor engine then fired for 19 seconds, placing Starship into a roughly circular orbit at an altitude of about 275 kilometers. Payload deployment followed, with 26 Starlink V3 satellites slowly released from Starship’s payload bay. SpaceX reported soon after the completion of the half-hour deployment that all 26 were functioning, making contact with the ground and with other Starlink satellites through laser links. “If this flight goes well,” Musk said earlier this month, “then on Flight 15 we will attempt to catch the ship.” The original plan for Flight 14 was for Starship to make about six orbits of the Earth, reentering and splashing down in the South Pacific Ocean off the coast of Chile nearly ten hours after liftoff. Instead, SpaceX decided to end the mission early, wrapping up after less than two orbits with a splashdown in the North Pacific several hundred kilometers north of Hawaii. The reentry was similar to previous suborbital flights, with the ship making a “soft” splashdown before toppling over and exploding. “Out of an abundance of caution given the engine issue experienced during ascent, the flight control team decided to limit the duration spent on orbit and proceeded with deorbiting Starship to a splashdown location in the northern Pacific Ocean,” SpaceX said in a summary of the mission published later in the day. While Musk had his mind blown with the first Falcon 1 reaching orbit, he seemed more sedate about the first Starship. “First orbital flight of Starship successful!” he posted on X, the social media site now part of SpaceX, but didn’t appear to fixate on the milestone, posting as much about AI developments at the company as about Starship. Now to do it again and again With SpaceX now demonstrating that Starship can reach orbit and deliver payloads, it’s now time for the company to demonstrate what will set the vehicle apart: recovering and reusing both stages. Before the launch, Musk said that the next mission, Flight 15, could be the first to not just recover the Super Heavy booster—which SpaceX has done on previous missions dating back nearly two years—but also the upper stage. “If this flight goes well,” SpaceX Chief Executive Elon Musk said of Flight 14 during an appearance at the All-In Summit earlier this month, “then on Flight 15 we will attempt to catch the ship.” The ship, like the booster, will be caught by a launch tower back at Starbase. He sounded confident that could be done. On Flight 13 in July, the ship made a pinpoint splashdown in the Indian Ocean and remained intact after toppling over. SpaceX spent weeks recovering the ship, loading it on a transport vessel currently on its way back to Texas. For the Flight 13 splashdown in the Indian Ocean, he said, “if there had been a tower at that location, it would have caught the ship.” He gave SpaceX a 50–60% chance of catching the ship on that next flight. One question, though, is whether this flight went sufficiently well to attempt a recovery of the ship at Starbase. In addition to the premature Raptor shutdown on the ship, one of 33 Raptors in Super Heavy shut down during ascent and a second failed to relight for boostback and landing burns. That did not affect the mission—Super Heavy made a controlled splashdown in the Gulf of Mexico as planned—but Raptor engine malfunctions have been an issue on several Starship test flights. Musk said earlier this month he was primarily concerned about Starship’s ability to remain intact through reentry since, for a return to Starbase, it will reenter over land. “What we’re most concerned about is, if the ship were to break up over land and rain debris on people, our popularity would diminish very rapidly,” he said. “Either at the end of this year or, more likely, early next year, we will refly the ship and refly the booster,” Musk said. Notably, Musk said in early August in a SpaceX earnings call that Flight 14 would be the first to attempt a return to Starbase for the upper stage. “I would say things look very good, and that’s why we, assuming we receive regulatory approval to do so, will attempt to catch the ship with the tower on the next flight, which is tentatively scheduled for the end of this month,” he said. By later in the month, though, he scaled back those plans, saying a catch of the ship was planned “in a few months.” By that point Flight 14’s launch had also slipped from end of August to mid-September, before being pushed back again to the end of the month. One Starship and Super Heavy are recovered, SpaceX will then need to demonstrate they can be reflown, and rapidly. “Either at the end of this year or, more likely, early next year, we will refly the ship and refly the booster,” Musk said at the All-In Summit, with the goal of “full reusability with rapid reflight” in 2027. That is vital to SpaceX’s ambitions. SpaceX is counting on Starship to start deploying next-generation Starlink satellites with greater capacity than the Starlink V2 mini satellites being launched by Falcon 9 today. Last month, SpaceX abruptly ended Falcon 9 Starlink launches from Florida as part of that transition, although it continues to launch them from Vandenberg Space Force Base in California. Starship is also needed for the company’s orbital data center satellites that it plans to launch as soon as next year. While SpaceX has two Starship launch pads in Texas and three under construction in Florida, the company is thinking much bigger. It announced last month plans for Starbase Louisiana, a massive spaceport on the Gulf coast that could ultimately include 10 pads and support infrastructure. “By starting with a clean-sheet design, we’re planning to build a self-sustaining spaceport with its own propellant production, power generation, deepwater shipping capabilities, vehicle processing facilities, and probably an airport,” SpaceX president Gwynne Shotwell said at the event announcing the spaceport. Louisiana state officials said SpaceX would invest $100 billion in Starbase Louisiana, far more than what the company has spent on Starship development overall to date, but did not disclose details about how the money would be spent or over what period. The first launches from Louisiana could take place as soon as 2029. NASA is also anxiously awaiting routine Starship flights. Starship is a central part of the Artemis lunar exploration effort, but delays in Starship’s development have raised doubts about whether the vehicle will be ready to support a lunar landing mission in 2028, requiring NASA to turn to Blue Origin’s Blue Moon (see “Artemis 3 take shape”, The Space Review, June 15, 2026.) That includes a long-awaited demonstration of in-space cryogenic propellant transfer from one Starship to another, a core enabling technology for any Starship mission beyond low Earth orbit. While SpaceX has tested transfers between tanks inside a Starship on a suborbital flight, the ship-to-ship transfer required an orbital capability. Many technical details about the vehicle have changed since then, along with its name, but the broad outlines Musk presented in 2016 are present in Starship today: full reusability, use of methane as fuel, and in-space propellant transfer. In an interview at a Wall Street Journal Leadership Institute event earlier this month, NASA administrator Jared Isaacman called that technology a “gamechanger for America’s competitiveness in space.” He expected that demonstration to take place “in very early 2027, maybe the end of this year.” NASA itself has provided few details about the development of the lunar lander version of Starship or other capabilities needed for Artemis since June, although Isaacman said in a memo to agency employees last week that preparations for the Artemis 3 LEO mission, involving Starship and Blue Moon, were running about three months behind schedule. He promised an “Artemis acceleration update” in early October. The first Starship orbital flight took place 18 years to the day after the first Falcon 1 reached orbit, but it also took place ten years and one day after another milestone: a talk by Musk at the International Astronautical Congress in Guadalajara, Mexico, where he unveiled what was then known as the Interplanetary Transport System, the precursor to Starship (see “Elon Musk’s road to Mars”, The Space Review, October 3, 2026.) Many technical details about the vehicle have changed since then, along with its name, but the broad outlines Musk presented then are present in Starship today: full reusability, use of methane as fuel, and in-space propellant transfer. He predicted then that the vehicle would become the central focus of SpaceX, with the company investing $10 billion to develop it. (SpaceX has spent more than $15 billion on Starship, the company disclosed in filing as part of going public earlier this year.) He said then that the vehicle could be ready by the early 2020s, with the first missions to Mars in the mid-2020s. But, he acknowledged even then a reputation for setting and then missing deadlines: “I’m not the best at this sort of thing.” Ten years later, Starship has finally delivered payloads to orbit. Now it’s time for the vehicle to deliver on that promise of rapid reusability, something demanded by the company’s investors and partners. Jeff Foust (jeff@thespacereview.com) is the editor and publisher of The Space Review, and a senior staff writer with SpaceNews. He also operates the Spacetoday.net web site. Views and opinions expressed in this article are those of the author alone.

Nepal: The Watchers and the Warning

flood map Satellite images were used to study the aftermath of floods in the Himalayas but could not provide people living there with timely warnings. (credit: Satellite Image Credit: WorldView-3 © Vantor (2026), provided by European Space Imaging (acquired on 27/08/2026 at 05:05 UTC). All images are provided under COPERNICUS by the European Union and ESA, all rights reserved.) The watchers and the warning: what a Himalayan flood asks of Golden Dome by Bharath Gopalaswamy and Daniel Dant Monday, September 28, 2026 At about 20 minutes to nine on the morning of August 26, high above the Lhende Khola on the Nepal side of the Tibetan border, a section of glacier gave way. The ice and rock that fell into the valley either caused or deepened a temporary blockage of the river, and when that blockage failed it released a wall of water and debris that traveled nearly a hundred kilometers downstream. In the district of Rasuwa, the surge erased the border crossing at Rasuwagadhi, flattening buildings and smoothing the ground where a town had stood. Downstream, the Trishuli rose as much as nine meters in 30 minutes. The villages of Timure and Syapru Besi were struck first. Bodies were later recovered far to the south, in Gorkha, Tanahun, and Chitwan. Dozens of bridges are gone, roads are severed, hundreds of megawatts of hydropower are offline, and the losses are counted in the billions. The dead and the missing are counted in people. The failure is the absence of the layer that should sit between the camera and the person at risk, the layer that turns an observation into a decision and a decision into a warning that arrives while there is still time to move. We are a space-security scholar and a retired military officer, and we write ordinarily about missile defense, satellites, and the architecture of homeland protection. We do not write about Himalayan disasters, and we do not claim any standing to speak for the communities of Rasuwa and Nuwakot, whose grief is their own. We write because of something we could not stop considering in the days after the flood, and because we believe it bears directly on decisions the United States is making right now about how it defends itself from the sky. The world watched this disaster happen from orbit. And watching, it turned out, was not the same as warning. Seen from space, in time, and still too late Within hours, the imagery was everywhere. Planet Labs captured the before and after. The European Union’s Copernicus Sentinel-2 satellites stitched together the sequence of the flood’s descent. The International Charter on Space and Major Disasters activated, as it does for catastrophes of this scale, marshaling the world’s Earth-observation assets to map the damage. By any measure of sensing, the system worked. The glacier, the blockage, the surge, the ruined crossings: all of it was observed, recorded, and understood with remarkable speed and clarity. It is worth being precise about how well observed this region is, because it changes where the problem lies. This is not a corner of the world starved of satellites. India operates one of the most capable civil and security Earth-observation fleets in existence, including high-resolution optical and all-weather radar spacecraft. China fields an extensive constellation of its own across the same skies. Europe’s Sentinels stream openly and globally. Commercial operators image the entire Himalayan arc, in many cases daily. Between them, the states and companies with eyes on these mountains possess an abundance of observation that would have been unimaginable a generation ago. We raise this not to ask why any of them did not sound an alarm, which would be both unfair and beside the point. With all of that capability trained on the region, the warning still did not reach the valley in time. That tells us the frontier is no longer detection. It is everything that must happen between the observation and the person in the water’s path. The satellites documented the disaster but did not avert it. This is not a failure of the cameras or of anyone operating them. The failure is instead the absence of the layer that should sit between the camera and the person at risk, the layer that turns an observation into a decision and a decision into a warning that arrives while there is still time to move. That layer is the hardest part of any sensing enterprise to build, because it is not a matter of better optics or more satellites, of which the region has many. It is a matter of fusing many signals, judging which ones matter, and acting at machine speed under the pressure of minutes. It is, we have come to believe, the same problem the United States is now spending a great deal of money and attention trying to solve for an entirely different threat. The same gap, in a different sky Golden Dome, the homeland missile-defense architecture now taking shape, rests on a foundation of space-based sensing: a proliferated layer of satellites in low Earth orbit to track threats, a data backbone to move what they see, and interceptors to act on it. In our earlier writing we have argued that the part of this architecture most likely to determine whether it succeeds is neither the sensors nor the interceptors, but instead the decision layer between them, the command and control that must fuse thousands of tracks, judge intent, prioritize, and assign a response in the seconds available, while a human retains authority over the choice to act. Detection, we wrote, without a pre-rehearsed decision chain, may simply document an attack. The case for building durable decision and warning infrastructure, rather than improvising after each disaster, grows stronger with every season. Nepal is that sentence rendered in water instead of fire. The threat could not be more different, a warming glacier rather than a hostile missile, but the shape of the failure is identical. Observation outran decision. The sensors saw more, and sooner, than the systems and institutions below them could turn into a timely act. If that gap is the thing that will decide whether a missile-defense architecture protects American cities, it is also, we now see plainly, the thing that decided how many people in a Himalayan valley had a chance to reach high ground. The engineering challenge that keeps defense planners awake is, underneath, a humanitarian one as well. What would close the gap Stated as an architecture rather than a lament, the missing layer has recognizable parts, and none of them require a single new satellite. The first is fusion across owners and borders: a means to combine what Indian, Chinese, European, and commercial sensors each see into one coherent picture, so that no single operator must detect an unfolding event alone. The second is automated triggering: change-detection and threshold logic that can recognize a glacier collapse or a sudden river rise and raise an alert without waiting for a human analyst to notice, because in a thirty-minute flood there is no time for a human to be the first to notice. The third is pre-delegated dissemination: agreed channels and authorities that carry a validated warning the last mile, to the district officer and the village, before anyone convenes a meeting to decide whether to send it. The fourth, and the hardest, is institutional: the cross-border data-sharing arrangements that let one nation’s observation lawfully and instantly become another nation’s warning. The technology for the first three exists. The fourth is a matter of will, and it is where the greatest lives-per-dollar return almost certainly lies. There is an example of this approach. Israel has built, and operates at national scale, close to the most mature example of the architecture this argument calls for. Radar detects a launch, an automated system computes where it will fall, and within seconds a location-specific alert reaches the civilians in its path, by siren and by a warning pushed to their phones, telling them how long they have to reach shelter. The interceptors of Iron Dome are the part the world sees, but the part that saves the most lives is quieter: the chain that turns a sensor reading into a person moving to safety, resolved in the seconds that are all anyone has. Where the Nepal flood shows the gap between seeing and warning at its widest, the Israeli civil-alert system shows the same gap closed. The architecture is not aspirational. It exists, it functions under fire, and it demonstrates that the hard problem—detection turned into a decision turned into a warning at the last mile—is solvable when a society decides to solve it. What remains, for Himalayan valleys as for homeland defense, is the will to build it where it does not yet reach. It would be a comfort to treat the Nepal flood as a freak occurrence, a once-in-a-generation collapse. It is not. Glacial-lake outburst floods of this kind are growing more frequent as the high mountains warm, as meltwater works deeper into the ice and weakens the bonds that hold rock and glacier together. Nepal has now suffered damaging floods with a glacial signature in successive years, and the Rasuwagadhi crossing was struck by a smaller flood only last year. What was once rare is becoming a recurring feature of life along these rivers, which means the warning problem is not a problem to be solved once but a permanent condition to be lived with. The case for building durable decision and warning infrastructure, rather than improvising after each disaster, grows stronger with every season. The architecture we build for war should also serve the vulnerable Here is the argument we most want to make, and we make it with care. The United States is about to build one of the most capable space-based sensing and decision enterprises in history, and it is building it for national defense. That is a legitimate and necessary purpose. But the capability at the heart of it—the fusion of many sensors into a fast, trustworthy decision—is not intrinsically military. The same architecture that could tell a command center which of a thousand tracks is a genuine threat could also tell a district officer in Rasuwa that the river will rise nine meters in half an hour. The same architecture that could tell a command center which of a thousand tracks is a genuine threat could also tell a district officer in Rasuwa that the river will rise nine meters in half an hour. The expertise the United States is developing to build machine-speed decision layers over a proliferated sensing base is precisely the expertise a multinational disaster-warning system needs, and which the region’s existing satellites already place within reach. We treat these as separate problems, funded through separate channels, one as security and one as disaster relief, the first lavishly and the second on whatever is left. The flood is a reminder that they are, at the level of the underlying capability, the same problem. We are not proposing that missile-defense satellites be redirected to flood duty, or that humanitarian need justify a defense program or vice versa. We are proposing something more modest and, we think, more durable: that as the nation designs the decision architecture above its sensing layer, it designs it in the knowledge that the same capability serves more than one mission, and that the hard-won craft of building it can be shared with the civil-warning effort at little cost to the defense one. Built narrowly, for war alone, it would waste a chance to protect the vulnerable at the margins where a warning is the difference between an evacuation and a funeral. A decision layer built with that breadth in mind is not a weaker instrument of defense. It is a wiser one. In the days after the flood, the images that stayed with us were not the satellite composites, striking as they were. They were the views from the valley floor: excavators clearing sludge from where homes had been, mud to the rooflines in Trishuli, families waiting for news that in too many cases came from far downstream. The people of Rasuwa and Nuwakot did not need to be told that a glacier had failed. They needed 30 minutes, and a voice telling them to climb. The world’s satellites, of many nations, saw the water coming. The distance between that seeing and that voice is the whole of the problem, and it is the problem we are now, for our own reasons, spending a fortune to solve. We should solve it in a way that would have reached the valley too. Bharath Gopalaswamy, PhD, is an aerospace, defense, and emerging-technology executive. Col. (Ret.) Dan Dant, Vice President at KBR, is a defense industrial-base strategist. Gopalaswamy and Dant are Senior Fellows of the National Spacepower Center. The views expressed are the authors’ own.

The Delima Of Space Weaponization

Meink Secretary of the Air Force Troy Meink used a September 14 conference speech to disclose that the US has “space control” weapons in orbit. (credit: US Air Force photo by Andy Morataya) The dilemma of space weaponization by Ajey Lele Monday, September 28, 2026 For decades, the international community has broadly maintained that outer space should remain a peaceful global common, free from the deployment of any weapons. However, a recent US announcement has challenged this longstanding norm and prompting a major scare about the space weaponization. The recent US announcement that it has deployed weapons in orbit is a significant departure from the self-constrained approach followed so far. On September 14, Secretary of the Air Force Troy Meink stated at a conference that the United States has deployed weapons in space and would use them to defend the country and its forces, if required. He argued that the US needs such capabilities in orbit to signal to potential adversaries that it is prepared to respond to hostile actions in the space domain. The deployment supposedly provides the US with on-orbit space-control capabilities. The US administration has not disclosed the nature or capabilities of these weapons, but considers their deployment an important step towards establishing deterrence in space. The US has chosen not to disclose the nature of these weapons, arguing that doing so would compromise the element of surprise and potentially weaken their deterrent value. For several years, concerns over the prospect of warfare reaching outer space have been growing. There are major concerns regarding the development of counterspace capabilities by China and Russia. The US is also known to be simultaneously developing such capabilities. Along with that, the US established the US Space Force as a separate military service in 2019. Obviously, one of the major considerations for this was the various challenges posed by Russia and China in the space domain. However, despite the growing military competition among the three major powers, none had openly acknowledged the deployment of weapons in space. Some degree of strategic restraint was in place since there was a realization about the potentially destabilizing consequences of crossing the red line. However, the recent US announcement that it has deployed weapons in orbit is a significant departure from the self-constrained approach followed so far. Possibly, the US no longer wants any ambiguity in this regard. This clearly indicates that they want to establish a space deterrence mechanism. This move is bound to push some other powers to respond accordingly. The US decision denotes an important turning point in the evolution of space security and is likely to have implications for the future character of warfare, particularly in space. This move is much of a concern since it could contribute to greater military competition in outer space and even start an arms race in space. The US is setting a dangerous precedent that could ultimately prove detrimental to global peace and the sustainable use of outer space. Actually, the US had an option to avoid putting any weapons is space. For this purpose, they could have followed the path of arms control and disarmament. Interestingly, it was an initiative pushed by Russia (supported by China) that was giving them an opportunity. UNGA Resolution 69/32, “No First Placement of Weapons in Outer Space”, also known as PPWT, was adopted on December 2, 2014, with 126 votes in favor, 4 against, and 46 abstentions. It was a significant step towards strengthening international attention to space security and the prevention of an arms race in outer space (PAROS). The willingness of UN member states to pursue initiatives aimed at creating a more secure and sustainable space environment was clearly evident. However, the US showed little interest in the resolution. This could be viewed as a missed opportunity, as greater US engagement with the resolution might have contributed to delaying the potential weaponization of outer space, now sure if it could have stopped it totally. Arms control and disarmament initiatives may at times appear constrained by geopolitical interests and even by hypocrisy among states. However, they continue to retain considerable relevance in the contemporary international system. UN resolutions can influence state behavior and gradually contribute to greater international acceptance of the norms and principles they promote. Many experts argue that Russia and China possess significant counterspace capabilities. However, broader acceptance of UNGA Resolution 69/32 could, at the very least, have contributed to greater restraint against placing weapons in outer space. But it is unfortunate that the UN Security Council P5 group is deeply divided between Western nations and the China-Russia partnership. This is causing political gridlock on global issues, with space security one such victim of the impasse. Is US space deterrence a viable defense strategy, or has the US moved too quickly towards deploying weapons in space? Now, the US confession that it has placed weapons in space is likely to undermine the emerging normative framework and potentially open a Pandora’s box, encouraging other states to follow suit. Technically, the US has not broken any treaty obligations. The 1967 Outer Space Treaty (OST) is bans the testing of any weapons of mass destruction in space and does not explicitly ban conventional or non-kinetic weapons in space. There is a possibility the US could have placed in orbit systems like space-based jammers and electronic warfare systems as “weapons.” Particularly since the 1991 Gulf War, armed forces around the world have increasingly integrated space-based technologies into both peacetime and wartime processes. Satellites are used for weather monitoring; intelligence, surveillance, and reconnaissance; navigation; communications; and missile warning. There is broad international recognition that the military use of space-based technologies alone does not constitute the weaponization of outer space and is generally compatible with existing international law and norms. Such capabilities primarily serve as force multipliers for armed forces. In contract, weaponization of space is about development, deployment, or use of capabilities intended to threaten, harm, or destroy the space assets of adversaries, either in space or on ground. Is US space deterrence a viable defense strategy, or has the US moved too quickly towards deploying weapons in space without first giving adequate consideration to developing and establishing the concept of space deterrence as a coherent strategic framework? It is important to critically assess whether space deterrence can function as an independent strategic construct. Given the evolving nature of the space domain, future theorists and policymakers will need to examine its conceptual foundations, credibility, limitations, and practical applicability of this idea. Today, there is no strategic framework available in this regard. This is not to argue that deterrence has no role in space domain, but it has not been properly discussed. Rocket science and nuclear science are fundamentally different domains, and the strategic logic of nuclear deterrence cannot simply be juxtaposed to outer space. Nuclear deterrence works because nuclear weapons can threaten a state’s survival and invite massive retaliation. Space systems are becoming increasingly important in supporting human life and socioeconomic development. The civilian applications of space far exceed their military uses. At the same time, losing satellites can be serious but itself is not generally not an existential threat to a state. Traditional models like Mutual Assured Destruction (MAD) are not going to be effective for space domain. It has been often said that there is “no Mahan for space,” since even today the space domain has no unifying doctrine and the current international relations debate in this regard remains fragmented and inconclusive. Against the backdrop, it could be said that the existing logic for space deterrence is inadequate. It may now be only a matter of time before China and Russia also begin placing weapons in space, if they have not done so already. They are unlikely to continue pushing for negotiations on their pet mechanisms such as the PPWT with the same emphasis. The UN’s Open-Ended Working Group discussion will have to take these emerging realities into account. In such an environment, existing and future efforts to develop codes of conduct, rules of the road, and mechanisms such as transparency and confidence-building measures could lose much of their relevance and effectiveness. The US action is likely to increase the risks of space warfare and could also contribute to normalizing the idea that outer space is simply another domain of warfighting. Space assets are difficult to defend; vulnerabilities would be mostly asymmetric and challenges such as attribution can complicate any response. For the US, China and Russia may be the most obvious strategic challenges. But what is the guarantee that additional challenges will not emerge as the number of space actors continues to grow, including from private space companies with increasingly sophisticated capabilities? States such as North Korea and Iran could also seek to exploit emerging vulnerabilities in the space domain. Once momentum towards a space arms race begins, it could become difficult to reverse, potentially making outer space an unstable security environment. Ajey Lele is Deputy Director General at MP-IDSA, New Delhi, India and the views expressed are personal.

Rethinking China's 2026 Debris Events

CZ-6C A Long March 6C lifts off in August. The rocket’s upper stage later fragmented, creating debris in low Earth orbit. (credit: CASC) Cross the sea by deceiving the sky: Rethinking China’s 2026 debris events by Christopher Stone Monday, September 28, 2026 The ancient Chinese stratagem “Cross the Sea by Deceiving the Sky,” the first of the Thirty-Six Stratagems, rests on a simple principle: conceal a real objective in plain sight by embedding it within something ordinary, repetitive, or apparently benign. When an activity becomes routine, an adversary stops treating it as a warning. Deception succeeds not because the action is invisible, but because everyone sees it and assumes it means something harmless. Could China exploit the effects of repeated apparent accidents as part of a broader counterspace strategy? Modern Chinese gray-zone operations demonstrate why this remains relevant. China’s maritime militia uses ostensibly civilian fishing vessels to establish persistent presence in disputed waters. Survey vessels can conduct apparently peaceful activities while producing strategic access and information. Coast guard encounters can be characterized as routine law enforcement while normalizing a more coercive presence. The objective is not necessarily to conceal the action, but to conceal its strategic purpose. That distinction matters across domains, especially in space. Orbital debris as a stratagem? The conventional explanation for China’s recurring upper-stage and satellite breakups is engineering failure, inadequate passivation, or poor debris management. That explanation may be correct. But another question deserves examination: could China exploit the effects of repeated apparent accidents as part of a broader counterspace strategy? Chinese researchers have explicitly discussed the need to “kill” Starlink. A 2022 paper by researchers associated with the PLA’s Beijing Institute of Tracking and Telecommunications Technology examined Starlink’s military significance and proposed combining “soft kill” and “hard kill” approaches. Subsequent Chinese research has continued examining Starlink as a system whose intelligence, communications, and networking capabilities can contribute to the US military’s “kill chain.” A conventional Western counterspace analysis asks: How could China destroy a satellite? A system-destruction based Chinese analysis asks: How could China impose sufficient effects on a constellation that it can no longer perform its strategic function? Those are fundamentally different problems. Chinese analysts understand from the 2007 and 2014 kinetic ASAT demonstrations that physically destroying satellites can generate debris threatening China’s own spacecraft. Consequently, Chinese writings increasingly examine electronic warfare, cyber operations, directed energy, and other “soft kill” approaches as alternatives to physical destruction. Soft-kill capabilities can impose operational effects while reducing escalation and attribution risks. China therefore understands that debris can be both a cost of space warfare and, potentially, an operational source of strategic effect. The 2026 events The June 2026 Zhuque-2E breakup produced debris across approximately 335 to 423 kilometers altitude, creating an estimated 100 to 150 pieces in a heavily trafficked portion of LEO containing a substantial portion of the Starlink constellation. The August 2026 Long March 6C breakup followed deployment of a seven-satellite rideshare mission. Debris was distributed across approximately 396 to 482 kilometers, again within an orbital regime heavily utilized by Starlink and other spacecraft. It may be creating—or exploiting—conditions in which debris looks accidental, its effects incidental, attribution uncertain, and strategic costs accumulate over time. The September 2026 breakup involved Yaogan-50 (02), a Chinese reconnaissance/remote-sensing satellite launched in March 2026. It operated at approximately 952 kilometers in a highly retrograde, 142-degree inclination orbit. In early September, the spacecraft fragmented, with tracking identifying at least 43 associated debris objects distributed across approximately 600 to 1,100 kilometers, in a high-altitude, highly retrograde regime where debris can persist substantially longer. A debris population does not need to produce a collision to produce military effects. It can increase conjunction assessments, require avoidance maneuvers, consume propellant, impose workload on operators, complicate orbital planning, increase uncertainty, and potentially reduce spacecraft lifetime. The effect can therefore be cumulative rather than spectacular—and remain politically ambiguous. China is building its Starlink competitor, the Thousand Sails constellation. However, its constellation’s orbital distribution does not yet mirror Starlink’s enormous presence across LEO. A debris field therefore does not necessarily impose equal immediate costs on both sides. A minefield does not have to sink a ship to affect naval operations. Its existence changes routing, speed, caution, and resource allocation. Likewise, an orbital debris field does not have to destroy a satellite to affect a constellation. It can make operations more cautious, less predictable, or less operationally efficient. A different way to think about the events This begs a question: “If these events were accidental, did they nevertheless produce strategically significant effects—and could a sophisticated counterspace strategist recognize and exploit those effects?” The answer may ultimately be no. Engineering failures happen. Upper stages fail. Satellites malfunction. Space is increasingly congested. But if repeated Chinese launch and spacecraft failures produce debris in orbital regimes disproportionately occupied by US commercial, military, or intelligence systems; if those events impose greater operational burdens on the United States than China; and if Chinese military literature simultaneously demonstrates an interest in defeating Starlink at the system level, then the recent events deserve examination as more than isolated technical accidents. The most sophisticated application of “Cross the Sea by Deceiving the Sky” may therefore not be deliberately destroying an adversary’s satellites. It may be creating—or exploiting—conditions in which debris looks accidental, its effects incidental, attribution uncertain, and strategic costs accumulate over time. Christopher Stone previously served as Special Assistant to the Deputy Assistant Secretary of Defense for Space Policy (2018–2019). His insights and opinions reflect independent analysis of space deterrence challenges and do not reflect the opinions of the Department of War, United States Government or his employer. The views of the author are his own.

Should Australia Send An Astronaut To the I.S.S.?

Bennell-Pegg Australia’s Katherine Bennell-Pegg completed astronaut training at ESA in 2024 and is awaiting a potential flight to space. (credit: Australian Space Agency) Australia’s $100 million astronaut question: what would it actually buy? by Richard de Grijs Monday, September 28, 2026 Australia may soon have to decide whether sending one of its own astronauts to the International Space Station (ISS) is worth something like A$100 million (US$70 million). The real issue is not simply whether Australia should pay to put an astronaut in orbit, but what national capability it would gain in return. Put that way, the quick answer can sound obvious. A hundred million dollars is a substantial sum for a country with a relatively small civil space budget. An astronaut flight can easily be dismissed as an expensive national prestige project. But that may be the wrong question. The real issue is not simply whether Australia should pay to put an astronaut in orbit, but what national capability it would gain in return. Katherine Bennell-Pegg is not a prospective space tourist. She is an Australian Space Agency employee who completed 13 months of basic astronaut training with the European Space Agency (ESA), graduating in April 2024 as the first qualified astronaut under the Australian flag. She is now eligible for assignment to future human-spaceflight missions, including to the ISS. Australia now has an opportunity to turn that qualification into an operational mission through enhanced cooperation with ESA. With the ISS approaching retirement around 2030 and mission opportunities allocated well in advance, the window for turning that qualification into a flight is narrowing. The campaign gained new momentum in September when mining giant BHP committed A$1 million, conditional on federal government support. The funding would support education and outreach connecting the mission with schools and regional communities. Australian aerospace and defense company Nova Systems has separately committed A$1 million in cash and in-kind support, including access to aircraft for microgravity experiment development and expertise in systems engineering, mission integration and launch safety. Those commitments materially change the proposition. They also sharpen the question Canberra needs to answer: if Australia spends close to A$100 million, what exactly would it be buying? Not simply a ticket The first complication is that the widely reported A$100 million figure is an estimate rather than an agreed mission price. An astronaut mission could therefore be treated as an isolated national event, or used to deepen a relationship that already exists. The parameters of any mission and the associated Australian contribution would have to be negotiated. Supporters of the mission argue that describing the expenditure as purchasing an astronaut “ticket” misunderstands the premise of the model under consideration. The proposal is instead for a government-to-government cooperation framework with ESA that could embed Australian research, industry, and technology in the mission itself. Contributions could potentially include funding, technology, infrastructure, or services rather than simply a payment for a seat. That distinction is crucial. Australia could spend a large sum to put its flag on an astronaut’s spacesuit and receive little enduring benefit once the mission is over. Or it could use the flight as the centerpiece of a broader agreement that gives Australian researchers, companies, and engineers access to international programs and experience they would struggle to acquire independently. The flight itself is therefore the least interesting part of the proposition. Australia has already made the first investment Australia has already spent public money creating the capability. The Australian Space Agency paid about A$466,000 (US$330,000) for Bennell-Pegg’s basic ESA astronaut training. That investment provided training in areas such as spacecraft systems, robotics, life support, spacewalking, survival, and medical operations. At the time, the obvious question was what Australia would do with a trained astronaut if there were no flight opportunity. Two years later, that question has become more concrete. Australia has also been steadily deepening its relationship with ESA. In 2025, the Australian government announced negotiations towards a formal Cooperative Agreement. ESA operates major deep-space communications infrastructure at New Norcia in Western Australia, while Australian researchers and companies already interact with European space programs. An astronaut mission could therefore be treated as an isolated national event, or used to deepen a relationship that already exists. That second model is the one that deserves serious consideration. What could Australia put on the mission? Scientific return provides one obvious test. Australia already has researchers developing experiments for microgravity. Medical and biotechnology research is particularly promising because cells, tissues, and biological systems can behave differently in microgravity, providing experimental conditions that cannot be reproduced straightforwardly on Earth. Australian researchers are already working on microgravity projects involving cancer biology, regenerative medicine and plant science. Professor Fiona Wood, known internationally for her work on burns treatment, has been associated with proposals to use a Bennell-Pegg mission to investigate regenerative processes with potential relevance to wound healing. There are similarly natural connections with areas in which Australian industry has unusual strengths. Mining has made Australia a world leader in operating complex machinery remotely across enormous distances. Autonomous haulage, field robotics, communications, remote asset management and the operation of equipment in hazardous environments all have obvious analogues in lunar and planetary exploration. The involvement of BHP is therefore more interesting than a corporate sponsorship announcement might suggest. Australia does not build human-rated launch vehicles or operate its own space station. But it does possess expertise in technologies that increasingly matter as space exploration moves from short visits towards sustained operations: robotics, autonomous systems, resource processing, remote medicine, and communications. A well-designed agreement could use an astronaut mission to connect some of those capabilities with ESA’s much larger exploration ecosystem. The economic case requires more care This is also where advocates need to be cautious. Space investment is often accompanied by impressive claims about economic multipliers. Some are well supported; others become detached from the conditions that produced them. But inspiration alone cannot justify an investment on this scale. The mission needs to leave infrastructure, skills, relationships and opportunities behind. A major UK government evaluation published in 2025 estimated that every £1 of British public investment in ESA generated £7.49 in direct benefits to the UK economy. Firms receiving ESA contracts experienced gains in turnover, employment, productivity, and private research and development. The study also identified spillovers into non-space sectors. That is meaningful evidence that participation in a large international space organization can generate economic benefits well beyond the initial government contribution. However, it is not evidence that Australia could spend A$100 million on one astronaut mission and automatically receive A$749 million back. Britain is a longstanding ESA member with a well-established industrial base, extensive participation in ESA programs and mechanisms through which national contributions are returned as contracts and research activity. Australia does not yet have an equivalent relationship. That difference should sit at the center of Canberra’s decision. The relevant question is not whether ESA participation has produced economic returns elsewhere. It clearly has. Instead, the question is how much of the Australian contribution would create comparable pathways for Australian organizations. And that depends on the agreement. Set the conditions before signing the check A decision to support the mission should therefore come with measurable expectations: How much Australian research would fly? How many Australian companies would receive contracts or become integrated into ESA supply chains? Would Australian engineers participate in mission preparation and operations? Would the partnership create continuing access to ESA facilities, programs or research opportunities after Bennell-Pegg returned to Earth? Would technologies developed for the mission remain useful to Australian companies in mining, medicine, robotics, advanced manufacturing or other sectors? And, perhaps most importantly, would this be the beginning of a sustained Australian relationship with human spaceflight and exploration, or an exceptional mission that may not be repeated? These questions are more useful than trying to attach an abstract monetary value to national inspiration. Inspiration certainly matters. Bennell-Pegg has already become a highly visible advocate for science and technology education, and BHP’s contribution is explicitly intended to extend the mission into schools and regional communities. Australia faces persistent concerns about its STEM workforce, and astronauts command a public visibility few other scientists or engineers can match. But inspiration alone cannot justify an investment on this scale. The mission needs to leave infrastructure, skills, relationships and opportunities behind. A small country does not need a small ambition Australia faces a familiar space policy dilemma. It has neither the resources nor a compelling reason to reproduce the complete human spaceflight infrastructure of the US, China, or Europe. Building an independent astronaut corps, launch system, and orbital facilities would make little economic sense. The opportunity is real, but so is the cost. The government’s task should therefore be to negotiate backwards from the legacy it wants. International partnership offers another route. Countries can acquire capabilities by contributing areas in which they have genuine expertise to much larger cooperative programs. Canada’s robotics contribution to human spaceflight is the classic example. Japan converted major infrastructure and technology contributions into a sustained role aboard the ISS. Australia is not Canada or Japan. Its space sector is smaller and its relationship with ESA much less mature. But that makes the structure of this prospective mission more important, not less. The strongest argument for flying Bennell-Pegg is not that Australia deserves an astronaut in orbit. Nor is A$100 million a trivial price for national prestige. It is not. It is that Australia already possesses a qualified astronaut, nurtures an increasingly important relationship with ESA, and has domestic scientific and industrial capabilities that could benefit from deeper participation in international human spaceflight. The opportunity is real, but so is the cost. The government’s task should therefore be to negotiate backwards from the legacy it wants. If Australia can turn the mission into research access, industrial contracts, operational experience, international partnerships and capabilities that remain useful long after Bennell-Pegg lands, then the expenditure should be judged as investment in a wider space ecosystem. If it cannot, A$100 million starts looking much more like the price of a very expensive seat. Richard de Grijs is Professor of Physics and Astronomy at Macquarie University (Sydney, Australia) and former Executive Director of the International Space Science Institute-Beijing.

Coming To Terms With The End of The Falcon 9

Falcon 9 launch A Falcon 9 lifts off September 13 carrying three O3b mPower satellites for SES. (credit: Katalyst Space) Coming to terms with the end of the Falcon 9 by Jeff Foust Monday, September 21, 2026 Last week, space industry executives gathered in Paris for the annual World Space Business Week conference, an opportunity to discuss the state of the commercial space field as well as make deals and announce contracts. “Without naming names, we all know who the go-to easy button was for many years” when it came to launch, said Crain. This year, there were few contracts to announce since the conference was preempted by the International Space Summit, held the preceding week also in Paris. The French government, which organized the summit, encouraged French and other European space companies to make their major announcements there, ranging from launch contracts by Arianespace to satellite manufacturing awards for IRIS², the European secure connectivity constellation. There was, though, plenty to talk about at World Space Business Week beyond contracts. The biggest theme to emerge from both onstage and offstage discussions was that the launch constraints the industry was facing, with demand for launches outstripping supply, may soon get much worse before it gets better. “It seems like all anyone is talking about this week is access to launchers,” said Jeff Thornburg, CEO of Portal Space Systems, a company developing highly maneuverable spacecraft, on one conference panel. The reason it was a hot topic in Paris was not just the problems with existing vehicles, like Blue Origin’s New Glenn and ULA’s Vulcan, which remain grounded, or new vehicles whose first flights keep getting delayed (see “Wishing for rockets”, The Space Review, August 17, 2026.) It was the realization that the rocket that has been the workhorse for the commercial space industry in recent years, SpaceX’s Falcon 9, is going away. SpaceX has not made a formal announcement about the future of the Falcon 9. Earlier this year, though, companies said that SpaceX had stopped taking reservations for rideshare launches beyond late 2028 or early 2029. At World Space Business Week, executives said privately that it was now effectively impossible to buy a Falcon 9 for any commercial mission, either for a rideshare flight or a dedicated launch of a larger satellite or constellation of spacecraft. That is becoming a problem for an industry that had relied on the Falcon 9 as much for its availability as for its price. The Falcon 9 flew 165 times last year and SpaceX executives has previously said they were willing to balance its own demand on the rocket for the Starlink constellation with commercial customers. “Without naming names, we all know who the go-to easy button was for many years” when it came to launch, said Tim Crain, senior vice president and chief technology officer of Intuitive Machines, at the conference. His company has used the Falcon 9 for launching its lunar landers while customers of its satellite manufacturing unit, the former Lanteris Space Systems acquired last year, turned to Falcon 9 for launching large GEO communications satellites. Access to space is “the critical supply chain issue” for the industry, he added. “If we don’t obsolete our own products and services, someone’s going to find a way to obsolete them for us,” Shotwell said. “Look at what we did to the market, right?” That leaves companies worried about where they’ll go for launch when that easy button no longer works. “It would be very undesirable that the key launch service provider for us disappears from the market, so we obviously don’t want to see that,” said Peter Olsen, CEO of Space Norway Satcom, an operator of communications satellites that has previously used the Falcon 9 with a contract for an upcoming launch as well. While the withdrawal of the Falcon 9 from the commercial launch market was something of a revelation at the conference, it was, to some, not a surprise. “This situation was totally predictable. Everybody knew it was going to happen,” said Jean-Luc Maria, CEO of Exotrail, a French company developing orbital transfer vehicles. “You could really see this coming a few months ago. At least, we did,” said Thornburg, whose company announced last month it signed a contract for a Falcon 9 launch of its first Supernova spacecraft—perhaps one of the last commercial Falcon 9 contracts. Portal is working with launch aggregator Maverick Space Systems to sell excess capacity on the launch for rideshare payloads, including a deal announced at the conference to fly ten satellites for Kepler Communications’ data-relay constellation. SpaceX has dropped hints that it would phase out the Falcon 9 in the coming years. “While we have steadily increased our Falcon 9 launch cadence over recent years, we expect Falcon 9 launches to decrease over time,” the company said in May in the prospectus for its initial public offering. That document also suggested that commercial launches would be the first to be wound down for the Falcon 9 while the vehicle continues to fly for government customers. “As Starship progresses toward full operational utilization, the Falcon 9 and Falcon Heavy platforms will remain key assets for specialized missions, including NASA crew rotations and national security payloads,” it stated. SpaceX was absent from launch discussions at World Space Business Week, skipping the conference’s traditional launch panel. Gwynne Shotwell, president and COO of SpaceX, instead appeared at the All-In Summit where she suggested the company was willing to disrupt itself by ending Falcon 9 to focus on Starship. “If we don’t obsolete our own products and services, someone’s going to find a way to obsolete them for us,” she said. “Look at what we did to the market, right? The analogy is there. They were caught flatfooted. We crushed them. Now we want to make sure we are not flatfooted.” The simplest answer is that customers who had used the Falcon 9 will shift to Starship, which is expected to make its first orbital launch as soon as next Monday. However, there remain several concerns in the industry about that, including how available Starship will be for commercial customers. The vehicle will be busy launching next-generation Starlink satellites and Starmind orbital data center spacecraft, as well as supporting NASA’s Artemis missions. There are also issues about the compatibility of commercial satellites with Starship, which initially will have a unique slot-shaped payload bay door. That works well for the “flatsat” designs SpaceX has developed for Starlink and Starmind, but not for more traditional commercial satellites. The company has offered a version with a larger clamshell payload bay door for larger spacecraft, but it’s unclear how available that will be. Starship also does not help on the smaller end of the market, those smallsats that had relied on Falcon 9 rideshare missions for regular and relatively inexpensive access to Sun-synchronous and mid-inclination orbits. SpaceX has hinted in the past it might offer a similar rideshare program for Starship, although the vehicle would likely be oversized for that application. Another simple answer is for other launch companies to step into the gap created by the departing Falcon 9. That has proven to be easier said than done, though, as companies face delays with the first launches and challenges scaling up launches. “There’s two years to go displace what Falcon 9 did, and there’s a couple providers out there trying to do that,“ said Jenkins. “I think they need to hit the gas pedal on it.” “Every single design decision has been thought through to ensure very rapid producibility,” said Jordan Charles, senior vice president of New Glenn at Blue Origin, during the conference’s launch panel. He cited work on an upgraded version of that rocket, called the New Glenn 9x4. “Our vision, our goal for 9x4, is to be operating north of 100 launches a year. That system—the design, everything about it—is intended to scale to those rates.” He did not, though, disclose a timeline for getting to 100 launches a year or intermediate steps along the way, other than reiterating that the company was still working to resume New Glenn launches by the end of this year after a pad explosion in late May. Other launch companies have more modest goals. Arianespace is seeking to reach the current limit of nine to ten Ariane 6 launches a year in 2027, as it works with ESA on studies of potentially increasing that launch rate to as high as 20 per year. “Currently, we are looking at the investment required and, let's say, the overall business case for a cadence increase,” Arianespace CEO David Cavaillolès said on the panel. That would require investments in increased production of vehicles, including solid-propellant boosters, and potentially upgrades to the launch site in French Guiana. “We'll see if we go to 11, 12, 15, or beyond,” he said. “But clearly, we want to be there for our clients.” (Arianespace set a goal this year of seven to eight launches, but has done only four to date, with engine issues reportedly limiting the company to just one or two more launches this year.) At the conference there was a desire by some launch customers, bordering on impatience, for Falcon 9 alternatives. “We have launch vehicles that have not met the timelines they originally promised to be competitive with Falcon 9,” said Thornburg. “There’s got to be a lot of advancement in the next two years,” said Matt Jenkins, chief space systems officer at Vantor, an Earth imaging company previously known as Maxar Intelligence. “There’s two years to go displace what Falcon 9 did, and there’s a couple providers out there trying to do that. I think they need to hit the gas pedal on it.” There are some signs of progress. Earlier this month, Stoke Space announced it raised $1 billion to advance work on its fully reusable launch system called Nova. The company also announced it would scale up the original Nova, now called Nova Pathfinder and capable of placing several tons into low Earth orbit, to the larger Nova Block 2, with a capacity of 15 metric tons. “What we’ve seen in the last year is an explosion in demand for more capable and higher quantities of satellites,” said Stoke Space CEO Andy Lapsa. “We think that we can fly at rate and fly full payloads at the 15-ton capacity.” However, the Nova Block 2 won’t be ready until 2029, with Nova Pathfinder making “multiple” launches in 2027 and 2028 ahead of Block 2’s debut. Based on the experience of past vehicles, it will take several years for Nova Block 2 or other new vehicles in the same payload class—Relativity Space’s Terran R, Rocket Lab’s Neutron, or the joint Firefly Aerospace-Northrop Grumman Eclipse—to start flying at a useful cadence. The problem is worse for smallsat customers who had relied on Falcon 9 rideshare launches, with few options open to them. In an earnings call earlier in the month, Giulio Ranzo, CEO of Avio, said his company has seen a steady stream of smallsat customers interested in his company’s Vega C. “We have a whole bunch of customers coming to us and saying, ‘Oh my God, can you fly us? Because SpaceX no longer gives us a chance to launch,’” he said. “Guess what? The party is finished, and they don’t do that anymore.” However, Avio’s ability to serve those customers is limited. The Vega C has flown twice this year, including a launch of two Earth science satellites for ESA and the European Commission last week, with one more launch expected this year. At the International Space Summit, Ranzo said Avio was looking at ways to increase Vega C’s launch rate to six per year, and then to nine, but did not offer a schedule for doing so. The SpaceX rideshare missions also helped undermine the business case for many small launch vehicles. “What’s happened over the last decade is that one company has dominated this market and it has chilled investment,” said Chris Kemp, CEO of Astra, during one conference panel. Astra had a small launch vehicle, Rocket 3.3, but withdrew it from the market in 2022 after several failures. Kemp argued on the panel that Astra ended that Rocket not because of its checkered flight history but because it was too small to serve a market that had shifted from cubesats to larger spacecraft. He said Astra’s larger Rocket 4, capable of putting up to a ton into LEO, will make its first launch early next year from Wallops Island, Virginia. Astra is planning quarterly launches of Rocket 4 next year as it works to ramp up to weekly launches “within five years.” “What’s happened over the last decade is that one company has dominated this market and it has chilled investment,” said Kemp. In Europe, Isar Aerospace successfully reached orbit for the first time September 5, when the German company’s Spectrum rocket launched for the second time from Norway’s Andøya Spaceport. At a briefing during World Space Business Week, company executives said they are ready to begin commercial launches of the rocket, with a capacity of up to one ton to LEO. Stella Guillen, Isar’s chief commercial officer, said at the briefing that Spectrum’s manifest is fully booked for 2027 and 2028. The company is planning four launches next year and “a little bit more than doubling” that in 2028. Isar’s new factory near Munich can produce up to 40 Spectrum rockets a year. “The market is there and demand is super high,” she said. “What we’re trying to do is scale up as much as we can.” She said that customers are increasingly worried about how they will get their satellites to orbit as the Falcon 9 phases out. “Now there is suddenly this panic mode for 2028 and 2029,” she noted. Others, though, said companies that once pressed the easy button of SpaceX should avoid now hitting the panic button. “We seem to see a lot of panic in the industry over the lack of capacity,” said Portal’s Thornburg. “That’s what gets written, but I don’t believe that’s really the case. I think it’s the lack of ability of the current capacity to meet the growing demand.” “Realistically, people are going to jump into that opportunity and come in to replace that Falcon 9 capacity,” he predicted. That capacity, most in the industry expect, will eventually be replaced, either by SpaceX itself with Starship or competing vehicles. However, they also expect a crunch around the end of the decade as Falcon 9 exits the commercial market while those replacements are still working to fly at sufficient rates to replace that capacity. “Don’t panic. I don’t think this is a structural problem. I think it’s a temporary gap,” said Renato Panesi, chief commercial officer of D-Orbit, which develops orbital transfer vehicles that have flown on many SpaceX rideshare missions. “The critical moment will be 2029 and 2030, and maybe 2031,” he predicted. “That specific window is risky because I think new entrants will not have the launch cadence needed to meet the market demand.” D-Orbit has worked to mitigate its risk by buying launches from others, including Isar Aerospace and Spanish small launch company PLD Space. “I’m really confident that there will be just a small period of time where it will be difficult to have access to space,” Exotrail’s Maria said. “For me, the problem will be solved.” The solutions that emerge, though, may not be everyone. “You have the very small players, cubesats. I think some of them are in trouble because it will be very difficult to access space,” he said. The industry left Paris last week less hopeful about the future than hoping that alternatives will emerge in time. “There’s a lot of development going on,” said Intuitive Machines’ Crain. “What we’re seeing now is the opportunity for the rest of the market to step up and expand and fill the gap.” Jeff Foust (jeff@thespacereview.com) is the editor and publisher of The Space Review, and a senior staff writer with SpaceNews. He also operates the Spacetoday.net web site. Views and opinions expressed in this article are those of the author alone.

The E-3 Samos Program

Samos The first Samos E-1 reconnaissance satellite was launched in October 1960 but failed to reach orbit. The E-1 and E-2 satellites used film-readout technology. The Samos E-3 was a successor proposed in July 1959 using a newer technology and having higher resolution. It was never built. (credit: Peter Hunter Collection) To E-3 or not to E-3: the liminal Samos E-3 program by Dwayne A. Day Monday, September 21, 2026 Samos was the United States’ first reconnaissance satellite program, emerging from a US Air Force project known as Weapons System 117L in 1957. Briefly named Sentry, the renamed Samos quickly expanded into more than a half-dozen different satellite types, resulting in 11 flights, including several launch failures. Because Samos was unsuccessful, it is mostly forgotten in histories of the early space program. But Samos is also problematic because although the Air Force preserved substantial programmatic records, relatively few technical records, illustrations, and photographs survive. It is therefore possible to write a history about when Samos was started and evolved and what decisions were made along the way, but more difficult to describe how each of the spacecraft worked, or show what they looked like Samos A September 1959 Lockheed illustration of the Samos E-3 satellite. The primary optics, which would have gathered the light to focus inside the camera, are omitted. Unfortunately, the source documents are blurry and not high quality, making some of the labels difficult to read. The Samos E-3 was canceled by December 1959. (credit: NRO) From October 1960 to November 1962, the Air Force launched nearly a dozen Samos satellites with designations E-1, E-2, E-5, and E-6. But no Samos E-3 or E-4 satellites were ever launched, making them the most emblematic spacecraft in the Samos program. The E-4 was a mapping camera that was built but never flown, whereas the E-3 only existed for the second half of 1959, never even getting off the drawing board. The Samos E-3 emerged because the limitations of film readout were becoming apparent by summer 1959, but some in the Pentagon did not want to abandon a requirement to return imagery to the ground soon after the photographs were taken, even if very few photographs were actually taken. The Samos E-3 was the ultimate liminal system, caught between two worlds: the readout technology that was fading due to its limitations and the film-return technology that would dominate US satellite reconnaissance for the next two decades. Samos The Samos program consisted of visual reconnaissance satellites with an "E" designation and signals intelligence satellites with an "F" designation. The E-4 and E-5 were never built or flown. In addition to the satellites listed here, the Samos E-6 was also built and flown, but was unsuccessful. (credit: NRO) The Samos E series Samos was initially the overall name for a series of subsystems including the satellite, propulsion system, and payloads that were given letter designations A through G: A for airframe, B for propulsion, C for auxiliary power, D for guidance and control, and G for infrared (missile warning). Most of these designations were quickly abandoned or forgotten by those working on the program except for Samos E, which designated photographic reconnaissance satellites, and Samos F, which designated signals intelligence collection satellites. Both the E and F subsystems soon produced multiple variants. Samos The Samos program had major subsystems designated A-G (later adding subsystem H). In practice, most of these designations were ignored other than Samos E and Samos F. (credit: NRO) In early 1958, a project was spun-off from the Samos E-series. It was a small recoverable satellite that would return its film to the ground. It was given the codename CORONA, and the camera system was designed and built by Itek and managed by the CIA, with the Air Force responsible for launch and tracking and spacecraft operations and recovery. CORONA was covert, meaning that its existence was classified, unknown even to most of the Air Force and contractor personnel working on Samos. Samos E-1 and E-2 were “film-relay” satellites that recorded images on film, developed the film inside the satellite, and scanned that film for relay to Earth via radio transmission. The Samos E-1 was primarily a proof-of-concept system, with the Samos E-2 being the operational system. Up until late 1959, the Air Force expected that eventually multiple Samos E-2 satellites would fly and become the primary Air Force reconnaissance satellite. Samos The Samos E-1 satellite. Film-readout technology had existed in some form for many years. Samos was applying it to a satellite. But it had substantial limitations, leading to a search for better technologies. (credit: Peter Hunter Collection) By 1959, due to the limitations of the E-2’s film-readout technology, the Air Force began considering Samos film-return systems as well, soon leading to the E-4 and E-5 systems in the first half of 1959, and later the E-6 system. Samos E-5 was a high-resolution “film-return” system that took photographs on film and then returned both the film and the camera to Earth inside a large reentry vehicle. “High resolution” meant the ability to spot images on the ground five feet (1.5 meters) large. The Samos E-6, which did not start until 1960, was a broader area reconnaissance satellite. Its photos covered more territory than the E-5, were taken by two cameras operating in stereo mode, and were also recorded on film, but the E-6’s ground resolution was not as good as the E-5. The Samos E-6 film, but not the camera, would be returned to Earth inside a reentry vehicle smaller and pointier than the E-5. The E-4 was a mapping system that would use the same large reentry vehicle as the E-5. Although E-4 mapping cameras were apparently produced, the program was canceled at least in part due to bureaucratic in-fighting, with the US Army insisting that it, and not the Air Force, was responsible for mapping the Earth. Samos This 1959 illustration shows the overall layout of the Samos vehicles. The payloads were different for each of the E-series. (credit: NRO) The Samos E-3 system Lockheed, which was building the Agena spacecraft that supported all the Samos payloads, proposed the Samos E-3 on July 29, 1959, according to an official history of early satellite programs. The history indicates that Lockheed may have assumed that the Advanced Research Projects Agency (ARPA) then running the overall program was more interested in readout satellites like the E-1 and E-2 than in film-return satellites. Lockheed therefore proposed the E-3 as the next step in technology that could return images to Earth relatively quickly, with the goal of achieving five-foot resolution. One of the limitations of the Samos E-2 was that the film supply was finite: once it was used up, the satellite could no longer operate. In contrast, the Samos E-3’s electrostatic storage tape could be reused. Lockheed asserted that the E-2 was “based on pre-1959 concepts” and a new requirement for five-foot ground resolution required new readout technology. The E-2 was a hybrid system, using both mechanical and film development as well as electronic readout. By using a new “electronic tape,” the Samos E-3’s “all-electronic approach would provide the highest possible performance in the earliest time period at minimum cost.” Lockheed asserted that electronic tape systems had already been proven under Aeronautical Research Laboratory contracts at the Wright Air Development Center in Ohio, and claimed that the performance was excellent. Samos The Samos E-3 would have used a new electrostatic tape system for recording images onto a tape storage medium. The images would then be extracted from that tape and transmitted to the ground. The tape was intended to be reusable. (credit: NRO) For the Samos E-3, an image would be recorded on photoelectric-sensitive electrostatic tape. It would then be read out “by deflecting the modulation of an electron beam to scan a portion of the tape, and the view signal amplified and then applied as a modulating signal for transmission to ground stations.” Using a transmission system with a bandwidth of 12 megacycles per second—which would require new tubes to be developed—the system could achieve a readout time of 8.7 seconds per frame. On the ground, the images would then be read on to film for the best possible reproduction. Samos Images taken by a Samos E-3 satellite in space would be transmitted to the ground and then directly read-onto film. Film was a storage medium capable of holding a tremendous amount of data. (credit: NRO) One of the limitations of the Samos E-2 was that the film supply was finite: once it was used up, the satellite could no longer operate. In contrast, the Samos E-3’s electrostatic storage tape could be reused. This, combined with a higher orbit, meant that the Samos E-3 satellite could operate for a year in space. The goals for the E-3 Visual Reconnaissance System were: Active life of approximately one year. Ground resolution of five feet, or 2.5 feet (0.75 meters) with a power changer [unexplained]. Optics of 144 inches (366 centimeters) effective focal length, with F/4.5 optics. Sensor electrostatic storage tape, which would be 60 feet (18 meters) long and reusable. Readout would be an electron beam directly from tape. Ground reconstruction would be an electron beam film recorder operating in vertical, oblique, and stereo modes. The Samos E-3 satellite would operate in a nominally circular orbit at an altitude of 483 kilometers (300 miles). This was a tradeoff. It would be easier to achieve higher resolution in a lower orbit. But a lower orbit would have greater atmospheric drag, decreasing the satellite’s lifetime. The 483-kilometer orbit therefore required a more powerful optical system because the satellite was farther from the targets it was photographing. Samos E-3’s proponents expected that having an all-electronic visual reconnaissance equipment would also maximize optical resolution. Samos A schematic showing the Samos E-3's camera system. Lockheed's illustrations omitted the optics that would focus the image onto the storage medium. Lockheed referred to this as an "all electronic" design because it did not require the film and chemicals used for the E-1/E-2 film-readout technnology. (credit: NRO) As a satellite moves over the Earth, the image inside its camera system also moves. Reconnaissance satellites required some method of compensating for the image motion inside the camera. For the Samos E-3, the exposure period would be only one millisecond, which would hopefully simplify the vehicle attitude control and the camera image-motion compensation. According to Lockheed, the approach provided a very high degree of flexibility in operational use and performance capability. “The system provides a very high resolution capability and, through the use of the reusable image storage medium, permits a payload design of minimum size and weight.” “Breadboard designs of this camera have already been built and tested by Radio Corporation of America, Astro-electronic Products Division.” Lockheed claimed that they determined that it was “technically feasible.” The proposal contains no discussion of the payload optics other than the bare basics. The Samos E-3 was the ultimate liminal system, caught between two worlds: the readout technology that was fading due to its limitations and the film-return technology that would dominate US satellite reconnaissance for the next two decades. The available technical schematics for the proposed satellite payload are simple and difficult to read due to poor reproduction. The “primary optics” that would have gathered light and sent it to the electrostatic tape camera are not described. The overall proposal reads like the kind of reconnaissance payload one would expect from a spacecraft designer rather than a camera designer: for instance, Lockheed lists the focal length as 44 inches (112 centimeters) in one part of a document and 144 inches in another part. That was one of the problems that plagued the Samos program, particularly the E-5 which had a camera that was compromised from the start. In contrast, CIA-led reconnaissance programs like the CORONA tended to maximize camera performance over other criteria. Samos The system for converting the images to stored data in the E-3 camera. Unfortunately, the source documents are blurry and not high quality, making some of the labels difficult to read.(credit: NRO) A short life, a quick death The Samos E-3 would have used the same Atlas rocket that was used for the E-1, E-2, E-5, and E-6. The Air Force’s view was that the Atlas was available, and capable. But Atlas was not cheap, which is why both CORONA and later signals intelligence satellites used the less expensive Thor instead. In December 1959, the Air Force approved the recoverable Samos E-5 to satisfy the five-foot ground resolution requirement and ordered Lockheed to cancel any work on the Samos E-3. ARPA had annoyed the military services with its overall management of military space programs and was removed from having any control over Samos by the middle of 1960. Samos A general early timeline for the American reconnaissance satellite program. Although a major contract was awarded to Lockheed in 1956, it was not until after the October 1957 Sputnik launch that the program began to receive the necessary funding to proceed. (credit: NRO) The first Samos E-1 launched in October 1960 but failed to reach orbit. The second launched in January 1961 and had limited success. A Samos E-2 blew up on its launch pad in September 1961, putting an end to the film-readout program. Three Samos E-5s and five Samos E-6s were launched between November 1961 and November 1962, and all suffered various launch, operational, or recovery failures. But Samos E-3 never even got that far, being canceled while still in the laboratory stage, and quickly forgotten. Sources HEXAGON Mapping Camera History, National Reconnaissance Office, June 1979, pp. 43-44. LMSD Satellite Systems Briefing Part II, The SAMOS Program, September 14, 1959. Dwayne Day can be reached at zirconic1@cox.net. Special thanks to Steve Schultz.