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.
Tesla entered two new markets this week by advancing its presence in Latvia (Europe) and officially launching operations in Uruguay (South America), marking a rapid dual-continent expansion.
These moves underscore the company’s strategy to tap into emerging EV markets with supportive policies, renewable energy grids, and growing demand for sustainable transport.
Latvia: Strengthening the Baltic Footprint
In Latvia, Tesla has built on its earlier registration of Tesla Latvia SIA in late 2025 with recent steps toward full operations, including job postings for a service center and representation in Riga. This aligns with broader Baltic expansion following Lithuania’s model of pop-up stores and service centers.
Coming to Latvia https://t.co/XNkQQJ2O6a pic.twitter.com/yS9kpcNky1
— Tesla Europe, Middle East & Africa (@teslaeurope) July 17, 2026
EV penetration in Latvia stands at around 7 percent for BEVs in new passenger car registrations. 2025 data showed 1,602 BEVs out of about 22,500 total, or 7.1 percent, with combined plug-ins nearing 19 percent. Growth has been steady but below the European average, supported by government subsidies and infrastructure development. Tesla models like the Model 3 lead local EV registrations.
Vehicles for the Latvian market will likely be sourced from Gigafactory Berlin or Gigafactory Shanghai. Charging infrastructure is robust for the region as well, with over 400- 2,000 public points, with Tesla Superchargers in Riga, Jūrmala, and along Via Baltica routes offering up to 250 kW.
Uruguay: Third South American Country
Tesla teased its Uruguay arrival with “Estamos llegando,” or, “We are arriving,” on social media, followed by an official presentation scheduled for mid-July.
Hola Uruguay 🇺🇾
Nuestros Model 3 y Model Y están cada vez mas cerca! pic.twitter.com/FR41fsA7um
— Tesla Latinoamérica (@Tesla_LatAm) June 30, 2026
The company established Tesla Uruguay SAS, homologated Model 3 and Model Y (three versions each), and appointed local leadership. This makes Uruguay Tesla’s third official South American market after Chile and Colombia.
Uruguay boasts one of Latin America’s highest EV penetrations, with battery-electric vehicles exceeding 20 percent market share recently, driven by tax incentives, high fuel prices, and a nearly 95-100 percent renewable electricity grid. Hundreds of Teslas already operate via grey imports, but official sales bring warranties, service, and support.
Vehicles will be imported from Gigafactory Shanghai, enabling competitive pricing for Model 3 and Model Y. Charging plans include Supercharger development alongside existing infrastructure, leveraging the country’s green energy advantage for affordable operation.
Tesla Superchargers follow Model 3 and Model Y to South American country
Tesla’s Dual Continent Expansion
Tesla’s simultaneous push into Latvia and Uruguay demonstrates efficient scaling: prioritizing service and infrastructure first, then direct sales in high-potential niches. In Europe, it fills Baltic gaps; in Latin America, it counters Chinese dominance while leveraging renewables.
This dual move signals Tesla’s ambition to accelerate global EV adoption amid varying regional paces. By addressing local needs, like subsidies in Latvia or incentives and green grids in Uruguay, Tesla not only boosts volumes but advances its mission of sustainable energy.
For investors and consumers, it highlights resilience and opportunity in diverse markets, potentially paving the way for further growth in underserved regions. With strong fundamentals in both, these entries could yield long-term gains as EV transitions mature worldwide.
SpaceX has announced a new target date for the thirteenth test flight of Starship: Monday, July 20, with the launch window opening at 6:45 p.m ET/5:45 p.m. CT.
This is the first rescheduling attempt of Starship’s 13th test flight. It was set to launch last night, but SpaceX scrubbed the launch attempt.
🚨 SpaceX is now looking at Monday, July 20th at 6:45 p.m ET/5:45 p.m. CT for the 13th test flight of Starship pic.twitter.com/7s8aMJV5Ge
— TESLARATI (@Teslarati) July 17, 2026
CEO Elon Musk revealed that some of the engines on Starship did not start, which automatically triggers a launch abort. Two of the Raptor engines will be removed and replaced.
To be confident of a good flight, 2 Raptors will be removed & replaced. Most probable launch timing is early next week.
— Elon Musk (@elonmusk) July 17, 2026
SpaceX officially announced the new launch window this morning.
Starship’s 13th test launch comes with a few new objectives, but SpaceX does not plan to attempt a catch of the booster, which it has done several times in the past.
For Starship’s Upper Stage, there are some adjustments to ensure engine reusability that will be assessed during the ascent, and 20 operational Starlink V3 satellites are also set to make their way into space. SpaceX also plans to attempt an in-space relight of a single Raptor engine, which is a critical demonstration for future orbital deorbit, refueling, and deep space maneuvers.
Ultimately, it will splash down in the Indian Ocean.
The continuous tests help SpaceX advance the Starship program toward eventual full reusability, operational Starlink V3 deployment, and future missions, which include NASA’s Artemis program.
Elon Musk
SpaceX Starship Flight 13 aborted at Zero and Musk just told us what broke
Four Raptor engines failed to ignite at T-zero, forcing SpaceX to scrub Starship Flight 13 Thursday.
SpaceX scrubbed the Starship Flight 13 launch attempt Thursday evening at the last possible moment, after four of the Super Heavy booster’s 33 Raptor 3 engines failed to ignite during the startup sequence. The 90-minute window had opened at 6:45 p.m. EDT from Starbase in Boca Chica, Texas, and the countdown had proceeded without issue all day, with more than 11.5 million pounds of liquid methane and liquid oxygen being fully loaded into the rocket before the automated abort triggered. SpaceX’s launch directors posted on X, “Standing down from today’s flight test attempt,” and shut down the livestream shortly after.
Musk confirmed the root cause within hours. “Some of the engines didn’t start, triggering an automatic launch abort,” he wrote on X. “To be confident of a good flight, 2 Raptors will be removed and replaced. Most probable launch timing is early next week.” SpaceX engineers began draining propellant tanks immediately and Booster 20 was rolled back to its hangar for inspection.
The timing adds a layer of significance that did not exist during any of the previous 12 Starship flights. This is the first time SpaceX has attempted to launch Starship since the company made its stock market debut in June, listing under ticker SPCX at $135 per share. Public investors are now watching every Starship outcome in real time, and a last-second abort carries more visibility than it would have six months ago.
Flight 13 was designed to be one of the most consequential tests in the program’s history. It was set to carry 20 Starlink V3 satellites, the first operational payload Starship has ever attempted to deploy. Six of those satellites carried external cameras to photograph Starship’s heat shield from the outside during flight, which would act as a self-inspection approach SpaceX has never attempted before. The mission also needed to complete a Raptor engine relight in space, a step SpaceX skipped on Flight 12 in May after losing an engine during ascent. That Flight 12 booster also flipped 90 degrees off course during its boostback burn when five engines failed to reignite.
SpaceX has not announced an official next launch date. Musk’s “early next week” window points to July 21 or 22 at the earliest, pending the engine swap and a return to the pad.
Tesla enters two new markets on two different continents in one week
SpaceX announces new Starship 13 test flight target date
