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.

Advertisement

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.

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.

Advertisement

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

Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration

Published

on

Credit: CNBC

Tesla has finally clarified the situation regarding the viral crash in Texas where a Model 3 slammed into a home.

CEO Elon Musk replied to reports on Monday that stated the crash was due to the company’s Full Self-Driving or Autopilot suite, which seemed unlikely to those who are familiar with it. Video showed the car slamming into a house at an excessive rate of speed, making it highly unlikely the crash was due to the suite’s operation, as it does not travel at those speeds in residential areas.

Musk said:

“This makes no sense. FSD drives slowly through neighborhood streets, and this was a high-speed crash!”

Tesla’s Head of AI, Ashok Elluswamy, added context, revealing that the company’s data shows the driver “manually overrode self-driving by pressing the accelerator all the way to 100%.”

He revealed the speed reached by the car was 73 MPH, and the accelerator was still pressed “even after the crash.”

Authorities are reportedly investigating “whether Tesla’s Autopilot system played a role after a Model 3 left the roadway…slammed through a brick house at high speed and fatally struck Matha Avila as she sat inside,” the New York Post reported.

The National Highway Traffic Safety Administration (NHTSA) is now investigating the crash. Tesla will work with the agency to provide them with whatever information they need in order to clarify the cause of the crash.

Similarly, Tesla had claims of a fatal accident in Harris County, Texas, a few years ago. Early reports indicated that Full Self-Driving was the cause of the crash. After the National Transportation Safety Board (NTSB) worked with Tesla, the agency proved there was “no use of the Autopilot system at any time during this ownership period of the vehicle, including the time frame up to the last transmitted timestamp on April 17, 2021.”

Tesla alleged “driverless” crash in Texas: What is known so far

“Application of the accelerator pedal was found to be as high as 98.8 percent,” the NTSB said in their findings. The highest recorded speed in the five seconds leading up to the impact was 67 miles per hour. The area where the crash occurred is residential, and Texas State laws have default speed limits of 30 MPH in residential streets.

This appears to be a similar situation. However, an investigation will prove what happened for sure.

Continue Reading

Investor's Corner

SpaceX makes $20 billion move to optimize its balance sheet

Published

on

Credit: SpaceX

SpaceX announced today that it commenced its first-ever public bond offering, marking a significant step in the newly public company’s capital markets strategy.

The company announced an offering of senior unsecured notes expected to raise at least $20 billion.

The move comes just a short time after SpaceX completed one of the largest initial public offerings in history. In mid-June, the company priced shares at $135 and raised more than $85 billion, propelling founder Elon Musk’s net worth past the trillion-dollar mark and giving the firm substantial liquidity.

According to the company’s SEC filing, the net proceeds from the notes will be used primarily to repay in full the outstanding borrowings under its existing bridge loan facility, cover related fees and expenses, and fund general corporate purposes. The offering is being conducted under Rule 144A, as well as Regulation S, targeting qualified institutional buyers and non-U.S. investors. Notes will be unsecured obligations ranking equally with other unsubordinated debt.

The $20 billion bridge loan was used to refinance approximately $17.5 billion in higher-cost “junk” debt tied to X and xAI. SpaceX had merged with xAI in February 2026 in an all-stock deal. The bridge facility, which matures in September 2027, had represented the bulk of SpaceX’s long-term debt.

SpaceX officially acquires xAI, merging rockets with AI expertise

In connection with the bond launch, SpaceX disclosed it held approximately $100.8 billion in cash and cash equivalents as of June 19. Investor calls began on the announcement date, with pricing and launch expected shortly thereafter. Rating agencies have assigned investment-grade ratings to the proposed bonds, reflecting confidence in SpaceX’s dominant position in commercial launches and the growth trajectory of its Starlink internet offering.

The debt raise also allows SpaceX to optimize its balance sheet by replacing short-term, higher-cost bridge financing with longer-date, lower-cost fixed-income securities. This provides greater financial flexibility to support capital-intensive initiatives, including the development of Starship, the expansion of the Starlink constellation, and the integration of AI capabilities following the xAI combination.

SpaceX shares (NASDAQ: SPCX) fell sharply on the news, dropping over 16 percent overall on the market on Monday. The stock had surged initially after debuting but pulled back amid profit-taking and broader market dynamics.

Overall, the bond offering underscores SpaceX’s transition to a mature public company with access to diverse funding sources. It positions the firm to pursue its long-term vision of multiplanetary expansion and AI infrastructure, while maintaining a disciplined approach to its capital structure in a high-growth but capital-heavy industry.

Continue Reading

Elon Musk

SpaceX confirms third massive compute deal at Colossus data center

Published

on

Credit: xAI Memphis

SpaceX confirmed today that it has officially signed its third massive compute deal, providing compute at its Colossus data center in Southaven, Mississippi.

Reflection AI will gain immediate access to NVIDIA GB300 chips at SpaceX’s Colossus 2 data center. In return, Reflection will pay SpaceX $150 million per month starting on July 1, with total payments reaching approximately $6.3 billion if the contract runs through its duration, which is until 2029. Either party can terminate the agreement with 90 days’ notice after the initial three-month period.

CNBC first reported the deal.

This latest partnership highlights SpaceX’s strategy of commercializing its massive Colossus supercomputing infrastructure, originally developed to power Elon Musk’s Grok AI models. The company has rapidly expanded its customer base in the AI sector following its February 2026 merger with xAI, a transaction that valued the combined entity at $1.25 trillion.

SpaceX has previously signed significant compute deals with other major players.

It granted Anthropic exclusive access to the full capacity of its Colossus 1 data center, which exceeds 300 megawatts and includes over 220,000 NVIDIA GPUs. Details from SpaceX’s IPO filings indicate Anthropic will pay $1.25 billion per month through May 2029, potentially generating around $45 billion over the term of the deal.

Additionally, Google agreed to pay SpaceX $920 million per month for compute capacity from October 2026 through June 2029. This 32-month period will provide Google access to roughly 110,000 NVIDIA GPUs, along with supporting processors and memory. Capacity ramps up through September at a reduced fee, with termination options after the first year.

SpaceXA also established arrangements for computing power with Cursor, an AI coding startup. SpaceX acquired them in a $60 billion all-stock deal.

SpaceX makes first acquisition post-IPO

These arrangements position SpaceX’s collective position as an AI infrastructure powerhouse with high-margin revenue potential. The Google deal alone could generate nearly $29.5 billion over its term, while the Reflection contract adds another $6.3 billion.

Combined with the Anthropic arrangement, SpaceX stands to realize tens of billions in revenue from compute leasing in the coming years, which diversifies beyond SpaceX’s traditional rocket launches and Starlink operation.

The deals underscore growing demand for advanced AI training and inference capacity amid chip shortages and surging model development needs. Reflection, valued at $25 billion and focused on “American open intelligence” with government and national security ties, cited recent restrictions on closed models as validation for open-source approaches.

For SpaceX, the partnerships transform capital-intensive data centers into flexible revenue sources while supporting its broader AI ambitions after the company has gone public.

Continue Reading