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.

Advertisement
-->

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.

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.

Advertisement
-->

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.

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 tinkering with Speed Profiles on FSD v14.2.1 has gone too far

Published

on

Credit: Tesla

Tesla recently released Full Self-Driving (FSD) v14.2.1, its latest version, but the tinkering with Speed Profiles has perhaps gone too far.

We try to keep it as real as possible with Full Self-Driving operation, and we are well aware that with the new versions, some things get better, but others get worse. It is all part of the process with FSD, and refinements are usually available within a week or so.

However, the latest v14.2.1 update has brought out some major complaints with Speed Profiles, at least on my end. It seems the adjustments have gone a tad too far, and there is a sizeable gap between Profiles that are next to one another.

The gap is so large that changing between them presents a bit of an unwelcome and drastic reduction in speed, which is perhaps a tad too fast for my liking. Additionally, Speed Profiles seem to have a set Speed Limit offset, which makes it less functional in live traffic situations.

Before I go any further, I’d like to remind everyone reading this that what I am about to write is purely my opinion; it is not right or wrong, or how everyone might feel. I am well aware that driving behaviors are widely subjective; what is acceptable to one might be unacceptable to another.

Speed Profiles are ‘Set’ to a Speed

From what I’ve experienced on v14.2.1, Tesla has chosen to go with somewhat of a preset max speed for each Speed Profile. With ‘Hurry,’ it appears to be 10 MPH over the speed limit, and it will not go even a single MPH faster than that. In a 55 MPH zone, it will only travel 65 MPH. Meanwhile, ‘Standard’ seems to be fixed at between 4-5 MPH over.

This is sort of a tough thing to have fixed, in my opinion. The speed at which the car travels should not be fixed; it should be more dependent on how traffic around it is traveling.

It almost seems as if the Speed Profile chosen should be more of a Behavior Profile. Standard should perform passes only to traffic that is slower than the traffic. If traffic is traveling at 75 MPH in a 65 MPH zone, the car should travel at 75 MPH. It should pass traffic that travels slower than this.

Hurry should be more willing to overtake cars, travel more than 10 MPH over the limit, and act as if someone is in a hurry to get somewhere, hence the name. Setting strict limits on how fast it will travel seems to be a real damper on its capabilities. It did much better in previous versions.

Some Speed Profiles are Too Distant from Others

This is specifically about Hurry and Mad Max, which are neighbors in the Speed Profiles menu. Hurry will only go 10 MPH over the limit, but Mad Max will travel similarly to traffic around it. I’ve seen some people say Mad Max is too slow, but I have not had that opinion when using it.

In a 55 MPH zone during Black Friday and Small Business Saturday, it is not unusual for traffic around me to travel in the low to mid-80s. Mad Max was very suitable for some traffic situations yesterday, especially as cars were traveling very fast. However, sometimes it required me to “gear down” into Hurry, especially as, at times, it would try to pass slower traffic in the right lane, a move I’m not super fond of.

We had some readers also mention this to us:

After switching from Mad Max to Hurry, there is a very abrupt drop in speed. It is not violent by any means, but it does shift your body forward, and it seems as if it is a tad drastic and could be refined further.

Continue Reading

News

Tesla’s most affordable car is coming to the Netherlands

The trim is expected to launch at €36,990, making it the most affordable Model 3 the Dutch market has seen in years.

Published

on

Tesla is preparing to introduce the Model 3 Standard to the Netherlands this December, as per information obtained by AutoWeek. The trim is expected to launch at €36,990, making it the most affordable Model 3 the Dutch market has seen in years. 

While Tesla has not formally confirmed the vehicle’s arrival, pricing reportedly comes from a reliable source, the publication noted.

Model 3 Standard lands in NL

The U.S. version of the Model 3 Standard provides a clear preview of what Dutch buyers can expect, such as a no-frills configuration that maintains the recognizable Model 3 look without stripping the car down to a bare interior. The panoramic glass roof is still there, the exterior design is unchanged, and Tesla’s central touchscreen-driven cabin layout stays intact.

Cost reductions come from targeted equipment cuts. The American variant uses fewer speakers, lacks ventilated front seats and heated rear seats, and swaps premium materials for cloth and textile-heavy surfaces. Performance is modest compared with the Premium models, with a 0–100 km/h sprint of about six seconds and an estimated WLTP range near 550 kilometers. 

Despite the smaller battery and simpler suspension, the Standard maintains the long-distance capability drivers have come to expect in a Tesla.

Advertisement
-->

Pricing strategy aligns with Dutch EV demand and taxation shifts

At €36,990, the Model 3 Standard fits neatly into Tesla’s ongoing lineup reshuffle. The current Model 3 RWD has crept toward €42,000, creating space for a more competitive entry-level option, and positioning the new Model 3 Standard comfortably below the €39,990 Model Y Standard.

The timing aligns with rising Dutch demand for affordable EVs as subsidies like SEPP fade and tax advantages for electric cars continue to wind down, EVUpdate noted. Buyers seeking a no-frills EV with solid range are then likely to see the new trim as a compelling alternative.

With the U.S. variant long established and the Model Y Standard already available in the Netherlands, the appearance of an entry-level Model 3 in the Dutch configurator seems like a logical next step.

Continue Reading

News

Tesla Model Y is still China’s best-selling premium EV through October

The premium-priced SUV outpaced rivals despite a competitive field, while the Model 3 also secured an impressive position.

Published

on

Credit: Grok Imagine

The Tesla Model Y led China’s top-selling pure electric vehicles in the 200,000–300,000 RMB segment through October 2025, as per Yiche data compiled from China Passenger Car Association (CPCA) figures.

The premium-priced SUV outpaced rivals despite a competitive field, while the Model 3 also secured an impressive position.

The Model Y is still unrivaled

The Model Y’s dominance shines in Yiche’s October report, topping the chart for vehicles priced between 200,000 and 300,000 RMB. With 312,331 units retailed from January through October, the all-electric crossover was China’s best-selling EV in the 200,000–300,000 RMB segment.

The Xiaomi SU7 is a strong challenger at No. 2 with 234,521 units, followed by the Tesla Model 3, which achieved 146,379 retail sales through October. The Model Y’s potentially biggest rival, the Xiaomi YU7, is currently at No. 4 with 80,855 retail units sold.

Efficiency kings

The Model 3 and Model Y recently claimed the top two spots in Autohome’s latest real-world energy-consumption test, outperforming a broad field of Chinese-market EVs under identical 120 km/h cruising conditions with 375 kg payload and fixed 24 °C cabin temperature. The Model 3 achieved 20.8 kWh/100 km while the Model Y recorded 21.8 kWh/100 km, reaffirming Tesla’s efficiency lead.

The results drew immediate attention from Xiaomi CEO Lei Jun, who publicly recognized Tesla’s advantage while pledging continued refinement for his brand’s lineup.

Advertisement
-->

“The Xiaomi SU7’s energy consumption performance is also very good; you can take a closer look. The fact that its test results are weaker than Tesla’s is partly due to objective reasons: the Xiaomi SU7 is a C-segment car, larger and with higher specifications, making it heavier and naturally increasing energy consumption. Of course, we will continue to learn from Tesla and further optimize its energy consumption performance!” Lei Jun wrote in a post on Weibo.

Continue Reading