RLV Markets VII: Four Models for Commercializing Reusable Launch

It’s been almost a decade since the most recent post in this series, but I’ve had a lot of different things pushing me to want to do a writeup on potential business models for RLV developers. I think that fully-reusable launch vehicles can create economic opportunities far beyond just selling launch services, but because most of the economic value of space is downstream of launch, how RLV companies capture more of that value matters. And I think that some business models will likely do a better job at spreading the benefits of reusable launch to the broader commercial space economy.

Background/Motivation

One triggering event for this blog post was talking with a friend of mine who was trying to get back into the space startup scene after being away for a few years. He was looking for advice on problems to potentially tackle with a new startup. We had discussed one area that I felt desperately needed innovative and competitive new players1, but how one of the key challenges was the high cost of launch, and the challenge of tackling that problem when you have to buy launch retail, and your competitor effectively only has to pay the internal marginal costs. In brainstorming solutions to the problem, I came up with some of the ideas I wanted to write about in this post.

Some other things that have been making me think about this topic include: the SpaceX IPO, rumors that SpaceX is getting out of the F9 rideshare business2, indications that several other competitors are trying to follow Elon’s vertical integration approach between launch and launch-consuming businesses like satellite megaconstellations, rereading “The Rocket Company“, discussions with a friend starting an RLV startup3, etc.

Anyhow, I thought it would be worth talking about a few major approaches that I’ve seen or thought of for how to make money as an RLV developers. I’m sure this won’t be an exhaustive list, but hopefully this both helps get others creative juices going, and also shows people that while SpaceX has a great model, that there may be other ones worth consideration.

Ultimately, these various models revolve around how the RLV developer captures the value created by affordable reusable launch, including how far downstream of launch does the RLV developer participate, and how much control does the RLV developer retain over the launch asset.

Model I: Launch Services Provider

The most basic business model for an RLV developer is to serve as a launch service provider to others. This is probably the most traditional model, and almost all rocket companies, whether expendable or reusable, have had this as part or all of their business model, at some point in their existence. This can be slightly bundled by combining it with other transportation segments, such as what SpaceX and Northrop have done with providing both launch services, as well as commercial crew and/or cargo delivery. But basically, you’re primarily selling transportation services to third party customers in this business model. Sometimes one-off customers who fly irregularly, like smaller GEO commsat operators, sometimes frequent customers who buy in larger quantities, like NASA for commercial crew/cargo, or LEO megaconstellations.

I only have a few observations about this business model:

  • A key drawback of just being a launch provider is that most of the value created in the space industry are captured by launch-consuming applications. Selling transportation services avoids some of the risk of picking the right application and executing well on it, but it also misses out on most of the upsides of success. This is a large part of why it was so hard to get investors to fund launch for so long, as it was unclear if a launch-only company could capture enough value to justify the high up-front investment.
  • When you’re just providing launch services, and aren’t sharing in the upside of the application layer, you really don’t have much incentive to lower prices much beyond what is necessary to capture enough of the launch market4. Especially given the high cost of vehicle development that you need to recoup.

Ultimately, the point of the other three models discussed below is to explore different ways to capture more of the value from downstream application-layer businesses, while simultaneously exposing more of those application-layer businesses to the economic benefits of reusable launch.

Model II: Vertical Integration with the Application Layer

The second model is the one that SpaceX has been proving out, and which I caught the first inklings of in my previous blog post5, of vertically integrating a launch and a launch-consuming application-layer business. Basically, within a single company, you have both a low-cost reusable launch solution, as well as one or more application layer businesses like a LEO telecom mega constellation, or the current craze for orbital data centers. I can see a few different major subvariants of this model type:

Model IIa: Organically Grown Verticalization

This is the approach SpaceX took with Starlink. First, they got a successful partially-reusable launch system going with Falcon 9, and worked out enough of the kinks to get into regular operations. Then they raised a ton of additional money to go after an application layer business with Starlink, which was enabled by the low internal launch costs of partially-reusable F96. While initially risky, they executed well on this, and by the time of their IPO, Starlink was the main revenue-generating, and high-margin part of their business, completely dwarfing the revenue, profits, and value being created by the launch side of their business7. Blue Origin is also looking like they want to take this approach with their Terawave telecom constellation.

Model IIb: Acquisitive Verticalization

The second subvariant of this model is the approach that Rocket Lab seems to be taking. Instead of trying to grow the new constellation entirely from scratch, they’ve recently announced the acquisition of the Iridium constellation. Basically, they’re growing the launch layer internally, but using M&A to buy other constellations that are already operational, licensed, and revenue generating, to start capturing more of the value of the application layer of space. This is partially enabled by Rocket Lab’s past success with acquisitions/integration8, and also enabled by them being a publicly-traded company with access to the kind of capital that can provide.

Model IIc: Reverse Acquisition Verticalization

The final subvariant to this approach is one where an application-layer company purchases a launch company, to bring launch in-house, and start gaining the ability to buy launch at cost, and to not having to compete as much with other customers for launch opportunities. This is the approach that I heard AST Space Mobile has recently explored. At one point a few months back, I heard rumors that one of the other major AI players was kicking the tires on acquiring a launch company to enable going after space-based data centers. This probably works best if the launch company is still a diamond-in-the-rough, as otherwise it could be a pretty expensive acquisition.

Some observations on this business model and its three subvariants:

  • Being able to get your launch at “wholesale” prices9 instead of “retail” prices10 makes a huge difference in the business viability and profitability of an application-layer business. If you’re competing in a market where there are one or more other vertically-integrated competitors, this may be table-stakes for survival. If you’re competing in a market space that doesn’t have vertically-integrated competitors, it’s your “unfair advantage”11 and moat.
  • Vertically integrating with an application layer business is probably the highest risk, but highest payoff business model. You have to raise a lot more capital, you have a lot more technology development, but if you’re successful, application-layer businesses capture an order of magnitude or more value than just launch does.
  • The much higher capital costs of this approach, likely an order of magnitude more than that required to develop just the RLV portion, is true whether you’re growing the business organically, or acquisitively. Though in the case of acquisitive growth, it’s likely easier and cheaper to get money to purchase an existing, profitable partner than it is to raise the money to grow something like that from scratch. And the revenue/profits from that existing line of business hit immediately rather than having to wait for them to grow. But on the flip-side, you’re probably also going to have to deal with more legacy issues and constraints that may make growth from there more involved than with a fresh start. You start at a better position, but you have to pay for it, and your growth rate may be slower for a while until you have fully integrated things, and taken advantage of the new capabilities that being vertically integrated provides.
  • Part of the risk is due to dilution of focus. Not only do you have to become an expert in launch and launch operations, but also in satellite design and manufacturing, and in marketing the satellite-provided services to end-users. The most lucrative space-enabled markets are often the ones that push down closest to the end-user, but that also requires an organization that can handle working with millions or eventually billions of customers. Growing into that is more than twice as hard as growing into being a good launch company.
  • It’s probably going to become increasingly harder to do this play in a specific application-layer business like LEO internet telecoms, once there are already one or two established vertically integrated competitors.

In summary, Model II captures a lot more of the downstream value, but also concentrates the risk to the RLV developer, because of the need for multiple consecutive successes.

Model III: Launch Vehicle Sales

In this model, the RLV developer sells launch vehicles to customers who then operate the RLVs, either for their own launch needs, or for third party launch customers. This is similar to aviation, where companies like Boeing, Airbus, Embraer, and Bombardier manufacture aircraft and then sell them to passenger airlines, cargo transportation companies, and governments and militaries. This is the approach recommended by the book The Rocket Company, which was a semi-fictional/semi-technical book written in 200412 about a group that was trying to develop the first fully-reusable launch vehicle business, with the goal of driving down the cost of space access to open up the space frontier.

In some ways, this is how launch was initially handled by NASA and the Air Force. Contractors would design and built the rockets, then NASA or the Air Force personnel would launch them. They’ve since moved away from that model to purchasing launch services. But I would argue that in a world with reusable launch vehicles, it might be worth revisiting the vehicle purchase/operation approach vs buying a launch service. For a single-use rocket, I can understand why buying the service rather than buying a single-use vehicle could make more sense. But ownership of a reusable launch asset, and its associated launch infrastructure gives you flexibility that just buying a launch service never will. If you’re only ever launch satellites, and don’t have a lot of urgency about when they launch, maybe that distinction doesn’t matter. But in an era of peer adversaries, in-space reuse and logistics, etc. I think people will quickly relearn that there’s a value to owning the capability, and not just hoping you can get a launch slot when you need it.

In some ways you can think of Model III as sort of a mirror image to Model II, where instead of the RLV developer vertically integrating with downstream applications, the application-layer customer vertically integrates upstream by owning its own reusable launch capability. The RLV developer still captures some of the application-layer value, but does so by selling the assets and support services rather than by operating the application-layer business(es) as well.

As with the previous version, there are at least two main subvariants I can think of:

Model IIIa: Vehicle Sales

One subvariant is the case where the manufacturer sells the launch vehicle, launch infrastructure, training, and maintenance parts to multiple operators who handle the launch operations. This could be a megaconstellation developer with a small fleet for launching their own prototypes and operational spacecraft, a launch service spaceline operator, or a military that wants to not just launch satellites, but perform other missions that could benefit from a reusable upper stage.

Model IIIb: Vehicle Wet Leases

The other major subvariant I can think of is one where instead of selling the vehicle outright, the manufacturer leases it to a customer, along with an operational and maintenance crew, which in aviation terms is called a wet lease13. This is sometimes used in the aviation community for when an airline wants to try out a new routes, or fill in gaps or deal with temporary surges in demand.

Some observations for this RLV business model:

  • One of the major benefits of this approach is that the revenue from vehicle sales can hit a lot sooner than the spread-out revenue from launch operations. With a Model I approach, you develop your RLV, then slow start ramping up operations as you dial things in, then start making revenue back as you grow market share, etc., only really making your money back several years later. With a Model III approach, the vehicle manufacturer makes revenue from vehicle sales as soon as the sales hit, which can often be long before the operator has ramped up operations, or gotten into a regular cadence. And for an operator, they only have to pay for the vehicle once development is done and it’s ready to be handed over, rather than having to invest money for half a decade or more till the vehicle even shows up, and then keep investing for a year or two or three while launch cadence ramps up.
  • Additionally, since this is a reusable, tangible asset, operators can likely purchase them using financing, rather than having to equity-finance things. This can have a much lower cost of money, and so long as it’s paired with adequate insurance, allows you to spread the cost of ownership out over the lifetime of the launch vehicle.
  • If an RLV’s sales price can be kept around the cost of buying a jet aircraft, it’s quite plausible to be hitting $B/yr revenue streams within a year or two of when the first vehicle enters service. Trying to ramp up to that revenue rate via launch service sales could easily take 5+ years after the first successful flight.
  • It’s worth mentioning that in addition to airlines and sea vessels, this approach of the builder selling the asset to an operator is also very common in commercial real-estate. The company that manages a high-rise tower, and works with the tenants is often not the company that built the tower. Building and operating and working with customers are very different skillsets, and like in the first bullet-point, being able to sell the asset to an operator means the builder gets a faster return on investment, and the operator doesn’t have to have their capital tied up for as long before they can start making revenue either.
  • Like aviation though, I think a sale or wet lease approach to launch vehicles will only work if the manufacturer can sell into an international market. Which will mean working closely with export control agencies like the State and Commerce Departments in the US, to make sure that things are handled in a way that align well with export control licensing processes. If I were running a company taking one of these approaches, I’d have someone almost from day one, who has the thankless job of navigating that morass. Ultimately though, we regularly sell advanced military equipment to friendly countries around the world, so this should be a navigable morass, but one that should be taken seriously from day one.
  • Part of the reason for suggesting the wet lease model is that it might be easier to get export approval for that initially, since the personnel directly working on the RLV operations and maintenance would still be citizens of the original country.
  • In addition to business considerations, I think that a launch vehicle designed for vehicle sales/leases is going to have very different requirements and optimizations from one that is always intended to be operated by the vehicle developer (as in Models I and II). Since the longevity of the asset is critical for the economics to work, I think this will drive a much higher requirement for reliability and intact abort capabilities, ease of operations and maintenance, simplicity of ground support equipment, etc. Raw performance will probably be less important than those other aspects.
  • One trend that has been explored a little in the expendable small launch market has been “sovereign launch” capabilities, where a launch provider sets up launch facilities in another country like the UK, or Australia, allowing them to buy there way into launch capabilities that they have more control over. My guess is that this will likely be even more palatable for countries if they were able to own a reusable vehicle, and control launch operations domestically, at their own pace. I could see several secondary space powers buying their way into this sort of capability, and rapidly having more launch capacity than many first-tier space powers had only a few years ago.
  • Training, and the ability to work with multiple launch operators who are not directly controlled by your company will also be a critical skill.
  • While an optimal RLV won’t necessarily look or operate anything like an aircraft, I think you’ll likely find that a lot of the skillsets needed to make this sort of a business model work can be found in the aviation and shipbuilding industries.
  • Of all of the models discussed, this one is the one most likely to create low launch prices to third-party customers. Because anyone can buy a vehicle and offer the services, there will likely be fierce competition, which is more likely to drive down launch prices than a world where most reusable launch capacity is tied up in Model II launch businesses.

Model IV: Equity-Linked Launch Partnerships

The final major class of model I came up with is one where the RLV developer forms an agreement with another entity exchanging equity in the customer company in exchange for them gaining access to “wholesale” launch prices. Unlike in Model II, the launch-consuming customer isn’t fully owned by the launch developer/operator, but because the launch developer/operator has a non-trivial equity stake in the launch-consuming entity, it becomes in their interest to sell launch services closer to the marginal cost than they would for a purely third-party launch customer. I can see at least two main subvariants for this model, though there likely are more.

Model IVa: Spinout Launch Partnerships

The original idea came from hearing stories from Dave Masten about the Silicon Valley startup he had been working at prior to starting Masten Space Systems. This company, Andiamo Systems, was spun-out from Cisco to explore a new storage area networking business, in a more startup-like environment than could be done inside Cisco. Cisco infused initial capital, and provided some support services/incubation, and they had a deal with Andiamo that would give them the right to acquire and spin the company back in if Andiamo was successful, which they ultimately did, and which ultimately is where Dave got the money he needed to start MSS. I’m not coming from the Silicon Valley tech ecosystem, so I had to look up some details, but apparently Cisco used this approach several other times, though not without some controversy14.

My thinking for how to apply this to the RLV industry is that if you have a company like Stoke, or Radian, or Sagittarius developing RLVs, there are a lot of application-layer markets they could go after. But they can’t really afford the distraction or funding dilution of going after too many of those until they’re most of the way through RLV development. And even once they get there, it’s unclear which of those markets will really take off, and they only have so much bandwidth to chase them. They could try a Model II approach like mentioned earlier where they try to own the whole pie, or they could try spinning out one or more startups focused on those application markets. In exchange for a significant equity stake in the new startup, the new startup would have a deal for accessing the launches at some highly discounted rate, maybe only modestly marked-up from the RLV developer’s marginal launch costs. Because they can now get costs at a price point that is potentially competitive with or at least close to Model II companies like SpaceX, and dramatically cheaper than anyone doing an application-layer company that isn’t vertically integrated, they have a competitive advantage. It’s both cheaper to developer their launch-consuming application-layer business (by accessing cheap and frequent access to space), but when they go to scale, they also don’t need as much capital to scale, and their unit economics will be better. The RLV developer wins because multiple other companies are better able to attract capital sooner to start using their vehicle on a repeat basis, and they get to see which markets pan out. For those that are successful, they might have some sort of Cisco-esque spin-in agreement that would allow them to convert into a Model II company, but a lower risk, and with less distraction and dilution of the original company.

Model IVb: External Equity-Linked Launch Partnerships

The name is clunky, but the other variation on the theme I could think of is a situation where a non-spin-out company, whether a new startup founded by someone outside of the company, or an existing company trying to improve their unit economics, approaches an RLV developer and offers a non-trivial equity stake in their company in exchange for a similar wholesale/near-marginal cost launch pricing deal. This might or might not include a “spin-in” pre-agreement like in Model IVa. But basically the idea is that the RLV developer gains a share in the upside from a new launch-consuming market, and the launch-consuming customer in exchange gains access to more competitive launch pricing.

Some observations on this final model:

  • This approach can allow for much more rapid development of launch-consuming application-layer businesses than the Model II approach, where it may be hard to raise money for the new market area until the RLV is far into development.
  • There are a lot of markets that are marginal if you have to buy launches at full retail prices, but which can be a lot more lucrative if you could get pricing at near-marginal costs15. Having access to the lower cost launch enables both charging a lower price to your customers, thus hopefully triggering demand elasticity, while simultaneously having healthier margins on your service.
  • Under Model II, most RLV developers can only afford to try one new launch consuming market at a time, if they’re successful, they capture more of the value, but there’s a higher risk of picking the wrong application-layer market. Whereas this Model IV enables trying out several potential application-layer markets simultaneously with different partners, and only doubling down on the successful ones.
  • This approach is more complicated from a business standpoint than the other models, with lots of details to be thought through such as: What should the discounted launch price be? If it’s tied to internal cost, how do you not create perverse cost-plus like incentives? What is the right trade between equity stake and discount price? The RLV developer will have a healthier balance sheet as the value of their stake in the launch-consuming partner’s company grows, but they’ll have less revenue — how do they strike that balance? How do they make sure they’re still profitable, while still offering an enabling launch price to their partner, especially in a situation where a non-trivial part of their launch demand is coming from equity partners through models like this? If launches for this customer are less revenue lucrative for the RLV developer than third-party launches, how do you juggle demand between them and other customers? How do you guarantee enough launch availability to be useful?
  • One big challenge if the RLV developer is selling to the government, is that they have rules that require them to be given the best price you offer to others for a similar product or service. I have some ideas for how this could be handled, but this will have to be careful navigated.

This one is definitely the least thought-through of the four models, so I’d be interested in feedback on the approach and how to refine it.

Hybrid Models

