News
SpaceX’s flight-proven Falcon 9 and drone ship fleet ready for duo of launches
SpaceX is gearing up for a duo of flight-proven Falcon 9 launches and drone ship landings on both coasts of the United States, set for liftoff from Cape Canaveral’s Kennedy Space Center and Vandenberg Air Force Base no earlier than (NET) November 15th and 19th, respectively.
#SpaceXArmada: Moments ago, outbound tugboat Hawk with droneship OCISLY in tow in @PortCanaveral. Destination: Booster core landing/recovery LZ of Thursday's #Eshail2 launch, approx 408 mi E of @NASAKennedy. pic.twitter.com/n5FvBdIvpt
— Cowboy Dan (@CowboyDanPaasch) November 12, 2018
East Coast activities
On the East Coast, drone ship Of Course I Still Love You departed from Port Canaveral late last night (Nov 11) as Falcon 9 B1047 rolled onto Pad 39A for a preflight static fire test, where the rocket will be filled with a full complement of fluids (TEA/TEB, helium, nitrogen, oxygen, kerosene) and all nine Merlin 1D engines are ignited in order to replicate the seconds just prior to a real launch. That static fire test was originally expected to occur on November 10 or 11 but has obviously been pushed back a day to Nov. 12, likely meaning that the rocket’s launch – carrying Qatari communications satellite Es’hail-2 – will slip 24 hours to 3:46pm EST (08:46 UTC) on the 16th,
Following the unfortunate loss of Amos-6 during a preflight static fire in September 2016, SpaceX has since made a reasonable move away from performing static fires with payloads integrated atop the rocket, unless the customer specifically requests that it be done that way to save time. As such, Falcon 9 must be brought horizontal, rolled back to the hangar, inspected, and finally have the payload and fairing attached to the rocket, a sensitive process that demands nuance and time. Combined with an analysis of data gathered during the static fire, this process – when all goes as planned – can take at least 48 hours from start to finish, and longer still if any minor off-nominal behavior is observed or the launch customer has additional requirements (typically reserved for NASA and national security-related missions).
- B1047 horizontal at Pad 39A, November 11. (Tom Cross)
- B1047 made an extraordinary ring vortex rainbow as it smashed through Max Q, the point of highest aerodynamic stress on the rocket. (Tom Cross)
- B1046 seen mid-static fire at Pad 39A ahead of Falcon 9 Block 5’s launch debut, May 2018. (Tom Cross)
Because rockets like Falcon 9 are extraordinarily intricate and finely-tuned machines, perfectly nominal launch-related events are few and far between. In reality, the time between static fire rollout and launch readiness is rarely less than three days (72 hours), not including the process of rolling the fully-integrated rocket back out to the pad, aligning and securing the vehicle and transporter-erector (TE) over the flame trench, and finally attaching all umbilical connections and verifying vehicle health. Speaking generally, four to five days is a good rule of thumb for the time it takes to complete Falcon 9’s static fire and return the rocket to the pad after attaching the payload.
Still, it’s always a good sign when a drone ship leaves port, much like OCISLY did on the evening of the 11th. The journey to its destination will take 2-3 days, meaning that the drone ship will be ready to catch Falcon 9 whenever the rocket is ready to launch.

Drone ships and sooty rockets, oh my!
On the West Coast, SpaceX is also getting ready for drone ship Just Read The Instructions (JRTI) to depart Port of San Pedro in anticipation of a presumed sea recovery of Falcon 9 following the NET Nov 19 launch of a multi-satellite rideshare mission known as SSO-A. While SpaceX currently holds two recovery licenses for the booster, one by sea and one at the land-based LZ-4 pad, it’s possible that the company will be forced to use JRTI despite the fact that Falcon 9 will have plenty of propellant left to return itself to the launch site (RTLS). United Launch Alliance’s (ULA) next Delta IV Heavy rocket is currently on-pad with a presumably very expensive National Reconnaissance (NRO) satellite attached roughly 1.5 miles northeast of SpaceX’s LZ-4 – the rest of the gaps are easy enough to fill in.
- Falcon 9 Block 5 booster B1046 seen during both of its post-launch landings. (SpaceX/SpaceX)
- B1047 completed its first successful launch in July 2018. (Tom Cross)
- B1047 seen rolling into 39A’s integration hangar for refurbishment on July 31st. (Reddit – Kent767)
JRTI was spotted by Teslarati photographer Pauline Acalin performing some rare sea trials on November 10 after spending several weeks berthed at port for routine maintenance and deck repairs. Fairing recovery vessel Mr. Steven has also been undergoing some unusual modifications, now proudly sporting what can only be described as a steel horn recently installed on the tip of his bow deck. After sitting out a catch attempt during the launch of SAOCOM 1A to prepare for controlled helicopter drop tests performed over a period of several weeks in October, Mr. Steven will most likely be ready for another stab at operational fairing recovery during SSO-A.
Both rockets – B1047 to the East and (presumed) B1046 to the West – are flight-proven, meaning that they have flown operational orbital missions prior to their upcoming launch attempts, B1047 launched communications satellite Telstar 19V in July 2018, while B1046 has actually performed two successful launches already, Bangabandhu-1 in May and Telkom 4 (Merah Putih) in August.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
News
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
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.
Elon Musk
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
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.
News
Tesla Cybercab has one important piece that AI4 cars might need for FSD
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.






