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 FSD (Supervised) fleet passes 8.4 billion cumulative miles
Tesla’s Full Self-Driving (Supervised) system has now surpassed 8.4 billion cumulative miles.
The figure appears on Tesla’s official safety page, which tracks performance data for FSD (Supervised) and other safety technologies.
Tesla has long emphasized that large-scale real-world data is central to improving its neural network-based approach to autonomy. Each mile driven with FSD (Supervised) engaged contributes additional edge cases and scenario training for the system.
The milestone also brings Tesla closer to a benchmark previously outlined by CEO Elon Musk. Musk has stated that roughly 10 billion miles of training data may be needed to achieve safe unsupervised self-driving at scale, citing the “long tail” of rare but complex driving situations that must be learned through experience.
The growth curve of FSD Supervised’s cumulative miles over the past five years has been notable.
As noted in data shared by Tesla watcher Sawyer Merritt, annual FSD (Supervised) miles have increased from roughly 6 million in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and 4.25 billion in 2025. In just the first 50 days of 2026, Tesla owners logged another 1 billion miles.
At the current pace, the fleet is trending towards hitting about 10 billion FSD Supervised miles this year. The increase has been driven by Tesla’s growing vehicle fleet, periodic free trials, and expanding Robotaxi operations, among others.
With the fleet now past 8.4 billion cumulative miles, Tesla’s supervised system is approaching that threshold, even as regulatory approval for fully unsupervised deployment remains subject to further validation and oversight.
Tesla’s Full Self-Driving (Supervised) system has now surpassed 8.4 billion cumulative miles.
The figure appears on Tesla’s official safety page, which tracks performance data for FSD (Supervised) and other safety technologies.
Tesla has long emphasized that large-scale real-world data is central to improving its neural network-based approach to autonomy. Each mile driven with FSD (Supervised) engaged contributes additional edge cases and scenario training for the system.
The milestone also brings Tesla closer to a benchmark previously outlined by CEO Elon Musk. Musk has stated that roughly 10 billion miles of training data may be needed to achieve safe unsupervised self-driving at scale, citing the “long tail” of rare but complex driving situations that must be learned through experience.
The growth curve of FSD Supervised’s cumulative miles over the past five years has been notable.
As noted in data shared by Tesla watcher Sawyer Merritt, annual FSD (Supervised) miles have increased from roughly 6 million in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and 4.25 billion in 2025. In just the first 50 days of 2026, Tesla owners logged another 1 billion miles.
At the current pace, the fleet is trending towards hitting about 10 billion FSD Supervised miles this year. The increase has been driven by Tesla’s growing vehicle fleet, periodic free trials, and expanding Robotaxi operations, among others.
With the fleet now past 8.4 billion cumulative miles, Tesla’s supervised system is approaching that threshold, even as regulatory approval for fully unsupervised deployment remains subject to further validation and oversight.
Elon Musk
Elon Musk fires back after Wikipedia co-founder claims neutrality and dubs Grokipedia “ridiculous”
Musk’s response to Wales’ comments, which were posted on social media platform X, was short and direct: “Famous last words.”
Elon Musk fired back at Wikipedia co-founder Jimmy Wales after the longtime online encyclopedia leader dismissed xAI’s new AI-powered alternative, Grokipedia, as a “ridiculous” idea that is bound to fail.
Musk’s response to Wales’ comments, which were posted on social media platform X, was short and direct: “Famous last words.”
Wales made the comments while answering questions about Wikipedia’s neutrality. According to Wales, Wikipedia prides itself on neutrality.
“One of our core values at Wikipedia is neutrality. A neutral point of view is non-negotiable. It’s in the community, unquestioned… The idea that we’ve become somehow ‘Wokepidea’ is just not true,” Wales said.
When asked about potential competition from Grokipedia, Wales downplayed the situation. “There is no competition. I don’t know if anyone uses Grokipedia. I think it is a ridiculous idea that will never work,” Wales wrote.
After Grokipedia went live, Larry Sanger, also a co-founder of Wikipedia, wrote on X that his initial impression of the AI-powered Wikipedia alternative was “very OK.”
“My initial impression, looking at my own article and poking around here and there, is that Grokipedia is very OK. The jury’s still out as to whether it’s actually better than Wikipedia. But at this point I would have to say ‘maybe!’” Sanger stated.
Musk responded to Sanger’s assessment by saying it was “accurate.” In a separate post, he added that even in its V0.1 form, Grokipedia was already better than Wikipedia.
During a past appearance on the Tucker Carlson Show, Sanger argued that Wikipedia has drifted from its original vision, citing concerns about how its “Reliable sources/Perennial sources” framework categorizes publications by perceived credibility. As per Sanger, Wikipedia’s “Reliable sources/Perennial sources” list leans heavily left, with conservative publications getting effectively blacklisted in favor of their more liberal counterparts.
As of writing, Grokipedia has reportedly surpassed 80% of English Wikipedia’s article count.
News
Tesla Sweden appeals after grid company refuses to restore existing Supercharger due to union strike
The charging site was previously functioning before it was temporarily disconnected in April last year for electrical safety reasons.
Tesla Sweden is seeking regulatory intervention after a Swedish power grid company refused to reconnect an already operational Supercharger station in Åre due to ongoing union sympathy actions.
The charging site was previously functioning before it was temporarily disconnected in April last year for electrical safety reasons. A temporary construction power cabinet supplying the station had fallen over, described by Tesla as occurring “under unclear circumstances.” The power was then cut at the request of Tesla’s installation contractor to allow safe repair work.
While the safety issue was resolved, the station has not been brought back online. Stefan Sedin, CEO of Jämtkraft elnät, told Dagens Arbete (DA) that power will not be restored to the existing Supercharger station as long as the electric vehicle maker’s union issues are ongoing.
“One of our installers noticed that the construction power had been backed up and was on the ground. We asked Tesla to fix the system, and their installation company in turn asked us to cut the power so that they could do the work safely.
“When everything was restored, the question arose: ‘Wait a minute, can we reconnect the station to the electricity grid? Or what does the notice actually say?’ We consulted with our employer organization, who were clear that as long as sympathy measures are in place, we cannot reconnect this facility,” Sedin said.
The union’s sympathy actions, which began in March 2024, apply to work involving “planning, preparation, new connections, grid expansion, service, maintenance and repairs” of Tesla’s charging infrastructure in Sweden.
Tesla Sweden has argued that reconnecting an existing facility is not equivalent to establishing a new grid connection. In a filing to the Swedish Energy Market Inspectorate, the company stated that reconnecting the installation “is therefore not covered by the sympathy measures and cannot therefore constitute a reason for not reconnecting the facility to the electricity grid.”
Sedin, for his part, noted that Tesla’s issue with the Supercharger is quite unique. And while Jämtkraft elnät itself has no issue with Tesla, its actions are based on the unions’ sympathy measures against the electric vehicle maker.
“This is absolutely the first time that I have been involved in matters relating to union conflicts or sympathy measures. That is why we have relied entirely on the assessment of our employer organization. This is not something that we have made any decisions about ourselves at all.
“It is not that Jämtkraft elnät has a conflict with Tesla, but our actions are based on these sympathy measures. Should it turn out that we have made an incorrect assessment, we will correct ourselves. It is no more difficult than that for us,” the executive said.
Tesla FSD (Supervised) fleet passes 8.4 billion cumulative miles
Elon Musk fires back after Wikipedia co-founder claims neutrality and dubs Grokipedia “ridiculous”
