Week in Space Data, every Friday.
By the SpaceNexus Desk
AI-drafted analysis, fact-checked before it publishes
Drafted by AI, fact-checked before publishing, corrected in public. How the desk works
On October 22, 2026, Ars Technica published a report titled "Latest estimate for Starship launches required to support a Moon landing? 22." The article opens by noting that NASA guards the number of Starship launches needed for an Artemis landing as if it were a state secret. The piece carries a quoted warning that observers "need to keep our eyes on numerous required fuelings for the lander."
The available excerpt is short, so this analysis relies on the headline figure and on the architectural logic of the program, not on a detailed breakdown from the article. The 22 figure should be treated as a reported estimate, not an official NASA baseline. The sources do not tell us how the number divides between tanker flights, propellant depot flights and the lander itself, or what assumptions about transfer efficiency and boil-off sit behind it.
The Starship Human Landing System is a very large vehicle that must depart low Earth orbit with enough propellant to reach lunar orbit, descend and, in the Artemis design, return to a rendezvous point. Starship itself reaches orbit with its tanks mostly empty after ascent. Filling it requires multiple tanker Starships launching to the same orbit and transferring cryogenic propellant, which is a capability that has to be demonstrated at scale. Every additional tanker flight adds a launch, a transfer operation and a chance of failure, and the whole chain must complete within the boil-off window of the cryogenic propellants.
Sources:
About this analysis
Written by the SpaceNexus Desk: a language model drafts each piece from the sources listed above, a second model pass fact-checks it against those sources, and drafts that fail that check are held for a person. No human typed this article. How the desk works · Report a correction
For information only, not investment advice. SpaceNexus is not a registered investment adviser, broker or dealer, and nothing here is a recommendation to buy, sell or hold any security. Data may be delayed, estimated or incomplete; check the source before acting. Full disclaimer
Week in Space Data every Friday: the week in numbers, our own analysis clearly labelled, the chart of the week and next week’s launches. Add SpaceNexus AM for a short brief on weekday mornings.
Week in Space Data on Fridays, SpaceNexus AM on weekday mornings if you tick it. Unsubscribe anytime.
This analysis does not revisit the double-catch or Starbase environmental stories. It concentrates on the new element: a reported launch-count estimate and its architectural meaning.
A lunar landing that needs 22 launches is a cadence problem. If a Starship turnaround takes weeks, the tanker campaign takes months. If turnaround takes days, the campaign compresses. NASA's lunar landing date depends less on whether the lander design works in isolation and more on whether the full chain, including ascent, orbital rendezvous, propellant transfer and reuse, runs reliably at a rate no program has previously attempted. The figure makes the dependency visible.
The Ars piece highlights that the agency treats the number as sensitive. For a program funded by public money and tied to national prestige, the count of required flights is a basic planning parameter. Congress, the Government Accountability Office and the NASA Inspector General have all previously scrutinized Artemis cost and schedule assumptions. A publicly stated estimate invites sharper oversight questions, such as what failure rate was assumed, what margin exists and what happens to the landing date if one tanker flight is lost.
Cryogenic propellant transfer in orbit at this scale has not yet been demonstrated end to end in a way that supports a crewed mission. The quote about "numerous required fuelings" points to this as the critical path item. Technical risks include boil-off during the loiter period, slosh and settling in microgravity, docking or mating reliability between large vehicles, and thermal management. We do not have in the sources any new test results, so we flag these as the known risk categories, not new findings.
A 22-launch campaign per landing multiplies range demand. The Space Force's range modernization roadmap, the FAA's Starbase review and Blue Origin's New Glenn cadence proposal all intersect here. Pads at Starbase and in Florida need to support high flight rates, and the regulatory frameworks for environmental review, airspace integration and public safety need to scale with them. The Part 450 licensing changes under consideration are part of the same story. Any cadence limit imposed on a pad directly lengthens the tanker campaign.
Blue Origin, which is building its own lunar lander and a satellite factory in Texas, has an architecture with different launch and refueling requirements. A published high launch count for Starship strengthens the case that NASA benefits from at least two lander approaches with different risk profiles. It also raises the question of how much weight the agency will give to launch-count efficiency when evaluating schedule risk across providers. We have no information in the sources that NASA has changed its competitive posture.
The National Academies recommendation for four nonpolar sites sits in tension with a landing architecture that is costly in launches. If each landing demands a campaign of this size, the number of distinct sites a program can afford to visit is limited. The report itself describes short crewed missions, so the question is whether the logistics of a reusable heavy lander make such missions practical at scale. This is an inference from the combined facts and not a statement from either source.
The Space Force intends to field cislunar capabilities by the end of fiscal 2029, per a Breaking Defense report. A civil campaign of dozens of heavy launches and orbital transfers would create a visible logistics pattern and an enlarged set of assets to track and protect. The civil architecture and the defense interest in the cislunar domain are converging, and refueling operations in Earth orbit and beyond are likely to be of interest to space domain awareness planners.
Suppliers of cryogenic systems, thermal protection, docking hardware, propellant handling equipment and ground support gain demand from a high-cadence architecture. Conversely, any evidence that the launch count needs to go higher increases schedule and cost exposure for the whole chain. The sources do not provide supplier data, so these are directional observations.
If transfer and reuse perform well, the 22-launch figure could shrink as tanker capacity per flight improves, and the number becomes a historical footnote. If they perform poorly, the figure could grow, and NASA would face a choice between schedule slips, architectural changes or a larger role for alternative landers. A middle outcome is also plausible, where the count stays near 22 but cadence rises enough to make the campaign tolerable. The sources do not allow us to assign probabilities, and we avoid doing so.