SpaceX has completed a Starship catch for the first time using the large mobile arms of its launch and recovery tower, informally known as Mechazilla. During Flight 15, the spacecraft re-entered, shifted into an upright position, and slotted between the tower’s two catching arms. This outcome stands apart from those achieved previously with the boosters: this time, the recovered element was Starship itself.

However, the mission did not conclude with the recovery of the entire system. The booster initially had a flight profile that also called for a catch, but the procedure was aborted. SpaceX is still working to determine why the vehicle aborted the landing before exploding over the Gulf of Mexico. The success of the spacecraft and the failure of the booster therefore coexist within the same test: on the one hand, a technical first achieved; on the other, an anomaly that remains to be clarified.

A maneuver tested on boosters, now achieved with the spacecraft

The term “chopstick catch,” widely used to describe this type of recovery, refers to the appearance of the tower’s two arms as they close around the vehicle. SpaceX had already performed booster catches using this infrastructure. The novelty of Flight 15 is that the method was successfully applied to the Starship vehicle—that is, the component designed to continue flight after separating from the booster.

Footage of the final phase shows the spacecraft punching through the clouds, adjusting its attitude into a vertical position, and approaching the tower. The final moments are the most critical: Starship must reach the area between the arms along a trajectory compatible with the catch, while the tower must complete the operation at the intended moment. The sequence concluded with the vehicle supported by the Mechazilla structure.

The significance of the event lies primarily in practical verification. Tower recovery is no longer merely an objective shown in simulations or a capability demonstrated by the booster: SpaceX now has a successful precedent for Starship as well. This does not yet amount to a routine procedure, nor does it erase the issues that emerged during the same flight, but it narrows one of the program’s greatest areas of uncertainty.

Flight 15 remains a test with a mixed outcome

Reducing the day solely to the catch of the spacecraft would, however, be misleading. SpaceX was aiming to recover the launch stack, and the booster did not complete its part of the maneuver. After the landing abort, the vehicle exploded over the Gulf of Mexico. No causes have been stated: the company is currently analyzing what happened.

For an experimental program, a partial outcome can still be significant if it allows what worked to be isolated from what requires correction. In this case, the catch of Starship demonstrates that the interaction between the spacecraft and the tower has reached a level sufficient for a first complete execution. Conversely, the failure to recover the booster serves as a reminder that the reliability of the entire architecture cannot be deduced from a single successful step.

It is an important distinction in how future tests will be viewed as well. The metric to measure will not merely be repeating the catch of the spacecraft: SpaceX will need to verify whether the operation can be performed again and consistently, as well as understand what prevented the booster from completing its return. Until that investigation is concluded, it is not possible to attribute the abort to a specific cause.

Why the tower is central to the recovery strategy

Mechazilla combines two key functions cited by SpaceX into a single infrastructure: launch and catch. The concept of returning vehicles directly to the tower makes the launch site an active part of the mission’s final phase, rather than limiting it to liftoff. This is precisely what makes the maneuver so visible: the return concludes in the very area from which the vehicle departed, requiring extremely close coordination between the vehicle in flight and the ground structure.

The company had already gained experience with boosters, a factor that made attempting the next step with Starship reasonable. However, a precedent with one component of the system does not automatically guarantee the same outcome with the other. Flight 15 provided the first concrete confirmation that catching the spacecraft can succeed; it has not yet proven that every part of the flight profile can unfold without exception.

Ahead of the flight, Elon Musk addressed the topic during SpaceX's third-quarter earnings call, noting that success was not guaranteed but viewing the odds for the following mission as favorable. The prediction was only partially fulfilled. Starship was caught by the tower, while the booster was not recovered. The most accurate assessment of the facts is therefore that of a technical milestone achieved within an incomplete mission.

What to watch for in upcoming flights

The next test will be the ability to turn this event into a repeatable procedure. SpaceX will first need to complete its analysis of the booster abort and determine what modifications, if any, to implement. Only subsequent tests will tell whether recovering Starship with Mechazilla will remain an isolated demonstration or become a standard phase of operations.

In the meantime, Flight 15 shifts the program's starting point. Until now, catching the spacecraft was a goal yet to be achieved; after this flight, it is a maneuver already executed at least once. It is a significant but limited shift: it does not resolve the booster anomaly and does not automatically turn the entire system into a vehicle that can be recovered on every mission.

The successful sequence confirms, however, that SpaceX is pushing testing beyond simple controlled re-entry. Attention will now shift from the spectacle of the first catch to the quality of the data gathered: approach precision, tower behavior, and the causes of the abort recorded by the booster. These are the elements that will determine how quickly the outcome of Flight 15 can become a repeatable operational capability.

Sources