ULA plans a November 13 return to flight for Vulcan, carrying Amazon Leo satellites as the company works to restore customer confidence after booster-nozzle failures. The episode also covers the Pentagon’s new commercial space reserve, an Air Force cargo-recovery test and claims about satellite cooperation.
Chapters
00:00 Today's headlines
00:46 Six space-tracking contracts under CASR
03:13 Air Force recovered Starfall cargo pods
04:45 Putin claim of contact with Musk
06:06 Ship 42 completes six-engine static fire
07:29 Vulcan plans return on November 13
10:13 Vulcan flight would test nozzle changes
Source links
Source links
Space Stakes is an AI-voiced podcast, built and run by a real person. Nothing in this episode is financial advice.
Follow Space Stakes: subscribe on YouTube · Apple Podcasts · Spotify
More from Brian Lampert: Quickly Quantum, the daily quantum computing briefing, and Concrete Compute, the daily AI infrastructure briefing. Transcripts and every episode: space-stakes.kngoworld.chatgpt.site.
The money, missions, and power shaping space. Space Stakes is a daily briefing on the business of the new space race — launches, contracts, constellations, and the capital behind them. Every episode cuts through the industry's hype: signed contracts vs. paper constellations, funded orders vs. "up to" ceilings, launch dates vs. track records. Who pays, who profits, and who actually delivers — told so both aerospace insiders and curious newcomers finish feeling it was made for them. Space Stakes is an AI-voiced podcast, created and built by a real human, Brian Lampert. Nothing on this show is financial advice.
Also from Brian Lampert: Quickly Quantum and Concrete Compute.
United Launch Alliance plans to return Vulcan to service on November 13, carrying 40 Amazon Leo satellites on the first of 38 Vulcan flights Amazon has booked. The date is pending range approval, and the rocket is returning after solid rocket booster nozzle failures on two of its first four missions. Amazon’s broadband deployment and national-security launches both depend on Vulcan proving the improved nozzle design in flight. What will this mission actually establish? We’ll separate what ULA says it changed from what only flight data can confirm. Welcome back to Space Stakes, your daily brief on the business of space. It's Thursday, October 29, 2026. Let's get into it.
A commercial space reserve is now operational at the Pentagon, but its first test is modest by design: six contracts for extra space-tracking capacity, with a combined value of $1.37 million. Aviation Week reports that Space Systems Command awarded the first operational contracts under the Commercial Augmentation Space Reserve, or CASR, program after three years of pilot programs. The six companies are Anduril, InTrack Radar Technologies, LeoLabs, Slingshot Aerospace, Australia’s Electro Optic Systems Space Systems and Canada’s NorthStar Earth and Space. Their sensor options include space-based optical systems, ground-based radar, orbital intelligence, and data analysis that combines information from different sources. The military hopes to call on that extra capacity quickly if an unexpected event occurs in orbit.
The first awards are intended to show how the arrangement works in practice. Aviation Week says the Space Force expects the initial awards to inform similar contracts for different mission areas, including satellite communications or launch. Col. Timothy Trimailo, director of the Commercial Space Office, told reporters, “We want to see how it works in practice, and frankly, we want to see how much our operational counterparts call upon it over the next year.”
What does the taxpayer get for that first $1.37 million? A standing way to reach commercial tracking networks when the government needs more observations, and a real-world test of whether those companies can add useful capacity. Aviation Week says the agreements build on earlier pilot efforts, and that the awards came about one year after the service originally anticipated them. The agreements formalize processes already in place through Slingshot’s work with the Joint Commercial Operations cell, a virtual unit that combines unclassified space-tracking data from military, international and commercial partners.
The analogy Aviation Week uses is the Civil Reserve Air Fleet: airlines provide aircraft for military use during a surge. Here, the first mission area is tracking objects in orbit, and the service is working on separate arrangements for other needs. That’s the useful distinction for you: this is an operational contracting mechanism, while the first contracts are a small initial step. Aviation Week also quotes NorthStar spokesperson Delanie Khan-Dobson saying the company can scale support during surge operations and provide sustained space awareness within hours. The practical question is whether operators call on these networks, and whether the information helps them act sooner.
That military interest in commercial capacity also has a physical test attached: the Air Force says it recovered cargo pods flown aboard SpaceX’s Starfall capsule. Space.com reports that the Air Force Research Laboratory completed a point-to-point rocket cargo test and confirmed recovery of the package in the Pacific Ocean. Point-to-point here means using a rocket to move cargo between locations on Earth, via space; this was a test of the idea, not an operational delivery service.
The capsule flew on a Falcon 9 as part of SpaceX’s Bandwagon-5 mission, which lifted off from Cape Canaveral Space Force Station on October 20. Space.com reported that the pods carried representative items including medical equipment, food ration packs and other military kit. Sensors inside monitored temperature during launch, reentry and splashdown, and measured shock and vibration. The point is to learn what the cargo experiences on the trip home.
What would make that useful beyond a successful recovery? AFRL Technology Transition Office director Adam Remaly called it “a critical achievement to demonstrate the potential of Rocket Cargo delivery for point-to-point rapid global mobility for the Future Force,” in a press release cited by Space.com. The lab will assess the recovered data as part of its broader Rocket Cargo initiative. The article also says AFRL conducted a fit check of a UNI-PAC III life raft inside Starfall, which could potentially be included in future tests. That’s a useful sign of what the lab is examining, not proof that rocket cargo is ready for routine delivery. For now, the result is a recovered test payload and data to assess.
From a U.S. military test to a geopolitical claim about satellite networks, Vladimir Putin said Russia maintains contact with SpaceX head Elon Musk and other American partners on low Earth orbit satellite constellations. The Insider reports that Putin made the statement while viewing an exhibition at the Russia–Africa summit in Moscow.
Putin called Musk a “truly brilliant” man, then said, “We are in close contact with American partners, including Mr. Musk, because in orbit it is very important not to interfere with each other and to observe a certain discipline and order.” The Insider also reports Putin said Russia values cooperation with Musk’s company “despite all the political issues” and is developing a domestic Starlink analogue called Rassvet.
What does that claim amount to? Bloomberg’s @business posted on X that Putin said Russia is coordinating on low-Earth-orbit satellite networks with Musk and other U.S. partners despite political tensions between Moscow and Washington. That post describes Putin’s statement; it doesn’t independently verify the coordination. The Insider reports that Rassvet’s commercial launch is planned for next year, with more than 900 satellites anticipated to be in operation by 2035. The distinction matters: a leader’s public account of contact is not the same thing as a documented operational partnership. We have the claim, and the attributed ambition for Russia’s network.
And from claims about coordination to a rocket getting ready for another test, SpaceX has completed a six-engine static-fire test on Starship Ship 42, according to TeslaOracle. A static fire holds a rocket in place while its engines fire, testing hardware before flight. The outlet says the test followed a single-engine static fire on October 27 and a 33-engine test on Super Heavy Booster 22 on October 25.
TeslaOracle says the single-engine test simulated a deorbit burn, a firing intended to push a spacecraft out of orbit toward Earth’s atmosphere. The outlet also reports that SpaceX ran a ship-catch simulation at the Starbase launch tower, using the tower’s mechanical arms to lift and lower Starship 43 while Ship 42 was on a test stand.
There’s a lot packed into that rehearsal: SpaceX is preparing for Flight 15, and the outlet says Elon Musk confirmed on the Q3 2026 earnings call that SpaceX will attempt to catch both the booster and the upper-stage Starship. TeslaOracle says SpaceX has not given a no-earlier-than date, as it awaits final regulatory approval. The outlet says environmental clearance for a Starship catch at Starbase has been obtained. It also says a Starship upper-stage catch would be a first, while SpaceX has caught Super Heavy boosters multiple times. The proposed catch is a demanding test; the date is still unannounced.
That's the rest of the rundown. Now, the story that deserves the long look. Vulcan’s return matters because Amazon has booked it to deploy the bulk of its Leo broadband network, and the U.S. Space Force relies on it for major national-security launches. The question is whether the changes ULA says it made to the solid rocket booster nozzle can earn confidence in flight.
Space - Ars Technica reports that United Launch Alliance announced Wednesday it plans to return Vulcan to service on November 13, nine months after a solid rocket booster anomaly threw the company’s 2026 launch schedule into oblivion. The return-to-flight mission will launch 40 satellites for Amazon Leo, the first of 38 Vulcan flights Amazon has booked. ULA says the launch date is pending range approval.
The failures at issue were in the nozzles of Vulcan’s solid rocket boosters — the parts that direct the hot exhaust to help push the rocket upward. Ars Technica says nozzle failures occurred on two of the rocket’s first four missions, most recently during a flight in February. In both cases, the rocket overcame the nozzle failure and completed its mission. That successful completion matters, but it didn’t erase the concern: officials at the U.S. Space Force, ULA’s primary customer, lost confidence in Vulcan.
There’s real work riding on the next flight. Ars Technica says the Space Force has entrusted Vulcan with roughly half of its major launches through the early 2030s. The Space Force certified Vulcan for national-security launches in 2025, then flew two missions on it before grounding the rocket after the February booster incident. And Amazon’s mission is the first of the 38 Vulcan flights it has booked to deploy the bulk of its network. One flight has to serve two kinds of confidence: the government’s confidence in a launch vehicle for national-security missions, and Amazon’s confidence in the rocket it booked for its constellation.
ULA says its engineers “made great strides” in understanding the February anomaly. The company says engineers “have identified several potential contributors, which have been mitigated through design and process improvements to the nozzle.” That wording matters: ULA describes multiple potential contributors and changes, not a single publicly specified cause. The company says the upcoming launch will use the improved nozzle design, while additional testing and analysis continue in parallel with the mission.
ULA’s stated case is that flying the improved design will provide valuable flight data to validate the improvements and is the most beneficial path in support of its customers. For you, the important distinction is that the flight is both a return to service and a test of the design changes under actual launch conditions. The mission’s payload is concrete — 40 Amazon Leo satellites — while the broader confidence question applies to future commercial and national-security work.
But the flight data ULA wants is exactly what doesn’t exist yet. The company says the nozzle improvements have mitigated several potential contributors, and that further testing and analysis will continue alongside the mission. Ars Technica reports that the February incident came after an earlier nozzle failure on one of Vulcan’s first four missions. The rocket completed both affected missions, but Space Force officials lost confidence after the latest failure.
That leaves a real tension in ULA’s approach. A flight is a way to gather evidence from the improved design; at the same time, the customer whose confidence matters most will be scrutinizing that flight. The mission may provide useful data, but the company’s description of the changes is not itself proof that the nozzle problem is resolved. The only claim we can make today is the one ULA makes: it has identified several potential contributors and mitigated them through design and process improvements.
So what would make this credible? A successful November 13 mission would establish that Vulcan flew with the improved nozzle design and delivered its payload. It would be a meaningful step for Amazon’s booked launches and the Space Force’s reliance on Vulcan. It wouldn’t, by itself, settle every question about the causes of the failures or how the vehicle performs across the rest of its manifest. ULA says additional testing and analysis will continue in parallel, which makes its public explanation and the evidence from flight important parts of the same story.
I think ULA has a sensible reason to put the improved design in flight: customers need a path back to launches, and the flight itself can produce evidence that ground work cannot. But I’m not ready to treat the problem as solved. The earlier affected flights completed their missions, yet the Space Force still lost confidence after the February anomaly; successful payload delivery and confidence in a rocket’s reliability are related, but they aren’t interchangeable.
And the business stakes are unusually clear. Amazon has booked 38 Vulcan flights, while the Space Force has entrusted the rocket with roughly half of its major launches through the early 2030s. That gives ULA a substantial customer case to make. My view is that the company’s explanation earns attention, not a clean bill of health. I’d change that view as the improved design flies and ULA’s continuing testing and analysis give customers evidence they can evaluate. For a company carrying large public responsibilities, I think schedule honesty and clear cost information matter alongside the hardware — though this story gives us no contract price to assess.
Time for the Hype Check. My substance score is 6 out of 10: the strongest point against that score is that Vulcan completed both missions affected by nozzle failures, but I land at six because the Space Force still lost confidence after the February anomaly and the improved design has yet to fly. The announced November 13 return puts 40 Amazon Leo satellites on the manifest and offers the next flight as a test of ULA’s changes. If Vulcan flies that mission on November 13 with the improved nozzle design, that will show the rocket has returned to service with the Amazon payload aboard; the question of lasting customer confidence will still rest on what follows.
If you value a clear-eyed look at what’s announced, what’s contracted and what’s actually flown, follow Space Stakes wherever you listen. This has been Space Stakes, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!
Watching on YouTube? Hit subscribe, and tomorrow's briefing will be waiting for you. I also host Quickly Quantum: a daily quantum computing briefing you don't need a physics degree to follow. The breakthroughs, the funding rounds, and how much substance is really under each claim. Find it wherever you get your podcasts.