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

Energy

Tesla Model 3 and Model Y can now do what only Cybertruck could

Tesla Model 3 and Model Y can power your home with Powerwall 3 during outages.

Published

on

By

Tesla has turned its two top sellers into backup batteries for the house.

Tesla Energy announced on Tuesday that Powershare Home Backup is now available for new Model 3 and Model Y vehicles paired with a Powerwall 3, saying the car can “extend your home backup by over 2 days.” Minutes later, Tesla’s main account quoted the post with a broader pitch: “With Powerwall 3, every Tesla can now serve as your home’s backup battery.”

Until this week, the Cybertruck was the only Tesla that could send power back into a home, and that capability only began working alongside Powerwall 3 last month, after years of ambitious targets.

Tesla’s updated Powershare page says every Model 3 and Model Y ordered in the U.S. or Puerto Rico on or after October 1, 2026 can use the feature. Some, but not all, earlier cars also qualify. Owners can check on the touchscreen under Software, then Additional Vehicle Information, where a capable car shows “Powershare Support: Enabled.” As Electrek reported, bidirectional power on the two cars runs through an inverter Tesla calls PCS2 Lite, and the company has not said when that part entered production on each trim.

The home side is simpler. A house that already has a Powerwall 3 and either a Wall Connector 3 or Universal Wall Connector needs no additional equipment, and Tesla says compatibility is enabled through a software update. When the grid drops, the Powerwall and the car work together, with up to 11.52 kW of continuous power available. Tesla’s “over two days” estimate assumes a home using 30 kWh per day and a car starting at a 90 percent charge. Standard trims are rated for up to two days, while the Cybertruck adds more than three.

There are limits. Powerwall 2 and Powerwall+ support is listed as “coming soon.” Model S and Model X are not included, and Grid Support, the program that lets Cybertruck owners in Texas send power back to the grid during demand spikes for bill credits, is not available for Model 3 or Model Y.

The rollout also lines up with something Elon Musk said more than three years ago. At Tesla’s March 2023 Investor Day, Musk said, “I don’t think very many people are going to want to use bidirectional charging, unless you have a Powerwall.” Tesla has now shipped the feature for its volume cars with exactly that requirement attached.

The Powerwall pairing was the hard part on Cybertruck. Tesla told owners in December 2025 that Powershare with Powerwall had been pushed to mid 2026, and lead engineer Wes Morrill explained that two devices capable of forming a home’s grid have to negotiate which one leads during an outage, across multiple generations of hardware. With that work done for the truck, Tesla was able to extend it to the Model 3 and Model Y within a month.

Ford and GM have offered home backup from their EVs for several years, but both require a separate inverter and backup hardware. Tesla’s version leans on equipment many Powerwall 3 owners already have on the wall. Powershare for the two cars also ships as part of software update 2026.38.3, the same release that began delivering Halloween Mode on Tuesday.

Continue Reading

News

Tesla ships ‘spooky’ Halloween Mode with creepy and fun features

Published

on

Credit: Tesla

Tesla is now starting to ship a “Halloween Mode” that is filled with some creepy and fun features; the company says, “This spooky update turns your Tesla into a haunted house on wheels.”

The update is just the latest in a series of updates that Tesla typically ships out in a seasonal fashion. The Spring and Summer Updates provided some fun novelty items while also packing some cool features that are actually useful for the ownership experience.

This one seems to be more fun-forward, and there are not any updates to the Full Self-Driving suite or overall operation of the vehicle. Instead, these novelty features are geared toward getting you in the mood for the Fall and Halloween.

New Ghost Costume on Car Avatar

Driver Visualization will now show your vehicle as a ghost, as an all-white sheet is draped over the vehicle. Pedestrians are turned into mummies or skeletons, and other vehicles are all a spooky green:

Credit: Tesla

Additionally, the Park Scene with your Tesla now displays that ghost costume draped over your vehicle in the foreground of a scary backdrop with Jack-o-Lanterns and a haunted house:

Credit: Tesla

Trick or Treat Mode

Trick or Treat Mode will enable the vehicle to play spooky sounds and flicker the lights as visitors approach. This might be a nice touch for when you’re handing out candy to kids on Halloween Night.

Other Features

Tesla is also adding a new Light Show, new Wrap Options, and a new Lock Sound with this update.

Credit: Tesla

Additionally, Photobooth has a new Halloween option:

Credit: Tesla

You will also be able to speak remotely through the app and transmit your voice to people outside, which is not a new feature, but the car will say it in a voice of its own, which is a new feature with that bullhorn-like feature.

Continue Reading

Investor's Corner

SpaceX reveals how its 1 Million AI satellite network will work and prevent space collisions

SpaceX reveals plans for one million Starmind AI satellites and calls out operators hiding maneuvers.

Published

on

By

Concept rendering of SpaceX Starmind constellation via Grok
Concept rendering of SpaceX Starmind constellation via Grok

SpaceX has put the largest satellite count it has ever published into writing, and it says that plan only works if every other operator in orbit starts sharing what it knows.

In a new Space Safety page highlighted Tuesday morning by Sawyer Merritt on X, SpaceX said it “plans to operate up to 100,000 Starlink satellites and up to 1 million Starmind AI satellites to meet the growing demand for broadband and supercompute.” Starlink has a little over 11,000 satellites in orbit today, so the target alone implies roughly a ninefold expansion of the broadband network.

Starmind is SpaceX’s orbital AI compute constellation. Elon Musk confirmed the Starmind name in June after an xAI trademark filing surfaced, and in August SpaceX said it was working with Nvidia on the compute payload. The FCC accepted the filing for up to one million satellites back in February.

FCC accepts SpaceX filing for 1 million orbital data center plan

SpaceX also released a new render of what a full Starmind constellation could look like. Alongside it, SpaceX VP Michael Nicolls explained why the satellites will not operate on their own. “We need to operate clusters of satellites in tight formation to get enough coherent compute to run AI models efficiently,” Nicolls said. “A cluster will be 10-ish satellites connected with 10 terabits or so of bandwidth between them, and interconnected to the broader constellation.”

That is the most specific detail SpaceX has given on how Starmind will be built. Instead of a million independent servers, the network would work as tightly packed groups of about 10 satellites acting as one compute unit, with Starlink’s laser links carrying results back to Earth.


Packing satellites that close together, at that scale, makes collision avoidance the central problem, and most of the Space Safety page is aimed at other operators. SpaceX said Starlink encountered collision risks with about 650 unique maneuvering third party satellites in 2026, and only about half of them shared data. Over six months, Starlink recorded roughly 164,000 more collision risks where the closest approach came within four hours of an unannounced maneuver.

Some operators keep maneuver plans private over proprietary concerns, while others cannot get government permission to share them. SpaceX called those policies “counterproductive,” saying they “largely only serve to create preventable collision risk between satellites.” Starlink is also offering a free ephemeris sharing and screening platform that returns risk results within a minute, backed by its Stargaze network of 30,000 optical sensors.

The push comes as the Starmind application draws opposition from astronomers and environmental groups. In a September filing with the FCC, SpaceX said each Starmind satellite could weigh up to 4,000 kg, nearly seven times the mass of a Starlink V2 Mini. Musk has brushed off crowding concerns before, telling viewers in June that “space is enormous” and that SpaceX already knows how to run very large constellations safely.

SpaceX’s Starmind page says its Gigasat factory in Bastrop, Texas, is designed to produce AI satellites at scale, with deployment of thousands of units starting as soon as late 2027.

Continue Reading