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.
Elon Musk
Elon Musk reiterates Tesla Optimus’ most sci-fi potential yet
Musk shared his comments in a series of posts on social media platform X.
Elon Musk recently reiterated one of the most ambitious forecasts for Tesla’s humanoid robot, Optimus, stating it could become the first real-world example of a Von Neumann machine. He also noted once more that Optimus would be Tesla’s biggest product.
Musk shared his comments in a series of posts on social media platform X.
Optimus as a von Neumann machine
In response to a post on X that pondered on sci-fi timelines becoming real, Musk wrote that “Optimus will be the first Von Neumann machine, capable of building civilization by itself on any viable planet.” In a separate post, Musk wrote that Optimus will be Tesla’s “biggest product ever,” a phrase he has used in the past to describe the humanoid robot’s importance to the electric vehicle maker.
A Von Neumann machine is a class of theoretical self-replicating systems originally proposed in the mid-20th century by the mathematician John von Neumann. In his concept, von Neumann described machines that could travel to other worlds, use local materials to create copies of themselves, and carry out large-scale tasks without outside intervention.
Elon Musk’s broader plans
Considering Musk’s comments, it appears that Optimus would eventually be capable of performing complex work autonomously in environments beyond Earth. If Optimus could achieve such a feat, it could very well unlock humanity’s capability to explore locations beyond Earth. The idea of space exploration becomes more than feasible.
Elon Musk has discussed space-based AI compute, large-scale robotic production, and the role of SpaceX’s Starship in transporting hardware and materials to other planets. While Musk did not detail how Optimus would fit with SpaceX’s exploration activities, his Von Neumann machine comments suggest he is looking at Tesla’s robotics as part of a potential interplanetary ecosystem.
News
Tesla China January wholesale sales rise 9% year-on-year
Tesla reported January wholesale sales of 69,129 China-made vehicles, as per data released by the China Passenger Car Association.
Tesla China reported January wholesale sales of 69,129 Giga Shanghai-made vehicles, as per data released by the China Passenger Car Association (CPCA). The figure includes both domestic sales and exports from Gigafactory Shanghai.
The total represented a 9.32% increase from January last year but a 28.86% decline from December’s 97,171 units.
China EV market trends
The CPCA estimated that China’s passenger new energy vehicle wholesale volume reached about 900,000 units in January, up 1% year-on-year but down 42% from December. Demand has been pressured by the start-of-year slow season, a 5% additional purchase tax cost, and uncertainty around the transition of vehicle trade-in subsidies, as noted in a report from CNEV Post.
Market leader BYD sold 210,051 NEVs in January, down 30.11% year-on-year and 50.04% month-on-month, as per data released on February 1. Tesla China’s year-over-year growth then is quite interesting, as the company’s vehicles seem to be selling very well despite headwinds in the market.
Tesla China’s strategies
To counter weaker seasonal demand, Tesla China launched a low-interest financing program on January 6, offering up to seven-year terms on select produced vehicles. The move marked the first time an automaker offered financing of that length in the Chinese market.
Several rivals, including Xiaomi, Li Auto, XPeng, and NIO, later introduced similar incentives. Tesla China then further increased promotions on January 26 by reinstating insurance subsidies for the Model 3 sedan. The CPCA is expected to release Tesla’s China retail sales and export breakdown later this month.
News
Tesla’s Apple CarPlay ambitions are not dead, they’re still in the works
For what it’s worth, as a Tesla owner, I don’t particularly see the need for CarPlay, as I have found the in-car system that the company has developed to be superior. However, many people are in love with CarPlay simply because, when it’s in a car that is capable, it is really great.
Tesla’s Apple CarPlay ambitions appeared to be dead in the water after a large amount of speculation late last year that the company would add the user interface seemed to cool down after several weeks of reports.
However, it appears that CarPlay might make its way to Tesla vehicles after all, as a recent report seems to indicate that it is still being worked on by software teams for the company.
The real question is whether it is truly needed or if it is just a want by so many owners that Tesla is listening and deciding to proceed with its development.
Back in November, Bloomberg reported that Tesla was in the process of testing Apple CarPlay within its vehicles, which was a major development considering the company had resisted adopting UIs outside of its own for many years.
Nearly one-third of car buyers considered the lack of CarPlay as a deal-breaker when buying their cars, a study from McKinsey & Co. outlined. This could be a driving decision in Tesla’s inability to abandon the development of CarPlay in its vehicles, especially as it lost a major advantage that appealed to consumers last year: the $7,500 EV tax credit.
Tesla owners propose interesting theory about Apple CarPlay and EV tax credit
Although we saw little to no movement on it since the November speculation, Tesla is now reportedly in the process of still developing the user interface. Mark Gurman, a Bloomberg writer with a weekly newsletter, stated that CarPlay is “still in the works” at Tesla and that more concrete information will be available “soon” regarding its development.
While Tesla already has a very capable and widely accepted user interface, CarPlay would still be an advantage, considering many people have used it in their vehicles for years. Just like smartphones, many people get comfortable with an operating system or style and are resistant to using a new one. This could be a big reason for Tesla attempting to get it in their own cars.
Tesla gets updated “Apple CarPlay” hack that can work on new models
For what it’s worth, as a Tesla owner, I don’t particularly see the need for CarPlay, as I have found the in-car system that the company has developed to be superior. However, many people are in love with CarPlay simply because, when it’s in a car that is capable, it is really great.
It holds one distinct advantage over Tesla’s UI in my opinion, and that’s the ability to read and respond to text messages, which is something that is available within a Tesla, but is not as user-friendly.
With that being said, I would still give CarPlay a shot in my Tesla. I didn’t particularly enjoy it in my Bronco Sport, but that was because Ford’s software was a bit laggy with it. If it were as smooth as Tesla’s UI, which I think it would be, it could be a really great addition to the vehicle.