What did SpaceX’s Ship 42 static-fire tests actually prove for Starship Flight 15?

On October 28, 2026, SpaceX completed two static-fire tests for Ship 42, the Starship preparing for Flight 15: a full-duration firing of all six engines, then a single-Raptor firing simulating a deorbit burn. Here is what each test proved, why no launch date was announced, and what to watch next.

Short answer: on October 28, SpaceX completed two static-fire tests of Ship 42, the Starship being prepared for Flight 15 — first a full-duration firing of all six engines, then a second firing of a single Raptor engine that simulated a deorbit burn. In a static fire the ship is held down: the engines run for real, but nothing leaves the ground.Why there were two tests: they answer two different questions. The six-engine firing checks the ship in its flight configuration — every engine together, for the full planned duration, while engineers watch thrust, temperatures and plumbing behave as one system.

The single-engine firing rehearses a different job entirely: the short, precise burn late in a flight that slows the ship out of orbit and starts it home. Same ship, two jobs — and each one has to be proven before flight, on the ground, where a problem costs a test day instead of a vehicle.What to watch next:1. Booster tests for the Flight 15 stack — the ship is only half the vehicle.2.

The regulatory steps, including FAA licensing for the flight.3. An official SpaceX flight announcement. SpaceX gave no launch date in its October 28 post, so treat any date you see elsewhere as unconfirmed until SpaceX itself publishes one.Common mistake: do not book travel or make plans around rumoured Starship dates.

Only a SpaceX-announced date counts — everything else is a guess wearing a calendar.Ad’s take: Two firings, two jobs proven on the ground. That is how a launch date gets earned.