SpaceX aborts Starship launch after three Raptor engines fail to ignite

SpaceX aborted the Starship orbital test flight scheduled for July 17 at Boca Chica after telemetry showed three of the vehicle’s 33 Raptor engines failed to start during the final countdown sequence [Ars Technica][SpaceX X].

At T‑0 the launch controller received an engine‑start anomaly flag, triggering an automatic scrub. Ground crews began offloading the remaining liquid methane and liquid oxygen to limit boil‑off and preserve the tanks for a later attempt. SpaceX confirmed the scrub and said a new launch window would be evaluated within 48‑72 hours [Ars Technica].

This is the second engine‑start failure in Starship’s test program; the first occurred in November 2023 when a single Raptor failed to ignite. SpaceX’s post‑flight brief linked both incidents to sensor‑validation logic and valve‑actuation timing [Ars Technica].

The failure underscores three implications. First, engine‑start reliability is the primary bottleneck for a 33‑engine vehicle—three failures represent a 9 % engine‑failure rate, reducing launch‑success probability to roughly 73 % if failures are independent. Second, the rapid methane/oxygen dump tests the launch pad’s cryogenic transfer system; the successful offload without spill shows the infrastructure can survive repeated scrubs. Third, each delay pushes back the “late‑July” cadence promised to satellite‑constellation customers, opening a window for rivals such as Blue Origin’s New Glenn to capture time‑critical contracts [Ars Technica].