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

Elon Musk

OpenAI cites distrust of SpaceX in decision to drop Cursor partnership

OpenAI will cut SpaceX-owned Cursor’s model access in November, citing Musk’s history of broken contracts.

Published

on

By

OpenAI, the company behind ChatGPT, announced late Friday that it is ending its partnership with Cursor, cutting off the coding tool’s access to its models on November 12. The move comes two weeks after SpaceX completed its $60 billion acquisition of Cursor’s parent company, Anysphere, folding the popular AI coding assistant into Elon Musk’s growing SpaceXAI division.

In a post on its website, OpenAI said the decision came down to trust, not technology. “We cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk’s companies violating contracts,” the company wrote. OpenAI pointed to two specific incidents: X, now part of SpaceX, allegedly breaking the terms of an existing OpenAI contract after Musk bought Twitter.

That lawsuit is the backdrop for all of this. Musk cofounded OpenAI in 2015, left the board in 2018, and sued Sam Altman and Greg Brockman in 2024, arguing they abandoned the company’s nonprofit mission for profit. A federal jury sided with OpenAI in May, finding Musk waited too long to sue rather than ruling on the merits of his claims. Musk said at the time he would appeal to the Ninth Circuit, calling the outcome a “calendar technicality” rather than a real judgment.

Elon Musk breaks silence on OpenAI trial decision

SpaceX’s interest in Cursor predates that verdict by weeks. The company first struck a deal with Cursor in April, securing an option to acquire it for $60 billion or pay $10 billion for joint development work instead. As Teslarati reported at the time, the logic was straightforward: Cursor was paying retail prices to Anthropic and OpenAI, two of its most direct competitors, every time a developer used its product, while SpaceX had idle capacity on its Colossus supercomputer, roughly the equivalent of a million Nvidia H100 GPUs, that Cursor could use to train its own models instead. SpaceX exercised the option in June, days after its own IPO, and the deal closed in mid-August.

Once it closed, Musk moved fast. On an all-hands call with more than 1,000 Cursor employees, he reportedly told staff that SpaceXAI’s Grok was playing catchup in the AI race, unlike Tesla and SpaceX in their own markets, and singled out Anthropic as the company to catch. Cursor CEO Michael Truell now reports directly to Musk inside SpaceXAI.

Elon Musk admits he was ‘clearly wrong’ about Anthropic

Losing OpenAI’s models leaves Cursor leaning harder on Anthropic’s Claude, which has its own compute agreement with SpaceX, and on Cursor’s in-house Composer model, the one SpaceX’s compute was supposed to accelerate in the first place. OpenAI framed the November deadline as maximum notice under its contract, and said it wants to “go above and beyond” to help developers through the transition. Whether Anthropic makes the same call is now the open question in AI coding.

Continue Reading

News

Tesla Theater might be getting plenty more streaming platforms

Published

on

Credit: YouTube/Tesla Theater

The in-car Tesla Theater is among the most unique features available within the cars. When charging, parked, camping, or just hanging out, vehicle occupants can access a variety of streaming platforms on the large center screen, helping keep them entertained during downtime.

However, the Theater might be getting plenty more streaming platforms, something that owners have requested for some time.

Tesla owners recently discovered that visiting Apple TV in the vehicle browser can launch a fullscreen interface that looks and behaves like a dedicated application rather than an ordinary webpage:

The experience drops the usual address bar and browser chrome, presenting catalogs, continue watching rows, and playback controls in the same window Tesla Theater already uses for its listed services. Independent testers soon found similar treatment for HBO Max, Paramount+, Peacock, Disney+, and Prime Video when those sites are opened from the car browser.

This shift is a plausible early signal that Tesla is widening Theater support without a formal software note. Theater has long been a set of web views rather than native applications, so recognizing extra domains and stripping the browser frame is a small server-side change that can expand the catalog quickly.

Owners still lack permanent Theater icons for the newly recognized services, and video remains limited to Park, yet the smoother launch is a meaningful step toward a broader lounge while charging.

Tesla Theater arrived with software version 10 in September 2019. The first video services were Netflix, YouTube, and Hulu, available only while parked and originally tied to WiFi. Spotify arrived in the same era as music rather than Theater video. Disney+ joined officially in July 2021 with the 2021.24 update, giving owners another major catalog on the center screen. Twitch and TikTok later appeared among the default Theater tiles, and Tesla Tutorials remained a persistent educational tile.

Not every addition stayed put. In December 2023, a Holiday software build removed the Disney+ tile for many United States owners after a public dispute involving advertising on X. Hulu stayed visible even though Disney owned it. Visiting disneyplus.com in the browser often restored the tile, which suggested the removal was a recognition list change rather than a complete block. Owners have also reported occasional blank Theater grids after updates, usually fixed by language toggles, resets, or later firmware.

Tesla axes Disney+ from vehicles with Musk-Iger rivalry, but there’s a workaround

Code archives from 2024 listed many unused source names, including Apple TV and Prime Video, that never became official icons, which now looks like groundwork for the current fullscreen browser behavior.

Now that this hint toward an expanded Theater experience has been recognized, Tesla could follow through with these additional shortcuts as a sign that more streaming platforms are available in Teslas than ever before.

Continue Reading

News

Tesla Semi’s biggest adoptee gives an update on production timeline

Published

on

Credit: Tesla

Tesla recently received its largest order for the all-electric Semi from Einride, a Swedish transport service, for 500 units, a groundbreaking invoice to receive before the first deliveries begin.

Even more remarkable, Einride CEO Roozbeh Charli said in a recent interview that he expects his company to take delivery of all 500 — the entire order — before the end of 2027. He even expects to have 75 Tesla Semi units in the Einride fleet before the end of this year.

Charli said the Tesla partnership was part of a broader push, along with its earlier partnership with Amazon. Einride is assisting Amazon with the use of its Saga AI platform, which helps eliminate questions about budgeting and forecasting for logistics companies.

The Semi, as well as Tesla’s production and subsequent delivery of the units to Einride, will help the company “to have a good supply of vehicles that we can deploy on the [Saga AI] platform,” Charli said. “Tesla is also a relationship we’ve had for a while, and as the Tesla Semi deliveries are firming up, we decided to do a larger commitment to that and deploy that on our platform.”

In its initial announcement, Einride said it anticipated taking delivery of the trucks over the next two years, but now it appears the company is expecting all 500 units within the next 16 months.

Tesla Semi gets its largest order yet

Built at a dedicated factory in Sparks, Nevada, the Tesla Semi has been perhaps the biggest and most intensive testing process the company has ever had for a single vehicle model. For the past several years, Tesla has been working with many companies, most notably Frito-Lay and PepsiCo, to gain knowledge on the performance on regional routes.

Tesla plans to launch the Semi officially on September 24, five months after production started ramping.

Additionally, drivers have said they are happy about the Semi’s performance and that its numerous safety and productivity features have made their jobs and routes much easier.

Continue Reading