News
SpaceX CEO Elon Musk details orbital refueling plans for Starship Moon lander
After a much-anticipated GAO denial of Blue Origin and Dynetics protests over NASA’s decision to solely award SpaceX a contract to turn Starship into a crewed Moon lander, an in-depth (but heavily redacted) document explaining that decision was released on August 10th.
Aside from ruthlessly tearing both companies’ protests limb from limb, the US Government Accountability Office’s decision also offered a surprising amount of insight into SpaceX’s HLS Starship proposal. One of those details in particular seemed to strike an irrational nerve in the online spaceflight community. Specifically, in its decision, GAO happened to reveal that SpaceX had proposed a mission profile that would require as many as 16 launches to fully fuel a Starship Lander and stage the spacecraft in an unusual lunar orbit.
After around 24 hours of chaos, confusion, and misplaced panic, SpaceX CEO Elon Musk finally weighed in on the GAO document’s moderately surprising indication that each Starship Moon landing would require sixteen SpaceX launches.
Confirming many expectations, SpaceX’s solution to sending an entire single-stage Starship to the Moon, landing it on the lunar surface, and returning it to a lunar orbit (and maybe even Earth) goes as follows.
First, SpaceX will launch a custom variant of Starship that was redacted in the GAO decision document but confirmed by NASA to be a propellant storage (or depot) ship last year. Second, after the depot Starship is in a stable orbit, SpaceX’s NASA HLS proposal reportedly states that the company would begin a series of 14 tanker launches spread over almost six months – each of which would dock with the depot and gradually fill its tanks.
Third, once the depot ship is topped off, the actual Starship Moon lander would launch, dock with the depot, and be fully fueled. Finally, the fueled lander would fire up its Raptor engines and head to the Moon, where it would enter a near-rectilinear halo orbit (NRHO) – a weird high-altitude, elliptical orbit only necessary because NASA’s Orion spacecraft and SLS rocket are too underpowered to reach a more normal, functional orbit around the Moon.
After reaching NRHO, Starship would dock with Orion (or vice versa), receive its Artemis astronauts, land on the Moon for several days, and launch back to NRHO to return those astronauts to Orion. After its main mission is complete, it remains to be seen if Starship will have enough propellant left over to return to some kind of Earth orbit, where it could potentially be refueled and reused on future missions to the lunar surface.
In response to GAO revealing that SpaceX proposed as many as 16 launches – including 14 refuelings – spaced ~12 days apart for every Starship Moon lander mission, Musk says that a need for “16 flights is extremely unlikely.” Instead, assuming each Starship tanker is able to deliver a full 150 tons of payload (propellant) into orbit after a few years of design maturation, Musk believes that it’s unlikely to take more than eight tanker launches to refuel the depot ship – or a total of ten launches including the depot and lander.
But, as Musk notes, so long as Starship gets anywhere close to its design objectives, it would be a non-issue even if each Starship Moon lander mission somehow required 16 launches. A step further, assuming that SpaceX proposed 16 launches per mission out of an abundance of conservatism, it’s fair to assume that a 12-day gap between tanker launches is also an extremely conservative worst-case scenario. Per Musk and SpaceX, Starship’s design goals call for multiple reuses of ships and boosters per day. Even if SpaceX falls a full magnitude short of those ambitious goals, Starship tankers should feasibly be able to launch every few days or maybe every week.
But thanks to SpaceX’s relatively conservative proposal, the company now knows that NASA is more than happy with Starship even if it falls something like 50% short of its payload performance goals and two magnitudes short of its reusability goals.
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’
