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
Elon Musk
Tesla Semi’s official battery capacity leaked by California regulators
A California regulatory filing just confirmed the exact battery size inside each Tesla Semi variant.
A regulatory filing published by the California Air Resources Board in April 2026 has put official numbers on what Tesla Semi owners and fleet buyers have long wanted confirmed: the exact battery capacities of both the Long Range and Standard Range Semi truck variants. CARB is California’s independent air quality regulator, and it certifies zero-emission powertrains before they can be sold or operated in the state. When a manufacturer submits a vehicle for certification, the resulting executive order becomes a public document, making it one of the most reliable sources for confirmed production specs on any EV.
The document lists two certified powertrain configurations. The Long Range Semi carries a usable battery capacity of 822 kWh, while the Standard Range version comes in at 548 kWh. Both use lithium-ion NCMA chemistry and share the same peak and steady-state motor output ratings of 800 kW and 525 kW respectively. Cross-referencing Tesla’s published efficiency figure of approximately 1.7 kWh per mile under full load, the 822 kWh pack supports roughly 480 miles of real-world range, which aligns closely with Tesla’s advertised 500-mile figure for the Long Range trim. The 548 kWh Standard Range pack works out to approximately 320 miles, again consistent with Tesla’s stated 325-mile target.
Here is a direct comparison of the two versions based on the CARB filing and published specs:
| Tesla Semi Spec | Long Range | Standard Range |
| Battery Capacity | 822 kWh | 548 kWh |
| Battery Chemistry | NCMA Li-Ion | NCMA Li-Ion |
| Peak Motor Power | 800 kW | 525 kW |
| Estimated Range | ~500 miles | ~325 miles |
| Efficiency | ~1.7 kWh/mile | ~1.7 kWh/mile |
| Est. Price | ~$290,000 | ~$260,000 |
| GVW Rating | 82,000 lbs | 82,000 lbs |
The timing of this certification is not incidental. On April 29, 2026, Semi Programme Director Dan Priestley confirmed on X that high-volume production is now ramping at Tesla’s dedicated 1.7-million-square-foot facility in Sparks, Nevada. A key advantage of the Nevada location is vertical integration: the 4680 battery cells powering the Semi are manufactured in the same complex, eliminating the supply chain bottleneck that had delayed the program for years.
Tesla’s long-term goal is to reach a production capacity of 50,000 trucks annually at the Nevada factory, which would represent roughly 20 percent of the entire North American Class 8 market. With CARB certification now in hand and the production line running, the regulatory and manufacturing groundwork for that target is in place.
Tesla became the first company to pass the United States government’s new Advanced Driver Assistance Systems (ADAS) testing with the Model Y, completing each of the new tests with a passing performance.
In a landmark announcement on May 7, the National Highway Traffic Safety Administration (NHTSA) declared the 2026 Tesla Model Y the first vehicle to pass its newly ADAS benchmark under the New Car Assessment Program (NCAP).
Model Y vehicles manufactured on or after November 12, 2025, met rigorous pass/fail criteria for four newly added tests—pedestrian automatic emergency braking, lane keeping assistance, blind spot warning, and blind spot intervention—while also satisfying the program’s original four ADAS requirements: forward collision warning, crash imminent braking, dynamic brake support, and lane departure warning.
The NHTSA has just officially announced that the 2026 @Tesla Model Y is the first vehicle model to pass the agency’s new advanced driver assistance system tests.
2026 Tesla Model Y vehicles, manufactured on or after Nov. 12, 2025, successfully met the new criteria for four… pic.twitter.com/as8x1OsSL5
— Sawyer Merritt (@SawyerMerritt) May 7, 2026
NHTSA administration Jonathan Morrison hailed the achievement as a milestone:
“Today’s announcement marks a significant step forward in our efforts to provide consumers with the most comprehensive safety ratings ever. By successfully passing these new tests, the 2026 Tesla Model Y demonstrates the lifesaving potential of driver assistance technologies and sets a high bar for the industry. We hope to see many more manufacturers develop vehicles that can meet these requirements.”
The updates to NCAP, finalized in late 2024 and effective for 2026 models, reflect growing recognition that ADAS features are no longer optional luxuries but essential tools for preventing crashes.
Pedestrian automatic emergency braking, for instance, targets one of the fastest-rising causes of roadway fatalities, while blind spot intervention and lane keeping assistance address common sources of side-swipes and run-off-road incidents. By incorporating objective, performance-based evaluations rather than mere presence of the technology, NHTSA aims to give buyers clearer data on real-world effectiveness.
This milestone arrives at a pivotal moment when vehicle autonomy is transitioning from science fiction to everyday reality.
Tesla’s Full Self-Driving (FSD) software and the impending rollout of robotaxis underscore a broader industry shift toward higher levels of automation. Yet regulators and consumers remain cautious: safety data must keep pace with technological ambition.
The Model Y’s perfect score on these ADAS benchmarks validates that current driver-assist systems—when engineered rigorously—can dramatically reduce human error, which still accounts for the vast majority of crashes.
For Tesla, the result reinforces its long-standing claim of building the safest vehicles on the road. More importantly, it signals to the entire auto sector that meeting elevated federal standards is achievable and expected.
As autonomy edges closer to Level 3 and beyond, where drivers may disengage more fully, such independent verification becomes critical. It builds public trust, informs purchasing decisions, and accelerates the development of systems that could one day eliminate tens of thousands of annual traffic deaths.
In an era when software-defined vehicles promise transformative mobility, the 2026 Model Y’s NHTSA triumph is more than a manufacturer accolade—it is a regulatory green light that autonomy’s future must be built on proven, testable safety foundations. The bar has been raised. The industry, and the roads we share, will be safer for it.
Tesla is going to fix the nearly 219,000 vehicles that it recalled due to an issue with the rearview camera with a simple software update, giving owners no need to travel to a service center to resolve the problem.
Tesla is formally recalling 218,868 U.S. vehicles after regulators discovered a software glitch that can delay the rearview camera image by up to 11 seconds when drivers shift into reverse.
The affected models include certain 2024-2025 Model 3 and Model Y, as well as 2023-2025 Model S and Model X vehicles running software version 2026.8.6 and equipped with Hardware 3 computers. The National Highway Traffic Safety Administration (NHTSA) determined the lag violates Federal Motor Vehicle Safety Standard 111 on rear visibility and could increase crash risk.
Yet this is no ordinary recall. Owners do not need to schedule a service-center visit, hand over keys, or wait for parts.
Tesla fans call for recall terminology update, but the NHTSA isn’t convinced it’s needed
Tesla identified the issue on April 10, halted further deployment of the faulty firmware the same day, and began pushing a corrective over-the-air (OTA) software update on April 11.
By the time the NHTSA posted the recall notice on May 6, more than 99.92 percent of the affected fleet had already received the fix. Tesla reports no crashes, injuries, or fatalities linked to the glitch.
The episode underscores a deeper problem with regulatory language. For decades, “recall” meant hauling a vehicle to a dealership for hardware repairs or replacements. That definition no longer fits software-defined cars. When a fix arrives wirelessly in minutes — identical to an iPhone update — the term evokes unnecessary alarm and misleads the public about the actual risk and remedy.
Elon Musk has repeatedly called for exactly this change. After earlier NHTSA actions, he stated plainly: “The terminology is outdated & inaccurate. This is a tiny over-the-air software update.” On another occasion, he added that labeling OTA fixes as recalls is “anachronistic and just flat wrong.”
The terminology is outdated & inaccurate. This is a tiny over-the-air software update. To the best of our knowledge, there have been no injuries.
— Elon Musk (@elonmusk) September 22, 2022
Musk’s point is simple: regulators must evolve their vocabulary to match the technology. Traditional recalls involve physical intervention and downtime; OTA updates do not. Retaining the old label distorts consumer perception, inflates perceived defect rates, and slows the industry’s shift to faster, safer software iteration.
Tesla’s rapid, remote remedy demonstrates the safety advantage of over-the-air capability. Problems that once required weeks of dealer appointments are now resolved in hours, often before most owners notice. As more automakers adopt software-first designs, the entire regulatory framework needs to catch up.
Updating “recall” terminology would align language with reality, reduce public confusion, and recognize that modern vehicles are no longer static hardware — they are continuously improving computers on wheels.
For the 219,000 Tesla owners involved, the process is already complete. The camera works, the car is safe, and no one left their driveway. That is the new standard — and the vocabulary should reflect it.
Tesla Semi’s official battery capacity leaked by California regulators
Tesla crushes NHTSA’s brand-new ADAS safety tests – first vehicle to ever pass
