Vulcan Return to Flight Targets Oct. 29 After Falcon 9 Scrub

A rare stumble and a long-awaited comeback

At the start of October, SpaceX's Falcon 9 had trouble getting off the ground, and United Launch Alliance's Vulcan looked close to flying again. For two companies with very different track records, that is an unusual combination. Falcon 9 still flies almost constantly. But the week shows how much of the industry's near-term story depends on whether America's second heavy-lift supplier can finally build up a launch rate.

The headline event was minor in itself. A Falcon 9 set to launch early Monday, October 5, from Vandenberg was scrubbed in the last minute of the countdown, as the rocket was handing off to its automated startup sequence. SpaceX did not give a reason.1 The payload was a batch of data-transport satellites for the U.S. Space Force's Space Development Agency.1 SpaceX called off a second attempt on Tuesday, October 6, made more changes, and set a new target of no earlier than Saturday, October 10.1 Launch listings put the mission, Tranche 1 Transport Layer A, at 07:29 UTC that day.1 Earlier coverage put the payload at 21 satellites.15

The booster, B1103, is fairly new by Falcon standards. This would be its sixth flight, after the SDA's T1TL-E mission, NROL-179, and three Starlink batches.1

How rare is "rare"?

The coverage agrees that late scrubs like this are unusual for Falcon 9. One market-focused analysis called it an uncommon event for SpaceX's main rocket and noted that the technical cause is still undisclosed.23 Some context is needed, though. In July 2026, a Falcon 9 carrying Starlink satellites from Vandenberg aborted after all nine Merlin engines had briefly ignited. That was SpaceX's second scrub in under a week, and it came days after a post-ignition abort of Starship at Starbase.28 Before that, the last Falcon 9 abort after engine ignition was in June 2024.28

That is still a tiny share of a very busy schedule. By mid-September, SpaceX had flown 107 Falcon 9 missions in 2026.16 On October 1 alone it flew three Falcon missions: Crew-13 to the space station, the Transporter-18 rideshare with 130 payloads, and the National Reconnaissance Office's first Falcon Heavy launch.16 At that pace, a few scrubs a year are a rounding error. Still, delays of several days on a national-security constellation launch are the kind of event rivals like to point to.

The gokhshtein.com analysis made that point directly. It argued that launch delays squeeze satellite operators' margins and that ULA is positioning Vulcan to take advantage.23 It is right that availability can matter more to a constellation operator than small price differences.23 It goes too far, though, in treating Vulcan as a new entrant timed to SpaceX's troubles. Vulcan has flown national-security missions since 2025.2 Its own problem has been reliability, not timing.

Vulcan's solid rocket booster problem

Vulcan's 2026 so far has been mostly an investigation. On February 12, during the USSF-87 mission from Cape Canaveral, one of its four solid rocket boosters had what looked like a nozzle burn-through about 30 seconds after liftoff. It resembled an anomaly on an earlier Vulcan flight.2 ULA said the payload, which included a Geosynchronous Space Situational Awareness Program spacecraft, still reached the correct trajectory.2 After the 2024 incident, investigators traced the cause to a manufacturing defect in a carbon composite insulator inside the nozzle. A repeat suggested either that the fix had not worked or that Northrop Grumman's boosters had a separate problem.26 In late February, a senior Space Systems Command official expected a "many months process" to find the exact cause and corrective actions.26

That estimate held. As of October 1, Orlando-area launch tallies showed only one Vulcan flight from the Space Coast in 2026, against 51 from SpaceX.2 Amazon's satellites moved to other rockets in the meantime. An Atlas V carried 29 Amazon Leo satellites in April, on a mission originally assigned to Vulcan's first Amazon flight.2

Weeks, not months

The tone changed this week. Ars Technica reported a no-earlier-than date of October 29 for Vulcan's return to flight, carrying Amazon Leo satellites, with a second Amazon Leo mission also planned before year's end.1 Launch trackers updated the LV-01 listing to that date on October 8, after carrying a vague "late Q3" target since June.3 The mission will use the VC6L configuration: six solid boosters, Vulcan's most powerful version, and a long payload fairing.36

