News
SpaceX’s Mr. Steven returns with Falcon fairing half in net after drop test practice
Captured in a series of photos taken by Teslarati photographers Pauline Acalin and Tom Cross over several days, SpaceX Falcon fairing recovery vessel Mr. Steven and recovery technicians and engineers have been preparing and practicing for a campaign of controlled fairing drop tests.
By using a helicopter to lift and drop a fairing into Mr. Steven’s net, SpaceX will be able to gather an unprecedented amount of data and control far more variables that might impact the success of recoveries. If the fairing is not destroyed in the process, this test series could be as long-lived as SpaceX’s Grasshopper program, used to work the largest up-front kinks out of Falcon 9 booster recovery.
Mr Steven looks ready. Should be leaving port at some point today ahead of SAOCOM-1A launch scheduled for Sunday, Oct 7, 7:21pm PT #mrsteven #SpaceX pic.twitter.com/Hk7HLmMDra
— Pauline Acalin (@w00ki33) October 6, 2018
Although SpaceX technicians managed to reassemble and install Mr. Steven’s net and arm fairing recovery mechanisms in just a handful of days, finishing less than 48 hours before the West Coast launch of SAOCOM 1A, the ship remained in port for the mission, passing up its fifth opportunity to attempt recovery of one of Falcon 9’s two fairings halves. Why exactly Mr. Steven never left port is unclear and unconfirmed, although SpaceX did mention that recovery would not be attempted this time around during its official launch webcast.
The most likely explanation is mundane – sea states with average swells as large as 4m (13ft) were forecasted (and later recorded) at and around the optimal fairing recovery zone. As a Fast Supply Vessel (FSV) explicitly designed to rapidly and reliably resupply oil rigs and other maritime work areas almost regardless of weather conditions, 4m waves would normally be a tiny pittance for ships as large and heavy as Mr. Steven and would be a nonsensical reason to halt deep-sea operations.
-
- Thanks to their relatively high angle of attack, Mr. Steven’s newest arms should not seriously impact his stability, but there is a chance that they limit his operational envelope in high sea-states. (Chuck Bennett)
-
- Mr. Steven seen listing roughly 5 degrees to port during arm installation, July 10th. (Pauline Acalin)
-
- A few-degree list seen during fairing recovery practice, August 13th. (Pauline Acalin)
-
On the other hand, Mr. Steven is without a doubt the most unusual FSV in existence thanks to his massive arms and net, stretching at least 60m by 60m. Based on photos of the arm installation process, significant lists of 5+ degrees are not uncommon when arms are unbalanced during normal staggered (one-at-a-time) installations, and SpaceX quite clearly installs the first two arms on opposite sides and orientations in order to minimize installation-related listing. This indicates that his newest arms have significant mass and thus leverage over the boat’s roll characteristics, perhaps explaining why Mr. Steven has performed anywhere from 5-10 high-speed trials at sea both with and without arms installed.
Most recently, however, Mr. Steven spent a solid six weeks armless at Berth 240 while some sort of maintenance, analysis, or upgrade was undertaken with those four arms and their eight shock-absorbing booms. It’s hard to know for sure, but there are no obvious visual changes between the arms installed in July and August and those now present on his deck, and the net also looks almost identical.
Fairing drop tests?
What’s less familiar these days is an oddly arranged Falcon 9 payload fairing half that has been floating around SpaceX’s Port of Los Angeles berths for the last two or so weeks. Up until October 4th, the purpose of that single half was almost entirely unclear. On October 4th, Teslarati’s entire space team (Tom, Pauline, and I) coincidentally arrived at the same time as 5-10 SpaceX technicians were working on the fairing, attaching a series of guylines and harnesses and inspecting a number of actuating mechanisms on the half.
Just minutes after we arrived, a worker called out a short countdown and a wholly unexpected crashing noise sounded, followed immediately by several loud clangs as the harness connection mechanisms swung back and connected with metallic parts of the fairing. After the adrenaline wore off, the initial crashing noise was almost certainly the sound of the same mechanical jettison mechanism used to separate fairing halves ~3 minutes after the rocket lifts off.
Once photos of the event could be examined more carefully, that was exactly what we found – the six harness connections were attached to the fairing by way of the same mechanical interface that allows two halves to safely attach to each other. What we had witnessed was a harness separation test, using pressurized gas stored in COPVs (the gold striped cylinders) to rapidly actuate a latch, allowing the metal harness connectors to fall away. This is further evidenced by the presence of neon orange zip-ties connecting the ends of those harnesses to any sturdy fairing structure near the connection port, an easy and (presumably) affordable way to prevent those heavy connectors from swinging down and damaging sensitive piping and components.
-
- An overview of the weird fairing test article just before the harnesses were jettisoned. (Pauline Acalin)
-
- Note the taut, yellow ropes connected to the fairing at its original serparation connector ports. (Pauline Acalin)
-
- Zip-ties prevented the harness connectors from smashing (too hard) into the fairing’s innards. (Pauline Acalin)
-
- A Falcon 9 fairing during encapsulation, when a launch payload is sealed inside the fairing’s two halves. This small satellite is NASA’s TESS, launched in April 2018. (NASA)
According to someone familiar with these activities, the purpose of that testing is to prepare for true fairing drop tests from a helicopter. The jettisonable harness would be a necessity for easy drop testing, allowing the helicopter to carry a basic cargo hook and line while technicians inside communicate with the fairing to engage its built-in separation mechanism, all while ensuring that it immediately begins a stable glide or free-fall after dropping.
Observed on October 4th, it was at least moderately disappointing to see Mr. Steven remain in port during the spectacular Falcon 9 launch of SAOCOM 1A, October 7th. Reasons aside, roughly 12 hours after launch, Mr. Steven left on a 10+ hour cruise ~100 miles off the coast, where he repeatedly met up with tugboat Tommy and circled Santa Catalina Island once before heading back to port. Just 24 hours before launch (Oct. 6), the test fairing seen above was placed in Mr. Steven’s net for communications and harness testing – 24 hours after launch, Mr. Steven returned to Port of San Pedro after his 10-hour cruise with the same fairing half resting in his net.
-
-
- Mr. Steven returned to Port of San Pedro around 7pm on October 8th after a day spent at sea, apparently with a Falcon fairing half in tow. This is the second known time that a fairing has been in Mr. Steven’s net. (Pauline Acalin)
-
- An overlay of the paths of travel of a test-related helicopter and Mr. Steven, both on Oct. 8. The yellow plane is the heli at the beginning of a hover, while the gap between blue triangles in the lower left is where Mr. Steven was during that hover. (MarineTraffic + Flightradar24)
How and why it got there is unknown, as is the purpose of half a day spent boating around with the half in his net. However, a helicopter known to be involved in fairing drop tests was seen hovering and flying around Mr. Steven at the same time. Perhaps the two were practicing for real drop attempts, or perhaps the helicopter actually dropped a Falcon fairing (from > 2000 feet) and Mr. Steven successful caught it.
What is clear is that SpaceX is just getting started with efforts to perfect fairing recovery and eventually make the practice as (relatively) routine as Falcon 9 booster recovery and reuse is today. The latter was hardwon and the former will clearly be no easier.
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.
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
