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
SpaceX maintains unbelievable Starship target despite Booster 18 incident
It appears that it will take more than an anomaly to stop SpaceX’s march towards Starship V3’s refinement.
SpaceX recently shared an incredibly ambitious and bold update about Starship V3’s 12th test flight.
Despite the anomaly that damaged Booster 18, SpaceX maintained that it was still following its plans for the upgraded spacecraft and booster for the coming months. Needless to say, it appears that it will take more than an anomaly to stop SpaceX’s march towards Starship V3’s refinement.
Starship V3 is still on a rapid development path
SpaceX’s update was posted through the private space company’s official account on social media platform X. As per the company, “the Starbase team plans to have the next Super Heavy booster stacked in December, which puts it on pace with the test schedule planned for the first Starship V3 vehicle and associated ground systems.”
SpaceX then announced that Starship V3’s maiden flight is still expected to happen early next year. “Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X.
Elon Musk mentioned a similar timeline on X earlier this year. In the lead up to Starshp Flight 11, which proved flawless, Musk stated that “Starship V3 is a massive upgrade from the current V2 and should be through production and testing by end of year, with heavy flight activity next year.” Musk has also mentioned that Starship V3 should be good enough to use for initial Mars missions.
Booster 18 failure not slowing Starship V3’s schedule
SpaceX’s bold update came after Booster 18 experienced a major anomaly during gas system pressure testing at SpaceX’s Massey facility in Starbase, Texas. SpaceX confirmed in a post on X that no propellant was loaded, no engines were installed, and personnel were positioned at a safe distance when the booster’s lower section crumpled, resulting in no injuries.
Still, livestream footage showed significant damage around the liquid oxygen tank area of Booster 18, leading observers to speculate that the booster was a total loss. Booster 18 was among the earliest vehicles in the Starship V3 series, making the failure notable. Despite the setback, Starship V3’s development plans appear unchanged, with SpaceX pushing ahead of its Q1 2026 test flight target.
News
Tesla Sweden faces fresh union blockade at key Gothenburg paint shop
Allround Lack works with painting and damage repair of passenger cars, including Teslas.
Tesla’s ongoing labor conflict in Sweden escalated again as the trade union IF Metall issued a new blockade halting all Tesla paintwork at Allround Lack in Gothenburg.
Allround Lack works with painting and damage repair of passenger cars, including Teslas. It currently employs about 20 employees.
Yet another blockade against Tesla Sweden
IF Metall’s latest notice ordered a full work stoppage for all Tesla-related activity at Allround Lack. With the blockade in place, paint jobs on Tesla-owned vehicles, factory-warranty repairs, and transport-damage fixes, will be effectively frozen, as noted in a report from Dagens Arbete. While Allround Lack is a small paint shop, its work with Tesla means that the blockade would add challenges to the company’s operations in Sweden, at least to some degree.
Paint shop blockades have been a recurring tool in the longstanding conflict. The first appeared in late 2023, when repair shops were barred from servicing Tesla vehicles. Days later, the Painters’ Union implemented a nationwide halt on Tesla paint work across more than 100 shops. Since then, a steady stream of workshops has been pulled into the conflict.
Earlier blockades faced backlash from consumers
The sweeping effects of the early blockades drew criticism from industry groups and consumers. Employers and industry organization Transportföretagen stated that the strikes harmed numerous workshops across Sweden, with about 10 of its members losing about 50% of their revenue.
Private owners also expressed their objections. Tibor Blomhäll, chairman of Tesla Club Sweden, told DA in a previous statement that the blockades from IF Metall gave the impression that the union was specifically attacking consumers. “If I get parking damage to my car, I pay for the paint myself. The company Tesla is not involved in that deal at all. So many people felt singled out, almost stigmatized. What have I done as a private individual to get a union against me?” Blomhäll stated.
In response to these complaints, IF Metall introduced exemptions, allowing severely damaged vehicles to be repaired. The union later reopened access for private owners at workshops with collective agreements. The blockades at the workshops were also reformulated to only apply to work that is “ordered by Tesla on Tesla’s own cars, as well as work covered by factory warranties and transport damage on Tesla cars.”
News
Tesla breaks Norway’s all-time annual sales record with one month to spare
With November alone delivering 4,260 new registrations, Tesla has cemented its most dominant year ever in one of Europe’s most mature EV markets.
Tesla shattered Norway’s decade-old annual sales record this month, overtaking Volkswagen’s long-standing milestone with over one month still left in the year. Backed by surging demand ahead of Norway’s upcoming VAT changes, Tesla has already registered 26,666 vehicles year-to-date, surpassing Volkswagen’s 2016 record of 26,572 units.
With November alone delivering 4,260 new registrations month-to-date, Tesla has cemented its most dominant year ever in one of Europe’s most mature EV markets.
Model Y drives historic surge in Norway
Tesla’s impressive momentum has been led overwhelmingly by the Model Y, which accounted for 21,517 of Norway’s registrations this year, as noted in a CarUp report, citing data from Elbil Statistik. The Model 3 followed with 5,087 units, while the Model S and Model X contributed 30 and 19 vehicles, respectively. Even the parallel-imported Cybertruck made the charts with 13 registrations.
Demand intensified sharply through autumn as Norwegian buyers rushed to secure deliveries before the country’s VAT changes take effect in January. The new regulation is expected to add roughly NOK 50,000 to the price of a Model Y, prompting a wave of early purchases that helped lift Tesla beyond the previous all-time record well before year-end.
With December still ahead, Tesla is positioned to extend its historic lead further. Needless to say, it appears that Norway will prove to be one of Tesla’s strongest markets in Europe.
FSD could be a notable demand driver in 2026
What’s especially interesting about Tesla’s feat in Norway is that the company’s biggest selling point today, Full Self-Driving (Supervised), is not yet available there. Tesla, however, recently noted in a post on X that the Dutch regulator RDW has reportedly committed to issuing a Netherlands national approval for FSD (Supervised) in February 2026.
The RDW posted a response to Tesla’s post, clarifying the February 2026 target but stating that FSD’s approval is not assured yet. “The RDW has drawn up a schedule with Tesla in which Tesla is expected to be able to demonstrate that FSD Supervised meets the requirements in February 2026. RDW and Tesla know what efforts need to be made to make a decision on this in February. Whether the schedule will be met remains to be seen in the coming period,” the RDW wrote in a post on its official wesbite.
If FSD (Supervised) does get approved next year, Tesla’s vehicles could gain a notable advantage over competitors, as they would be the only vehicles on the market capable of driving themselves on both inner-city streets and highways with practically no driver input.
SpaceX maintains unbelievable Starship target despite Booster 18 incident
Tesla Sweden faces fresh union blockade at key Gothenburg paint shop
