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
Honda gives up on all-EV future: ‘Not realistic’
Mibe believes the demand for its gas vehicles is certainly strong enough and has changed “beyond expectations.” As many drivers went for EVs a few years back, hybrids are becoming more popular for consumers as they offer the best of both worlds.
Honda has given up on a previous plan to completely changeover to EVs by 2040, a new report states. The company’s CEO, Toshihiro Mibe, said that the idea is “not realistic.”
Mibe believes the demand for its gas vehicles is certainly strong enough and has changed “beyond expectations.” As many drivers went for EVs a few years back, hybrids are becoming more popular for consumers as they offer the best of both worlds.
Mibe said (via Motor1):
“Because of the uncertainty in the business environment and also the customer demand, is changing beyond our expectation and, therefore, we have judged that it’ll be difficult to achieve. That ratio [100-percent electric in 2040] is not realistic as of now. We have withdrawn this target.”
Instead of going all-electric, Honda still wants to oblige by its hopes to be net carbon neutral by 2050. It will do this by focusing on those popular hybrid powertrains, planning to launch 15 of them by March 2030.
Honda will invest 4.4 trillion yen, or almost $28 billion, to build hybrid powertrains built around four and six-cylinder gas engines.
There are so many companies abandoning their all-electric ambitions or even slowing their roll on building them so quickly. Ford, General Motors, Mercedes, and Nissan have all retreated from aggressive EV targets by either cancelling, delaying, or pausing the development of electric models.
Hyundai’s 2030 targets rely on mixed offerings of electric, hybrid & hydrogen vehicles
Early-decade pledges from multiple brands proved overly ambitious as infrastructure lags, battery costs remain high in some markets, and many buyers prefer hybrids for their convenience and range. Toyota has long championed hybrids, while others have quietly extended internal-combustion timelines.
For Honda—historically known for reliable gasoline engines—this shift leverages its core strengths while buying time to refine electric technology. Whether the hybrid-heavy strategy will protect market share in an increasingly competitive landscape remains to be seen, but one thing is clear: the gas engine is far from dead at Honda, unfortunately.
Elon Musk
Delta Airlines rejects Starlink, and the reason will probably shock you
In a pointed exchange on X, Elon Musk defended SpaceX’s uncompromising approach to Starlink’s in-flight internet service, explaining why Delta Air Lines walked away from a deal.
SpaceX frontman Elon Musk explained on Wednesday why commercial airline Delta got cold feet over offering Starlink for stable internet on its flights — and the reason will probably shock you.
In a pointed exchange on X, Elon Musk defended SpaceX’s uncompromising approach to Starlink’s in-flight internet service, explaining why Delta Air Lines walked away from a deal.
Delta rejected Starlink because it insisted on routing all connectivity through its branded “Delta Sync” portal rather than allowing a simple Starlink experience.
Instead, the airline partnered with Amazon’s Project Kuiper—rebranded as Amazon Leo—for high-speed Wi-Fi on up to 500 aircraft, with rollout targeted for 2028. At the time of the announcement, Kuiper had roughly 300 satellites in orbit, while Starlink operated more than 10,400.
The use of the “Delta Sync” portal would not work for SpaceX, as Musk went on to say that:
“SpaceX requires that there be no annoying ‘portal’ to use Starlink. Starlink WiFi must just work effortlessly every time, as though you were at home. Delta wanted to make it painful, difficult and expensive for their customers. Hard to see how that is a winning strategy.”
Musk doubled down in a follow-up post:
“Yes, SpaceX deliberately accepted lower revenue deals with airlines in exchange for making Starlink super easy to use and available to all passengers.”
Not exactly. SpaceX requires that there be no annoying “portal” to use Starlink.
Starlink WiFi must just work effortlessly every time, as though you were at home.
Delta wanted to make it painful, difficult and expensive for their customers. Hard to see how that is a winning…
— Elon Musk (@elonmusk) May 13, 2026
SpaceX has structured its airline agreements to prioritize zero-friction access—no captive portals, no SkyMiles logins, no paywalls or ads blocking basic connectivity.
While this means forgoing higher-margin deals that would let carriers monetize the service more aggressively, it ensures Starlink feels like home broadband at 35,000 feet. Passengers on partner airlines such as United, Qatar Airways, and Air France have already praised the service for enabling seamless video calls, streaming, and work mid-flight without interruptions.
Delta’s choice reflects a different philosophy. By keeping Wi-Fi behind its Delta Sync ecosystem, the airline aims to drive loyalty program engagement and control the digital passenger journey. Yet, critics argue this short-term control comes at the expense of immediate competitiveness.
Airlines already installing Starlink are pulling ahead in customer satisfaction surveys, while Delta passengers face years of reliance on slower, legacy systems until Leo launches.
SpaceX’s decision to trade revenue for simplicity will pay off in the longer term, as Starlink is already positioning itself as the default high-speed option for carriers that value passenger satisfaction over incremental fees.
Musk’s focus on creating not only a great service but also a reasonable user experience highlights SpaceX’s prowess with Starlink as it continues to expand across new partners and regions.
News
Tesla gathers 93,000 FSD miles in a country where FSD isn’t approved – here’s how
Tesla has quietly logged an impressive 93,000 miles (roughly 150,000 km) of autonomous driving at its Giga Berlin factory—using Full Self-Driving (FSD) in a country where the technology remains unavailable to consumers on public roads.
Tesla has gathered 93,000 Full Self-Driving miles in a country where Full Self-Driving is not even approved. Here’s how.
Tesla has quietly logged an impressive 93,000 miles (roughly 150,000 km) of autonomous driving at its Giga Berlin factory—using Full Self-Driving (FSD) in a country where the technology remains unavailable to consumers on public roads.
The milestone, revealed alongside news that Giga Berlin has now built 750,000 Model Y vehicles, highlights how Tesla is putting its AI to work in one of the most controlled environments imaginable: it’s own factory floor.
Every Model Y that rolls off the final assembly line at Giga Berlin doesn’t need a human driver to reach the outbound lot. Instead, the freshly built vehicles engage FSD and navigate themselves across the factory campus.
The Tesla Model Ys rolling off the production line at Giga Berlin have now driven themselves on FSD a combined 93,000 miles from the end of the production line to the outbound lot. https://t.co/6RhL3W4q4p pic.twitter.com/DOKKHUcSSL
— Sawyer Merritt (@SawyerMerritt) May 11, 2026
The route—from the end of the production line through marked internal pathways to the staging area where cars await delivery or export—is entirely on private property. No public roads, no mixed traffic, and no regulatory hurdles for on-road autonomous operation.
It’s a closed-loop system: wide lanes, predictable layouts, minimal pedestrians, and consistent conditions that make it one of the simplest proving grounds for the software.
A short factory tour video shared by Tesla Manufacturing shows General Assembly team member Jan explaining the process. Gesturing beside a glossy black Model Y still wearing its protective wrap, he notes the cumulative distance the fleet has covered autonomously.
Tesla Giga Berlin seems to be using FSD Unsupervised to move Model Y units
The cars handle the short drive flawlessly, freeing up workers who would otherwise spend hours shuttling vehicles manually. For a high-volume plant like Giga Berlin, the time and labor savings add up quickly. Even small gains in cycle time per car can reclaim valuable space in the outbound lot and streamline logistics.
This internal deployment serves multiple purposes. First, it delivers zero-cost validation data. Each factory run exposes FSD to real-world physics—acceleration, steering precision, obstacle avoidance—in a repeatable setting far safer than public testing.
Second, it demonstrates the system’s readiness at scale. If FSD can reliably move thousands of brand-new cars without intervention inside a busy factory, it underscores the robustness of the vision-based, end-to-end neural network Tesla has been refining.
Critics often point to Europe’s cautious regulatory stance on unsupervised autonomy, yet Tesla has turned that limitation into an advantage. While owners in Germany still cannot activate consumer FSD on highways or city streets, the software is already proving its worth behind the factory gates.
The 93,000 miles represent not just internal efficiency gains but a subtle flex: the cars are manufactured ready to navigate autonomously, at least in the bounds of the factory. It’s a big feather in the cap of FSD, even if regulators have yet to green-light broader use.
As Giga Berlin continues ramping output, expect this autonomous logistics loop to grow. What began as a practical workaround for moving finished vehicles has quietly become one of the most compelling real-world showcases of FSD’s potential—right in the heart of regulated Europe. Tesla isn’t waiting for approval to perfect its autonomy; it’s already driving the future, one factory mile at a time.
Honda gives up on all-EV future: ‘Not realistic’
Delta Airlines rejects Starlink, and the reason will probably shock you
