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
SpaceX Starship Version 3 booster crumples in early testing
Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory.
Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
Booster test failure
SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.
Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.
Tight deadlines
SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.
While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.
News
Tesla FSD (Supervised) is about to go on “widespread” release
In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”
Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin.
The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.
FSD V14.2 improvements
FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.
A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.
Elon Musk’s predicted wide release
The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”
FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles.
News
Tesla FSD V14.2 starts rolling out to initial batch of vehicles
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.
So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well.
Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots.
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.


Release Notes
2025.38.9.5
Currently Installed
FSD (Supervised) v14.2
Full Self-Driving (Supervised) v14.2 includes:
- Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
- Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
- Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
- Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!
Upcoming Improvements:
- Overall smoothness and sentience
- Parking spot selection and parking quality