The strongest signal came from the customer. Rajeev Badyal, Amazon Leo's vice president, said the company is "weeks away from launching on Vulcan." He said an Arianespace launch would follow, plus at least one more Vulcan flight this year.1 He also said ULA now has two vehicle integration facilities, each holding a vertical Vulcan being prepared for Amazon missions, so two rockets can be processed at once.1 At least one aggregator credited the "weeks away" quote to Ars reporter Eric Berger, but it was Badyal's.9 The distinction matters: the confidence is coming from the paying customer, not from a journalist reading the schedule.

The figures are less consistent. One launch database says each Vulcan will carry 45 Amazon Leo satellites.3 The Orlando Sentinel lists 44 for the first proliferation mission and elsewhere says Vulcan can hold 42.2 All agree on the scale: ULA has 38 Vulcan launches under contract with Amazon.2 The constellation is planned at roughly 3,200 satellites, and Amazon needs 3,236 in orbit by July 2029.23

The bottom line: if the boosters perform, Ars thinks Vulcan could see a major jump in launch rate in 2027.1 That condition is the whole story. Two Amazon flights plus the USSF-57 missile-warning launch, which trackers list for December, would be the busiest stretch Vulcan has had.5 A third booster anomaly would set it back again.

Starship crosses the orbital threshold

Vulcan is trying to show it can fly reliably. Starship is trying to change what a launch can carry. On September 28, Flight 14 became the first Starship mission to reach orbit and deploy an operational payload: 26 Starlink V3 satellites.1418 CNBC reported SpaceX's claim that one Starship can carry 60 V3 satellites, about 20 times what earlier Falcon 9 rockets could.18

The flight was not clean, and accounts differ on the details. Ship 41 lost an engine early in ascent. Controllers first indicated the vehicle would not commit to orbit, then went ahead once engineers confirmed enough redundancy.14 Some trackers identify the failed engine as a Raptor Vacuum.20 Others count it as one of the ship's six Raptors.14 Either way, SpaceX cut a planned flight of roughly ten hours to about three and brought the ship down under control in the Pacific.1720 Even shortened, the mission showed orbital insertion, payload deployment, deorbit, and controlled reentry.14

What comes next is less clear. Provisional planning documents point to October 19 for Flight 15 and October 30 for Flight 16. Space.com called those dates possibly "a bit aspirational."19 One crowd-edited tracker already lists Flight 15 in early November.14 Before Flight 14, Musk said a success would clear Flight 15 for an attempt to catch the ship.14 Another company tracker says Musk has since indicated the first ship catch will wait a few months.16 Given the engine-out on Flight 14, a short delay seems more likely than a fast turnaround.

Florida, the Moon, and a crowded Cape

Starship is also moving east. A SpaceX official said on October 1 that work at Kennedy's Pad 39A is going "super well." At least one more Starbase flight will come first, so the first Florida launch could be Flight 16.19 Work on Starship towers at SLC-37 is also underway.19

The lunar program is closely tied to this. Starship's first Artemis role is Artemis III, now described as a 2027 docking test in Earth orbit with NASA's Orion capsule, launching from 39A.19 That is a smaller goal than a crewed landing, and it follows Artemis II, which flew this year with Canadian astronaut Jeremy Hansen aboard.15 NASA's plans for a Moon landing depend on Starship's orbital refueling, but the propellant-transfer demonstration has slipped from March 2025 to March 2026 and still has no date.14

The rest of the launch business is pushing in the same direction. Jeff Bezos said Blue Origin is building three more pads for New Glenn, in connection with a request to the FAA for 50 Florida launches a year.1 Cape Canaveral, which saw hundreds of drone incursions last year, is getting laser-based drone defenses, partly because jamming radio signals could harm spacecraft.1 Abroad, South Korea's Nuri rocket succeeded for the fourth straight time, deploying its first domestically launched microsatellite constellation. One CubeSat, Quaternion's PERSAT-02, failed to separate.1

The reading

The Falcon 9 scrub matters less as a sign of weakness at SpaceX than as a reminder of how few alternatives exist. SpaceX's rate is high enough to absorb a multi-day slip on an SDA mission, and Starship is starting to carry real payloads. Amazon's deadline means it needs more than one supplier. If Vulcan flies cleanly on October 29 and again before New Year's, ULA moves from recovery into the regular production flying it was built for. The coming weeks will show whether this is Vulcan's moment or another delay.