News
SpaceX set to launch reused Dragon on a new Falcon 9 as NASA requests delay
An electrical fault aboard the International Space Station (ISS) has forced NASA to delay SpaceX’s CRS-17 Cargo Dragon launch from May 1st to May 3rd, giving the station’s crew more time to fix the issues at hand.
A new Falcon 9 Block 5 booster is tasked with launching the spacecraft and completed a static fire test at SpaceX’s LC-40 pad on April 27th. The Cargo Dragon capsule, however, completed its first orbital resupply mission (CRS-12) in September 2017 and has since been refurbished for a second launch. After CRS-17, three launches remain on SpaceX’s CRS1 NASA contract between now and early 2020, after which Dragon 2 (i.e. Crew Dragon) is expected to take over. However, a recent failure during a Crew Dragon test have thrown those plans into question.
Cargo Dragon’s 17th mission
Known as C113, the CRS-12 capsule is the last Dragon 1 manufactured by SpaceX, leaving a fleet of five flight-proven spacecraft for SpaceX to complete the eight remaining ISS resupply missions under its Commercial Resupply Services 1 (CRS1) contract. CRS-17 is the latest installment in SpaceX’s ISS resupply saga and is manifested with ~2500 kg (5500 lb) of cargo.
Along for the ride are NASA’s Orbiting Carbon Observatory-3 (OCO-3) and the multi-experiment STP-H6 investigation, two large pieces of hardware that will be delivered to the ISS in Dragon’s unpressurized trunk. After being berthed to the ISS, astronauts will unpack dozens of packages stored inside Cargo Dragon’s cabin. Sometime later, the station’s Canadarm2 will be used to grab OCO-3 and STP-H6 and install each on the outside of the space station, where they will hopefully live long and scientifically fruitful lives.
SpaceX and NASA have assigned a new Falcon 9 Block 5 booster – likely B1056 – to launch CRS-17. To preserve the scene of Crew Dragon C201’s April 20th explosion, the booster will attempt to land around 20 miles (32 km) offshore aboard drone ship Of Course I Still Love You (OCISLY). Originally scheduled for April 25th, CRS-17 was delayed to the 26th, 30th, 1st, and now May 3rd, most of which were requested by NASA for ISS scheduling purposes.
The latest delay – from May 1st to no earlier than (NET) May 3rd – was triggered by an unexpected electrical fault aboard the ISS, cutting the redundancy of its Canadarm2 (SSRMS) control systems from two strings to one. In other words, Canadarm2 – used to ‘grapple’ and berth spacecraft like Cargo Dragon and Cygnus to the station – is now just one electrical fault away from being rendered inoperable. CRS-17 will stay grounded until two-string (i.e. single fault) redundancy is returned to Canadarm2 and additional impacted systems.
In the event that ISS astronauts and NASA ground control are able to repair the electrical systems in a timely fashion, CRS-17 is scheduled to launch at 3:11 am EDT (07:11 UTC) on May 3rd.
In the shadow of Crew Dragon
A recent catastrophic failure of Crew Dragon (i.e. Dragon 2) raises serious questions about SpaceX’s follow-up CRS2 contract, but the nominal plan involves retiring Dragon 1 after CRS-20 and flying all future cargo missions with flight-proven Crew Dragon spacecraft. In the likely event that Crew Dragon C201’s failure delays SpaceX’s CRS2 schedule by several months, there are contingency plans to continue flying refurbished Dragon 1 spacecraft.
However, each Dragon 1 was designed for a maximum of three orbital missions, meaning that SpaceX’s current capsule fleet can support no more than six additional resupply missions before they reach the end of their usable lifespans. SpaceX thus has two potential buffer missions – CRS-21 and CRS-22 – that could theoretically account for up to a year of Dragon 2 delays. Beyond that, additional Dragon 2 delays could create a gap where NASA would have to supply the ISS without SpaceX’s services.
In a best-case scenario, SpaceX and NASA will quickly uncover an unequivocal culprit of C201’s catastrophic explosion, fix the technical and organizational failures that allowed it to happen, and be back on their feet in no time. In reality, it’s likely that the failure will delay future Crew Dragon (and thus Dragon 2) launches by a minimum of 6-12 months. SpaceX will likely need to change up the launch order of its capsules, reassigning DM-2’s Crew Dragon to the in-flight abort (IFA) test and the US Crew Vehicle 1 (USCV-1) Crew Dragon to SpaceX’s first crewed demonstration mission (DM-2). After such a serious and potentially fatal failure, it’s even possible that NASA will require an additional uncrewed orbital launch before permitting SpaceX to fly astronauts on Crew Dragon.
Given that SpaceX’s nominal CRS2 plan involved lightly modifying and reusing Dragon 2s after crewed missions, the future (and schedule) of the company’s Cargo and Crew contracts are intimately intertwined. With any luck, SpaceX and NASA will be able to solve the technical, organizational, and logistical problems now facing them and ensure a stable future for Dragon 2. In the meantime, Cargo Dragon’s CRS-17 mission offers SpaceX a chance to partially verify that Cargo Dragon C201’s issues are are relegated to Dragon 2 and Dragon 2 alone.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
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.
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.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
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:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
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.
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:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
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.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
