News
SpaceX’s first “next-gen” Starlink satellites are suspiciously familiar
In a strange twist, SpaceX says that its next Starlink mission will launch 54 satellites into low Earth orbit (LEO), implying that they’re roughly the same size as the V1.5 satellites it’s already launching – not the larger V2 or V2 Mini satellites discussed in recent FCC filings.
However, the data SpaceX provided also shows that those 54 satellites are headed to an orbit that only matches the company’s next-generation Starlink Gen2 (V2) constellation. While SpaceX quietly indicated that a V1.5-sized satellite was an option for early Gen2 launches in a supplemental October 2022 filing [PDF] with the FCC, it’s still unclear why SpaceX would prioritize launching V1.5-sized V2 satellites while its V1 constellation remains unfinished.
Adding to the confusion, in November 2021, CEO Elon Musk strongly implied that the inefficiencies of smaller Starlink V1.x satellites were so significant that they could risk bankrupting SpaceX if the company couldn’t start launching larger V2 satellites on its next-generation Starship rocket by the end of 2022. What, then, is the purpose of SpaceX’s imminent “Starlink G5-1” launch?
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
The name alone is confusing. Using the same shorthand as past Starlink V1 launches, “G5-1” refers to the first launch of “Group 5” of a constellation. “Group” here is synonymous with “shell,” which describes a set of satellites that share the same orbital inclination (the angle at which the orbit crosses the equator) and a similar orbital altitude. Of SpaceX’s three approved constellations, only one has five shells, and that shell can only exist at 97.6 degrees, not 43 degrees. SpaceX’s Gen2 constellation technically has nine planned shells, but the FCC has only partially approved three of those shells, one of which is at 43 degrees.
Ignoring the obtuse name, one possibility is that aspects of Starlink V2 satellite upgrades are not explicitly tied to the much larger size of those satellites and can be applied to SpaceX’s first-generation Starlink constellation without requiring a modified FCC license. If SpaceX wanted to add larger satellites to its V1 constellation or change the frequency bands they use, it would almost certainly have to seek a modified license from the FCC, which could take months.
There is no evidence SpaceX has done so, and any attempt would produce public documentation. The 43-degree inclination SpaceX’s mysterious “Starlink G5-1” launch is targeting also rules out any involvement in its V1 constellation, which only has approval for satellites between 53 and 97.6 degrees.
Aside from the unlikely possibility that details about the Starlink 5-1 mission are somehow incorrect or an artifact of a messy launch licensing process, there is at least one other unlikely explanation. In October 2018, the FCC granted SpaceX permission to launch a very low earth orbit (VLEO) constellation of 7518 Starlink satellites with dimensions similar to satellites that make up the 4408-satellite constellation the company is currently launching. More than four years later, SpaceX has yet to begin launching its approved VLEO constellation.
In November 2022, SpaceX told the FCC it intended to combine its Starlink VLEO and Starlink Gen2 constellations by adding V-band antennas to some of the almost 33,000 Gen2 satellites it hoped to launch – a move that would reduce the total number of Starlink satellites SpaceX needs to launch. Around the turn of the month, the FCC partially granted SpaceX’s Starlink Gen2 license, adding unprecedentedly strict requirements and only permitting the launch of 7500 of 33,000 planned Gen2 satellites to a limited set of inclinations (33, 43, and 53 degrees).
Perhaps, then, the uncertainty created by the FCC’s strange partial Gen2 grant made SpaceX change its mind about a dedicated Starlink VLEO constellation. However, without a license modification, SpaceX’s VLEO constellation is stuck with the same smaller (and potentially bankruptcy-inducing) satellites that its CEO believes make the first Starlink V1 constellation unsustainable. SpaceX also has less than two years until its VLEO constellation crosses its first deployment milestone, at which point the company will need to have launched half of it (3759 satellites) to avoid penalties from the FCC – up to and including the revocation of its license.
Despite the numerous reasons it wouldn’t make sense for Starlink 5-1 to be SpaceX’s first Starlink VLEO launch, almost 2500 of SpaceX’s approved VLEO satellites were intended to operate in a 336-kilometer (~209 mi) orbit inclined by 42 degrees – oddly similar to the 338-kilometer (~210 mi), 43-degree orbit SpaceX appears to be targeting with Starlink 5-1.
A surprise VLEO launch is a very unlikely explanation, but it’s only marginally stranger than the alternatives: that Starlink 5-1 is a V1-sized V2 launch with no prior mention or warning, a V1 launch to an orbit that would explicitly violate SpaceX’s Starlink V1 FCC license, or a paperwork error that has propagated so far that SpaceX distributed incorrect orbit information (which could threaten other satellites and rockets) less than two days before liftoff.
Thankfully, there is one last explanation – raised after this article was published – that appears to be much more likely. In response to a tweet summarizing these claims, astrophysicist Jonathan McDowell noted that SpaceX had, in fact, mentioned a third smaller Starlink V2 satellite variant in an October 2022 FCC filing that fell mostly under the radar. In that filing, SpaceX told that FCC it was developing three variants, not two. The smallest variant was said to weigh 303 kilograms and featured dimensions seemingly identical to SpaceX’s existing V1.5 satellites, which are estimated to weigh around 307 kilograms. SpaceX also stated that initial Falcon 9 launches will carry “approximately twenty to sixty satellites,” again confirming that V2 satellites could be about the same size and shape as V1.5 satellites.
SpaceX’s decision to develop a V1.5-sized version of V2 satellites makes little sense in the context of Musk’s implicit claims that problems inherent to its smaller V1 satellites threaten the company’s solvency. It’s clearer than ever that the SpaceX CEO may have been stretching the truth of the matter to craft an existential threat that might encourage employees to work longer hours. Still, developing and launching a V1.5-sized V2 satellite variant and beginning to launch those satellites while SpaceX’s Starlink Gen1 is more than 25% incomplete is confusing at best.
Regardless of what it’s carrying or why, a SpaceX Falcon 9 rocket is scheduled to launch Starlink 5-1 out of Florida’s Cape Canaveral Space Force Station (CCSFS) no earlier than 4:40 am EST (09:40 UTC) on Wednesday, December 28th.
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’
