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.
News
Tesla’s Cybercab fleet just had its biggest day ever
Tesla registered a record 200 Cybercabs in one day, and Dallas could be next up.
Tesla added a record 200 Cybercabs to its Texas Robotaxi fleet in a single day, pushing the purpose-built two-seater past 750 registered units in the state. The batch landed on the Texas Department of Motor Vehicles automated vehicle register at 3:45 p.m. CT on November 17 and included 200 Cybercabs and one Model Y. Tesla’s Cybercab count had sat at 573 since late October before the jump.
The additions also put Tesla back ahead of Waymo on the register. Tesla now has 1,507 vehicles registered for driverless operation in Texas against Waymo’s 1,321, a lead of 186. Waymo had been ahead by 15 vehicles before the batch arrived. Tesla first passed Waymo on November 10, as Teslarati reported, before Waymo briefly moved back in front.
🚨 There are more CYBERCABS in the Tesla Robotaxi fleet in Texas than Model Y! https://t.co/BdRK2LnnAP — TESLARATI (@Teslarati) November 18, 2026
Cybercabs now make up 51.3 percent of Tesla’s registered Texas fleet, at 773 units against 734 Model Ys. Waymo’s fleet in the state is split between 874 Jaguar I-PACEs and 447 Ojai vehicles.
The register does not say where vehicles will operate, and registration does not mean a car is carrying riders. Still, the timing lines up with Tesla’s plans for Dallas. On the company’s third quarter earnings call in October, AI chief Ashok Elluswamy said, “next month, we’ll be launching in Dallas,” and a video posted over the weekend showed more than 50 Cybercabs parked in rows at a Dallas lot, with more on a car carrier nearby. Tesla has not announced a start date.
Dallas is already one of Tesla’s busiest Robotaxi markets. Model Y Robotaxis there have run without anyone in the driver’s seat around the clock since November 11, and the city logged 608,130 miles with no safety monitor between January 22 and October 18, second only to Austin, according to Tesla’s first Robotaxi Safety Report. Public Cybercab rides have been limited to Austin since the vehicle joined the service in September.
The fleet growth comes as Tesla shifts more of its factory capacity toward the Cybercab. The company is winding down Cybertruck production at Giga Texas by the end of summer 2027 to make room, and announced this week a €3 billion expansion of Giga Berlin with a new building designed to produce up to 1 million Cybercabs a year starting in 2029, as Teslarati covered.
Some Cybercabs will soon go to private owners too. Tesla began inviting select customers to buy the vehicle for personal use last week at $29,990 with a required $299 monthly Autonomy Subscription, with deliveries targeted for December in the same five Texas cities where Robotaxi operates.
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.