News
SpaceX’s first orbital Starship launch slips to March 2022 in NASA document
A NASA document discussing a group’s plans to document SpaceX’s first orbital-velocity Starship reentry appears to suggest that the next-generation rocket’s orbital launch debut has slipped several months into 2022.
In March 2021, CEO Elon Musk confirmed a report that SpaceX was working towards a target of July 2021 for Starship’s first orbital launch attempt. At the time, it seemed undeniably ambitious but far from impossible. Less than half a year prior, SpaceX had kicked off a series of suborbital Starship test flights to altitudes of 10-12.5 km (6.2-8 mi). Beginning in December 2020, SN8 – effectively the first structurally complete Starship prototype – nearly stuck a landing on its first try, only narrowly falling short due to an engine and pressurization issue.
Less than two months later, SpaceX completed and launched Starship SN9 – again with a nearly flawless six-minute flight capped off with an unsuccessful landing attempt. Starship SN10 followed less than a month later and became the first prototype to land in one piece – albeit only for a few minutes. It was two weeks after that near-success – SpaceX’s third launch in as many months – that Musk revealed a goal of July 2021 for Starship’s first orbital launch. At that point in time, it appeared all but inevitable that SpaceX would be technically ready for an orbital launch before the end of the year.
Two weeks after Musk’s comments and less than four weeks after SN10’s near-miss, Starship SN11 gave one of the worst performances yet, invisibly exploding inside a fogbank well above the ground. However, further stoking the fires of optimism, Starship SN15 debuted a number of upgrades and became the first prototype to successfully launch, land, and survive a ~10km test flight in early May. Put simply, SpaceX built five Starship prototypes practically from scratch in roughly eight months and then completed five test flights in less than five months – all of which were largely successful.
SpaceX considered reusing Starship SN15 or launching SN16 to gain more landing experience but ultimately decided to mothball the prototypes to avoid disrupting orbital launch site construction. Just three months after SN15’s successful landing, SpaceX rolled the first orbital-class Starship and Super Heavy to the orbital launch site and briefly stacked the pair (Ship 20 and Booster 4) to their full height, forming the tallest rocket ever assembled. Although largely a photo opportunity, SpaceX still installed a full 29 Raptors on Super Heavy B4 and six Raptors on Starship S20, further raising confidence that the company’s engine production was already up to the task of supplying the nearly three-dozen needed for a single orbital test flight.
However, for reasons that are less than clear, that August 6th full-stack milestone is about where SpaceX’s H1 2021 momentum appeared to run into a brick wall. Perhaps due to a desire to focus on orbital launch site construction even at the cost of avoiding road closures or testing that would require a clear pad, Starship S20 sat on a stand for the better part of two months before completing even a minor test – by far the longest any Starship prototype has waited.
Seemingly in the midst of its third round of Raptor engine removal, Super Heavy B4 has yet to attempt a single test and it’s unclear how close to ready the orbital pad is to support booster proof and static fire tests. Neither ship nor booster has attempted to static fire its Raptor engines, though S20 could potentially be ready for its first test as early as Monday, October 18th.
Combined with recent developments in the FAA’s Boca Chica environmental review process, the odds of SpaceX attempting the first orbital Starship launch by the end of 2021 have rapidly dropped from decent to near-zero. From a technical perspective, it seems likely that SpaceX could still be ready for an orbital launch attempt just a few months from now. From a regulatory perspective, though, it would be practically unprecedented for the FAA to complete a favorable environmental review and approve even a one-off orbital Starship launch license in ~10 weeks. Even the apparent March 2022 target revealed in a NASA poster focused on the agency’s plans to film an orbital Starship reentry via high-altitude jet assumes that the FAA’s review and licensing process will take ~7 months from August 2021 – still extremely optimistic.
Ultimately, after two months with next to no prototype testing, it’s beginning to look like SpaceX has decided to focus on finishing Starbase’s first orbital launch site, refining vehicle designs, and building new prototypes (B5, S21, S22) rather than pushing hard for rapid B4/S20 testing and an imminent launch attempt. As a result, it’s becoming increasingly unlikely that Booster 4 and Ship 20 will fly as new and improved prototypes like Super Heavy B5 and Starship S21 prepare to overtake them.
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’
