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.
News
Tesla Semi gets new product launch as mass manufacturing hits Plaid Mode
While the 1.2 MW Megacharger handles quick 30-minute en-route boosts, the Basecharger serves as a reliable overnight solution for longer dwell times at warehouses, distribution centers, fleet yards, and even, potentially, homes.
The Tesla Semi is getting a new production launch as mass manufacturing on the all-electric truck is gearing up to hit Plaid Mode.
Tesla has introduced a game-changing addition to its commercial charging lineup with the new 125 kW Basecharger for Semi. Launched this week as part of the new “Semi Charging for Business” program, this compact unit is purpose-built for depot and overnight charging of Tesla Semi trucks.
While the 1.2 MW Megacharger handles quick 30-minute en-route boosts, the Basecharger serves as a reliable overnight solution for longer dwell times at warehouses, distribution centers, fleet yards, and even, potentially, homes.
Our new 125 kW Basecharger is designed for longer dwell times and overnight charging of Semis. It’s the “home charging” for heavy-duty fleets.
It features a fully integrated design that eliminates the need for a separate AC-to-DC cabinet, simplifying installation. The 6 meter… https://t.co/ovy1C4PsRW pic.twitter.com/vBUCNMzs57
— Tesla Charging (@TeslaCharging) May 1, 2026
Delivering up to 60 percent of the Semi’s range in roughly four hours, perfect for overnight top-ups during mandated driver rest periods or while trucks are loaded or unloaded. Its fully integrated design eliminates the need for bulky separate AC-to-DC cabinets.
Tesla engineers tucked one of the power modules from a V4 Supercharger Cabinet directly inside the sleek post, resulting in a compact footprint. It also features a six-meter cable for layout flexibility. This is one thing that must have been learned through the V4 Supercharger rollout.
Installation and operating costs drop dramatically thanks to daisy-chaining. Up to three Basechargers can share a single 125 kVA breaker, slashing electrical infrastructure requirements. The unit outputs 150 amps continuous across an 180–1,000 VDC range, matching the Semi’s high-voltage architecture while supporting the MCS 3.2 standard.
Tesla Semi sends clear message to Diesel rivals with latest move
Priced from $40,000 for a minimum order of two units, the Basecharger is far more affordable than the $188,000 Megacharger setup for two posts. Deliveries begin in early 2027. Buyers also receive Tesla’s full network-level software, remote monitoring, maintenance, and a guaranteed 97 percent or higher uptime—critical for fleet reliability.
This launch arrives as Tesla accelerates high-volume Semi production at its Nevada factory, targeting 50,000 units annually. By pairing affordable depot charging with ultra-fast highway options, Tesla removes one of the biggest obstacles to electrifying Class 8 trucking: infrastructure cost and complexity.
Fleet operators stand to gain lower electricity rates during off-peak hours, dramatically reduced maintenance compared to diesel, and quieter yards at night. The Basecharger isn’t just another charger—it’s the practical bridge that makes large-scale electric semi adoption economically viable.
With the Basecharger handling “home” duties and Megachargers powering the road, Tesla is delivering a complete ecosystem that could finally tip the scales toward zero-emission freight. For trucking companies ready to go electric, the future just got a whole lot more charger-friendly.
News
Tesla revises new Intervention Reporting system with Full Self-Driving
It is the second revision to the program as Tesla is trying to make it easier to decipher driver and owner complaints, but also to make it easier to report issues within the suite for them.
Tesla has revised its new Intervention Reporting system within the Full Self-Driving suite that now categorizes reasons that drivers take over when the semi-autonomous driving functionality is active.
It is the second revision to the program as Tesla is trying to make it easier to decipher driver and owner complaints, but also to make it easier to report issues within the suite for them.
With the initial rollout of Full Self-Driving v14.3.2, Tesla included a new reporting menu that gave four options for an intervention: Preference, Comfort, Critical, and Other. A slightly revised version of Full Self-Driving with the same ID number then came out a few days later, changing the “Other” option to “Navigation” after numerous complaints from owners.
It appears Tesla has listened to those owners once again and has not only made it smaller and more compact, but also easier to report the issues than previously.
The new menu is now embedded within the request for a Voice Memo from Tesla, and does not block the entire screen, as the second rollout of the menu was:
Thank you Tesla! The new intervention screen is much better! @Tesla_AI pic.twitter.com/1lea9G27N1
— Dirty Tesla (@DirtyTesLa) May 1, 2026
There will likely be one additional revision to the Interventions Menu, as we have coined it here at Teslarati.
Unfortunately, at times, there are no reasons for an intervention at all, but the menu does not give an option to simply disregard the reporting and forces the driver to choose one of the options. We, as well as other notable Tesla influencers, indicated that there is not always a reason for an intervention.
For example, I choose to back into my parking spot in my neighborhood at least some of the time for the reason of charging. I usually hit “Preference” for this, but it sends a false positive to Tesla that there was a reason I took over that I was unhappy with.
Tesla begins probing owners on FSD’s navigation errors with small but mighty change
Instead, I’m simply performing a maneuver that is not yet available to us. When Tesla allows drivers to choose the orientation at which their car enters a parking spot, I and many others won’t have to deal with this menu.
Others are still skeptical that it will help resolve any issues whatsoever and prefer to disregard the menu altogether. It does seem as if Tesla will issue another revision in the coming days to allow this to happen.
Lifestyle
California hits Tesla Cybercab and Robotaxi driverless cars with new law
California just gave police power to ticket driverless cars, including Tesla’s Cybercab fleet.
California DMV formally adopted new rules on April 29, 2026 that allow law enforcement to issue “notices of noncompliance”, or in other words ticket autonomous vehicle companies when their cars commit moving violations. The rules take effect July 1, 2026 and officially closes a regulatory gap that previously let driverless cars operate on public roads with nearly no traffic enforcement consequences.
Until now, state traffic laws only applied to human “drivers,” which meant that when no person was behind the wheel, police had no mechanism to issue a ticket. Officers were limited to citing driverless vehicles for parking violations only. A well-known example came in September 2025, when a San Bruno officer watched a Waymo robotaxi execute an illegal U-turn and could do nothing but notify the company.
Under the new framework, when an officer observes a violation, the autonomous vehicle company is effectively treated as the driver. Companies must report each incident to the DMV within 72 hours, or 24 hours if a collision is involved. Repeated violations can result in fleet size restrictions, operational suspensions, or full permit revocation. Local officials also gained new authority to geofence driverless vehicles out of active emergency zones within two minutes and require a live emergency response line answered within 30 seconds.
Tesla Cybercab ramps Robotaxi public street testing as vehicle enters mass production queue
California’s new enforcement rules arrive at a pivotal moment for Tesla. The company is ramping Cybercab production at Giga Texas toward hundreds of units per week, targeting at least 2 million units annually at full capacity, while simultaneously pushing to expand its Robotaxi service to dozens of U.S. cities by end of 2026. Unsupervised FSD for consumer vehicles is currently targeted for Q4 2026, and when it arrives, Tesla’s fleet may not have a human to absorb legal accountability, under the July 1 rules.
Tesla has confirmed plans to expand its Robotaxi service to seven new cities in the first half of 2026, including Dallas, Houston, Phoenix, Miami, Orlando, Tampa, and Las Vegas, with the service already running without safety drivers in Austin. Musk has said he expects robotaxis to cover between a quarter and half of the United States by end of year.
Tesla Semi gets new product launch as mass manufacturing hits Plaid Mode
Tesla revises new Intervention Reporting system with Full Self-Driving
