News
SpaceX’s path to refueling Starships in space is clearer than it seems
Perhaps the single biggest mystery of SpaceX’s Starship program is how exactly the company plans to refuel the largest spacecraft ever built after they reach orbit.
First revealed in September 2016 as the Interplanetary Transport System (ITS), SpaceX has radically redesigned its next-generation rocket several times over the last half-decade. Several crucial aspects have nevertheless persisted. Five years later, Starship (formerly ITS and BFR) is still a two-stage rocket powered by Raptor engines that burn a fuel-rich mixture of liquid methane (LCH4) and liquid oxygen (LOx). Despite being significantly scaled back from ITS, Starship will be about the same height (120 m or 390 ft) and is still on track to be the tallest, heaviest, and most powerful rocket ever launched by a large margin.
Building off of years of growing expertise from dozens of Falcon 9 and Falcon Heavy launches, the most important fundamental design goal of Starship is full and rapid reusability – propellant being the only thing intentionally ‘expended’ during launches. However, like BFR and ITS before it, the overarching purpose of Starship is to support SpaceX’s founding goal of making humanity multiplanetary and building a self-sustaining city on Mars. For Starship to have even a chance of accomplishing that monumental feat, SpaceX will not only have to build the most easily and rapidly reusable rocket and spacecraft in history, but it will also have to master orbital refueling.
The reuse/refuel equation
In the context of SpaceX’s goals of expanding humanity to Mars, a mastery of reusability and orbital refueling are mutually inclusive. Without both, neither alone will enable the creation of a sustainable city on Mars. A Starship launch system that can be fully reused on a weekly or even daily basis but can’t be rapidly and easily refueled in space simply doesn’t have the performance needed to affordably build, supply, and populate a city on another planet (or Moon). A Starship launch system that can be easily refueled but is not rapidly and fully reusable could allow for some degree of interplanetary transport and the creation of a minimal human outpost on Mars, but it would probably be one or two magnitudes more difficult, risky, and expensive to operate and would require a huge fleet of ships and boosters from the start.
The question of how SpaceX will make Starship the world’s most rapidly, fully, and cheaply reusable rocket is a hard one, but it’s not all that difficult to extrapolate from where the company is today. Currently, the turnaround record (time between two flights) for Falcon boosters is two launches in less than four weeks (27 days). SpaceX’s orbital-class reuse is also making strides and the company recently flew the same orbital Crew Dragon capsule twice in just 137 days (less than five months) – fast approaching turnarounds similar to NASA’s Space Shuttle average, the only other reusable orbital spacecraft in history.


While Dragon and Falcon 9 are far smaller than Starship and Super Heavy, Dragon is only partially reusable and requires significant refurbishment after recovery and Falcon 9 boosters are fairly complex. Starship, on the other hand, should effectively serve as a fully reusable all-in-one Falcon upper stage, Dragon capsule, Dragon trunk, and fairing, making it far more complex but potentially far more reusable. To an extent, Super Heavy should also be mechanically simpler than Falcon boosters (no deployable legs or fins; no structural composite-metal joints; no dedicated maneuvering thrusters) and its clean-burning Raptor engines should be easier to reuse than Falcon’s Merlins. Put simply, there are precedents set and evidence provided by Falcon rockets and NASA’s Space Shuttle that suggest SpaceX will be able to solve the reusability half of the equation.
What about refueling?
The other half of that equation, however, could not be more different. The sum total of SpaceX’s official discussions of orbital refueling can be summed up in a sentence included verbatim in CEO Elon Musk’s 2017, 2018, and 2019 Starship presentations: “propellant settled by milli G acceleration using control thrusters.”

On the face of it, that simple phrase doesn’t reveal much. However, with a few grains of salt, hints from what the company’s CEO has and hasn’t said, and context from the history of research into orbital propellant transfer, it’s possible to paint a fairly detailed picture of the exact mechanisms SpaceX will likely use to refill Starships in space. The cornerstone, somewhat ironically, is a 2006 paper – written by seven Lockheed Martin employees and a NASA engineer – titled “Settled Cryogenic Propellant Transfer.” Aside from the obvious corollaries just from the title alone, the paper focuses on what the authors argue is the simplest possible route to large-scale orbital propellant transfer.
In orbit, under microgravity conditions, the propellant inside a spacecraft’s tanks is effectively detached from the structure. If a spacecraft applies thrust, that propellant will stay still until it splashes against its tank walls – the most basic Newtonian principle that objects at rest tend to stay at rest. If, say, a spacecraft thrusts in one direction and opens a hatch or valve on the tank in the opposite direction of that thrust, the propellant inside it – attempting to stay at rest – will naturally escape out of that opening. Thus, if a spacecraft in need of fuel docks with a tanker, their tanks are connected and opened, and the tanker attempts to accelerate away from the receiving ship, the propellant in the tanker’s tanks will effectively be pushed into the second ship as it tries to stay at rest.
The principles behind such a ‘settled propellant transfer’ are fairly simple and intuitive. The crucial question is how much acceleration the process requires and how expensive that continuous acceleration ends up being. According to Kutter et al’s 2006 paper, the answer is surprising: assuming a 100 metric ton (~220,000 lb) spacecraft pair accelerates at 0.0001G (one ten-thousandth of Earth gravity) to transfer propellant, they would need to consume just 45 kg (100 lb) of hydrogen and oxygen propellant per hour to maintain that acceleration.


