Connect with us

News

SpaceX fires up redesigned Crew Dragon as NASA reveals SuperDraco thruster “flaps”

On November 13th, SpaceX successfully static fired Crew Dragon capsule C205's Draco and SuperDraco thrusters. (SpaceX)

Published

on

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.

Advertisement

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.

Advertisement

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.

A pod of SuperDraco thrusters is pictured here shortly after installation on Crew Dragon C206, the spacecraft set to launch astronauts for the first time ever. (SpaceX)

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

In retrospect, flaps (actuating covers) are an obvious explanation for the cutouts visible directly underneath each SuperDraco pod. (SpaceX)

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.

The fact that Crew Dragon C201’s flaps appeared to be unchanged after launch and recovery suggests that they are more of a backup in the event that the abort thrusters have to be used. (NASA)

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.

Advertisement

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla faces Full Self-Driving pushback in EU over ‘speeding’

Published

on

Credit: Tesla

A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.

The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.

TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.

Tesla Full Self-Driving gets first-ever European approval

Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.

Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.

TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of ​vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.

This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.

This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.

However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.

Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.

Continue Reading

Elon Musk

Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’

Published

on

Credit: Tesla

Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.

The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.

A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”

Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.

Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.

This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.

The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.

Musk teased that a similar feature was “coming” back in February:

Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says

It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.

Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.

Here’s an example of that from December:

Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.

We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.

Continue Reading

News

Tesla Cybercab has one important piece that AI4 cars might need for FSD

Published

on

Credit: @tpgoebel | X

A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.

This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.

The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.

Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:

Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.

But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:

This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.

For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.

Without it, even the most advanced neural nets struggle when their “eyes” are compromised.

What Does This Mean for AI4 Cars?

This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:

Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys

As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.

As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.

Continue Reading