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.
A Texas man has been arrested and charged with manslaughter after his Tesla crashed into a home last month, striking a woman inside and killing her. The driver, Michael Butler, claimed the vehicle was in self-driving mode, but information from Tesla shows that Butler overrode the system.
Butler was arrested on Wednesday and booked at the Harris County, Texas, jail. He remained in custody through Thursday and Friday; he did not enter a plea, and his next court hearing is scheduled for Monday.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
There are a handful of new clues in the case that could clear Tesla of any wrongdoing, especially as the woman who was killed’s family, the Avilas, filed a wrongful death lawsuit against Tesla and Butler, seeking at least $1 million in damages.
Charging documents from the Harris County prosecutor now show that Butler, who was working DoorDash the evening of the accident, had been using Full Self-Driving mode without incident through the duration of multiple deliveries that evening.
In the moments leading up to the crash, while in FSD and approaching a left turn, Butler pressed the accelerator pedal, overriding FSD’s speed control, and continued to push it until it reached 100 percent. This caused rapid acceleration; the brake pedal was never pressed, and there is no data to show that Butler aimed to turn away from the curb or house.
The charging documents state:
“I noted that the brake pedal was never pressed in the final minute before the crash. I also did not see any data to indicate that the driver attempted to turn away from the curb that he eventually struck. Further, I observed that no mechanical error was detected or recorded by the vehicle before BUTLER and the Tesla struck the curb.”
Additionally, a forensic analysis of Butler’s phone showed that he searched Google around the time of the crash with queries questioning why FSD was “too timid,” “not aggressive enough,” and even searched, “FSD is not aggressive enough for city driving.”
The documents outlined this:
“Investigator Veal also informed me that he had received BUTLER’s cell phone from Deputy Amad and that HDAO digital forensics team had completed a data extraction and download of the phone. Multiple Google searches related to Tesla had been made from BUTLER’s phone in the months leading up the crash. I noted multiple searches in May of 2026 indicating an apparent frustration with Tesla’s FSD mode, including the following searches: “Tesla fsd not aggressive enough 2026 model,” “Tesla fsd not [sic) aggressive enough 2026,” “FSD is not aggressive enough for city driving,” and “tesla fsd too timid.”‘
Tesla had claimed just after the crash that its internal data showed Butler had overridden the system’s speed control and pressed the accelerator completely, causing the vehicle to travel at an excessive rate of speed. Eventually, the car slammed into Avila’s house, killing her.
Butler has now been formally charged with Manslaughter, a felony.
Tesla shocked with its quarterly delivery report yesterday by reporting it delivered 480,126 vehicles in the second quarter of 2026, a 25 percent year-over-year jump that crushed Wall Street estimates of roughly 400,000–408,000 units. Production reached 451,758, with Model 3 and Model Y accounting for the vast majority.
The result ended two years of annual delivery declines and drew down inventory, signaling demand that outpaced earlier production.
Tesla bears had long warned that the expiration of the U.S. federal EV tax credit would hammer demand. Without the $7,500 incentive, they argued, American buyers would balk at higher effective prices, leading to a sharp slowdown.
Will Tesla thrive without the EV tax credit? Five reasons why they might
That narrative has not played out as predicted. While U.S. EV sales faced broader headwinds, Tesla’s global numbers held firm, underscoring the company’s ability to offset domestic pressure through other levers.
There are several plausible factors that explain Tesla’s strength during this quarter. Let’s take a look at them:
Rising Gas Prices
Rising gas prices provided a powerful tailwind, especially in the U.S.
Geopolitical tensions tied to the Iran conflict pushed fuel costs higher earlier in the year, amplifying the lifetime savings of electric vehicles. Even as oil prices later moderated, the psychological and financial impact lingered, encouraging fleet operators and private buyers to accelerate EV purchases. European sales rebounded sharply, helping drive the quarter’s outperformance.
Full Self-Driving Adoption
Advances in Full Self-Driving (FSD) supervised software also appear to have boosted appeal. Tesla expanded FSD availability in select European markets and continued refining the system.
No complaints from me because I finally got to enjoy this drive on FSD; I usually like to manually drive down this mountain https://t.co/RBFniRPSR0 pic.twitter.com/XQ5sOpN1Yg
— TESLARATI (@Teslarati) June 26, 2026
For tech-oriented buyers, the promise of future autonomy and enhanced driver-assistance features adds perceived value beyond the car itself. This differentiation helps Tesla stand out in a crowded market where competitors focus primarily on hardware and basic range.
Pricing Strategy, Affordable Configurations
Tesla’s offerings and its pricing strategy during Q2 further stimulated demand. Tesla introduced lower-cost versions of the Model 3 and Model Y, widening accessibility without sacrificing core margins.
These moves countered affordability concerns and attracted buyers who had been waiting on the sidelines. Combined with attractive financing and leasing options, the pricing strategy converted interest into actual orders more effectively than many analysts expected.
Broad European Recovery
Supported by government incentives, corporate fleet electrification, and easing political headwinds around CEO Elon Musk, Tesla was supplied additional momentum through stronger registration numbers throughout Europe.
Strong exports from the Shanghai Gigafactory and a production ramp at Giga Berlin ensured supply met this resurgent demand. Corporate buyers, in particular, accelerated transitions to EVs to meet sustainability targets, providing a steady volume base.
These elements created a virtuous cycle that delivered the strong deliveries report. While bears correctly flagged the loss of the U.S. tax credit as a risk, Tesla’s diversified playbook demonstrated that it could remain resilient against those headwinds. The Q2 beat suggests the company remains adept at navigating shifting market conditions, even as competition intensifies.
A Tesla Semi was involved in a fatal collision on U.S. Highway 50 in Dayton, Nevada, on Sunday, June 28, 2026, marking the first known fatal crash involving the electric Class 8 truck. The incident occurred around 7:20 a.m. at the intersection with Traditions Parkway, approximately 40 miles east of Reno and close to Tesla’s Gigafactory Nevada.
According to the Lyon County Sheriff’s Office and the Nevada State Police Highway Patrol, a semi-truck struck two passenger vehicles stopped at a traffic signal. The truck hit the vehicles from behind. Two people were pronounced dead at the scene, and a third person suffered life-threatening injuries and was flown to a hospital, Forbes reported.
Preliminary statements gathered at the scene by the Lyon County Sheriff’s Office suggested the truck driver may have fallen asleep at the wheel. However, the Nevada Highway Patrol, which is leading the investigation, stated that the official cause has not yet been determined.
Additional information is expected to be released early the following week. The truck was seized for evidence as part of the ongoing probe.
Responders at the scene included deputies from the Lyon County Sheriff’s Office, personnel from the Nevada Highway Patrol, Central Lyon County Fire Department, and the Nevada Department of Transportation. The crash led to the temporary closure of U.S. 50 in both directions.
The Tesla Semi is Tesla’s battery-electric heavy-duty truck, produced at the nearby Gigafactory in Nevada. Authorities initially described the vehicle as a semi-truck; its make was subsequently confirmed through reporting and scene identification; an interesting bit of information here, as the Semi is not yet available publicly and many do not know that Tesla builds electric trucks.
The investigation remains active, with no further official details on contributing factors or vehicle systems released as of early July 2026.
This incident highlights ongoing scrutiny of commercial vehicle safety on Nevada highways, particularly involving fatigue. Law enforcement continues to gather evidence and witness statements.
Texas man charged in fatal Tesla crash where he blamed Autopilot
Tesla’s strong Q2 deliveries: Four key drivers behind the surprise
