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.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
-
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
-
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
-
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
-
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
-
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
-
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
-
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
