On Oct. 1 and early Oct. 2, SpaceX completed a remarkable launch sequence. NASA’s Crew-13 lifted from Cape Canaveral on a Falcon 9. Roughly three hours later, Transporter-18 launched 130 rideshare payloads from Vandenberg. Before midnight in Florida, a Falcon Heavy launched the classified NROL-97 mission from Kennedy Space Center. Three launches, three pads, two coasts, and less than 13 hours separated the first liftoff from the third.
That is an extraordinary demonstration of American launch capacity. It also illustrates a distinction Washington should make explicit as it pursues President Donald Trump’s goal of more than 1,000 launches and reentries a year by 2030: throughput and resilience are not the same metric.
All three missions were launched by one company. That does not diminish the achievement. In fact, the use of multiple pads and both coasts shows meaningful redundancy within a single provider. But it also shows why a raw launch count cannot tell the government how many alternatives remain when a particular provider, vehicle family, propulsion system, pad, range, or supplier is unavailable.
Three days earlier, Starship reached orbit for the first time and deployed 26 Starlink V3 satellites, even though an engine problem shortened the planned flight. The milestone adds future capacity. The policy question is how much of America’s growing capacity can substitute for another path under the specific failure the government is planning against.
Trump’s Aug. 20 National Space Transportation Policy already points in that direction. It sets the 1,000-launch benchmark while also directing agencies to build a competitive and resilient industrial base, preserve multiple avenues for government payloads, develop adaptable interfaces for remanifesting spacecraft, and evaluate whether high-priority missions can receive responsive access to space on timelines as short as 48 hours. The Transportation Department has begun implementing the policy through its SPACE Task Force.
Seven providers are not seven interchangeable launch stacks
The Space Force expanded its National Security Space Launch Phase 3 Lane 1 pool to seven providers in July. That is meaningful competition, and the bench is continuing to mature. NASA added Relativity Space’s Terran R to its launch-services contract in September, while Impulse Space won another Space Force award later that month.
But a contract roster still is not an operational substitution map. Impulse entered Lane 1 as the first upper-stage prime; its Helios stage must ride on a separate medium-lift launch vehicle and is scheduled for first flight in 2027. Relativity says Terran R is progressing toward a first flight in late 2026. Stoke Space’s first orbital Nova configuration is also still ahead of first flight. These companies may become important alternatives. Future capacity and capacity available today should not be counted as the same thing.
Shared hardware creates another layer. Blue Origin’s New Glenn uses BE-4 engines, as does United Launch Alliance’s Vulcan. A common engine family does not mean a defect in one vehicle automatically affects the other, and it should not be treated that way. It does mean that two corporate brands can share an industrial dependency that belongs on a resilience map.
Independence is failure-specific, not absolute
The right question is not whether two launch paths are completely independent. Very few complex systems are. The useful question is whether they are sufficiently independent of the failure being planned against.
The SpaceX tripleheader makes that clear. A closure at one launch pad would not necessarily stop missions from the other two. A problem limited to one coast would leave capacity on the other. But a provider-wide grounding or a failure affecting a shared vehicle architecture would cut across more of the schedule. The same logic applies across companies: a second prime contractor adds more resilience when it does not share the dependency that caused the first path to fail.
Blue Origin’s May New Glenn hot-fire anomaly offers a useful example without turning the company into a cautionary tale. The event damaged launch-support hardware at Launch Complex 36. Blue Origin responded by rebuilding the pad, beginning work on a second pad, LC-36B, and arranging with NASA to perform upper-stage hot-fire testing at Stennis Space Center. Those investments create physical alternatives. They are exactly the kind of redundancy a national launch strategy should be able to see and credit.
Measure time to substitute, not only provider count
Space Systems Command has already demonstrated what genuine substitution looks like. In an August review of its first five years, SSC said it had executed several payload swaps between launch providers and launched three of those missions within two months of contract modification. That operational record suggests a practical companion metric to launch cadence: time to substitute.
For each high-priority mission, acquisition teams could maintain a compact dependency map showing the launch vehicle, propulsion family, critical suppliers, pad, range, integration flow, and the estimated time required to move the payload to another viable option. The map should be tested against specific failure classes: loss of a pad, range closure, grounding of a vehicle family, supplier disruption or a regulatory hold.
This would not punish commonality. Shared components can lower costs, simplify maintenance, and accelerate production. Nor should every mission require a completely separate industrial base. The purpose is visibility: if one dependency goes offline, leaders should know which missions still have a usable path and how long the switch will take.
That approach fits the administration’s existing policy rather than adding a competing one. The White House memorandum already calls for multiple avenues to deploy government payloads, adaptable interfaces, rapid restoration after launch-system failures, and resilient infrastructure. An independence map and a time-to-substitute measure would turn those goals into operational evidence.
ELON MUSK BUILT THE ROCKETS. WASHINGTON FORGOT TO BUILD THE ROADS
A thousand launches and reentries a year would measure extraordinary U.S. capacity. Assured access requires a second measure: after a specific failure, how many priority missions still have a viable path to orbit, and how quickly can they move to it?
America needs both cadence and substitutability.
Burak Oktenli is a graduate student in Applied Intelligence at Georgetown University and an independent researcher focused on trustworthy AI, cybersecurity, autonomous systems, and high-consequence technology governance. He holds a bachelor’s degree in Computer Science and Engineering from the University of South Florida and an MBA.