SpaceX lit all 33 Raptor engines on a Super Heavy booster at its Starbase facility in Boca Chica, Texas, in late May 2026, completing a full-duration static fire that the company called the last major ground test before the first flight of Starship Version 3. The roar from the test stand rattled windows miles away and sent a column of exhaust billowing over the South Texas coastline, marking another milestone for a rocket system that already holds the record as the most powerful ever built.
With roughly 16.7 million pounds of thrust at liftoff, Super Heavy dwarfs every rocket that has come before it, including NASA’s Saturn V (7.5 million pounds) and the Space Launch System (8.8 million pounds). But raw power on a test stand and permission to fly are two different things, and the gap between them is where the real countdown begins.
What the static fire actually proved
A static fire pins the booster to the ground while its engines ignite and run through a planned burn sequence. For Super Heavy, that means firing all 33 Raptors simultaneously, verifying that thrust levels, engine health, propellant flow, and vehicle structures perform within acceptable margins. SpaceX has conducted multiple static fires throughout the Starship program, but the company specifically flagged this one as the final qualification burn before committing hardware to a V3 launch attempt.
That distinction matters. Previous Starship iterations, from the early integrated flight tests through the most recent missions, have progressively demonstrated booster return and catch maneuvers, upper-stage re-entry survival, and orbital-class performance. Starship V3 represents the next leap: a stretched upper stage with greater propellant volume, redesigned plumbing, and a significant increase in payload capacity to low-Earth orbit. SpaceX has publicly targeted over 200 metric tons to orbit for the V3 configuration, a figure that would make it the highest-capacity launch vehicle ever flown if confirmed in flight.
The regulatory picture at Boca Chica
Engineering readiness is only half the equation. The Federal Aviation Administration must grant a launch license or approve a license modification before any Starship flight can leave the pad. The FAA maintains a dedicated Starbase stakeholder portal that tracks completed and in-progress environmental reviews under the National Environmental Policy Act, along with the scope of agency evaluations for Starship and Super Heavy operations.
At Boca Chica, the FAA has already completed environmental assessments tied to earlier Starship flights and has issued prior launch licenses, which gives the agency a foundation of existing findings to build on. Incremental license modifications for upgraded hardware or expanded operations can, in principle, move faster than a brand-new review. But “faster” is relative. The specific modification covering a V3 maiden flight, including any outstanding conditions or additional safety requirements, has not yet appeared as a completed action in the FAA’s public records.
SpaceX’s characterization of the static fire as a “final” pre-flight milestone reflects the company’s own engineering checklist, not an FAA determination that every pre-launch requirement has been satisfied. Range scheduling, national airspace coordination, debris mitigation plans, and any supplemental conditions attached to a license modification all remain variables that a successful engine burn cannot resolve on its own.
Kennedy Space Center is on a separate track
SpaceX is also preparing to launch Starship from Kennedy Space Center’s Launch Complex 39A in Florida, but that site is on a fundamentally different regulatory timeline. The FAA’s Kennedy Space Center portal shows that the agency is still working through the Notice of Intent and full Environmental Impact Statement process required before any Starship flights can be authorized from KSC.
That process is far more involved than the incremental reviews underway at Boca Chica. A full EIS typically involves public scoping, draft and final impact statements, and a formal Record of Decision, a sequence that can stretch over a year or more. For now, Starbase remains the only site positioned to host a V3 flight in the near term, and the KSC pathway is best understood as a parallel effort aimed at supporting higher launch cadence down the road.
What previous flights have shown
Starship’s flight-test campaign has moved quickly by historical standards. The program’s early integrated flights ended in vehicle loss, but each successive attempt pushed further. More recent missions have demonstrated controlled booster flyback and catch by the launch tower’s mechanical arms, upper-stage re-entry and controlled descent, and engine relights in space. Those results gave SpaceX the engineering confidence to advance toward V3, which introduces hardware changes significant enough to warrant its own qualification testing, including the static fire completed in late May 2026.
The progression also matters to the FAA. Each flight generates data that feeds into the agency’s safety assessments, and a track record of increasingly successful missions can streamline the review of subsequent license applications. Conversely, any anomaly or failure during flight tends to trigger a mishap investigation that pauses the cadence until root causes are identified and corrective actions are verified.
How FAA licensing will shape the V3 launch window
SpaceX has not publicly committed to a specific launch date for Starship V3’s first flight. However, the company’s pace of hardware preparation suggests it is targeting a window in June 2026, contingent on regulatory clearance. The FAA has not published a timeline for completing the relevant license modification, but the agency’s Starbase portal shows that the environmental review foundation is already in place, and prior license modifications for the Starship program have been completed within weeks once the technical review was finalized. If that pattern holds, a V3 license modification could follow relatively soon after the FAA confirms that SpaceX’s updated safety data, including results from the late May 2026 static fire, satisfy all outstanding requirements.
The most reliable signal will come from the FAA itself: a formal license or modification posted through its portal system would confirm that all engineering, safety, and environmental requirements have been met. Until that document appears, the static fire is best understood as a significant engineering milestone that brings the program to the threshold of flight without guaranteeing when the door will open.
SpaceX’s development philosophy prizes rapid iteration and accepts hardware risk in pursuit of long-term reliability. The FAA, by design, moves more deliberately, weighing innovation against public safety, environmental protection, and national airspace management. Those two tempos can coexist, but they do not always sync up.
For anyone tracking the countdown, the clearest picture comes from watching both threads at once: SpaceX’s hardware milestones and the FAA’s documented regulatory actions. Where both advance together, a flight is likely close. Where they diverge, the bottleneck almost always sits on the side that has not yet produced a public, verifiable record. Right now, the engines have spoken. The paperwork has not.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
