News
SpaceX says Crew Dragon capsule exploded due to exotic titanium fire
SpaceX has announced via an official update and conference call the preliminary results of a failure investigation convened immediately after Crew Dragon capsule C201 exploded in the midst of an April 20th static fire test.
Hosted by SpaceX Vice President of Mission Assurance Hans Koenigsmann and NASA Commercial Crew Program manager Kathy Lueders, the call provided some minor additional insight beyond a fairly extensive press release issued just prior. According to the preliminary results from SpaceX’s failure investigation, Crew Dragon’s explosion was unrelated to the spacecraft’s propellant tanks, Draco maneuvering thrusters, or SuperDraco abort engines. Rather, the cause lies in a more exotic and unanticipated chemical/material interaction between a plumbing valve, liquid oxidizer, and a helium-based pressurization system.
When metal burns
According to Hans Koenigsmann, SpaceX is approximately 80% of the way through what is known as the fault tree, essentially meaning that the failure investigation is 80% complete. That additional 20% could certainly throw some curveballs but the SpaceX executive was fairly confident that the results presented on July 15th would be representative of the final conclusion.
The ultimate (likely) cause of Crew Dragon’s extremely energetic and destructive explosion centers around the spacecraft’s extensive SuperDraco/Draco plumbing and its associated pressurization system, which uses helium to keep the pressure-fed engines, propellant tanks, and feed lines around 2400 psi (16.5 megapascals). Necessarily, this method of pressurization means that there is direct contact between the pressurant (helium) and the oxidizer/fuel, thus requiring some sort of valve preventing the pressurized fluid from flowing into the pressurization system.

During flight-proven Crew Dragon capsule C201’s April 20th static fire testing, that is reportedly exactly what happened. Over the course of ground testing, a “check valve” separating the pressurization system and oxidizer leaked what SpaceX described as a “slug” of nitrogen tetroxide oxidizer (NTO) into the helium pressurization lines. Around T-100 milliseconds to a planned ignition of the vehicle’s 8 SuperDraco abort engines, the pressurization system rapidly “initialized” (i.e. quickly pressurized the oxidizer and fuel to operational pressures, ~2400 psi).
To do this, helium is rapidly pushed through a check valve – designed with low-molecular-mass helium in mind – to physically pressurize the propellant systems. Unintentionally, the NTO that leaked ‘upstream’ through that valve effectively was taken along for the ride with the high-pressure burst of helium. In essence, picture that you crash your car, only to discover that your nice, fluffy airbag has accidentally been replaced with a bag of sand, and you might be able to visualize the unintended forces Dragon’s check valve (the metaphorical airbag) was subjected to when a “slug” of dense oxidizer was rammed into it at high speed.

In itself, this sort of failure mode is not hugely surprising and SpaceX may have even been aware of some sort of check valve leak(s) and accepted what it believed to be a minor risk in order to continue the test and perhaps examine Dragon’s performance under suboptimal conditions. What SpaceX says it did not realize was just how energetic the reaction between the NTO and the check valve could be. SpaceX’s understanding is that the high-speed slug of dense NTO was traveling so fast and at such a high pressure that, by impacting the titanium check valve, it quite literally broke the valve and may have chemically ignited the metal, thus introducing a slug of burning NTO into the liberated NTO system itself – effectively a match tossed into a powder keg.
It’s unclear if the ignition came from a chemical reaction between titanium (a technically flammable metal similar to magnesium) and NTO, or if the source came from the titanium valve being smashed apart, perhaps quite literally creating a spark as metal debris violently interacted. Either way, the solution – as SpaceX perceives it – is the same: instead of a mechanical check valve (simple but still not 100% passive), the barrier between pressurant and oxidizer (as well as fuel, most likely) will be replaced with something known as a burst disk. According to Koenigsmann, only a handful (~4) of those valves exist and thus need to be replaced by burst disks, a relatively fast and easy fix.
Burst disks are single-use and inherently unreusable, but they are also completely passive and simply do not leak until subjected to a specific amount of pressure. Because they are single-use, they can’t be directly tested prior to flight, limiting some of the in-principle reliability for the sake of an extremely leak-proof barrier.

