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 revealed a major new Cybercab detail in a guide it released for First Responders, showing new territory in its beliefs and intentions for the ride-hailing-focused vehicle that entered production in April.
The First Responders Guide is released to give fire departments, paramedics, and other emergency personnel the proper guidance on what to do in the event of an accident, entrapment, or other situation that would require immediate attention.
On one of the pages of the First Responders Guide, Tesla revealed a stark detail about the Cybercab, which could help personnel enter the vehicle more easily in case of an emergency.
Tesla Cybercab has one important piece that AI4 cars might need for FSD
It shows Tesla has no intention of releasing any Cybercab units that were initially proposed for ride-hailing services for the general public with any manual controls, meaning a steering wheel or pedals:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or acceleration and brake pedals.”
New official Cybercab documentation from Tesla:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or… https://t.co/P6ut1mZyzr pic.twitter.com/yq6skl9s2J
— Sawyer Merritt (@SawyerMerritt) June 27, 2026
This is a major development for those who continue to believe Tesla planned to release the Cybercab with any sort of manual controls so that passengers could take over if needed. However, when Tesla started manufacturing production versions of the Cybercab in Giga Texas earlier this year, they were spotted without a steering wheel or pedals.
It essentially confirms the company has no intentions of bringing manual controls to the car’s production versions. Some have argued that the likelihood of Tesla having something
There still are some Cybercab units out there with a steering wheel and pedals, and as Tesla said, these cars are engineering or test vehicles, which have Safety Monitors on board to help the car out of a precarious situation or emergency.
Tesla released the Full Self-Driving v14 ‘Lite’ suite to owners of Hardware 3 or AI3 vehicles today, adding several new features to the vehicles that were once believed to be capable of unsupervised self-driving.
Now, Tesla has released this modified suite to older Tesla vehicles, adding plenty of new features and capabilities.
Here are the full release notes for the suite:
- Distilled the intelligence from HW4 V14 into HW3. This allows HW3 to directly learn how to handle scenarios using HW4 V14 as a guide. This process unlocks the improvements that have been made to HW4 including Reinforcement Learning (RL) and offline models for HW3.
- Improved both proactive and reactive responsiveness across a wide variety of categories including navigation handling, merges and forks, pedestrian interactions, traffic lights, and vehicle cut-in scenarios.
- Improved general comfort in nominal scenarios through fewer false slowdowns, smoother steering and more consistent lane centering.
- Introduced parking, unparking, and reversing capabilities.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, or at the Curbside.
- Speed Profiles are now available at all times, to further customize driving style preference.
These improvements, according to Tesla’s Head of AI, Ashok Elluswamy, help distill the driving behavior from AI4’s v14 series into both the camera and compute configurations of AI3.
Tesla Full Self-Driving v14 ‘Lite’ for older cars finally gets released
He added:
“It includes destination options and speed profiles on city roads, but more importantly significantly improved safety. We hope you’ll enjoy it, once the build ships wide.”
FSD v14 Lite is now rolling out to AI3 early-access customers. Based on the feedback, will rollout to more customers over the next few weeks.
This build distills the driving behavior from AI4’s v14 series into both the camera and compute config of AI3. It includes destination…
— Ashok Elluswamy (@aelluswamy) June 29, 2026
Tesla will continue to roll out the v14 Lite suite more widely in the coming weeks, the company said.
Tesla has finally released its Full Self-Driving v14 ‘Lite’ suite for older cars that equip the Hardware 3 or AI 3 chip, which have not been able to handle the newest versions of the company’s driver assistance software.
Tesla officially started releasing the v14 Lite suite to owners in the Early Access Program last night. The company’s Head of AI, Ashok Elluswamy, said that the rollout will continue over the next few weeks. The build distills the driving behavior from AI4’s v14 series into both the camera and compute configurations of an AI3 car.
🚨 Tesla is releasing v14 Lite for AI3 owners who are in early-access
This will give AI3 cars the ability to experience new FSD features like parking preferences. https://t.co/pp6Q5FOKoz pic.twitter.com/tqexMB8SVy
— TESLARATI (@Teslarati) June 29, 2026
It also includes a variety of new features that were available to AI4 cars running v14, including:
- Start Self-Driving from Park
- Arrival and Parking Options
- Speed Profiles
The release is highly anticipated because those owners with AI3 vehicles were early adopters into the FSD platform and were promised that their cars would be capable of achieving Full Self-Driving.
However, Tesla CEO Elon Musk admitted during the company’s recent Q1 Earnings Call that these vehicles would not be capable of achieving unsupervised Full Self-Driving, which is what Tesla had originally said.
Owners were not pleased with this answer, or the idea that their commitment to buying the suite outright for thousands of dollars would not yield the ability to drive without operating the car. Tesla gave some solutions for this, including a discount on a new car, or an upgrade to an AI4 or AI5 self-driving computer and new, upgraded cameras.
Tesla owners do not seem pleased with these options, as they require giving the company more money.
Nevertheless, it is important to note that Tesla came through for owners here by releasing v14 Lite before the end of Q2, something it had promised owners during the previous Earnings Call. Tesla has had trouble keeping up with timelines, but this is a big achievement for the team.
Tesla reveals huge Cybercab detail in new guide for First Responders
Tesla Full Self-Driving v14 ‘Lite’ Release Notes: new capabilities and features
