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.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
