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.
Tesla has scaled back driver monitoring to be less naggy with the latest version of the Full Self-Driving (Supervised) suite, which is version 14.3.3.
The latest version is already earning praise from owners, who are reporting that the suite is far less invasive when it comes to keeping drivers from taking their eyes off the road. The first to mention it was notable Tesla community member on X known as Zack, or BLKMDL3.
14.3.3 nags less too https://t.co/IuiWzuYO6O
— Elon Musk (@elonmusk) May 18, 2026
Musk confirmed that v14.3.3 was made to nag drivers significantly less, something that Tesla has worked toward in the past and has said with previous versions that it is less likely to push drivers to look ahead, at least after looking away for a few seconds.
This refinement aligns with Tesla’s ongoing push toward unsupervised FSD. The update also brings faster Actual Smart Summon (now up to 8 mph), reliable “Hey Grok” voice commands, richer visualizations, smoother Mad Max acceleration, and an intervention streak counter that rewards consistent use. Reviewers describe the drive as more human-like and confident, with fewer twitches or unnecessary maneuvers.
Musk has repeatedly signaled this direction. In late 2025, he stated that FSD would allow phone use “depending on context of surrounding traffic,” noting safety data would justify relaxing rules so drivers could text in low-risk scenarios like stop-and-go traffic.
We tested this, and even still, the cell phone monitoring really seems to be less active in terms of alerting drivers:
Tesla Full Self-Driving v14.2.1 texting and driving: we tested it
Earlier, ahead of v14, Musk promised the system would “nag the driver much less” once safety metrics improved.
In 2023, he confirmed the steering wheel torque nag would be “gradually reduced, proportionate to improved safety,” shifting reliance to the cabin camera. Subsequent updates like v13.2.9 and v12.4 further loosened monitoring, cracking down on workarounds while easing legitimate distractions.
These steps reflect Tesla’s data-driven approach: FSD’s safety record—reportedly averaging millions of miles per crash—now outpaces human drivers in many scenarios, giving the company confidence to dial back interventions. Reduced nags improve usability and trust, encouraging more drivers to rely on the system rather than disengaging out of frustration.
However, there are certainly still some concerns. In many states, it is illegal to handle a cell phone in any way, requiring the use of hands-free devices. In Pennsylvania, it is illegal to use your cell phone at stop lights, which is definitely a step further than using it while the car is actively in motion.
v14.3.3 represents tangible progress. Making FSD less adversarial and more seamless is definitely a step forward, but drivers need to be aware of the dangers of distracted driving. FSD is extremely capable, but it is in no way fully autonomous, nor does its performance warrant owners to take their attention off the road.
Tesla has officially expanded its Full Self-Driving (FSD) suite in Europe once again, as it will now be offered to customer vehicles in Lithuania, marking a significant milestone as the second European Union country to offer the system.
Tesla confirmed FSD’s rollout in Lithuania this morning:
FSD Supervised now rolling out to Teslas in Lithuania 🇱🇹!
Making European roads safer, one by one pic.twitter.com/Uuj0bNG7pP
— Tesla Europe, Middle East & Africa (@teslaeurope) May 20, 2026
Tesla showed several clips of Full Self-Driving navigation in Lithuania to mark the announcement, while Lithuanian Transport Minister Juras Taminskas highlighted the system’s potential to assist with lane-keeping, speed adjustment, and traffic tasks on longer drives, while emphasizing that drivers must stay alert and ready to intervene.
Just a few weeks ago, Tesla officially entered Europe with Full Self-Driving in the Netherlands. The expansion of FSD on the continent is now officially underway.
Full Self-Driving’s European Journey
Europe has long posed one of the toughest regulatory challenges for Tesla’s autonomy ambitions due to stringent safety standards under the United Nations Economic Commission for Europe (UNECE) framework, particularly UN Regulation 171 for Driver Control Assistance Systems.
The Netherlands’ RDW authority granted the pioneering approval after over 18 months of rigorous testing, including 1.6 million kilometers on European roads and extensive data submissions.
This approval enables mutual recognition across the EU, allowing other member states to adopt it nationally without full re-testing. Lithuania quickly leveraged this mechanism, becoming the second adopter. Tesla positions FSD Supervised as a tool to incrementally improve road safety, with the company claiming it reduces incidents when used properly.
Bottlenecks slowing broader European deployment include fragmented national regulations, varying levels of regulatory skepticism, and requirements for robust driver monitoring. Some EU officials have raised concerns about performance in adverse conditions like icy roads or speeding scenarios, alongside frustrations over Tesla’s public advocacy approach.
Additional hurdles involve data privacy, liability frameworks, and the need for EU-wide harmonization. While countries like Belgium appear to be fast-tracking adoption, larger markets such as Germany, France, and Italy are expected to follow in the coming months, with potential EU-wide progress targeted for later in 2026.
Tesla Full Self-Driving Across the World
As of May, Full Self-Driving (Supervised) is available in approximately ten countries.
In North America, it has been live for years in the United States, Canada, Mexico, and Puerto Rico. Asia-Pacific additions include Australia, New Zealand, and South Korea, while China utilizes what Tesla calls “City Autopilot.” In Europe, the Netherlands and now Lithuania join the list, with more countries mulling the possibility of also approving FSD.
Tesla offers FSD via monthly subscriptions (around €99 in Europe) or one-time purchases (with deadlines approaching in many markets), shifting toward recurring revenue models. Today is the final day Europeans will be able to purchase the suite outright.
This expansion underscores Tesla’s push for global autonomy, starting with supervised and building toward greater capabilities. With Lithuania now online, momentum is building across Europe, though regulatory caution will continue shaping the pace. Owners in approved regions report smoother highway and urban driving, but the system remains Level 2, which requires human oversight.
Elon Musk
Tesla ditches India after years of broken promises
Tesla has ditched its plans to build a factory in India after years of failed negotiations.
Tesla’s long-running effort to establish a manufacturing presence in India is officially over. India’s Minister of Heavy Industries H.D. Kumaraswamy confirmed on May 19, 2026 that Tesla has informed authorities it will not proceed with a manufacturing facility in the country.
Tesla first signaled serious interest in India around 2021, when it began hiring local staff and lobbying the Indian government for lower import tariffs. The ask was straightforward: reduce duties enough for Tesla to test the market with imported vehicles before committing capital to a local factory. India’s position was equally firm, with an ask of Tesla to commit to manufacturing first, then receive tariff relief. Neither side moved, and the talks quietly collapsed.
Tesla to open first India experience center in Mumbai on July 15
India had offered a policy that would reduce import duties from 110% down to 15% on EVs priced above $35,000, provided companies committed at least $500 million toward local manufacturing investment within three years. Tesla declined to participate. The tariff standoff was only part of the problem. Analysts pointed to significant gaps in India’s local supply chain, inadequate industrial infrastructure, and a mismatch between Tesla’s premium pricing and the purchasing power of India’s automotive market as additional factors that made the investment difficult to justify.
First signs of an unraveling relationship came in April 2024, when Musk abruptly cancelled a planned trip to India where he was set to meet Prime Minister Modi and announce Tesla’s market entry. By July 2024, Fortune reported that Tesla executives had stopped contacting Indian government officials entirely. The government at that point understood Tesla had capital constraints and no plans to invest.
The more fundamental issue is that Tesla’s existing factories are currently operating at approximately 60% capacity, making a commitment to building new manufacturing capacity in a new market difficult to defend to investors. Tesla will continue selling imported Model Y vehicles through its existing showrooms in Mumbai, Delhi, Gurugram, and Bengaluru, but local production is no longer part of the plan.
Tesla scales back driver monitoring with latest Full Self-Driving release
Tesla Full Self-Driving expands in Europe, entering its second country
