News
SpaceX ship Mr. Steven renamed ahead of Falcon Heavy fairing catch attempt
In a pleasant, last-minute surprise, SpaceX fairing recovery vessel Mr. Steven has departed Port Canaveral for its first Falcon fairing catch attempt in more than half a year. The speedy ship has already traveled more than 1250 km (800 mi) in ~48 hours and should soon be in position to attempt recovery of Falcon Heavy Flight 3’s payload fairing halves.
In another surprise, Mr. Steven has been renamed to GO Ms. Tree, a strong indicator that Guice Offshore (GO) – a company SpaceX is heavily involved with – has acquired the vessel from financially troubled owner/operator Sea-Tran Marine. With this likely acquisition, nearly all of SpaceX’s non-drone ship vessels are now leased from – and partially operated by – GO. The name change is undeniably bittersweet for those that have been following Mr. Steven’s fairing recovery journey from the beginning. However, it’s also more than a little fitting given that the vessel switched coasts and suffered an accident that forced SpaceX to replace the entirety of its arm-boom-net assembly. Much of Mr. Steven – now GO Ms. Tree – has been replaced in the last few months and with any luck, the vessel is better equipped than ever before to snag its first Falcon fairing(s) out of the air. Falcon Heavy is scheduled to lift off no earlier than (NET) 11:30 pm ET (03:30 UTC), June 24th.
♫ [Mr. Steven] would [sail nine] hundred miles ♫
Not one to dip his/her toes in first, Mr. Steven/GO Ms. Tree’s first fairing recovery attempt since crossing the Panama Canal will be a record-breaker. In yet another last-second surprise, Falcon Heavy Flight 3 – assigned to the US Air Force’s Space Test Program 2 (STP-2) mission – had its center core recovery profile radically modified just days ago, moving the booster’s drone ship landing from ~40 km offshore to more than 1240 km (770 mi) off the coast of Florida.
Given that the upper stage and its fairing-shrouded payload inherently separate after the center stage, after which the two fairing halves are ejected, those fairings will end up even further downrange than the center stage. In the case of Falcon Heavy’s STP-2 mission, the fairing halves could end up splashing down (or, hopefully, landing in a net) anywhere from 1400-1600 km (870-1000 mi) downrange from SpaceX’s Pad 39A Cape Canaveral launch facilities.
Records on records
With a fairing recovery attempt more than ~1400 km downrange and an attempted Falcon Heavy center core landing nearly 1250 km off the Florida coast, Falcon Heavy’s STP-2 mission is chock-full of records. As discussed previously on Teslarati, aside from the surprise recovery records-to-be, STP-2 will be a milestone launch attempt for several additional reasons.
“To successfully complete STP-2, the upper stage will be subjected to ‘four separate upper-stage engine burns, three separate deployment orbits, a final propulsive passivation maneuver, and a total mission duration of over six hours.‘ It will likely be SpaceX’s most technically-challenging launch ever.”
— Teslarati.com, 06/19/2019
“The US Air Force has decided that STP-2 presents an excellent opportunity to begin the process of certifying flight-proven SpaceX rockets for military launches. The STP-2-related work is more of a preliminary effort for the USAF to actually figure out how to certify flight-proven commercial rockets, but it will still be the first time a dedicated US military mission has flown on a flight-proven launch vehicle. Down the road, the processes set in place thanks – in part – to STP-2 and Falcon Heavy may also apply to aspirational rockets like Blue Origin’s New Glenn and ULA’s “SMART” proposal for Vulcan reuse.”
— Teslarati.com, 06/16/2019
In almost every conceivable way, STP-2 will absolutely be the most challenging launch SpaceX has ever attempted. Success would effectively confirm beyond any reasonable doubt that SpaceX is just as capable as – if not more capable than – its sole US competitor, Lockheed Martin and Boeing’s United Launch Alliance (ULA). On top of being able to compete for and perform all mission profiles required by the US military and NASA, SpaceX will also remain the only entity (private or public) in the world that is actively launching, landing, and refusing orbital-class rocket hardware.
Tune in to SpaceX’s hosted webcast around 11:15 pm ET (03:15 UTC), June 24th to watch Falcon Heavy’s third launch ever and (hopefully) catch a glimpse of multiple record-breaking recovery attempts and Falcon S2’s most challenging mission ever.
Want to remember the awesomeness of Falcon Heavy every single day? Consider a limited-edition set of high-quality prints, signed by both Teslarati photographers to commemorate the rocket’s inaugural Starman launch.
-
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
