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 owners surpass 8 billion miles driven on FSD Supervised
Tesla shared the milestone as adoption of the system accelerates across several markets.
Tesla owners have now driven more than 8 billion miles using Full Self-Driving Supervised, as per a new update from the electric vehicle maker’s official X account.
Tesla shared the milestone as adoption of the system accelerates across several markets.
“Tesla owners have now driven >8 billion miles on FSD Supervised,” the company wrote in its post on X. Tesla also included a graphic showing FSD Supervised’s miles driven before a collision, which far exceeds that of the United States average.
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.
Tesla also recently updated the safety data for FSD Supervised on its website, covering North America across all road types over the latest 12-month period.
As per Tesla’s figures, vehicles operating with FSD Supervised engaged recorded one major collision every 5,300,676 miles. In comparison, Teslas driven manually with Active Safety systems recorded one major collision every 2,175,763 miles, while Teslas driven manually without Active Safety recorded one major collision every 855,132 miles. The U.S. average during the same period was one major collision every 660,164 miles.
During the measured period, Tesla reported 830 total major collisions with FSD (Supervised) engaged, compared to 16,131 collisions for Teslas driven manually with Active Safety and 250 collisions for Teslas driven manually without Active Safety. Total miles logged exceeded 4.39 billion miles for FSD (Supervised) during the same timeframe.
Elon Musk
The Boring Company’s Music City Loop gains unanimous approval
After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project.
The Metro Nashville Airport Authority (MNAA) has approved a 40-year agreement with Elon Musk’s The Boring Company to build the Music City Loop, a tunnel system linking Nashville International Airport to downtown.
After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project. Under the terms, The Boring Company will pay the airport authority an annual $300,000 licensing fee for the use of roughly 933,000 square feet of airport property, with a 3% annual increase.
Over 40 years, that totals to approximately $34 million, with two optional five-year extensions that could extend the term to 50 years, as per a report from The Tennesean.
The Boring Company celebrated the Music City Loop’s approval in a post on its official X account. “The Metropolitan Nashville Airport Authority has unanimously (7-0) approved a Music City Loop connection/station. Thanks so much to @Fly_Nashville for the great partnership,” the tunneling startup wrote in its post.
Once operational, the Music City Loop is expected to generate a $5 fee per airport pickup and drop-off, similar to rideshare charges. Airport officials estimate more than $300 million in operational revenue over the agreement’s duration, though this projection is deemed conservative.
“This is a significant benefit to the airport authority because we’re receiving a new way for our passengers to arrive downtown at zero capital investment from us. We don’t have to fund the operations and maintenance of that. TBC, The Boring Co., will do that for us,” MNAA President and CEO Doug Kreulen said.
The project has drawn both backing and criticism. Business leaders cited economic benefits and improved mobility between downtown and the airport. “Hospitality isn’t just an amenity. It’s an economic engine,” Strategic Hospitality’s Max Goldberg said.
Opponents, including state lawmakers, raised questions about environmental impacts, worker safety, and long-term risks. Sen. Heidi Campbell said, “Safety depends on rules applied evenly without exception… You’re not just evaluating a tunnel. You’re evaluating a risk, structural risk, legal risk, reputational risk and financial risk.”
Elon Musk
Tesla announces crazy new Full Self-Driving milestone
The number of miles traveled has contextual significance for two reasons: one being the milestone itself, and another being Tesla’s continuing progress toward 10 billion miles of training data to achieve what CEO Elon Musk says will be the threshold needed to achieve unsupervised self-driving.
Tesla has announced a crazy new Full Self-Driving milestone, as it has officially confirmed drivers have surpassed over 8 billion miles traveled using the Full Self-Driving (Supervised) suite for semi-autonomous travel.
The FSD (Supervised) suite is one of the most robust on the market, and is among the safest from a data perspective available to the public.
On Wednesday, Tesla confirmed in a post on X that it has officially surpassed the 8 billion-mile mark, just a few months after reaching 7 billion cumulative miles, which was announced on December 27, 2025.
Tesla owners have now driven >8 billion miles on FSD Supervisedhttps://t.co/0d66ihRQTa pic.twitter.com/TXz9DqOQ8q
— Tesla (@Tesla) February 18, 2026
The number of miles traveled has contextual significance for two reasons: one being the milestone itself, and another being Tesla’s continuing progress toward 10 billion miles of training data to achieve what CEO Elon Musk says will be the threshold needed to achieve unsupervised self-driving.
The milestone itself is significant, especially considering Tesla has continued to gain valuable data from every mile traveled. However, the pace at which it is gathering these miles is getting faster.
Secondly, in January, Musk said the company would need “roughly 10 billion miles of training data” to achieve safe and unsupervised self-driving. “Reality has a super long tail of complexity,” Musk said.
Training data primarily means the fleet’s accumulated real-world miles that Tesla uses to train and improve its end-to-end AI models. This data captures the “long tail” — extremely rare, complex, or unpredictable situations that simulations alone cannot fully replicate at scale.
This is not the same as the total miles driven on Full Self-Driving, which is the 8 billion miles milestone that is being celebrated here.
The FSD-supervised miles contribute heavily to the training data, but the 10 billion figure is an estimate of the cumulative real-world exposure needed overall to push the system to human-level reliability.