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 released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