One last thing to mention is that RLV developers can use different models and different combinations of models at different stages in their lifecycle. For instance, most companies may choose to start with Model I to get started, but can transition into Models II and/or IV as they mature. A Model II company could decide that for markets outside of a core focus area, that they’d rather support Model IV ventures rather than going all-in on those other application-layer markets, or ignoring them completely. A company selling vehicles, could also wet lease some of them, and use the wet lease approach to enable Model IV partnerships.

Conclusions

My goal in writing this was to try to show that in a world of fully-reusable launch vehicles, there are more potential business models than are commonly discussed, and that the key business model questions are how an RLV developer chooses to capture value, and how much of the benefit of affordable launch do they make available to others.

While I love what SpaceX has done, I want to see a thriving marketplace, and worry that a world where all of the good launch is tied up in Model II silos, will be less exciting and dynamic than one where broader groups can access the cost savings due to reusability. Maybe enough RLV companies will be successful to drive down third-party launch costs to the point where the complexity of alternative business models won’t be worth it, but I think that future is more likely if people think more creatively about RLV business models. I particularly hope that we can see some people try alternative business models like Model III or Model IV, both of which I think are more likely to lead to healthier, more dynamic and competitive space ecosystem, than one dominated by a few siloed Model II juggernauts.


  1. Commercial crew launch, where currently SpaceX has no competent competition, and NASA seems to be trying really hard to encourage me to finish writing my Starliner Reponendum Est blog series. ↩︎
  2. Handing it over to rideshare aggregators like SEOPS, Exolaunch, and others willing to buy a full launch and handle the rideshare cat-herding. ↩︎
  3. After leaving Astrobotic last year, Dave Masten and a few other Masten alumni started Sagittarius Space Logistics. Definitely one I’m going to keep an eye on. ↩︎
  4. Notice for instance that while SpaceX started out with significantly lower prices for Falcon 9 than ULA started at with its EELVs, once ULA lowered its prices a little with Vulcan, SpaceX’s prices have basically stayed steady, with yearly increases for inflation. While the $/kg has improved a little over time as F9’s performance increased, it’s now almost $75M to buy a Falcon 9. Most of the dramatic cost savings from reuse aren’t passed on to third party launch consumers, because SpaceX doesn’t yet have competent competition for third-party launches. ULA unfortunately doesn’t really count. Hopefully this changes as Rocket Lab, Stoke, Firefly, and Relativity all have shots-on-goal in the near future. ↩︎
  5. Starting around the fourth paragraph in. I definitely miscalled some of the details in earlier paragraphs in that post, in part due to bad luck/decisions on OneWeb’s part causing them to declare bankruptcy during the pandemic when the initial market freekout happened to coincide with their latest fundraise. Honestly, if they had either closed that round two months earlier, or if they had needed to close it two months later, they likely could’ve avoided the bankruptcy, and likely could’ve finished launching their constellation before Russia invaded Ukraine in 2022 (which created more delays while they had to pivot their launch solution). ↩︎
  6. Also enabled by Elon’s almost inhuman ability to get investors to put insane amounts of money into his companies at eye-watering valuations that almost nobody else could’ve pulled-off at a similar stage in their business’s operations. His fundraising abilities is probably one of his strongest superpowers as an entrepreneur. ↩︎
  7. I don’t have the exact numbers at hand, but one analyst said something to the effect that if SpaceX had only been a launch company, launching as often as they currently are, at the revenue they’re capturing from that, and the profitability they’re seeing, they’d likely only be worth $10-20B right now. With Starlink, they could easily justify a $500B+ valuation. Most of the $2T IPO valuation was a bet on the future of AI, and Elon’s ability to capture a huge share of that value. I’ll be honest and say I’m not convinced about the AI part of his business, and think the valuation is premature. Maybe they’ll grow into it, but man this feels like a bubble (to this guy who has accurately predicted nine out of the past three market downturns). ↩︎
  8. Honestly, of all of the companies doing significant space M&A recently, they’re one of the only ones who have shown real competence at this. They’re one of the only groups that has retained a significant fraction of the entrepreneurial talent from the companies they’ve bought, they’ve shown a great ability to find good complementary businesses that open them up to new markets where the whole is greater than the sum of the parts. ↩︎
  9. At or near the marginal internal cost of the launch. ↩︎
  10. Having to pay the going rate for third-party launch customers. ↩︎
  11. Gemini’s definition of the term sums it up reasonably well: “An unfair advantage in entrepreneurship is a special trait, asset, or background that a company or founder has which cannot be easily copied, bought, or surpassed by competitors. It creates a powerful barrier to entry, ensuring that competing against you is remarkably difficult.” ↩︎
  12. I.e. written long before SpaceX had successfully flown a rocket, let alone become anything like the juggernaut it is today. ↩︎
  13. I think it was my friends at XCOR who got me first thinking about this business model for RLV operations. They had been exploring this approach for Lynx suborbital flights in friendly foreign countries, as an alternative to just selling flight services, and an easier to license alternative to selling vehicles. ↩︎
  14. Apparently, many of the employees who stayed behind at Cisco were resentful of having colleagues leave to a startup that was heavily backstopped/derisked by Cicsco, and then get the chance to reap the rewards and become multi-millionaires a few years later. Definitely sounds like something that is promising, but needs some refinement to not piss off those who stay behind. ↩︎
  15. Some examples I can think of include: crew/cargo delivery to commercial LEO destinations, space tourism in general, OTVs, internet telecom and D2D megaconstellations, orbital data centers, and there are probably several others. ↩︎
Posted in Business, Commercial Crew, Commercial Space, Economics, Entrepreneurship, Launch Vehicles, MSS, RLV Markets, Space Development, Space Transportation, SpaceX, Uncategorized | Tagged , , , , , , , , , , | 6 Comments

The Cost of Skipping Bases

A few years ago I did a post suggesting that Starship skipped a base or two in development. Going for the biggest launcher in history with new engine types, burning a new propellant combination, novel landing techniques, and going for complete reusability all in one shot on vehicle one being an extreme gamble. One of my points being that there was no market appropriate to the projected flight rate and fleet size of Starship not to mention the huge cargo capacity. Second Guessing Starship | Selenian Boondocks

Some of my points have been answered, though not in the manner I expected. The record-breaking IPO was heavily influenced by the projected capabilities of Starship and orbital data centers. Million sat orbital data centers never crossed my mind, or that of anyone else that I know of. That potential market makes more sense than Mars colonization from a business standpoint. Though I know nothing about data centers or their potential profitability, many investors apparently do.

In the Second-Guessing post, I suggested that SpaceX would have been better served by going with a smaller vehicle building on the well-known methods of the Falcon9. Falcon Raptor for that post. The water tower was flying in 2019, and the flip flights by 2021. I suggested then that if they had gone with a Falcon9 layout and operational technique, that vehicle would have been operational and matching Falcon9 tempo by 2022. Falcon9 has flown several hundred times since then.

In 2022, I mentioned that some people were certain that Starship would be operational in a year (2023), while some were saying end of decade. Not to mention those saying never. (Oler, Church) or those projecting a massive ramp up to thousands (Eagleson, David, etc) annually by now. Those of us saying somewhere between the extremes didn’t have much of a following.

With almost 4 years since that post, and with Starship flight 13 scheduled in a few days, I’ll try to make the case for a smaller and simpler precursor vehicle as it relates to Starship and the IPO.

The Raptor engine is the key to Starship success. It has considerably more Isp that Merlin, a thrust/weight at least as good, and burns a cleaner fuel that is also much cheaper than RP1 kerosene. The cleaner is the key point as it should lead to far less maintenance between flights. Cheaper is important, but less so. The higher Isp is good on the vacuum engines compared to Merlin, but really shines on the sea level units with a 50 point jump.

A Falcon9 layout with Raptor engines would necessarily be wider, probably 5-7 meters in diameter. That would allow the height to match some of the Falcon9 access points on the launch towers so that total rebuilds wouldn’t be required. New Glenn class except with an organization that MOVES. With over double the thrust of the Merlins and higher Isp, payloads should be well over double that of the kerosene Falcon9.

The critical thing though is the cleaner operation of the engines. A Raptor Falcon in either RTLS mode or returning on a barge should have turnaround times a fraction that of Falcon9 due to not having soot clean up. Also Raptor supposed to have been designed and built with low maintenance and fast turnaround. Falcon9 has a cadence of over 150 flights a year for the last three years. If Raptor is as good as most of us think, Raptor Falcons would be at double or more of that flight rate.

How does this relate to Starship, data centers and the record-breaking IPO? If the Raptor Falcon (or whatever a proper name would be) were flying hundreds of times per year for the last few years, there would be an experienced team on the ground that knew fast paced methane vehicle operations inside and out. That experience would have been feeding into the development of Starship for the last several years. It seems very likely that Starship would not only be further along but also would have left far less hardware in the deeps of the Gulf and the Indian Ocean. Excess capacity to date could have already tested in orbit refueling, prototype data centers, and a Mars flight or two.

So if you were an investor, wouldn’t you be more impressed with a high flight rate vehicle delivering up to 40 tons a shot on a daily basis and a Starship entering operability already with flight 5 or 6? Or with flight 14 hoping to be the first orbital? And the same company retiring the most successful launch vehicle in history (Falcon9) because it was so much more expensive to operate than the Raptor Falcon?

Posted in Uncategorized | 4 Comments

Happenings Elsewhere In the Goffosphere

A few years ago, I split off two separate blogs, to try and keep Selenian Boondocks focused more on space, technology, and policy. I have my personal blog (Taong Boondocks) that is focused on a mixture of politics and government, religion, recipes, personal accountability on goals, and other stuff that I thought would be a distraction from the core audience on this blog. I also created a blog for my consulting LLC (Starbright Engineering blog). The consulting LLC is in hibernation mode, but I’ve been using that for blog posts specifically related to satellite servicing policy and technology. Given that there are some people here who might be interested in some of those other topics, I thought I’d crosspost a few of my major posts this year from those other blogs:

While Chris and Kirk have been holding down the fort here on Selenian Boondocks, I do still intend to do some posts soon, likely finishing off my Starliner Reponendum Est series, and maybe one on some random thoughts on RLV business models.

Also, on a personal update side, for those who haven’t been following me on Twitter/Facebook, my two oldest sons (of Jonny-Bloggin and Jimmy-Bloggin fame) are now serving full-time missions for our church out in Los Angeles and Louisiana respectively. I’ll probably start posting more about them periodically on Taong Boondocks.

Posted in Administrivia, Family, Politics, Starbright | 2 Comments

Human colonies floating in the clouds of Venus

Last time I talked about how successful human colonies would likely need to begin with an existing culture. This time I’d like to talk about one of the places that humans might wish to colonize, and it is the first post in a series about Venus that I have wanted to write for a long time. What would it take to make the surface Earth-like, what would it take to live there before we make it Earth-like? I think Venus deserves more attention than it gets for three simple reasons, gravity, pressure, and temperature.

The series will get to the terraforming engineering eventually, including things like energy budgets, propulsion problems, orbital mechanics, parasols and solettas and electromagnetic spin-up motors. All of that good stuff eventually. But first I want to talk about where humans can actually live, right now, with the engineering capabilities we have or could plausibly develop in the next century.

That place is Venus. Not the hellish surface of course—which is at a temperature of 737K/464C/867F under 95 bars of carbon dioxide—but the cloud layer, at 50 km altitude.

This was an extremely fringe view for a long time, but less and less as people seriously think about it. NASA Langley spent two years on the High Altitude Venus Operational Concept (HAVOC), a phased mission architecture built around floating habitats. Geoffrey Landis published the modern technical case in a 2003 NASA paper that is still the canonical reference. The Soviets were working on atmospheric Venus habitation concepts in the 1970s. Paul Birch’s 1991 paper, which we will spend several posts on later in this series, treats floating colonies as the primary human habitat throughout the centuries-long terraforming process. The case has been in the literature for half a century. The popular conversation just has not caught up to it, so let’s plunge in.

The 50 km altitude

Venus’s atmosphere falls off exponentially with altitude. The scale height depends on local temperature, varying from about 16 km at the surface (where T = 737 K) to about 6 km at the cloud deck (where T ≈ 290 K). The 95 bar surface pressure drops by a factor of about 95 over the first 50 km of altitude, working out to a column-averaged scale height of around 11 km. At 50 km altitude you reach 1 bar of pressure, which is almost exactly Earth sea level, and temperatures between 0 and 50 degrees Celsius depending on local time and latitude. Climb another 5 km and the temperature drops into the 20s. A spring day, in other words.

Gravity at this altitude is essentially Venus’s surface gravity, 8.87 m/s², or 0.904 g. That is meaningfully lower than Earth gravity — about 10% less, which is much larger than the 0.5% variation humans experience between the equator and the poles, or between sea level and the top of Everest. We do not know exactly what 0.904 g does to the human body over decades and generations, because we have no data points between 1 g and zero. But the deficit is small. Mars at 0.379 g and the Moon at 0.166 g are dramatically further from Earth gravity than Venus is. If there exists a habitable gravity range for long-term human life with some lower bound, Venus’s 0.904 g is almost certainly inside it, and Mars and the Moon are almost certainly outside it.

The atmosphere above 50 km provides about 1 kg per square centimeter of mass shielding against cosmic radiation, which is approximately the same column density as Earth’s atmosphere. Dale Arney and Chris Jones, in the HAVOC study, put it bluntly: radiation exposure at the 50 km altitude on Venus is about the same as you would experience in Canada. Call it 0.01 mSv per day above Earth-surface background. Comparable to a high-altitude airline pilot.

Compare those numbers to the alternatives:

Mars surface: 0.64 to 0.7 mSv per day, measured directly by the Curiosity rover’s RAD instrument. About 230 mSv per year.

Lunar surface: roughly 0.4 mSv per day. No atmospheric shielding at all. Habitats require buried construction or regolith berms or water tanks for radiation protection.

Free space, International Space Station, O’Neill habitat: 0.4 to 1.0 mSv per day depending on the solar cycle.

Mars transit: 1.8 mSv per day for the duration of the cruise.

Venus 50 km altitude: approximately equivalent to Earth’s surface.

The cloud layer of Venus is, in radiation terms, the most Earth-like environment in the solar system outside Earth itself. By a factor of 50 to 100 over the Martian surface. By larger factors over the Moon or free space.

That single fact is almost enough to make the case. But there is more.

Your air is your envelope

Here is the design feature that makes everything else work. The first time you hear it, it sounds like science fiction. It turns out to be elementary atmospheric chemistry.

Venus’s atmosphere is 96.5% carbon dioxide. The molar mass of CO₂ is 44 grams per mole. A breathable nitrogen-oxygen mix — 78% N₂ at 28 grams per mole, 21% O₂ at 32 grams per mole — has an average molar mass of about 29 grams per mole. Gas density scales linearly with molar mass at the same temperature and pressure, so breathable air is about two-thirds the density of the surrounding Venusian atmosphere. The buoyant lift is the difference, about 0.63 kg per cubic meter at cloud-deck conditions.

That means breathable air is a lifting gas on Venus. About 0.6 kilograms of lift per cubic meter, which is around 60% of what helium gives you on Earth.

Think about what this means. On Earth, a balloon requires helium or hot air — something different from the surrounding atmosphere. You have to manufacture or import the lifting gas, contain it in a sealed envelope, and keep it separate from the air your passengers breathe. On Venus, the air your colonists breathe is itself the lifting gas. There is no separate lift envelope. There is no pressure differential to maintain. The inside of your habitat is 1 bar of N₂/O₂, the outside is 1 bar of CO₂, and the structure sits in mechanical equilibrium.

This is the dream of every pressure-vessel engineer. Pressure vessels are hard! They want to burst. They fatigue under thermal cycling. They require thick walls, leak monitoring, double-hull architectures. Every other off-Earth habitat anyone has proposed — Mars surface, lunar surface, O’Neill cylinder, space station — is a pressure vessel holding 1 bar against vacuum. A Venus cloud city is not a pressure vessel at all. It is a containment envelope at zero pressure differential. The walls only need to keep the two atmospheres from mixing across the boundary. They do not need to contain pressure.

The structural mass implications are staggering. Birch estimated his floating colonies at 1000 kg per square meter total areal density, with 200 kg/m² for the base structure and 50 kg/m² for the roof. The rest is soil, water, agriculture, and habitation. By comparison, an O’Neill cylinder requires meters of bulk shielding, plus a pressure-rated hull, plus structural accommodation for rotational stress, and even the lightest designs are orders of magnitude heavier per unit habitable area.

Versus Mars

Mars is the obvious comparison.

Where Mars wins: Mars has water ice in known accessible quantities. Mars has a 24.6-hour day, well within human circadian tolerance. Mars has surface chemistry — Sabatier reactions, perchlorate processing — that produces oxygen and propellant from in-situ resources. Mars is energetically cheap to reach from Earth, with delta-V budgets we know how to handle. Rovers have been operating on the surface for decades and we have a deep operational understanding of the environment.

These are real advantages.

But here is what you trade for those advantages: surface gravity of 0.379 g, which we have no biological evidence is safe for long-term human habitation; atmospheric pressure of 0.006 bar, which means full pressure suits required any time anyone steps outside; mean surface temperature of −63 °C, with excursions to −140 °C at the poles; radiation exposure 50 to 100 times higher than at Earth’s surface; solar power density at 590 W/m² compared to Earth’s 1361 and Venus’s 2620; and global dust storms that bury solar panels and grind into every seal and joint in your equipment.

The dust point is underappreciated. Martian regolith is electrostatically charged, mildly toxic from perchlorates, and gets into everything. Apollo astronauts complained about lunar dust within days of their first surface operations. Mars colonists will be dealing with dust intrusion problems for decades, in habitats, in equipment, in their lungs. Venus cloud habitats face sulfuric acid, which is corrosive but contained. Acid is a chemical engineering problem. Dust is a mechanical infiltration problem. The first is easier.

What about day length? Venus rotates once every 243 days retrograde — pathologically slow, and we will spend three posts on that problem later in this series. But at the cloud altitude, the super-rotating atmosphere circles the planet much faster than the surface. A floating colony drifting with the cloud layer experiences a solar day of about 4 Earth days at the equator. Not 24 hours. But not 117 days either, which is what surface settlements would face. And cloud cities can choose their drift rate to some extent by altitude selection. Mars wins on day length. But the gap is much smaller than people usually assume.

