The return trip is the product.

SpaceX is aiming to fly Starship for the fifteenth time on Friday 13 November, from Starbase in Texas. The date was given at UP.Summit by the company's vice president of launch, after FAA airspace notices had earlier pencilled in the 8th and then the 12th. The plan is the part worth reading twice. On the October earnings call, Elon Musk said this flight would try to catch both stages with the launch tower: the Super Heavy booster, which has been caught three times before, and the ship itself, which never has.

Nothing about that is certain. Musk put the odds of a successful ship catch at "more likely than not", reporting at the end of last week noted the FAA had not yet listed a licence for the flight, and launch dates at Starbase move. We are not writing about whether it works on Friday. We are writing about why SpaceX keeps spending flights on the way down.

Getting there was never the expensive part

Rockets have reached orbit for nearly seventy years. What made launch expensive was that almost everything was thrown away afterwards, so every flight paid for a new vehicle. Catching the booster changed the booster's economics. Catching the ship would close the loop: the whole stack comes home, gets inspected, and flies again. The outbound trip is the visible part. The return trip is where the product is.

A ship catch is also a harder brief than a booster catch. The ship comes back from orbit, through re-entry heat, and has to arrive at a tower with enough precision for the arms to close on it. Every design decision on the vehicle is now judged twice: does it get there, and does it come back in a state worth catching.

"

If the thing has to come back, the way back is a design requirement, not an afterthought.

Installations have a return trip too

Most brand installations and event builds are designed for the opening night. The screen, the sensor rig, the kiosk shell, the software running it all. Then the event ends and the build comes down, and that is where the budget quietly leaks. Cables cut because nobody labelled them. Enclosures that only fit one venue. A content pipeline that has to be rebuilt by hand for the next city. The first stop is a launch. Every stop after that is a reuse problem.

When we build anything that tours, we try to design the strike as carefully as the set-up. The question is not only whether it works on day one, it is how quickly it can be inspected, packed, shipped and running again somewhere else, and whether the next venue needs an engineer or just a checklist.

What we would design for from the start

• 01Turnaround time as a target. Write down how long a teardown and rebuild should take, and test it before the first event, not after.
• 02Modules you can swap, not repair on site. A failed unit should come out in minutes and be fixed back at the studio.
• 03Configuration in data, not in the build. A new venue, language or brand should be a file change, not a code change.
• 04Health checks that run on boot. The kit should tell you what came back damaged before anyone plugs in a laptop.
• 05A log of every stop. What failed, what was replaced, how long the rebuild took. That is the data that makes the tenth stop cheaper than the second.

Should clients care

If you are commissioning something for one night, no. Spend on the night. If it is meant to tour, sit in a hundred shops, or run for years, the cost that matters is the cost per reuse, and that is decided at the drawing stage. SpaceX has spent years making the way back routine for the booster and is now trying it on the ship. Whatever happens on the 13th, the principle stands: plan the return trip before you plan the launch.