News
SpaceX “intends” to start launching next-generation Starlink satellites in March
In a new Q&A with the Federal Communications Commission (FCC), SpaceX says it still “plans” and “intends” to begin launching the next generation of Starlink satellites as early as March 2022.
In August 2021, SpaceX filed an application modification request with the FCC in a bid to change its plans for the next-generation “Gen2” Starlink constellation, which still aims to drastically improve and expand upon its first few phases. SpaceX filed the first unmodified Gen2 Starlink application with the FCC in May 2020, requesting permission to launch an unprecedented 30,000 satellites. While the size of the proposed constellation is extraordinary, the FCC has also been exceptionally slow to process it. Only five months after SpaceX submitted its Starlink Gen2 modification request and nineteen months after its original Gen2 application did the FCC finally accept it for filing, which means that it has taken more than a year and a half to merely start the official review process.
That extremely slow pace of work could pose problems for SpaceX’s characteristically ambitious deployment schedule.
In a January 7th, 2022 electronic filing in which SpaceX answered a dozen questions from the FCC, the company didn’t outright criticize the extreme sluggishness with which it was reviewing the application but the sentiment was still just below the surface throughout it. After noting that the FCC continues to ask for far more information from SpaceX than it does from other constellation applications, some of which have recently received licenses in spite of that, SpaceX states that it while it “filed its Gen2 Application more than nineteen months ago…and its Amendment nearly five months ago, they were accepted for filing only two weeks ago.”
It’s perhaps no coincidence that that inexplicable delay only came to an end two weeks after FCC Chairwoman Jessica Rosenworcel – who SpaceX notes recently acknowledged a “need to speed the processing of applications to keep pace with…innovation” – was finally confirmed by the US Senate.
Most importantly, though, SpaceX used its extensive Q&A to reveal that it downselected to one of the two similar constellation configurations proposed in its Gen2 application modification. Specifically, SpaceX says it will continue to develop Configuration 1 only, which is designed and organized to take full advantage of the company’s next-generation Starship launch vehicle. That should simplify the licensing process for many Starlink competitors, which have sought to hobble SpaceX’s application with bizarre requests to the FCC and complained ad nauseam about how much of a burden analyzing two potential constellation layouts was for them. Now they will only have to consider one constellation layout, making SpaceX’s Gen2 constellation a more traditional – if still massive – proposal.
Clearly lacking a great deal of self-awareness about the irony of such of a question, the FCC also saw fit to ask SpaceX for “any updates regarding the expected timing of launches for the Gen2 system.” The timing of Starlink Gen2 launches is obviously unequivocally contingent upon FCC approval more than 19 months after SpaceX first submitted an application for said approval. Nonetheless, SpaceX politely answered the question, revealing that it had “informed Commission staff before filing its Amendment” in August 2021 that it “plans to have Gen2 satellites prepared for launch as soon as March 2022” and “still intends to begin launching [Starlink Gen2 satellites] as early as March 2022.”
Many readers and industry followers interpreted this as an implicit claim that Starship will be ready to launch Starlink Gen2 satellites as early as March 2022 – just another of the company’s detached-from-reality schedule estimates, in other words. That’s simply not the case, though. While SpaceX does confirm that it’s settling on a Starlink Gen2 configuration that will explicitly depend upon Starship for the full 29,988-satellite constellation’s timely, cost-effective deployment, FCC deployment and operations licensing are almost inherently unconcerned with how the constellation gets into space. For example, the original Gen2 application SpaceX modified last August never mentioned which launch vehicle would be responsible for launching tens of thousands of satellites. So long as the rocket is compliant with FCC regulations and has an active permit for any given launch, which is also the responsibility of a different bureau, the FCC is effectively indifferent about which rockets launch a given constellation.
In other words, while SpaceX has made it clear that Starlink Gen2 Configuration 1 is optimized for Starship, SpaceX will be free to launch Gen2 satellites on any rocket it wants if or when the FCC approves the constellation. Assuming that Starlink Gen2 satellites will still be able to fit inside a 5.2m (17 ft) wide payload fairing, that includes Falcon 9. Further, in early 2018, the FCC allowed SpaceX to launch the first two Starlink satellite prototypes before it had issued the company a license for the full constellation, making it clear that with the right paperwork, prospective constellation operators can launch and test prototype satellites before their full constellations are approved.
This is to say that there is nothing theoretically preventing SpaceX from again pursuing permission to launch a few prototype Starlink satellites (this time Gen2) before the FCC has finished reviewing and approving the whole constellation. In fact, anything less would actually be surprising and unusual for the company. When SpaceX says in January 2022 that it plans to have Gen2 satellites ready for launch by March 2022, it’s thus not hard to believe that that’s the truth. Perhaps it will take a month or two longer than planned to complete the prototypes, secure temporary FCC approval, and build and license a new E-band ground station, but it’s still believable that SpaceX will be ready and able to launch the first few Starlink Gen2 satellites on Falcon 9 within the next several months. Above all else, unless SpaceX has explicitly designed Starlink Gen2 satellites such that they no longer fit inside a Falcon fairing, nothing is forcing SpaceX to wait for Starship if Gen2 prototypes are ready to launch before the next-gen rocket.
Given that Starship will have to wait until at least March 2022 for its first orbital test flight after FAA review delays, it’s obviously implausible that the rocket will be ready to launch Starlink prototypes by then. Starship S20 – currently said by CEO Elon Musk to be the first space-bound prototype – doesn’t even have a payload bay. Unless SpaceX wants to wait several more months after that to kick off the flight-testing phase of Starlink Gen2 development, it’s likely that the first few satellites will launch on Falcon 9 – either alongside routine Starlink V1.5 launches or on their own.
Turn-by-turn navigation is not new technology.
For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.
Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.
Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.
Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.
But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.
This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.
More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.
It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?
Multiple Data Sources
First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.
Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.
Persistent Learning
FSD seems to struggle with persistent learning from driver interventions.
Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.
This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.
I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.
The next thing I’ve noticed, and this might be controversial, is that Nav has gotten even worse.
I think that might actually be a good thing; Tesla seems to be adjusting it. They just need to adjust it the opposite way.
The car is taking extremely strange routes to very… https://t.co/UHg3tVfNA2
— TESLARATI (@Teslarati) June 16, 2026
Reasoning, Scaling, and Intuition
Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.
Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.
Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.
Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.
Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.
A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”
Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”
🚨 A Tesla Cybertruck, which is illegal to drive in the UK due to safety concerns, has been seized by police in Greater Manchester
“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a… pic.twitter.com/cqhdPok3DM
— TESLARATI (@Teslarati) June 16, 2026
The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.
The Greater Manchester Police Department then added:
“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”
The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.
Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.
A new report claims that Apple is in the process of developing what would be the missing link for Tesla to get CarPlay.
Apple and Tesla have been reportedly working together for some time to give Tesla owners the opportunity to utilize CarPlay within their vehicles. While many owners are more than happy with Tesla’s in-house UI, which is seamless, effective, and smooth, some still want CarPlay, which does have its advantages.
A report from 9to5Mac now states that a new CarPlay technology that was highlighted during the Worldwide Developers Conference (WWDC) would potentially be the bridge between Tesla and Apple. With the addition of a feature known as “Route Sharing,” which gives a navigation app the ability to share routing data with the vehicle, Tesla would be able to launch CarPlay in its vehicles, the report states.
CarPlay has not been a priority for Tesla because it has done extremely well with its in-house UI, but some drivers are just used to it. Additionally, it could improve Tesla’s subpar Navigation or offer improved app capabilities, especially with iMessage.
Route Sharing is an intended addition to CarPlay’s iteration in iOS 26.4, which was released in March:
The addition of CarPlay would undoubtedly be welcome, but at the same time, it seems like Tesla realizes it is not of the utmost priority. There are so many things that Tesla is working on currently within its own vehicles, especially attempting to solve self-driving.
Back in February, Bloomberg had reported that Tesla was still working on bringing CarPlay to its vehicles, but it had not due to app compatibility issues and incredibly low adoption rates of iOS 26.
This bottleneck could buy Tesla the proper amount of time to develop CarPlay for its vehicles. It would be a welcome addition, and could be brought on with either the Summer or Fall 2026 Software Updates.
Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest
Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK
