Connect with us

News

SpaceX Starship booster survives explosion

Super Heavy Booster 7 appeared to narrowly avoid catastrophe on July 11th, surviving an accidental explosion. (NASASpaceflight Starbase Live)

Published

on

A SpaceX Super Heavy booster was rocked by a substantial explosion and subjected to multiple fires at the launch pad during the rocket’s latest round of testing.

As of 9 pm CDT, July 11th, the fate of the upgraded Super Heavy – known as Booster 7 or B7 – is leaning towards survival but and it won’t be certain until the rocket is drained of all cryogenic propellant and potentially flammable gas and safe for SpaceX employees to approach. The incident began around 4:20 pm CDT, when Super Heavy Booster 7 (or its launch mount) unintentionally ignited a cloud of flammable gas produced during flow test involving most or all of its 33 Raptor engines. In the past, SpaceX has performed “spin prime” tests with Raptors installed on Starship prototypes, flowing high-pressure gas through the engines’ turbines to get them up to operating speeds and pressures. Booster 7’s test ended a bit differently.

When the resulting cloud of well-mixed methane and oxygen gas was accidentally ignited, it functioned like a small fuel-air bomb, rapidly combusting to produce a violent explosion and shockwave. After the initial explosion, the fire also expanded to burn as much of the resulting gas as possible, producing a fireball that briefly reached 80-90 meters (~260-300 ft) in height. CEO Elon Musk – apparently not directly participating in the test – initially stated that the explosion and fire was planned, implying that it was more or less a nominal outcome. Virtually everyone with experience observing Starship testing felt otherwise, however.

To preserve the safety of the few local residents still living at Boca Chica Village, SpaceX is required to issue printed safety warnings well in advance of Starship tests that could create a shockwave capable of shattering glass and injuring locals. SpaceX has never intentionally performed such a test without distributing those warnings and did not distribute a warning before July 11th, all but guaranteeing that no ignition event was planned. A few hours later, Musk deleted his original tweet and posted a different one, confirming that the explosion was “actually not good” and that SpaceX is “assessing the damage.”

For the most part, Booster 7 and the Starbase Orbital Launch Site (OLS) exceeded viewers’ expectations of their sturdiness, exhibiting very little off-nominal behavior after being subjected to a unexpected explosion, shockwave, and fire. Immediately after the event, B7 quickly depressurized its propellant tanks and appeared to leave those vents open, reducing the chances of the booster destroying itself if SpaceX were to lose control. SpaceX also appeared to intentionally avoid using the orbital launch mount’s (OLM) umbilical mechanism to remove propellant from the Super Heavy’s tanks, perhaps concerned that the shockwave might have weakened its connection to B7.

Starship SN4 demonstrates one possible outcome of attempting to use a leaky pad umbilical to detank.

About an hour after the explosion, Booster 7 dumped a large amount of cryogenic liquid out of a new vent located on its aft end, producing a flood that spread around the adjacent pad. It’s unclear if that liquid was nitrogen or oxygen but either way, the emergency propellant dump appeared to cause a fire to start about 100 feet (~30m) from the booster and launch mount. That fire proceeded to burn intermittently for the next two hours, all the while posing a clear and present danger to the rest of the pad and booster if it were to spread in the wrong direction or breach the wrong underground pipe. Instead, SpaceX got lucky and the fire eventually self-extinguished.

In a worst-case scenario, Super Heavy’s engine section and 33 Raptor engines could have been seriously damaged, while the subsequent pad fire(s) could have also significantly damaged crucial pad systems, requiring weeks of repairs. The booster could even be beyond repair. More optimistically, given that SpaceX appears to have gotten lucky enough to avoid a total loss of vehicle, Booster 7 may be fine after some inspections and moderate repairs. The pad damage could also be limited to a single isolated, non-critical piece of equipment catching fire and burning to a crisp

Advertisement
-

Regardless, SpaceX will need to figure out what exactly caused the explosion and make sure that that failure mode does not appear again. In the meantime, the company recently finished stacking Super Heavy Booster 8, and Starship S24 – installed on a nearby suborbital test stand – is ready to begin its own static fire test campaign in the near future.

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

SpaceX just locked up a NASA record no other U.S. spacecraft can touch

SpaceX’s Crew-13 Dragon reached the ISS in under eight hours, and NASA confirmed a record.

Published

on

By

spacex-dragon-axiom-ax-4-mission-iss

SpaceX now owns every spot on the list of the five fastest trips a U.S. spacecraft has ever made to the International Space Station, and its newest entry beat the old mark by more than four hours.

Crew Dragon Grace docked to the forward port of the station’s Harmony module at 7:05 p.m. ET on October 1, just 7 hours and 55 minutes after lifting off from Space Launch Complex 40 at Cape Canaveral. NASA confirmed the milestone in a space station blog update, writing that the flight “marked the fastest launch‑to‑docking of a U.S. spacecraft in the history of the International Space Station.”

The previous U.S. record also belonged to Dragon. SpaceX’s uncrewed CRS-31 cargo mission reached the station in a little over 12 hours in November 2024. The fastest crewed trip before last week was Crew-11, which took 14 hours and 43 minutes in August 2025, according to Space.com.

