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.

Advertisement

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

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

Tesla to open source Model S and Model X designs and software

Published

on

Credit: Tesla

In a move echoing its earlier commitment to open innovation, Tesla CEO Elon Musk announced recently that the company plans to make the design and software of its Model S and Model X fully open source.

This follows the same approach Tesla took with its original Roadster, releasing all available design, engineering, and diagnostic materials in November 2023 so that “whatever we have, you now have.”

The Model S, introduced in 2012, was Tesla’s first mass-produced vehicle and a groundbreaking luxury electric sedan. It offered impressive range, rapid acceleration, and over-the-air software updates that redefined expectations for electric cars.

The Model X, launched in 2015, built on that foundation as a high-performance electric SUV notable for its distinctive falcon-wing doors, spacious interior, and advanced safety features. Both models served as flagships that helped establish Tesla as a leader in the EV industry and popularized long-range battery-electric vehicles.

Production of the Model S and Model X was wound down earlier in 2026, with manufacturing ending in the second quarter. Tesla redirected the Fremont factory space previously used for these vehicles toward higher-priority projects, including Optimus humanoid robots and the Cybercab autonomous vehicle.

By the time of Musk’s open-source announcement, custom orders had closed and only remaining inventory was available.

Open-sourcing the designs and software offers several clear advantages. Owners of these aging but still capable vehicles gain better access to technical documentation, diagnostic tools, and software resources, making independent repairs and modifications easier and more affordable.

Independent repair shops and third-party specialists can support the large existing fleet without relying solely on Tesla’s service network. Enthusiasts and engineers can study real-world implementations of Tesla’s battery, powertrain, and software systems, potentially accelerating broader industry progress in electric mobility.

The step aligns with Tesla’s 2014 patent pledge and its overall mission to advance sustainable transport by sharing hard-won knowledge rather than locking it behind proprietary walls.

By releasing these materials now that the models have left production, Tesla ensures continued support for its early adopters while freeing internal resources for future technologies. The open-source release of the original Roadster already enabled simulations, community projects, and deeper technical understanding.

Extending that practice to the Model S and Model X should deliver similar benefits on a larger scale, helping keep these influential vehicles relevant and repairable for years to come

Continue Reading

News

Tesla flexes incredible Robotaxi metric that skeptics will hate

Published

on

Credit: Tesla

Tesla flexed one incredible Robotaxi metric during the Q2 Earnings Call that skeptics have to hate to hear. The company’s platform has already driven more than 380,000 miles of unsupervised ride-hailing across several states with no notable incidents.

During the company’s Q2 Earnings Call on Wednesday, Vice President of AI, Ashok Elluswamy, said:

“First of all, I’d like to state that the Robotaxi program has been operating extremely well. Especially in terms of safety, the program has had an impeccable safety record. We have driven more than 380,000 miles of unsupervised Robotaxi, now across six cities in two different states. We have had zero notable incidents. Any reports have been of other actors impacting us when we were stationary. I like to emphasize how safe the operation has been so far. Zero notable incidents over 380,000 miles.”

Elluswamy’s claim over Robotaxi miles is a significant milestone for Tesla in the grand scheme, especially considering this is a sizeable number of miles without any incident.

Tesla’s self-driving approach is much different than that of other companies. Tesla has maintained that vision is the only thing needed to have a solid and effective self-driving suite. Many self-driving companies utilize things like LiDAR, sensors, and other elements to improve performance, but Elluswamy sent a jab at those who believe it’s needed.

“Historically, the so-called experts have always claimed that you need LiDARs, radars, HD maps, and the entire kitchen sink to drive safely. Here we show that such is not true. You can have safe, comfortable, and affordable autonomy with just cameras. This record should be a huge validation of Tesla’s entire AI approach.”

The feat of accumulating this many miles without any driver behind the wheel is impressive. The thing is, Tesla is also doing this across several different locations, with varying traffic rules, pedestrian levels, weather patterns, and other important factors.

While Tesla is not ready to roll out an unsupervised platform completely, it is a slow but steady indication that the company is well on its way to figuring things out.

The company’s attitude toward expansion is slow, safe, and controlled, and despite this huge milestone, it will still be some time until we see Tesla truly unleash unsupervised rides more aggressively.

Continue Reading

Elon Musk

SpaceX Starship just nailed something it’s never done before

SpaceX’s Starship flew successfully Friday, landing both stages and deploying its first Starlink V3 satellites.

Published

on

By

Starship’s thirteenth test flight delivered exactly what SpaceX needed with a clean liftoff, two successful stage recoveries, and the first real payload the vehicle has ever carried to space. Booster 20 and Ship 40 lifted off at 5:51 p.m. CT from Starbase, and by the time the mission wrapped roughly an hour later, both halves of the rocket had done exactly what they were supposed to do.

Booster 20 separated from Ship 40 a few minutes into the flight and stuck a controlled splashdown in the Gulf of Mexico about six minutes after liftoff. That is a meaningful turnaround from Flight 12 in May, when the booster lost several engines during its boostback burn before a hard water landing attempt.


Starship 40’s performance was arguably the bigger win. The vehicle deployed the first 20 operational Starlink V3 satellites Starship has ever carried, then flew a suborbital arc to a landing in the Indian Ocean that SpaceX commentator Dan Huot called the company’s softest splashdown yet. “This is a dream scenario for this team that’s trying to get this heat shield data,” Huot said on the live broadcast, according to Space.com’s live coverage. “I’m a little over the moon right now. Wow. Lucky number 13.”

Unlike the mass simulators SpaceX flew on Flight 12, these were production Starlink V3 satellites, meant to extend solar arrays and antennas and attempt to link with the broader constellation before reentering minutes later. Getting real hardware through a full deploy sequence on only the second flight of the V3 generation keeps Starship on schedule for the payload work NASA is counting on for future Artemis lunar landings.

— TESLARATI (@Teslarati) July 25, 2026

The flight also arrives at a moment when SpaceX needed a win. SPCX has traded below its $135 IPO price since mid-July, as Teslarati reported when the mission slipped to Friday, and short interest has climbed to roughly a third of the tradable float. A clean flight will not fix a balance sheet, but it does answer the one question SpaceX absolutely needed answered this week: whether the fixes made after the July 16 abort would hold up under real flight conditions. They did, on both stages, on the first try after the redesign.

SpaceX has not set a target date for Flight 14, though the company has said it wants to push toward an orbital attempt on the next mission. After Friday, that goal looks a lot more within reach.

Continue Reading