Why mission control changed its call
About seven minutes into Starship Flight 14 on September 28, 2026, one of the six white dots on the webcast’s engine display went dark. The engine that shut down was one of the three large Raptors around the outside of the upper stage. The flight plan called for those engines to finish their work on the climb. For the rest of the mission, Starship would rely on the three smaller engines clustered in the middle. SpaceX flight-day webcast, 43:07–43:11 · SpaceX mission account
The five remaining engines fired a little longer, enough to put the ship on its planned path toward the Indian Ocean. Mission control had about 17 minutes to decide whether to leave it there. One center engine could give the ship the extra speed to reach orbit. Once there, it would take another successful start to come down over a stretch of ocean already clear of ships and aircraft. The team cleared the burn after checking that all three center engines were healthy. SpaceX’s account of the coast and the engine team’s recommendation, 6:14–8:35
Watch the flight
Look for the outer dot that goes dark on the climb. Later, when the webcast shows the burn for orbit, just one dot lights up in the middle.
What the Indian Ocean option bought the team
SpaceX had planned the first part of the flight so that even a ship that lost contact with the ground would come down in a known place. At engine cutoff, Starship was high above Earth and moving fast, but its path still curved back into the atmosphere over the Indian Ocean. It could reach that water with every engine switched off. All 26 Starlink satellites were still aboard. SpaceX’s preflight plan
That explains the two announcements on the live webcast. At about eleven minutes, the host said the ship would skip the burn for orbit. At about fifteen minutes, he reported that the three center engines looked healthy. SpaceX calls them sea-level Raptors, but they can restart in space. In the company’s later film, the engineer responsible for the engines describes recommending that the flight continue. The ship and engine teams gave their go-aheads in the final poll. Flight-day webcast, 47:06–57:51 · Mission-control poll
About 25 minutes after liftoff, one of those engines fired. It gave Starship enough sideways speed to keep circling Earth. The ship then released its payload. A little over an hour after launch, the host reported all 26 satellites away. SpaceX later said each had connected to the Starlink network. The independent satellite catalog lists 26 Starlinks from the launch and a separate entry for the ship. SpaceX mission results · CelesTrak catalog for launch 2026-225
What happened to engine six?
In SpaceX’s film, a voice on the engine team’s radio reports that the computer controlling engine six appears to have reset. Twelve days after the flight, Elon Musk said he suspected a problem in that computer’s software. He said the other engine computers showed no apparent sign of the same problem. That distinction mattered in flight because a fault shared by the center engines could also threaten the burn to bring the ship home. Engine-team call, 1:34–1:40 · Musk’s October 10 answer, 23:20–24:15
What triggered the apparent reset? SpaceX’s postflight account records the lost thrust and how the ship made up for it. The engine-team call and Musk’s interview leave the trigger unresolved. SpaceX postflight account · Musk on the engine computer
Why come down near Hawaii?
The original schedule put splashdown off Chile almost ten hours after launch. A long coast would let engineers see how the ship handled a restart after hours in orbit. Its methane and oxygen have to reach the engines as liquids. Heat getting into the tanks can turn some of either liquid into gas. And while the ship coasts, liquid can drift away from the outlets that feed the engines. In the film, an engineer says the team had ways to settle the propellant back into place. SpaceX mission timeline · Propellant and restart discussion, 13:57–14:31
There was another landing area north of Hawaii, also cleared before launch. It came up much sooner. With the satellites already away and the ascent shutdown still unexplained, one controller asked what else the team might have missed. The group judged the earlier reentry the lower-risk choice. SpaceX’s postflight account gives the ascent engine problem as the reason it shortened the flight. Return discussion and decision, 12:42–14:53 · Mission results
At about two hours and twelve minutes, a single center engine restarted and slowed the ship enough to bring it back into the atmosphere. Close to the water, all three center engines started for the landing maneuver. A buoy camera caught Starship turning upright and splashing down just over three hours after it left Texas. The 26 satellites stayed in orbit. Flight-day webcast, 2:48:07 and 3:44:11 · SpaceX flight results
Flight records and further reading
- SpaceX’s September 28 mission account includes both the written result and the original schedule. The nearly ten-hour landing time in the schedule was the plan for Chile.
- SpaceX’s flight-day webcast carries the live announcements. Replay times above use the player clock. Liftoff comes about 35 minutes and 50 seconds into the broadcast.
- Go For Orbit is SpaceX’s edited account from inside mission control. The October interview records Musk’s separate assessment of engine six.
- For a case where ground tests helped investigators pin down a failure in space, read how a change in ground power damaged Apollo 13’s oxygen tank.
