Connect with us

News

SpaceX reveals Starship “marine recovery” plans in new job postings

Super Heavy on YOUR drone ship? It's more likely than you think! (Richard Angle/Teslarati/SpaceX)

Published

on

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.

Advertisement
-

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.

Advertisement
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.

The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.

Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.

That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.

Elon Musk’s reply to the delay was a single word: “Sigh.”

Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.

Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.

The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.

An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.

Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval

The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.

Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.

Continue Reading

News

SpaceX readies Starship Flight 14 for a historic journey into uncharted territory

SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.

Published

on

By

Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX
Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX

SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.

A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.

Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.


Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.

Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.

The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.

Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”

Continue Reading

Elon Musk

Google just picked SpaceX for its first step into orbital AI

Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.

Published

on

By

Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.

The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.

The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.

MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.

SpaceX and Google mull massive partnership on Musk’s orbital data dream: report

Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.

The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.

Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”

Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.

Continue Reading