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.
SpaceX’s Raptor engine family has steadily increased sea-level thrust while simultaneously reducing mass, turning iterative engineering gains into substantially higher performance for the Super Heavy booster. CEO Elon Musk shed more light on how powerful Raptor 4 will be, and it’s pretty crazy.
Raptor 1 delivered 185 metric tons of thrust at roughly 2,080 kilograms, while Raptor 2 raised that to 230 tons while cutting mass to about 1,630 kilograms. SpaceX data for Raptor 3 lists a target of 280 tons at 1,525 kilograms (with further reductions in associated vehicle hardware), while operational flight ratings have been cited near 250 tons.
This morning, Elon Musk stated that Raptor 4 is expected to reach 300 tons of sea-level thrust at roughly the same mass as Raptor 3. Across these versions, thrust has risen by more than 60 percent from the first engines while engine mass has fallen, producing a sharp improvement in thrust-to-weight ratio. This is a true testament to how great SpaceX engineering has been:
🚀 Elon says Raptor 4 will make 300 tons of thrust at sea level at roughly the same mass as Raptor 3.
How far Raptor has come:
Raptor 1: 185 tf, 2,080 kg
Raptor 2: 230 tf, 1,630 kg
Raptor 3: 250 tf, 1,525 kg
Raptor 4: 300 tf33 on Super Heavy = ~9,900 tf, nearly 3x Saturn V https://t.co/HQDswZhyvL
— TESLARATI (@Teslarati) October 26, 2026
With 33 engines on SuperHeavy, the jump from earlier versions to a 300-ton Raptor 4 would produce roughly 9,900 metric tons of total liftoff thrust, nearly three times the Saturn V’s approximately 3,400 metric tons from its five F-1 engines.
This is not just a larger number on a data sheet, either, as sea-level thrust is the force available the moment the vehicle leaves the pad. This is when it is heaviest and still deep in Earth’s gravity well and dense atmosphere.
Higher levels of sea-level thrust directly improves the initial thrust-to-weight ratio of the full stack. A higher ratio produces faster acceleration off the pad, which shortens the time the rocket has to spend fighting gravity, and gravity losses during the first minute or two of the flight are a major drain on total available delta-v. Every second shaved off of that early climb preserves more propellant energy for reaching orbital velocity or for carrying extra payload.
Because Super Heavy’s engine count is constrained by vehicle diameter and packing density, increasing thrust per engine is the most straightforward way to raise total liftoff performance without redesigning the booster structure or design.
The same-mass target for Raptor 4 is equally important. Holding engine mass roughly constant while raising thrust improves the engine’s own thrust-to-weight ratio and reduces the structural and propellant mass fraction that must be carried solely to support the engines.
Earlier Raptor iterations also simplified or eliminated extensive vehicle-side hardware such as heat shields. These gains compound: more force for less installed mass leaves additional capacity for propellant, payload, or operational margins such as engine-out capability.
For Starship’s architecture, the practical effects are large. Greater liftoff thrust supports heavier vehicles, larger propellant loads, and higher payloads to low Earth orbit, figures SpaceX has targeted in the 100-plus-ton reusable range. That capacity underpins orbital refueling, lunar missions, and eventual Mars cargo and crew flights.
Continued growth in sea-level thrust therefore tightens the gap between theoretical rocket performance and the high flight rates and reusability needed to make large-scale space transport practical.
Tesla has expanded its Tesla Assisted Driving (TAD) suite to its tenth European country, as Latvia joined a growing list of European Union member states authorizing the company’s advanced driver assistance technology.
Tesla Europe announced this morning that the system is now approved in Latvia, with a software rollout to begin soon.
The approval and rollout follow recognition of a provisional European type approval originally granted by the Netherlands’ RDW authority on April 10.
🚨 Latvia has just received approval for Tesla Full Self-Driving (Supervised)
This is the 10th country in the EU to gain approval:
1. Netherlands — 10 April 2026 (original RDW approval)
2. Lithuania — 20 May 2026
3. Estonia — 29 May 2026
4. Denmark — 9 June 2026
5. Belgium — 10 June 2026
6. Slovenia — 7 September 2026
7. Czechia — 21 September 2026
8. Croatia — 29 September 2026
9. Slovakia — 16 October 2026— TESLARATI (@Teslarati) October 26, 2026
Latvia’s Road Traffic Safety Directorate (CSDD) evaluated the Dutch documentation, coordinated with the other national authorities, and reviewed updates from Tesla. These included tightened limits on speed offsets, automatic resets of any manual speed adjustments after each trip, and stronger driver monitoring.
In Europe, the feature is marketed as Tesla Assisted Driving after a recent rule change that labeled the name “Full Self-Driving” as misleading.
The system remains an SAE Level 2 driver assistance tool, not unsupervised autonomy. It can control speed, steering, braking, lane changes, and intersections while following a navigation route. Drivers need not keep their hands on the wheel at all times, yet they must continuously monitor the road and be prepared to intervene immediately.
The sequence of EU recognitions began with the Netherlands in April and continued through Lithuania, Estonia, Denmark, Belgium, Slovenia, Czechia, Croatia, and Slovakia. Most have relied on mutual recognition of the single Dutch provisional approval rather than independent national testing.
These national clearances do not yet constitute bloc-wide authorization. An EU-wide decision requires a qualified majority in the Technical Committee on Motor Vehicles: at least 15 of 27 member states representing 65 percent of the EU population. Larger markets, like Germany, France, and Italy, remain under review, and a vote is expected this December.
However, for Latvian Tesla owners with compatible vehicles and software, the imminent rollout expands access to the supervised system while underscoring that attentive human oversight remains essential.
Tesla expanded its Robotaxi geofence in Houston, Texas, today, enlarging the service area and drawing a new rocket-shaped boundary across the city’s northwestern and central parts.
Although CEO Elon Musk said it was just a coincidence, the expansion seems to be an ode to SpaceX and its potential merger with Tesla.
🚨 Tesla has just expanded its Robotaxi geofence in Houston
It looks a lot like a rocket — we all remember the shape in Austin 🤣 https://t.co/cFOPEuiJ4u
— TESLARATI (@Teslarati) October 26, 2026
The official Tesla Robotaxi account announced the change with the lines “Houston, we have liftoff” and “Bigger service area now live,” pairing them with a map overlay.
The prior white geofence, roughly 25 square miles covering Jersey Village, Harvest Bend, and the Willowbrook corridor along U.S. 290 and State Highway 249, now sits inside a larger blue zone that stretches southeast toward Bellair and closer to central Houston.
Houston’s Robotaxi service launched on April 18, 2026, the same day as Dallas, as Tesla’s first unsupervised public expansion beyond Austin. From the start, the vehicles were Model Ys running without anyone in the front seats, booked through the dedicated Tesla Robotaxi app and open to the public inside the geofence.
Trackers measured the initial zone at about 25 square miles; by late September it had not grown substantially. Community and registry data indicated a modest local fleet of unsupervised Model Ys, while dozens to nearly 200 Cybercabs, the purpose-built, steering-wheel-free two-seaters, have been spotted staging and testing in Houston lots, though public Cybercab rides remain limited to Austin for now.
Across the broader Robotaxi program, Tesla began public Robotaxi rides in Austin in June 2025, as a small geofence and vehicles with safety monitors became available for a ride-hailing service. Later on, Tesla removed the monitors and steadily expanded the service area until it covered most of the Austin metro area.
Unsupervised Robotaxi services now run in six cities: Austin, Dallas, Houston, Miami, Orlando, and Tampa. Cumulative driverless miles reported by the company have reached several million. The Cybercab entered public service in Austin in early September 2026 and has scaled rapidly there. The company has also said that Dallas is next for Cybercab rides in November, with further cities and 24/7 hours targeted by year-end, plus fleet-operator sales of the vehicle.
Waymo also operates a fully driverless service in Houston, which has been open to the public since August of this year.
The Houston expansion continues Tesla’s pattern of starting with tightly controlled validation zones before widening coverage as real-world data accumulates, while the rocket motif on the map underscores the company’s habit of injecting visual flair into its autonomy rollout.
Riders inside the new boundary can request unsupervised Model Y trips in the Robotaxi app; exact operating hours and further Cybercab availability remain subject to app updates and company statements.
How SpaceX Is raising Raptor’s sea-level thrust while holding engine mass steady
Tesla Assisted Driving expands to tenth EU country
