Connect with us

News

SpaceX Crew Dragon spacecraft set to static fire SuperDraco abort thrusters after delays

Crew Dragon hovers with its SuperDraco abort thrusters. (SpaceX)

Published

on

Originally scheduled for early November, SpaceX now plans to static fire a Crew Dragon capsule’s SuperDraco abort thrusters no earlier than Wednesday, November 13th. Success would pave the way for SpaceX to launch the spacecraft’s in-flight abort (IFA) before the end of 2019.

In April 2019, a bad design choice finally reared its head, triggering an oxidizer leak and exotic titanium chemical fire that lead to the catastrophic explosion of Crew Dragon capsule C201, the first upgraded spacecraft to successfully launch, dock with the ISS, and return to Earth. That explosion occurred shortly after a successful Draco maneuvering thruster test and just milliseconds before the planned ignition of C201’s eight SuperDraco abort thrusters.

SpaceX planned on reusing flight-proven Crew Dragon capsule C201 to complete its In-Flight Abort (IFA) test, in which the spacecraft will attempt to escape from Falcon 9 during Max Q, the most aerodynamically stressful period of launch. After C201’s premature demise, SpaceX was forced to reassign new Crew Dragon spacecraft already in production, and capsule C205 – previously assigned to Dragon’s Demo-2 astronaut launch debut – was delivered to SpaceX’s Florida launch facilities in early October.

C205 will now support SpaceX’s IFA test. However, prior to launch, SpaceX (or NASA, or both entities) want to ensure that the fixes and upgrades retroactively applied to Crew Dragon will prevent C201’s failure mode from reoccurring. This proof will come in the form of a static fire test identical to the one that caused C201’s explosion. Dragon capsule C205 will be loaded with liquid dinitrogen tetroxide (also known as NTO or N2O4) and monomethylhydrazine (MMH) fuel and fire its much smaller Draco maneuvering thrusters.

Advertisement
Seven of Cargo Dragon capsule C113’s Draco maneuvering thrusters are visible here. Crew Dragon uses similar thrusters. (Pauline Acalin)

Lastly, C205 will ignite its eight SuperDraco abort thrusters – capable of producing more than 570 kN (128,000 lbf) of combined thrust – to conclude the static fire acceptance test. NASA and SpaceX will likely analyze the results together, while SpaceX will refurbish and refuel the spacecraft as expediently as possible. If everything goes as planned, Crew Dragon C205 will be integrated with its disposable trunk section and transported to Launch Complex 39A sometime in late-November or December.

In an impressive demonstration of SpaceX’s ability to work fast, the company managed to determine the cause of C201’s explosion, correct design flaws, prove those corrections with extensive testing, modify Crew Dragon C205 in light of those changes, and ship the completed spacecraft to Florida in less than six months. NASA Commercial Crew Program Manager Kathy Lueders, rare to heap praise, deemed SpaceX’s response “a pretty phenomenal turnaround.”

NASASpaceflight reporter Michael Baylor says that Crew Dragon’s static fire is now scheduled no earlier than the morning of November 13th, a delay of 11 days from the static fire’s first known target, November 2nd. It’s unclear what triggered the delay, but it would be unsurprising for SpaceX to be treading with extreme caution in a bid to avoid another serious Crew Dragon anomaly.

SpaceX recently began the installation of SuperDraco abort thrusters on the Crew Dragon capsule set to support Demo-2, SpaceX’s first astronaut launch. (SpaceX)
Crew Dragon capsule C205 and Falcon 9 booster B1046 arrived in Florida around October 3rd ahead of SpaceX’s critical In-Flight Abort (IFA) test. (SpaceX)

If all goes as planned during the test and the post-test inspections raise no red flags, SpaceX and NASA will likely be ready to launch Crew Dragon’s IFA test some 4-6 weeks after. Stay tuned for updates.

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

Advertisement

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