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 Hardware 3 owners are set to get a new Full Self-Driving version this month as the company plans to release what it is referring to as v14 Lite.
The rollout is not yet confirmed for June, but Tesla executives have stated on several occasions that this more refined FSD iteration will work with their cars and increase its capabilities.
This comes after Tesla admitted during its last Earnings Call that these Hardware 3 vehicles would not be able to achieve Full Self-Driving, something that they did not know when they bought these cars. We regularly receive messages from Hardware 3 owners asking when v14 Lite will come out, what they should expect, and whether it is worth it to upgrade the self-driving computer or buy a new car altogether.
Following future rollout of FSD V14 Lite for HW3 vehicles in the US, we plan on expanding V14 Lite to additional international markets.
This update ensures that HW3 vehicle owners will continue to benefit from ongoing software updates.
Since international rollout is subject to…
— Tesla (@Tesla) April 29, 2026
It is hard not to feel for them; Tesla CEO Elon Musk said at the company’s 2019 Autonomy Day that all vehicles produced at the time, including Hardware 3 cars, had “all the hardware necessary, compute and otherwise, for Full Self-Driving.”
Musk also said in March of that year that, “Anyone who purchased Full Self-Driving will get FSD computer upgrade for free.”
Anyone who purchased full self-driving will get FSD computer upgrade for free. This is the only change between Autopilot HW2.5 & HW3. Going forward “HW3” will just be called FSD Computer, which is accurate. No change to vehicle sensors or wire harness needed. This is v important. https://t.co/lICMpT7xnX
— Elon Musk (@elonmusk) March 29, 2019
However, during the Q1 2026 Earnings Call, Musk admitted that Hardware 3 vehicles would not be capable of FSD, as “It has only 1/8th the memory bandwidth of Hardware 4, and memory bandwidth is one of the key elements needed for unsupervised FSD.”
Tesla has made some effort to remedy these Hardware 3 owners by offering:
- Discounted trade-ins toward AI4 cars
- Hardware retrofits, which would replace the self-driving computer and upgrade all cameras
- Full Self-Driving v14 Lite
The issue is that many of these owners were led to believe their cars would be capable of unsupervised self-driving. Now, they’re left scrambling for options, and while there are several, they will all require more money out of their pockets.
Expectations for Tesla v14 Lite for Hardware 3 Owners
The big differences between the AI4 v14 and v14 Lite for Hardware 3 owners will stem primarily from hardware constraints. Tesla developed v14 Lite with an optimized frame of mind; the v14 neural nets are toned down to run on an HW3 computer.
Tesla v14 will use the same behavior, but its limits will be hardware-related, especially given that the cameras on HW3 vehicles are lower-resolution.
Tesla reveals its plans for Hardware 3 owners who are eager for updates
This will result in potentially more edge cases due to the lower quality perception and less long-range detection, but reaction time and overall confidence should be more refined.
There should also be a handful of additional features that are available on AI4 cars, such as:
- Starting Full Self-Driving from Park
- Auto Shift
- Streaks
- Speed Profiles
- Improved Dynamics, like Pulling Over for Emergency Vehicles
Tesla plans to release v14 Lite this month, but we are all familiar with how the company can be with timelines. Additionally, if v14 Lite has not proven to be ready for a wide release, Tesla will slam the brakes on the rollout.
We would anticipate that Tesla is testing v14 Lite internally, and likely has been for several months.
Elon Musk
SpaceXAI just launched into your kitchen with their new app
SpaceXAI just powered its first consumer app and it predicts what you want to buy.
SpaceXAI just made its first move into consumer AI, and it involves your grocery cart. On June 3, 2026, Gopuff and SpaceXAI announced the launch of Go, a Grok-powered shopping assistant built directly into the Gopuff app that predicts what you need before you even start searching for it.
Gopuff is an instant delivery platform that operates more than 400 micro-fulfillment centers across the U.S., delivering everyday essentials, snacks, drinks, and household items in as little as 15 minutes. It is not a restaurant delivery app or a marketplace. It owns its inventory, controls its warehouses, and handles its own logistics, which means it has built one of the most detailed consumer behavior datasets in retail over its 13-year history.
Go combines SpaceXAI’s advanced reasoning, voice, and image generation models with Gopuff’s dataset of hundreds of millions of orders and real-time cultural signals from X to prepare a suggested cart the moment a customer opens the app. It learns each shopper’s habits and automatically builds a personalized cart based on time of day, location, order history, and real-time indicators. Returning customers can check out with a single tap.
Rather than searching for specific items, users can describe a situation like a game-day party or the desire for a healthy breakfast and Go will assemble a cart automatically. It can also predict when shoppers are running low on items like coffee or paper towels and have them packed and delivered in under 15 minutes. Grok voice integration lets users talk to the app in plain conversational language and check out completely hands-free.
Gopuff co-founder and co-CEO Yakir Gola said: “Today, we believe the greatest friction left in commerce is not delivery or instantaneous access to the essentials customers need. It’s the moment before: the thinking, the deciding, the remembering. We’re combining Gopuff’s demand intelligence with xAI’s frontier reasoning to create an everyday shopping experience that feels like a true extension of you.”
Why SpaceX just made a $60 billion bet on AI coding ahead of historic IPO
The timing carries context beyond the product launch. SpaceXAI was formed after SpaceX completed an all-stock merger with Elon Musk’s xAI earlier this year, folding one of the most advanced AI labs in the world into the same corporate structure as the company preparing what could be the largest IPO in history. SpaceXAI is dipping into consumer-focused AI just as it prepares for its public debut, and while Musk has openly discussed building an everything app, this launch uses Grok to power another company’s product rather than launching a standalone consumer platform. Every consumer-facing deployment of Grok ahead of the IPO roadshow adds tangible evidence that SpaceXAI is not just an infrastructure play but a direct competitor in the AI application layer where OpenAI and Google are already fighting for dominance.
Tesla has introduced an enhanced visualization in its Supercharger navigation system, building directly on the Site Maps feature rolled out a few months ago.
This latest software update adds detailed 3D icons that represent specific vehicle models parked at charging stalls, offering drivers a more precise view of site occupancy and layout.
The Site Maps debuted in Tesla’s 2025 Holiday Update, providing 3D overviews of select Supercharger locations with real-time stall availability.
Tesla supplements Holiday Update by sneaking in new Full Self-Driving version
Drivers could see which spots were open, occupied, or out of service when navigating to supported stations.
Now, the system takes this capability further by rendering accurate representations of Tesla vehicles, including distinctions between models such as the Model 3, Model Y, Model S, Model X, and Cybertruck. These icons appear as lifelike 3D renderings, complete with recognizable shapes and proportions that match the actual cars charging at the site:
Supercharger update now shows type of Tesla at charger as well.
Pretty cool. pic.twitter.com/J3NRSIgM0m
— DennisCW | wen my L (@DennisCW_) June 2, 2026
This refinement improves the user experience during road trips and daily charging stops. As drivers approach a Supercharger, the navigation display now shows not just generic occupied markers but identifiable vehicle types plugged into each stall.
Blue indicators highlight active charging sessions, while other visual cues denote availability or maintenance status. The feature integrates seamlessly with the existing map interface, allowing quick assessment of the best available spot based on vehicle size and positioning.
Tesla continues to expand the availability of these detailed Site Maps across its global network. Initially piloted at a limited number of locations, the rollout has progressed steadily, with more stations gaining support in recent software versions.
Owners benefit from better planning, as the system helps identify compatible stalls and reduces uncertainty upon arrival. The update reflects Tesla’s ongoing commitment to refining its navigation and charging ecosystem through iterative software improvements.
In addition to model-specific icons, the enhanced maps maintain all prior functionalities, such as integration with nearby amenities and energy usage predictions. This ensures a comprehensive tool for efficient Supercharging.
As Tesla’s fleet grows and the network scales, such features play a key role in optimizing the overall ownership experience. Future updates may extend similar visualizations to additional sites and incorporate even more data points for drivers.
With this piggyback enhancement, Tesla demonstrates how small but thoughtful additions can elevate an already useful tool, making Supercharger visits smoother and more informed for its customers. The company is expected to broaden the feature’s reach in upcoming releases, further solidifying its leadership in EV charging infrastructure.
Tesla Hardware 3 owners could be made whole this month
SpaceXAI just launched into your kitchen with their new app
