Starship Flight 13: What SpaceX Changed After Flight 12

If Starship lifts off as soon as Thursday, July 16, the most revealing moments will not be the first seconds of the climb. They will come just after separation, when Super Heavy must turn the right way and restart multiple engines, and later when Starship tests whether it can learn more about its heat shield in flight.

SpaceX says its 13th Starship flight test is currently targeting a 90-minute window opening at 5:45 p.m. Central Time on July 16 (7:45 p.m. BRT). The schedule is dynamic, so use the official SpaceX Flight 13 mission page for the live status and webcast; coverage is expected to begin about 30 minutes before liftoff.

This is not simply another launch-date story. Flight 13 is a live check of how SpaceX responded to specific Flight 12 behavior: a booster that turned about 90 degrees away from its intended direction during stage separation, five booster engines that had trouble relighting for boostback, and an upper-stage vacuum engine outage. It is also meant to fly 20 next-generation Starlink V3 satellites and test a new way of inspecting thermal-protection tiles while in space.

First: a better-controlled booster flip

The first engineering checkpoint arrives during hot-staging. Starship’s upper stage ignites and separates while the Super Heavy booster begins its maneuver for a boostback burn. SpaceX says that on Flight 12, small differences in the upper stage’s engine-start timing left the booster’s directional flip approximately 90 degrees off its intended orientation.

That detail matters because orientation is not cosmetic. A booster has to point its thrust in the intended direction to make the most effective return maneuver. SpaceX says it has changed the start sequence to make it more tolerant of timing variability and more reliable at flipping in the desired direction. Flight 13’s offshore Gulf landing-point plan makes this a test of the complete chain: ascent, separation, flip, boostback, and landing burn—not a promise of a tower catch.

Then: can the relight logic work in a 33-engine environment?

After Flight 12’s separation and flip, five of Super Heavy’s 33 engines encountered issues during attempted relight. That ended the boostback burn early. For Flight 13, SpaceX describes both hardware changes aimed at relight reliability and updates to engine alarms and abort logic tailored to the multi-engine flight environment.

That last phrase is worth lingering on. A single-engine test can establish basic behavior; a booster relight must manage many engines, shared propellant conditions, timing, and fault detection at once. The public timeline lists boostback burn start at about 2 minutes 25 seconds after liftoff and landing-burn start at about 6 minutes 27 seconds. Those timings are approximate, but they give livestream viewers a practical checklist.

For context on why Flight 12’s findings remain part of the story, read our guide to the FAA’s Flight 12 mishap investigation. Flight 13 is a developmental test, so a result can generate useful data even when it does not follow the nominal sequence perfectly.

Starship’s engine-out response is also under the microscope

SpaceX says the upper stage lost one of its three vacuum-optimized Raptor engines roughly 40 seconds after separation on Flight 12. The vehicle still reached its planned suborbital trajectory, demonstrating its engine-out capability. For Flight 13, SpaceX says it has made hardware and operational changes addressing interconnected causes, with additional Raptor reliability improvements planned for future versions.

The planned upper-stage sequence is ambitious: deploy 20 Starlink V3 satellites, relight one Raptor in space, then conduct a controlled entry, descent, and splashdown in the Indian Ocean. The on-orbit relight is listed around 38 minutes 58 seconds after liftoff in SpaceX’s current timeline. That is a distinct test from the initial ascent engine issue: it asks whether a single engine can be restarted in the very different conditions of space.

The heat-shield experiment is a measurement test, not a stunt

Flight 13 also adds an unusually concrete inspection demonstration. SpaceX says six of the 20 Starlink V3 satellites will carry cameras intended to scan Starship’s heat shield and send imagery to operators. The company has painted several tiles white to simulate missing tiles and act as imaging targets.

The point is to develop ways to judge thermal-protection readiness for future returns to the launch site. SpaceX also plans to test tiles mounted on the metallic side of the aft flaps, modified tile-attachment approaches near the aft skirt, and load-sensing tiles. Those sensors are intended to measure stresses under higher ascent dynamic pressure—an engineering trade that could support more payload to orbit but places extra demand on the tile attachments.

What to watch, wherever you are

For viewers in Austin, Houston, or Los Angeles, this is a livestream-first event rather than a local skywatching opportunity. Set a reminder for roughly 30 minutes before the currently listed window, then check the official mission page again before you settle in: SpaceX specifically warns that the schedule is likely to change.

During the webcast, listen for four milestones:

1. Stage separation and booster orientation — does the flip look controlled before boostback?
2. Boostback and landing-burn sequence — are the relights and engine-management calls nominal?
3. Satellite deployment and in-space relight — does the upper stage complete both demonstration objectives?
4. Entry and heat-shield observations — what does SpaceX say about the inspection-target tiles, attachment tests, and entry data?

The best way to enjoy a complicated launch is with people who are happy to pause, ask why a maneuver matters, and compare notes afterward. Join the Cosmic Match space community to meet fellow launch-watchers, or explore the Cosmic Match homepage to find your next shared night-sky conversation.

All launch timing and objectives in this article reflect SpaceX’s official Flight 13 mission page as checked on July 14, 2026. Developmental-test plans can change before liftoff.