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.
The Tesla Model Y L is arguably the most hyped trim of the all-electric crossover, other than the Performance configuration that comes with white-knuckle speed and sports car-level handling.
However, it is not all perfect. Tesla owners in China who took delivery of the Model Y L, denoted with an L to highlight its longer wheelbase, are experiencing what they are referring to as “collapsing” of the rear wheels, as suspension issues appear to be an issue with some of the builds.
🚨 Model Y L owners in China report rear suspension sag
• Six-seat long-wheelbase Y. Shanghai. On sale since August 2025
• Owners say the rear tire-to-arch gap shrinks after mileage or a full load. Some cases after about 9,000 km loaded. Others near 30,000 km
• Tesla service… pic.twitter.com/Lr6i5Tbi07— Joe Hansen (@joehansen) September 1, 2026
The gap between the wheel arch and tire has narrowed to the point that “not even a single finger” could fit, according to a report from Car News China. The failures are not tied to a specific mileage, as one owner said that after just 9,000 kilometers (5,600 miles), they noticed the suspension issue when their car was fully loaded.
Another one had the issue at 30,000 kilometers (18,640 miles) and noticed that the wheel gap shrank to two fingers, so not as drastic as the person who reported a similar issue at 9,000 km.
Tesla Model Y L is gaining momentum in China’s premium segment
Along with the visual recognition of the issue, others are saying the sagging is causing abnormal wear on the inside of the tires. Extra weight and instant torque already provide additional stress on the tires in electric vehicles during normal operation, so it is no surprise that this is another complaint.
There has been no recall issued by Tesla, and the company has not yet publicly acknowledged the issue.
Some are suggesting that owners use a “finger test” to self-diagnose whether there is an issue with the suspension. There should be four fingers between the tire and the wheel well; anything less than that starts to get dicey.
Tesla is starting to truly tease and hype its groundbreaking Cybercab event, which takes place tomorrow in Austin, Texas. It will be the first time members of the public will be able to ride in a Cybercab, a vehicle without any manual controls, on public roads.
Tesla has been dropping some hype on X over the past several days, but this morning, the excitement has truly started to build up for the event. Although Cybercab has been unveiled before, this is truly Tesla’s announcement that it is ready to start offering autonomous rides for public passengers in its new ride-hailing-geared vehicle for the first time.
The hype has started with a variety of different social media posts that are a true indication that Tesla is preparing for something big. Teasing so much of the potential of Cybercab, including its ability to truly revolutionize how people hail rides for local travel, is what the big idea for the event entails. The time that many Tesla owners, fans, and investors have been waiting for is potentially here:
— Tesla (@Tesla) September 2, 2026
The event has remained slim on details. Even invitees are still awaiting true details about what the event will entail, where they’ll go, and what is in store for the evening. This is pretty typical for an event run by Tesla; they keep things under wraps for the most part until the very last minute.
However, there is no secret about what the real intention of Tesla is for this event: it is going to be a huge reveal party for a vehicle that has no steering wheel and no pedals. It is a truly massive step for the company moving forward.
No steering wheel, no pedals
— Tesla Robotaxi (@robotaxi) September 2, 2026
Speculation persists as to whether this is going to be an event that simply announces that rides will begin with the Cybercab, or it will be something more substantial. Tesla has said in the past that they plan to sell the Cybercab to the general public in what could become a great way to earn passive income by adding it to a more global fleet of Robotaxi-geared vehicles.
Tomorrow, the show begins in Austin, and the Cybercab goes live at some capacity; we just don’t know exactly how quite yet.
News
SpaceX tells the FCC that Starship Flight 14 is going to orbit
SpaceX filed with the FCC for Starship Flight 14, its first true orbital launch attempt.
SpaceX has asked the Federal Communications Commission for permission to fly Starlink terminals during Starship’s fourteenth flight test, and the filing lays out a genuine trip to orbit, something the program has never attempted.
Every Starship flight so far, including Flight 13’s successful splashdown in the Indian Ocean on July 24, has flown a suborbital arc that ends with the ship reentering the atmosphere within the same hour it launches. The FCC paperwork describes a mission profile built around an actual orbital insertion instead.
The payload is the other half of the story. Flight 13 carried 20 production Starlink V3 satellites, but because that mission never reached orbit, the satellites reentered along with the ship rather than joining the constellation, something Teslarati covered in detail after SpaceX released footage shot from one of those satellites as it drifted away from Starship in space. Flight 14 is designed to close that gap. If the orbital insertion holds, the roughly 20 V3 satellites onboard would separate into an operational orbit and could eventually go into service, each one rated for about 1 terabit per second of downlink capacity by SpaceX’s own account.
SpaceX announces new Starbase for ‘thousands of Starship launches annually’
Elon Musk first flagged the orbital attempt during SpaceX’s August 4 earnings call, the company’s first as a public entity following its June IPO under the ticker SPCX. He also floated catching the ship with the Starbase tower on the same flight, an idea he walked back on August 20, saying the catch attempt would more likely come “in a few months,” as Teslarati reported at the time. Flight 14 will instead target a splashdown for the ship in the Indian Ocean, the same recovery method used since Flight 12.
Hardware has been catching up to the ambition. Booster 21 completed a full 33-engine static fire on August 28, and Ship 41 finished its own six-engine test the week before. An airspace briefing circulated to pilots on August 20 listed September 15 as the target date, later than the end of August window Musk mentioned on the earnings call, though SpaceX has not confirmed a launch date publicly and Starship schedules routinely slip while hardware and FAA paperwork line up.
The FCC filing itself does not guarantee a launch date. It covers communications authority, and not flight readiness, considering SpaceX still needs Ship 41 fully stacked and cleared by the FAA before Flight 14 can fly. But the filing is a real marker of intent and it puts a specific regulatory process behind what had so far only been Musk’s word on the earnings call.
Tesla Model Y L gets suspension complaints in over odd issue China
Tesla Cybercab event gains steam ahead of massive launch
