News
SpaceX’s Falcon Heavy rocket back in action after a three-year hiatus
Update: The US Space Systems Command says that SpaceX’s first direct launch to geosynchronous orbit was a “simply outstanding” success, safely deploying several satellites more than 36,000 kilometers (~22,400 mi) above the Earth’s surface.
The success of the US Space Force’s USSF-44 mission means that SpaceX’s Falcon Heavy rocket is now one of just a handful of operational rockets in the world that has demonstrated the ability to launch satellites directly to geosynchronous orbit. More importantly, it’s one of just three US rockets with that established capability. The other two rockets – ULA’s Atlas V and Delta IV – will cease to be available for US military missions by the end of 2023, meaning that Falcon Heavy may briefly become the only rocket in the world able to launch certain US military missions until ULA’s next-generation Vulcan rocket is ready to prove itself.
SpaceX’s Falcon Heavy has continued a streak of successful dual-booster landings during its first attempted launch directly to geosynchronous orbit, a mission that was also the rocket’s first launch in more than three years.
Known as USSF-44 and initially scheduled to launch more than two years ago, the US Space Force mission finally lifted off on November 1st, 2022 after relentless payload delays. By mid-2021, the hardware required for SpaceX’s first Falcon Heavy launch since June 2019 – mainly three new first-stage boosters – had finished qualification testing and been shipped to Florida in anticipation of a late-2021 or early-2022 launch. That launch never came.
Only in November 2022 did most or all of USSF-44’s payloads finally come together, resulting in a gap of more than 40 months between Falcon Heavy launches as practically every other payload assigned to the rocket in the interim experience their own significant delays. Regardless, on November 1st, Falcon Heavy lifted off for the fourth time and performed flawlessly for the nine minutes the US Space Force allowed SpaceX’s webcast to continue.
Over the course of those nine minutes, Falcon Heavy’s twin side boosters – both flying for the first time – helped send the rest of the rocket on its way to space before separating from the center core, upper stage, and payload to boost back towards the Florida coast. Less than eight minutes after liftoff, they safely touched down seconds apart at SpaceX’s LZ-1 and LZ-2 landing zones. Lacking grid fins or landing legs, Falcon Heavy’s intentionally-expendable center core (middle booster) continued burning for another 90 seconds and only separated from the upper stage after reaching a speed of almost four kilometers per second (8,900 mph) – a new record for a SpaceX rocket booster.
The center core, B1066, was likely obliterated when it reentered Earth’s atmosphere traveling at approximately 50% of orbital velocity. Side boosters B1064 and B1065, however, will be rapidly refurbished for a “future US Space Force mission” that SpaceX – perhaps incorrectly – says could follow USSF-44 as early as “later this year.” Unless SpaceX has received an additional USSF launch contract in secret, the company’s next USSF mission appears to be USSF-67, which the US Space Systems Command reported could launch as early as January 2023 in their latest press release [PDF]. USSF-44 and USSF-67 are technically set to launch in the same US fiscal year but not the same calendar year.
-
USSF-44 is SpaceX’s first direct geosynchronous launch, meaning that Falcon Heavy is attempting to deliver the US military’s payloads to a circular geosynchronous orbit (GEO) approximately 36,000 kilometers (~22,400 mi) above Earth’s surface. “Geosynchronous” refers to the fact that a spacecraft’s orbital velocity matches Earth’s rotational velocity at that altitude, making it a popular destination for communications and Earth observation satellites that want to observe the same region of Earth all the time. Ordinarily, to simplify the rocket’s job, most GEO-bound satellites are launched into an elliptical geosynchronous or geostationary transfer orbit (GTO) and use their own propulsion to circularize that ellipse.
On a direct-to-GEO launch, the rocket does almost all of the work. After reaching a parking orbit in Low Earth Orbit (LEO), Falcon Heavy’s upper stage likely completed a second burn to geosynchronous transfer orbit. Then, while conducting a complex ballet of thermal management and tank pressure maintenance to prevent all of its cryogenic liquid oxygen (LOx) from boiling into gas and its refined kerosene (RP-1) from freezing into an unusable slush, the upper stage must coast ‘uphill’ for around five or six hours.
Over that journey from an altitude of about 300 kilometers to 36,000 kilometers, in addition to the above tasks, the upper stage must also survive passes through both of Earth’s radiation belts. At apogee, Falcon S2 must reignite its Merlin Vacuum engine for around one or two minutes to reach a circular geosynchronous orbit. Payload deployment will follow and could last anywhere from a few minutes to an hour. Finally, to be a dutiful space tenant, Falcon’s upper stage must complete at least one or two more burns to reach its final destination: a graveyard orbit a few hundred kilometers above GEO.
SpaceX’s third Falcon Heavy launch, a US Air Force mission called STP-2, was a partial dry-run of direct-to-GEO launch – albeit in low Earth orbit (LEO) instead of LEO, GTO, and GEO. During STP-2, Falcon Heavy’s upper stage completed four successful burns in three and a half hours. USSF-44 is significantly more challenging by most measures but not entirely outside of SpaceX’s range of experience. In addition to STP-2, Falcon 9 upper stages have conducted a few long-duration coast tests after completing unrelated primary missions.
In statements made to Spaceflight Now, the US Space Systems Command said that USSF-44’s two main payloads are a pair of propulsive kick stages and payload platforms, one – LDPE-2 – supplied by Northrop Grumman and the other – the “Shepherd Demonstration” – a mystery. LDPE-2 will reportedly carry three hosted payloads and deploy three rideshare satellites: likely two Lockheed Martin LINUSS-A cubesats and Millenium Space Systems’ TETRA-1. All three rideshare satellites are designed to demonstrate various new technologies, ranging from propulsion systems to avionics.
Rewatch SpaceX’s USSF-44 Falcon Heavy launch here.
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
