Connect with us
starlink-1-4-billion-revenue-spacex starlink-1-4-billion-revenue-spacex

News

SpaceX Starlink Gen2 constellation weakened by “partial” FCC grant

Published

on

More than two and a half years after SpaceX began the process of securing regulatory approval for its next-generation Starlink constellation, the US Federal Communications Commission (FCC) has finally granted the company a license – but only after drastically decreasing its scope.

In May 2020, SpaceX filed its first FCC license application for Starlink Gen2, an upgraded constellation of 30,000 satellites. In the second half of 2021, SpaceX amended its Starlink Gen2 application to take full advantage of the company’s more powerful Starship rocket and further improve the constellation’s potential utility. Only in December 2021 did the FCC finally accept SpaceX’s Gen2 application for filing, kicking off the final review process.

On November 29th, 2022, the FCC completed that review and granted SpaceX permission to launch just 7,500 of the ~30,000 Starlink Gen2 satellites it had requested permission for more than 30 months prior. The FCC offered no explanation of how it arrived at its arbitrary 75% reduction, nor why the resulting number is slightly lower than a different 7,518-satellite Starlink Gen1 constellation SpaceX had already received a license to deploy in late 2018. Adding insult to injury, the FCC repeatedly acknowledges that “the total number of satellites SpaceX is authorized to deploy is not increased by our action today, and in fact is slightly reduced.”

That claimed reduction is thanks to the fact that shortly before this decision, SpaceX told the FCC in good faith that it would voluntarily avoid launching the dedicated V-band Starlink constellation it already received a license for in order “to significantly reduce the total number of satellites ultimately on orbit.” Instead, once Starlink Gen2 was approved, it would request permission to add V-band payloads to a subset of the 29,988 planned Gen2 satellites, achieving a similar result without the need for another 7,518 satellites.

Advertisement

In response, the FCC slashed the total number of Starlink Gen2 satellites permitted to less than the number of satellites approved by the FCC’s November 2018 Starlink V-band authorization; limited those satellites to middle-ground orbits, entirely precluding Gen2 launches to higher or lower orbits; and didn’t even structure its compromise in a way that would at least allow SpaceX to fully complete three Starlink Gen2 ‘shells.’ Worse, the FCC’s partial grant barely mentioned SpaceX’s detailed plans to use new E-band antennas on Starlink Gen2 satellites and next-generation ground stations, simply stating that it will “defer acting on” the request until “further review and coordination with Federal users.”

The FCC’s “partial grant” only allows SpaceX to launch 7,500 of 10,080 Starlink Gen2 satellites meant to operate at altitudes between 525 and 535 kilometers.

Throughout the partial grant, the FCC couches its decision to drastically downscale SpaceX’s Starlink Gen2 constellation in terms of needing more time “to evaluate the complex and novel issues on the record before [the Commission],” raising the question of what exactly the Commission was doing instead in the 30 months since SpaceX’s first Gen2 application and 15 months since its Gen2 modification. In comparison, SpaceX received a full license for its 7,518-satellite V-band constellation less than five months after applying. SpaceX’s 4,408-satellite Starlink Gen1 constellation – the first megaconstellation ever reviewed by the modern FCC – was licensed 16 months after its first application and eight months after a modified application was submitted.

Adding to the oddity of the unusual and inconsistent decision-making in this FCC ruling, the Commission openly acknowledges that the idea to grant SpaceX permission to launch a fraction of its Starlink Gen2 constellation came from Amazon’s Project Kuiper [PDF], a major prospective Starlink competitor. The FCC says it agreed with Amazon’s argument, stating that “the public interest would be served by taking this approach in order to permit monitoring of developments involving this large-scale deployment and permit additional consideration of issues unique to the other orbits SpaceX requests.”

The V-band Starlink constellation already approved by the FCC was for 7,518 satellites in very low Earth orbits (~340 km). In the first 4,425-satellite Starlink constellation licensed by the FCC, the Commission gave SpaceX permission to operate 2,814 satellites at orbits between 1100 and 1300 kilometers. Increasingly conscious of the consequences of space debris, which would last hundreds of years at 1000+ kilometers, SpaceX later requested permission in 2019 and 2020 to launch those 2,814 satellites to around 550 kilometers, where failed satellites would reenter in just five years. For unknown reasons, the FCC only fully approved the change two years later, in April 2021.

