News
SpaceX’s next Falcon Heavy begins to arrive at 39A as center core heads to TX
Approximately a week after a Falcon Heavy side booster – the first of two – arrived at SpaceX’s LC-39A launch complex, a sign of late-stage preparation for the massive rocket’s second and third launches, a Falcon Heavy center stage was spotted rolling through the Waco, Texas locale on its way to SpaceX’s McGregor testing facilities.
Signified by the outlines of unusual bumps under the Falcon booster’s protective shrink wrap, this probable Falcon Heavy center core’s Texas arrival indicates that SpaceX has most likely completed static fire testing of both side boosters, with the second booster now likely to depart McGregor and/or arrive at SpaceX’s Florida facilities in the coming weeks.
The first component of Falcon Heavy Block 5 has arrived at HLC-39A! https://t.co/38spGaCps9
— Thomas Burghardt (@TGMetsFan98) December 22, 2018
In February 2018, Falcon Heavy took flight for the first time ever, bringing to an end an almost mythical series of delays that pushed the rocket’s debut back more than five years. Aside from the unintentional demise of Falcon Heavy Flight 1’s center core, the inaugural launch was a spectacular and technologically valuable success, perfectly verifying the rocket’s ability to safely ignite, launch, separate, and recover two Falcon 9-class boosters simultaneously. SpaceX also took the opportunity – a payload with no practical value aside from inspiration – to perform a successful six-hour coast of the Falcon upper stage, demonstrating a capability critical for many potentially valuable launch contracts.
Now verified by planning schedules, SpaceX plans to attempt a truly impressive feat in the first half of 2019. Assuming all goes well during the center booster’s static fire and the subsequent integration and static fire of all three first stages, the company intends to launch the same Falcon Heavy hardware (all three boosters) twice in as little as two months, currently tentatively penciled in for February/March and April 2019.
Surprise sighting of a #SpaceX Falcon 9 rocket booster in my hometown headed a few minutes down the road to the McGregor, TX test site. First time in years seeing a booster in transit “in the wild” like this. 🚀 @elonmusk #falcon9 #falconheavy #STEM #bfr #space pic.twitter.com/daEz4NZPi5
— Abby Garrett (@abbygarrettart) January 1, 2019
-
Corroborated a few weeks ago by a NASA official involved in one of the payloads that will be present on that planned April launch, SpaceX plans to attempt recovery of both the side boosters and center core and rapidly refurbish them after their first launch in February or March, nominally placing the 6000 kg (~13,200 lb) Arabsat 6A satellite into a high-energy orbit. Perhaps as few as 4-8 weeks later, the rocket will be reintegrated, perform a second static fire at Pad 39A, and launch once again with a USAF rideshare known as Space Test Program (STP) 2, a program specifically designed to allow the Air Force to support low-risk test launches of unproven rockets.
Even more so than the fact that an ~8-week Falcon Heavy turnaround would simultaneously break SpaceX’s previous booster turnaround record in triplicate, the biggest reason to be skeptical of these plans is the fact that this schedule appears to require that the USAF fly a mission on not one but three flight-proven Falcon boosters. This stands at odds with the military branch’s unwillingness (by all appearances) to so much as allow a brand new Falcon 9 enough propellant margin (typically just a few percent) to land itself after the December 23rd launch of GPS III SV01, let alone allow their satellites to ride on a previously-flown rocket.
-
- Falcon Heavy is composed of a Falcon 9 upper stage and three Falcon 9-class boosters. (SpaceX)
-
- Falcon Heavy’s simultaneous side booster recovery. This will likely be repeated for both Arabsat 6A and STP-2. (SpaceX)
-
- The communications satellite Arabsat-6A. (Lockheed Martin)
-
- The USAF’s STP-2, a combination of a few dozen different satellites. (USAF)
The major wrench in the machine here is the fact that GPS III SV01 most likely cost the USAF upwards of $700M to procure and will ultimately become a critical part of a widespread infrastructural upgrade, whereas STP-2 features two dozen or so small satellites worth dramatically less than the single GPS satellite SpaceX launched last month. STP-2 also operates under a program that is in large part meant to offer opportunities for new or wholly unproven launch vehicles (like Falcon Heavy) to conduct experimental launches, carrying the assumption that certifying those rockets for national security space (NSS) missions would be in the best interests of the Air Force and DoD.
As such, the back-to-back Falcon Heavy launch schedule is by no means impossible despite the fact that it offers up many reasons to doubt its plausibility. Either way, the fact that the next Falcon Heavy’s center core has already left SpaceX’s Hawthorne factory – following in the footsteps of two new side boosters – is a nearly unequivocal sign that the rocket’s second launch rapidly approaching.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
-
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.
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
