News
SpaceX Crew-1 launch set for Sunday, ULA successfully launches spy satellite
On Friday evening, Nov. 13, NASA and SpaceX announced that the first operational Commercial Crew Program mission of the Crew Dragon would be delayed 24 hours to Sunday, Nov. 15, at 7:27 pm EST (0027 GMT 11/16). During a Crew-1 pre-launch news conference, SpaceX’s senior director of the Human Spaceflight Programs, Benji Reed, stated that the delay was driven by impacts on recovery efforts caused by tropical storm Eta, which had plagued Florida for days.
Just prior to the news conference, United Launch Alliance(ULA) successfully launched its Atlas V rocket after suffering delays of its own earlier in the week. The NROL-101 mission carried a classified payload for the National Reconnaissance Office of the U.S. government and successfully launched from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station at 5:32 pm EST.
Florida weather caused multiple launch delays
Weather, especially that caused by tropical storm Eta, has caused a domino effect of delays for SpaceX and ULA over the last few weeks. The ULA Atlas V 531 rocket stacked with the secretive NROL-101 payload, initially set to liftoff on Nov. 3, was first delayed by damage sustained to environmental control system hardware of the upper stage.
According to company CEO, Tory Bruno, as the rocket was transported from ULA’s vertical integration facility (VIF) to the launchpad of SLC-41, very high winds caused damage to a duct that controlled the flow rate of an upper payload environmental control system. As a result, the rocket was returned to the VIF to have the duct replaced. A launch attempt scheduled for the following day on Wednesday, Nov. 4, was called off due to an unrelated problem with ground support equipment.
The NROL-101 mission was then set to launch on Sunday, Nov. 8, but that attempt was eventually called off due to the impending weather that would be brought across the Florida peninsula by then hurricane Eta. On Friday, Nov. 6, the Atlas V 531 rocket and payload for the National Reconnaissance Office was once again returned to the VIF for protection from the storm.
A final launch attempt was identified for Friday, Nov. 13, just 22 hours before the scheduled launch of the SpaceX, NASA Crew-1 mission from nearby Launch Complex 39A at the Kennedy Space Center. Fortunately, the weather held out long enough for the ULA Atlas V 531 rocket to liftoff. Following liftoff and successful payload deployment the mission was later declared a full success by ULA.
Florida weather also caused offshore recovery delays, impacting crewed launch
Similarly, the SpaceX and NASA Crew-1 mission has also suffered setbacks due to inclement weather, although not at the launch site. Following the successful launch and landing of the B1062 Falcon 9 of the recent GPSII-SV04 mission on Thursday, Nov. 5, SpaceX recovery teams battled unsettled seas to return the booster and the recovery droneship, Of Course I Still Love You (OCISLY), safely back to Port Canaveral.
After securing B1062 safely aboard OCISLY, the SpaceX recovery vessel GO Quest took refuge at the Port of Morehead City in North Carolina. The recovery crew would wait there to assist with the recovery of the B1061 Falcon 9 of the Crew-1 mission, rather than return to Port Canaveral in Florida. The droneship Just Read The Instructions (JRTI) was intended to meet the crew of GO Quest at the Crew-1 booster recovery zone prior to the end of the week.
Due to high winds and rough seas churned up by tropical storm Eta, the OCISLY droneship took an exceptionally tedious 7-day journey hugging the eastern coast of the United States to return to Port Canaveral. The delay caused the crew transfer process from OCISLY to JRTI to be delayed which in turn hindered the departure of the JRTI droneship.
As tropical storm Eta moved out and away from Florida the waters of the Atlantic remained too rough for the JRTI droneship to make up for the lost time. Following the conclusion of SpaceX’s Crew-1 preflight launch readiness review on Friday, Nov. 13, it was announced that the delay in getting the recovery droneship to the B1061 landing zone would delay the Crew-1 launch attempt by 24 hours.
Recovering the Falcon 9 booster, of any mission, is a secondary mission objective. However, the recovery of the Crew-1, B1061 Falcon 9 is important to both NASA and SpaceX – enough so to delay a launch attempt. NASA and SpaceX have already designated this booster to be reused on the next Crew Dragon mission, Crew-2, targeted for no earlier than March 30, 2021. In order to reuse a booster to save on launch costs, it must first be successfully recovered.
If all goes to plan, three NASA astronauts and one astronaut from the Japan Aerospace Exploration Agency will climb aboard the Crew Dragon Resilience on Sunday, Nov. 15, and blast off to the International Space Station precisely at 7:27 pm EST (0027 11/16) from LC-39A at the Kennedy Space Center.
NASA and SpaceX will provide a hosted live broadcast of all Crew-1 events beginning at 3:15 pm EST on Sunday, Nov. 15, on NASA TV and on the SpaceX website.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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’
