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.
Elon Musk
SpaceX’s Starship FL launch site will witness scenes once reserved for sci-fi films
A Starship that launches from the Florida site could touch down on the same site years later.
The Department of the Air Force (DAF) has released its Final Environmental Impact Statement for SpaceX’s efforts to launch and land Starship and its Super Heavy booster at Cape Canaveral Space Force Station’s SLC-37.
According to the Impact Statement, Starship could launch up to 76 times per year on the site, with Super Heavy boosters returning within minutes of liftoff and Starship upper stages landing back on the same pad in a timeframe that was once only possible in sci-fi movies.
Booster in Minutes, Ship in (possibly) years
The EIS explicitly referenced a never-before-seen operational concept: Super Heavy boosters will launch, reach orbit, and be caught by the tower chopsticks roughly seven minutes after liftoff. Meanwhile, the Starship upper stage will complete its mission, whether a short orbital test, lunar landing, or a multi-year Mars cargo run, and return to the exact same SLC-37 pad upon mission completion.
“The Super Heavy booster landings would occur within a few minutes of launch, while the Starship landings would occur upon completion of the Starship missions, which could last hours or years,” the EIS read.
This means a Starship that departs the Florida site in, say, 2027, could touch down on the same site in 2030 or later, right beside a brand-new stack preparing for its own journey, as noted in a Talk Of Titusville report. The 214-page document treats these multi-year round trips as standard procedure, effectively turning the location into one of the world’s first true interplanetary spaceports.
-->Noise and emissions flagged but deemed manageable
While the project received a clean bill of health overall, the EIS identified two areas requiring ongoing mitigation. Sonic booms from Super Heavy booster and Starship returns will cause significant community annoyance” particularly during nighttime operations, though structural damage is not expected. Nitrogen oxide emissions during launches will also exceed federal de minimis thresholds, prompting an adaptive management plan with real-time monitoring.
Other impacts, such as traffic, wildlife (including southeastern beach mouse and Florida scrub-jay), wetlands, and historic sites, were deemed manageable under existing permits and mitigation strategies. The Air Force is expected to issue its Record of Decision within weeks, followed by FAA concurrence, setting the stage for rapid redevelopment of the former site into a dual-tower Starship complex.
SpaceX Starship Environmental Impact Statement by Simon Alvarez
News
Tesla Full Self-Driving (FSD) testing gains major ground in Spain
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Tesla’s Full Self-Driving (Supervised) program is accelerating across Europe, with Spain emerging as a key testing hub under the country’s new ES-AV framework program.
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Spain’s ES-AV framework
Spain’s DGT launched the ES-AV Program in July 2025 to standardize testing for automated vehicles from prototypes to pre-homologation stages. The DGT described the purpose of the program on its official website.
“The program is designed to complement and enhance oversight, regulation, research, and transparency efforts, as well as to support innovation and advancements in automotive technology and industry. This framework also aims to capitalize on the opportunity to position Spain as a pioneer and leader in automated vehicle technology, seeking to provide solutions that help overcome or alleviate certain shortcomings or negative externalities of the current transportation system,” the DGT wrote.
The program identifies three testing phases based on technological maturity and the scope of a company’s operations. Each phase has a set of minimum eligibility requirements, and applicants must indicate which phase they wish to participate in, at least based on their specific technological development.
-->
Tesla FSD tests
As noted by Tesla watcher Kees Roelandschap on X, the DGT’s new framework effectively gives the green flight for nationwide FSD testing. So far, Tesla Spain has a total of 19 vehicles authorized to test FSD on the country’s roads, though it would not be surprising if this fleet grows in the coming months.
The start date for the program is listed at November 27, 2025 to November 26, 2027. The DGT also noted that unlimited FSD tests could be done across Spain on any national route. And since Tesla is already in Phase 3 of the ES-AV Program, onboard safety operators are optional. Remote monitoring would also be allowed.
Tesla’s FSD tests in Spain could help the company gain a lot of real-world data on the country’s roads. Considering the scope of tests that are allowed for the electric vehicle maker, it seems like Spain would be one of the European countries that would be friendly to FSD’s operations. So far, Tesla’s FSD push in Europe is notable, with the company holding FSD demonstrations in Germany, France, and Italy. Tesla is also pushing for national approval in the Netherlands in early 2026.
News
Tesla FSD V14.2.1 is earning rave reviews from users in diverse conditions
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise.
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise for its smoother performance and smarter decision-making.
Videos and firsthand accounts from Tesla owners highlight V14.2.1 as an update that improves navigation responsiveness, sign recognition, and overall fluidity, among other things. Some drivers have even described it as “more alive than ever,” hinting at the system eventually feeling “sentient,” as Elon Musk has predicted.
FSD V14.2.1 first impressions
Early adopters are buzzing about how V14.2.1 feels less intrusive while staying vigilant. In a post shared on X, Tesla owner @LactoseLunatic described the update as a “huge leap forward,” adding that the system remains “incredibly assertive but still safe.”
Another Tesla driver, Devin Olsenn, who logged ~600 km on V14.2.1, reported no safety disengagements, with the car feeling “more alive than ever.” The Tesla owner noted that his wife now defaults to using FSD V14, as the system is already very smooth and refined.
Adverse weather and regulatory zones are testing grounds where V14.2.1 shines, at least according to testers in snow areas. Tesla watcher Sawyer Merritt shared a video of his first snowy drive on unplowed rural roads in New Hampshire, where FSD did great and erred on the side of caution. As per Merritt, FSD V14.2.1 was “extra cautious” but it performed well overall.
-->Sign recognition and freeway prowess
Sign recognition also seemed to show improvements with FSD V14.2.1. Longtime FSD tester Chuck Cook highlighted a clip from his upcoming first-impressions video, showcasing improved school zone behavior. “I think it read the signs better,” he observed, though in standard mode, it didn’t fully drop to 15 mph within the short timeframe. This nuance points to V14.2.1’s growing awareness of temporal rules, a step toward fewer false positives in dynamic environments.
FSD V14.2.1 also seems to excel in high-stress highway scenarios. Fellow FSD tester @BLKMDL3 posted a video of FSD V14.2.1 managing a multi-lane freeway closure due to a police chase-related accident. “Perfectly handles all lanes of the freeway merging into one,” the Tesla owner noted in his post on X.
FSD V14.2.1 was released on Thanksgiving, much to the pleasant surprise of Tesla owners. The update’s release notes are almost identical to the system’s previous iteration, save for one line item read, “Camera visibility can lead to increased attention monitoring sensitivity.”
SpaceX’s Starship FL launch site will witness scenes once reserved for sci-fi films
Tesla Full Self-Driving (FSD) testing gains major ground in Spain
