Lead: SpaceX’s upgraded Starship V3, scheduled for a critical test flight no earlier than Friday, May 22 at 6:30 p.m. EDT (2230 GMT) from Starbase, Texas, was scrubbed at the last minute during a May 21 attempt. The company paused countdown activity at roughly T‑40 seconds after an automated hold triggered while teams reviewed a ground-system indicator. SpaceX says it expects to try again on May 22; a company-hosted webcast will begin about 45 minutes before the planned liftoff.
Key Takeaways
- Flight 12 is the 12th Starship test since 2023 and the first Starship mission of 2026, ending a seven‑month pause since Flight 11 in October 2025.
- The launch was scrubbed on May 21 during a last‑minute hold at about T‑40 seconds; SpaceX indicated a ground‑system item (a water‑diverter) tripped the hold and teams reviewed telemetry.
- The next earliest attempt is set for May 22 at 6:30 p.m. EDT (2230 GMT) with a 90‑minute window closing at 8 p.m. EDT (0000 GMT); the webcast begins at 5:45 p.m. EDT (2145 GMT).
- Starship V3 stacks Ship 39 atop Super Heavy Booster 19 and stands 408 feet tall; the first stage is powered by 33 Raptor engines.
- The mission will be suborbital: the Ship upper stage is planned to splash down in the Indian Ocean ~65 minutes after liftoff while the Super Heavy first stage will splash down in the Gulf of Mexico ~7 minutes after launch.
- Payload reporting varies; live coverage referenced both 20 and 22 dummy Starlink satellites and additional instrumentation aboard Ship for photography and telemetry.
- Pad 2 is in use for this debut V3 flight; SpaceX reported fueling proceeded and a wet dress rehearsal was completed on May 20.
Background
SpaceX developed Starship as a fully reusable heavy‑lift system intended to serve a wide range of missions: large satellite deployment, crewed lunar landings for NASA’s Artemis program, and eventual crewed Mars missions. The vehicle is built as a two‑stage stack: a Super Heavy booster and a Ship upper stage. Several iterative test flights since 2023 have focused on proving staging, control and recovery procedures rather than immediate operational service.
V3 is presented by SpaceX as the largest and most powerful version yet, incorporating structural and systems upgrades designed to improve performance and to move the program closer to operational reuse. Those upgrades include pad and ground‑system changes at Starbase, where Mechazilla catch arms and two pad sites are being readied to support routine, rapid turnaround flights. The long interval since Flight 11 reflects both technical iteration and a deliberate cadence of testing before attempting orbital operations or crewed missions.
Main Event
On May 21 SpaceX conducted final tanking operations and began countdown procedures for Flight 12. Teams completed fueling of the combined stack with cryogenic liquid methane and liquid oxygen after a wet dress rehearsal on May 20; SpaceX noted pad fueling on Pad 2 ran about 20% faster than earlier Pad 1 operations. Observers at Starbase and the webcast crew provided continual status updates as the clock advanced toward the opening of the 90‑minute launch window.
Near T‑40 seconds the automated system registered a trip related to a water‑diverter component under the pad, prompting an official hold while telemetry was evaluated. The clock had briefly restarted earlier in the count before cycling back to the hold. SpaceX commentator Dan Huot explained the hold gave the team time to inspect the indicator and determine whether an extension of the count or a scrub was required.
After several minutes of review, SpaceX announced the team had called off the May 21 attempt and planned to make another flight attempt on May 22, keeping the same 6:30 p.m. EDT (2230 GMT) target within a 90‑minute window. The scrub removed the immediate opportunity to test V3’s in‑flight behavior, payload deployment and planned splashdown profiles for both stages.
The public saw heightened attention around the event, including high‑profile attendees visible at Starbase and an unexpected company announcement during the webcast about a privately sponsored Mars flyby mission. SpaceX emphasized these public elements do not affect vehicle flight readiness and that the technical hold was the reason for the abort.
Analysis & Implications
Technically, a T‑40 hold indicates launch‑control software or a ground‑support system performed as designed by preventing ignition until a parameter was resolved. While such holds are commonplace across modern rocketry, they highlight the complexities of scaling Starship to V3, particularly with new pad hardware at Pad 2. Quick, conservative scrubs can be preferable to silent failures that risk hardware or personnel.
Programmatically, Flight 12’s success or failure will reverberate across multiple stakeholders. NASA sees Starship as a candidate lunar lander for Artemis missions, so continued delays or failures could compress Artemis schedules or require contingency planning. Commercially, SpaceX’s plans to use Starship for bulk Starlink launches and future orbital infrastructure mean sustained progress is important to customers and investors.
Operationally, the use of Pad 2 and faster tanking speeds are positive signs for cadence and turnaround, but pad and ground‑system items remain a focus for reliability engineering. The presence of high‑profile guests and surprise mission announcements underscores SpaceX’s dual role as a technology developer and a media magnet; while public attention can boost awareness, it also places program milestones under intense scrutiny.
Comparison & Data
| Characteristic | Starship V3 (Flight 12) | Previous Starship (V2) |
|---|---|---|
| Stack height | 408 feet | ~387–400 feet (varied by configuration) |
| First stage engines | 33 Raptor engines | ~33 Raptor engines (similar count; engine models evolved) |
| Payload carried on test | Reported 20–22 dummy Starlink satellites | Earlier test flights carried dummy Starlink payloads or instrumentation |
| Target splashdowns | Ship → Indian Ocean (~65 min); Booster → Gulf of Mexico (~7 min) | Previous flights used similar splashdown profiles for suborbital tests |
The table distills publicly reported differences. V3 centers on incremental hardware and ground‑system changes intended to improve operational readiness; some metrics (exact payload count) were reported inconsistently across live coverage and remain to be reconfirmed.
Reactions & Quotes
SpaceX spokespeople and commentators framed the scrub as a learning event consistent with debuting new systems. Their public remarks emphasized caution and an intent to reattempt quickly under the existing window.
“New rocket, new pad, we’re learning a lot about these new systems as we execute them for the first time. We are expecting to be able to make another flight attempt tomorrow.”
Dan Huot / SpaceX live commentary
Public figures present at the site expressed enthusiasm for the program despite the scrub, underscoring the wide public interest in Starship’s next steps.
“This is historic. This is a major moment, y’all.”
Nicki Minaj, attendee
Separately, SpaceX introduced a private mission announcement during coverage, which drew attention but does not alter Flight 12’s primary objectives. That plan remains reported by SpaceX representatives and independent verification is awaited.
“So it’s going to be a fly by mission of Mars… let’s get it started with a flyby.”
Chun Wang / recorded statement (reported)
Unconfirmed
- The precise payload manifest is inconsistent in live reports: some coverage cited 22 dummy Starlink satellites while earlier notes referenced 20; official postflight documentation will confirm the exact count.
- Full root cause details for the May 21 hold/scrub have not been released beyond a reference to a water‑diverter indicator; a more detailed anomaly report from SpaceX is pending.
- The timing and manifest details for the privately announced Mars flyby remain unverified beyond the on‑air statement and require formal filing or mission documentation.
Bottom Line
The May 21 scrub of Starship Flight 12 is a routine but high‑profile setback in a program that is iterating toward greater capability and reusability. Because the hold occurred late in the count, teams elected caution; SpaceX plans to reattempt the flight on May 22 within the same 90‑minute window, with a webcast beginning roughly 45 minutes prior to liftoff.
Flight 12 will be closely watched by NASA, commercial customers and international observers: a successful V3 debut would advance SpaceX’s case for using Starship in Artemis lunar missions and for bulk commercial launches, while a failure or further delay could require schedule adjustments. For now, engineers and watchdogs alike will await post‑scrub telemetry and any subsequent mission updates before drawing stronger conclusions.
Sources
- Space.com live coverage of Flight 12 (news coverage, live updates)
- SpaceX official website (official company site)