Update July 16, 7:10 p.m. EDT (2310 UTC): SpaceX aborted the mission following an apparent engine issue.
SpaceX will have to wait debut its long-promised Starlink Version 3 satellites after an apparent engine issue forced a last second abort of the suborbital test mission
The Starship Flight 13 mission will be the second launch of a third-generation Starship-Super Heavy launch vehicle and the second mission for the program this year.
SpaceX reached ignition of the Super Heavy booster at the Pad 2 at SpaceX’s Starbase facilities in southern Texas at 5:45 p.m. CDT (6:45 p.m. EDT / 2245 UTC), but on-screen telemetry data showed four engines that apparently didn’t ignite as anticipated.
“Some of the engines didn’t start, triggering an automatic launch abort,” SpaceX founder Elon Musk wrote on his social media site, X, about 10 minutes after the abort. “Next launch attempt hopefully in a few days.”
When it flies, SpaceX will launch this mission using Booster 20 and the Ship 40 upper stage. Both stages are flying for the first time and SpaceX will not attempt to recover either for reuse.
One of the biggest differences between Flight 13 and Flight 12, which launched in May, is that this time around, SpaceX will be deploying 20 production Starlink V3 satellites. While they’re not going into orbit, SpaceX does intend to briefly link them to the broader network in low Earth orbit.
“As part of this initial test, Starship is planned to deploy 20 satellites which will extend solar arrays and antennas and will attempt to connect with the larger Starlink constellation via high-capacity lasers,” SpaceX wrote prior to launch. “The Starlink satellites will be on the same suborbital trajectory as Starship and are expected to demise upon reentry approximately 20 minutes after deployment.”
Other mission objectives are fairly similar to what was demonstrated in Flight 12. Those include a relight of a Raptor engine on the upper stage during the coast phase and performing a controlled landing of the booster in the Gulf of Mexico. Neither of those objectives were able to be accomplished back in May.
SpaceX said the startup sequence of the engines on Ship 39 “caused the directional flip of the booster to be off by approximately 90 degrees.” That coupled with issues with five out of 33 sea-level engines on the booster prevented a nominal boostback burn and Booster 19 was lost prematurely.
“The Super Heavy on this upcoming flight has hardware modifications to improve re-light reliability along with updates to engine alarms and aborts to match the conditions seen in the multi-engine flight environment,” the company wrote.
In between these two flights of Starship Version 3, SpaceX said it also made “several hardware an operational modifications” to address issues that caused one of the three Raptor Vacuum engines to go offline less than a minute after stage separation.
SpaceX is also continuing its heat shield iterative work in order to produce a protective system that will eventually allow for rapid reuse of the upper stage.
“Multiple tiles will be attached to the metallic side of Starship’s aft flaps along with modified tiles and attachment mechanisms in the heat shield covering the aft skirt to gather flight data on different attachment options,” SpaceX said. “Finally, Starship’s heat shield will have load sensing tiles to take measurements as the vehicle experiences higher dynamic pressure on ascent than previous flights, putting added stress on the tile attachments in exchange for increased payload to orbit capability.”
Gwynne Shotwell, SpaceX’s president and chief operating officer, told CNBC in an interview in June that the company may attempt to perform an orbital launch as soon as Flight 14, depending on how this next mission goes. She said a monthly launch cadence is the company’s target.
Rapid learning will be critical as NASA is relying on SpaceX to get Starship to orbit sooner rather than later. A modified version of a Starship Version 3 rocket with a docking adaptor is scheduled to fly next years part of the Artemis 3 mission.
Unlike Blue Origin’s Blue Moon Mark 2 Alpha spacecraft, the Artemis 3 crew will not enter into Starship on that flight, but rather NASA and SpaceX will focus on testing the interaction of these two vehicles when they dock.
“Software testing between spacecrafts will help demonstrate that the commercial human landing system prototypes and Orion can meet at a precise time and location in space,” NASA said in a press release on Wednesday. “When Orion docks with the Blue Moon test lander, the Orion spacecraft’s software will control the docked spacecraft. Meanwhile, the SpaceX test article will control the docked spacecraft for the second portion of the mission.”
Flight 13 is also SpaceX’s first mission for the Starship program since it became a publicly traded company on the Nasdaq. The company’s new investors will be keenly watching the performance of the launcher and launch infrastructure as SpaceX hopes to begin deploying orbital payloads later this year.
Facts Only
* SpaceX aborted the mission following an apparent engine issue at 7:10 p.m. EDT on July 16.
* The abort was due to four engines apparently not igniting as anticipated.
* The mission involved Starship Flight 13, the second launch of a third-generation Starship-Super Heavy vehicle and the second mission for the program this year.
* Ignition of the Super Heavy booster occurred at Pad 2 at SpaceX’s Starbase facilities in southern Texas at 5:45 p.m. CDT.
* On-screen telemetry showed four engines did not ignite as anticipated.
* SpaceX founder Elon Musk stated that some engines did not start, triggering an automatic launch abort.
* The mission used Booster 20 and Ship 40 for the first time; neither stage was attempted for reuse.
* Twenty production Starlink V3 satellites were planned for deployment during this flight.
* Starlink satellites were expected to remain on the suborbital trajectory before demise upon reentry approximately 20 minutes after deployment.
* The startup sequence caused the booster's directional flip to be off by approximately 90 degrees.
* Issues with five out of 33 sea-level engines prevented a nominal boostback burn, and Booster 19 was lost prematurely.
* SpaceX implemented hardware modifications for improved re-light reliability and engine alarm updates following the flight.
Executive Summary
SpaceX aborted the Starship Flight 13 mission following an apparent engine issue at 7:10 p.m. EDT on July 16, resulting in a last-second abort. This mission was intended to launch the third-generation Starship-Super Heavy vehicle and deploy 20 production Starlink V3 satellites, which would briefly link to the network in low Earth orbit. Telemetry data showed that four engines did not ignite as anticipated. The flight involved Booster 20 and Ship 40, which were flying for the first time, and neither stage was recovered for reuse.
The mission objectives included deploying the Starlink satellites via high-capacity lasers during the suborbital trajectory. Other planned objectives, similar to the previous flight, included relighting a Raptor engine on the upper stage and attempting a controlled landing of the booster in the Gulf of Mexico. SpaceX reported that the engine startup sequence caused a 90-degree directional flip in the booster and issues with several sea-level engines prevented a nominal boostback burn. In response to these events, SpaceX implemented hardware modifications to improve re-light reliability and updated engine alarms for future flights. The company is also continuing work on heat shield iterative improvements to enable eventual upper stage reuse.
Full Take
The narrative highlights a transition from ambitious demonstration to necessary engineering iteration under high operational stress. The abort of Flight 13 underscores a crucial tension between rapid deployment goals (launching Starlink satellites) and achieving rigorous, reliable vehicle performance (engine ignition, boostback maneuvers). The focus shifts from mission success toward hardening the system itself, evidenced by the immediate implementation of hardware modifications to address engine reliability and flight dynamics.
The deployment of Starlink assets during a suborbital test introduces a layer of complexity where operational objectives intersect with physical testing boundaries. This sets up a pattern where ambitious commercial goals are constrained by the physics of emergent systems. The necessity for iterative hardware improvements in the heat shield, specifically integrating load-sensing tiles, suggests that achieving future mass-to-orbit capability is contingent not just on propulsion success but also on managing dynamic stresses across the vehicle structure during ascent.
The broader context involves the evolving relationship between private aerospace development and governmental objectives, particularly NASA's reliance on SpaceX for orbital access via Starship for Artemis missions. The testing of docking interfaces between commercial prototypes and government systems, as seen with the planned interaction between Starship and the Blue Moon test lander, suggests that future progress will hinge on validating complex software and hardware interactions across disparate systems rather than solely on single vehicle performance metrics. The cost implications of these necessary redesigns and iterative testing—who bears the risk and cost associated with these learning phases—remains an open, unstated pattern in this technological race.
Bridge Questions: What is the optimal balance between mission scope (e.g., satellite deployment vs. core vehicle reliability) when executing developmental flight tests? How should regulatory frameworks evolve to accommodate rapid, iterative hardware modification schedules for systems deployed outside traditional safety envelopes? What are the long-term systemic consequences if the necessity for in-flight aborts becomes a predictable factor in commercial launch cadence?
Sentinel — Human
The text reads like standard, fact-based reporting on an aerospace incident, characterized by specific details and attributed quotes, suggesting human authorship rather than pure synthetic generation.