Fire during most recent Starship prototype test


Please consider donating to Behind the Black, by giving either a one-time contribution or a regular subscription, as outlined in the tip jar below. Your support will allow me to continue covering science and culture as I have for the past twenty years, independent and free from any outside influence.


 

Regular readers can support Behind The Black with a contribution via paypal:

Or with a subscription with regular donations from your Paypal or credit card account:


 

If Paypal doesn't work for you, you can support Behind The Black directly by sending your donation by check, payable to Robert Zimmerman, to
 
Behind The Black
c/o Robert Zimmerman
P.O.Box 1262
Cortaro, AZ 85652

Capitalism in space: A fire during most recent Starship prototype test that did not do any apparent serious damage has however left that prototype in limbo.

The fate of SpaceX’s fourth full-scale Starship prototype appears to be in limbo after a third (seemingly successful) engine ignition test unintentionally caught the rocket on fire.

Now more than 12 hours after Starship SN4 fired up its new Raptor engine, the ~30m (~100 ft) tall, 9m (~30 ft) wide prototype is apparently trapped with one or both of its propellant tanks still partially filled with liquid (or gaseous) methane and/or oxygen. An initial road closure scheduled from noon to 6pm local quickly came and went and SpaceX and Cameron County Texas have since modified the paperwork, extending the closure a full 24 hours. In other words, SpaceX has reason to believe that Starship SN4 may continue to be unsafe (i.e. pressurized) as many as ~30 hours after it technically completed its third static fire test – extremely unusual, to say the least.

The article at the link offers a lot of speculation. The bottom line is that the first actual hop of this prototype is probably delayed. SpaceX had said it wanted to do it before the end of the month (probably to maximize publicity by having it occur about the same time as the manned Dragon launch). They will need to get this prototype safed, review the data and damage from the fire, and then make repairs before doing that hop. I would also expect SpaceX to do another tank and engine test first as well, to make sure those repairs worked.

This is not to say that the delay will be long. SpaceX does not waste time in these matters. It just probably means the hop won’t occur until mid- to late June.

Share

2 comments

  • geoffc

    Seems like some wrapping left on the pad was part of the fire, but a gas relief line may have torn/burned off causing the detanking issues.
    We shall see.

  • Ray Van Dune

    When I had to leave the NASASpaceFlight webcast after the fire, there was still speculation about the apparent failure of the water deluge system, and whether that had contributed to damage that allowed a fire to occur. Has it been determined whether the deluge system failed?

    I saw no evidence of a water deluge prior to the static fire, and I cannot imagine that if the deluge is essential, the firing would have been allowed to proceed without it! Note that a water deluge is not usually just to cool the pad, but also to absorb sonic shockwaves that can cause mechanical damage to the launchpad, and the vehicle itself.

Leave a Reply

Your email address will not be published. Required fields are marked *