Designing the Delta-V Ledger

Abstract

A destination name does not define a mission. The useful engineering object is a time-ordered trajectory with initial conditions, force models, maneuvers, dispersions, constraints, navigation updates, reserves, and recoverable off-nominal states. I construct a delta-v ledger that links orbital mechanics to vehicle mass and operational risk. The ledger distinguishes ideal maneuver requirements from gravity loss, steering loss, finite-burn effects, station keeping, collision avoidance, navigation cleanup, disposal, and contingency reserve. It also records time, eclipse, communication geometry, radiation exposure, and abort access because a lower delta-v path can still be a worse human mission. I use simple analytical relationships for first estimates, then define the numerical evidence required before design closure. The objective is to prevent a clean trajectory diagram from hiding the real obligations placed on propulsion, guidance, thermal control, and crew survival.

Begin with a state, not a picture

An arrow from Earth to the Moon is a story. A trajectory begins with position, velocity, time, mass, coordinate frame, and uncertainty. It ends with another state that a following system can accept. If two analysts use different parking-orbit altitudes, lunar ephemerides, departure dates, or definitions of arrival, their delta-v values can differ while both calculations remain internally correct.

I require every reference trajectory to publish:

• epoch and time standard;
• coordinate frames and planetary ephemeris;
• initial orbit and state covariance;
• force model and propagated bodies;
• maneuver location, duration, direction, and control law;
• target conditions and tolerances;
• correction and reserve policy;
• eclipse, communication, radiation, and thermal events;
• alternate, abort, and disposal states.

NASA’s General Mission Analysis Tool exists precisely because multi-phase missions require numerical propagation and optimization beyond hand sketches. Analytical estimates remain valuable. They reveal scaling and catch impossible outputs. They should bracket a numerical solution, not masquerade as final flight design.

The ledger contains more than ideal maneuvers

For a two-body impulsive transfer between coplanar circular orbits, the vis-viva equation provides speed at radius $r$:

$$v=\sqrt{\mu\left(\frac{2}{r}-\frac{1}{a}\right)},$$

where $\mu$ is the central body’s gravitational parameter and $a$ is semimajor axis. Differences between the transfer-orbit and circular-orbit velocities give an ideal Hohmann estimate.

That estimate excludes the conditions under which hardware actually flies. I build the mission ledger in layers.

Layer	Included demand	Why it cannot remain hidden
Ideal geometry	Departure, capture, landing, ascent, and return	Establishes the physical lower bound
Execution	Finite burn, gravity, steering, throttling, and residuals	Couples maneuver to engine and vehicle design
Navigation	Statistical correction, state error, and dispersions	Connects sensors and tracking to propellant
Operations	Rendezvous, station keeping, avoidance, and relocation	Accumulates across service life
End state	Passivation, disposal, or graveyard transfer	Prevents the mission from exporting risk
Contingency	Engine out, missed burn, wave-off, and rescue	Preserves credible failure response

The final reserve should not be a percentage copied from another mission. It should be traceable to uncertainties and failure policies. A vehicle with precise navigation and redundant restart may justify a different reserve from a single-burn stage with broad injection dispersion.

GeometryNominal state history

Defines where and when the vehicle must be throughout the mission.

ExecutionReal propulsion demand

Adds finite burns, losses, corrections, and operating maneuvers.

ExposureTime-dependent environments

Tracks eclipse, radiation, thermal attitude, and communication.

RecoveryReachable safe states

Maps abort, loiter, rescue, disposal, and missed-event options.

Delta-v becomes mass through the vehicle

The ideal rocket equation converts maneuver demand into mass ratio:

$$\frac{m_0}{m_f}=\exp\left(\frac{\Delta v}{I_{sp}g_0}\right).$$

