SpaceX Starship Flight 13 Launch, Date, Mission Details, and What to Expect

Quick Answer

SpaceX's Starship Flight 13 launched successfully on July 24, 2026, from Starbase in Texas after multiple delays and a previous abort. The mission deployed 20 production Starlink V3 satellites during a sub-orbital test flight, demonstrated an in-space Raptor engine relight, and achieved a controlled ocean splashdown of the upper stage.

This flight marked the second launch of the Block 3 Starship vehicle and represented a significant step forward in SpaceX's iterative development process.

Key Facts

• Launch date: July 24, 2026 (originally targeted July 23, delayed by 24 hours)
• Launch window: 5:45 PM to 7:15 PM CDT (22:45-00:15 UTC)
• Launch site: Pad 2, Starbase, Texas
• Vehicle: Integrated Starship (Booster B20-1, Ship S40-1) - Block 3 version
• Mission type: Sub-orbital test flight with trans-atmospheric trajectory
• Payload: 20 production Starlink V3 satellites
• Key milestones achieved: Payload deployment demonstration, Raptor in-space relight demonstration, controlled entry and landing burn
• Booster recovery: Expended (water splashdown, no recovery attempted)
• Ship recovery: Expended (water splashdown, no recovery attempted)
• Previous attempts: T-0 abort on July 16, weather scrub on July 23
• Live webcast: Began approximately 30 minutes before liftoff, available on SpaceX's website and X platform

The Road to Flight 13 Delays, Aborts, and a Successful Launch

Why This Launch Was Different

Starship Flight 13 was not just another test in SpaceX's development campaign. It represented the second flight of the Block 3 vehicle architecture, which had debuted on Flight 12.

The Block 3 upgrade includes significant hardware changes compared to earlier Starship prototypes, and Flight 12 had revealed issues that needed correction. The reference material indicates that Flight 13 aimed to "correct issues from version 3's debut flight," though specific details about those issues are not provided in the available sources.

The vehicle configuration for Flight 13 consisted of Booster B20-1 and Ship S40-1. Both were designated as expendable for this mission, meaning neither the Super Heavy booster nor the Starship upper stage would be recovered.

Instead, both would attempt controlled water splashdowns in the ocean. This decision suggests that SpaceX prioritized data collection and payload deployment over recovery operations for this test.

The Abort That Reset the Schedule

SpaceX's first attempt at Flight 13 occurred on July 16, 2026. During the countdown, the launch was aborted at T-0, meaning the engines were commanded to start but the computer detected an anomaly and shut everything down at the last second.

The reference content describes this as a "T-0 abort" that occurred on the vehicle's third attempt overall (counting earlier aborted attempts from previous flights). Following the abort, SpaceX reset the launch target to July 23.

The company then faced a weather scrub on that date, pushing the launch to July 24. This pattern of aborts and weather delays is common in developmental test programs, where hardware margins are thin and mission success depends on precise conditions.

Launch Day July 24, 2026

On July 24, the launch window opened at 5:45 PM CDT and lasted 90 minutes until 7:15 PM CDT. The vehicle successfully lifted off from Pad 2 at Starbase, Texas, during this window.

The reference material confirms that the launch was "successful" and that the mission achieved its primary objectives. The timeline of key events during the flight, as detailed in the reference content, includes:

• Flame diverter activation at T-0:17 seconds
• Booster engine startup command at T-0:03 seconds
• Liftoff at T-0:00
• Payload deployment demonstration started at T+16:40 and completed at T+27:39
• Raptor in-space relight demonstration at T+38:58
• Starship entry at T+47:30
• Transonic transition at T+1:02:23
• Subsonic transition at T+1:03:01
• Landing burn start at T+1:05:01
• Landing flip at T+1:05:03
• Landing burn engine reduction (3 to 2 engines) at T+1:05:12
• Landing burn reduction (2 to 1 engine) at T+1:05:19
• Landing at T+1:05:21

The reference material describes the landing as "exciting," though it does not specify whether the landing was fully successful or if there were anomalies. Given that the vehicle was expendable and planned for a water splashdown, the "exciting" description likely refers to the complexity of the maneuver rather than a specific outcome.

