News
SpaceX installs Raptor Vacuum engine on first orbital-class Starship
Update: Providing the best views yet of the Raptor Vacuum installation process, SpaceX began installing one of Starship S20’s six engines (one of at least two recently trucked to the launch site) on Monday morning.
It remains to be seen exactly how many engines will be installed on Ship 20 or how many will be ignited during its first static fire test but barring the delivery of more Raptors, signs currently point to an initial test of two engines – one sea-level-optimized Raptor Center (RC) and one Raptor Vacuum with a much larger nozzle. Whenever Ship 20 does fire up those engines, it will be the first static fire of a RVac engine installed on a Starship and the first simultaneous, side-by-side static fire of two different Raptor variants. Since publishing time, SpaceX has cancelled a Tuesday road closure, pushing Starship S20’s first static fire attempt to no earlier than (NET) Wednesday evening.
For the third time in two months, SpaceX has begun installing Raptor engines on its first orbital-class Starship prototype – hopefully for good.
In no uncertain terms, Starship 20’s (S20) path to what could be its last Raptor installations has been about as windy and mysterious as they come. Starship 20 (S20) left the Starbase factory floor for the first time in early August – all six Raptors installed in another program first – for a brief fit check and photo op. After spending about an hour installed on top of Super Heavy Booster 4 (B4), Ship 20 was removed and returned to the build site, where teams removed all six engines and finished wiring and plumbing the vehicle.
Days before the ship’s long-anticipated trip to Starbase’s suborbital launch site for qualification testing, the mount SpaceX prepared for the process quickly had hydraulic rams – used to safely simulate Raptor thrust – were abruptly removed. Starship S20 was then installed on the Pad B mount, where SpaceX proceeded to reinstall six Raptors. Weeks later, after slow heat shield repairs neared completion, SpaceX again removed Ship 20’s Raptors and reinstalled the hydraulic rams it had removed – unused – the month prior. Finally, on September 30th, some seven weeks after the prototype arrived at the suborbital launch site, SpaceX put Starship S20 through its first major test – a lengthy ‘cryoproof’.
Now, ten days after completing a seemingly flawless cryoproof test on its first try, SpaceX has once again trucked multiple Raptors – at least one sea level and one vacuum engine – from the Starbase build site to Starship S20’s suborbital test stand. From the outside looking in, it’s hard not to view the contradictory path S20 took to its first tests – and is still taking to its first static fire(s) – as an unusually visible sign of some kind of internal tug of war or major communication failure between different SpaceX groups or executives.
It’s impossible to determine anything specific beyond the apparent fact that several of the steps taken from Ship 20’s first factory departure to its first cryoproof and static fire tests could have probably been deleted entirely with no harm done and many dozens of hours of work saved. At the end of the day, Starship S20 completed cryoproof testing without issue on the first try and is now seemingly on track to begin its first static fire test campaign later this month.
At the moment, SpaceX has three possible static fire test windows scheduled from 5pm to midnight CDT on Tuesday, Wednesday, and Thursday (Oct 12-14). A similar Monday window was canceled days ago on October 7th, suggesting that more cancellations are probably on the horizon. For now, there’s a chance that Starship S20 – with anywhere from two to all six Raptor engines installed – will fire up for the first time before next weekend. It’s hard to say how exactly SpaceX will proceed. It’s not inconceivable that SpaceX will install all six engines and gradually ramp up to a full six-engine static fire over several tests.

Given that SpaceX has already static fired three Raptor Center (RC) engines on multiple Starship and Super Heavy prototypes, odds are good that Starship S20’s test campaign will be similar – beginning with a three-Raptor static fire, in other words. SpaceX could then add one, two, or all three Raptor Vacuum engines into the fray for one or more additional tests with 4-6 engines total. It’s also possible that suborbital launch mount and pad limitations will prevent more than three engines from firing at once, in which case SpaceX would presumably perform two separate tests of Ship 20’s Raptor Center and Raptor Vacuum engines.
Given that two Raptor variants have never been static fired simultaneously on the same vehicle, it’s hard to imagine that SpaceX won’t also want to perform one or several combined static fires with Raptor Vacuum and Raptor Center engines on Ship 20.
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.
News
Tesla crushes NHTSA’s brand-new ADAS safety tests – first vehicle to ever pass
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.
News
Tesla to fix 219k vehicles in recall with simple software update
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.