Connect with us

News

SpaceX’s Starship explosion explained by Elon Musk

The burning wreckage of Starship SN4, May 29th. (SPadre)

Published

on

Shortly after a briefing following SpaceX’s flawless astronaut launch debut, CEO Elon Musk casually revealed the best explanation yet for why a Starship prototype violently exploded during testing on May 29th.

On that fated Saturday, SpaceX successfully completed the fifth static fire of a Raptor engine installed on a full-scale Starship prototype, preceded by about an hour and a half of vehicle checks and propellant loading. Unfortunately, around a minute after Raptor shut down, what was quickly identified as liquid methane began spurting out of a specific section at the base of Starship, rapidly creating a massive cloud as the cryogenic propellant boiled and turned into gas. The specific source is unclear but moments later, something under Starship SN4 provided the shock or spark needed to ignite the expanding fire hazard, producing a spectacularly large and violent explosion.

Unsurprisingly, the accidental fuel-air explosion that was created obliterated Starship SN4 in the blink of an eye, shredding its lower (liquid oxygen) tank into steel confetti and immediately breaching the upper (liquid methane) tank, which fell to the ground and subsequently exploded again. The launch mount Starship was staged on was also damaged beyond repair and has been fully dismantled and scrapped in the two days since the anomaly. Thankfully, however, SpaceX already has replacement mounts and ships well on their way to carrying Starship SN4’s torch forward and Elon Musk already seems to understand what caused the prototype’s demise.

Shortly after a post-launch briefing celebrating and discussing SpaceX’s inaugural astronaut launch on May 30th, Reuters reporter Joey Roulette was able to ask Musk about Starship SN4’s spectacular demise the day prior. The SpaceX CEO was quoted saying that “what we thought was going to be a minor test of a quick disconnect ended up being a big problem”, confirming suspicions based on careful analysis of public views of the explosion that it was caused by issues with Starship’s ground support equipment (GSE).

Starhopper’s quick-disconnect umbilical panel is pictured here in May 2019. Starship SN4 used a similar mechanism, although the plumbing is now located inside the vehicle’s circumference. (NASASpaceflight – bocachicagal)

In Musk’s statement, “quick disconnect” (QD) refers to an umbilical port that connects a launch vehicle to GSE, enabling the loading and offloading of propellant and fluids, clamping down the rocket, and providing a wired telemetry and communications link for ground controllers. QDs must perform all those tasks while also being able to rapidly release and disconnect, allowing the rocket to lift off while still protecting its sensitive ports for ease of reuse.

In theory, Starship’s quick-disconnect umbilical panel is even more complex, as it will have to simultaneously enable the ship to be fueled and controlled while sitting on top of a Super Heavy booster and permit in-orbit docking and refueling. Given that Starships are currently being tested independently on spartan launch mounts, it’s unclear if the current generation of prototypes has been outfitted with advanced QD panels. More likely, Musk was referring to a test of a less advanced QD panel similar to the rough version used on Starhopper last year, and SpaceX simply wanted to test its ability to disconnect and reconnect to Starship on command.

SpaceX’s existing Starship launch mount was heavily damaged by SN4’s explosion and has since been fully dismantled. (NASASpaceflight – bocachicagal)
Starship SN4’s remains have already been cleared from the pad. (NASASpaceflight – bocachicagal)

If that’s the case, the likeliest explanation for SN4’s explosion is that that quick disconnect was unable to fully reconnect after the test, resulting in a leak from the liquid methane port when SpaceX began to detank the rocket. Instead of the highly-pressurized fluid flowing smoothly back to ground storage tanks, the liquid methane sprayed wildly, akin to the effect one might observe when attempting to block off an active water source with an open palm.

Work on a second launch mount was already ongoing when Starship SN4 exploded on May 29th. (NASASpaceflight – bocachicagal)
Starship SN5 and SN6 are simultaneously being assembled in SpaceX’s new vertical assembly building (VAB). (NASASpaceflight – bocachicagal)

Compared to the many possible ways a fueled Starship could fail, a propellant leak started by a faulty umbilical panel is about as convenient as they come. Starship SN4 may have been violently destroyed as a result, turning a relatively small error into exceptionally painful lesson but SpaceX has already had some success building full-scale prototypes at an almost unbelievably low cost – likely less than $10M apiece. Starship SN5 appears to be just shy of ready to take SN4’s place on the launch mount, although SpaceX will have to build an entirely new launch mount before it can resume testing.

At the same time, Starship SN5’s successor – SN6 – is just one stacking event away from reaching a level of completion similar to SN4 and SN5. All told, Starship SN4’s demise is just another part of the process of developing a new kind of rocket by building and testing hardware – failure can be a valuable tool when managed properly. Based on past observations, SpaceX could be ready to continue testing (and hopefully flying) Starship prototypes before the end of the month.

Advertisement
-

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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 may test customer-owned Robotaxis as early as next month, Musk says

Published

on

Credit: @AdanGuajardo/X

Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.

In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:

“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”

The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.

This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.

Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.

December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.

Tesla Cybercab goes on sale for $29,990, slated for December deliveries

Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.

The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.

Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.

For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.

Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.

Continue Reading

Elon Musk

FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says

Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.

Published

on

By

Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “As I was saying … Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” Musk wrote on X Monday.

Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.

The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.

Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.

Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.

Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.

Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.

Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.

Continue Reading

News

Tesla makes $3.3 billion Cybercab bet at Giga Berlin

Published

on

Credit: Tesla

It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.

Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.

The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.

Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.

The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).

This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.

The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.

The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.

For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.

They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.

Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.

Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.

Continue Reading