Mars has water and propellant and a Sun-friendly day. Venus cloud altitude has nearly every other habitability advantage that matters for human bodies and human structures. We have been investing in the harder planet.

Versus the Moon

The Moon is the closest body and the cheapest in delta-V. Three-day transit each way. No atmosphere to complicate landing. Known ice deposits in permanently shadowed polar craters. Working ISRU concepts for regolith oxygen extraction.

The Moon makes sense as an industrial outpost, a science platform, a stepping stone for cislunar infrastructure. It does not make sense as a place where humans live for generations.

Lunar gravity is 0.166 g. That is even further from Earth gravity than Mars is — about 44% of Martian gravity. Whatever speciation pressure 0.379 g produces on Mars, 0.166 g produces faster and more severely on the Moon. The lunar surface is a vacuum environment with temperature swings of 300 °C across the 14-day lunar day. Radiation exposure is in free-space range, with no atmospheric shielding at all. Habitats have to be buried under regolith, built underground, or shielded with water tanks. The whole architecture is constrained by these requirements.

A lunar base is a good idea. A lunar civilization, in the sense of millions of people living their lives there for generations, is a more troubling proposal. The biology does not work, and we have not been honest about that.

Versus O’Neill cylinders

The free-space habitat advocates — Gerard O’Neill’s intellectual descendants in the National Space Society and adjacent groups — have a real case I want to take seriously. O’Neill habitats can be built anywhere there is solar power and raw material. They can be sized for any population. They can rotate to provide any artificial gravity, including exactly 1 g, which puts them in a different biological category from Mars or Moon surfaces. They scale with industrial capacity in ways that planetary surfaces do not.

The problem is the construction cost.

A Stanford torus or Bernal sphere is millions to tens of millions of tonnes of structure. The radiation shielding alone is meters of bulk regolith or water, which is kilotonnes to megatonnes of mass per habitat. The pressure containment is a serious materials problem. The rotational stability and station-keeping require active control. Every single habitat has to be built before anyone can move in. There is no incremental occupation of a half-finished O’Neill colony.

Compare that to a Venus cloud habitat, which can be a single inflated structure deployed from a single lander mission, lifted by the breathable air inside it. Birch’s floating colonies at 1000 kg/m² scale linearly with envelope area. A square-kilometer colony at one million kilograms is comparable in mass to the International Space Station and hosts hundreds of people. Scaling up means inflating more envelope.

O’Neill cylinders are more flexible. You can put them anywhere, size them however you want, give them whatever rotational gravity you choose. Venus cloud cities are more immediate. They can be built with substantially less industrial infrastructure than a free-space colony requires. For the early decades and centuries of off-Earth settlement, cloud cities arrive first.

There is also a deeper distinction. An O’Neill cylinder is a constructed environment. Every cubic meter of air, every kilogram of water, every photon of light is provided by engineering. A Venus cloud city sits inside an environment. The air outside is at breathing pressure (if not breathable composition), the temperature is shirt-sleeve, the gravity is set by the planet. The cloud city is the more forgiving habitat. A pressure leak in an O’Neill cylinder is a hull breach. A pressure leak in a Venus cloud city is a slow exchange between two atmospheres at the same pressure. The failure modes are categorically different.

What a cloud city actually looks like

Let me describe a plausible early Venus cloud habitat, drawing on Birch, Landis, and HAVOC.

You arrive in Venus orbit and aerocapture into an entry trajectory aimed at the equatorial day side. Your habitat is packed inside an aeroshell similar in scale to a Mars EDL system — a few tonnes of payload behind a heat shield. At about 70 km altitude you deploy a parachute. At 60 km you jettison the aeroshell and begin inflating the habitat envelope. The same envelope serves as parachute (during inflation) and as the buoyant structure once full. By 55 km altitude the envelope is inflated and your lift is sufficient to halt descent.

You float at 50 to 55 km altitude in equilibrium with the surrounding atmosphere. The envelope is filled with breathable air at 1 bar — the same pressure as outside but about half the density. Your habitat hangs below the envelope, or is integrated into it, shielded from cloud-layer sulfuric acid by an outer skin of fluoropolymer or coated polymer. Your structure is light because there is no pressure differential to contain. Your radiation environment is Earth-equivalent. Your gravity is 0.904 g. Your power comes from solar panels on the upper envelope surface, which receive nearly twice the irradiance of an Earth-surface panel plus significant reflected light from the cloud layer below.

You move horizontally by riding the super-rotation winds, about 95 m/s eastward at cloud tops, slower below. You move vertically by adjusting envelope volume through compression or venting. The super-rotation is a feature, not a problem. It gives you a 4-day day-night cycle and continuously carries you across the planet, exposing you to varying weather and giving you global access without translational propulsion.

You grow food in pressurized greenhouses or in the main envelope itself, since the air is already there. You collect water from cloud humidity or extract it from sulfuric acid, which is, after all, mostly water by molar count. You scrub CO₂ leakage and replenish O₂ through electrolysis or photosynthesis. You communicate with Earth through a relay satellite in Venus orbit, with round-trip light times of 4 to 28 minutes depending on planetary geometry.

This is mission-architecture-compatible with present technology. The HAVOC study laid out a phased approach — robotic precursors, then short-duration crewed flybys, then longer crewed stays in orbit, then atmospheric habitats — using technology that is at TRL 5 or higher today. The hardest unsolved problems are sulfuric acid resistance for long-duration envelope materials, large-scale envelope deployment, and propulsive return from the atmosphere to orbit. None of these requires breakthrough physics. All of them are tractable engineering.

Why this is not the dominant proposal

Why does Mars dominate the human-spaceflight conversation rather than Venus? Several reasons.

First, cultural inertia. Venus became unfashionable after Mariner 2 confirmed the surface temperature in 1962. The popular space-advocacy community moved its attention to Mars and never came back. The cloud city case requires explaining a counterintuitive idea — that you can live in a planet’s atmosphere without being on its surface — which is a conceptual move that surface-bound Mars colonization does not require. Familiar wins over unfamiliar.

Second, surface bias. “Colonize Venus” sounds, to most people, like “colonize the Venusian surface,” which is obviously preposterous given that the surface is 737 K. The cloud city case requires a conceptual move that popular discussions do not make. Mars surface settlement is at least visualizable. Venus cloud settlement requires explanation.

Third, economic geography. Mars has been pitched as a stepping stone outward to the asteroid belt, the outer planets, eventually the stars. Venus is on the inside of Earth’s orbit and leads outward only to Mercury and the Sun. For a settlement strategy organized around outward expansion, Mars is in the right place geographically and Venus is not.

Fourth, ISRU. Mars has accessible water ice, mineral resources, and surface materials usable for construction. Venus has none of those in easily extractable form. Atmospheric mining is harder than regolith mining, and the surface is inaccessible. For mission concepts emphasizing in-situ resource utilization, Mars has the obvious edge.

Fifth, robotic exploration. We have continuous robotic presence on Mars and have for decades. Our intuitions about Mars are rich and our institutional momentum on Mars exploration is enormous. Venus has been visited briefly by Soviet landers (lasting about two hours each) and by atmospheric probes. The robotic exploration gap reinforces the cultural and political gap.

These are real reasons. They are not, however, engineering reasons. They are reasons about which planet we are familiar with, which planet fits an outward-expansion narrative, and which planet has better local resources for an isolated outpost. None of them are reasons that the habitats themselves would be harder to build on Venus than on Mars.

The engineering case is straightforward. Venus has a layer where humans can live in shirt sleeves at 1 g with Earth-equivalent radiation shielding. Mars does not. The Moon does not. Free space does not. The settlement strategy that takes biology seriously settles where biology wants to live.

What this means

Venus is the easiest place humans can live off Earth. Not the easiest place to land. Not the easiest place to extract resources. Not the easiest place to reach. But the easiest place where, once you have a habitat in place, humans actually live in a way that does not constantly fight their biology and their engineering.

Habitability is not a surface property. Earth’s surface is not habitable for most of life that we care about. Most of Earth’s biosphere lives in oceans, not on land. Our own habitable zone is a thin layer at the bottom of an atmosphere. The lesson of Venus is that habitability is about finding the right layer in a planetary system, not about finding the right planet.

That lesson generalizes. Jupiter has a 1-bar layer. So does Saturn, Uranus, Neptune. The radiation environments at most gas giants are hostile, especially Jupiter’s, but the atmospheric pressure and temperature of the right layer of any gas giant is closer to Earth-like than the surface of any rocky world except Venus and possibly an early-period Mars. Cloud-layer habitation may be the normal way humans will eventually live on most worlds in the solar system. Rocky-surface settlement of the Earth kind may turn out to be the exception, obtaining only on the small minority of bodies where the geology cooperates.

That is a different vision of human expansion than the one we have inherited. I think it is the one the engineering favors.

The next post in this series will make the case that beginning a serious cloud-city presence on Venus makes terraforming the surface inevitable. Not as an aspiration. As a consequence of biology, economics, and what people want from a planet they have committed to live on. The argument turns on something I have come to think is the deepest constraint on off-world human settlement, which has nothing to do with engineering and everything to do with what we are.

I hope these thoughts help you see why Venus deserves more serious attention than it has been getting, and why the conversation we have been having about Mars for the last forty years has been, in important ways, the wrong conversation.

Posted in Uncategorized | 13 Comments

Colonies on Mars require more than engineering

Elon Musk talks about a city on Mars the way a developer talks about a new subdivision outside Phoenix. The engineering problems are hard, but they are the kind of hard we know how to attack: get there cheaply, make propellant on site, close the life-support loop, shield against the radiation, and eventually warm the place up. There is a technical roadmap. There is a financial roadmap. There is no social roadmap at all.

That missing roadmap is what I want to talk about. I am an aerospace engineer, I spend my days on molten-salt reactor power systems and the long-term energy infrastructure any settlement off Earth would have to carry with it, and I share the technical optimism completely. The hard problems are hard, not impossible. What I do not share is the assumption that the society on Mars will sort itself out once the engineering is finished. The historical record says the opposite. The society is the harder problem, and it does not build itself.

What the history actually shows

Go to the Mormon pioneer cemetery at Winter Quarters, in Florence, Nebraska. The ground holds several hundred graves from the winter of 1846–47, when the Saints driven out of Nauvoo wintered on the Missouri River before going west to the Salt Lake Valley. A great many of the graves are children. Roughly one in twelve of the people who wintered there died that winter.

The Saints went anyway. They went the next year, and the year after, and for twenty years after that, organizing wagon and handcart companies that moved tens of thousands of people thirteen hundred miles to a place the rest of the country had already written off. On the federal maps the Great Basin was part of the Great American Desert—unfit for settlement, skipped over by the wagons bound for Oregon and California. The Saints chose it partly because nobody else wanted it, and partly because Missouri and Illinois had made staying impossible.

This is the pattern that real migration follows. People do not, as a rule, move to worse conditions to chase a dream. They move to survivable conditions to escape unsurvivable ones. The Pilgrims left England because England had become impossible for them. The Irish came during the famine because staying meant starving. The Saints crossed the plains because Illinois had burned them out and an extermination order in Missouri was fresh in living memory. The Vietnamese in the boats and the Cubans on the rafts were pushed by where they had been, not pulled by where they were going. The destination only had to be survivable.

It is a pleasant thing to picture a confident civilization at the height of its powers deciding to spread to other worlds. I do not believe that is how it will happen. Voluntary migration toward dramatically worse conditions, for the sake of an aspiration, is rare. It draws a few individuals. It does not draw a population, and a settlement needs a population.

If human beings ever live on the frozen plains of Mars or float in cloud cities in the air of Venus, it will most likely be because something on Earth made staying worse than going. That is not a thing to look forward to. But it is the honest framing, and it is also the useful one, because it asks the right question: what does the minimum survivable refuge actually require, for people who have already lost—or are losing—what they had?

The social architecture problem

We techy-types do not like to dwell on this, so we mostly don’t. We would never sign off on a hull design that left an airlock standing open. We leave this one open all the time.

A colony on Mars is a closed system. Every person in it depends, every single day, on equipment that other people maintain, on supply chains internal to the settlement, and on a social structure that hands out the work, settles the fights, raises the children, tends the sick and the old, and persuades people to sacrifice for the common good. The hostile environment charges a tax on every member, every day. Air, water, food, heat, radiation shielding—none of it can be taken for granted. The tax gets paid in continuous labor, in freedoms given up, in gratification deferred, and in standing exposure to the risk of death.

A person can carry that load alone for a little while. Nobody carries it indefinitely without a structure that spreads the burden, supplies the motivation, and provides a meaning larger than the personal cost. On Earth the surrounding society does most of that work without anyone noticing. In a colony there is no surrounding society. The colony is the society. There is no fallback.

Look at the settlements of hostile places that actually worked, and every one of them was carried by a tight community that existed before the settlement did. Plymouth had the Separatist congregation. Massachusetts Bay had the Puritan covenant towns. Jamestown survived only when the Virginia Company imposed near-military discipline, and nearly died every time that discipline slipped. The pioneer Saints had the ward and the priesthood quorum and the Relief Society. The Israeli kibbutzim had ideology and an explicit communal vow. The Antarctic stations run on military or quasi-military hierarchy. Even the Space Station rides on rigorous selection, years of training, and a wall of institutional support behind every six-month rotation.

I cannot find a single case in the record where a loose collection of individuals out of a consumer society settled a hostile place without first forming, or being taken into, a tight community. Where it was tried on the loose-individual basis, it failed nearly every time. The environment finds the social weakness, and the weakness compounds until the settlement folds or goes home.

This is the part that never appears in the engineering presentation. A million volunteers out of twenty-first-century industrial civilization will not step off the ships and spontaneously become a society that can hold together across generations. The history is not ambiguous on this point. The community comes first, or it does not come at all.

Which communities could actually do it

So the question is no longer “can we build the ship.” It is: what community exists today that can hold itself together under hostile conditions across generations, and run a high-technology settlement, and shoulder the cost of a hard migration for something bigger than personal comfort?

The high-cohesion religious communities are the obvious place to look. So let’s look.

What about the Amish, or the Hutterites? The cohesion is real and the multi-generational track record is excellent. But their identity is bound up in refusing exactly the technological apparatus a colony would have to run on. An Amish settlement on Mars is not a coherent idea. The conservative Mennonites run into the same wall.

What about the Haredi Jewish communities? Strong cohesion, yes. But the cultural energy is aimed at Torah study, not at engineering, and the dominant pattern does not produce physicists and aerospace specialists at anything like the rate a settlement would need.

What about the Catholic religious orders? Technically sophisticated and deeply committed—and small, celibate, and not built to expand. A community that does not have children cannot settle anything.

Then turn it around and ask after the people who already have the engineering: the secular educated professionals, the broad technical workforce of the rich economies. They have the skills and none of the cohesion. They are individualistic, atomized, and reproducing well below replacement. They cannot supply a multi-generational anything.

That leaves a very short list. To be honest, I can think of one community that sits in the intersection, and it is my own.

The cohesion is real and it is documented. The LDS Church runs a welfare system that can feed a family that has lost its income. It runs a missionary program that turns out tens of thousands of young adults a year, trained in disciplined deprivation under organized leadership—which is to say, trained in exactly the thing a colony demands. It has a temple system that anchors the community’s deepest commitments in ritual, and a ward structure that knows the families, visits the homes, and organizes mutual aid as a matter of routine. And the institutional muscle for moving people to hard country exists in living memory: the wagon and handcart companies, the advance parties planting crops for those coming behind, the systematic colonization of the Great Basin from Idaho to Mexico under Brigham Young.

The technology posture is the load-bearing distinction. Latter-day Saint theology authorizes technical work and treats it as part of the work of God. The community turns out engineers and scientists well above the rate its size would predict. BYU’s engineering programs are substantial. The Utah technology economy is full of companies founded or shaped by Latter-day Saints, in software, biotech, and aerospace. The LDS Church itself operates family-history infrastructure at planet scale and broadcasts a global conference in dozens of languages. A lot of the engineers quietly working U.S. defense and aerospace and frontier-technology programs are members. Jon Goff and I are two of them.

High cohesion married to high-technology participation is a rare profile. Most people miss it, because Latter-day Saints don’t lead with their religion at work, because the media caricature of the community looks nothing like its actual professional reality, and because the community itself doesn’t advertise its technical contribution. But the profile is real, and it is closer to what an off-world settlement would actually require than anything else currently on offer.

What the pioneer migration actually demonstrated

The Latter-day Saint migration to the Great Basin, from 1847 into the early 1870s, is the closest thing history offers to organized off-world settlement. The space community doesn’t study it, because it gets filed under “religious history” instead of “settlement logistics.” That is a mistake, because the lessons transfer.

The migration moved roughly seventy thousand people across thirteen hundred miles of barely-mapped country, on a budget the migrants raised themselves, under a leadership that planned the whole operation centrally and executed it through distributed wagon and handcart companies. The system ran advance parties that planted crops for the companies coming behind, supply caches stocked by the previous year’s travelers, scouting reports that updated the route, and disciplinary structures that held order in thousand-person camps over months on the trail. The mortality was real but lower than the surrounding context would lead you to guess. The 1856 handcart disaster—the Willie and Martin companies, perhaps two hundred dead—was the exception, and it was the exception that forced the reforms that made the later companies better provisioned and better timed. Across the two decades, the migration as a whole moved at a death rate comparable to ordinary American mortality of the day. Of my sixteen great-great-grandparents, all but two made the crossing before the advent of the railroad, and some of them made it multiple times as they returned east for missionary service.

On arrival the Saints colonized a region the federal government had marked unfit for agriculture. Brigham Young directed the founding of more than three hundred settlements between 1847 and 1877, calling specific families to specific places with specific jobs—farming the river valleys, mining the mountains, manufacturing in Salt Lake, missions to the native peoples. Each settlement was organized before it existed: a bishop, a Relief Society, a school, an irrigation plan, a farm plan, and a plan for defense. Most of them held. Many of them are cities now.

And the engineering was not trivial. Agriculture in the Great Basin runs on irrigation, and the Saints built the first significant Anglo-American irrigation works in North America, inventing the legal and cooperative frameworks the rest of the West later copied. The roof of the Salt Lake Tabernacle, designed with no modern structural analysis, has stood more than a hundred and fifty years and still gets studied for how well it performs. They built railroads, telegraph lines, woolen mills, sugar-beet processing, and iron foundries, often years or decades ahead of the regions around them.

