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.
Investor's Corner
Elon Musk drops a Thanksgiving hint about Starship’s biggest test yet
Elon Musk says Starship Flight 15 will try to catch the ship itself, a first.
Elon Musk says SpaceX’s next Starship flight will try something nobody has done before, by catching the ship itself. Speaking to roughly 2,000 people at the X Takeover event at Giga Texas on Saturday, Musk said Flight 15 is about four to six weeks away and “probably launches a little bit before Thanksgiving, is my guess.”
That is a slip from earlier reporting, which had pointed to a launch as early as October 19. Musk explained why the date keeps moving. “We’re making a bunch of improvements to the rocket between every flight,” he said, adding that there are often hundreds, sometimes thousands, of small changes. This time the list is short, “but some of them take a fair bit of work and we’ve got to go inside the tank to make some of these changes.”
“We’re going to try to catch the ship, which is a super big deal,” Musk said. “If we do so, that’ll be the first time that there’s been full recovery of an orbital class rocket.” SpaceX has already caught the Super Heavy booster with the tower’s mechanical arms, and has talked about catching the ship since late 2025, but the upper stage has never been caught.
Musk also laid out what comes after. “The next big milestone would be to refly both the booster and the ship,” he said, describing a Flight 16 where “all parts of an orbital rocket are reflown.”
The reason SpaceX wants this comes down to cost and cadence. Every Starship ship so far has ended its flight in the ocean, and SpaceX expects most of those water landings to end in fireballs. A ship that returns to Starbase intact can be inspected and flown again. SpaceX’s IPO filing, says Starship V3 is designed to deliver 100 metric tons to orbit in a fully reusable configuration, that SpaceX aims to cut the cost to reach orbit by 99% or more versus the historical average, and that tower catches should allow “multiple launches per day.”
The payoff goes beyond cheaper launches. The next generation Starlink V3 satellites are too large for Falcon 9 and can only fly on Starship, which can carry up to 60 per flight. Flight 14 on September 28 deployed the first 26 of them after Starship reached orbit despite an early engine shutdown, as Teslarati reported. Musk blamed engine computer software, and said the heat shield “was extremely robust,” which he claimed in August had solved Starship’s biggest challenge.
NASA’s Moon plans depend on the same capability. NASA’s inspector general has described a lander mission that needs a propellant depot in low Earth orbit and more than 10 tanker flights, with SpaceX targeting one tanker launch every six days. That schedule only works if ships and boosters come back fast and fly again. Also, ship to ship propellant transfer has not been attempted yet.
One interesting hurdle yet to be explored is bringing the ship back to the launch site, with reentry over land, which will undoubtedly come with a lot of aviation safety reviews.
Lifestyle
Tesla’s mirrorless Cybercab will give riders a visibility upgrade
Tesla engineer confirms Cybercab update letting riders pull up rear and repeater cameras on demand.
Tesla is working on a Cybercab update that would let passengers pull up the vehicle’s rear and side cameras on demand, and the request came straight from a rider.
The exchange played out on X late Friday. Cybercab rider Dan Burkland shared photos of the two-seater’s cabin screen after an evening ride, praised the UI team’s work, and left one request: let riders open the rear and repeater cameras whenever they want, “especially for peace of mind.” Tesla UI software engineer Evan (@CarCoder) answered with two words: “In development.”
The Tesla UI team absolutely crushed it with the infotainment software. Nicely done @CarCoder!
One feature request: Allow folks to pull up the rear & repeater cameras on demand. This would be great especially for peace of mind. https://t.co/mNAOSLx6pE
— Dan Burkland (@DBurkland) October 10, 2026
The idea fits a pattern Teslarati has tracked since public rides began. Days after paid Cybercab service opened in Austin, Tesla sent riders a survey that asked them to rate the touchscreen, the app and the cabin, and to pick the features they wanted most. We reported on that survey in September, and a camera view is the kind of small software change Tesla can push quickly if riders keep asking.
It also speaks to something unique about the vehicle. With no steering wheel, no pedals and no driver, passengers have no mirror to check and no way to see behind them. The hardware is clearly built for camera awareness, from the repeater cameras to the rear camera. Letting a passenger look through those same cameras would give a nervous first time rider a way to confirm what is around the car.
The timing matters because the fleet is growing fast. Tesla’s Robotaxi account said on Saturday that more than 300 Cybercabs are now serving Austin, an eightfold increase in 30 days, and Tesla AI chief Ashok Elluswamy named Dallas as the next city. More cars and more cities mean more people riding in a driverless vehicle for the first time, which is exactly when small trust features carry weight.
For now, the feature is confirmed only as in development. If Tesla follows its usual pattern with Cybercab software, riders could see it appear in a point release without any announcement, and Teslarati will watch for it.
News
Tesla’s Cybercab fleet jumped 8x in a month, with Dallas up next
Tesla confirms its first official Cybercab fleet number as Austin scales fast and Dallas looms.
Tesla says more than 300 Cybercabs are now serving Austin, the first time the company has put an official number on its active Cybercab fleet. The figure came from the Robotaxi account on X on Saturday, which wrote that one month after launch the service had “scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days.”
Ashok Elluswamy, Tesla’s head of AI software, quoted the post with a line that carried the bigger news. “Two years since the 10/10 Cybercab WeRobot event, the cabs are everywhere in Austin now. Dallas soon,” he wrote. It is the first time Tesla has named the next city for public Cybercab rides.
One month after launch, we’ve scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days https://t.co/EagJy2JAsm
— Robotaxi (@robotaxi) October 10, 2026
Tesla opened Cybercab rides to the public in Austin on September 4, as Teslarati reported, a day after an invite only launch event. The ramp since then has been steep. Our September 28 report had the fleet at well over 100 units after availability jumped from 58 to 125 in a single week. On Thursday, Tesla added 150 Cybercabs to the Texas automated vehicle registry, lifting its registered count to 319 from 169. The first seven appeared on the registry on August 31.
RobotaxiTracker, a community site that counts vehicles from sightings and state records, listed 275 vehicles in unsupervised service in Austin on Saturday, 105 of them Cybercabs, which is well below Tesla’s figure. Tracker counts can lag official numbers, though Sawyer Merritt noted that Cybercab wait times in Austin stayed short on Saturday evening even with more than 2,000 fans in town for X Takeover.
Regulators are watching the rollout. NHTSA opened an audit query into Tesla’s certification that the Cybercab meets federal safety standards, and sworn answers are due October 30. Tesla reports third quarter earnings on October 21, which gives the company a natural venue to define its fleet numbers and put a date on Dallas.