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 Model Y and Model 3 named safest vehicles tested by ANCAP in 2025
According to ANCAP in a press release, the Tesla Model Y achieved the highest overall weighted score of any vehicle assessed in 2025.
The Tesla Model Y recorded the highest overall safety score of any vehicle tested by ANCAP in 2025. The Tesla Model 3 also delivered strong results, reinforcing the automaker’s safety leadership in Australia and New Zealand.
According to ANCAP in a press release, the Tesla Model Y achieved the highest overall weighted score of any vehicle assessed in 2025. ANCAP’s 2025 tests evaluated vehicles across four key pillars: Adult Occupant Protection, Child Occupant Protection, Vulnerable Road User Protection, and Safety Assist technologies.
The Model Y posted consistently strong results in all four categories, distinguishing itself through a system-based safety approach that combines structural crash protection with advanced driver-assistance features such as autonomous emergency braking, lane support, and driver monitoring.
This marked the second time the Model Y has topped ANCAP’s annual safety rankings. The Model Y’s previous version was also ANCAP’s top performer in 2022.
The Tesla Model 3 also delivered a strong performance in ANCAP’s 2025 tests, contributing to Tesla’s broader safety presence across segments. Similar to the Model Y, the Model 3 also earned impressive scores across the ANCAP’s four pillars. This made the vehicle the top performer in the Medium Car category.
ANCAP Chief Executive Officer Carla Hoorweg stated that the results highlight a growing industry shift toward integrated safety design, with improvements in technologies such as autonomous emergency braking and lane support translating into meaningful real-world protection.
“ANCAP’s testing continues to reinforce a clear message: the safest vehicles are those designed with safety as a system, not a checklist. The top performers this year delivered consistent results across physical crash protection, crash avoidance and vulnerable road user safety, rather than relying on strength in a single area.
“We are also seeing increasing alignment between ANCAP’s test requirements and the safety technologies that genuinely matter on Australian and New Zealand roads. Improvements in autonomous emergency braking, lane support, and driver monitoring systems are translating into more robust protection,” Hoorweg said.
News
Tesla Sweden uses Megapack battery to bypass unions’ Supercharger blockade
Just before Christmas, Tesla went live with a new charging station in Arlandastad, outside Stockholm, by powering it with a Tesla Megapack battery.
Tesla Sweden has successfully launched a new Supercharger station despite an ongoing blockade by Swedish unions, using on-site Megapack batteries instead of traditional grid connections. The workaround has allowed the Supercharger to operate without direct access to Sweden’s electricity network, which has been effectively frozen by labor action.
Tesla has experienced notable challenges connecting its new charging stations to Sweden’s power grid due to industrial action led by Seko, a major Swedish trade union, which has blocked all new electrical connections for new Superchargers. On paper, this made the opening of new Supercharger sites almost impossible.
Despite the blockade, Tesla has continued to bring stations online. In Malmö and Södertälje, new Supercharger locations opened after grid operators E.ON and Telge Nät activated the sites. The operators later stated that the connections had been made in error.
More recently, however, Tesla adopted a different strategy altogether. Just before Christmas, Tesla went live with a new charging station in Arlandastad, outside Stockholm, by powering it with a Tesla Megapack battery, as noted in a Dagens Arbete (DA) report.
Because the Supercharger station does not rely on a permanent grid connection, Tesla was able to bypass the blocked application process, as noted by Swedish car journalist and YouTuber Peter Esse. He noted that the Arlandastad Supercharger is likely dependent on nearby companies to recharge the batteries, likely through private arrangements.
Eight new charging stalls have been launched in the Arlandastad site so far, which is a fraction of the originally planned 40 chargers for the location. Still, the fact that Tesla Sweden was able to work around the unions’ efforts once more is impressive, especially since Superchargers are used even by non-Tesla EVs.
Esse noted that Tesla’s Megapack workaround is not as easily replicated in other locations. Arlandastad is unique because neighboring operators already have access to grid power, making it possible for Tesla to source electricity indirectly. Still, Esse noted that the unions’ blockades have not affected sales as much.
“Many want Tesla to lose sales due to the union blockades. But you have to remember that sales are falling from 2024, when Tesla sold a record number of cars in Sweden. That year, the unions also had blockades against Tesla. So for Tesla as a charging operator, it is devastating. But for Tesla as a car company, it does not matter in terms of sales volumes. People charge their cars where there is an opportunity, usually at home,” Esse noted.
Elon Musk
Elon Musk’s X goes down as users report major outage Friday morning
Error messages and stalled loading screens quickly spread across the service, while outage trackers recorded a sharp spike in user reports.
Elon Musk’s X experienced an outage Friday morning, leaving large numbers of users unable to access the social media platform.
Error messages and stalled loading screens quickly spread across the service, while outage trackers recorded a sharp spike in user reports.
Downdetector reports
Users attempting to open X were met with messages such as “Something went wrong. Try reloading,” often followed by an endless spinning icon that prevented access, according to a report from Variety. Downdetector data showed that reports of problems surged rapidly throughout the morning.
As of 10:52 a.m. ET, more than 100,000 users had reported issues with X. The data indicated that 56% of complaints were tied to the mobile app, while 33% were related to the website and roughly 10% cited server connection problems. The disruption appeared to begin around 10:10 a.m. ET, briefly eased around 10:35 a.m., and then returned minutes later.
Previous disruptions
Friday’s outage was not an isolated incident. X has experienced multiple high-profile service interruptions over the past two years. In November, tens of thousands of users reported widespread errors, including “Internal server error / Error code 500” messages. Cloudflare-related error messages were also reported.
In March 2025, the platform endured several brief outages spanning roughly 45 minutes, with more than 21,000 reports in the U.S. and 10,800 in the U.K., according to Downdetector. Earlier disruptions included an outage in August 2024 and impairments to key platform features in July 2023.
Tesla Model Y and Model 3 named safest vehicles tested by ANCAP in 2025
Tesla Sweden uses Megapack battery to bypass unions’ Supercharger blockade
