Connect with us

News

Here’s why SpaceX’s latest Starship rocket exploded after touchdown

CEO Elon Musk has taken to Twitter to explain why Starship SN10 exploded after a hard landing. (NASASpaceflight - bocachicagal)

Published

on

In what has become a bit of a tradition, CEO Elon Musk has taken to Twitter again to explain the outcome of SpaceX’s latest Starship launch and landing attempt in more detail.

This time around, Musk’s debriefing comes after Starship serial number 10 (SN10) briefly became the first prototype of its kind to land in one piece – an extremely encouraging milestone for SpaceX. Less than 15 minutes later, though, an uncontrolled fire somehow breached the rocket’s stainless steel propellant tanks, resulting in a violent depressurization and explosion that tore Starship SN10 to pieces.

SN10’s momentarily successful landing came less than 30 days after Starship SN9’s own launch and landing attempt, which debuted a quick-fix design change meant to sidestep a different issue that caused Starship SN8 to fail shortly before touchdown last December. As it turns out, that design change – which SN9 never really had the chance to test – may have been Starship SN10’s downfall.

Starships must perform highly unusual maneuvers during their skydiver-style approach to atmospheric descent and the aggressive flip required to transition from that belly-down attitude into a propulsive vertical landing configuration. To enable those acrobatics, Starships need secondary ‘header’ tanks that permit the high-pressure storage of landing propellant.

Instead of having to maintain Starship’s building-sized main tanks at high pressures, header tanks make it far easier to safely store and feed propellant to Raptor engines. Most importantly, they help avoid prevent fuel flow interruptions or bubbles that can easily damage or destroy high-performance liquid rocket engines like Starship’s Raptors.

After Starship SN8’s last-second landing failure on December 8th, SpaceX concluded that low pressure in the liquid methane header tank was largely to blame. Normally pressurized with methane gas in a cutting-edge process called autogenous pressurization, SpaceX ultimately seemed to think that that process was the root cause and responded by adding an alternative helium pressurization workaround at the last second. Long-term, helium is not a viable solution as it’s virtually impossible to resupply in-situ (on the fly), meaning that any Starships reliant upon helium would find themselves stranded on the Moon or Mars.

Advertisement
-

Starship SN9 ultimately failed a few seconds earlier than Starship SN8 when one of its Raptor engines failed to ignite, precluding a true flight test of the helium pressurization fix. As it turns out, Musk believes that that very fix may have doomed Starship SN10.

As Starship SN10 forged ahead past the points of failure that killed SN8 and SN9, the SpaceX CEO thinks that one or more of the vehicle’s three Raptor engines began to ingest some of that helium pressurant as they emptied their methane header tank. As a result, engine thrust would have dropped below expected values, preventing Starship SN10 from slowing down for a truly soft landing. Instead, the Starship hit the ground traveling a solid 25 mph (~10 m/s), obliterating its tiny landing legs and damaging its skirt section.

It’s unclear if that hard landing was the sole cause of SN10’s subsequent explosion, as both official and unofficial webcasts of the launch appear to show a major fire starting well before touchdown and continuing to burn up to the point of failure. Regardless, Musk says that “multiple fixes” are in work for Starship SN11, which is currently speeding towards a launch attempt as early as next week. It remains to be seen if those planned “fixes” will delay SN11’s launch plans.

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

Lifestyle

Tesla’s mirrorless Cybercab will give riders a visibility upgrade

Tesla engineer confirms Cybercab update letting riders pull up rear and repeater cameras on demand.

Published

on

By

Tesla Cybercab camera visibility for passengers (Credit: Dan Burkland via X)
Tesla Cybercab camera visibility for passengers (Credit: Dan Burkland via X)

Tesla is working on a Cybercab update that would let passengers pull up the vehicle’s rear and side cameras on demand, and the request came straight from a rider.

The exchange played out on X late Friday. Cybercab rider Dan Burkland shared photos of the two-seater’s cabin screen after an evening ride, praised the UI team’s work, and left one request: let riders open the rear and repeater cameras whenever they want, “especially for peace of mind.” Tesla UI software engineer Evan (@CarCoder) answered with two words: “In development.”

The idea fits a pattern Teslarati has tracked since public rides began. Days after paid Cybercab service opened in Austin, Tesla sent riders a survey that asked them to rate the touchscreen, the app and the cabin, and to pick the features they wanted most. We reported on that survey in September, and a camera view is the kind of small software change Tesla can push quickly if riders keep asking.

It also speaks to something unique about the vehicle. With no steering wheel, no pedals and no driver, passengers have no mirror to check and no way to see behind them. The hardware is clearly built for camera awareness, from the repeater cameras to the rear camera. Letting a passenger look through those same cameras would give a nervous first time rider a way to confirm what is around the car.

