Starship Flight 15 is cleared to come home. Since ENN’s last update, when the ship was healthy on its long coast and the tower was go for catch, SpaceX has posted that its teams have polled go to return Starship to the launch site at Starbase1. At the same time, Elon Musk stepped in to explain what happened to the Super Heavy booster, why it showed a green flame, and why he says the setback will not slow the program down23.
Teams have polled go to return Starship to the launch site at Starbase https://t.co/BsrI3nLXFe
— @SpaceX Nov 14, 2026
Go for return to Starbase
The go poll is the decision point the whole long-duration mission has been building toward. Musk had already laid out the plan: Starship was completing 14 orbits of Earth before initiating deorbit and attempting to land at Starbase4. He added that the ship was traveling around the world about every 90 minutes5.
SpaceX’s own updates through the coast phase were steady and upbeat. Shortly after reaching its long coast, the company said teams would monitor Starship’s systems over the roughly 21 hours it intended to stay in orbit, that a few early deorbit options were available if needed, and that all systems were looking good6. Later, SpaceX reported that Starship and its heatshield were healthy after what it called a spectacular start to the mission nearly 7 hours earlier, with a return to launch site catch planned about 22.5 hours after launch7.
Musk’s own read at that point was short and positive: “So far, so good for the ship”8. Then came another SpaceX update saying Starship was coasting in orbit, still looking good for return to launch site today, and that pad and tower systems were go for catch9. The latest post turns that outlook into a formal go1.

Musk: the booster was slightly low on fuel
The open question from launch day was the booster. Replying to the account @Erdayastronaut, Musk gave a direct answer:
Booster was slightly low on fuel
That reply is the clearest statement yet of why the booster did not complete its planned return2.
@Erdayastronaut Booster was slightly low on fuel
— @elonmusk Nov 14, 2026
Why the engines burned green
Sharp-eyed watchers noticed a green tint in the booster’s engine flame. Musk confirmed what it meant in a longer post:
Yes, the green flame is caused by burning copper from depleting fuel in the regenerative cooling circuit and going oxygen-rich (closer to stoichiometric temperature) in the main combustion chamber.
In plain terms: as the fuel ran down, the engines’ cooling circuit, which uses fuel to keep hardware cool, was starved, and the combustion chamber ran with extra oxygen and higher temperatures. The green color came from copper burning3.
Musk named the root cause in the same post: “Slight underperformance of engines on this flight is the reason.” He also explained why a small shortfall matters so much here. “The booster is meant to land with tiny residuals,” he wrote, meaning the vehicle is designed to come home with very little propellant left over, so even slightly weaker engines can leave too little for the final maneuvers3.

Yes, the green flame is caused by burning copper from depleting fuel in the regenerative cooling circuit and going oxygen-rich (closer to stoichiometric temperature) in the main combustion chamber. Slight underperformance of engines on this flight is the reason. The booster is meant to land with tiny residuals, so the solution is to improve engine performance and performance consistency (underway with Raptor V3.2), as well as adjust flight software to do MECO1 about one second earlier to ensure enough propellant for boostback and landing (tiny change). These early ships and boosters are already outdated by improved designs in production or on the test stand, so this booster loss does not change our timeline to reach high volume, fully reusable Starship flights.
— @elonmusk Nov 14, 2026
The fix is already underway
What stands out in Musk’s explanation is how specific and manageable the solution is. He described two steps3:
- Better engines: improve engine performance and performance consistency, work he said is “underway with Raptor V3.2.”
- A small software change: adjust flight software to do MECO1, the first main engine cutoff, about one second earlier “to ensure enough propellant for boostback and landing.” Musk called it a “tiny change.”
Cutting the engines a second sooner trades a sliver of ascent performance for a safer propellant margin on the way back. Pairing that with more consistent Raptor engines addresses the problem from both ends3.
Why Musk says the timeline holds
Musk also put the booster in perspective. He wrote that “these early ships and boosters are already outdated by improved designs in production or on the test stand, so this booster loss does not change our timeline to reach high volume, fully reusable Starship flights”3.
That framing fits how SpaceX builds Starship: fly, learn and fold the lessons into hardware that is already moving down the line. A booster that came up a little short on propellant points to a clear engineering fix, and Musk says newer vehicles are already ahead of the one that flew3.
Meanwhile, the ship side of Flight 15 has been the bright spot of the day. SpaceX has repeatedly described the ship and its heatshield as healthy7, kept it on a long orbital coast6, and now cleared it to return to Starbase1. Earlier in this thread, ENN covered the climb to orbit and start of the Starlink V3 deployment and the launch day double catch plan.
What to watch next
The next milestones are the ones the whole flight was designed to reach:
- Deorbit: Musk said Starship would initiate deorbit after completing 14 orbits4.
- Reentry: SpaceX has said the heatshield is healthy going in7.
- The catch: SpaceX said pad and tower systems are go for catch9, with the catch planned about 22.5 hours after launch7.
- Booster follow-up: watch for progress on Raptor V3.2 and the earlier MECO1 software change Musk described3.
ENN will update this thread as Starship comes home.



