News
SpaceX Starship aborts Raptor engine test, briefly catches fire
Update: On March 15th, SpaceX got within milliseconds of Starship serial number 11’s (SN11) first Raptor engine test but suffered an abort just before full ignition, briefly leaving the rocket on fire.
Around 12:26 pm CDT, after an otherwise nominal static fire flow, Starship SN11 momentarily ignited one or two of its three Raptor engines’ preburners, referring to a central component that burns cryogenic liquid propellant into gas that’s ready for combustion. As with all preburner tests, intentional or otherwise, the end result looked a bit like a weak static fire and produced a small but visible amount of flame and thrust. Unlike intentional preburner tests, the static fire abort seemingly ignited something hidden inside Starship SN11’s and appeared to burn for at least another 30-40 seconds.
Raptor has proven itself to be an extremely durable engine, up to and including surviving visible onboard fires during actual Starship flight tests. Nevertheless, depending on the source of SN11’s post-abort fire and what it may or may not have burned or damaged, it’s no surprise that SpaceX ended testing for the day instead of quickly trying again, which it’s done several times prior. If the fire was largely harmless, SpaceX has already distributed notices suggesting a second attempt could happen as early as 6am to 12pm CDT (UTC-5) on Tuesday, March 16th. If more time is needed, SpaceX has the rest of the week to conduct any necessary repairs or swap out SN11’s Raptor engines.
Public documents show that SpaceX has plans to static fire and launch its latest Starship prototype within a two-day period that could begin later today.
SpaceX shipped Starship SN11 from its Boca Chica, Texas rocket factory to test and launch facilities a mile down the road on March 8th, less than five days after Starship SN10 exploded minutes after touchdown. The very next day, SpaceX completed ambient-temperature proof testing, filling Starship with benign nitrogen gas to check for leaks and verify system health. Two days after that, Starship SN11 appeared to complete a several-hour cryogenic proof test – swapping nitrogen gas for its supercool liquid form – without issue.
Despite the seemingly successful ‘cryo proof,’ something prevented a subsequent static fire test planned on March 12th before any attempt could be made, delaying the next attempt until after the approaching weekend. An agreement between SpaceX, Cameron County, and the state of Texas currently prevents road closures (and thus rocket testing) on weekends falling between Labor Day and Memorial Day, rules meant to preserve some level of public access to Boca Chica Beach.
As a result, unless SpaceX is already ready to launch (it has waivers for three such weekend closures for launch attempts), the company has to wait until Monday even if a minor issue fixable in hours or a day or so scrubs Friday test plans. While inconvenient, it’s worth noting that the existence of that public beach and the strong regulations that protect its public domain is likely one of the only reasons the general public can still get as close as they can to SpaceX’s Boca Chica ‘Starbase’.
For whatever reason, that road closure agreement does still mean that SpaceX will (in theory) be able to test and launch any day of the week from May 31st to September 6th, save for a few holidays, effectively boosting the number of opportunities by 40% for those 14 weeks. Until then, SpaceX is doing everything it can to take full advantage of the five days a week it is allowed to test Starship prototypes. N
Notably, although Starships SN8 and SN9 both hit a few weeks of technical and regulatory snags while preparing for their high-altitude launch attempts, SpaceX has been gradually speeding up that process over time. Starship SN10, the first prototype of its kind to land in one piece, took just 33 days to go from pad arrival to liftoff and spent just 8 days between its first static fire and launch attempts. The same feats took Starship SN8 77 and 50 days, respectively, with SN9 splitting the difference at 43 days from transport to liftoff and 28 days between its first static fire and launch attempts.
Road closure requests, a safety warning for residents, and a Temporary Flight Restriction (TFR) filed with the FAA all suggest that SpaceX’s current plan is to attempt Starship SN11’s first triple-Raptor static fire between 6am and 12pm CDT on Monday, March 15th. If that test goes almost perfectly, SpaceX wants to turn the rocket around for a 10 km (6.2 mi) launch attempt on Tuesday, March 16th – the very next day. Given the past performance of high-altitude Starship prototypes, that target is decidedly ambitious and likely to incur delays, but it still reveals the true scope of SpaceX’s goals even at this early stage of development.
If Starship SN11 does manage to launch within a few days of its first static fire attempt, SpaceX would still crush SN10’s 33-day record by a factor of three. Stay tuned for updates on Monday’s possible Starship static fire and rapid Tuesday turnaround attempt
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