What made all of it work was the combination we have been circling: cohesion, multi-generational commitment, a theology that authorized the technical work, a willingness to suffer for purposes the community held as transcendent, and central planning executed through distributed hands. Pull any one of those out and the migration either never happens or happens and fails.

What follows from this

Take the pattern seriously and several things follow.

First, the engineering case is not the binding constraint. The binding constraint is social, and the social constraint is being almost entirely ignored in the public conversation. A serious settlement program will either bring strong-cohesion communities in on purpose, or it will fail, or it will end up inherited by whichever community inside the first settlement turned out to actually have the capability.

Second, the arithmetic favors the cohesive communities even when they start as a minority of the settlers. Strong transmission down the generations, plus replacement-level-or-above fertility, plus a closed system, equals eventual majority. A Mars settlement that starts as a Musk-style mixed founder population, with some fraction of Latter-day Saints or some comparable community in the mix, will most likely, given enough generations, become a settlement run by the descendants of that sub-community. That isn’t a boast. It’s arithmetic, working on communities instead of individuals.

Third, the kind of community required is unusual enough that planning ought to name it. The current model—open volunteer recruitment, on the assumption that a working society will simply emerge—has no historical precedent for success. The model that has succeeded is the chartered community: an existing tight-bonds group, leadership and structures intact, transplanted whole. Plymouth was a chartered community. The Great Basin settlement was a chartered community. Israel was, in its way, a chartered settlement undertaken by a people who had organized themselves for the purpose.

Fourth, religious or quasi-religious motivation matters more than secular space advocacy wants it to. The work will be hard, the rewards distant, the costs immediate, and the meaning is not going to come out of the labor itself. A community that can supply transcendent meaning has an advantage that no salary and no flag can replace. Secular space advocacy does not enjoy hearing this. The record says it anyway. LDS colonists on Mars will build a temple there and feel spiritually anchored.

A speculative note

I will be the first to say that the Latter-day Saint community has not been pointed toward space settlement by its leadership. The emphasis right now is on missionary work to the living, proxy temple work for the deceased, and on individual discipleship. I think it highly unlikely that the leadership ever calls the community off the planet. But then I remember that I have already watched things come to pass in this century that I would never have believed. The latent capability is real. Whether it is ever switched on depends on a direction that has not been given.

The capability, though, exists. The same community that made Utah out of a refugee migration in the 1840s could in principle make a lunar or Martian settlement out of a far smaller starting population, given a comparable timeline and a comparable commitment from the active membership. The LDS Church has demonstrated, more than once, that it can absorb a major new direction when leadership calls for one—the gathering to the West, the temple-building, the worldwide missionary effort, the global expansion of the organization. Each was an enormous investment of the community’s resources and attention, undertaken when it was called for, and largely accomplished.

I make no prediction. I only observe that among the communities now on Earth with the demonstrated ability to settle a hostile place across generations, the Latter-day Saints are one of the very few—and may be the only one—that pairs that cohesion with the high-technology posture that life off Earth would demand.

What the space community should do

There is a practical implication in all of this, and it is mostly homework.

Study the social architecture of historical settlement, harder than we have. Plymouth, Massachusetts Bay, the pioneer Saints, the kibbutzim, the long list of settlement projects that succeeded and the longer list that failed—that is the empirical record any honest settlement planning has to rest on. Most space advocacy treats it as irrelevant, or never learned it. It is neither irrelevant nor unknowable.

Be honest about the kind of society a colony will need, and about which communities can actually supply it. The current talk of recruiting willing individuals is unhistorical and unserious. The settlement that lasts will be the one that arrived as a community, or that formed one fast enough to live through the first hard winter. Planning that ignores this is planning to fail. And Mars is one long winter.

And understand that the communities who could supply the social architecture have their own purposes, their own theology, and their own clocks. They are not commodity inputs to be hired onto someone else’s project on someone else’s terms. If you want them, the terms will have to take seriously what they are and what they require. That is uncomfortable for a secular program to hear. The alternative is to keep designing a Mars city on the assumption that the society will take care of itself, which it will not.

A closing observation

Standing at Winter Quarters, looking at those graves, I saw something I had not quite seen before. The people buried there did not go West because the Salt Lake Valley sounded nice. They went because staying in Nauvoo had become impossible, because the community they belonged to was strong enough to organize an impossible journey, and because the meaning they shared was enough to carry the cost. The destination only had to be survivable. The push, the community, and the meaning did the rest.

That, I think, is what settlement off Earth will look like, if it ever happens at the scale the visionaries imagine. Not a triumph of individual ambition, but the work of communities bound by something larger than themselves, going to hard places because the difficulty had become preferable to the alternative, and holding together across generations by the same means human beings have always used under hard conditions. The engineering will be necessary. The engineering will not be enough. The communities that can supply what the engineering cannot are the ones who will decide whether the cities ever rise.

I do not know whether a city on Mars will ever be built. If one is, I suspect it will be built by people who already know how to build cities in cold red deserts, and who already know the building takes more than blueprints and propellant. The pattern is old. The Saints know it because their ancestors lived it. I hope that these thoughts help you see why I think that is important to our future in space.

Posted in Mars, Religion, Space Settlement, Venus | 9 Comments

How Starship will use the Henry Hub to access energy 10x cheaper than Jet Fuel

News broke recently of rumors of a space company looking to buy up like a couple hundred square miles of land in Louisiana, possibly to set up a launch site.

Why Louisiana?

Two reasons:

1. Launch site advantages
Louisiana is one of the very few pro-industrial-development locations with a coastline suitable for polar orbit launches. This is required for SpaceX’s AI satellite constellation in sun-synchronous orbit. A viable launch path for polar orbits exists from Louisiana.

2. Proximity to cheap energy
It is located right next to the Henry Hub, the primary U.S. benchmark for natural gas pricing.
Current price: under $3/MMBTU
→ under $3/Gigajoule
→ under 1 cent/kWh-thermal

Based on the above tweet and this image of Louisiana’s natural gas pipeline system: https://rbnenergy.com/daily-posts/blog/here-comes-gas-again-why-henry-hub-sitting-pretty

Direct connection to this pipeline network would allow SpaceX to:

  • Undercut the cost of trucking LNG
  • Beat typical delivered industrial rates for U.S. electrical power plants
  • Achieve energy cheaper per unit than Appalachian coal

For all intents and purposes, it is the cheapest source of energy humanity has access to — other than starting a coal mine on fire.

Starship v4 propellant requirements (approximate)

  • First stage: 4050 t of propellant
  • Second stage: 2300 t of propellant

Total propellant: ~6350 t
→ to deliver >200 t of payload to orbit

Based on these figures for Starship V4:

Propellant-to-payload ratio
Ratio of propellant mass to LEO payload mass = 31.75

Raptor engine mixture ratio
Oxidizer-to-Fuel (O:F) ratio = 3.6 by mass
(Design goal was 3.8; future operations may approach this.)

Propellant breakdown (per 1 t LEO payload)

  • Methane (CH₄): 6.9 t
  • Oxygen (O₂): 24.85 t

Total propellant: 6.9 t + 24.85 t = 31.75 t

Energy calculation
High-Heating-Value (HHV) of methane = 55.5 MJ/kg

Energy content of the methane used per kg to orbit:

6.9×55.5 MJ/kg=383MJ/kg6.9\times 55.5\ \text{MJ/kg} = 383\text{MJ/kg}

Cost implications
This energy figure alone suggests raw fuel costs on the order of ~$1/kg to orbit.

However, real-world propellant costs include substantial overhead:

  • Purification of natural gas (byproducts such as butane and propane are often more valuable than methane, which can offset some costs)
  • Liquefaction of methane
  • Liquefaction of oxygen
  • Subcooling of both propellants for rocket loading
  • Chill-down losses for the vehicle and ground support equipment

Realistic target
If liquefaction equipment is built on-site (as SpaceX is now explicitly doing per environmental permits), total propellant costs to orbit could reach the range of ~$2–3/kg.

Launch vehicles are just elaborate machines for turning chemical energy into payload kinetic energy. The best launch vehicles are on the order of 10% efficient at doing this. Just like a power plant, an aluminum smelter, or a data center, it makes sense to put such a machine as close as possible to the cheapest source of energy.

Posted in Uncategorized | 2 Comments

Apollo Manned Venus Flyby retrospective

In February 1967, five Bellcomm engineers completed a 177-page study showing that a manned Venus flyby was feasible with a single Saturn V and Apollo hardware. Nobody flew it. But every engineering conclusion they reached applies, with interest, to the 2034 inner solar system circumnavigation.

The previous post described the 2034 Earth-Venus-Mars-Venus-Earth circumnavigation trajectory — the mission that departs August 4th, flies past Venus, then Mars, then Venus again, and returns to Earth 750 days later, all without a single deterministic propulsive maneuver after departure. I traced the trajectory family back to A. A. VanderVeen’s 1969 Journal of Spacecraft and Rockets paper, and to the internal Bellcomm memo that preceded it in April 1968.

But VanderVeen’s work was trajectory analysis. The question his colleagues were asking simultaneously — and answering in parallel — was the engineering question: what would you actually need to build, and could you do it with hardware that existed or was nearly in hand?

That question was answered in February 1967 in Bellcomm Technical Report TR-67-600-I-I, “Manned Venus Flyby,” authored by M. S. Feldman, L. A. Ferrara, F. L. Havenstein, J. E. Volonte, and P. H. Whipple. It is 177 pages long. It is thorough, sober, and technically careful. And it sits in a NASA archive largely unread, having described a mission that was never flown despite being demonstrated feasible fifty-seven years ago.

Reading it now is enlightening.

What the Study Was Trying to Do

The Bellcomm Venus flyby study was not primarily about flying to Venus. It was conducted under NASA contract NASw-417 as guidance for the Apollo Applications Program — the post-Apollo program that was supposed to leverage Saturn and Apollo hardware for longer-duration missions. The AAP had no single clear goal of its own, and it needed to understand what future planetary missions would require in order to make sensible technology investments in the present.

The study’s authors put it plainly: “It is clearly not the intent of this study to recommend that NASA undertake a Venus flyby mission in 1973 or at any time; but it is the intent to show that such a mission is feasible under the above ground rules and, therefore, provides a reasonable basis for choosing long duration system characteristics.”

In other words, the Venus flyby was a requirements generator. By designing a complete spacecraft for a one-year interplanetary mission, the study team could identify which subsystem technologies needed development — which existing Apollo systems could be extended and which required entirely new approaches. The answers to those questions would then inform what AAP should be building toward.

The mission they analyzed was a three-man Venus flyby departing October 31, 1973, passing Venus on March 3, 1974 at an altitude of approximately one Venus radius (~6,052 km above the surface), and returning to Earth on December 1, 1974. Total mission duration: 396 days. The entire mission would be accomplished on a single standard Saturn V, with a total injected mass of 48,430 kg — within the 50,350 kg capability available for a 30-day launch window.

What followed was one of the most detailed spacecraft systems analyses ever performed for a manned interplanetary mission that was never flown.

The Vehicle Configuration

The flight configuration had three major elements. The Command and Service Module was essentially Apollo, modified for long-duration storage and high-speed Earth return. The Environmental Support Module (ESM) occupied the adapter area where the Lunar Module would normally sit — it was a new module, not derived from any existing Apollo hardware, providing environmental control, additional propulsion, experiments, and communications. And the spent S-IVB upper stage — the third stage of the Saturn V, which would normally be discarded after trans-lunar injection — was retained and converted into habitable volume for the crew during the interplanetary cruise.

The S-IVB habitability concept is obviously one that had been considered several ways. The hydrogen tank of the S-IVB had an internal volume large enough for three crew members to live and work comfortably for a year. The study team proposed equipping it with curtains and cord webbing for compartmentation, installing approximately 680 kg of fittings and equipment stored in the ESM until after injection, and using the solar panels mounted on the outside of the S-IVB as a meteoroid bumper shield — serving double duty as protection and power generation. The result was a vehicle with generous habitable volume, more than enough for the mission if zero-gravity conditions proved physiologically acceptable.

From Venus Flyby to Skylab: The Same Idea, Grounded

The Bellcomm team’s S-IVB habitability concept was not original to them — it was the central idea of the entire Apollo Applications Program, and it was being developed in parallel by multiple groups within NASA at the same time the Venus flyby study was being written. Understanding what happened to that concept, and how it was eventually realized in a very different form, illuminates exactly what was lost when the planetary mission program collapsed.

The original AAP concept for an orbital workshop was a “wet workshop”: a Saturn IB would launch an S-IVB stage that had to fire its engine to reach orbit. Once there, the crew would arrive on a second Saturn IB, enter the hydrogen tank through an airlock, pressurize it with oxygen and nitrogen from tanks in a docking module, and then — working in zero gravity — install furnishings, fabric floors and walls, lighting, and experimental equipment transferred from the Command Module. The equipment had to be stored outside the tank during launch because the hydrogen fuel occupied the interior. The crew would be doing construction work in orbit, in spacesuits, in a freshly emptied cryogenic tank.

This is essentially what the Bellcomm Venus flyby study proposed for the interplanetary mission — with the difference that the Bellcomm concept was somewhat more elegant. Rather than requiring the crew to outfit the tank in zero gravity after arrival, Bellcomm proposed storing approximately 680 kg of fittings, curtains, cord webbing, and equipment in the Environmental Support Module during launch, then transferring and installing them in the S-IVB hydrogen tank after injection into the interplanetary trajectory. It was still a wet workshop concept in spirit, but with the installation work occurring in the less time-pressured environment of interplanetary cruise rather than in Earth orbit immediately after rendezvous.

The wet workshop concept was abandoned in July 1969, when NASA Administrator Thomas Paine approved the switch to a “dry workshop” — a fully ground-outfitted S-IVB launched atop a Saturn V without needing to fire its own engine. The cancellation of Apollo missions 18, 19, and 20 had freed up Saturn V rockets, and their much greater payload capacity meant the S-IVB could be converted into a complete space station on the ground, lifted into orbit already equipped, and entered by the crew immediately on arrival. This became Skylab, launched in May 1973.

Skylab’s Orbital Workshop was exactly what the Bellcomm Venus flyby study had proposed using as a cruise habitat — the liquid hydrogen tank of an S-IVB stage, converted into habitable volume. The S-IVB’s 73,280-litre liquid oxygen tank below the Orbital Workshop was used to store trash and wastewater. The liquid hydrogen tank — the large upper volume, 6.6 meters in diameter — became the main living and working space, with two floors installed on the ground, an exercise area, galley, waste management system, and a zero-gravity shower. Solar panels extended from the exterior. The total pressurized volume was approximately 320 cubic meters, more than enough for three crew members for months at a time.

The Skylab crews set long-duration spaceflight records that stood for years. The third and final crew spent 84 days aboard — far longer than any previous mission, and sufficient to demonstrate that humans could survive and work productively in extended weightlessness with appropriate countermeasures. The medical data gathered on all three Skylab crews became the foundation for understanding long-duration spaceflight physiology.

Now consider the counterfactual the Bellcomm study implicitly describes. The S-IVB habitability work that eventually produced Skylab was proceeding in 1967 — and simultaneously, the Venus flyby mission study was showing that the same vehicle configuration, deployed on an interplanetary rather than Earth-orbital trajectory, could carry three humans to Venus and back in 396 days. The departure energy was the same as a planetary mission. The S-IVB hydrogen tank provided the same habitable volume. The modifications required were similar in kind if not in detail.

What happened instead was that the wet workshop became the dry workshop became Skylab — an Earth-orbiting station, firmly tethered to the resupply and rescue capabilities that only low Earth orbit provides. The planetary mission that motivated the entire long-duration technology development program was never flown. The AAP, which had been conceived in part as a pathway toward interplanetary capability, ended with three crews in Earth orbit. The Venus flyby windows of 1973 and 1977 opened and closed with no one aboard.

The irony is sharpest when you look at the timing. Skylab’s final crew returned to Earth in February 1974. Mariner 10 flew past Venus on February 5, 1974. The Bellcomm reference Venus flyby mission would have passed Venus on March 3, 1974. Three things were happening in the same month that could have been one thing: the end of a long-duration orbital mission that proved humans could survive in space for months, the first operational gravity assist demonstrating the trajectory mechanism, and the opening of the planetary window that had been planned for in 1967. The convergence was exact. The mission was not flown.

We now know the answer. Valery Polyakov demonstrated in 1994–95 that a human being can survive 437 days in zero gravity and eventually recover, but the recovery was grueling and the long-term bone and cardiovascular effects were severe. The 750-day circumnavigation would push far beyond what any human has experienced in microgravity, and the crew would need to survive atmospheric entry at the end of it. The Bellcomm team’s “if” has been answered: artificial gravity is not optional for a two-year mission. The tethered rotation architecture described in the previous post addresses this, using the spent Earth departure stage as a counterweight exactly as the Bellcomm team used the S-IVB — the same concept, applied to the same problem, six decades later.

The Trajectory

The 1973 Venus flyby trajectory had an injection velocity of 3,932 m/s from a 185 km circular parking orbit, and an Earth return velocity of 13,655 m/s. These numbers frame an important comparison with the 2034 EVMVE mission.

The 2034 circumnavigation departs at approximately 4.23 km/s from a 200 km parking orbit — essentially the same departure energy as the 1973 Venus flyby. But the Earth return velocity is dramatically lower: 11.5 km/s versus 13.7 km/s. The circumnavigation returns more gently than the simple Venus flyby, despite having traveled immeasurably farther. This is a consequence of the triple-planet trajectory’s geometry — the two Venus gravity assists on the outbound and return legs, combined with the nearly tangential Mars encounter, leave the spacecraft on a much more benign Earth approach than a direct Venus round-trip would produce.

The Bellcomm study confirmed that the Apollo Command Module heat shield could be modified to survive 13,655 m/s entry without retropropulsion, with an entry corridor of 34 km between the overshoot and undershoot limits — manageable, but demanding. At 11.5 km/s, the 2034 return is substantially more forgiving. If the Bellcomm team showed that an Apollo CM could survive the harder problem, the easier problem is clearly within the performance envelope of modern heat shield technology.

