TechNews

Starship reached orbit, then exploded: what Flight 14 achieved

SpaceX delivered 26 operational Starlink satellites before cutting its test flight short. The explosion came after a controlled ocean splashdown.

SpaceX Starbase launch facility viewed across the bay, with Starship hardware and a launch tower visible
File photograph of SpaceX’s Starbase launch facility in Boca Chica, Texas, viewed across the bay on September 5, 2021. Lars Plougmann, ‘SpaceX Starbase launch facility (51438071556)’ (resized and converted to WebP). CC BY-SA 2.0.
LinkedInPostEmail
Save for later

SpaceX’s Starship reached Earth orbit for the first time after launching from Starbase, Texas, on September 28, 2026, and deployed 26 operational Starlink satellites. Flight 14 delivered that milestone before returning earlier than planned and exploding after a controlled Pacific Ocean splashdown.

The sequence matters: the satellites were already away before Starship returned to Earth. Its upper stage splashed down upright north of Hawaii, then tipped onto its side and exploded as residual propellants ignited, according to Spaceflight Now. The orbital achievement and the spacecraft’s destruction both happened.

What Starship Flight 14 achieved

Flight 14 followed 13 suborbital tests. Those earlier flights travelled through space without entering orbit; even previously released Starlink V3 test satellites followed paths that brought them back into the atmosphere. This time, Starship delivered satellites into an operational orbit.

Getting there was uncertain during ascent. One of the upper stage’s six engines stopped early, prompting controllers to assess whether to proceed. SpaceX spokesperson Dan Huot initially announced that the orbital attempt was off, then reversed course as the assessment continued, Space.com reported.

“We are not giving up yet,” Huot said during the webcast. About 25 minutes after launch, the spacecraft briefly fired a single Raptor engine to enter orbit. Mission control then announced: “Starship is orbital.”

Releasing all 26 Starlink V3 satellites took about 30 minutes. SpacePolicyOnline reported that contact was established with each one after deployment. That confirmed release and initial communication; it did not establish that every satellite had begun serving broadband customers.

Why Starship returned early

The original plan called for approximately six orbits over nearly ten hours, followed by a splashdown in the Pacific west of Chile. Instead, Starship returned after three hours, eight minutes and 27 seconds. The planned endurance flight was therefore left incomplete.

SpaceX subsequently said it shortened the mission “out of an abundance of caution” over the ascent engine issue, according to Ars Technica. That explanation describes the reason for the precautionary return; it does not establish the technical root cause of the engine shutdown.

The alternate landing area was north of Hawaii. SpacePolicyOnline reported that contingency preparations had been made in advance, including arrangements to keep airspace clear, and that recovery teams were positioned for both the original and alternate splashdown areas.

Which part of Starship had engine trouble?

Starship’s name can make the flight harder to follow. It refers both to the complete two-stage rocket and to the upper spacecraft, also called Ship. The first-stage booster is Super Heavy. Each vehicle had its own engine issues and a separate ocean return.

Super Heavy has 33 engines, while Ship has six. One booster engine shut down shortly after liftoff; a separate Raptor Vacuum engine on Ship stopped early during ascent. Spaceflight Now also reported an apparent additional booster engine shutdown during its return burn.

Despite those problems, Super Heavy completed a controlled splashdown near the Texas coast. SpaceX did not attempt to catch it at the launch tower on this flight. That booster landing was separate from Ship’s later return from orbit to the Pacific.

When did Starship explode?

The upper spacecraft reentered the atmosphere belly-first, slowing before restarting its engines and turning upright. Spaceflight Now described a controlled, tail-first splashdown at approximately 15:57 UTC. Only after reaching the ocean did it topple over and explode.

Post-splashdown destruction had happened on previous tests too. Flight 13, on July 16, was an exception: the upper stage remained intact. SpacePolicyOnline reported that SpaceX retrieved that vehicle and obtained useful heat-shield data from it.

Ars Technica reported that the Federal Aviation Administration said Flight 14 stayed within its authorized activities and would not require a formal mishap investigation. That regulatory response does not explain the engine fault or change the fact that the planned six-orbit mission ended early.

What Flight 14 means for NASA’s Moon plans

NASA Administrator Jared Isaacman welcomed the orbital milestone, writing “Gorgeous launch, getting Ship to orbit” in an official-account post reproduced by SpacePolicyOnline. SpaceX is developing a version of Starship to carry astronauts between lunar orbit and the Moon’s surface.

NASA’s May announcement described Artemis III as a planned 2027 mission in Earth orbit, testing Orion rendezvous and docking with SpaceX and Blue Origin lander pathfinders ahead of an Artemis IV lunar landing. Those are future mission plans, not capabilities demonstrated by Flight 14.

Lunar operations still require an orbital fuel depot and a demonstration of in-space cryogenic refueling, SpacePolicyOnline reported. Space.com also noted that SpaceX had yet to attempt a launch-tower catch of the upper spacecraft, another step toward its intended reuse.

As of Ars Technica’s September 28 report, SpaceX had announced no official date for the next flight. The underlying cause of the upper-stage engine shutdown also remained unestablished in that reporting.

Sources and context

AI-assisted article checked against the listed sources. NewsJaws did not conduct interviews or attend the reported events.

About NewsJaws Desk

AI-assisted reporting and explainers reviewed against the linked source documents. No claim of on-scene reporting or original interviews.