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.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Elon Musk
Elon Musk just upped his Tesla stake further fueling SpaceX merger conversation
Elon Musk just collected a $116 billion Tesla payday and the timing is eye-opening
Elon Musk quietly collected one of the largest single-transaction paydays in corporate history on Monday. A Form 4 filed with the SEC on June 17, 2026 disclosed that Musk exercised 303,960,630 Tesla stock options from his 2018 compensation package, with the transaction dated June 16. No shares were sold on the open market.
The numbers are straightforward but striking. Musk exercised the options at a split-adjusted strike price of $23.34, with Tesla closing at $404.66 that day, putting the spread at $381.32 per share and generating roughly $115.9 billion in paper gains in a single transaction. To cover the exercise cost, Tesla withheld 17,531,857 shares through a net share settlement, meaning Musk paid nothing out of pocket.
For perspective, in 2018, Elon Musk’s award was originally approved by Tesla shareholders on March 21, 2018, and structured entirely around performance milestones that many analysts at the time called unreachable. Every tranche eventually vested. The original grant covered 20,264,042 shares at $350.02, which after Tesla’s 5-for-1 split in 2020 and 3-for-1 split in 2022 adjusted to 303,960,630 shares at $23.34. A Delaware court rescinded the award in January 2024, ruling the board was conflicted. As Teslarati reported, Tesla shareholders voted to ratify the package anyway in June 2024 by a wide margin. The Delaware Supreme Court reversed the decision in December 2025, finding full cancellation too extreme, and Tesla’s board signed an Implementation Agreement on April 21, 2026 to formally deliver the shares.
The Tesla and SpaceX merger everyone is talking about is quietly building
The timing and structure of the Form 4 filing carries more weight than a routine stock option exercise typically would. Musk exercised his 2018 Tesla award on June 16, a week into SpaceX completing its IPO and trading publicly, and giving SpaceX a public market valuation and share currency for the first time in the company’s history. A stock-for-stock merger between two companies requires the acquiring entity to have tradeable shares it can offer to the target’s shareholders, and SpaceX now has exactly that. At the same time, Musk just increased his direct Tesla voting power to approximately 20%, giving him greater influence over any shareholder vote that a merger would require. The restricted shares he received cannot be sold until 2033, which removes any near-term incentive to cash out and instead positions this stake as long-term structural collateral in a deal. Additionally, Musk’s two companies are already deeply intertwined through shared semiconductor fabrication at their joint TERAFAB facility in Austin, cross-company supply chain transactions, and Tesla’s $2 billion investment in xAI prior to the SpaceX-xAI merger.
Wedbush analyst Dan Ives has publicly placed the odds of a Tesla and SpaceX combination at 80% to 90% by early 2027. The Implementation Agreement that made Monday’s exercise possible was signed on April 21, 2026, roughly two months before the SpaceX IPO closed. That sequencing, building Musk’s Tesla ownership to its highest point ever immediately before SpaceX gains the public currency needed to acquire it, is either an extraordinary coincidence or a carefully staged foundation for the largest corporate merger in history.
Tesla Full Self-Driving is going to be getting a major parking upgrade. That’s according to CEO Elon Musk, who detailed a crafty new feature that will improve parking preferences, removing a layer of human input.
Musk said that upcoming releases of Full Self-Driving will “remember your parking preferences.” It will go to the location you prefer, based on where you’ve parked in the past, instead of taking the first spot available, which is where the suite is currently.
The CEO went on to explain that destination parking is “by far” the biggest reason for intervention during FSD operation. We’d have to believe this is true; many takeovers in my Model Y, which runs the latest version of FSD as it is in the Early Access Program, are due to parking because it chooses a spot I do not want to be in.
Many times, as soon as I enter a parking lot, I take over and park manually. I prefer to park away from the entrance of wherever I am, away from cars. Too many lessons learned over the years from people with free-swinging doors.
Upcoming releases of FSD will remember your parking preferences, so that the car goes to the right location at your home, office, school drop off, etc.
Destination parking is by far the biggest reason people now intervene with FSD. Critical safety interventions are extremely…
— Elon Musk (@elonmusk) June 17, 2026
We’d imagine these new updates will also solve things like parking orientation. Let’s say when you arrive at work, you always park in the third spot in the third row, and you prefer to back in. It seems as if Musk is implying that your car will now do this, learning from takeovers and aiming to eliminate the need to manually park whenever possible.
This is a major upgrade because parking is a major shortcoming of FSD currently. We’ve requested things like manual input of parking preferences, choosing to park far away, first available, or away from cars, for example.
This is a big reason Parking Preferences with Supervised FSD will be so valuable.
If possible, parking a little further away and being distant from people like this is worth it. https://t.co/1YqQLgnfTz pic.twitter.com/3Ac71KQiQ3
— TESLARATI (@Teslarati) June 7, 2026
However, some have used the option of dropping a pin at the location you’d like to park at your destination. This has worked some of the time, but FSD will still choose to park in whatever it sees first.
Musk did not give a timetable for when the improvements would be released, but it is likely to come soon. Tesla has been releasing a new FSD version every few weeks, so we may not have to wait long to test it.
Tesla Cybercab has one important piece that AI4 cars might need for FSD
Elon Musk just upped his Tesla stake further fueling SpaceX merger conversation
