News
SpaceX’s next Falcon Heavy launch may feature record-breaking center core landing
Thanks to a temporary reopening of the US federal government, SpaceX was finally able to continue the process of filing FCC and FAA paperwork needed to acquire permits for upcoming launches, including Falcon Heavy.
One such filing related to the first operational Falcon Heavy launch has revealed a fairly impressive statistic: comprised of three first stage boosters, SpaceX indicated that Falcon Heavy’s center core will attempt to land on drone ship Of Course I Still Love You (OCISLY) nearly 1000 km (600 mi) away from its launch site, easily smashing the record for the greatest distance traveled by a Falcon booster in flight.
Of Course I Still Love You will be positioned a record ~965km downrange. That's nearly 300km further that the previous greatest distance of 681km, set during the Eutelsat-117WB mission in June 2016. (The landing was a failure, with the booster running out of LOX!) https://t.co/RECKjMtd37
— Gav Cornwell (@SpaceOffshore) January 28, 2019
The same FCC filings also revealed a No Earlier Than (NET) launch date: March 7, 2019. Originally targeted for mid to late February, the complexity and logistical challenges of building, shipping, testing, and delivering two side boosters, a center core, one upper stage, and a payload fairing from SpaceX’s California factory to its Texas test facilities and Florida launch pad unsurprisingly took a small toll on the launch’s aspirational schedule. Nevertheless, if the launch data actually holds to March 7th, SpaceX will not have missed the mark by much considering that this Falcon Heavy – based on new and more powerful Block 5 boosters – is likely a significant departure from the Block 2/Block 3 hardware that has flight heritage from the triple-booster rocket’s Feb. 2018 launch debut.
Just shy of a year after Falcon Heavy’s launch debut, it appears that the rocket’s second and third launches were pushed back by a fundamental lack of production capacity. In other words, SpaceX’s Hawthorne rocket factory simply had to focus on more critical priorities in the 6-9 months that followed the demo mission. At nearly the same time as Falcon Heavy was lifting off for the first time, SpaceX’s world-class production crew was in the midst of manufacturing the first upgraded Falcon 9 Block 5 booster (B1046) and wrapped up final checkouts just 10 days after Heavy’s Feb. 6 launch debut, sending the pathfinder rocket to McGregor, Texas for the first static fire of a Block 5 booster.
In the meantime, SpaceX’s decision to intentionally expend otherwise recoverable reused Falcon boosters after their second launches meant that the company’s fleet of flightworthy rockets was rapidly approaching zero, a move CEO Elon Musk specifically indicated was meant to make room for Block 5, the future (and final form) of the Falcon family. SpaceX’s busy 2018 launch manifest and multiple critical missions for the US government were thus balanced on the success, reliability, and rapid production of a serious number of Merlin engines, boosters, and upper stages. This included B1051 – the first explicitly crew-rated Falcon 9 – and B1054, the first SpaceX rocket rated to launch high-value US military (specifically Air Force) satellites. However, SpaceX also needed to produce a cadre of Falcon 9 boosters capable of easy reuse to support the dozen or so other commercial launches on the manifest.
-
- Falcon 9 B1046 is processed in Port of LA shortly after its third successful launch and landing, December 2018. (Pauline Acalin)
-
- Falcon 9 B1047 is pictured here beneath an upper stage and satellite Es’hail-2 prior to its second launch. (Tom Cross)
-
- Falcon 9 B1048 returned to Port of Los Angeles aboard drone ship Just Read The Instructions after its first launch. July 27. (Pauline Acalin)
-
- Falcon 9 B1049 returned to Port of Los Angeles after its second successful launch and landing in four months. (Pauline Acalin)
-
- Falcon 9 B1050 is seen here just after liftoff. GPS III SV01’s Falcon 9 will feature no grid fins or landing legs. ☹ (Tom Cross)
-
- Falcon 9 B1051 and Crew Dragon vertical at Pad 39A. (SpaceX)
-
That gamble ultimately paid off, with Block 5 performing admirably and supporting a reasonable – if not record-breaking – rate of reuse. SpaceX successfully launched B1054 for the USAF, completed B1051 (now at Pad 39A awaiting NASA’s go-ahead), and built enough reusable Block 5 boosters to support nine additional commercial missions in 2018. In hindsight, barring an assumption of a truly miraculous and unprecedented Falcon booster production rate, Falcon Heavy’s next launches were almost guaranteed to occur no fewer than 6-12 months after the rocket’s launch debut – SpaceX’s entire launch business depended on building 5+ unrelated Falcon 9 boosters, while Falcon Heavy customers Arabsat and the USAF were unlikely to be swayed to launch on flight-proven hardware so early into Block 5’s career.
https://twitter.com/_TomCross_/status/1048483536917823488
All cylinders firing
Once Falcon 9 B1054 departed SpaceX’s Hawthorne factory (see above) in early October, it appears that the company’s production team pivoted directly to integrating and shipping the next three (or more) Falcon Heavy boosters back to back for the rocket’s second and third launches. The first new side booster departed the factory in mid-November, followed by a second side booster in early December and a (presumed but highly likely) center core at the turn of 2019. Both side boosters have been static-fired in Texas and are now at SpaceX’s Florida facilities, while the center core either just completed its Texas static fire testing or is already on its way East.
-
- SpaceX’s Falcon Heavy Block 5 side booster is pictured here in Texas in November 2018. (Teslarati/Aero Photo)
-
- The second (and third) flight of Falcon Heavy is even closer to reality as a new side booster heads to Florida after finishing static fire tests in Texas. (Reddit /u/e32revelry)
-
- SpaceX Facebook group member Joshua Murrah captured the second Falcon Heavy side booster to arrive in Florida in the last month. (Joshua Murrah, 01/17/19)
-
- The next Falcon Heavy’s first side booster delivery was caught by several onlookers around December 21. (Instagram)
-
- A booster – likely the next Falcon Heavy center core – was vertical at McGregor’s S1 static fire stand. (Instagram /u/tcryguy)
-
- A booster – either Falcon Heavy’s next center core or a new Falcon 9 – was vertical at SpaceX’s McGregor, TX test facilities on Jan 28. (Instagram /u/n75sd)
-
- A diagram from a recent SpaceX document offers an idea of what Falcon Heavy Block 5 will look like. (SpaceX)
Once the center core and upper stage make their way to SpaceX’s Kennedy Space Center Pad 39A, the company’s technicians and engineers will be able to integrate the second Falcon Heavy to have ever existed in preparation for a critical static fire test. That could occur as early as February, although the launch debut of Crew Dragon (DM-1) – now NET March from Pad 39A after a relentless string of slips – will likely take precedence over Falcon Heavy and could thus directly interfere with its launch, as the launch pad and transporter/erector (T/E) has to undergo at least a few days of modifications to switch between Falcon 9 and Heavy.
Regardless, the next two Falcon Heavy launches will be well worth the wait. SpaceX’s FCC filings indicate that the center core may travel nearly 1000 km (600 mi) East of Pad 39A to land on drone ship OCISLY after launch, smashing the previous record attempt – during the June 2016 launch of Eutelsat 117WB – of ~700 km (430 mi). That Falcon 9 booster – albeit a less-powerful Block 2 variant – was unsuccessful in its landing attempt, running out of oxidizer seconds before landing. Falcon Heavy’s debut center core also happened to suffer a wholly different but no less fatal anomaly during landing, causing it to miss the drone ship and slam into the Atlantic Ocean at almost half the speed of sound (300 mph/480 km/h).
Looks like early liquid oxygen depletion caused engine shutdown just above the deck pic.twitter.com/Sa6uCkpknY
— Elon Musk (@elonmusk) June 17, 2016
-
Known for their rocket performance estimates, NASASpaceflight forum user “Orbiter” first pointed out the impressive distance – gathered by mapping coordinates included in SpaceX’s Jan. 28th FCC filing – and estimated that the Falcon Heavy center booster flying a trajectory as implied could be traveling as fast as ~3.5 km/s (2.2 mi/s) at main engine cut-off (MECO), the point at which the booster separates from the upper stage and fairing. This would be a nearly unprecedented velocity for any Falcon booster, let alone a booster with plans to land after launch. Falcon 9 MECO typically occurs at velocities between 1.5 and 2.5 km/s for recoverable missions, while even the recent expendable GPS III launch saw F9 S1’s engines cut off around 2.7 km/s.
Whether that MECO velocity estimate is correct, Falcon Heavy’s NET March launch of the ~6000 kg (13,300 lb) Arabsat 6A satellite is likely to be an exceptionally hot reentry and recovery for the center core, while the rocket’s duo of side boosters will attempt a repeat of the debut mission’s spectacular double-landing at LZ-1.
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 claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
