Routine Test Leads to Starship Explosion at SpaceX Facility

Ship 36 Incident Occurs Prior to Scheduled Flight

During preparations for its tenth test flight, SpaceX's Starship vehicle, designated Ship 36, encountered an unexpected explosion at its Texas-based Starbase. The incident was captured live, showcasing the vehicle erupting into flames shortly after a routine examination of its forward flap, moments before a planned static fire evaluation.

SpaceX confirmed the occurrence of a 'major anomaly' around midnight Eastern Time on June 19. Fortunately, the implementation of a designated safety perimeter ensured the safety of all personnel, with no reported injuries. The company assured the public that there is no hazard to nearby residents while urging them to stay away from the area. Local officials attributed the incident to a 'catastrophic failure' and have commenced investigations to ascertain the underlying cause.

Ambitious Plans for Starship Face Setbacks

Starship, which represents SpaceX's vision for a super-heavy-lift launch vehicle, is intended for future space missions carrying heavier payloads, aiming beyond low Earth orbit to destinations like the moon and Mars. Despite these ambitious goals, the vehicle has encountered numerous hurdles. During previous flight tests, notably the seventh and eighth trials, the second stage, termed the 'Ship,' erupted amidst its ascent, marking a pattern of unreliability.

Although the ninth test flight successfully reached space, communication was lost with the second stage before achieving a controlled oceanic descent. Similarly, the Super Heavy booster stage suffered an abrupt disassembly shortly post-launch, six minutes into the flight, further complicating SpaceX's progress toward reliable launch systems.

Safety Measures and Continued Investigation

On the night of June 18, just before midnight Central Time, the Starship unit slated for its tenth test stood on a test platform at Starbase. Through strict safety protocols, SpaceX ensured the security of its team amidst the operation. The event was documented by the company's official communication channels on June 19.