News
SpaceX Starship prototype ignites six engines, starts major brush fire
SpaceX has successfully ignited all six engines on its latest Starship prototype, taking a significant step towards ensuring that the upper stage will be ready for the rocket’s first orbital launch attempt.
Unfortunately, the same successful static fire of a Starship upper stage – potentially producing almost twice as much thrust as the booster of SpaceX’s Falcon 9 rocket – scattered superheated debris hundreds of meters away, igniting a major brush fire. It’s not the first major fire caused by Starship activities in South Texas, and it likely won’t be the last.
Starship S24 completed its first successful static fire on August 9th, igniting two Raptor engines. Several unsuccessful attempts to test more engines followed throughout the rest of the month, and SpaceX ultimately decided to replace one of Starship S24’s three Raptor Vacuum engines in early September before trying again. After workers installed the new engine and buttoned up Ship 24, the stars eventually aligned on September 8th.
Kicking off the test, SpaceX pumped several hundred tons of liquid oxygen (LOx) and a much smaller quantity of liquid methane (LCH4) fuel into Ship 24 in about 90 minutes, producing a crisp layer of frost wherever the cryogenic liquids touched the skin of the rocket’s uninsulated steel tanks. No frost formed on Starship’s upper methane tank, implying that SpaceX only loaded methane fuel into internal ‘header’ tanks meant to store propellant for landings. The hundreds of tons of liquid oxygen, then, were likely meant as ballast, reducing the maximum stress Starship could exert on the test stand holding it to the ground.
That potential stress is substantial. Outfitted with upgraded Raptor 2 engines, Starship S24 could have produced up to 1380 tons (~3M lbf) thrust when it ignited all six for the first time at 4:30 pm CDT. On top of smashing the record for most thrust produced during a Starbase rocket test, Ship 24’s engines burned for almost 8 seconds, making it one of the longest static fires ever performed on a Starship test stand.
Several brush fires were visible almost immediately after clouds of dust and steam cleared. More likely than not, the combination of the extreme force, heat, and burn duration likely obliterated the almost entirely unprotected concrete surface below Ship 24. Despite continuous evidence that all Starship static fire operations would be easier and safer with the systems, SpaceX still refuses to install serious water deluge or flame deflector systems at Starbase’s test stands and launch pads.
Instead, under its steel Starship test stands, SpaceX relies on a single middling deluge spray nozzle and high-temperature concrete (likely martyte) that probably wouldn’t pass muster for a rocket ten times less powerful than Starship. In multiple instances, Starships have shattered that feeble martyte layer, creating high-velocity ceramic shards that damage their undersides or Raptor engines, requiring repairs and creating risky situations. With essentially no attempt at all to tame the high-speed several-thousand-degree Raptor exhaust, static fire tests at Starbase thus almost always start small grass fires and cause minor damage, but those fires rarely spread.
Ship 24’s first six-engine test was not so lucky, although the Starship made it through seemingly unscathed. Most likely, eight long seconds of blast-furnace conditions melted the top layer of surrounding concrete and shot a hailstorm of tiny superheated globules in almost every direction. Indeed, in almost every direction there was something readily able to burn, a fire started. In several locations to the south and west, brush caught fire and began to burn unusually aggressively, quickly growing into walls of flames that sped across the terrain. To the east, debris even made it into a SpaceX dumpster, the contents of which easily caught fire and burned for hours.
Eventually, around 9pm CDT, firefighters were able to approach the safed launch pad and rocket, but the main fire had already spread south, out of reach. Instead, they started controlled burns near SpaceX’s roadblock, hoping to clear brush and prevent the fire (however unlikely) from proceeding towards SpaceX’s Starbase factory and Boca Chica Village homes and residents.
The nature of the estuary-like terrain and wetlands means that it’s very easy to stop fires at choke points, so the fire likely never posed any real threat to Boca Chica residents, SpaceX employees, or onlookers. It was also unlikely to damage SpaceX’s launch facilities or return to damage Starship S24 from the start, as both of are surrounded by a combination of concrete aprons, empty dirt fields, and a highway.
Still, the “brush” burned by the fire is a protected habitat located in a State Park and Wildlife Refuge. While fire is a natural and often necessary element of many habitats, including some of those in Boca Chica, this is the second major brush fire caused by Starship testing since 2019, which may be less than desirable. At a minimum, fighting fires around Starbase generally requires firefighters to walk or even drive on protected wetlands and salt flats, the impact of which could ultimately be as bad for wildlife and habitats as the fire itself.
SpaceX’s Federal Aviation Administration (FAA) Programmatic Environmental Assessment (PEA), which fully greenlit the company’s existing Starbase Texas facilities and launch plans earlier this year, only discusses fire [PDF] a handful of times. Repairing and preventing future damage to wetlands, however, comes up dozens of times and is the subject of numerous conditions SpaceX must meet before the FAA will grant Starship an orbital launch license.
Ultimately, given that the FAA approved that PEA in full awareness of a 2019 brush fire caused by Starhopper (an early Starship prototype) that may have been as bad or worse than 2022’s, there’s a chance that it will play a small role in the ongoing launch licensing process, but the odds of it being a showstopper are close to zero. Still, it would likely benefit SpaceX at least as much as the surrounding Boca Chica wilderness if it can implement changes that prevent major brush fires from becoming a regular ‘accidental’ occurrence.
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
