News
SpaceX rocket catch simulation raises more questions about concept
CEO Elon Musk has published the first official visualization of what SpaceX’s plans to catch Super Heavy boosters might look like in real life. However, the simulation he shared raises just as many questions as it answers.
Since at least late 2020, SpaceX CEO Elon Musk has been floating the idea of catching Starships and Super Heavy boosters out of the sky as an alternative to having the several-dozen-ton steel rockets use basic legs to land on the ground. This would be a major departure from SpaceX’s highly successful Falcon family, which land on a relatively complex set of deployable legs that can be retracted after most landings. The flexible, lightweight structures have mostly been reliable and easily reusable but Falcon boosters occasionally have rough landings, which can use up disposable shock absorbers or even damage the legs and make boosters hard to safely recover and slower to reuse.
As a smaller rocket, Falcon boosters have to be extremely lightweight to ensure healthy payload margins and likely weigh about 25-30 tons empty and 450 tons fully fueled – an excellent mass ratio for a reusable rocket. While it’s still good to continue that practice of rigorous mass optimization with Starship, the vehicle is an entirely different story. Once plans to stretch the Starship upper stage’s tanks and add three more Raptors are realized, it’s quite possible that Starship will be capable of launching more than 200 tons (~440,000 lb) of payload to low Earth orbit (LEO) with ship and booster recovery.
One might think that SpaceX, with the most capable rocket ever built potentially on its hands, would want to take advantage of that unprecedented performance to make the rocket itself – also likely to be one of the most complex launch vehicles ever – simpler and more reliable early on in the development process. Generally speaking, that would involve sacrificing some of its payload capability and adding systems that are heavier but simpler and more robust. Once Starship is regularly flying to orbit and gathering extensive flight experience and data, SpaceX might then be able refine the rocket, gradually reducing its mass and improving payload to orbit by optimizing or fully replacing suboptimal systems and designs.
Instead, SpaceX appears to be trying to substantially optimize Starship before it’s attempted a single orbital launch. The biggest example is Elon Musk’s plan to catch Super Heavy boosters – and maybe Starships, too – for the sole purpose of, in his own words, “[saving] landing leg mass [and enabling] immediate reflight of [a giant, unwieldy rocket].” Musk, SpaceX executives, or both appear to be attempting to refine a rocket that has never flown. Further, based on a simulation of a Super Heavy “catch” Musk shared on January 20th, all that oddly timed effort may end up producing a solution that’s actually worse than what it’s trying to replace.
Based on the simulated telemetry shown in the visualization, Super Heavy’s descent to the landing zone appears to be considerably gentler than the ‘suicide burn’ SpaceX routinely uses on Falcon. By decelerating as quickly as possible and making landing burns as short as possible, Falcon saves a considerable amount of propellant during recovery – extra propellant that, if otherwise required, would effectively increase Falcon’s dry mass and decrease its payload to orbit. In the Super Heavy “catch” Musk shared, the booster actually appears to be landing – just on an incredibly small patch of steel on the tower’s ‘Mechazilla’ arms instead of a concrete pad on the ground.
Aside from a tiny bit of lateral motion, the arms appear motionless during the ‘catch,’ making it more of a landing. Further, Super Heavy is shown decelerating rather slowly throughout the simulation and appears to hover for almost 10 seconds near the end. That slow, cautious descent and even slower touchdown may be necessary because of how incredibly accurate Super Heavy has to be to land on a pair of hardpoints with inches of lateral margin for error and maybe a few square feet of usable surface area. The challenge is a bit like if SpaceX, for some reason, made Falcon boosters land on two elevated ledges about as wide as car tires. Aside from demanding accurate rotational control, even the slightest lateral deviation would cause the booster to topple off the pillars and – in the case of Super Heavy – fall about a hundred feet onto concrete, where it would obviously explode.
What that slow descent and final hover mean is that the Super Heavy landing shown would likely cost significantly more delta V (propellant) than a Falcon-style suicide burn. Propellant has mass, so Super Heavy would likely need to burn at least 5-10 tons more to carefully land on arms that aren’t actively matching the booster’s position and velocity. Ironically, SpaceX could probably quite easily add rudimentary, fixed legs – removing most of the bad aspects of Falcon legs – to Super Heavy with a mass budget of 10 tons. But even if SpaceX were to make those legs as simple, dumb, and reliable as physically possible and they wound up weighing 20 tons total, the inherent physics of rocketry mean that adding 20 tons to Super Heavy’s likely 200-ton dry mass would only reduce the rocket’s payload to orbit by about 3-5 tons or 1-3%.
Further, per Musk’s argument that landing on the arms would enhance the speed of reuse, it’s difficult to see how landing Super Heavy or Starship in the exact same corridor – but on the ground instead of on the arms – would change anything. If Super Heavy is accurate enough to land on a few square meters of steel, it must inherently be accurate enough to land within the far larger breadth of those arms. The only process landing on the arms would clearly remove is reattaching the arms to a landed booster or ship, which it’s impossible to imagine would save more than a handful of minutes or maybe an hour of work. SpaceX’s Falcon booster turnaround record is currently 27 days, so it’s even harder to imagine why SpaceX would be worrying about cutting minutes or a few hours off of the turnaround and reuse of a rocket that has never even performed a full static fire test – let alone attempted an orbital-class launch, reentry, or landing.
Put simply, while Starbase’s launch tower arms will undoubtedly be useful for quickly lifting and stacking Super Heavy and Starship, it’s looking more and more likely that using those arms as a landing platform will, at best, be an inferior alternative to basic Falcon-style landings. More importantly, even if everything works perfectly, the arms actually cooperate with boosters to catch them, and it’s possible for Super Heavy to avoid hovering and use a more efficient suicide burn, the apparent best-case outcome of all that effort is marginally faster reuse and perhaps a 5% increase in payload to orbit. Only time will tell if such a radical change proves to be worth such marginal benefits.
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’
