News
SpaceX Starbase construction takes priority as next orbital Starship, Super Heavy pair come together
As SpaceX teams slowly prepare the first orbital-class Starship and Super Heavy booster for the next-generation rocket’s first full-stack launch, the company has simultaneously begun assembling a second ship/booster pair. However, it’s clear that orbital pad construction remains a priority.
Known as Ship 20 and Booster 4, the two stages of the first orbital-class Starship first arrived at the launch site in early August. Only eight weeks later has Starship S20 finally become the first of the pair to attempt and complete one of two crucial proof tests, opening the door for one or several Raptor static fires in the coming week or two. Meanwhile, Booster 4 has had all 29 of its Raptor engines installed, uninstalled, and reinstalled and twice been placed on and removed from Starbase’s orbital launch mount in the same time frame but has yet to attempt any proof testing.
Despite the apparent delays and challenges slowing Ship 20 and Booster 4’s test debuts and two plodding FAA reviews that appear all but guaranteed to preclude an orbital launch attempt in 2021, though, SpaceX has recently begun assembling a second two-stage Starship.
Save for Starhopper back in 2019, no Starship or Super Heavy prototype has spent nearly as long at the launch site without a single test as Ship 20 and Booster 4 have. To an extent, there have likely been some technical delays while assembling, outfitting, and working with two first-of-their-kind prototypes. Still, the difference between past vehicles like Starship SN15 and Super Heavy Booster 3 are so stark that some portion of the testing delays almost has to be a conscious decision made by SpaceX.
To be able to fully proof and static fire test Super Heavy B4, SpaceX first needs to plumb, wire, and outfit Starbase’s orbital launch mount and complete a majority of the orbital pad’s massive tank farm. However, the orbital pad and its many unfinished systems are situated just a thousand (~300m) east of the suborbital launch site and Starship test facilities, which are complete and ready for testing. To test a Starship at those facilities, SpaceX has to entirely clear the pad of personnel – now several hundred people at the peak of construction – for 6-12+ hours.
The implication is that SpaceX management effectively chose to rip off the bandage now rather than later, sacrificing timely testing of Starship S20 to allow a near-total focus on orbital pad construction and activation over the last ~8 weeks. It’s hard to say if that’s paid off but the fact that SpaceX has chosen this particular moment to begin assembling the next orbital-class Starship and Super Heavy suggests that a clearer plan is starting to come together.
B4/S20, meet B5/S21
Parts of Starship S21 and Super Heavy B5 have been floating around Starbase’s build site for weeks. There was a multi-week period, for example, where the site’s massive high bay was effectively unused – clearly a conscious choice given SpaceX’s history of Starship prototype production earlier this year and late last. Parts of Super Heavy B5 were likely ready for assembly (i.e. stacking) by mid to late August. The ‘mid bay’ used for Starship tank section assembly has been similarly underutilized for even longer – only recently accepting its first Starship S21 section after supporting assembly of the orbital pad’s final storage tank.
Instead, Booster 5 stacking began around September 15th. At the current rate of assembly, which has slowed down considerably in the last week, SpaceX’s second flightworthy Super Heavy could reach its full 69m (~225 ft) height as early as mid-October. Starship S20 likely won’t be far behind. Further, thanks to SpaceX’s preferred style of continuous improvement, Booster 5 and Ship 21 production already appear well on track to outpace Booster 4 and Ship 20. With B5, rather than installing a range of external equipment (avionics, wiring, plumbing) after assembly is finished, SpaceX appears to be completing some of those subsystems during stacking, potentially speeding up final assembly by 1-2+ weeks. With S21, SpaceX has begun outfitting the Starship’s nose cone with heat shield tiles far earlier in the assembly process than it did with S20.
Given that it has taken SpaceX the better part of a month to finish and spot-fix Starship S20’s heat shield since the prototype’s second trip to the test site, taking those lessons learned to heart and getting Starship S21’s heat shield installation right on the first try could cut weeks from final assembly.
In the meantime, after completing Ship 20’s first cryoproof test on September 29th, SpaceX will hopefully be able to kick off the first six-engine Raptor static fire test campaign within the next week or so. With any luck, the start of B5/S21 assembly also means that the orbital launch pad is nearly ready to support Super Heavy B4’s first proof tests, even if static fires with anything close to a full set of 29 Raptors appear to be weeks away. Regardless, it looks like it won’t be long before SpaceX will be juggling two pairs of orbital-class Starships and Super Heavy boosters.
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’
