News
SpaceX rapidly stacks Starship and Super Heavy with ‘Mechazilla’
For the second time ever, SpaceX has used Starbase’s ‘Mechazilla’ tower and arms to stack a Starship upper stage on top of a Super Heavy booster.
This time around, though, SpaceX clearly learned a great deal from its second February 9th Starship stack and was able to complete the stacking process several times faster on March 15th. During the second attempt, depending on how one measures it, it took SpaceX around three and a half hours from the start of the lift to Starship fully resting on Super Heavy. With Stack #3, however, SpaceX was able to lift, translate, lower, and attach Starship to Super Heavy in just over an hour.
Oddly, SpaceX managed that feat without a claw-like device meant to grab and stabilize Super Heavy during stacking operations. For Stack #2, all three arms were fully in play. First, a pair of ‘chopsticks’ – giant arms meant to grab, lift, and even recover Starships and boosters – grabbed Ship 20, lifted it close to 100 meters (~300 ft) above the ground, rotated it over top of Super Heavy, and briefly paused. A third arm – known as the ship quick-disconnect or umbilical arm – swung in and extended its ‘claw’ to grab onto hardpoints located near the top of Super Heavy. Once the booster was secured, the ‘chopsticks’ slowly lowered Ship 20 onto Booster 4’s interstage and six clamps joined the two stages together.
A few hours after the two were clamped together, an umbilical device located on the swing arm extended and connected to Ship 20. It’s unclear if the panel was actually used in any way but the umbilical is designed to connect Starship to ground systems to supply propellant, power, communications, and other consumables. Regardless, the device did appear to connect to Starship. Prior to Stack #3, however, SpaceX removed both of the swing arm’s ‘claws,’ meaning that it had no way to grab onto Super Heavy. That diminished capability clearly appeared to have zero impact on the ease or speed of the stacking process given that it was completed a full three times faster than Stack #2.
That could imply that the claw is either completely unnecessary or only needed when attempting stacking operations in extreme winds. What is clear is that the claw removal likely only shaved a handful of minutes off of the full stacking process. What really saved time on Stack #3 was a faster lift and fewer pauses throughout – especially while lowering Starship the last several meters onto Super Heavy. During Stack #2, SpaceX took close to an hour and a half to fully lower Ship 20. The same sequence took just ~20 minutes during Stack #3.
Still, after the impressively rapid one-hour stack, it then took SpaceX close to two hours to connect the swing arm’s umbilical to Starship, leaving plenty of room for improvement. Ultimately, assuming SpaceX can speed up the start of the stacking process and replicate its Starship success with Super Heavy, which will also need to be grabbed and installed on an even more complex launch mount, it’s possible that Starbase’s orbital launch integration system is already capable of supporting multiple Starship launches per day. Of course, SpaceX has yet to demonstrate that the orbital launch site can be turned around in a matter of hours after being subjected to the violence and stresses of a Starship launch.
More significantly, SpaceX has never even attempted an orbital Starship launch, recovery, or reuse. That leaves the company in the unusual position of building and testing expensive, specialized support equipment before it actually knows that the rocket that equipment is designed to support is in any way capable of taking advantage of it. For an orbital spacecraft the size of Starship, only the Space Shuttle comes anywhere close and NASA’s all-time record for orbiter turnaround was 54 days. SpaceX has technically flown two Falcon 9 boosters twice in 27 days but no matter how impressive that feat is, reusing a far smaller suborbital booster is vastly easier than reusing a massive orbital spacecraft.
At the end of the day, it’s not really SpaceX’s fault that it’s still waiting for permission to attempt orbital test flights. Nonetheless, the growing gap in maturity between Starship and Super Heavy and the orbital launch site designed to support them continuously raises the risk that SpaceX will have to extensively redesign the rocket, its support equipment, or both if significant problems arise during orbital test flights.
Up next, there’s a chance that SpaceX could attempt to cryoproof Starship while on top of Super Heavy – or perhaps both stages at once. While SpaceX has performed more than half a dozen cryoproofs of Ship 20 and Booster 4 using the orbital launch site’s propellant storage and distribution system, it hasn’t fully tested the hardware needed to route hundreds of tons of propellant hundreds of feet into the air – essential for full-stack testing and launch operations.
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’
