News
SpaceX Starlink Gen2 constellation weakened by “partial” FCC grant
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.”
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
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.
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.”
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.
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.
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.
-
Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
