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.
News
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.
SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.
Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.
Watch Falcon 9 launch the USSF-385 mission from pad 4E in California https://t.co/CAdbx85Ydy
— SpaceX (@SpaceX) September 26, 2026
USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.
The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.
Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.
The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.
News
Tesla hints at new Roadster design in surprise clip
Tesla ended its Semi event with a Roadster teaser revealing a new front light bar.
Tesla closed out its Semi event in Nevada on Thursday night with a nod to its own history, dropping a short Roadster teaser that suggests the production car will look noticeably different from the prototype first shown in 2017.
“We can’t have a Semi event without the Roadster,” Tesla engineering executive Lars Moravy told the crowd before the clip played. The line was a deliberate callback. Tesla first revealed the next generation Roadster in November 2017 by driving it out of the back of a Semi trailer at the truck’s original unveiling in Hawthorne, California.
The new video opens on trailer doors swinging apart in the dark. A thin white light bar glows across what appears to be the nose of the car, Tesla and SpaceX logos flash over the frame, and the Roadster name appears before the clip ends on “See you next week.” Tesla posted the nine second clip on X after the livestream wrapped.
See you next week pic.twitter.com/BT52bGVxFu
— Tesla (@Tesla) September 25, 2026
The light bar is the most concrete design detail so far. The 2017 prototype used two separate curved headlamp pods, while a connected front light strip would bring the Roadster in line with the Cybertruck, Cybercab, Semi, and refreshed Model Y. Sawyer Merritt was among the first to point out what looked like part of a SpaceX logo in the video, something Tesla has not addressed.
That logo fits the buildup around the optional SpaceX Package, which Elon Musk has long said would use cold gas thrusters to improve acceleration and possibly allow the car to briefly leave the ground. Tesla’s “Go for launch” post on September 12 set the October 1 date, and invitations sent to reservation holders place the event in Waco, Texas, at 8:30 p.m. Eastern. Waco sits roughly 20 minutes from SpaceX’s McGregor rocket test site, where the FAA has put a temporary flight restriction in place from September 18 through October 2, covering a 1.5 nautical mile radius from the surface up to 10,000 feet.
Tesla is also taking money ahead of the reveal. The company reopened Roadster reservations earlier this week with a $5,000 refundable card payment, followed by a $45,000 wire transfer due within 10 days. That puts buyers at $50,000 committed before Tesla has published a price.
The original pitch set a high bar: 0 to 60 mph in 1.9 seconds before any upgrades, 620 miles of range, a top speed above 250 mph, and production in 2020. That timeline has slipped repeatedly, and Tesla has since pointed to production at Gigafactory Texas no earlier than 2027. The company has said next Thursday’s event will include pricing, specifications, and production targets, the three details original reservation holders have been waiting on for nearly nine years.
Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.
The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.
Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.
That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.
Elon Musk’s reply to the delay was a single word: “Sigh.”
Sigh
— Elon Musk (@elonmusk) September 25, 2026
Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.
Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.
The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.
An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.
Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval
The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.
Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
Tesla hints at new Roadster design in surprise clip
