News
SpaceX’s Crew Dragon suffers catastrophic explosion during static fire test
Six weeks after the spacecraft completed its orbital launch debut, SpaceX’s first flight-proven Crew Dragon capsule suffered a catastrophic explosion seconds before a planned SuperDraco test fire.
In the last nine years, SpaceX has successfully built, tested, launched, and recovered Cargo and Crew Dragons 18 times, including five instances of Cargo Dragon capsule reuse, all with minor or no issues. The April 20th event is the first time in the known history of SpaceX’s orbital spacecraft program that a vehicle – in this case, the first completed and flight-proven Crew Dragon capsule – has suffered a total failure. Regardless of the accident investigation’s ultimate conclusions, the road ahead of Crew Dragon’s first crewed test flight has become far more arduous.
According to information acquired by NASASpaceflight.com, SpaceX was in the middle of a series of static fire tests meant to verify that the flight-proven capsule was in good working order after Crew Dragon’s inaugural mission to orbit. The spacecraft was to be tested near SpaceX’s Cape Canaveral Landing Zone facilities, where the company has a small but dedicated space for Dragon tests. Crew Dragon C201’s testing began earlier on Saturday, successfully firing up its smaller Draco maneuvering thrusters. This transitioned into a planned SuperDraco ignition, what would have been the first such integrated test fire for capsule C201.
SpaceX planned to rapidly reuse Crew Dragon C201 for an upcoming in-flight abort (IFA) test, in which the spacecraft would be required to successfully escape from Falcon 9 at the point of peak aerodynamic stress (Max Q). Based on a leaked video of the failure, one or several faults in Crew Dragon’s design and/or build led to a near-instantaneous explosion that destroyed the spacecraft. Sound in the background seems to indicate that the explosion occurred several seconds before the planned SuperDraco ignition, a major concern given their pressure-fed design.
As pressure-fed rocket engines specifically designed to be the basis of a launch escape system, Crew Dragon and its SuperDraco thrusters are meant to be ready to ignite at a millisecond’s notice once they are armed in a flight-ready configuration. It’s safe to say that ten seconds away from a specifically planned ignition is one of those moments, although there is a limited chance that SpaceX’s static fire procedures intentionally diverge from an abort-triggered ignition. Regardless, the fact that Crew Dragon was destroyed before the ignition of its SuperDracos is not an encouraging sign.
Instead of a problem with its high-performance abort thrusters, it can be tentatively concluded that Crew Dragon’s explosion originated in its fuel tanks or propellant plumbing. Such an immediate and energetic explosion points more towards a total failure of propellant lines or valves (or their avionics), while another – and potentially far more concerning – cause could be one of Crew Dragon’s pressure vessels. In a space as enclosed as a Dragon capsule, the rupture of a pressure vessel could trigger a chain reaction of pressure vessel failures, freeing both oxidizer (NTO) and fuel (MMH). Known as hypergolic propellant, NTO and MMH ignite immediately (and violently so) when mixed.
It’s quite possible that the accident investigation to follow will be SpaceX’s most difficult and trying yet. Regardless of the specific cause, the footage of Crew Dragon C201’s demise does not support any positive conclusions about the fate of astronauts or passengers, had they been aboard during the violent explosion. Seemingly triggered in some way by the very system meant to safely extricate Crew Dragon and its astronauts from a failing Falcon 9 rocket, major work will need to be done to prove to NASA that the spacecraft is safe. Sadly, Boeing’s Starliner spacecraft – funded in parallel with Crew Dragon under NASA’s Commercial Crew Program – suffered a far less severe but no less significant failure during a static fire test of its own abort thrusters. Boeing was forced to remove the impacted hardware from its flight plans to extensively clean, repair, and rework the service module.
NASA is now faced with the fact that both of the spacecraft it supported with CCP have exhibited major failures related to their launch escape systems. Crew Dragon’s catastrophic explosion comes as a particularly extreme surprise given how extensively SpaceX has already tested the SuperDraco engines and plumbing, as well as the successful completion of the spacecraft’s launch debut. In the process of DM-1 launch preparations, Crew Dragon likely spent a minimum of 80 minutes with its SuperDraco thrusters and propellant systems primed and ready to abort at any second, apparently without a single mildly-concerning issue.
Godspeed to SpaceX and NASA as they enter into this challenging and unplanned failure investigation.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
