SpaceX shared details of the first Starship test flight of 2025, which achieved several milestones but ended in an unexpected failure.
The mission, conducted on January 16 at 4:37 p.m. CT from Starbase, Texas, focused on testing upgraded systems for the world’s most powerful rocket.
The launch began smoothly, with all 33 Raptor engines on the Super Heavy booster firing as planned. After separation, the booster executed its boostback burn, landing safely on the launch tower’s arms (Mechazilla for the win!)—marking the second successful recovery of a Super Heavy booster.
Following stage separation, the Starship upper stage ignited its six Raptor engines, ascending toward space. However, about eight and a half minutes into the flight, SpaceX lost contact with the vehicle.
Preliminary analysis indicates a fire broke out in the ship’s aft section, leading to a rapid breakup, or what SpaceX refers to as a “rapid unscheduled disassembly.”
Yesterday, SpaceX CEO Elon Musk said on X, “Preliminary indication is that we had an oxygen/fuel leak in the cavity above the ship engine firewall that was large enough to build pressure in excess of the vent capacity. Apart from obviously double-checking for leaks, we will add fire suppression to that volume and probably increase vent area. Nothing so far suggests pushing next launch past next month.”
SpaceX confirmed that Starship stayed within its designated flight corridor, ensuring safety for people on the ground, water, and air. Any debris fell into a pre-determined hazard area, and the company reminded the public not to touch or collect debris. Instead, individuals are advised to contact local authorities or the SpaceX Debris Hotline at 1-866-623-0234 or email recovery@spacex.com.
Despite the failure, SpaceX views the test as a critical learning opportunity. Engineers are reviewing data and working with the Federal Aviation Administration (FAA) to determine the root cause and improve the system’s reliability.
The next Starship and Super Heavy booster are already built and undergoing prelaunch testing.
