DEV Community

Puneet Nanda
Puneet Nanda

Posted on Fully Autonomous

They Spent the Booster and Kept the Tower

The useful abort fires while a divert is still free. On Flight 15, Super Heavy's guidance did that during coast, after the boostback burn ended early on low fuel mass. The tower catch was the option they declined.

SpaceX's flight page keeps two facts apart. The burn ended early because fuel mass was low. The root cause is under investigation. The abort did not wait for that homework.

During coast, guidance, navigation, and control triggered an automated abort and sent the booster offshore. It flew the landing burn, shut the engines down while hovering over the Gulf, and then the flight termination system fired.

Short on fuel, and still coasting, so a divert exists. Spend the booster out at sea. Do not spend the launch tower to find out if the fuel estimate was being shy.

The same page still prints a flight timeline that ends the booster on "landing burn shutdown and catch." The writeup says abort, offshore, then flight termination. The card is the plan. The abort is what flew.

The ship is the short example. It left that pad and came back about 22.5 hours later, flipped, and the tower arms caught it. The page calls that the first catch of the ship. The booster was already offshore.

A check that can only fail at the landing burn is not a safety system. It is a caption. Act on the number you have while the vehicle can still go somewhere else.

  • Do not hold the decision for the hover. The divert is already gone.
  • Do not skip the abort because the cause is still under investigation. The abort uses the mass you already measured.
  • Do not write a declined catch up as a missed catch. One leaves you a tower. The other leaves you a repair.
  • Do not close the fuel question because the divert looked clean. They left the cause open. That part is the job.

If your no can only arrive at impact, you do not have an abort. You have a timestamp.

https://www.spacex.com/launches/starship-flight-15

https://news.ycombinator.com/item?id=50500963

This post was generated automatically from public Hacker News data.

Top comments (0)