Connect with us

News

SpaceX Starship prototype in limbo after engine test lights rocket on fire

Published

on

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.

There’s only one obvious conclusion to draw. Whether it was something invisible to the public eye or damage related to the off-nominal fire that burned for some 15 minutes after Raptor shut down, SpaceX appears – to some extent – to have lost control of Starship SN4.

At the moment, it’s unclear what is wrong and what SpaceX is attempting to do to resolve the problem. Based on photos of Starship SN4 taken before the fire, there is good news and bad news from what can be publicly ascertained. Controlled from the ground by unprotected wires strung up and down the rocket and connected at its base, the uncontrolled fire that burned in at least two locations around Starship’s aft may have severed some or all of those critical connections.

Advertisement
Starship SN4’s third successful Raptor test caused a secondary fire that has put the vehicle in a state of limbo. (LabPadre)

That would render Starship – potentially perfectly healthy and operational – almost entirely uncontrollable, while also potentially removing SpaceX’s access to telemetry. In other words, the company may currently have no idea how pressurized all or part of Starship SN4 is and may also have little to no control of some or all of the rocket. For that to be true, Starship SN4 would, however, have to have less than fully redundant control hardware. To perform hops, for example, the ship would need both wired and radio links capable of sending telemetry and receiving commands to remain both on the ground and after liftoff.

It’s possible that Starship SN4 has the necessary hardware installed but that it wasn’t activated for the static fire test (think “Starship will never leave the ground, why would we need to enable wireless controls?”). It’s also possible that the blown pipe and methane leak that appeared to cause the secondary fire damaged crucial propellant management hardware (valves, pumps, etc.) or was just a symptom of an even worse overpressure event that damaged or destroyed multiple such systems.

Given that safety is almost certainly the priority, chances are that some combination of fairly mild hardware failure and telemetry/control loss has left SpaceX with just enough uncertainty that it can’t risk sending technicians to the launch site to inspect the damage and reestablish control. As a result, the only option left is to quite literally sit and wait until it’s once again safe to approach the rocket. Thankfully, at this point, the risk of the mystery problem actually destroying Starship SN4 is very low. If, as it appears, only its methane tank is affected, leaving some unknown quantity of latent liquid methane trapped inside, it’s possible that waiting will actually solve the problem and safe the rocket.

Starship SN4 is pictured a few hours before its ill-fated third static fire test. (NASASpaceflight – bocachicagal)
On a positive note, it appears that the concerning amount of dark smoke created in the first minute or two of the post-test fire was caused by a huge amount of tape/insulation/???? wrapped around part of Starship’s test stand in the hours before its May 19th test attempt.(NASASpaceflight – bocachicagal)

The fact that Starship hasn’t exploded yet strongly implies either that the amount of propellant trapped is minuscule or that the vast majority of SN4’s propellant management systems (including vents) remain functional. Assuming that’s the case, any remaining cryogenic propellant will eventually boil into gas, increasing the pressure inside Starship’s tanks, while those tanks will continue to vent to prevent an explosion or rupture. Eventually, Starship SN4 will be empty once again and SpaceX will be able to approach the rocket to regain control and begin inspections and repairs.

Regardless, after such an unintentionally eventful static fire test, it’s extremely unlikely that SN4 will be ready for its inaugural flight test within the next few days. Stay tuned for updates as SpaceX works to regain control over the fourth full-scale Starship prototype.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Elon Musk reveals date of Tesla Full Self-Driving’s next massive release

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Published

on

Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.

For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.

For the most part, things are better in terms of overall behavior.

However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”

He added:

“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”

Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.

Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.

Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever

They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.

Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.

Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.

It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.

What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.

Continue Reading

Cybertruck

Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party

From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone

Published

on

By

Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.

If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.

This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.

Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.

The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.

Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.

Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.

Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡

Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.

Continue Reading

News

Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

Published

on

Credit: Tesla

The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.

The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.

The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.

The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.

The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.

Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.

However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:

“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”

It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”

The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.

The investigation is listed as EA26002.

Continue Reading