News
SpaceX aces 60th orbital launch of 2022
SpaceX has completed its 60th orbital launch of 2022, marking the first time the company has fully hit a public cadence target set by one of its executives.
By every possible measure, 2022 has been a groundbreaking year for SpaceX even when considering the vast list of achievements it’s racked up over the last half-decade. It owns and operates the largest satellite constellation in history by an order of magnitude. Its Starlink satellite internet service has secured more than a million subscribers less than two years after entering beta. It operates the only routinely reusable orbital-class rockets and orbital spacecraft currently in service. Its Falcon 9 workhorse has launched more in one year than any other single rocket in history. It’s regularly launching at a pace that hasn’t been sustained by any one country – let alone a single company – in 40 years. It’s managing that near-historic cadence while simultaneously recovering and reusing boosters and fairings that represent some 70% of the value of almost every rocket it launches.
And now, SpaceX can also proudly show that it was able to hit a launch cadence target that seemed impossibly ambitious when CEO Elon Musk first shared it nine months ago.
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
Exactly nine months later, SpaceX has just completed its 60th launch of 2022. 69 days after its last orbital-class launch, Falcon 9 booster lifted off for the 11th time with a somewhat mysterious batch of 54 Starlink satellites. A bit less than nine minutes after liftoff, B1062 touched down 660 kilometers (410 mi) downrange on SpaceX drone ship A Shortfall Of Gravitas (ASOG). Seconds prior, Falcon 9’s expendable upper stage reached orbit, shut down its lone Merlin Vacuum engine, and began slowly spinning itself end over end.
Nineteen minutes after leaving the ground, the stack of 54 Starlink satellites was released all at once, slowly spreading out like a splayed deck of cards. Over the coming hours, days, and weeks, those satellites will naturally spread out, deploy solar arrays, stabilize their attitudes, test their payloads, and begin climbing toward an operational orbit somewhere between 480 and 580 kilometers (300-360 mi) above Earth’s surface.
As previously discussed, SpaceX’s so-called “Starlink 5-1” mission raises a number of questions that the company’s launch webcast and communications unfortunately failed to answer. First and foremost, the “5-1” name is nonsensical. The only information SpaceX did disclose about the mission is that it’s the “first [launch] of Starlink’s upgraded network…under [a] new license,” implying – but not actually confirming – that “Starlink 5-1” is the first launch for the Starlink Gen2 constellation.
The orbit the launch targeted only matches one of the Gen2 ‘shells’ the US Federal Communications Commission (FCC) recently approved. Using a naming scheme that’s been consistent for a year and a half, “5-1” implies that the mission is the first launch of Starlink Gen1’s fifth ‘shell’ or group, which the orbit it was actually launched to explicitly makes impossible. It’s very odd that SpaceX did not explicitly call the mission what it actually is: the first launch of an entirely new Starlink Gen2 constellation. The name ultimately doesn’t matter much, but is now likely to create confusion given that SpaceX’s Starlink Gen1 constellation has a fifth shell that may begin launches in the near future.
-
Additionally, outside of a single obscure FCC filing submitted two months ago, it’s long been stated and implied that the Starlink Gen2 constellation’s main advantage over Gen1 was the much larger size of the Gen2/V2 satellites. But the satellites launched on “Starlink 5-1” appear to be virtually identical to all recent Starlink V1.5 satellites, which CEO Elon Musk once suggested were so cost-inefficient that they could risk bankrupting SpaceX in November 2021.
There is one obvious explanation for why SpaceX would launch ordinary Starlink V1.5 satellites in place of the larger V2 variants that will supposedly make the internet constellation more financially sustainable: a desire to add new customers as quickly as possible, no matter the relative cost. While a much smaller V1.5 satellite likely offers around 3-8 times less usable bandwidth than one of the larger V2 variants SpaceX is developing, it may still be true that a V1.5 satellite is better than nothing while larger V2 satellites are stuck behind development delays or waiting on SpaceX’s next-generation Starship rocket.
SpaceX will almost certainly want to replace any V1.5 satellites with V2 satellites when the opportunity arises, but in the meantime, V1.5 satellites launched as part of the Gen2 constellation may technically allow SpaceX to temporarily double the amount of bandwidth available where most people (and Starlink customers) live. Ultimately, that means that it makes a lot of sense for SpaceX to prioritize Gen2 launches. It doesn’t appear that SpaceX will go that far, but the Starlink Gen1 constellation is so far along that the company could easily leave the constellation as-is and prioritize Gen2 Falcon 9 launches for all of 2023 without risking an FCC penalty. SpaceX simply needs to finish its Gen1 constellation before April 2027 to avoid breaking those rules.
Instead, it looks like SpaceX will roughly split its launch and V1.5 satellite manufacturing capacity between Starlink Gen1 and Gen2 moving forward. That will let SpaceX significantly expand bandwidth where most customers live while also finishing the polar-orbiting Gen1 shells that will let the older constellation better serve maritime and aviation subscribers, and reach Starlink’s most remote customers.
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
