News
SpaceX reveals Starship “marine recovery” plans in new job postings
In a series of new job postings, SpaceX has hinted at an unexpected desire to develop “marine recovery systems for the Starship program.”
Since SpaceX first began bending metal for its steel Starship development program in late 2018, CEO Elon Musk, executives, and the company itself have long maintained that both Super Heavy boosters and Starship upper stages would perform what are known as return-to-launch-site (RTLS) landings. It’s no longer clear if those long-stated plans are set in stone.
Oddly, despite repeatedly revealing plans to develop “marine recovery” assets for Starship, SpaceX’s recent “marine engineer” and “naval architect” job postings never specifically mentioned the company’s well-established plans to convert retired oil rigs into vast floating Starship launch sites. Weighing several thousand tons and absolutely dwarfing the football-field-sized drone ships SpaceX recovers Falcon boosters with, it goes without saying that towing an entire oil rig hundreds of miles to and from port is not an efficient or economical solution for rocket recovery. It would also make very little sense for SpaceX to hire a dedicated naval architect without once mentioning that they’d be working on something as all-encompassing as the world’s largest floating launch pad.
That leaves three obvious explanations for the mentions. First, it might be possible that SpaceX is merely preparing for the potential recovery of debris or intact, floating ships or boosters after intentionally expending them on early orbital Starship test flights. Second, SpaceX might have plans to strip an oil rig or two – without fully converting them into launch pads – and then use those rigs as landing platforms designed to remain at sea indefinitely. Those platforms might then transfer landed ships or boosters to smaller support ships tasked with returning them to dry land. Third and arguably most likely, SpaceX might be exploring the possible benefits of landing Super Heavy boosters at sea.
Through its Falcon rockets, SpaceX has slowly but surely refined and perfected the recovery and reuse of orbital-class rocket boosters – 24 (out of 103) of which occurred back on land. Rather than coasting 500-1000 kilometers (300-600+ mi) downrange after stage separation and landing on a drone ship at sea, those 24 boosters flipped around, canceled out their substantial velocities, and boosted themselves a few hundred kilometers back to the Florida or California coast, where they finally touched down on basic concrete pads.
Unsurprisingly, canceling out around 1.5 kilometers per second of downrange velocity (equivalent to Mach ~4.5) and fully reversing that velocity back towards the launch site is an expensive maneuver, costing quite a lot of propellant. For example, the nominal 25-second reentry burn performed by almost all Falcon boosters likely costs about 20 tons (~40,000 lb) of propellant. The average ~35-second single-engine landing burn used by all Falcon boosters likely costs about 10 tons (~22,000 lb) of propellant. Normally, that’s all that’s needed for a drone ship booster landing.
For RTLS landings, Falcon boosters must also perform a large ~40-second boostback burn with three Merlin 1D engines, likely costing an extra 25-35 tons (55,000-80,000 lb) of propellant. In other words, an RTLS landing generally ends up costing at least twice as much propellant as a drone ship landing. Using the general rocketry rule of thumb that every 7 kilograms of booster mass reduces payload to orbit by 1 kilogram and assuming that each reusable Falcon booster requires about 3 tons of recovery-specific hardware (mostly legs and grid fins) a drone ship landing might reduce Falcon 9’s payload to low Earth orbit (LEO) by ~5 tons (from 22 tons to 17 tons). The extra propellant needed for an RTLS landing might reduce it by another 4-5 tons to 13 tons.
-
Likely less than coincidentally, a Falcon 9 with drone ship booster recovery has never launched more than ~16 tons to LEO. While SpaceX hasn’t provided NASA’s ELVPerf calculator with data for orbits lower than 400 kilometers (~250 mi), it generally agrees, indicating that Falcon 9 is capable of launching about 12t with an RTLS landing and 16t with a drone ship landing.
This is all to say that landing reusable boosters at sea will likely always be substantially more efficient. The reason that SpaceX has always held that Starship’s Super Heavy boosters will avoid maritime recovery is that landing and recovering giant rocket boosters at sea is inherently difficult, risky, time-consuming, and expensive. That makes rapid reuse (on the order of multiple times per day or week) almost impossible and inevitably adds the cost of recovery, which could actually be quite significant for a rocket that SpaceX wants to eventually cost just a few million dollars per launch. However, so long as at-sea recovery costs less than a few million dollars, there’s always a chance that certain launch profiles could be drastically simplified – and end up cheaper – by the occasional at-sea booster landing.
If the alternative is a second dedicated launch to partially refuel one Starship, it’s possible that a sea landing could give Starship the performance needed to accomplish the same mission in a single launch, lowering the total cost of launch services. If – like with Falcon 9 – a sea landing could boost Starship’s payload to LEO by a third or more, the regular sea recovery of Super Heavy boosters would also necessarily cut the number of launches SpaceX needs to fill up a Starship Moon lander by a third. Given that SpaceX and NASA have been planning for Starship tanker launches to occur ~12 days apart, recovering boosters at sea becomes even more feasible.
In theory, the Starship launch vehicle CEO Elon Musk has recently described could be capable of launching anywhere from 150 to 200+ tons to low Earth orbit with full reuse and RTLS booster recovery. With so much performance available, it may matter less than it does with Falcon 9 and Falcon Heavy if an RTLS booster landing cuts payload to orbit by a third, a half, or even more. At the end of the day, “just” 100 tons to LEO may be more than enough to satisfy any realistic near-term performance requirements.
But until Starships and Super Heavy boosters are reusable enough to routinely launch multiple times per week (let alone per day) and marginal launch costs have been slashed to single-digit millions of dollars, it’s hard to imagine SpaceX willingly leaving so much performance on the table by forgoing at-sea recovery out of principle alone.
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
