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.
Tesla rolled out Full Self-Driving (Supervised) v14.3.5 yesterday, and about fifty miles of driving on the new version has given me enough time to highlight what seems to be strong about the release and what is not.
Additionally, Tesla has added a few new features with this specific update, which we’ll highlight as well.
Tesla Full Self-Driving v14.3.5 Performance
The new update is business as usual. Things seem to be running completely normal and necessary, but there are a few things that we’ve seemed to pick up on based on our own experience with v14.3.5, as well as what other users are seeing.
Initially, it seems to be more aware of its surroundings, making moves that are incredibly courteous to other drives and operating just a tad more reserved than what the suite might have done previously.
We had two instances where it showed this, the first being FSD needing to pass a Flagger Force vehicle that was placing down signage for the day. Their work truck was right at the front corner of a right-hand turn; typically where most cars travel when they take that turn.
FSD v14.3.5 recognized this, slowed down, and took the turn wide with no issues:
🚨 Tesla Full Self-Driving v14.3.5 takes a wide turn as flagger crews set up signage for the day https://t.co/3v0PL9qhlI pic.twitter.com/i4CKqxE16c
— TESLARATI (@Teslarati) July 13, 2026
Additionally, v14.3.5 backed up for a semi truck that was making a wide turn onto a road my car was on. This is not new, but it seemed to be backing up for courtesy; it didn’t seem completely necessary, but it might have put some peace of mind in the truck driver’s head:
🚨 Tesla Full Self-Driving v14.3.5 backs up for an oncoming tractor trailer taking a wide turn https://t.co/0WuAqNMpRR pic.twitter.com/s6yZGVm5Te
— TESLARATI (@Teslarati) July 13, 2026
X user Mike P, also a Pennsylvania native like myself, shared three clips of his Tesla running v14.3.5 performing similar maneuvers. He said:
“FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.”
Check it out here:
Rapidfire epic moments on FSD V14.3.5
1) FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.2) Insane speed to vehicle cues. As FSD approaches… pic.twitter.com/bSnySSlFHR
— Mike P (@mikepat711) July 13, 2026
It seems like Speed Profiles are still in need of some tweaking; I am adjusting what Speed Profile I’m in frequently, constantly changing it to get it to travel at the correct speed. This was an issue for me on v14.3.4. It seems like they’re just a little inconsistent.
Terrible Parking
Parking attempts on v14.3.5 were not good. There are quite a few people who have said this:
Yeah it seems like FSD v14.3.5 is having some issues with parking early on https://t.co/Bw5ULfVmDq pic.twitter.com/RHdpjOEpIo
— TESLARATI (@Teslarati) July 13, 2026
David Moss, the Tesla owner who has taken multiple coast-to-coast drives without any interventions, also has had some issues with parking early on with v14.3.5:
Horrible first impression v14.3.5 on my 2025 Tesla Model 3 LR RWD Premium ðŸ˜
3 terrible parking jobs in 23 min including parking on a ramp in a business park & parking perpendicular out in the road on street only parking situation.Wish I had a better drive but I still believe… pic.twitter.com/TtyhRHAFG7
— David Moss (@DavidMoss) July 13, 2026
New Features
Tesla has added the ability to open Camera Preview at any time. Previously, it was only available in Park. Here’s what that feature looks like in action:
🚨 Here’s the new Camera Preview feature on FSD v14.3.5 pic.twitter.com/OodfZgDppy
— TESLARATI (@Teslarati) July 13, 2026
Check back later this week for a longer review of what we’ve noticed on Full Self-Driving v14.3.5.
Lifestyle
Tesla makes the cut on California’s newest EV Rebate program
California just signed a $270 million EV rebate into law and it starts this summer.
California Governor Gavin Newsom signed SB 168 into law on Monday, July 13, 2026, creating a $270 million EV rebate program that delivers money directly at the dealership rather than as a tax credit applied months later. The program, called MyFirstEV, is funded equally by California’s state budget and participating automakers, with each contributing $135.5 million to make the math work.
The timing is directly tied to the loss of federal support when the $7,500 federal EV tax credit ended, removing the most significant consumer incentive that had driven EV adoption in the U.S. California, which accounts for roughly one-third of all EVs sold nationally, moved to fill that gap with a state-level replacement.
The rebate structure is straightforward. First-time EV buyers can receive $3,500 off any new battery-electric vehicle with an MSRP up to $50,000. Used EVs priced at $25,000 or below qualify for a $1,750 rebate. The credit is applied at the point of sale, which removes the friction of the old federal system where buyers had to wait for tax season to see the benefit. The program goes live later this summer, with the California Air Resources Board expected to release full participation details next month.
California hits Tesla Cybercab and Robotaxi driverless cars with new law
For Tesla buyers, the implications are mixed. The Tesla Model 3 RWD at $42,490 and the Model 3 Long Range at $47,490 both fall under the $50,000 cap and would qualify for the full $3,500 rebate for first-time buyers. The Model Y, which starts at $44,990 after Tesla’s recent price adjustment, also qualifies. The Model X, Model S, and Cybertruck all exceed the cap and receive no benefit. As Teslarati has reported, the program also includes a carve-out exempting California-based automakers like Rivian and Lucid from the price cap entirely, a provision that puts Tesla at a disadvantage since it relocated its headquarters to Texas in 2021.
Other qualifying vehicles include the Chevrolet Equinox EV, Ford Mustang Mach-E, Hyundai Ioniq 5, Kia EV6, and Volkswagen ID.4.
The Tesla Semi is entering a new Pilot Program with Paper Transport, LLC (PTI), a Wisconsin-based transportation provider. The company will test the Semi’s Long Range configuration through “dedicated operations within the Chicago market.”
Chicago presents an interesting challenge for the Semi, as it will be a colder-weather climate that will test the Semi’s ability to operate in lower temperatures and in potentially large accumulations of snow. This is something Tesla has been testing with the Semi in Alaska and even in Northern California during the colder months, but Chicago will present a truly tough midwestern winter.
Tesla Semi spotted on journey home after winter performance testing
PTI says it is using the Semi to evaluate its strategy of reducing transportation emissions while maintaining performance, reliability, and cost efficiency. These are major arguments for the Semi being introduced into new fleets.
CEO of PTI Tyler Ellison said:
“PTI has been a leader in sustainable transportation solutions for over 15 years. We take a consultative approach to helping customers identify and implement the right transportation solution for their network. Our partnership with Tesla expands our portfolio alongside renewable natural gas and intermodal, giving customers more ways to reduce Scope 3 emissions without compromising service or economics.”
PTI is far from the first company to adopt the Semi within a fleet, as Tesla entered strategic agreements with PepsiCo. and its subsidiary Frito-Lay for a Pilot Program that extended throughout the California region.
Tesla has let companies like those utilize the Semi to determine whether it would be suitable for their operations. Additionally, Tesla gets valuable information regarding the Semi’s performance, knowing what to improve and what is ideal for companies that will utilize the all-electric truck for regional and nationwide logistics.
PTI plans to utilize the Long Range configuration, which is priced at $290,000 and features a range of approximately 500 miles, a three-motor powertrain, up to 800 kW of drive power, and consumption of just 1.7 kWh per mile.
Tesla Semi pricing revealed after company uncovers trim levels
VP of Maintenance at PTI, Bryan Ellen, added:
“We are excited to partner with Tesla, leveraging their ever-evolving technology. We are bullish in our estimation of the parallels available between our dedicated model and the efficiency of their fully electric Class 8 tractor. We anticipate a growing synergy between our businesses as we work to facilitate this sustainable solution for our customers.”
PTI has logged more than 87 million miles using sources like compressed and renewable gas, but now is looking to take it a step further with fully electric operations.
Tesla Full Self-Driving v14.3.5 Early Impressions: new features and early performance
Tesla makes the cut on California’s newest EV Rebate program
