Orply.

Starship Reaches Orbit, Deploys 26 Satellites Before Engine Failure Cuts Flight Short

Ed LudlowBloomberg TechnologyMonday, September 28, 20262 min read

SpaceX’s Starship reached orbit for the first time and deployed 26 satellites, but an engine failure cut the mission short. Bloomberg reports that the spacecraft splashed down in the Pacific near Hawaii about three hours into the flight. The orbital milestone and satellite deployment were achieved before the early end; the available account does not specify which engine failed or what further objectives remained.

Reaching orbit did not mean the mission ran to completion

Starship reached orbit for the first time and deployed 26 satellites into orbit. The flight nevertheless ended early: an engine failure cut the mission short, and about three hours into it the spacecraft splashed down in the Pacific near Hawaii.

Those facts describe different parts of the mission. Reaching orbit and releasing the satellites were accomplishments the flight achieved; they do not mean Starship continued through the rest of its mission as intended. Conversely, the early end does not erase the reported orbital milestone or satellite deployment. The available account identifies an engine failure as the reason the mission was cut short, but does not specify which engine failed or what further objectives remained.

26
satellites deployed into orbit

The descent readouts show a rapid approach that ended in the ocean

SpaceX’s descent footage displayed Starship’s speed and altitude as it approached the Pacific. At T+03:05:00, the readout showed 31.3 kilometers altitude and a speed of 3,420 kilometers per hour. Ten seconds later, it showed 14 kilometers and 2,653 kilometers per hour. The figures give a sense of how quickly the spacecraft was descending: over that interval, the displayed altitude fell by more than half, while the speed reading also dropped.

During the descent, a commentator said all three engines were lit, then observed that the view showed two. The footage does not establish in this brief exchange why the number changed, or connect that moment to the engine failure cited as the cause of the shortened mission. It does show engines firing during the approach.

Near the water, the display read 0.1 kilometers altitude and 27 kilometers per hour. An exterior camera then showed Starship firing its engines as it reached the ocean, producing a large burst of steam and fire. The commentator confirmed that Starship was in the water and described it as having landed.

The footage therefore records the final descent and splashdown, while the reported mission outcome supplies the wider context: Starship had reached orbit and deployed its satellites before the flight was cut short. The readouts document what the spacecraft was doing as it came down; they do not, on their own, explain the engine failure or the decision to end the mission.

The frontier, in your inbox tomorrow at 08:00.

Sign up free. Pick the industry Briefs you want. Tomorrow morning, they land. No credit card.

Sign up free