The timing matters because the fleet is growing fast. Tesla’s Robotaxi account said on Saturday that more than 300 Cybercabs are now serving Austin, an eightfold increase in 30 days, and Tesla AI chief Ashok Elluswamy named Dallas as the next city. More cars and more cities mean more people riding in a driverless vehicle for the first time, which is exactly when small trust features carry weight.

For now, the feature is confirmed only as in development. If Tesla follows its usual pattern with Cybercab software, riders could see it appear in a point release without any announcement, and Teslarati will watch for it.

Continue Reading

News

Tesla’s Cybercab fleet jumped 8x in a month, with Dallas up next

Tesla confirms its first official Cybercab fleet number as Austin scales fast and Dallas looms.

Published

on

By

Tesla says more than 300 Cybercabs are now serving Austin, the first time the company has put an official number on its active Cybercab fleet. The figure came from the Robotaxi account on X on Saturday, which wrote that one month after launch the service had “scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days.”

Ashok Elluswamy, Tesla’s head of AI software, quoted the post with a line that carried the bigger news. “Two years since the 10/10 Cybercab WeRobot event, the cabs are everywhere in Austin now. Dallas soon,” he wrote. It is the first time Tesla has named the next city for public Cybercab rides.

Tesla opened Cybercab rides to the public in Austin on September 4, as Teslarati reported, a day after an invite only launch event. The ramp since then has been steep. Our September 28 report had the fleet at well over 100 units after availability jumped from 58 to 125 in a single week. On Thursday, Tesla added 150 Cybercabs to the Texas automated vehicle registry, lifting its registered count to 319 from 169. The first seven appeared on the registry on August 31.

RobotaxiTracker, a community site that counts vehicles from sightings and state records, listed 275 vehicles in unsupervised service in Austin on Saturday, 105 of them Cybercabs, which is well below Tesla’s figure. Tracker counts can lag official numbers, though Sawyer Merritt noted that Cybercab wait times in Austin stayed short on Saturday evening even with more than 2,000 fans in town for X Takeover.

Regulators are watching the rollout. NHTSA opened an audit query into Tesla’s certification that the Cybercab meets federal safety standards, and sworn answers are due October 30. Tesla reports third quarter earnings on October 21, which gives the company a natural venue to define its fleet numbers and put a date on Dallas.

Continue Reading

Elon Musk

Elon Musk roasts India’s billionaire Mukesh Ambani as Starlink fight heats up

Elon Musk sarcastically calls Mukesh Ambani ‘Prime Minister’ as the Starlink India standoff escalates again.

Published

on

By

Elon Musk escalated his public fight over Starlink’s launch in India on Friday, addressing Reliance chairman Mukesh Ambani as “Prime Minister Ambani” in a sarcastic post on X. “Please accept my humble apologies for not realizing that you are the real boss of India,” Musk wrote, before accusing Ambani of “monopolistic exploitation” and asking whether he would “consider allowing Starlink to compete.” In follow up posts, he said Starlink has proven essential during natural disasters and would help parts of India with no internet access.

The post came two days into a fight that Musk sparked up on Wednesday, when he said Starlink was “being blocked by certain oligarchs in order to maintain their monopolistic chokehold on the Indian people.” He called it “a crime against the people of India” and left the names out, adding only, “You can guess who they are.” Jio and Airtel together hold more than 80% of India’s telecom market. On Thursday, Musk asked whether Ambani is “the real boss of India” and said Starlink has spent five years complying with “every single law and requirement” of the Indian government.

India’s government has pushed back each time. The Ministry of Communications called the suggestion that its framework is unfair or discriminatory “baseless and misconceived.” Communications Minister Jyotiraditya Scindia said Friday that three companies hold satcom licenses: Starlink, Jio Satellite Communications, and Bharti backed Eutelsat OneWeb. Amazon’s Kuiper, now Amazon Leo, is still going through the process. None can launch until regulators finalize satellite spectrum pricing and the Home Ministry signs off on each company’s security compliance. Scindia said the telecom regulator and the Department of Telecommunications are close to a decision on pricing, The Hindu reported. Bharti chairman Sunil Mittal also said OneWeb is still waiting on approvals.

Starlink received its operator license in 2025 after a three year wait, and the space regulator IN-SPACe granted what industry executives called the last approval needed in July. The holdup since then centers on security, particularly concern that foreign operators could bypass Indian gateways.

Musk and Ambani have been on opposite sides of this before. In late 2024, Ambani argued for auctioning satellite spectrum, which Musk criticized as out of step with the rest of the world, and India chose administrative allocation instead. By March 2025, the two sides had signed a deal to sell Starlink devices in Reliance stores, and Starlink secured its telecom license that June. That partner is now also a competitor. Jio is reportedly weighing a constellation of 1,600 to 1,650 satellites costing an estimated $10 billion to $15 billion, while Akash Ambani has told shareholders Jio plans to lease capacity from global providers to move quickly.

Continue Reading