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 is gearing up for the 13th Starship integrated flight test, which is currently scheduled for Thursday, July 16, with the launch window opening up at 6:30 PM E.T. from Starbase in South Texas.
This mission, the second with the V3 Starship and Super Heavy vehicles, builds directly on the foundation of Flight 12 while introducing ambitious new objectives, including the debut deployment of next-generation Starlink V3 satellites.
The rapid iteration between flights underscores SpaceX’s “fail fast, learn faster” philosophy, with engineers addressing specific anomalies from the previous test to push reusability and payload capabilities further.
Starship’s thirteenth flight test is preparing to launch as early as Thursday, July 16 → https://t.co/Rp7VwBzpWx pic.twitter.com/jdpFlQUEpF
— SpaceX (@SpaceX) July 11, 2026
Flight 12 occurred earlier in 2026 and encountered notable challenges that became catalysts for Flight 13’s improvements. Issues included booster course deviations during the flip maneuver after stage separation, reusability problems with Super Heavy’s Raptor engine relights for the boostback burn, and an engine-out event on the Starship upper stage during its propulsion phase.
These hiccups, while they did not prevent overall mission success, highlighted areas needing refinement for more consistent performance and higher safety margins in future operational flights.
Elon Musk called it Epic: The full story of SpaceX’s Starship Flight 12
In response, SpaceX implemented a comprehensive suite of both hardware and software upgrades.
For the booster, engineers developed a more robust stage separation flip sequence to maintain stable orientation and prevent off-course rotation. Hardware modifications have enhanced Raptor re-light reliability during the boostback burn, complemented by updated engine alarms and abort logic tailored for multi-engine operations. On the Starship side, propulsion system changes directly tackle the Flight 12 engine-out scenario, improving redundancy and operational resilience.
Another major focus of SpaceX for Flight 13 was the advancements in the heat shield. New tile designs and attachment mechanisms, including tests of aft flaps and skirts, aim to boost durability.
Load-sensing tiles will measure real-time stresses during atmospheric entry, while white-painted tiles simulate missing ones as imaging targets. Six of the 20 Starlink V3 satellites carried aboard will feature specialized cameras to scan and transmit heat shield imagery back to ground teams, providing critical data for future return-to-launch-site attempts.
The mission profile also includes a higher dynamic pressure ascent to stress-test the thermal protection system and increase payload potential, alongside a planned in-space Raptor engine relight demonstration.
The V3 Starlink satellites themselves mark a leap forward, equipped with laser links, deployable solar arrays, and improved antennas to expand network capacity and speeds.
The company wrote:
“For the first time, Starship will carry V3 Starlink satellites to space, which aim to greatly expand the network’s capacity and user speeds. As part of this initial test, Starship is planned to deploy 20 satellites which will extend solar arrays and antennas and will attempt to connect with ground stations in South Africa and the larger Starlink constellation via high-capacity lasers. Six of the satellites have been modified with a suite of cameras to scan Starship’s heat shield and transmit imagery down to operators to continue testing methods of analyzing Starship’s heat shield readiness for return to launch site on future missions. Several tiles on Starship have been painted white to simulate missing tiles and serve as imaging targets in the test.”
This dual-purpose flight tests both vehicle reliability and satellite tech in one integrated operation.
These iterative changes, catalyzed by Flight 12’s data, position Starship closer to rapid reusability goals essential for ambitious programs like Artemis lunar missions and global Starlink coverage.
As SpaceX continues its aggressive test cadence, Flight 13 exemplifies how targeted engineering responses to real-flight anomalies accelerate progress toward fully operational, high-cadence launches. Success here could mark another milestone in the Starship program for SpaceX.
Tesla received a price target upgrade just on the heels of what was a crazy successful quarter for its automotive business, as the company reported a delivery beat of over 15 percent for Q2.
Jefferies analysts are upping Tesla’s price target (NASDAQ: TSLA) to $400 from $375, while maintaining their “Hold” rating on shares, and the strong automotive deliveries from Q2 is a big reason. However, there are some other catalysts that Jefferies believes position Tesla for a strong position in the second half of the year.
Strong Deliveries
Tesla reported 480,000 deliveries for Q2, while Wall Street was between 395,000 and 405,000, as an overall consensus. It was an incredibly strong quarter from a delivery perspective, and Tesla sold well more than it produced during the three months.
Tesla crushes Wall Street expectations, beats delivery estimates by over 15 percent
While vehicle deliveries are not necessarily looked at in the light that they used to be, Tesla still maintains a lot of advantages for keeping deliveries strong. With the loss of the $7,500 EV Tax Credit last year, Tesla still maintains a strong demand case for its EVs.
Robotaxi Performance
Tesla has been operating Robotaxi for over a year now, as it launched in Austin in mid-2025. That program has expanded to Houston and Dallas, the San Francisco Bay Area, and, most recently, Miami, Florida, the suite’s first appearance in the Sunshine State.
While the Robotaxi suite is still in its early phases and Tesla is working through things like fleet size and wait times, the company has been able to undercut the pricing of its competitors and has a great safety record.
Merger Speculation with Tesla and SpaceX
This is perhaps the biggest topic that many are speaking about with Tesla and SpaceX, and it is the one thing that seems to be on the mind of every investor.
Jefferies warns that growing talk of a Tesla-SpaceX merger could cause Tesla stock to trade more like a SpaceX proxy, which may disconnect it from underlying automotive fundamentals. SpaceX has a lot going for it, especially its compute deals that have been widely publicized as of late.
Profitability in New Projects Could Take Some Time
Tesla has a few long-term ventures in the pipeline, most notably the Optimus project and Robotaxi, which is launched but will take several years to expand to a meaningful level that resonates with everyday people.
This is something that investors need to be careful of. Tesla’s projects could take some time to round out, so Jefferies advises that these may carry initial losses, rather than immediate profit. Seasoned Tesla investors have echoed something like this for a long time; they knew going in it would not be an open-and-shut strategy. It was going to take time.
These new projects are no different.
News
Tesla readies its autonomous Cybercab and Robotaxi cleaning service
A Texas permit just confirmed Tesla’s cleaning robot is coming to service its Cybercab and Robotaxi fleet.
A routine Texas building permit may have quietly confirmed that Tesla’s robot vacuum and autonomous cleaning bot for the Robotaxi and Cybercab is coming. A state filing with the Texas Department of Licensing and Regulation, as first discovered by Tesla enthusiast Spencer and posted to X, that project number TABS2025022006, lists the scope of work at Tesla’s Austin Robotaxi hub at 5900 E Ben White Blvd to include a “Cleaning Robot” alongside Supercharger cabinets and an Equipment Inspection System.
Tesla first showed the cleaning robot publicly on January 31, 2025, posting a short video on X with the caption “This robot sucks,” showing a large robotic arm inside a Cybercab cabin switching between attachments to vacuum debris, pick up trash, and wipe down surfaces.
The operational case for this hardware comes down to mathematics. A robotaxi running rides across Austin needs to cycle passengers continuously to generate revenue. Every minute a vehicle sits waiting for a human cleaning crew is a minute it is not earning. A robotic arm that can fully clean a Cybercab cabin between rides in under two minutes removes one of the key bottlenecks in fleet utilization that no autonomous vehicle company has yet solved at scale.
This robot sucks pic.twitter.com/VUmGfCM5B3
— Tesla (@Tesla) January 31, 2025
The 5900 E Ben White Blvd address sits roughly 12 miles southwest of Gigafactory Texas, where Tesla has been mass producing its Cybercab. The Ben White facility is expected to functions as Tesla’s Austin Robotaxi Hub, the physical base of operations where fleet vehicles return between rides to charge, get cleaned, and undergo inspection before being dispatched again – and all autonomously. One can imagine a Cybercab dropping off a passenger, routes itself back to Ben White, pulls into the cleaning station, charges on one of the Supercharger cabinets listed in the same permit, passes the equipment inspection system, and returns to service, all without a human making a single decision.
The sighting activity around both locations has accelerated in parallel with production. By mid-March 2026, Cybercabs were spotted regularly on public roads across Austin and Silicon Valley. Tesla’s Robotaxi operations in Texas has expanded to cover the entire Austin metro area and has spread to Dallas, while autonomous Cybercab employee shuttle runs at Gigafactory Texas are also set to begin soon. What it represents is the physical infrastructure behind a fleet that Tesla intends to run without anyone cleaning, driving, or dispatching it by hand.
SpaceX comes with a slew of changes for Starship Flight 13
Tesla gets price target upgrade on heels of crazy successful auto quarter
