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

Lifestyle

NTSB findings on fatal Tesla crash tell a very different story

The NTSB confirmed the driver, not Tesla’s FSD, caused the fatal Texas house crash.

Published

on

By

The National Transportation Safety Board released preliminary findings Wednesday confirming that a Tesla driver, not the vehicle’s software, caused a fatal crash in Katy, Texas in June. The driver, 44-year-old Michael Butler, had engaged Full Self-Driving Supervised mode on Rose Hollow Lane, a residential street with a 30 mph speed limit, before manually overriding the system by pressing the accelerator pedal all the way to 100%. Data recovered from the 2025 Tesla Model 3 showed the vehicle was traveling over 70 miles per hour when it struck a home and killed 76-year-old Martha Avila, who was inside. Weather was clear, the road was dry, and it was daylight.

Texas man charged in fatal Tesla crash where he blamed Autopilot

Butler told authorities he had passed out at the wheel. But security camera footage obtained by the NTSB told a different story, and showed the car accelerating through an intersection before leaving the road entirely. Police also found that Butler’s phone had Google searches including the terms “Tesla FSD not aggressive enough 2026” and “Tesla FSD too timid,” raising serious questions about how he was using the system before the crash. Butler has since been charged with manslaughter. The victim’s family has filed a lawsuit against both Butler and Tesla, alleging negligence.

The NTSB findings aligned directly with what Tesla VP of AI Software Ashok Elluswamy had already stated publicly on X in the weeks after the crash, writing that “the driver manually overrode self-driving by pressing the accelerator all the way to 100%.” The data confirmed his account.

Continue Reading

Investor's Corner

Lucid CEO dispels any rumors of bankruptcy: ‘So far from the facts’

Published

on

Credit: Lucid

Lucid CEO Silvio Napoli responded to rumors of an imminent bankruptcy that was reportedly being mulled after a report stated the automaker was working with the firm AlixPartners to iron out its next steps.

The company felt a massive loss on Wall Street yesterday, as the report essentially pushed the stock down as much as 55 percent on Tuesday.

The report, published initially by Eletric-Vehicles.com, claimed Lucid was essentially in dire straits and was told by AlixPartners, a commonly used restructuring advisor, to either take shares private or file for Chapter 11 bankruptcy protection.

Lucid denies rumors of bankruptcy after over 40% stock drop

Lucid’s head of Communications, Nick Twork, immediately challenged the report and stated the company “has sufficient liquidity to carry its operations well into next year.”

Now, the company’s CEO is chiming in as well, stating that the report is “so far from the facts that they require a direct response.”

Napoli said:

“Lucid is not considering bankruptcy or a transaction to take the company private. Those reports are false. The Board did not explore either scenario. Period.

As disclosed in our most recent quarterly filing, Lucid has sufficient liquidity to fund its operations well into next year.

We work with outside advisors to improve operational performance and execution. They are not advising Lucid on a take-private transaction or bankruptcy, and any suggestion that they have recommended either course of action to management or the Board is false.

My priority is clear: turn this company around. That is where the leadership team and I are focused.

I look forward to providing a full update during our quarterly earnings call on August 4th.”

It seems pretty clear that Lucid is confident things will be okay, and, to be honest, they should not have much to worry about, especially considering the company has been backed by the Saudi Public Investment Fund (PIF) for years. It has solid financial backing, and its sales, while weak, are pretty much right on par with a company of this age.

Lucid also sent a Cease & Desist letter to the publication for their report.

Lucid shares have rebounded nicely and are up nearly 21 percent at the time of publication. As soon as the company dispelled the rumors of bankruptcy yesterday, the stock began to climb back toward more reasonable levels.

Continue Reading

News

Tesla responds to strange Supercharging pricing error with classy move

Published

on

(Credit: Tesla)

Tesla has once again demonstrated strong customer focus by swiftly addressing and fully refunding a bizarre Supercharger pricing glitch that affected drivers in Atlantic Canada.

The issue surfaced earlier this month when the Tesla app began displaying dramatically inflated per-minute charging rates at stations in Prince Edward Island and parts of New Brunswick.

One widely shared screenshot from a Charlottetown, PEI Supercharger showed rates reaching ridiculous levels: $6.00 per minute for the 180-250 kW tier, along with $3.57/min for 100-180 kW and $2.29/min for 60-100 kW.

These figures were several times higher than normal Supercharger pricing in the region.

To put the error in perspective, charging at the highest incorrect rate would have been shockingly expensive.

At 250 kW, a common charging speed at Superchargers, a vehicle pulls roughly 4.17 kWh per minute. Under the glitch, a driver spending just 10 minutes at peak power would face a $60 bill. A typical 20- to 30-minute session to add meaningful range could have cost $120 to $180 or more, before any congestion fees.

Tesla gets another layer of gamification with Free Supercharging on the line

By comparison, standard Canadian Supercharger rates usually fall between $0.25 and $0.60 per kWh, making a similar session cost roughly $15–$40. The erroneous per-minute structure, combined with the inflated numbers, turned what should be a convenient stop into a potential financial shock.

The glitch appears to have started sometime around early July, and quickly drew attention on social media as owners questioned whether Tesla had implemented steep hidden increases. Some drivers even reported seeing $0 charges in their history, indicating broader billing confusion.

Tesla’s official Charging account on X stated that correct pricing would roll out at midnight on July 13, so the fix is already in effect. More importantly, the company announced it would waive all fees for every Supercharger session since July 2. This blanket waiver covers the entire affected period without requiring users to file individual claims, with automated refunds expected soon. The decision affects stations in PEI and nearby areas in New Brunswick and Nova Scotia.

It’s a classy move, and rather than issuing partial credits or forcing owners to submit support tickets, Tesla simply absorbed the cost of the system error and made drivers whole. In an industry where hidden fees and bill disputes are common, Tesla’s proactive, no-questions-asked approach reinforces owner trust and highlights the company’s commitment to service excellence.

The incident, while disruptive for a short time, ultimately showcases Tesla’s ability to own mistakes and prioritize customer satisfaction. Atlantic Canada Tesla owners can now charge with confidence again, knowing the company has their back when technology glitches occur.

In an era of complex EV billing, such transparency and generosity are refreshing and set a positive example for the industry.

Continue Reading