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
Why SpaceX is finishing another space-internet system that isn’t Starlink
SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.
SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.
Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.
With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.
A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.
Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.
For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.
Elon Musk
Tesla gives the Roadster an official “Go for launch” demonstration date
Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.
Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.
Go for launch pic.twitter.com/Khu03eiZ04
— Tesla (@Tesla) September 12, 2026
Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.
The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.
Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video
Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.
The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.
Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.
Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.
In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.
Glad you are safe. Even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance coming as part of the next big upgrade (v15).
— Ashok Elluswamy (@aelluswamy) September 11, 2026
The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.
The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.
Tesla is rolling out a new FSD version with a massive safety addition
Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.
Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.
A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.
European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.
Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.
Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.
Why SpaceX is finishing another space-internet system that isn’t Starlink
Tesla gives the Roadster an official “Go for launch” demonstration date