Ultimately, both Koenigsmann and Lueders went out of their way to avoid answering any questions about SpaceX’s Crew Dragon upcoming test and launch schedule and what sort of delays the explosion will ultimately incur. Both individuals were nevertheless upbeat and by the sound of it, delays to Crew Dragon will be far less severe relative to delays caused by a pressure vessel or engine failure. For the time being, NASA has published a tentative target of mid-November 2019 for Crew Dragon’s first crewed launch to the International Space Station, while Lueders and Koenigsmann expressed hope in a 2019 launch but refused to give a specific estimate of the odds of that occurring.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Tesla’s Elon Musk: 10 billion miles needed for safe Unsupervised FSD
As per the CEO, roughly 10 billion miles of training data are required due to reality’s “super long tail of complexity.”
Tesla CEO Elon Musk has provided an updated estimate for the training data needed to achieve truly safe unsupervised Full Self-Driving (FSD).
As per the CEO, roughly 10 billion miles of training data are required due to reality’s “super long tail of complexity.”
10 billion miles of training data
Musk comment came as a reply to Apple and Rivian alum Paul Beisel, who posted an analysis on X about the gap between tech demonstrations and real-world products. In his post, Beisel highlighted Tesla’s data-driven lead in autonomy, and he also argued that it would not be easy for rivals to become a legitimate competitor to FSD quickly.
“The notion that someone can ‘catch up’ to this problem primarily through simulation and limited on-road exposure strikes me as deeply naive. This is not a demo problem. It is a scale, data, and iteration problem— and Tesla is already far, far down that road while others are just getting started,” Beisel wrote.
Musk responded to Beisel’s post, stating that “Roughly 10 billion miles of training data is needed to achieve safe unsupervised self-driving. Reality has a super long tail of complexity.” This is quite interesting considering that in his Master Plan Part Deux, Elon Musk estimated that worldwide regulatory approval for autonomous driving would require around 6 billion miles.
FSD’s total training miles
As 2025 came to a close, Tesla community members observed that FSD was already nearing 7 billion miles driven, with over 2.5 billion miles being from inner city roads. The 7-billion-mile mark was passed just a few days later. This suggests that Tesla is likely the company today with the most training data for its autonomous driving program.
The difficulties of achieving autonomy were referenced by Elon Musk recently, when he commented on Nvidia’s Alpamayo program. As per Musk, “they will find that it’s easy to get to 99% and then super hard to solve the long tail of the distribution.” These sentiments were echoed by Tesla VP for AI software Ashok Elluswamy, who also noted on X that “the long tail is sooo long, that most people can’t grasp it.”
News
Tesla earns top honors at MotorTrend’s SDV Innovator Awards
MotorTrend’s SDV Awards were presented during CES 2026 in Las Vegas.
Tesla emerged as one of the most recognized automakers at MotorTrend’s 2026 Software-Defined Vehicle (SDV) Innovator Awards.
As could be seen in a press release from the publication, two key Tesla employees were honored for their work on AI, autonomy, and vehicle software. MotorTrend’s SDV Awards were presented during CES 2026 in Las Vegas.
Tesla leaders and engineers recognized
The fourth annual SDV Innovator Awards celebrate pioneers and experts who are pushing the automotive industry deeper into software-driven development. Among the most notable honorees for this year was Ashok Elluswamy, Tesla’s Vice President of AI Software, who received a Pioneer Award for his role in advancing artificial intelligence and autonomy across the company’s vehicle lineup.
Tesla also secured recognition in the Expert category, with Lawson Fulton, a staff Autopilot machine learning engineer, honored for his contributions to Tesla’s driver-assistance and autonomous systems.
Tesla’s software-first strategy
While automakers like General Motors, Ford, and Rivian also received recognition, Tesla’s multiple awards stood out given the company’s outsized role in popularizing software-defined vehicles over the past decade. From frequent OTA updates to its data-driven approach to autonomy, Tesla has consistently treated vehicles as evolving software platforms rather than static products.
This has made Tesla’s vehicles very unique in their respective sectors, as they are arguably the only cars that objectively get better over time. This is especially true for vehicles that are loaded with the company’s Full Self-Driving system, which are getting progressively more intelligent and autonomous over time. The majority of Tesla’s updates to its vehicles are free as well, which is very much appreciated by customers worldwide.
Elon Musk
Judge clears path for Elon Musk’s OpenAI lawsuit to go before a jury
The decision maintains Musk’s claims that OpenAI’s shift toward a for-profit structure violated early assurances made to him as a co-founder.
A U.S. judge has ruled that Elon Musk’s lawsuit accusing OpenAI of abandoning its founding nonprofit mission can proceed to a jury trial.
The decision maintains Musk’s claims that OpenAI’s shift toward a for-profit structure violated early assurances made to him as a co-founder. These claims are directly opposed by OpenAI.
Judge says disputed facts warrant a trial
At a hearing in Oakland, U.S. District Judge Yvonne Gonzalez Rogers stated that there was “plenty of evidence” suggesting that OpenAI leaders had promised that the organization’s original nonprofit structure would be maintained. She ruled that those disputed facts should be evaluated by a jury at a trial in March rather than decided by the court at this stage, as noted in a Reuters report.
Musk helped co-found OpenAI in 2015 but left the organization in 2018. In his lawsuit, he argued that he contributed roughly $38 million, or about 60% of OpenAI’s early funding, based on assurances that the company would remain a nonprofit dedicated to the public benefit. He is seeking unspecified monetary damages tied to what he describes as “ill-gotten gains.”
OpenAI, however, has repeatedly rejected Musk’s allegations. The company has stated that Musk’s claims were baseless and part of a pattern of harassment.
Rivalries and Microsoft ties
The case unfolds against the backdrop of intensifying competition in generative artificial intelligence. Musk now runs xAI, whose Grok chatbot competes directly with OpenAI’s flagship ChatGPT. OpenAI has argued that Musk is a frustrated commercial rival who is simply attempting to slow down a market leader.
The lawsuit also names Microsoft as a defendant, citing its multibillion-dollar partnerships with OpenAI. Microsoft has urged the court to dismiss the claims against it, arguing there is no evidence it aided or abetted any alleged misconduct. Lawyers for OpenAI have also pushed for the case to be thrown out, claiming that Musk failed to show sufficient factual basis for claims such as fraud and breach of contract.
Judge Gonzalez Rogers, however, declined to end the case at this stage, noting that a jury would also need to consider whether Musk filed the lawsuit within the applicable statute of limitations. Still, the dispute between Elon Musk and OpenAI is now headed for a high-profile jury trial in the coming months.