News
SpaceX fires up redesigned Crew Dragon as NASA reveals SuperDraco thruster “flaps”
On November 13th, SpaceX revealed that a planned static fire test of a Crew Dragon’s powerful abort thrusters was completed without issue, a strong sign that the company has successfully redesigned the spacecraft to prevent a catastrophic April 2019 explosion from reoccurring.
Pending a far more extensive analysis, Wednesday’s static fire should leave SpaceX on track to perform Crew Dragon’s next major flight test before the end of 2019.
In an unexpected flourish of transparency, SpaceX and NASA published photos of the Crew Dragon capsule’s static fire test just a few hours after it was completed, an excellent sign that the ‘quick-look’ data analysis immediately following the test was extremely positive. Spaceflight Now was first to visually confirm that the test had occurred, publishing a photo that revealed a whitish cloud of smoke produced by the static fire around 3:15 pm EST (20:15 UTC).
Had a failure similar to the April 2019 explosion occurred, that cloud would have likely been tinged red by unburnt dinitrogen tetroxide (NTO) oxidizer, and the different appearance of November 13th’s exhaust cloud was seen as the first tentative sign that this static fire had gone more successfully.
Alongside photos of the SuperDraco thruster test published by NASA and SpaceX shortly after its conclusion, SpaceX confirmed that the test was completed without issue. Regardless of whether everything performed exactly as intended, this means that factory-fresh Crew Dragon capsule C205 made it through the test unscathed, likely securing SpaceX and NASA a large volume of uninterrupted telemetry data, as well as the hardware itself.
Just hours after C205’s static fire was completed, NASA published a detailed update, confirming that the tests were finished without any immediately apparent issues.
NASA described the test in much more detail than SpaceX, noting that it began with the ignition of two of Crew Dragon’s 16 Draco maneuvering thrusters, each performing two one-second burns. C205’s eight SuperDraco abort thrusters subsequently ignited and burned for a total of ~9 seconds to simulate required abort performance, followed by the reignition of two Draco thrusters immediately after SuperDraco cutoff.
Each capable of producing several dozen pounds of thrust, both Crew and Cargo Dragon use Draco thrusters to orient themselves in orbit, rendezvous with the International Space Station, and lower their orbits to reenter Earth’s atmosphere. Crew Dragon’s Draco thrusters are also designed to control its attitude during abort scenarios, stabilizing and flipping the spacecraft to prevent a loss of control and ensure proper orientation during emergency parachute deployment. The Draco firings during Crew Dragon’s November 13th static fire were meant to simulate that additional use-case.
Aside from verifying that SpaceX has successfully redesigned Crew Dragon to mitigate the failure mode that caused capsule C201’s catastrophic explosion in April 2019, the Draco static fires specifically mirrored the burns Crew Dragon C205 will need to perform to successfully complete its In-Flight Abort (IFA) test. As noted by NASA and SpaceX, with the static fire complete, both teams will now comb through the data produced, inspect Crew Dragon to verify its health and the performance of its redesigned high-flow pressurization system, and perform any necessary refurbishment.
SuperDraco’s mystery “flaps”
NASA’s post on Crew Dragon’s static fire revealed another thoroughly intriguing detail: the SpaceX spacecraft’s SuperDraco thrusters apparently have flaps! A bit of retroactive speculation suggests that SuperDracos are closed out with plugs of some sort to create a seal against the environment before Crew Dragon is rolled out to the launch pad. Perhaps, in the event of a SuperDraco ignition, SpaceX included actuating flaps as a method of resealing those thrusters prior to splashdown in the Atlantic Ocean.
“Immediately after the SuperDracos shut down, two Dracos thrusters fired and all eight SuperDraco flaps closed, mimicking the sequence required to reorient the spacecraft in-flight to a parachute deploy attitude and close the flaps prior to reentry. The full sequence, from SuperDraco startup to flap closure, spanned approximately 70 seconds.”
NASA, November 13th, 2019
Given that the obvious utility of those flaps appears to be extremely limited and their associated actuators have to survive the 9+ consecutive seconds of hellish conditions in the event of an actual abort, it seems like an excessively complicated system to include on Crew Dragon. Nevertheless, the ability to guarantee that SuperDracos are water-sealed before splashdown would almost without a doubt make Crew Dragon far easier to refurbish and reuse.
The SuperDraco flaps may also be a holdover from before propulsive Crew Dragon landings were canceled, although the use-cases for such a system still remain unclear. The flaps’ raison d’etre could even be as simple as preventing water intrusion that might otherwise cause Dragon to sink after splashdown.
Regardless of why they exist, NASA indicates that SpaceX’s November 13th static fire proved that they worked exactly as expected, closing soon after the simulated abort burn to seal Crew Dragon against water intrusion. If NASA and SpaceX’s deep-dive inspections and data analysis uncover no red flags, it’s extremely likely that SpaceX will able to launch C205 for its In-Flight Abort test some 4-8 weeks from now.
If the IFA also goes as planned, Crew Dragon could be ready for its inaugural NASA astronaut launch as early as February or March 2020.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