It is also worth noting that VanderVeen had already mapped this entire flyby landscape before discovering the low-energy 1977 triple-planet trajectory. In a May 1966 Bellcomm survey memo — written nearly two years before he found the 1977 conversion opportunity — VanderVeen catalogued the various classes of manned flyby missions available in the 1970s: high-energy lightside Mars flybys, high-energy darkside flybys, low-energy “twilight” Mars flybys, dual-planet flybys (Earth-Venus-Mars-Earth or Earth-Mars-Venus-Earth), and simple Venus flybys. He compared them all on a common mass basis, normalizing to a 213,800 kg 1979 Mars twilight flyby reference. The 1973 Venus flyby came in at a mass ratio of 0.70 — about 150,000 kg of mass-in-Earth-orbit, the cheapest of any class. The 1972 dual-planet Earth-Venus-Mars-Earth mission came in at 1.18, only modestly more expensive than the reference, with a 464-day duration. The 1979 Venus-swingby Mars orbiter mission with an 8-day Mars stopover required 4.32 km/s of total ΔV and would have placed 1,060,000 kg in Earth orbit. The trajectory landscape was understood. The cheapest entry point was a Venus flyby — exactly the mission Bellcomm was sized for in 1967.

What VanderVeen discovered the following year was not a new class of trajectory but a remarkable coincidence: in 1977 and again in 1983, the departure conditions for a low-energy triple-planet flyby and a simple Venus flyby were nearly identical, allowing one to be converted into the other at Venus with a small midcourse burn. This converted the simple Venus flyby — already the cheapest crewed planetary mission — into a circumnavigation of the inner solar system at essentially no additional cost, with a four-month abort option built in. The 1977 window was the first such opportunity identified, but they recur every 6.4 years. The 2034 window which I identified is the best one in decades.

Exactly how much harder is the Venus flyby return problem relative to the EVMVE? The answer comes from a companion 1965 Lockheed study — NASA Contractor Report CR-308, “Study of Heat Shielding Requirements for Manned Mars Landing and Return Missions” — which examined this question in quantitative detail across a wide range of entry velocities and vehicle configurations. Its results are directly applicable here, since the one-year Venus flyby missions have essentially the same Earth entry conditions as the lower end of what CR-308 analyzed.

The Heat Shield: What the Numbers Actually Say

The Lockheed CR-308 report examined Apollo-configuration heat shielding requirements for Earth entry velocities ranging from 11.0 to 22.9 km/s, covering everything from lunar return through interplanetary return velocities. Some key numbers from their analysis:

Mission Entry velocity Vehicle weight Shield weight Shield/vehicle
EVMVE 2034 (this mission) 11.5 km/s ~4,500 kg <10% Favorable
Apollo lunar return 11.0 km/s ~5,000 kg Baseline Baseline
1973 Venus flyby return 13.7 km/s 4,536 kg 680 kg 15%
M2 lifting body, max corridor 20.7 km/s 4,500 kg Much higher Upper limit

The Venus flyby return at 13.7 km/s requires a heat shield representing about 15% of the vehicle’s total mass. This is real — it is substantially heavier than the Apollo lunar heat shield — but it is not catastrophic. A 4,536 kg capsule returning from a Venus flyby needs about 680 kg of heat shield material. For comparison, the Apollo CM heat shield weighed approximately 385 kg returning from the Moon; the Venus flyby shield is roughly twice that, which is the penalty for the additional 2.7 km/s of entry velocity.

The 2034 EVMVE, returning at 11.5 km/s — closer to the Apollo lunar return than to the Venus flyby return — would require a shield mass fraction well below 15%, likely in the 8–10% range based on the CR-308 curves. This is consistent with a straightforward upgrade of an existing Apollo-class or Dragon-class heat shield, not a materials breakthrough.

What makes the Lockheed study particularly reassuring is a counterintuitive finding buried in their analysis of charring ablator performance. They found that heat shield mass does not scale linearly with entry velocity — and in fact, at higher heating rates, charring ablators become more efficient. A sixfold increase in total heat load increased required shield thickness by less than 30%. The reason is that at intense heating rates, the ablation products vaporizing off the shield surface blow outward through the boundary layer, partially blocking incoming heat from reaching the shield surface. At the most extreme heating rates they examined, this mass injection effect becomes so strong that it effectively blows off the thermal boundary layer entirely, stopping convective heating altogether. The ablator shields itself. This is why the Apollo shape — highly blunt, allowing the bow shock to do most of the work — remains the most mass-efficient configuration all the way up to about 15.2 km/s. Above that, slender high-lift configurations like the M2 can reach higher velocities with a manageable corridor, but require significantly more shield mass.

The practical implication for our mission: the 2034 EVMVE’s 11.5 km/s return sits in the most benign portion of the interplanetary entry regime. The heat shield is a well-understood engineering problem, solved in principle by Apollo, improved substantially by SpaceX’s PICA-X development, and not close to any material performance limit. The Lockheed team in 1965 was examining entry velocities nearly twice as high as what the 2034 circumnavigation requires. The heat shield is not the mission’s hard problem.

What is the hard problem, returning from the harder one-year Venus flyby, is the entry corridor. The Bellcomm study found a 34 km corridor between overshoot and undershoot for the 13.7 km/s Venus flyby return — narrower than the lunar return corridor, requiring more precise navigation and guidance in the final approach. For the EVMVE at 11.5 km/s, the corridor is wider and the navigation problem is correspondingly easier. But in either case the Lockheed analysis confirms: “Entry into the earth atmosphere upon return from a Mars mission can be accomplished by relatively simple maneuvers using the trimmed-lift, roll-control mode.” The same applies to Venus flyby returns. Roll-controlled lifting entry — the same mode used by Apollo — handles it.

The 1973 mission also had a far more brutal abort window than the EVMVE. The Bellcomm study analyzed post-injection abort capability and found that it existed for only the first 65 minutes after injection. After that, the crew’s propulsion was insufficient to return them to Earth within the CSM’s operational lifetime, and they had to accept the full 396-day mission. The 2034 EVMVE provides an abort window of 132 days — the entire outbound leg to the first Venus encounter. After Venus, the crew is committed, but for more than four months they have the option to apply a small burn at Venus and return home on the free-return trajectory. This represents an enormous improvement in crew safety architecture, entirely attributable to the fortuitous properties of VanderVeen’s trajectory class.

Mariner 10: The Robotic Proof of Concept

There is a remarkable coincidence embedded in this history that deserves explicit attention.

The Bellcomm reference mission departed Earth on October 31, 1973, and flew past Venus on March 3, 1974. NASA’s Mariner 10 launched on November 3, 1973 — just three days later — and reached Venus on February 5, 1974. While the Bellcomm team was writing the engineering study for a crewed Venus flyby in that exact launch window, NASA was simultaneously flying an unmanned spacecraft through the same interplanetary corridor to validate, for the first time in history, the very mechanism that makes multi-planet flyby trajectories work.

Mariner 10 was the first spacecraft to use the gravitational pull of one planet to reach another, and the first probe to visit two planets. It flew past Venus, used the gravity assist to redirect toward Mercury, and made three encounters with the innermost planet before its fuel ran out. During the Venus gravity assist, Mariner 10’s heliocentric velocity dropped from 37.008 km/s to 32.283 km/s in just four hours — a velocity change of nearly 5 km/s accomplished entirely by Venus’s gravity, at zero propellant cost. This is the same physical mechanism — a close planetary passage bending the spacecraft’s trajectory and exchanging momentum with the planet — that the EVMVE trajectory relies on at both Venus encounters.

The differences between Mariner 10’s trajectory and the EVMVE are instructive. Mariner 10 went inward from Venus toward Mercury. The EVMVE goes outward from Venus toward Mars, then bends back inward past Venus again to return to Earth. But the Venus gravity assist that does the bending is structurally identical. Mariner 10 demonstrated in 1974 that a spacecraft could swing past Venus and emerge on a precise new trajectory, hitting a target — Mercury — months later. The two-Venus-one-Mars trajectory is a more elaborate version of exactly what Mariner 10 proved.

The total mission cost was budget-capped at $98 million — in 1973 dollars, roughly $700 million today. For that sum, NASA obtained the first proof that gravity assists work as advertised, the first close images of both Venus and Mercury, and a trajectory that permitted two additional Mercury flybys at six-month intervals because the spacecraft’s orbit was resonant with Mercury’s. The mission was, in every relevant sense, a proof of concept for multi-planet ballistic flyby trajectories at zero additional propellant cost.

The irony is layered. The Bellcomm engineers were designing a crewed mission that would depart in the same window as Mariner 10, using the same Venus gravity assist mechanism. VanderVeen had already shown — in the 1968 memo and the 1969 journal paper — that a triple-planet ballistic flyby was possible at essentially the same departure energy. And NASA, that same year, flew a robotic spacecraft that validated the gravity assist technique upon which the entire mission concept depends. The three pieces of work — the crewed mission design, the triple-planet trajectory analysis, and the robotic gravity-assist demonstration — were all occurring simultaneously, in the same launch window, and they were never connected into a program.

Mariner 10 proved the physics. Bellcomm proved the spacecraft engineering. VanderVeen proved the trajectory. Nobody put the three together and flew the mission.

What the Crew Was Supposed to Do

The 1967 Bellcomm vehicle study answered the question of whether the crew could survive the trip. A second Bellcomm document, completed in November 1967 by D. E. Cassidy, C. L. Davis, and M. H. Skeer — TR-67-730-1, “Preliminary Considerations of Venus Exploration via Manned Flyby” — answered a different question: assuming they got there, what would they actually do?

The answer was an ambitious planetary science campaign organized around three Venus encounters: the 1977 triple-planet mission’s two Venus passes, and a 1978 dual-planet Venus flyby that would build on the data returned from the first two. Total Venus probe complement across both crewed missions was 12,300 kg in 1977 and 8,600 kg in 1978 — more than 21 metric tons of robotic spacecraft launched together with the crew, deployed under their direction during close approach, and operated through orbital relays after the spacecraft departed.

The 1977 first-pass complement was designed to characterize the atmosphere and begin surface exploration: six drop-sondes targeting different solar geometries (sub-solar, anti-solar, terminator, mid-light side, mid-dark side); four meteorological balloon probes deployed at varied altitudes for circulation studies; two small landers, one near the north pole and one on the mid-light side; two photo-RF probes returning images during atmospheric descent; and a polar orbiter for global radar mapping. The second pass, fourteen months later, was reserved for follow-up: five additional landers and five additional photo-RF probes, deployed to specific surface targets identified from the first-pass data.

The 1978 mission was the most scientifically interesting. Two high-altitude buoyant Venus devices — 25-meter hydrogen-filled super-pressure balloons designed to float in the temperate region between 40 and 60 km altitude for one to six months — would carry electron microscopes, mass spectrometers, gas chromatographs, and culture growth experiments specifically designed to detect aerosol-borne life forms in the Venusian cloud layer. Two near-surface floaters — 9-meter steel-fiber-weave balloons with liquid-hydrogen-cooled instrument capsules rated for 540°C surface temperatures — would descend on 600-meter tethers, anchor near the surface, and acquire samples with clam-shell devices for on-board analysis.

Reading this document fifty-eight years after it was written, the historical irony is overwhelming. Almost everything in this campaign has now been done — but as separate uncrewed missions, conducted over decades, often with more thoroughness than the crewed mission could have managed.

The atmospheric drop-sonde campaign was effectively flown by NASA’s Pioneer Venus Multiprobe in December 1978 — four probes targeting different latitudes and longitudes, returning atmospheric profiles down to the surface. The results validated and dramatically refined the atmospheric models the Bellcomm team had been working from. The same mission’s orbiter conducted radar mapping of approximately 93% of the surface at coarse resolution from 1978 through 1992. The polar orbiter that the Bellcomm team had specified, with its X-band mapping radar, was effectively flown by NASA’s Magellan mission from 1990 through 1994 — at vastly higher resolution than the 1977 plan would have achieved, mapping 98% of the surface at 100-meter resolution and producing the topographic dataset that remains the foundation of Venus geology to this day.

The meteorological balloon concept was partially realized by the Soviet VeGa mission in 1985, which deployed two small helium-filled balloons into the Venusian cloud layer during gravity-assist flybys en route to Halley’s Comet. Each balloon operated for about 46 hours, drifting roughly 11,000 km across the planet and confirming the atmospheric circulation patterns the Bellcomm team had hoped to characterize. The Soviet Venera lander program — Venera 7 through 14, plus the VeGa landers — accomplished what the Bellcomm landers were designed to do, multiple times over, between 1970 and 1985: landing on the surface, returning images and soil composition data, surviving for between 23 minutes (Venera 7) and 127 minutes (Venera 13) in the brutal surface environment.

The high-altitude biological experiment — the search for aerosol life in the Venusian cloud layer — has not been flown as a dedicated mission, but the question itself remains live. The 2020 announcement (later disputed) of phosphine in the Venus atmosphere, and ongoing analysis of cloud-layer chemistry from Venus Express (ESA, 2006–2014) and Akatsuki (JAXA, 2015–present), continue to grapple with whether the temperate cloud-deck altitudes the Bellcomm team identified might in fact harbor microbial life. The DAVINCI mission, currently under development, will conduct in-situ atmospheric chemistry analysis during descent in the early 2030s. The biological question is being addressed; the equipment is more sophisticated than what fit on a 1967 balloon; the answer, when it comes, will not require a crewed observer.

The near-surface floater — a tethered balloon descending to within hundreds of meters of the surface to acquire samples — has not been built, and remains genuinely difficult. The closest analog, the Soviet VeGa balloons, operated only at high altitude. The 9-meter steel-fiber-weave balloon with active liquid-hydrogen cooling that Cassidy, Davis, and Skeer described in 1967 was a remarkable piece of engineering; nothing like it has flown since, primarily because no Venus mission has needed that capability. Future Venus aerial platforms — the proposed Venus Aerobot concepts at JPL, balloon designs in development at various academic groups — still struggle with the same constraints the Bellcomm team identified, and have not yet matured to flight.

The point of this comparison is not that the Bellcomm team got it wrong. They got the science exactly right. The campaign they designed for crewed flyby in 1977–1978 anticipated, in essentially every particular, the robotic exploration of Venus that took place over the following half-century. Their drop sondes were Pioneer Venus. Their orbiter was Magellan. Their landers were Venera. Their balloons were VeGa. Their long-duration aerosol biology experiment is what DAVINCI and follow-on missions are still trying to do. The list is almost complete.

What the crewed flyby would have added, beyond robotic spacecraft, was real-time human supervision during deployment — the ability to retarget probes based on what was being seen, to reprogram experiments mid-mission, to make judgment calls about where to send the next lander. This is genuinely valuable, and there are scenarios where a human supervisor a few light-seconds away can outperform a ground operator twenty light-minutes away. But it is a marginal advantage relative to what the Bellcomm team’s robotic campaign was already designed to accomplish autonomously, and it does not justify the cost differential between a crewed and uncrewed mission. The science case for crewed Venus flyby was overtaken by robotic capabilities almost immediately after the 1967 study was written. The Mariner 10 robotic flyby in 1974 — the same launch window the Bellcomm crewed mission was sized for — accomplished more first-of-kind planetary science, at $98 million in 1973 dollars, than any crewed mission could have done at any imaginable cost.

This is part of why the Venus flyby was never flown, and why the 2034 EVMVE circumnavigation should not be sold on its scientific merit. The science has been done, or is being done, by spacecraft that do not require return trajectories or radiation shelters or 750-day life support systems. What the crewed mission offers is something different: the experience of being there, the human achievement of crossing the inner solar system, and the records that come with it. The Bellcomm planetary science team, working in 1967, did not have to make this argument because the robotic campaign they were anticipating had not yet flown. We do. The honest framing of the 2034 mission is not as a science mission but as an exploration mission — closer in spirit to Lindbergh than to Mariner 10 — and that framing is more defensible, not less, because the robotic alternative is so capable.

Radiation Shielding

The Bellcomm study identified solar cosmic radiation as the dominant hazard of the mission. Galactic cosmic ray background was acknowledged but less threatening than the acute dose from a major solar particle event. The study’s design criterion was to protect the crew against the worst year measured to that date — 1959, an unusually active solar year — which required shielding of approximately 49 kg/m² of crew volume.

The solution was a storm shelter: a reduced, heavily shielded volume within the spacecraft where the crew would retreat during a solar particle event. Non-sensitive equipment — food, water, waste water — was placed around the periphery of this shelter, contributing to the shielding mass without adding dedicated radiation shielding weight. The overall structure of the S-IVB hydrogen tank, with its large radius and the mass of systems distributed around its interior, provided partial shielding during normal cruise operations.

This is precisely the approach described in the previous post for the 2034 circumnavigation — a storm shelter lined with consumables, providing the crew a protected volume during SPE events. The concept has not changed in fifty-seven years because the physics has not changed. What has improved is our understanding of the radiation environment, our ability to predict solar events with some lead time, and our knowledge of the long-term biological effects of galactic cosmic ray exposure.

The GCR dose for a 750-day mission is approximately 750–1,500 mSv — meaningfully above Earth-surface background, enough to increase long-term cancer risk, but not acutely life-threatening. The Bellcomm team was working with 1960s radiobiology; their conservative shielding estimates may actually be more than sufficient by modern standards for the GCR component, while remaining appropriate for SPE protection. The storm shelter concept is sound. The uncertainty is not in the engineering but in the individual crew member’s willingness to accept an elevated long-term cancer risk — which is ultimately a personal decision, not an engineering constraint.

Life Support and Consumables

The study selected a semi-closed ecological system that recycled water but not carbon dioxide. Oxygen was stored cryogenically. The authors noted that even with modest leakage rates, the system was heavier than ideal, and that additional recycling would complicate an already difficult technology without proportional mass savings. Their conclusion: reduce leakage rates by minimizing airlocks and hatches, rather than trying to close the ecological loop more completely.

For the 2034 mission, the calculus has shifted somewhat. Water recycling technology has advanced enormously since 1967 — the ISS water recovery system processes approximately 90% of cabin humidity and urine back to potable water, and further improvements are in development. CO₂ removal and oxygen recovery systems have similarly improved. But the Bellcomm team’s fundamental insight remains correct: for a mission of this duration, reliability of the life support system matters more than its mass efficiency. A slightly heavier system that is robust and redundant is preferable to a lighter system with more failure modes.