For $I_{sp}=450\ \mathrm{s}$, increasing a leg from $3.0$ to $3.3\ \mathrm{km/s}$ changes ideal mass ratio from approximately 1.97 to 2.11. A ten percent delta-v increase raises required initial mass by about seven percent for the same final mass in this example. When tanks and engines grow with propellant, the integrated penalty is larger.

Electric propulsion complicates the simple picture. High specific impulse reduces propellant, but thrust is low and power hardware carries mass. Burn duration changes the path, gravity losses, eclipse exposure, and arrival geometry. The ledger must therefore link thrust and power history to propagated state rather than entering one impulsive number.

I preserve mass at every interface:

$$m_{arrival}=m_{departure}-m_{propellant}-m_{consumables}-m_{discarded}.$$

The obvious equation is frequently violated by bookkeeping. Residual propellant may be unusable. Boiloff changes tank content. Payload adapters and transfer lines may remain with the wrong element. Crew consumables change center of mass. A versioned mass ledger prevents these terms from disappearing between subsystem models.

Time is another form of exposure

A minimum-energy trajectory can increase mission duration. That changes water, food, oxygen, carbon-dioxide removal, exercise, maintenance, radiation, thermal cycles, and probability of a component failure before arrival.

For each leg I record at least:

$$J = w_v\Delta v + w_t t + w_r D + w_c C_{cons} + w_a T_{abort},$$

where $D$ is radiation dose estimate, $C_{cons}$ is consumable demand, and $T_{abort}$ characterizes return or safe-haven access. The weights are decision values, not universal constants. Their purpose is to expose tradeoffs that a delta-v minimum alone cannot resolve.

A cargo tug may accept months of transit. A crew with a medical emergency may value hours. A cryogenic tanker may lose inventory during the same delay. A solar-electric stage may gain performance from proximity to the Sun and lose it as distance grows. Time belongs in every propulsion claim.

Windows create campaign behavior

Planetary trajectories are constrained by relative geometry. Mars opportunities recur on a cadence of roughly 26 months, but candidate opportunities differ in energy, arrival speed, entry conditions, conjunction duration, and abort access. A missed launch can delay a campaign far longer than a failed terrestrial shipment.

This means architecture cannot optimize flights independently. Cargo must arrive and commission before crew departure. Surface propellant production needs time and verified inventory. Return vehicles need compatible departure windows. A delayed payload can consume storage life or force another element to wait in orbit.

BoundAnalytical estimate PropagateNumerical reference DisperseMonte Carlo cases RecoverFault and abort states ReproduceIndependent solution

Abort paths belong in the nominal design

An abort is not one maneuver labeled on a slide. It is a changing set of reachable safe states. Early after departure, a free-return or powered Earth return may exist. Later, the crew may need to continue to a lunar flyby, dock with a safe haven, or commit to the destination. Propulsion failures, pressure loss, radiation events, and medical emergencies create different time limits.

I map the abort envelope continuously. At each mission time, the model asks which engines, propellant paths, navigation sensors, communication assets, and life-support reserves are needed to reach each safe state. Common-cause failures matter. Two engines fed by one damaged tank do not create two return paths.

The same discipline applies to uncrewed vehicles. A failed capture burn should not create an uncontrolled long-lived object in a valuable orbit. Disposal capability, tracking, and passivation are trajectory requirements from the start.

Publish enough for disagreement

The strongest trajectory result is not the most precise number. It is the one another analyst can reproduce and challenge. I want reference cases that include machine-readable states, models, assumptions, constraints, maneuver logs, and achieved tolerances. Independent tools should agree within declared bounds.

This practice creates a common foundation for the rest of the route. Propulsion can size to the same burns. Thermal analysis can use the same attitudes and eclipses. Radiation analysis can integrate the same time history. Communication can evaluate the same geometry. Habitation can load the same mission duration. When one assumption changes, the consequences propagate visibly.

The delta-v ledger is therefore not a table at the back of the study. It is the spine of evidence that keeps a destination, a vehicle, and a survivable operation attached to the same physics.