What Flight 13 Achieved Starlink Deployment and Technology Demonstrations

Deploying the Next Generation of Starlink Satellites

The most commercially significant aspect of Flight 13 was the deployment of 20 production Starlink V3 satellites. The reference material consistently describes these as "V3" or "the most advanced Starlinks," indicating that these are not the standard Starlink satellites currently in orbit but rather the next-generation design.

The deployment occurred during a 20-minute sub-orbital test. The timeline shows that the payload deploy demonstration started at T+16:40 and was completed by T+27:39.

This means the satellite deployment took approximately 11 minutes, which is consistent with a sequential release mechanism rather than a single batch ejection. It is important to note that the satellites were deployed during a sub-orbital trajectory, not a full orbital insertion.

This suggests that the satellites themselves may have been non-operational test units, or that they were deployed with the expectation that they would not achieve stable orbit. The reference material does not clarify whether the 20 satellites were operational prototypes or inert mass simulators.

However, the fact that SpaceX chose to integrate real production satellites into the payload bay indicates that the company is moving beyond simple mass simulators and toward operational capability. The V3 satellites are presumably larger and more capable than the current V2 Mini versions, and deploying them from Starship validates the vehicle's ability to carry heavy payloads to deployment altitude.

The In-Space Engine Relight A Critical Milestone

At T+38:58, approximately 39 minutes into the flight, SpaceX performed a Raptor engine relight demonstration. This is one of the most technically challenging aspects of any rocket system.

Relighting an engine in space requires precise propellant management, ignition system reliability, and proper ullage (settling the propellant in the tanks using small thrusters before main engine ignition). The Raptor engine uses a full-flow staged combustion cycle with methane and liquid oxygen.

While Raptor has been tested extensively on the ground and during previous flights, in-space relight remains a critical capability for Starship's future missions. Without the ability to restart the engine in orbit, Starship cannot perform orbital maneuvers, trans-lunar injection burns, or de-orbit burns for controlled reentry.

The fact that SpaceX included this demonstration as a named milestone suggests that the relight was successful. The reference material does not provide additional details about the relight duration or whether it was a full-duration burn, but the inclusion of the milestone in the timeline indicates that it was a planned objective that was achieved.

Controlled Entry and Landing Dynamics

After completing the payload deployment and engine relight demonstrations, the Starship upper stage began its entry sequence at T+47:30. The vehicle transitioned through transonic speeds (approximately Mach 1) at T+1:02:23 and became subsonic at T+1:03:01.

These transitions are critical because aerodynamic forces change dramatically as the vehicle passes through the speed of sound. The landing burn started at T+1:05:01, just four minutes after the vehicle became subsonic.

At T+1:05:03, the vehicle performed a "landing flip" maneuver. This is the signature Starship landing sequence where the vehicle transitions from a horizontal belly-flop orientation to a vertical landing configuration.

The flip is accomplished by using the vehicle's forward and aft flaps to pitch the nose upward while the engines ignite to slow the descent. The reference material shows that the landing burn began with three engines, then reduced to two engines at T+1:05:12, and finally to one engine at T+1:05:19.

This engine reduction sequence suggests that the vehicle had more thrust than needed for a gentle touchdown, so the flight computer shut down engines one by one to fine-tune the descent rate. The landing occurred at T+1:05:21, just two seconds after the final engine reduction.

The reference material does not specify whether the landing was a stable splashdown or if the vehicle experienced any issues during the final moments. The description "an exciting landing" could indicate a successful but dramatic conclusion, or it could mean that the vehicle tipped over or exploded on contact with the water.

Given that the vehicle was planned for an expendable water landing, a hard impact would still be considered within expected parameters.

How Flight 13 Fits into SpaceX's Larger Starship Development Plan

From Flight 12 to Flight 13 The Iterative Improvement Cycle

Flight 12 introduced the Block 3 vehicle architecture, which includes upgrades to the engines, thermal protection system, and structural design. The reference material indicates that Flight 12 focused on "booster recovery objectives," while Flight 13 shifted attention to upper stage performance and payload deployment.