The Bellcomm study allocated consumables for three crew members for approximately 400 days, within the mass budget of a single Saturn V. For the 2034 mission, the crew is one or two people for 750 days, and the departure vehicle is far more capable than a Saturn V in terms of mass to orbit per dollar. The consumables budget is not the constraining problem.

Power: Solar Cells, Then and Now

On electrical power, the Bellcomm study’s conclusion was unambiguous: “Solar cell electrical power is a clear choice for both flyby and long duration systems.” Fuel cells — the Apollo standard — were rejected for long-duration missions because of their consumable hydrogen and oxygen requirements. Nuclear power was not considered mature enough. Solar cells, particularly fixed non-articulating arrays mounted on the S-IVB exterior, provided adequate power throughout the mission’s range of solar distances (0.7 to 1.2 AU from the Sun) with significant redundancy.

The 2034 EVMVE traverses similar solar distance ranges. At Mars (approximately 1.44 AU), solar flux falls to about 48% of Earth-normal — lower than the Bellcomm mission’s aphelion, but still workable for high-efficiency modern solar cells. At Venus (approximately 0.72 AU on the inbound leg), flux reaches about 192% of Earth-normal, well within the thermal management capability of modern spacecraft. The Bellcomm team’s solar cell conclusion holds fifty-seven years later, with the additional advantage that modern multijunction cells are roughly three times more efficient than the silicon cells available in 1967.

Communications: The Unchanging Problem

The Bellcomm study confirmed that the sun-spacecraft-Earth angle never drops below 27° throughout the Venus flyby mission, meaning solar noise would not interrupt the communications link. The study required continuous deep-space network tracking, with the spacecraft transmitting all scientific data to Earth rather than relying on tape return.

For the 2034 mission, the geometry is similar. The spacecraft spends most of its time at solar elongation angles well clear of solar conjunction, with communications interrupted only during brief periods if any. Maximum one-way light travel time at Mars closest approach is approximately 12 minutes. This is not a communications problem in the engineering sense — high-gain antennas of modest aperture can close the link budget at Mars distance with modern transmitter and ground station technology. It is a human factors problem: the crew has a 24-minute round-trip delay for any Earth conversation, and mission control cannot intervene in real time during emergencies.

The Bellcomm team’s communications conclusions were sound in 1967. The 2034 challenge is not link budget but latency, and latency cannot be solved by engineering — only by crew training, autonomy, and psychological preparation.

Development Cost: Apollo vs. Commercial

The Bellcomm study was written in the context of an agency with an annual budget measured in the tens of billions of dollars (in today’s money) and a mature heavy-lift vehicle in production. The Saturn V cost approximately $185 million per flight in 1967 dollars — roughly $1.7 billion in 2026 dollars. Three of them were proposed for the development flight test program, plus the operational mission. Development of the ESM module and modifications to the CSM and S-IVB would have required additional investment. Total program cost was not estimated in the document, but it would have been substantial by any measure.

The 2034 circumnavigation operates in a fundamentally different cost environment. A Falcon Heavy launch currently costs approximately $150 million — roughly one-tenth of a Saturn V in real terms. Starship, when operational at scale, aims for launch costs measured in the tens of millions per flight. The commercial habitat and crew capsule market, which barely existed when I opened the NSF thread in 2009, now has multiple serious players. The hardware that Bellcomm’s team had to design from scratch — the environmental support module, the modified command module, the long-duration life support system — has near-equivalents available commercially or in advanced development.

The Bellcomm study demonstrated that a one-year manned interplanetary mission was feasible within the constraints of a government program in 1967. The same conclusion, applied to today’s commercial capabilities and cost structure, suggests that the 2034 circumnavigation is feasible within the constraints of a well-funded private effort — at a cost perhaps two orders of magnitude lower than the Apollo-era equivalent.

What Bellcomm Got Right and What Has Changed

Reading the 1967 Bellcomm report and the 1965 Lockheed heat shield study alongside the 2034 mission analysis, the continuities are more striking than the differences. The storm shelter approach to radiation protection: unchanged. The use of solar cells for power: unchanged. The semi-closed life support architecture: refined but structurally similar. The identification of long-duration reliability as the dominant design driver: more true today than ever. The recognition that zero-gravity physiology was an open question: answered, and the answer requires artificial gravity. The confirmation that atmospheric entry from interplanetary velocity is manageable with a blunt ballistic capsule and an ablative heat shield: confirmed repeatedly in the decades since, and now quantified with the precision the Lockheed study provided.

On that last point the Lockheed CR-308 study is worth quoting directly: “Atmospheric braking of hyperbolic entry vehicles appears thermally feasible provided that efficient configurations and heat shield materials are selected.” This was written in 1965 for entry velocities ranging up to 22.9 km/s — nearly twice what the 2034 EVMVE requires. The conclusion was not hedged. The blunt Apollo shape is thermally efficient precisely because it generates a strong detached bow shock that converts most of the kinetic energy to radiation well ahead of the vehicle surface, rather than transferring it conductively through a thin boundary layer. The ablator then handles what gets through, becoming more efficient as the heating rate increases. The physics works in favor of getting home.

What has fundamentally changed is the cost structure. The Bellcomm team was designing within a government program with government budget constraints and government risk tolerance. The 2034 circumnavigation is a different kind of mission: private, voluntary, and accepting of risk levels that no government program could countenance. This is not a weakness of the mission concept — it is its defining feature. The historical parallels are not Apollo but Lindbergh, not the space shuttle but the Voyager aircraft that completed the first nonstop around-the-world flight in 1986.

The Bellcomm report concluded in 1967 that a manned Venus flyby was feasible and that its technical conclusions were applicable to guiding long-duration system development. The Lockheed study, two years earlier, confirmed that getting home from interplanetary velocity was a solvable heat shield problem, not a materials miracle. Nobody followed that guidance toward a flight. The AAP shrank and eventually became Skylab — three missions to a single Earth-orbiting station, remarkable achievements in their own right but a long way from interplanetary space. The Venus flyby window opened in 1973 with no one ready to fly it.

The Fifty-Seven Year Lag

There is something worth sitting with in the chronology.

In 1967, Bellcomm engineers demonstrated that a manned Venus flyby was feasible with existing hardware. In 1968, VanderVeen discovered that the triple-planet trajectory made a circumnavigation of the entire inner solar system possible at essentially the same energy cost, with a four-month abort option built in. In 1969, that result was published in the peer-reviewed literature. The 1973 window opened and closed. The 1977 window — the one with the most favorable geometry VanderVeen had identified — opened and closed. The opportunities have continued to come, approximately every six years, for more than fifty years.

In 2009, I opened a forum thread arguing that the mission was within reach of a private effort using commercial hardware. The Augustine panel was considering something similar. SpaceX was flying its first Falcon 1. Bigelow was building habitat modules. Nothing came of it.

The 2034 window opens on August 4th. Between now and that date, approximately eight years remain. That is not a long time to develop and test life support systems for a 750-day mission, commission and qualify a habitat module, design and build an Earth departure stage, certify a heat shield for hyperbolic entry, and train a crew for the most demanding and isolated human spaceflight ever attempted.

But it is not an impossible time. The Bellcomm team showed in 177 pages that the engineering was tractable in 1967. The commercial space industry has made most of the individual pieces available or nearly so. The remaining work is integration, testing, and will.

The 1967 report sits in the NASA Technical Reports Server at accession number 19790072165. It is freely available to anyone who wants to read it. Its authors demonstrated, more than half a century ago, that humans could travel to another planet and return safely on a single launch vehicle with Apollo-derived hardware. They were right. The mission they designed was never flown.

The 2034 window will not wait for committees or consensus. The trajectory opens when the planets are in the right positions, and closes again regardless of what we decide to do about it. VanderVeen’s trajectory family has already cycled through more opportunities than most space programs have had missions. Sooner or later, someone will fly it. The question is only whether that happens in 2034 or in some future cycle when perhaps the will finally matches the capability that has existed, in principle, since before the first Moon landing.


The Bellcomm vehicle study discussed in this post — “Manned Venus Flyby,” TR-67-600-I-I, February 1, 1967, by M. S. Feldman, L. A. Ferrara, F. L. Havenstein, J. E. Volonte, and P. H. Whipple — is available from the NASA Technical Reports Server at accession number 19790072165. The companion Venus science study is D. E. Cassidy, C. L. Davis, and M. H. Skeer, “Preliminary Considerations of Venus Exploration via Manned Flyby,” Bellcomm TR-67-730-1, November 30, 1967. The earlier flyby trajectory survey is A. A. VanderVeen, “A Survey of Manned Mars and Venus Flyby Missions in the 1970’s,” Bellcomm Memorandum for File, May 17, 1966, Case 103-2 (NASA CR-152882). The heat shield analysis is drawn from Lockheed Missiles and Space Company, “Study of Heat Shielding Requirements for Manned Mars Landing and Return Missions,” NASA Contractor Report CR-308, October 1965, prepared under Contract NAS 2-1798. The triple-planet flyby trajectory analysis is from A. A. VanderVeen, “Triple-Planet Ballistic Flybys of Mars and Venus,” Journal of Spacecraft and Rockets, Vol. 6, No. 4, April 1969, and VanderVeen’s preceding internal Bellcomm memo TM-68-1013-2, April 1968.

Posted in Uncategorized | 1 Comment

Manned Circumnavigation of the Inner Solar System

In 1969, a Bellcomm engineer named A. A. VanderVeen published a paper describing a family of trajectories so elegant they seem almost accidental. Fifty-five years later, the most attractive instance of that trajectory family departs Earth in August 2034. This post is about what it would mean to fly it.

Back in February 2009, I opened a thread on the NASASpaceFlight.com forum with what I thought was a simple thought experiment: what interplanetary mission might be within reach of an extremely wealthy private individual — not for scientific merit, but purely for the historical record? Something that would put a human being somewhere no human had ever been, set records that might stand for generations, and require the kind of courage that makes a person famous forever?

I had been reading an old paper, published in April 1969 in the Journal of Spacecraft and Rockets, authored by A. A. VanderVeen of Bellcomm Inc. — the systems engineering firm that supported NASA during Apollo. The paper was titled “Triple-Planet Ballistic Flybys of Mars and Venus,” and it described something that had been discovered almost by accident: a family of round-trip trajectories from Earth that would fly past Venus, then Mars, then Venus again, and return — all without any propulsive maneuver after the initial departure burn. The planets themselves would do the work.

The NSF thread ran for over a hundred pages and several years. It attracted serious engineers and enthusiastic amateurs, but none of it came to anything then. But the trajectory doesn’t care about programmatic timelines. It comes around again whether we’re ready or not.

The most attractive upcoming instance of this trajectory departs Earth on August 4, 2034. I’ve run the numbers with JPL’s MIDAS trajectory optimization code, and the results are striking. This post is my attempt to lay out the full case for what I’ve been calling the “inner solar system circumnavigation” — the trajectory, the history, the mission design implications, and why I think it deserves serious attention from whoever has the resources and the nerve to fly it.

The VanderVeen Discovery

To understand the 2034 opportunity, you need to understand what VanderVeen actually found — because it’s considerably more subtle than a simple gravity-assist tour.

By the mid-1960s, NASA contractors had catalogued most of the obvious interplanetary trajectory opportunities. Single-planet flybys were well understood. Mars stopover missions via Venus swingby had been studied extensively. What had not been found was a clean, low-energy, fully ballistic trajectory that would fly past Venus, fly past Mars, fly past Venus again, and return to Earth — all as a single connected trajectory with no deterministic maneuvers after departure.

VanderVeen found this trajectory class, and he found it in a characteristic way: by accident. He was investigating whether a spacecraft could depart on the easy trajectory of a simple Venus flyby mission and then, at Venus, fire a small rocket to redirect itself onto a triple-planet profile. During the investigation, something surprising happened. The required maneuver at Venus didn’t just become small — it approached zero. He had accidentally discovered a new family of ballistic triple-planet flyby trajectories whose energy requirements were lower than any previously identified, and whose first leg was identical to a simple roundtrip Venus flyby.

The structure of these trajectories is elegant. The spacecraft departs Earth, swings past Venus on the way inward, continues outward to a nearly tangential encounter with Mars, then swings past Venus again on the way back, and finally returns to Earth. The profile is nearly symmetric — the outbound and inbound halves mirror each other — and the planetary encounters are all relatively gentle. The Mars flyby in particular is nearly tangential, which is what keeps the encounter velocity low and the trajectory energy moderate.

VanderVeen identified three distinct classes of this trajectory, characterized by which type of Venus swingby geometry they employ. The most attractive class — the one he called #5/#5 — occurs when the outbound and inbound Venus swingbys are both of the “type 5” variety, which produces the symmetric profile and the lowest energy requirements. This class recurs approximately every 6.4 years, though the 6.4-year repeatability is only qualitative. The actual availability of a clean ballistic solution depends on Mars’s heliocentric distance at the time of its encounter with the spacecraft, and not every 6.4-year cycle produces a usable trajectory.

The 1977 opportunity — the specific case VanderVeen analyzed in detail — had a nominal mission duration of 720 days and required a departure delta-V of approximately 4.24 km/s from a 200 km circular Earth orbit. The Earth return velocity was about 11.95 km/s — high, but survivable with a robust heat shield. VanderVeen noted that the 1977 opportunity coincided almost perfectly with a simple Venus flyby mission window, which meant that the crew could fly the Venus flyby trajectory until they reached Venus, and then, if all was well, apply a burn of less than 150 m/s to redirect onto the triple-planet profile. If anything had gone wrong, they simply continued on the Venus free-return trajectory and came home — saving almost a year compared to completing the full mission. This abort option is one of the trajectory’s most attractive features.

The 1977 window opened. No one flew it. The 1983 window opened. No one flew it. The opportunities have kept coming, approximately every six years, through 1989, 1996, 2002, 2009, 2015, 2021, 2028. Now 2034 is approaching, and it may be the most attractive opportunity of the modern era.

The 2034 Opportunity: What the Numbers Say

I ran the 2034 trajectory through JPL’s MIDAS optimization code, searching for the minimum delta-V Earth-Venus-Mars-Venus-Earth trajectory in the 2034–2036 timeframe. The code converged in 27 iterations to a clean solution. Here is what it found.

Mission timeline:

Event Date Elapsed days Notes
Earth departure August 4, 2034 0 Departure burn from LEO
Venus flyby #1 December 14, 2034 132 Abort window closes here
Mars flyby May 16, 2035 286 Very distant, nearly tangential
Venus flyby #2 March 14, 2036 589 Final gravity assist for Earth return
Earth arrival August 23, 2036 750 Atmospheric entry at ~11.5 km/s

Total mission duration: 750 days — just over two years, and almost exactly the duration VanderVeen calculated for the analogous 1977 mission. The near-identical duration is not a coincidence; it’s a consequence of the same underlying planetary geometry repeating itself.

Departure: The minimum delta-V from LEO to start this trajectory is 3.986 km/s, corresponding to a hyperbolic excess velocity of 4.186 km/s and a C3 of 17.52 km²/s². From a 200 km circular parking orbit, the actual departure burn is approximately 4.23 km/s. The departure asymptote has a declination of +35.8°, which means the trajectory leaves Earth on a fairly steep angle above the ecliptic plane — a factor to consider in launch site and inclination planning, but not a prohibitive constraint.

Venus flyby #1 (Day 132): The spacecraft passes Venus at a closest approach distance of 6,584 km from Venus’s center — approximately 532 km above the surface, well clear of the atmosphere. The flyby velocity relative to Venus is 6.53 km/s, and the gravity assist bends the trajectory by 64.9°. This is a substantial turn — Venus is doing real work here, redirecting the spacecraft from its inbound trajectory toward Mars. The flyby geometry is nearly polar (inclination 96.7°), which means the spacecraft passes over Venus’s poles rather than its equator.

This is also the last moment at which a return to Earth on the abort trajectory remains practical. After Venus #1, the spacecraft is committed to the full mission.

Mars flyby (Day 286): This is where the trajectory’s elegant character becomes most apparent. The spacecraft passes Mars at a distance of 71,855 km from Mars’s center — roughly 68,600 km above the surface, well outside even Deimos’s orbit at 23,459 km. The flyby velocity relative to Mars is 9.48 km/s, and the gravity assist bends the trajectory by only 0.76°. Mars barely deflects the spacecraft at all.

This seems counterintuitive — why fly past Mars at such a large distance, with such a tiny bend angle? The answer is that in the #5/#5 trajectory class, Mars is not providing most of the gravity assist energy. Its role is primarily geometric: the spacecraft’s encounter with Mars sets the timing and phase for the return trajectory back toward Venus. The nearly tangential Mars encounter is what keeps the flyby velocity low (and thus the mission energy moderate), and it’s also what makes the trajectory profile nearly symmetric — the outbound and inbound legs have similar shapes.

There is an important practical implication of the large flyby distance: the crew will see Mars at roughly half the angular diameter of the Moon as seen from Earth, rather than the overwhelming close-up view that a low-altitude flyby would provide. That said, they will be the first humans ever to see Mars with their own eyes from interplanetary space, and for 286 days of transit they will have watched it grow from a dot to a resolved disk. That still counts.

Venus flyby #2 (Day 589): The return Venus encounter passes at 8,318 km from Venus’s center — about 2,266 km above the surface, slightly higher than the first flyby. The flyby velocity is 6.01 km/s and the bend angle is 62.6° — again a substantial gravity assist turn. This second Venus encounter redirects the spacecraft from its outbound trajectory back toward Earth for the final 161-day coast to arrival.

Earth arrival: The spacecraft returns to Earth on August 23, 2036, with a hyperbolic excess velocity of 3.950 km/s. This corresponds to an atmospheric entry velocity of approximately 11.5 km/s. For comparison, the Apollo capsules entered at about 11 km/s returning from the Moon. This mission’s entry velocity is slightly higher, but the heat shield technology has advanced enormously since 1969, and SpaceX has demonstrated Dragon capable of hyperbolic Earth entry in testing. The entry speed is challenging but not exotic.

