News
SpaceX Starship prototype in limbo after engine test lights rocket on fire
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.

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.


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.
Elon Musk
Musk forces Judge’s exit from shareholder battles over viral social media slip-up
McCormick insisted in a court filing that she harbors no actual bias against Musk or the defendants. She claimed she either never clicked the “support” button, LinkedIn’s version of a “like,” or did so accidentally.
Many Tesla fans are familiar with the name Kathaleen McCormick, especially if they are investors in the company.
McCormick is a Delaware Chancery Court Judge who presided over Tesla CEO Elon Musk’s pay package lawsuit over the past few years, as well as his purchase of Twitter. However, she will no longer be sitting in on any issues related to Musk.
Elon Musk demands Delaware Judge recuse herself after ‘support’ post celebrating $2B court loss
In a rare admission of potential optics issues in one of America’s most powerful corporate courts, Delaware Chancery Court Chancellor Kathaleen McCormick stepped aside Monday from a cluster of shareholder lawsuits targeting Elon Musk and Tesla’s board.
The move came just days after Musk’s legal team highlighted her apparent “support” on LinkedIn for a post that mocked the billionaire over his 2022 tweets about the $44 billion Twitter acquisition.
McCormick insisted in a court filing that she harbors no actual bias against Musk or the defendants. She claimed she either never clicked the “support” button, LinkedIn’s version of a “like,” or did so accidentally.
She wrote in a newly published memo from the Delaware Chancery Court:
“The motion for recusal rests on a false premise — that I support a LinkedIn post about Mr. Musk, which I do not in fact support. I am not biased against the defendants in these actions.”
Yet she granted the reassignment anyway, acknowledging that the intense media scrutiny surrounding her involvement had become “detrimental to the administration of justice.”
The consolidated cases will now be handled by three of her colleagues on the Delaware Court of Chancery, the nation’s go-to venue for high-stakes corporate disputes. The lawsuits accuse Musk and Tesla directors of breaching fiduciary duties through lavish executive compensation and lax governance oversight.
One prominent claim, filed by a Detroit pension fund, challenges massive stock awards granted to board members, alleging the payouts harmed the company. The litigation also overlaps with issues stemming from Musk’s turbulent 2022 Twitter purchase.
McCormick’s history with Musk made her a lightning rod. In 2022, she presided over the fast-tracked lawsuit that ultimately forced Musk to complete the Twitter deal after he tried to back out.
Then in 2024, she struck down his record $56 billion Tesla compensation package, ruling the approval process was flawed and overly CEO-friendly. The Delaware Supreme Court later reinstated the pay on technical grounds, but the ruling fueled Musk’s long-standing criticism of the state’s judiciary.
Musk has repeatedly urged companies to reincorporate elsewhere, arguing Delaware courts have grown hostile to visionary leaders. Monday’s recusal hands him a symbolic victory and underscores how personal social-media activity can collide with judicial impartiality standards.
Delaware law requires judges to step aside if there’s even a “reasonable basis” to question their neutrality.
Court watchers say the episode highlights growing tensions in corporate America’s legal epicenter. While McCormick maintained her impartiality, the appearance of bias proved too costly to ignore. The cases will proceed without her, but the broader debate over Delaware’s dominance in business litigation is far from over.
Elon Musk
Elon Musk has generous TSA offer denied by the White House: here’s why
Musk stepped in on March 21 via a post on X, writing: “I would like to offer to pay the salaries of TSA personnel during this funding impasse that is negatively affecting the lives of so many Americans at airports throughout the country.”
Tesla and SpaceX CEO Elon Musk made a generous offer to pay the salaries of Transportation Security Administration (TSA) employees last week, but the offer was denied by the White House.
In a striking display of private-sector initiative clashing with federal bureaucracy, the White House has turned down an offer from Elon Musk to personally cover the salaries of TSA officers amid an ongoing partial government shutdown. The rejection, reported last Wednesday by multiple outlets, highlights the legal and political hurdles facing unconventional solutions to Washington’s funding gridlock.
The impasse began weeks ago when Congress failed to pass funding for the Department of Homeland Security (DHS), leaving TSA employees, essential workers who screen millions of travelers daily, without paychecks while still required to report for duty.
Frustrated travelers have endured record-long security lines at major airports, with reports of chaos and delays rippling across the country.
Musk stepped in on March 21 via a post on X, writing: “I would like to offer to pay the salaries of TSA personnel during this funding impasse that is negatively affecting the lives of so many Americans at airports throughout the country.”
I would like to offer to pay the salaries of TSA personnel during this funding impasse that is negatively affecting the lives of so many Americans at airports throughout the country
— Elon Musk (@elonmusk) March 21, 2026
But it was not for no reason.
White House spokesperson Abigail Jackson responded on behalf of the Trump administration, expressing appreciation for Musk’s gesture.
However, the legal obstacles, which would be insurmountable, would inhibit Musk from doing so. Jackson said:
“We greatly appreciate Elon’s generous offer. This would pose great legal challenges due to his involvement with federal government contracts.”
Musk’s companies hold significant federal contracts, including NASA launches through SpaceX and potential Defense Department work, raising concerns about conflicts of interest, ethics rules, and anti-bribery statutes that prohibit private payments to government employees. Administration officials also indicated they expect the shutdown to end soon, making external funding unnecessary.
The episode underscores deeper tensions in Washington. Musk, who has advised on government efficiency efforts and maintains a close relationship with President Trump, has frequently criticized wasteful spending and bureaucratic delays.
His offer came as airport security lines ballooned, drawing public frustration toward both parties. TSA officers, many of whom rely on paychecks to cover mortgages and family expenses, have continued working without compensation, a situation that has drawn bipartisan concern but little immediate resolution.
Critics of the rejection argue it prioritizes red tape over practical relief for frontline workers and travelers. Supporters of the White House position counter that allowing private funding sets a dangerous precedent and could undermine congressional authority over the budget.
The White House eventually came to terms with the TSA on Friday and started paying them once again, and lines at airports instantly shrank. The Department of Homeland Security (DHS) said that TSA staf would begin receiving paychecks “as early as” today.
Elon Musk
Tesla FSD mocks BMW human driver: Saves pedestrian from near miss
Tesla FSD anticipated a BMW driver’s lane drift before the human behind the wheel could react.
A video posted to r/TeslaFSD this week put a sharp spotlight on Tesla’s Full Self-Driving (FSD) software being able to react to pedestrian intent than an actual human driver behind the wheel. In the Reddit clip, a BMW driver can be seen rolling through a neighborhood street completely unaware of a pedestrian stepping in to cross. At the same time, a Tesla driving on FSD had already begun slowing down before the pedestrian even began their attempt to cross the street The BMW kept moving, prompting the pedestrian to hop back, while the Tesla came to a stop and provide right-of-way for the human to safely cross.
That gap between what the BMW driver saw and what FSD had already processed is the story. Tesla FSD wasn’t reacting to a person in the street, rather it was reading the signals that a person was about to enter it based on the pedestrian’s movement, trajectory, and their trajectory to telegraph intent.
Tesla’s FSD is now built on an end-to-end neural network trained on billions of real-world miles, learning to interpret subtle human behavioral cues the same way an experienced human driver does instinctively. The difference is consistency. A human driver distracted for two seconds misses what FSD does not.
Tesla sues California DMV over Autopilot and FSD advertising ruling
Reddit commenters in the thread were blunt about the BMW driver’s failure, with several pointing out that the pedestrian was visible well before the crossing. One response put it plainly that the car on FSD saw the situation developing before the human in the other car had registered there was a situation at all.
Tesla has published data showing FSD (Supervised) is 54% safer than a human driver, accumulated across billions of miles driven on the system. Elon Musk has said FSD v14 will outperform human drivers by a factor of two to three, and that v15 has “a shot” at a 10x improvement. Pedestrian safety is where the stakes are highest, and where intent prediction closes the gap fastest. At 30 mph, a car covers roughly 44 feet per second. An extra second of awareness from reading a person’s body language rather than waiting for them to step out is often the difference between a near miss and a fatality.
Video and community discussion: r/TeslaFSD on Reddit
FSD saves man from becoming a pancake. BMW driver nearly flattens him.
by
u/Qwertygolol in
TeslaFSD