The progression from Flight 12 to Flight 13 demonstrates SpaceX's standard iterative development approach: test one set of objectives, learn from the results, fix the issues, and test again with new objectives. On Flight 13, the booster (B20-1) was expended rather than recovered, suggesting that the company may have been testing new booster hardware or software that was not yet mature enough for a landing attempt.

The ship (S40-1) was also expended, which is consistent with SpaceX's strategy of sacrificing hardware for data. Each flight test generates enormous amounts of telemetry and video data that engineers use to refine the vehicle design.

The specific issues from the Block 3 debut on Flight 12 that Flight 13 aimed to correct are not detailed in the available sources, but they likely involve engine performance, thermal protection system durability, or flight control software.

Preparing for Flight 14 and Beyond

The reference material includes a mention of "Flight 14 developments" in one of the YouTube descriptions, suggesting that SpaceX is already planning the next test flight. The timeline for Flight 14 is not specified, but based on the pattern of previous flights—where gaps between flights have shortened as the program matures—a launch later in 2026 or early 2027 is plausible.

The successful deployment of Starlink V3 satellites on Flight 13 is a significant milestone for the Starship program's commercial viability. SpaceX has stated that Starship is designed to eventually replace Falcon 9 for Starlink launches, and each successful payload deployment brings that transition closer.

The V3 satellites are presumably larger and more capable than the current generation, meaning fewer launches would be needed to maintain and expand the constellation. However, the fact that the satellites were deployed during a sub-orbital test rather than a full orbital mission raises questions about whether Starship is ready for operational Starlink launches.

For the satellites to reach orbit, the Starship upper stage would need to perform a circularization burn after deployment, which requires the in-space engine relight capability that was demonstrated on this flight.

What This Means for the Human Spaceflight Timeline

Starship is central to NASA's Artemis program for returning humans to the Moon, and SpaceX has its own ambitions for Mars colonization. Each successful flight test reduces the technical risk associated with these long-term goals.

The reference material does not explicitly mention Artemis or Mars, but the capabilities demonstrated on Flight 13—payload deployment, in-space engine relight, and controlled reentry—are all necessary precursors to human spaceflight missions. The landing flip maneuver and engine reduction sequence are particularly relevant, as these are the same dynamics that would be used for landing Starship on the lunar surface or on Mars.

It is worth noting that Flight 13 did not attempt a landing on a landing pad or drone ship. All landings so far have been water splashdowns.

Before Starship can carry crew, the landing accuracy and reliability must be demonstrated on solid ground. This will likely be a focus of future flights.

Frequently Asked Questions

When did SpaceX Starship Flight 13 actually launch?

Starship Flight 13 launched on July 24, 2026, after a 24-hour delay from the original target date of July 23. The launch occurred during a 90-minute window that opened at 5:45 PM CDT from Starbase, Texas.

What payload did Flight 13 carry?

The mission carried 20 production Starlink V3 satellites. These are described as the "most advanced Starlinks" in the reference material, indicating they are a next-generation design compared to the current operational satellites.

Was the Starship upper stage recovered after Flight 13?

No. Both the Super Heavy booster and the Starship upper stage were designated as expendable for this mission.

They were planned to perform controlled water splashdowns with no recovery attempt. The reference material describes the landing as "exciting" but does not specify whether the vehicle survived the landing intact.

Why was Flight 13 delayed multiple times?

The flight experienced a T-0 abort on July 16, 2026, where the engines were commanded to start but the computer shut everything down at the last second. A subsequent attempt on July 23 was scrubbed due to weather.

The successful launch occurred on July 24.

What were the main objectives of Flight 13?

The primary objectives were to deploy 20 Starlink V3 satellites, demonstrate an in-space Raptor engine relight, achieve a controlled entry and landing burn, and correct issues identified during the Block 3 vehicle's debut on Flight 12. The payload deployment and engine relight demonstrations were completed during the flight.

Reference Notes

Information in this article is based on publicly available sources, including SpaceX's official launch page, space news websites, and YouTube livestream descriptions. Some details, such as the specific issues corrected from Flight 12 and the exact outcome of the landing, may be clarified in future official statements.

Some details may change over time. Verify with official sources before acting.