Primary cause of anomaly in 7th SpaceX Starship test flight by end of Q1 2025
Engine failure • 25%
Structural issue • 25%
Software malfunction • 25%
Other cause • 25%
SpaceX investigation reports and official announcements
SpaceX Loses Starship Spacecraft on 7th Test Flight Despite Successful Booster Catch, New Upgraded Craft Carried Dummy Satellites
Jan 16, 2025, 11:45 PM
SpaceX's Starship rocket experienced a setback during its seventh test flight on Thursday, losing the spacecraft due to an anomaly during ascent. The launch took place from SpaceX's Starbase facility near Brownsville, Texas, at approximately 4:37 p.m. local time. The 400-foot rocket, powered by 33 Raptor engines producing 16.7 million pounds of thrust, aimed to advance SpaceX's capabilities for future lunar and Mars missions. Despite the loss of the spacecraft, SpaceX successfully caught the Super Heavy booster back at the launch pad in Boca Chica using giant mechanical arms, marking the second successful catch of the booster. The spacecraft, equipped with 6 engines, was carrying 10 dummy Starlink satellites for a deployment test, but communication was lost about 8.5 minutes into the flight when it reached an altitude of 91 miles and a speed of 13,246 mph, resulting in the spacecraft's destruction. The spacecraft was intended to soar across the Gulf of Mexico and target the Indian Ocean for a controlled but destructive end to the hourlong demo. This test flight was significant as it involved a new and upgraded version of the spacecraft, aimed at advancing SpaceX's capabilities for future lunar and Mars missions, with the system designed to be fully reusable.
View original story
Software malfunction • 25%
Other • 25%
Human error • 25%
Structural failure • 25%
Other • 25%
Engine malfunction • 25%
Avionics failure • 25%
Tank system issue • 25%
Other • 25%
Structural failure • 25%
Fuel leak • 25%
Software malfunction • 25%
Other • 25%
Operational Error • 25%
Manufacturing Defect • 25%
Design Flaw • 25%
Fuel leak identified as cause • 25%
Other cause identified • 25%
Software malfunction identified as cause • 25%
Structural failure identified as cause • 25%
Other cause identified • 25%
Design flaw identified • 25%
Manufacturing defect identified • 25%
Operational error identified • 25%
Yes • 50%
No • 50%
Structural integrity issue • 25%
Communication system failure • 25%
Propulsion system failure • 25%
Other technical challenge • 25%
No significant issues • 25%
Technical malfunction • 25%
Weather-related delay • 25%
Regulatory delay • 25%
Yes • 50%
No • 50%
Gulf of Mexico • 25%
Other location • 25%
Pacific Ocean • 25%
Indian Ocean • 25%