A post that Elon Musk reposted on Monday filled out the rest of the ranking. Behind Crew-13, CRS-31 and Crew-11 sit Axiom’s Ax-2 mission at 15 hours and 35 minutes and NASA’s Crew-4 at 15 hours and 44 minutes. All five flew on Dragon.

SpaceX turned a heralding moment for Starship into its greatest

Crew-13 carried NASA astronauts Jessica Watkins and Luke Delaney, Canadian Space Agency astronaut Joshua Kutryk, and Roscosmos cosmonaut Sergey Teteryatnikov. NASA had projected a docking around 8 p.m. ET, as Teslarati reported the day before launch, and Dragon arrived nearly an hour early. Our launch day coverage noted that the flight was lined up to be the quickest Crew Dragon transit yet.

The speed came from timing more than hardware. SpaceX’s Julianna Scheiman said the station “was in an opportune spot in space,” which let Dragon start closing the gap almost immediately after reaching orbit. “This is close to the fastest it could be,” she added. Most Crew Dragon flights still take close to a day, using a series of Draco thruster burns to raise and phase their orbit before arrival.

Dragon’s next job at the station is a departure. NASA said Monday it is targeting 8:05 a.m. ET on Wednesday, October 7, for Crew-12 to undock, setting up a splashdown off the coast of California around 11:34 a.m. on Thursday. Clearing that port makes room for CRS-35, a cargo Dragon carrying the final set of iROSA solar arrays.

Dragon remains NASA’s only operational ride to the station while Boeing’s Starliner stays grounded, and the agency recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification.

Continue Reading

Elon Musk

Elon Musk teases TSMC as potential Terafab partner

Published

on

SpaceX Terafab rendering
SpaceX Terafab rendering

Elon Musk has acknowledged that early discussions with Taiwan Semiconductor Manufacturing Company (TSMC) could bring the company into his ambitious Terafab semiconductor project, signaling a possible partnership with the world’s leading contract chipmaker.

Musk confirmed that early talks are underway, but as of right now, they are “just discussions.” There is no confirmation of a deal nor dismissal of the possibility of one, leaving open the prospect of one of the largest advanced-chip collaborations under discussion in the U.S.

The report that speculated on potential discussions between Terafab and TSMC comes from Tim Culpan, who outlined a few ways the collaboration could operate. One is TSMC using the project as an “anchor customer” for future facilities in Texas, potentially contributing process expertise, operational know-how, or capacity while Terafab provides capital, long-term purchase commitments, or both.

Tesla and SpaceX jointly developed the Terafab project, with Intel already participating on the tech side. Elon Musk announced the project in March, and it intends to produce more than one terawatt of AI compute capacity annually once fully built.

Elon Musk’s Terafab project locks up massive new partner

Company statements place the first phase at approximately $16.8 billion in cost, with later filings pointing to a total that could reach well into the tens of billions across multiple stages.

Intel joined the effort in April 2026 and is expected to supply its 14A manufacturing process for the full-scale plant.

Musk has said existing suppliers, including Samsung and TSMC, remain important for near-term needs; Tesla already has production arrangements with Samsung for AI5 and AI6 chips, but that future demand from Optimus robots, Cybercab vehicles, and planned space-based data centers will eventually exceed what the global industry can currently deliver.

Terafab is positioned as the long-term answer to that projected shortfall, and Tesla did something similar during COVID to avoid a chip shortage. This is just a much larger-scale solution.

If the partnership were to materialize, it would add TSMC’s industry-leading strategies to a project that already combines Tesla’s and SpaceX’s capital and offtake with Intel’s process technology. For now, the only public confirmation is Musk’s brief acknowledgement that conversations are occurring.

Continue Reading

News

Tesla reveals early Robotaxi charging strategy, showing scrappy DNA

Published

on

Credit: Tesla

Tesla’s early strategy for charging units operating within its Robotaxi fleet reveals that the company surely has not lost any of that scrappy DNA that took it from an unlikely success story to the most valuable carmaker in the world.

An observer at a Tesla Supercharger in Austin spotted ten total Robotaxi vehicles arrive: one Cybercab and nine Model Y units. A Tesla employee was waiting at the lot and allowed each unit to park itself; every car that arrived had nobody in it.

Tesla wins FCC approval for wireless Cybercab charging system

The Tesla employee would walk around and plug each car in, adjusting the parking if needed:

It’s a very interesting strategy, but extremely understandable at this early point in the Robotaxi program. It’s only been out for about 15 months, and Cybercab just entered the fleet in early September.

On top of that, Tesla is still working tirelessly on its wireless charging apparatus, and a new patent was just published regarding that product last week.

However, this is just another example of how Tesla still has plenty of that scrappy DNA leftover from the “production hell” days, when CEO Elon Musk slept on the floor of the factory, employees were working crazy hours, Tesla was building Sprung Structures to build cars in, and the company was tiptoeing on the brink of bankruptcy.

For now, Tesla is utilizing a simple system for recharging its ride-hailing vehicles, and that is a Tesla employee doing it manually until another solution presents itself. Sure, it’s not the most high-tech thing, and it certainly is not what people might have expected at this point in time, but it works, and it’s keeping the entire suite running.

Continue Reading