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.

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.

Advertisement
-
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.

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

Tesla teases “Halloween Mode” update with Optimus rising from a graveyard

Tesla’s Halloween teaser hides a covered vehicle and an Optimus hand rising from the ground.

Published

on

By

Tesla has started teasing a Halloween software update for its vehicles, with  a short clip on X that reads, “Halloween is coming.” The clip opens on a glowing pumpkin before pulling back to the car’s center touchscreen, where the usual parked visualization has been replaced by a graveyard scene, and the vehicle draped with a white sheet so it reads as a cartoon ghost.

The second detail is a robotic hand clawing its way out of the dirt like a zombie, which looks to be the hand of Tesla’s latest Optimus V3 humanoid robot. While Tesla still has not formally shown Optimus Gen 3 walking around in service, renders pulled from Tesla’s Android app last month gave the clearest look yet, including far more refined hands that Tesla has said carry 22 degrees of freedom. The hand has been the hardest part of the program. Musk has called it the majority of the robot’s engineering difficulty, and Tesla’s patents describe a design driven by tendons with the actuators moved into the forearm.

Tesla Optimus V3 hand and arm details revealed in new patents

Optimus also has a Halloween track record. Last October the robot handed out candy in Times Square, and a costumed “zombie” Optimus shuffled around the Tesla Diner in Los Angeles on Halloween night.

On the software side, Tesla’s 2025 Holiday Update expanded Santa Mode with a Santa sleigh, snowmen, snow effects, and a festive lock chime, so it wouldn’t be too far fetched if we saw something similar but themed for a  Halloween Mode.

Continue Reading

News

Tesla says fixes on Full Self-Driving’s two biggest issues are on the way

Published

on

Tesla Full Self-Driving is set to receive improvements to address its two biggest issues, according to a company engineer.

Director of Engineering at Tesla AI, Phil Duan, revealed in a post on X that improvements to both pothole avoidance and navigation “are coming,’ something we have heard many times in the past. However, there are a few things that seem to hint that things might be different this time around.

Pothole avoidance, navigation, speed control, and left lane camping are some of the most prevalent and frequently mentioned shortcomings of the Full Self-Driving suite. These are a few of the biggest issues that have kept Tesla Full Self-Driving as a Supervised suite, meaning drivers must remain attentive during operation.

Pothole Avoidance

Pothole avoidance was first mentioned as an “Upcoming Improvement” with the Tesla Full Self-Driving v14.3 update back in early April of this year. It was listed alongside “Expand reasoning to all behaviors beyond destination handling.”

Tesla is fixing Full Self-Driving’s pothole problem

It’s been six months since we first saw pothole avoidance explicitly mentioned, and it has not moved beyond that and joined the main release notes yet.

Tesla has not shed any light on why pothole avoidance has been such an issue for it to solve, but it also has issues identifying large bumps much of the time, so its modeling of sudden changes in road conditions is likely pretty weak at this particular point. I’ve had more issues with large bumps than potholes, personally, but both are issues that need to be resolved.

It makes sense that things might be pretty close to being released to the public, as we are going on such an extensive period of time between it being mentioned and it actually being deployed.

Navigation

Navigation is likely the most painful part of using Full Self-Driving, as it routinely takes strange routes, has trouble with local rules (like Except Right Turn Stop Signs in Pennsylvania), and sometimes does not realize that maneuvers it is suggesting are against the law. Turning out of my neighborhood, you cannot turn left, yet my Model Y still suggests it roughly 70 percent of the time when I’m leaving.

However, Tesla might be close to a breakthrough on this. With the Summer Update, Tesla added “Preferred Routes” alongside “Automatic Navigation.”

Preferred Routes prioritized roads that the driver had actually taken before, instead of always defaulting to what the vehicle believes is the most efficient path. This has already solved many of my issues. Formerly, I would turn off the Online Routing setting, and that would eliminate most of my complaints with routing, but then you lose out later on the Live Traffic Visualization.

Tesla’s Navigation has improved tremendously thanks to the Preferred Routes release with the Summer Update, but it still could use some polishing, as it still suggests strange routes from time to time, and it also has a lot of issues getting out of a parking lot. I find that those truly confuse FSD sometimes.

Continue Reading

News

SpaceX’s midnight spy satellite launch quietly set a new record

Falcon Heavy launched its first NRO mission while SpaceX landed four boosters in one day.

Published

on

By

SpaceX's Falcon Heavy lifts off from Launch Complex 39A at NASA's Kennedy Space Center at 11:54 p.m. ET on October 1, 2026, carrying the classified NROL-97 mission for the National Reconnaissance Office. (Credit: SpaceX)
SpaceX's Falcon Heavy lifts off from Launch Complex 39A at NASA's Kennedy Space Center at 11:54 p.m. ET on October 1, 2026, carrying the classified NROL-97 mission for the National Reconnaissance Office. (Credit: SpaceX)

SpaceX closed out one of its busiest days ever with a midnight Falcon Heavy launch from Florida, and the rocket’s two side boosters came home to finish off a landing record the company had never set before.

Falcon Heavy lifted off from Launch Complex 39A at NASA’s Kennedy Space Center at 11:54 p.m. ET Thursday carrying NROL-97, a classified payload for the National Reconnaissance Office. It was the first time the NRO has flown on Falcon Heavy after 22 missions on Falcon 9, and the first NRO mission bought through the National Security Space Launch Phase 3 Lane 2 contract awarded in 2025, according to Spaceflight Now.

Roughly eight minutes after liftoff, side boosters B1104 and B1072 touched down at Landing Zones 1 and 2 at Cape Canaveral Space Force Station, setting off double sonic booms across Brevard County. B1104 was flying for the second time and B1072 for the fourth. Both last flew on August 30 on NASA’s Nancy Grace Roman Space Telescope, making NROL-97 the quickest turnaround between Falcon Heavy missions to date. The brand new center core, B1106, was expended in the Atlantic so the payload could reach its high energy orbit, and SpaceX’s mission page noted the fairing had previously flown on the NROL-95 mission in July.

The two landings capped a record for SpaceX. Earlier Thursday, Falcon 9 booster B1101 returned to Landing Zone 40 after sending the Crew-13 astronauts to the International Space Station, and another Falcon 9 launched the Transporter-18 rideshare with 130 payloads from Vandenberg Space Force Base in California. Spaceflight Now reported it was the first time SpaceX has landed four boosters in a single day, wrapping up the triple header Teslarati previewed on Wednesday.

The mission also brought Landing Zone 1 back for what may be its final landing. SpaceX first landed an orbital class booster there in December 2015, but its lease on the former Launch Complex 13 site ended in 2025 as the company moved Florida landings to new pads at its own launch complexes. With LZ-40 already holding the Crew-13 booster, SpaceX brought LZ-1 back into service for one more night. Launch tracker Next Spaceflight listed NROL-97 as the final expected landing at the site.

NROL-97 adds to a fast growing stack of national security work for SpaceX. The company has flown four Space Force missions from Vandenberg since mid August, several believed to carry Starshield satellites, pushing its Pentagon contract total for 2026 past $8 billion. Elon Musk was also named this week to help lead the Pentagon’s Project Meridian study on the future of warfare.

The Florida doubleheader stood out for another reason. The Space Coast saw only one launch in all of September as SpaceX shifts more of its East Coast infrastructure toward Starship, which reached orbit for the first time on Flight 14 just three days earlier.

Continue Reading