SpaceX automatically aborted Flight Test 13 of the Starship launch system at the launchpad on July 16, 2026 [1], [2].
The failure represents a setback in the company's rapid testing cadence for the heavy-lift vehicle. Persistent engine hurdles could delay the timeline for future orbital missions and lunar objectives.
The abort occurred at 22:45 UTC [1], [4]. According to reports, four Raptor engines failed to start, which triggered the launch system's automatic abort sequence [1], [2]. This safety mechanism is designed to prevent catastrophic failures on the pad by shutting down the sequence if the vehicle does not meet specific performance parameters before liftoff.
While some reports described the event as an unexpected issue interrupting the sequence [4], more detailed accounts specify the failure of the four engines [1]. This incident occurs as the company continues to refine the Raptor engine's reliability across various iterations of the Starship system.
SpaceX has not yet released a detailed post-mortem on the ignition failure. The company typically conducts a series of reviews before scheduling a subsequent attempt. The automatic shutdown prevented a potential explosion, ensuring the launch infrastructure remained intact for future flights [1], [3].
The company is currently testing the V3 version of its hardware, and this scrub exposes ongoing challenges in achieving consistent ignition across the entire engine cluster [3].
“Four Raptor engines failed to start, which triggered the launch system's automatic abort sequence.”
The automatic abort demonstrates that SpaceX's safety systems are functioning as intended to protect ground infrastructure. However, the failure of four engines during a critical ignition sequence suggests that the Raptor engine's reliability has not yet reached the stability required for high-frequency operations, potentially slowing the deployment of the Starship fleet.
