Starship Static‑Fire Test Ends in Explosive Failure

Arabian Post

8 hours ago

A dramatic explosion ripped through SpaceX's Starbase test site near Brownsville, Texas, at approximately 11 p.m. Central Time on Wednesday, June 18, when the Starship prototype designated Ship 36 detonated during a routine static‑fire test ahead of its anticipated tenth flight. The stainless‑steel vehicle was engulfed in flames following a 'major anomaly' while being fuel‑led for a multiple‑engine ignition sequence, according to SpaceX. All personnel remained outside the secured perimeter and were confirmed safe, and there were no hazards reported to neighbouring communities.
The incident triggered a massive fireball that illuminated the night sky, accompanied by a deep boom that rattled windows and prompted concern among South Texas residents. Local emergency services and SpaceX teams responded swiftly to contain the blaze, which smouldered for over two hours after the blast.
Ship 36 had undergone a single‑engine static fire on June 16 and was being loaded with liquid methane and oxygen for a six‑engine ignition when it suffered catastrophic failure. While details remain scarce, video feeds captured an initial eruption near the nose section, followed by a secondary blast near the vehicle's side, culminating in a fiery detonation that obliterated the test stand.
ADVERTISEMENT
SpaceX characterised the event as a 'rapid unscheduled disassembly,' reiterating that safety protocols functioned as intended. The company confirmed through its X account that the site was secured, all employees were safe, and there was no impending risk to surrounding residential zones.
The explosion delivers a significant blow to SpaceX's high‑tempo test programme. Ship 36 was central to the upcoming tenth integrated flight test, tentatively scheduled for late June, following FAA notices suggesting a launch window around 29 June. The blast is now expected to delay that timeline.
Ship 36 is part of a succession of upper stage prototypes built with lessons from earlier failures. This spring, Ship 33 was lost mid‑flight, and Ship 34 disintegrated after engine shutdowns. Ship 35 achieved flight but was lost during re‑entry in Flight 9 on May 27 due to attitude control issues over the Indian Ocean.
Despite these setbacks, SpaceX continues to follow its iterative testing model—'fail fast, learn fast'—to refine design and reliability for the massive Super Heavy–Starship system. In statements after previous explosions, CEO Elon Musk has noted that such events are part of the development process and maintain optimism about achieving high‑frequency launches.
The blast's impact on Starbase infrastructure remains unclear. Initial reports indicate that fires continued well into the early hours of Thursday, but the structural and logistical damage to test‑stand facilities has not yet been quantified. SpaceX has deployed teams alongside local authorities to secure the site and begin assessments.
Ship 36's loss will likely compel SpaceX to adjust schedules for its Artemis lunar programme and the planned orbital Starship missions. The starship upper stage is slated to act as the Human Landing System for NASA's Artemis 3 lunar landing mission in 2027, and delays in prototype testing could compress the development timeline.
SpaceX's core objective remains unchanged: delivering fully reusable launch systems to support deep‑space missions, including human travel to Mars by the mid‑2020s. The firm is progressing with development of a 'V3' Starship design, intended to enable weekly launches next year. Ship 36 represented the refined 'V2' design, offering increased propellant capacity, lower mass and improved system redundancy.
Local communities were warned to avoid the perimeter while recovery operations continue. The Federal Aviation Administration has signalled strong regulatory backing, recently granting Starbase approval for up to 25 launches and 50 landings annually.