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.
Just hours after Starship Flight 13 achieved a successful soft splashdown of its upper stage in the Indian Ocean on July 24, Elon Musk announced an ambitious next step for the company’s next launch of the rocket.
“Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on [the] next flight,” the SpaceX CEO posted on X on Friday.
That “next flight” is expected to be Flight 14. The plan involves returning the Starship upper stage, commonly called the “ship,” to the Starbase launch tower in Texas and catching it mid-air using the same mechanical “chopsticks” arms that have already proven themselves with the Super Heavy booster.
Unless we discover problems after mission data review, SpaceX will attempt to catch the ship with the tower on next flight
— Elon Musk (@elonmusk) July 25, 2026
A successful catch would mark the first time an orbital-class upper stage has been recovered this way, advancing SpaceX’s goal of full and rapid reusability for the entire vehicle.
SpaceX has already demonstrated the tower-catch technique multiple times with Super Heavy. The first successful catch came on Flight 5 in October 2024, when Booster 12 was plucked from the sky by the Mechazilla arms. Subsequent flights, including those involving Boosters 14 and 15, repeated the feat. Several of those recovered boosters were later inspected, refurbished, and flown again, proving the system’s viability for quick turnaround.
Traditional reusable rockets, such as SpaceX’s own Falcon 9 or Blue Origin’s New Shepard, land on legs either on land or droneships. Rocket Lab has recovered its small Electron first stages by helicopter, but those are far lighter vehicles.
SpaceX Starship just nailed something it’s never done before
The China Academy of Launch Vehicle Technology (CALT), a subsidiary of the China Aerospace Science and Technology Corp. (CASC), completed a catch of its booster on July 10. They are the only entity besides SpaceX to attempt and complete the feat.
Flight 13 provided encouraging data. The ship executed a controlled reentry, flipped, and soft-landed intact in the ocean after deploying Starlink satellites, offering the first clear post-splashdown views of an undamaged heat shield. The Super Heavy booster, meanwhile, experienced a harder splashdown in the Gulf of Mexico.
Musk has previously stressed that ship catches would only follow multiple successful soft ocean landings to minimize risk of debris over land.
If Flight 14 succeeds, SpaceX would take a major stride toward routine, rapid reuse of both stages—critical for lowering launch costs and supporting ambitious plans for lunar and Mars missions. For now, teams are reviewing the Flight 13 data. Should everything check out, the next Starship flight could deliver one of the most spectacular recoveries in aerospace history.
In a move echoing its earlier commitment to open innovation, Tesla CEO Elon Musk announced recently that the company plans to make the design and software of its Model S and Model X fully open source.
This follows the same approach Tesla took with its original Roadster, releasing all available design, engineering, and diagnostic materials in November 2023 so that “whatever we have, you now have.”
Just as Tesla made the original Roadster design & software open source, we plan to do the same with Model S & X
— Elon Musk (@elonmusk) July 24, 2026
The Model S, introduced in 2012, was Tesla’s first mass-produced vehicle and a groundbreaking luxury electric sedan. It offered impressive range, rapid acceleration, and over-the-air software updates that redefined expectations for electric cars.
The Model X, launched in 2015, built on that foundation as a high-performance electric SUV notable for its distinctive falcon-wing doors, spacious interior, and advanced safety features. Both models served as flagships that helped establish Tesla as a leader in the EV industry and popularized long-range battery-electric vehicles.
Production of the Model S and Model X was wound down earlier in 2026, with manufacturing ending in the second quarter. Tesla redirected the Fremont factory space previously used for these vehicles toward higher-priority projects, including Optimus humanoid robots and the Cybercab autonomous vehicle.
By the time of Musk’s open-source announcement, custom orders had closed and only remaining inventory was available.
Open-sourcing the designs and software offers several clear advantages. Owners of these aging but still capable vehicles gain better access to technical documentation, diagnostic tools, and software resources, making independent repairs and modifications easier and more affordable.
Independent repair shops and third-party specialists can support the large existing fleet without relying solely on Tesla’s service network. Enthusiasts and engineers can study real-world implementations of Tesla’s battery, powertrain, and software systems, potentially accelerating broader industry progress in electric mobility.
The step aligns with Tesla’s 2014 patent pledge and its overall mission to advance sustainable transport by sharing hard-won knowledge rather than locking it behind proprietary walls.
By releasing these materials now that the models have left production, Tesla ensures continued support for its early adopters while freeing internal resources for future technologies. The open-source release of the original Roadster already enabled simulations, community projects, and deeper technical understanding.
Extending that practice to the Model S and Model X should deliver similar benefits on a larger scale, helping keep these influential vehicles relevant and repairable for years to come
Tesla flexed one incredible Robotaxi metric during the Q2 Earnings Call that skeptics have to hate to hear. The company’s platform has already driven more than 380,000 miles of unsupervised ride-hailing across several states with no notable incidents.
During the company’s Q2 Earnings Call on Wednesday, Vice President of AI, Ashok Elluswamy, said:
“First of all, I’d like to state that the Robotaxi program has been operating extremely well. Especially in terms of safety, the program has had an impeccable safety record. We have driven more than 380,000 miles of unsupervised Robotaxi, now across six cities in two different states. We have had zero notable incidents. Any reports have been of other actors impacting us when we were stationary. I like to emphasize how safe the operation has been so far. Zero notable incidents over 380,000 miles.”
Elluswamy’s claim over Robotaxi miles is a significant milestone for Tesla in the grand scheme, especially considering this is a sizeable number of miles without any incident.
0 notable incidents across over 380,000 miles traveled by Robotaxi
— Tesla (@Tesla) July 22, 2026
Tesla’s self-driving approach is much different than that of other companies. Tesla has maintained that vision is the only thing needed to have a solid and effective self-driving suite. Many self-driving companies utilize things like LiDAR, sensors, and other elements to improve performance, but Elluswamy sent a jab at those who believe it’s needed.
“Historically, the so-called experts have always claimed that you need LiDARs, radars, HD maps, and the entire kitchen sink to drive safely. Here we show that such is not true. You can have safe, comfortable, and affordable autonomy with just cameras. This record should be a huge validation of Tesla’s entire AI approach.”
The feat of accumulating this many miles without any driver behind the wheel is impressive. The thing is, Tesla is also doing this across several different locations, with varying traffic rules, pedestrian levels, weather patterns, and other important factors.
While Tesla is not ready to roll out an unsupervised platform completely, it is a slow but steady indication that the company is well on its way to figuring things out.
The company’s attitude toward expansion is slow, safe, and controlled, and despite this huge milestone, it will still be some time until we see Tesla truly unleash unsupervised rides more aggressively.
SpaceX wants to catch Starship for launch 14, Elon Musk says
Tesla to open source Model S and Model X designs and software
