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.
For years, there have been images and videos across social media platforms that have reminded me of when I was a 15-year-old kid teased by “Xbox 720” videos on YouTube. These videos are of the supposed “Tesla Phone” that Elon Musk was secretly developing in between leading Tesla with its electric cars and SpaceX with its reusable rockets.
Would you buy a Tesla phone ? pic.twitter.com/aaTwvvIJit
— Tesla Owners Silicon Valley (@teslaownersSV) October 6, 2023
Although Musk has put those rumors to bed several times, it was never completely out of the realm that he could get involved in cell phones in some capacity. Think outside the box and more macro-level, though. Instead of reinventing the computer, Musk reinvented connectivity by developing Starlink with SpaceX.
It could be something similar, TD Cowen analyst Gregory Williams said in a note last week, where he hinted SpaceX could be gathering some steam to acquire T-Mobile.
Williams said it would be the “clear choice” for SpaceX if it decided to go through with a network acquisition. He also suggested AT&T.
The move would be possible through selling more of its own stock, which would help SpaceX raise the money to purchase T-Mobile, which would cost roughly $300 billion. It could be one of the moves SpaceX makes post-IPO in terms of an acquisition: it already acquired Cursor AI for $60 billion.
Other analysts, like Dan Ives of Wedbush, believe SpaceX and Tesla will eventually merge into one anyway, and that conglomeration could come as soon as this year, some have said.
The implications of SpaceX purchasing T-Mobile are massive. A combined entity would create a truly ubiquitous network: T-Mobile’s terrestrial 5G towers and Starlink’s growing constellation of Direct-to-Cell satellites. This would essentially eliminate dead zones across the U.S. and potentially globally.
SpaceX would instantly become a full-scale facilities-based carrier with satellite differentiation; a huge advantage. This would pressure AT&T and Verizon heavily.
There are also concerns like a potential reduction in long-term competition, and of course, a deal of that size would face intense scrutiny from government agencies.
The strategic fit is compelling due to the existing Starlink–T-Mobile partnership and complementary technologies (space + terrestrial). It could create a dominant integrated communications player. However, the regulatory, financial, and execution hurdles are enormous — this remains highly speculative with no indication SpaceX is actively pursuing it right now.
Tesla revealed a major new Cybercab detail in a guide it released for First Responders, showing new territory in its beliefs and intentions for the ride-hailing-focused vehicle that entered production in April.
The First Responders Guide is released to give fire departments, paramedics, and other emergency personnel the proper guidance on what to do in the event of an accident, entrapment, or other situation that would require immediate attention.
On one of the pages of the First Responders Guide, Tesla revealed a stark detail about the Cybercab, which could help personnel enter the vehicle more easily in case of an emergency.
Tesla Cybercab has one important piece that AI4 cars might need for FSD
It shows Tesla has no intention of releasing any Cybercab units that were initially proposed for ride-hailing services for the general public with any manual controls, meaning a steering wheel or pedals:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or acceleration and brake pedals.”
New official Cybercab documentation from Tesla:
“A Cybercab equipped with steering wheel, brake pedal, and an acceleration pedal is typically an engineering or test vehicle, and operates at SAE Level 2 autonomy. Cybercab is not typically equipped with a steering wheel or… https://t.co/P6ut1mZyzr pic.twitter.com/yq6skl9s2J
— Sawyer Merritt (@SawyerMerritt) June 27, 2026
This is a major development for those who continue to believe Tesla planned to release the Cybercab with any sort of manual controls so that passengers could take over if needed. However, when Tesla started manufacturing production versions of the Cybercab in Giga Texas earlier this year, they were spotted without a steering wheel or pedals.
It essentially confirms the company has no intentions of bringing manual controls to the car’s production versions. Some have argued that the likelihood of Tesla having something
There still are some Cybercab units out there with a steering wheel and pedals, and as Tesla said, these cars are engineering or test vehicles, which have Safety Monitors on board to help the car out of a precarious situation or emergency.
Tesla released the Full Self-Driving v14 ‘Lite’ suite to owners of Hardware 3 or AI3 vehicles today, adding several new features to the vehicles that were once believed to be capable of unsupervised self-driving.
Now, Tesla has released this modified suite to older Tesla vehicles, adding plenty of new features and capabilities.
Here are the full release notes for the suite:
- Distilled the intelligence from HW4 V14 into HW3. This allows HW3 to directly learn how to handle scenarios using HW4 V14 as a guide. This process unlocks the improvements that have been made to HW4 including Reinforcement Learning (RL) and offline models for HW3.
- Improved both proactive and reactive responsiveness across a wide variety of categories including navigation handling, merges and forks, pedestrian interactions, traffic lights, and vehicle cut-in scenarios.
- Improved general comfort in nominal scenarios through fewer false slowdowns, smoother steering and more consistent lane centering.
- Introduced parking, unparking, and reversing capabilities.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, or at the Curbside.
- Speed Profiles are now available at all times, to further customize driving style preference.
These improvements, according to Tesla’s Head of AI, Ashok Elluswamy, help distill the driving behavior from AI4’s v14 series into both the camera and compute configurations of AI3.
Tesla Full Self-Driving v14 ‘Lite’ for older cars finally gets released
He added:
“It includes destination options and speed profiles on city roads, but more importantly significantly improved safety. We hope you’ll enjoy it, once the build ships wide.”
FSD v14 Lite is now rolling out to AI3 early-access customers. Based on the feedback, will rollout to more customers over the next few weeks.
This build distills the driving behavior from AI4’s v14 series into both the camera and compute config of AI3. It includes destination…
— Ashok Elluswamy (@aelluswamy) June 29, 2026
Tesla will continue to roll out the v14 Lite suite more widely in the coming weeks, the company said.
Tesla Phone? Not quite, but close: analyst
Tesla reveals huge Cybercab detail in new guide for First Responders
