Connect with us

News

SpaceX Starship prototype ignites six engines, starts major brush fire

Despite starting a major grass fire, Starship S24's first six-engine static fire appears to have been a success. (SpaceX)

Published

on

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.

Advertisement
-

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.

It appears that September 8th’s accidental brush fire burned at least several dozen acres. (NASASpaceflight)

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.

Advertisement
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla surges Robotaxi fleet ahead of Cybercab launch event

Tesla’s unsupervised robotaxi fleet quietly grew sevenfold in three weeks just before Cybercab Day arrives.

Published

on

By

Tesla’s unsupervised Robotaxi fleet has grown far faster than the public numbers suggested, and the timing lines up with the company’s biggest autonomy showcase yet. According to data compiled by the crowdsourced Robotaxi Tracker, Tesla now has nearly 200 vehicles operating without a safety monitor across Austin, Dallas and Houston, yielding a roughly 7X increase in about three weeks.

The jump lands four days before this week’s Tesla Cybercab launch event in Austin, where the company plans to show off its purpose-built, two-seat robotaxi with no steering wheel or pedals in a live commercial setting for the first time. Stick with us on X and Facebook for live reporting from the event.

The strategic logic is straightforward. Tesla has spent the past year scaling Robotaxi in small, deliberate steps, first widening geofences, then extending operating hours, then quietly growing fleet size, usually with little advance notice. Ashok Elluswamy told investors on the Q2 earnings call that the program had logged more than 380,000 unsupervised miles with zero notable incidents, a safety record the company has leaned on to justify moving slowly. Critics have used the flip side of that caution, a fleet that appeared stuck around two dozen vehicles for months, as evidence that Tesla’s driverless ambitions were outrunning its actual deployment.

A fleet quietly scaling to nearly 200 vehicles right before Cybercab Day undercuts that argument without Tesla having to say anything about it directly. It also sets up the event to do double duty. Rather than simply introducing new hardware, Tesla can point to an operating base of unsupervised Model Ys already running at meaningful scale, then argue the Cybercab, which uses the same underlying Full Self-Driving stack according to earlier coverage of the fleet’s software upgrades, is a natural next steps. Tesla has separately been registering the two-seat Cybercabs with Texas regulators this week, with the count climbing from seven to 45 in a matter of days.

The two ramps, one in software-driven Model Y deployment and one in physical Cybercab registrations, are happening in parallel rather than in sequence. That suggests Tesla wants Thursday’s event to land as proof that the robotaxi business is already running at scale, not just a reveal of a new vehicle shape. Whether the unsupervised numbers hold up once Cybercabs start mixing into the same fleet is the detail worth watching once the event wraps.

Continue Reading

Cybertruck

Tesla Cybertruck windshield protection just got cheaper

Published

on

Credit: Tesla

Tesla is lowering the monthly price of its Cybertruck Windshield Protection Plan from $35 to $25. The new rate will apply to the first payment on or after October 1, 2026. Tesla has told subscribers that all other benefits stay the same.

The plan covers unlimited repairs for chips and minor cracks on the front windshield. It also includes one full replacement every 12 months at no extra charge. Additional replacements in the same year carry a $100 deductible. Service is performed with Tesla glass and camera calibration, which matters because Autopilot and Full Self-Driving rely on those lenses behind the windshield.

There is no long-term contract. Coverage applies only to the front glass and does not include collision, vandalism, or weather damage.

The Cybertruck’s large, complex windshield has been more expensive to replace than glass on Tesla’s cars, which is why the pickup started at a higher subscription price. The $10 monthly cut reduces the annual cost from $420 to $300. Tesla has not publicly explained the change. The timing coincides with a year of claims data after the plan was extended to the Cybertruck.

Tesla sells several related protection products as monthly subscriptions through the Tesla app. The Windshield Protection Plan is also offered on other models. Model 3 and Model Y currently cost $16 a month. Those passenger-car rates are unchanged in the latest Cybertruck notice.

The Wheel and Tire Protection Plan covers road-hazard damage such as potholes, nails, and debris. Repairs are unlimited. Each wheel or tire replacement appointment has a $25 deductible. Pricing varies by model and whether the vehicle is a Performance version. Tesla is raising some of those rates on the same October 1 date.

Reported examples include Model 3 Performance moving from $16 to $24 and Model Y Performance from $20 to $24. Cybertruck wheel-and-tire coverage has been listed at $20 a month for the standard configuration.

A separate Luxe Package bundles four years of windshield coverage, wheel-and-tire coverage, and recommended maintenance on certain new Model S, Model X, and Cyberbeast orders, although the Model S and X are now defunct.

Tesla also offers an Extended Service Agreement after the basic vehicle warranty ends. That product covers many Tesla-manufactured parts rather than glass or tires. Together, the plans give owners a menu of targeted, cancel-anytime coverage instead of relying only on auto insurance.

Continue Reading

News

Tesla Cybercab fleet grows in Austin ahead of launch event

Published

on

Credit: Teslarati

UPDATE: The number has now been updated to 45 units, up from 7!

Tesla is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.

Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.

The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.

Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:

Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.

Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.

The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.

Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.

The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.

Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.

Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.

Continue Reading