News
SpaceX considers second Crew Dragon launch pad to reduce risk from Starship
Reuters reports that SpaceX has proposed modifying a second Florida launch pad to support Crew Dragon missions after NASA raised concerns about the threat posed by plans to launch Starship out of the only pad currently certified for Dragon.
After more than a year of downtime, SpaceX restarted the construction of an orbital Starship launch site at NASA’s Kennedy Space Center LC-39A pad in late 2021. SpaceX has leased Pad 39A since 2014 and conducted 49 Falcon rocket launches out of the facility since its first use in 2017. Prior to SpaceX’s lease, Pad 39A supported 82 Space Shuttle launches from 1981 to 2011 and every Apollo Program launch to the Moon in the 1960s and 1970s, making it one of the most storied and well-used launch sites in the history of US spaceflight.
In 2018, Pad 39A began supporting launches of SpaceX’s Falcon Heavy, which was and still is the most powerful and capable rocket currently in operation. In May 2020, a Falcon 9 rocket and Crew Dragon spacecraft lifted off with two NASA astronauts in tow, marking SpaceX’s first human spaceflight and the United States’ first domestic astronaut launch of any kind since 2011. The next era of the historic pad could include Starship, a fully-reusable two-stage rocket that SpaceX has been developing in earnest since the mid-2010s. However, NASA is worried that a failure of that immense and unproven rocket could almost instantly destroy what is currently the only launch pad on Earth capable of launching the space agency’s astronauts to the International Space Station (ISS).
One certainly can’t blame NASA for worrying. In its latest iteration, SpaceX’s Starship 39A launch mount will sit roughly 1000 feet (~300m) East of Pad 39A’s existing Falcon launch facilities, which include a tower and arm that are needed for astronauts and cargo to access and board Crew and Cargo Dragons. The Starship mount is also around 1600 feet (~500m) northeast of Pad 39A’s lone horizontal integration hangar, without which Falcon launch operations would become far more difficult or even impossible.
For the Falcon pad and tower, there is a slight consolation: Starship’s own skyscraper-sized launch tower will be located directly between those Falcon facilities and Starship before and during launches and could partially protect them from any hypothetical blast. The hangar will be fully unprotected, however.
NASA is worried that if a Starship fails before or shortly after launch and explodes at or near its adjacent launch mount, it could destroy or damage the infrastructure the space agency and SpaceX need to launch Crew Dragon to the International Space Station (ISS). At the moment, Boeing – NASA’s second Commercial Crew partner – is likely a year or more away from its first operational astronaut launch, during which Falcon 9 and Crew Dragon will remain a single point of failure that could theoretically sever the space agency’s connection to its own space station at any moment.
In response to NASA’s concern, NASA executive Kathy Lueders – in an interview with Reuters – says that SpaceX has begun working with the agency on plans to both “harden” Pad 39A and modify its Cape Canaveral Space Force Station (CCSFS) LC-40 pad to support Dragon launches. According to Reuters, however, receiving approval to put those plans into action “could take months.” Depending on how significant the facilities LC-40 would need are, there’s also a chance that SpaceX would need to complete a new FAA environmental review to construct a crew access tower.
Meanwhile, Pad 39A is also the only launch pad in the world capable of supporting Falcon Heavy, which has also become an extremely important rocket for uncrewed NASA spacecraft launches, NASA’s plans to get cargo to its lunar Gateway space station, and to the US military. Modifying one of SpaceX’s other pads to support Falcon Heavy would likely be even harder and take even longer than adding Crew Dragon capabilities to LC-40. In both cases, it’s likely that NASA and the US military would strongly prefer – if they don’t eventually outright require – that SpaceX have backup options already constructed and ready to go before risking the destruction of Pad 39A with its first Starship launch.
39A’s Starship facilities could easily require another 6-12 months of work before they’ll be ready for launch, however, leaving a good amount of time for SpaceX to alleviate the concerns of its US government customers before they might actually start to disrupt plans for East Coast Starship launches.
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’