What Makes This Trajectory Special

The numbers above describe a specific trajectory, but they don’t fully convey what makes this class of mission so architecturally attractive. Let me try to do that more directly.

No deterministic burns after departure. Once the spacecraft leaves Earth orbit, the only propulsive maneuvers required are small course corrections — trajectory control maneuvers of perhaps 10–50 m/s per leg, well within the capability of any spacecraft with a modest propulsion system. The gravity of Venus and Mars do all the real work. This is not a consequence of clever mission design; it’s a fundamental property of the trajectory class that VanderVeen identified. The planets are in the right configuration to make the whole thing work ballistically. This dramatically simplifies the spacecraft design, reduces the propellant mass required, and eliminates the mission-critical single-point-failure events that would otherwise punctuate a two-year interplanetary flight.

The abort option. For the first 132 days — more than four months — the mission can be aborted by simply not performing the trajectory correction that converts the Venus flyby profile to the triple-planet profile. The abort costs less than 150 m/s, comparable to a routine midcourse correction. The crew continues past Venus, swings back toward Earth, and returns in about 13 months instead of 25. This is not a perfect rescue — 13 months is still a long time to wait for a crew in trouble — but it is a genuine abort option of the kind that most interplanetary mission concepts lack entirely. After Venus #1, there is no abort. The trajectory is committed. But for nearly one-third of the outbound journey, the crew retains a meaningful option to come home early at very modest cost.

The record book. I laid this out in the NSF thread in 2009 and it still applies. The crew of this mission would be:

  • The first humans to leave Earth’s gravitational sphere of influence (the Moon is technically still within it)
  • The first humans to fly past Venus
  • The first humans to fly past Mars
  • The holders of the longest crewed spaceflight in history (~750 days, more than double the current record)
  • The humans who have traveled farthest from Earth
  • The humans who have traveled closest to the Sun
  • The humans who have experienced the highest atmospheric entry velocity

That list is not diminished by the fact that the mission is a flyby rather than a landing. Magellan’s circumnavigation of the Earth was a surface-skimming voyage, not a systematic exploration of every coast. The historical significance of being the first humans to leave the Earth-Moon system and traverse the inner solar system is independent of whether any surface was touched.

The Mission Architecture

I’ve been thinking about mission architectures for this kind of flight for fifteen years. The core argument I’ve made — and still make — is that this is fundamentally a private mission, not a NASA mission. NASA will not voluntarily accept a mission where the probability of crew survival is meaningfully below 99%, where there is no possibility of rescue, and where the scientific return is essentially zero. These are all true of a circumnavigation mission, and they are precisely the properties that make it historically significant. The risk, the isolation, and the absence of any purpose other than the journey itself are the whole point.

The architecture that makes the most sense to me is still the one I sketched in the NSF thread, updated for the hardware that now exists or is in late development:

Habitat: A large inflatable habitat module — Sierra Space’s LIFE module or a Bigelow-derived design — providing 300–500 cubic meters of pressurized volume for one or two crew members. Two years in a telephone booth is a sentence, not a mission. The habitat needs to be genuinely habitable, with room to exercise, sleep comfortably, maintain a greenhouse, and maintain sanity. The mass penalty for adequate living space is trivial compared to the mass of propellant, and the mission duration means that life support reliability is far more important than any single hardware mass optimization.

Crew vehicle: A crew return capsule capable of surviving Earth entry at 11.5 km/s. SpaceX’s Dragon has been demonstrated capable of hyperbolic entry. Orion was designed with lunar return velocities in mind and has significant margin. Either would serve, with appropriate heat shield upgrades. The crew vehicle remains docked to the habitat for the entire mission and is used only for the final Earth return phase.

Propulsion: The departure burn of ~4.23 km/s from a 200 km parking orbit requires an Earth departure stage. For a 30,000 kg mission stack, this implies roughly 50,000–70,000 kg of propellant for a cryogenic upper stage — achievable with a single Falcon Heavy or New Glenn launch, or with in-orbit propellant transfer using Starship. The departure stage is expended after the burn and can be retained on a tether as a counterweight for artificial gravity during the coast phases.

Artificial gravity: Two years of microgravity will destroy a human body, and the mission requires the crew to survive atmospheric entry at elevated g-loads at the end. Tethered rotation — the departure stage connected to the habitat by a cable, spinning around the common center of mass — can provide 1g at reasonable tether lengths and rotation rates. This is the Mars Direct approach that Zubrin advocated, and it is mechanically feasible with existing technology. The Canfield joint solves the course-correction-while-spinning problem by allowing the thrusters to fire in the appropriate direction regardless of the spacecraft’s rotational phase.

The short video below shows a 3D rendering of this configuration: the habitat module (with the crew return capsule at its forward end) and the spent Earth departure stage as counterweight, the tether deploying between them, and the two masses separating into the rotating artificial-gravity configuration that would sustain the crew through the 750-day mission.

The tethered spacecraft configuration proposed for the inner solar system circumnavigation mission. The habitat and crew return vehicle are at left; the spent Earth departure stage serves as the counterweight at right. Rotation of the tethered system provides approximately 1g of artificial gravity throughout the cruise phase.

Communications: At maximum range during the mission — which occurs near Mars at approximately 1.44 AU from Earth, giving a one-way light travel time of roughly 12 minutes — real-time conversation is not possible. The crew will communicate by email, video messages, and asynchronous updates. The bandwidth requirements for maintaining public engagement are actually quite modest by modern standards; the mission’s primary communications challenge is reliability over two years, not bandwidth. A phased array antenna on the habitat, pointed at Earth, provides the link.

Radiation: This is the mission’s most serious engineering challenge. The crew will spend two years beyond the Earth’s magnetospheric protection, accumulating GCR (galactic cosmic ray) dose at a rate of roughly 1–2 mSv per day, plus the unpredictable acute dose from solar particle events. The total GCR dose over 750 days is approximately 750–1,500 mSv — enough to meaningfully increase long-term cancer risk, but not acutely life-threatening. Solar particle events are a more acute concern; a major SPE without shielding can deliver a potentially lethal dose in hours. The mitigation is a storm shelter: a small, heavily shielded volume inside the habitat — lined with water, food, and waste water — where the crew can retreat during an SPE. The shelter doesn’t have to be large; it just has to be dense enough to absorb most of the proton fluence from a Carrington-class event. This has been studied extensively in the context of Mars missions and the mass budget is manageable.

The Comparison to What We’ve Done

It is worth putting this mission in context against the history of human spaceflight.

The longest single continuous human spaceflight on record is Valery Polyakov’s 437 days aboard Mir in 1994–95. The ISS has hosted crew members on missions approaching 370 days. These missions were in low Earth orbit, with resupply, communication, and — if necessary — emergency return available within hours. The circumnavigation mission is 750 days, with no resupply, 12-minute communication delays, and no emergency return after day 132.

The farthest humans have ever traveled from Earth — as of this writing, just three weeks ago — is 406,771 km, achieved by the Artemis II crew on April 6, 2026, surpassing the Apollo 13 record of 400,171 km that had stood for 56 years. Commander Reid Wiseman marked the moment from Orion: “We will continue our journey even further into space before Mother Earth succeeds in pulling us back to everything that we hold dear. But we most importantly choose this moment to challenge this generation and the next to make sure this record is not long-lived.” He was right to say so. The circumnavigation mission would take the crew to roughly 1.44 AU at Mars — approximately 215 million km from Earth, or about 529 times farther than Artemis II’s brand-new record. Artemis II’s achievement is genuinely historic. The circumnavigation would leave it so far behind it would barely register as a comparison.

The fastest atmospheric entry was experienced by the Apollo 10 crew at 11.08 km/s. The circumnavigation mission returns at approximately 11.5 km/s — slightly faster, but the same order of magnitude and within the demonstrated performance envelope of modern heat shield materials.

What the circumnavigation mission is not is a landing. No one touches the surface of Mars or Venus. From a scientific standpoint, the mission is indeed nearly worthless — robotic probes have mapped Venus in radar and studied Mars’s surface and atmosphere far more effectively than any crewed flyby could. But from the standpoint of human achievement, the question is not what you learn. It is where you go and what you endure to get there and back.

Magellan didn’t do chemical analysis of the Pacific Ocean. Amundsen didn’t bring back commercially valuable mineral samples from the South Pole. Lindbergh didn’t carry airmail across the Atlantic. The value of the first human circumnavigation of the inner solar system is the fact of it — the demonstration that human beings can leave the Earth-Moon system, travel for two years through interplanetary space, fly past two planets, and come home alive. That demonstration changes what human civilization considers possible. It always has.

Why Now?

The 2034 opportunity exists whether or not anyone decides to fly it. The trajectory does not care. But the convergence of circumstances that makes this particular window worth discussing seriously is worth noting.

Commercial launch costs have fallen by roughly an order of magnitude over the past fifteen years. Starship, if it delivers on its design intent, reduces the cost of launching mass to orbit to levels that make even ambitious interplanetary missions conceivable on private budgets measured in the low billions rather than the tens of billions that would have been required in 2009. SpaceX has demonstrated autonomous rendezvous and docking, high-performance heat shields, and rapid reusability — all technologies that bear directly on this mission’s feasibility.

The commercial space habitat sector, which barely existed in concept in 2009, now has serious players. Sierra Space, Axiom, and others are building and testing large pressurized modules designed for long-duration human habitation. The physiological challenges of two years in microgravity are better understood than they were when I opened that NSF thread, and the countermeasures — artificial gravity, exercise protocols, pharmaceutical interventions — are more mature.

There are also, for the first time in history, private individuals with the financial resources to consider funding such a mission and the demonstrated appetite for high-risk ventures. The question of whether any of them will turn that appetite toward the inner solar system remains open.

What I can say is this: the 2034 window opens on August 4th. The departure delta-V is 4.23 km/s. The mission duration is 750 days. The Earth return velocity is 11.5 km/s. The abort option is available for the first 132 days. The trajectory has been verified by JPL’s MIDAS optimizer, and it is essentially identical in character to the trajectory VanderVeen identified in 1968 and published in 1969. The physics is settled. The materials exist. The vehicles are either operational or in late development.

The only thing missing is someone who decides that being the first human to circumnavigate the inner solar system is worth two years of their life and a meaningful probability of not coming back.

Magellan thought it was worth it. His name has been attached to the first circumnavigation of the Earth for five hundred years. He didn’t even make it home himself, and we still say his name first.

The 2034 window will open regardless. The question is only whether anyone will be ready when it does.


The trajectory class discussed was originally identified by A. A. VanderVeen of Bellcomm Inc., first in an internal technical memorandum (TM-68-1013-2, April 1968) and then in the peer-reviewed paper “Triple-Planet Ballistic Flybys of Mars and Venus,” Journal of Spacecraft and Rockets, Vol. 6, No. 4, April 1969.

Posted in Bigelow Aerospace, Commercial Space, Mars, Orbital Dynamics, Space Exploration, Space Tethers, Variable Gravity | 7 Comments

Lunar Space Elevator Design

The previous posts in this series described what the lunar space elevator can do. This one works through the structural mechanics that determine how much ribbon material you actually need to build it.

The central engineering question for any space elevator is: how thick does the ribbon need to be? Too thin and it snaps under the loads imposed by the gravitational and centrifugal forces acting along its length. Too thick and the ribbon’s own weight dominates the design, driving up the total mass until the system becomes impractical. The answer is a tapered ribbon — thicker at the balance point (EML2) where tensions are highest, thinner at the surface where they are lowest — and the governing equations tell you exactly how that taper must vary with position.

What makes the lunar elevator tractable, as discussed previously, is that the Moon’s weak gravity keeps the required taper ratio to a modest value of around 4 using materials available today. The derivation below shows exactly where that number comes from.

Setting Up the Problem

Consider a small element of the ribbon at position $x$ along its length, measured from the center of the Earth-Moon system. The element has cross-sectional area $A$, length $dx$, and material density $\rho$. Its mass is:

(1)    \begin{equation*} dm = \rho A \, dx \end{equation*}

This element experiences a net acceleration $a(x)$ from three sources: the Moon’s gravity pulling it toward the Moon, the Earth’s gravity pulling it toward Earth, and the centrifugal acceleration from the rotation of the Earth-Moon system pushing it outward from the system’s center of mass. The net force on the element is:

(2)    \begin{equation*} dF = a(x) \, dm \end{equation*}

In the rotating reference frame of the Earth-Moon system, the net acceleration at position $x$ is:

(3)    \begin{equation*} a(x) = \frac{\mu_L}{(x - \mu^*)^2} + \frac{\mu_E}{(x + \mu)^2} - \omega^2 x \end{equation*}

where $\mu_L$ and $\mu_E$ are the gravitational parameters of the Moon and Earth respectively, $\mu^*$ is the distance from the system barycenter to the Moon, $\mu$ is the distance from the barycenter to the Earth, and $\omega$ is the angular velocity of the Earth-Moon system. The first two terms are gravitational (attractive toward their respective bodies), and the third is centrifugal (repulsive from the barycenter). At EML2, these three terms sum to zero by definition — it is the balance point, the location where a free particle experiences no net force in the rotating frame.

Note that the sign convention here is important. Below EML2 (between the Moon and L2), the Moon’s gravity dominates and the net force pulls the ribbon toward the surface. Above EML2, the centrifugal term dominates and pulls the ribbon away from the Moon. The ribbon is therefore in tension everywhere, with maximum tension at EML2. This is exactly the condition that allows a tethered structure to be self-supporting.

Integrating Along the Ribbon

To find the total change in tension $\Delta F$ between two points $x_0$ and $x_1$ along the ribbon, we integrate the differential force over the ribbon element masses:

(4)    \begin{equation*} \int dF = \rho A \int \left(\frac{\mu_L}{(x - \mu^*)^2} + \frac{\mu_E}{(x + \mu)^2} - \omega^2 x\right)dx \end{equation*}

Separating the integrals:

(5)    \begin{equation*} \Delta F = \rho A \left(\mu_L\int\frac{dx}{(x - \mu^*)^2} + \mu_E\int\frac{dx}{(x + \mu)^2} - \omega^2 \int x \, dx \right) \end{equation*}

Each of these is a standard integral. The gravitational terms integrate to $-1/(x - \mu^*)$ and $-1/(x+\mu)$ respectively, and the centrifugal term integrates to $x^2/2$. Evaluating the antiderivative:

(6)    \begin{equation*} \Delta F = \rho A \left(-\frac{\mu_L}{x - \mu^*} - \frac{\mu_E}{x + \mu} - \frac{\omega^2 x^2}{2}\right) \end{equation*}

Evaluating between the limits $x_0$ (lower point) and $x_1$ (upper point):

(7)    \begin{equation*} \Delta F = \rho A \left(\frac{\mu_L}{x_0 - \mu^*} - \frac{\mu_L}{x_1 - \mu^*} + \frac{\mu_E}{x_0 + \mu} - \frac{\mu_E}{x_1 + \mu} + \frac{\omega^2}{2}(x_0^2 - x_1^2)\right) \end{equation*}

This expression gives the net tension change along any segment of the ribbon as a function of the positions of its endpoints, the material density and cross-sectional area, and the gravitational and rotational parameters of the Earth-Moon system. It is the core structural equation for the lunar space elevator.

The Taper Relationship

The ribbon must not break. At any point along its length, the cross-sectional area $A$ must be large enough to support the tension $F$ acting on it. If the ribbon material has a tensile strength $\tau$ and we apply a safety factor $f$, the required area at a point where tension is $F + \Delta F$ is:

(8)    \begin{equation*} A = \frac{(F + \Delta F) f}{\tau} \end{equation*}

Combining this with the integrated force expression, we can write the ratio of the tension change to the total tension at any point:

(9)    \begin{equation*} \frac{\Delta F}{F + \Delta F} = \frac{\rho f}{\tau} \left(\frac{\mu_L}{x_0 - \mu^*} - \frac{\mu_L}{x_1 - \mu^*} + \frac{\mu_E}{x_0 + \mu} - \frac{\mu_E}{x_1 + \mu} + \frac{\omega^2}{2}(x_0^2 - x_1^2)\right) \end{equation*}

Rearranging to isolate the material properties on the left:

(10)    \begin{equation*} \frac{\tau}{\rho f \left(\dfrac{F}{\Delta F} + 1\right)} = \left(\frac{\mu_L}{x_0 - \mu^*} - \frac{\mu_L}{x_1 - \mu^*}\right) + \left(\frac{\mu_E}{x_0 + \mu} - \frac{\mu_E}{x_1 + \mu}\right) + \frac{\omega^2}{2}(x_0^2 - x_1^2) \end{equation*}

The left-hand side is determined entirely by the ribbon material — its tensile strength $\tau$, density $\rho$, safety factor $f$, and the local tension ratio. The right-hand side is determined entirely by the geometry and the gravitational/rotational parameters of the Earth-Moon system. This clean separation between material properties and orbital mechanics is what makes the equation so useful for design: given a material, you can immediately calculate what taper profile is required, and given a desired taper, you can determine what material performance is needed.

The Lunar-Gravity Approximation

For a first-pass design, if the elevator spans only the region close to the Moon (well inside the Earth-Moon distance), we can simplify by assuming lunar gravity alone. In this case, the Earth’s gravitational term and the centrifugal term are small compared to the Moon’s gravity near the surface, and the acceleration reduces to:

     \begin{displaymath} a(x) \approx \frac{\mu_L}{(x - \mu^*)^2} \end{displaymath}

Under this approximation, we define a characteristic length $L$ related to the material’s breaking length:

     \begin{displaymath} L \equiv \frac{\tau}{\rho g_L f} \end{displaymath}

where $g_L$ is the lunar surface gravitational acceleration. This is essentially the breaking height — the maximum length of a uniform cable of the material that could support its own weight in a uniform $g_L$ field. One important check: $L$ must always be greater than $r_0$, the lunar radius, for the material to be capable of supporting even the lower portion of the elevator. Materials that fail this check — those with breaking heights shorter than the Moon’s radius of 1,737 km — cannot be used for a lunar elevator under any circumstances. Fortunately, all the candidate materials in the table from the previous post satisfy this condition comfortably.

