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.
Tesla has introduced an enhanced visualization in its Supercharger navigation system, building directly on the Site Maps feature rolled out a few months ago.
This latest software update adds detailed 3D icons that represent specific vehicle models parked at charging stalls, offering drivers a more precise view of site occupancy and layout.
The Site Maps debuted in Tesla’s 2025 Holiday Update, providing 3D overviews of select Supercharger locations with real-time stall availability.
Tesla supplements Holiday Update by sneaking in new Full Self-Driving version
Drivers could see which spots were open, occupied, or out of service when navigating to supported stations.
Now, the system takes this capability further by rendering accurate representations of Tesla vehicles, including distinctions between models such as the Model 3, Model Y, Model S, Model X, and Cybertruck. These icons appear as lifelike 3D renderings, complete with recognizable shapes and proportions that match the actual cars charging at the site:
Supercharger update now shows type of Tesla at charger as well.
Pretty cool. pic.twitter.com/J3NRSIgM0m
— DennisCW | wen my L (@DennisCW_) June 2, 2026
This refinement improves the user experience during road trips and daily charging stops. As drivers approach a Supercharger, the navigation display now shows not just generic occupied markers but identifiable vehicle types plugged into each stall.
Blue indicators highlight active charging sessions, while other visual cues denote availability or maintenance status. The feature integrates seamlessly with the existing map interface, allowing quick assessment of the best available spot based on vehicle size and positioning.
Tesla continues to expand the availability of these detailed Site Maps across its global network. Initially piloted at a limited number of locations, the rollout has progressed steadily, with more stations gaining support in recent software versions.
Owners benefit from better planning, as the system helps identify compatible stalls and reduces uncertainty upon arrival. The update reflects Tesla’s ongoing commitment to refining its navigation and charging ecosystem through iterative software improvements.
In addition to model-specific icons, the enhanced maps maintain all prior functionalities, such as integration with nearby amenities and energy usage predictions. This ensures a comprehensive tool for efficient Supercharging.
As Tesla’s fleet grows and the network scales, such features play a key role in optimizing the overall ownership experience. Future updates may extend similar visualizations to additional sites and incorporate even more data points for drivers.
With this piggyback enhancement, Tesla demonstrates how small but thoughtful additions can elevate an already useful tool, making Supercharger visits smoother and more informed for its customers. The company is expected to broaden the feature’s reach in upcoming releases, further solidifying its leadership in EV charging infrastructure.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla piggybacks recent Supercharger feature with update that takes it further
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