The “other orbits [requested by SpaceX]” that the FCC says create unique issues that demand “additional consideration” of Starlink Gen2 are for 19,400 satellites between 340 and 360 kilometers and 468 satellites between 604 and 614 kilometers. Starlink satellites are expected to be around four times heavier and feature a magnitude more surface area, but the fact remains that the FCC has already granted SpaceX permission to launch almost 3000 smaller satellites to orbits much higher than 604 kilometers and more than 7500 satellites to orbits lower than 360 kilometers. It’s thus hard not to conclude that the Commission’s claims that a partial license denial was warranted by “concerns about orbital debris and space safety,” and “issues unique to…other orbits” are incoherent at best.

Advertisement
SpaceX has already built a significant number of Starlink Gen2 prototypes.

Perhaps the strangest inclusion in the partial grant is a decision by the FCC to subject SpaceX to an arbitrary metric devised by another third-party, for-profit company LeoLabs. In a March 2022 letter, LeoLabs reportedly proposed that “SpaceX’s authorization to continue deploying satellites” be directly linked to an arbitrary metric measuring “the number of years each failed satellite remains in orbit, summed across all failed satellites.” The FCC apparently loved the suggestion and made it an explicit condition of its already harsh Starlink Gen2 authorization, even adopting the arbitrary limit of “100 object years” proposed by LeoLabs.

In other words, once the sum of the time required for all failed Starlink Gen2 satellites to naturally deorbit reaches 100 years, the FCC will force SpaceX to “cease satellite deployment” while it “[reviews] sources of satellite failure” and “determine[s] whether there are any adequate and reliable mitigation measures going forward.” The FCC acknowledges that the arbitrary 100-year limit means that the failure of just 20 Starlink satellites at operational orbits would force the company to halt launches. The Commission does not explain how it will decide when SpaceX can restart Starlink launches after a launch halt. SpaceX must simultaneously follow the FCC’s deployment schedule, which could see the company’s license revoked if it doesn’t deploy 3,750 Starlink Gen2 satellites by November 2028 and all 7,500 satellites by November 2031.

Based on the unofficial observations of astrophysicist Jonathan McDowell, SpaceX currently has more 30 failed Starlink Gen1 satellites at or close to their operational altitudes of 500+ kilometers, meaning that SpaceX would almost certainly be forced to stop launching Gen1 satellites if this arbitrary new rule were applied to other constellations. The same is true for competitor OneWeb, which had a single satellite fail at around 1200 kilometers in 2021. At that altitude, it will likely take hundreds of “object years” to naturally deorbit, easily surpassing LeoLabs’ draconian 100-year limit.

In theory, the FCC does make it clear that it will consider changing those restrictions and allowing SpaceX to launch more of its proposed Starlink Gen2 constellation in the future. But the Commission has also repeatedly demonstrated to SpaceX that it will happily take years to modify existing licenses or approve new ones – not a particularly reassuring foundation for investments as large and precarious as megaconstellations.

Advertisement

Ultimately, short of shady handshake deals in back rooms, the FCC’s partial grant leaves SpaceX’s Starlink Gen2 constellation in an undesirable position. For the company to proceed under the current license, it could be forced to redesign its satellites and ground stations to avoid the E-band, or gamble by continuing to build and deploy satellites and ground stations with E-band antennas without a guarantee that it’ll ever be able to use that hardware. There is also no guarantee that the FCC will permit SpaceX to launch any of the ~22,500 satellites left on the table by the partial grant, which will drastically change the financial calculus that determines whether the constellation is economically viable and how expansive associated infrastructure needs to be.

Additionally, if SpaceX accepts the gambit and launches all 7,500 approved Gen2 satellites only for the FCC to fail to approve expansions, Starlink Gen2 would be stuck with zero polar coverage, significantly reducing the constellation’s overall utility. Starlink Gen2 likely represents an investment of at least $30-60 billion (assuming an unprecedentedly low $1-2M to build and launch each 50-150 Gbps satellite). With its partial license denial and the addition of several new and arbitrary conditions, the FCC is effectively forcing SpaceX to take an even riskier gamble with the billions of dollars of brand new infrastructure it will need to build to manufacture, launch, operate, and utilize its Starlink Gen2 constellation.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

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.

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.

Continue Reading

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

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.”

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.

Continue Reading

News

Apple is developing the missing link for Tesla to get CarPlay: report

Published

on

Credit: Michał Gapiński/YouTube

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.

Continue Reading