For M5 fiber with its breaking height of 342–570 km (depending on whether you use the current or planned stress limit), $L$ is well above the lunar radius, and the taper ratio across the full elevator length works out to approximately 2.7–4.0. For T1000G carbon fiber with a breaking height of 361 km, the result is similar. These are the modest taper ratios that make the lunar elevator buildable with today’s materials — in stark contrast to the Earth elevator’s requirement for a taper ratio of roughly 6,000.

What the Equations Tell Us

A few insights emerge directly from the structure of these equations that are worth making explicit.

First, the taper is exponential. The ribbon cross-section doesn’t decrease linearly from EML2 to the surface — it decreases as an exponential function of the integrated gravitational potential difference. This means that the ribbon is relatively thick for a long stretch near EML2, and thins rapidly near the surface. The “waist” of the ribbon is at the lunar surface, where tension is lowest. If the elevator is going to fail, it will fail there first.

Second, the full three-body force field matters for accurate design. The simplified lunar-gravity approximation gives you the right order of magnitude, but the Earth’s gravity and the centrifugal term are not entirely negligible, especially in the upper portion of the elevator near EML2. A real design will integrate the full expression in the equation above, numerically if necessary.

Third, and most importantly, the right-hand side of the taper equation depends only on positions and physical constants. The material choice scales the left-hand side. This means that for any candidate material, you can immediately calculate whether it produces an acceptable taper ratio for a given elevator configuration — no iteration required. The design space is well-defined and directly computable.

The ribbon designed by these equations is not a speculative structure awaiting a materials breakthrough. The numbers close today, with materials you can order from a catalog. That is not true of any proposed Earth space elevator. It is true of the lunar version — and it has been true since Pearson first worked through this analysis in the 1970s.

In the next post, we’ll examine these equations implemented in actual computer code.

Posted in Lunar Commerce, Lunar Exploration and Development, Space Development, Space Tethers, Space Transportation | 3 Comments

Revisiting LUNOX and an ISRU critique

There’s a particular NASA mission concept from 1993 that deserves more attention than it gets, and a 2007 critique of lunar in-situ resource utilization that deserves to be read alongside it. Taken together, they map out why lunar ISRU has spent thirty years stuck in an architectural cul-de-sac — and, more usefully, they point toward the way out.

The Joosten/Guerra LUNOX Architecture

In 1993, Kent Joosten and Lisa Guerra at NASA/Johnson Space Center proposed a lunar outpost mission architecture called LUNOX.[1] It was a serious piece of work, developed in the wake of Mike Griffin’s First Lunar Outpost (FLO) study that had concluded in 1992 with a price tag so eye-watering it had effectively killed the program. LUNOX was a maverick attempt to rescue the idea of a return to the Moon by fundamentally rethinking the propellant mass equation.

The central insight was simple and obvious. A lunar lander that has to bring its return propellant from Earth is carrying enormous amounts of dead mass through two full gravity wells. Oxygen is the dominant component of chemical propellant mass. The Moon has oxygen bound to metals in regolith. If you can break those strong chemical bonds between oxygen and metals in the regolith, and liberate, purify, and liquefy the oxygen, you can shrink the lander’s size dramatically. That further shrinks the launch vehicle that sends it, and collapses the program cost.

Joosten’s numbers made the case. His “Phoenix” manned lander massed just 33,684 kg after translunar injection, compared to the 95,000 kg of FLO’s corresponding vehicle. The ascent propellant was 10,165 kg of lunar-produced liquid oxygen; only 2,492 kg of liquid hydrogen needed to come from Earth. A Shuttle-derived heavy-lift launcher (essentially the Shuttle-C design) could handle the job. Total program cost was estimated at $19.6 billion in FY1993 dollars for a first crewed landing in 2005.

The surface infrastructure was elegant. The first cargo flight delivered a 7,269 kg LUNOX plant and a 5,110 kg nuclear reactor in the 40–60 kWe class. The second flight brought a fleet of small robotic vehicles: two “Loader” bulldozers that collected 500 kg/hour of ilmenite-rich regolith, two “Tanker” rovers that moved the produced liquid oxygen, and two “Hauler” rovers for heavy equipment. The chemical process was hydrogen reduction of ilmenite in a fluidized-bed reactor, followed by solid-state high-temperature electrolysis of the resulting water, with Stirling-cycle liquefaction for storage. Annual production capability was 24,000 kg of LOX at roughly 4% extraction efficiency after beneficiation.

LUNOX was to be international. Russian Energia boosters would launch all the unmanned cargo, the Americans would develop the crew hardware and launch the crewed missions on Shuttle-derived vehicles, and the payloads would be cross-compatible so either partner could carry any element if the other pulled out. It was a plausible, well-engineered architecture.

It went nowhere. The International Space Station absorbed the agency’s human spaceflight bandwidth, Mars Direct absorbed its long-term exploration imagination, and LUNOX was filed away. When the U.S. returned seriously to lunar planning a decade later, under Constellation, ISRU had been re-scoped as a second-order problem to be solved after the basic architecture was in place.

Rapp’s Critique of ISRU

In 2007, Don Rapp — a former senior research scientist and division technologist at JPL who had managed Mars in-situ propellant production research there — published a two-part essay in The Space Review titled “The problems with lunar ISRU.”[2] The second part, in particular, is a clinically devastating cost-benefit analysis of ISRU as it was being planned within the Constellation/ESAS architecture.

Rapp’s argument ran as follows. In the ESAS architecture, ISRU would save approximately 4 metric tons of ascent oxygen propellant per crewed mission, twice per year — 8 MT/year total. With a LEO-to-lunar-surface “gear ratio” of about 4:1, that translates to 32 MT/year of mass savings in low Earth orbit, or roughly one avoided cargo delivery every four years at $1.2 billion per cargo mission. Net savings: about $300 million per year.

The investment required to realize those savings, by Rapp’s accounting, was staggering. Prospecting campaigns to locate polar ice (the assumed feedstock): ~$5 billion across LRO, multiple long-distance rovers, and a ground-truth mission. Technology development for excavation, processing, and autonomous operations: ~$6 billion, including a nuclear reactor required only because the candidate sites were in permanent darkness at the poles. In-situ test and validation of one-tenth-scale and full-scale demonstration systems: ~$8 billion. Total: ~$19 billion.

Rapp’s conclusion was direct: saving $300 million per year against a $19 billion investment required more than sixty years to break even, and that was before discounting for the time value of money. For any reasonable financial framing, ISRU in the ESAS architecture simply did not pay back.

The critique cut deeper than the numbers, though. Rapp’s real point was structural. ISRU in the Constellation architecture was an add-on, not a foundation. The lunar sorties had to be fully capable of landing, ascending, and returning without ISRU, because the architecture couldn’t be allowed to depend on a not-yet-validated surface plant. That independence requirement ate all the leverage. The ascent propellant was only 4 MT — a modest fraction of total mission mass. The descent propellant, at 20–25 MT, was the real prize, and the ESAS architecture had no path to capturing it. ISRU was being evaluated as a marginal optimization on a system designed not to need it, and when evaluated that way, it failed the cost-benefit test.

Rapp ended with five conditions under which lunar ISRU could justify itself. ISRU must be built into the fabric of the campaign from the start. An extended robotic precursor phase must establish the plant before crewed missions arrive. Polar ice must be the feedstock (his view, given the architectures under discussion). Oxygen must be retained as ascent propellant, ideally with hydrogen as well. And ISRU must address descent propellants, not just ascent.

The Architectural Lesson

Read together, LUNOX and Rapp’s critique tell a coherent story. LUNOX was architecturally correct in 1993: ISRU was designed into the mission from the start, every mass budget assumed lunar-produced oxygen, and the lander simply could not close its mass equation without the LUNOX plant. Rapp’s five conditions are, almost point for point, a description of what LUNOX already was. The mission designers of 1993 understood what the mission designers of 2007 had forgotten.

LUNOX imagined using hydrogen as the way to reduce a particular oxide, ilmenite, and it might have done better. Hydrogen reduction of ilmenite at 4% extraction efficiency meant 25 tons of regolith had to be mined, beneficiated, heated, and processed for every ton of oxygen produced. That’s a staggering materials-handling burden that drives plant mass up, reactor power requirements up, and robotic-vehicle complexity up. The LUNOX plant itself massed 7.3 tons precisely because it had to move that much mass to produce a useful oxygen stream. Hydrogen reduction of ilmenite also recovers, at best, only one-third of the oxygen even in the ilmenite itself — and ilmenite is a minor phase in most of the lunar surface. The process is feedstock-limited to mare basalts, specifically the ilmenite-rich ones, which constrains site selection and demands significant upstream beneficiation before processing.

Fluorination followed by electrical reduction is another chemistry that gets all of the oxygen out of the regolith at reasonable temperatures, produces silicon and aluminum as byproducts rather than discarding a slag, and works on any silicate phase the Moon has to offer. Fluorination as a strategy was sitting in the open literature when Joosten was doing his LUNOX study.

Why Fluorine Works on Lunar Rock

The foundational argument for fluorination of lunar materials is not just that fluorine is the most reactive element, though it is. The deeper argument is an acid-base argument, and it was laid out in its cleanest form by Donald Burt of Arizona State University in an abstract presented at the 19th Lunar and Planetary Science Conference in 1988.[3] Burt developed the idea more fully in a 1992 conference paper,[4] and Seboldt and colleagues at the German Aerospace Research Establishment and the University of Bonn provided experimental validation the following year.[5]

The chemistry works as an exchange reaction. For any metal oxide MO, the reaction with fluorine runs

     \begin{displaymath} 2\text{MO} + 2\text{F}_2 \rightarrow 2\text{MF}_2 + \text{O}_2 \end{displaymath}

Two fluorines go in for every oxygen that comes out. Burt, drawing on his earlier work in petrological acid-base theory, treated the combination “$\text{F}_2\text{O}_{-1}$” as an exchange operator with the properties of a Lewis acid — effectively, the anhydride of HF. The question of whether a given mineral will fluorinate readily then reduces to a question of how basic its constituent oxides are. The more basic the oxide, the more favorably it exchanges two fluorines for an oxygen.

The striking result is that the affinity sequence for $\text{F}_2\text{O}_{-1}$ exchange among common lunar elements is periodic: K > Na > Li > Ca > Mg > Be, and so on, tracking the acid-base character of the oxides themselves. Compare this to the affinity sequences for oxygen alone or fluorine alone, which are irregular and don’t follow obvious periodic patterns. The fluorine-oxygen exchange reaction, uniquely, tracks the chemistry most directly.

This matters because lunar minerals are basic. The dominant phases — anorthite with its CaO and Al2O3, olivine and pyroxene with their MgO and FeO — are built from basic oxides. Silica is the most acidic oxide in the lunar assemblage, and even it fluorinates readily because the SiF4 product is volatile and continuously leaves the reaction site, exposing fresh surface. The Moon’s mineralogy is, from a fluorination standpoint, about as favorable a feedstock as you could ask for. The same cannot be said for terrestrial crustal rocks, which are much more silica-rich and therefore more resistant to fluorine attack.

Seboldt’s experimental work at Bonn demonstrated this directly. Four lunar soil simulants — two highland-type, two mare-type — were fluorinated at temperatures between 623K and 923K. At 720K (roughly 450C, a temperature that’s essentially trivial to reach), approximately 80% of the oxygen was extracted from any of the four compositions. Above 800K, olivine-free highland simulants gave near-total oxygen release. Framework silicates like anorthite and chain silicates like pyroxene decomposed easily; olivine was the laggard, because its reaction products form solid passivating coatings rather than volatile SiF4 that clears the surface. For highland sites where olivine is essentially absent, this is a non-issue.

What Fluorination for LUNOX Would Have Looked Like

A LUNOX architecture built around fluorination of highland anorthite rather than hydrogen reduction of mare ilmenite would have had dramatically different infrastructure requirements. The 4% extraction efficiency becomes 80%. The 25 tons of regolith handled per ton of oxygen becomes 2.8 tons. The plant mass shrinks, the reactor shrinks, the robotic excavation fleet shrinks. The feedstock is no longer mare ilmenite but the anorthositic highlands — which cover the majority of the lunar surface and are accessible from most landing sites. Silicon for solar cells and aluminum for structure come out as byproducts of the same process.

The fluorine itself, which must be imported from Earth, is imported as a stable salt rather than as the reactive gas. Burt’s 1988 abstract proposed NaF as the transport form, with sodium reduction of the intermediate fluorides recovering metallic Al and Si, and Na2O/CaF2 exchange producing CaO and closing the fluorine loop back to NaF for electrolysis. In the same abstract, Burt noted an attractive alternative: LiF in place of NaF. Lithium is nearly as strong a reducing agent as calcium and markedly stronger than sodium, LiF melts at a lower temperature than NaF (advantage for electrolysis), and LiF is 38% lighter than NaF on a per-fluorine basis — so 38% less Earth-launched mass delivers the same fluorine inventory to the Moon. The LiF route also reduces magnesium from its fluorides, which opens olivine and pyroxene as feedstocks and makes mare regolith as workable as highland anorthite. It’s a pathway with genuinely distinct virtues, and the choice between Na and Li routes is one of the real engineering trades left open by the existing literature.

The remaining unsolved problem in Burt’s scheme was the electrolysis of the molten fluoride salt to regenerate F2 at an inert anode. Fluorine is aggressive enough to attack nearly any conventional electrode material, including platinum. Burt proposed lanthanide-doped CaF2 as a solid-state conductor with the right electronic properties, citing contemporary work on defects in solid fluorides. That specific materials-science path has not yet been demonstrated at production scale, though the intervening thirty-eight years have produced a large body of rare-earth molten fluoride electrolysis knowledge that has moved the adjacent problems considerably forward. The Seboldt group proposed an alternative: recycle fluorine via HF rather than via NaF, using mature industrial HF electrolysis as the electrochemical step and atomic hydrogen reduction of the mixed fluorides as the recycling chemistry. Either path closes the loop; the second uses entirely proven industrial technology.

Applying Rapp to the Present Day

The deeper reason to revisit both papers now is that the current Artemis architecture is repeating Constellation’s structural mistakes almost verbatim. ISRU is again being treated as a second-order add-on. The Human Landing System program has no architectural dependency on lunar-produced propellant. The mission-critical systems are being designed to close without ISRU, which means ISRU — when it arrives, if it arrives — will again be evaluated as a marginal optimization on a system that doesn’t need it. Rapp’s critique will apply to Artemis ISRU with exactly the same force it applied to Constellation ISRU, and the conclusion will again be that the numbers don’t close.

The way out is the same way out LUNOX found in 1993: design the architecture around ISRU from the start, accept an extended robotic precursor phase, and choose a feedstock that doesn’t require $5 billion of prospecting to locate. Highland anorthite meets that last test trivially. It’s everywhere, it’s well-characterized from Apollo, and we’ve known its composition since 1971. The prospecting phase that Rapp costed at $5 billion is, for an anorthite-feedstock architecture, a few lines in a site-selection trade study.

Fluorination also addresses Rapp’s fifth condition — capturing the descent propellant mass — in a way that no oxygen-only ISRU approach can. Fluorination of anorthite produces metallic aluminum as a coproduct of oxygen. Aluminum burns with liquid oxygen at a specific impulse of 270-280 seconds. It’s not the best propellant combination you could imagine, but it’s one where both components come from the same feedstock at the same plant. Once you can produce both Al and LOX on the Moon, you’re no longer limited to saving ascent mass. You can top off descent propellants from local production too — not on the first mission, but on missions after the plant has run long enough to build up inventory. That’s the architectural unlock Rapp was looking for and that the water-from-polar-ice approach cannot provide, because polar ice gives you only hydrogen and oxygen.

The nuclear power question, which Rapp called out as potentially a show-stopper, also looks different in an anorthite-fluorination architecture. You are no longer forced to operate in the permanent darkness of polar cold-traps to reach your feedstock. A surface reactor at a mid-latitude anorthositic site can run continuously on a predictable day-night cycle with buffer storage, and the reactor itself can be a technology that has an independent terrestrial market rather than an exploration-only development program. A liquid-fluoride-salt reactor has direct chemistry overlap with the fluorination plant it’s powering — the same containment alloys, the same fluoride-salt handling expertise, the same electrochemical toolkit. The reactor and the ISRU plant stop being two separate expensive development programs and start being two applications of one technology base.

The Thirty-Year Lesson

The LUNOX study is thirty-three years old. Rapp’s critique is nineteen years old. The fluorination chemistry they could have used is thirty-eight years old in its foundational form and thirty-three years old in its experimental validation. None of what I’ve described here requires inventing anything new. It requires reading papers that have been in the open literature for a generation, applying a cost-benefit framework that Rapp laid out two decades ago, and noticing that the chemistry trade and the architecture trade point the same direction.

Joosten was right about the architecture and might have picked a better chemistry. Rapp was right about the economics of ISRU-as-afterthought. Burt and Seboldt were right about fluorine as the universal oxidant and electricity as the universal reductant. Putting the three together — LUNOX’s mission architecture, Rapp’s discipline about economic closure, and the fluorination chemistry approach that makes the numbers actually work — gives you a blueprint for lunar ISRU that has a shot at paying back its investment. It’s worth thinking seriously about it.

References

  1. Joosten, B. K., and Guerra, L. A. (1993). “Early Lunar Resource Utilization: A Key to Human Exploration.” AIAA 1993-4784.
  2. Rapp, D. (2007). “The problems with lunar ISRU.The Space Review, two-part essay.
  3. Burt, D. M. (1988). “Lunar Production of Oxygen and Metals Using Fluorine: Concepts Involving Fluorite, Lithium, and Acid-Base Theory.Lunar and Planetary Science XIX, pp. 150–151.
  4. Burt, D. M. (1992). “Lunar Mining of Oxygen Using Fluorine.The Second Conference on Lunar Bases and Space Activities of the 21st Century, NASA CP-3166, Vol. 2, pp. 423–428.
  5. Seboldt, W., Lingner, S., Hoernes, S., Grimmeisen, W., Lekies, R., Herkelmann, R., and Burt, D. M. (1993). “Lunar Oxygen Extraction Using Fluorine.” In Resources of Near-Earth Space, pp. 129–147.
Posted in ESAS, Lunar Commerce, Lunar Exploration and Development, Space Transportation | 5 Comments