In the most extreme hypothetical refueling scenario (i.e. a completely full tanker refueling a ship with a full cargo bay), two docked Starships would weigh closer to 1600 tons (~3.5M lb) and the “Milli G” acceleration SpaceX has repeatedly mentioned in presentation slides would be ten times greater than the maximum acceleration analyzed by Kutter et al. Still, according to their paper, that propellant cost scales linearly both with the required acceleration and with the mass of the system. Roughly speaking, using the same assumptions, that means that the thrusting Starship would theoretically consume just over 7 tons (half a percent) of its methane and oxygen propellant per hour to maintain milli-G acceleration.
With large enough pipes (on the order of 20-50 cm or 8-20 in) connecting each Starship’s tanks, SpaceX should have no trouble transferring 1000+ tons of propellant in a handful of hours. Ultimately, that means that settled propellant transfer even at the scale of Starship should incur a performance ‘tax’ of no more than 20-50 tons of propellant per refueling. All transfers leading up to the worst-case 1600-ton scenario should also be substantially more efficient. Overall, that means that fully refueling an orbiting Starship or depot with ~1200 tons of propellant – requiring anywhere from 8 to 14+ tanker launches – should be surprisingly efficient, with perhaps 80% or more of the propellant launched remaining usable by the end of the process.


A step further, Kutter et al note the amount of acceleration required is so small that a hypothetical spacecraft could potentially use ullage gas vents to achieve it, meaning that custom-designed settling thrusters might not even be needed. Coincidentally or not, SpaceX (or CEO Elon Musk) has recently decided to use strategically located ullage vents to replace purpose-built maneuvering thrusters on Starship’s Super Heavy booster. If SpaceX adds similar capabilities to Starship, it’s quite possible that the combination of cryogenic propellant naturally boiling into gas as it warms and the ullage vents used to relieve that added pressure could produce enough thrust to transfer large volumes of propellant.
Last but not least, writing more than a decade and a half ago, the only technological barrier Kutter et al could foresee to large-scale settled propellant transfer wasn’t even related to refueling but, rather, to the ability to autonomously rendezvous and dock in orbit. In 2006, while Russia was already routinely using autonomous docking and rendezvous technology on its Soyuz and Progress spacecraft, the US had never demonstrated the technology on its own. Jump to today and SpaceX Dragon spacecraft have autonomously rendezvoused with the International Space Station twenty seven times in nine years and completed ten autonomous dockings – all without issue – since 2019.

Even though SpaceX and its executives have never detailed their approach to refueling (or refilling, per Musk’s preferred term) Starships in space, there is a clear path established by decades of NASA and industry research. What little evidence is available suggests that that path is the same one SpaceX has chosen to travel. Ultimately, the key takeaway from that research and SpaceX’s apparent use of it should be this: while a relatively inefficient process, SpaceX has effectively already solved the last remaining technical hurdle for settled propellant transfer and should be able to easily refuel Starships in orbit with little to no major development required.
There’s a good chance that minor to moderate problems will be discovered and need to be solved once SpaceX begins to test refueling in orbit but crucially, there are no obvious showstoppers standing between SpaceX and the start of those flight tests. Aside from the obvious (preparing a new rocket for its first flight tests), the only major refueling problem SpaceX arguably needs to solve is the umbilical ports and docking mechanisms that will enable propellant transfer. SpaceX will also need to settle on a location for those ports/mechanisms and decide whether to implement ullage vent ‘thrusters’, cold gas thrusters like those on Falcon and current Starship prototypes, or more efficient hot-gas thrusters derived from Raptors. At the end of the day, though, those are all solved problems and just a matter of complex but routine systems engineering that SpaceX is an expert at.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
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
Musk’s massive Terafab project will get final location soon
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.”
News
Elon Musk reveals SpaceX performed secret Starship test on Flight 13
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.

