Orbit Control, Δv Budget & Propellant Sizing

Δv Is a Mission Budget

The propulsion budget should include all manoeuvres expected across the mission plus uncertainty/reserve: orbit correction, drag make-up, inclination/RAAN control where applicable, formation maintenance, collision avoidance, momentum unloading, disposal and launch injection correction. Statistical launch/orbit dispersions should not be mixed casually with deterministic manoeuvres; the allocation and confidence basis should be explicit.

sat-delta-v-budget

Rocket Equation

Ideal rocket equation:
Δv = I_sp g₀ ln(m₀ / m_f)

Rearranged propellant fraction:
m_p / m₀ = 1 - exp[-Δv / (I_sp g₀)]

where:
I_sp = specific impulse
g₀   = standard gravity
m₀   = initial mass before burn
m_f  = final mass after burn

Finite burn, pointing error, minimum impulse bit and residual propellant may add further losses/allowances.

Propellant Budget Must Include Unusable Quantity

Not all loaded propellant can be guaranteed usable. Residuals, trapped volume, gauging uncertainty, thermal density variation and feed-system limitations can require explicit allocation. Pressurant mass and tank/valve/line mass also scale with the propulsion architecture. For electric propulsion, propellant mass may be small while power-system mass and manoeuvre duration become dominant.

Tank Location Changes Dynamics

As propellant is consumed, centre of mass and inertia can change. Slosh can couple with control/structure in larger tanks. Thruster placement should limit parasitic torque and plume impingement while preserving control authority across mass-property states. The Δv budget therefore connects directly to AOCS and structural configuration.

End-of-Life Must Be Designed Early

Disposal/deorbit capability consumes propulsion, power and operations resources. Current debris-mitigation requirements are mission/orbit/jurisdiction specific and should be flowed into mission requirements at concept stage rather than left as residual propellant if available.

Verification

• Independent manoeuvre budget and orbit-propagation check.
• Thruster performance over pressure/temperature/ageing range.
• Minimum impulse bit and pointing-loss effect for small manoeuvres.
• Propellant loading, gauging and residual assumptions.
• End-of-life/disposal margin protected through mission operations.

Design Inputs, Assumptions & Requirement Control

For Orbit Control, Δv Budget & Propellant Sizing, the analysis should begin with a controlled set of inputs rather than a geometry-first model. The key inputs include required thrust or wheel force, torque-speed envelope, mission/drive-cycle duty, efficiency maps, thermal limits, gear ratio, electrical supply, inertia, mounting stiffness and transient/fault loads. Each value should carry a source, units, reference condition, uncertainty and revision status. Requirements, measured data, supplier limits and engineering assumptions should remain distinguishable because they have different levels of authority. In a Satellites & Space Systems programme the disciplines evolve in parallel, so an assumption that is acceptable during concept selection can become non-conservative after mass, stiffness, software or operating conditions change. A useful design record therefore captures the baseline, the reason for every important simplification and the sensitivity of the conclusion to uncertain inputs. This prevents an early placeholder from becoming an invisible design requirement later in the programme.

Engineering Analysis & Design Workflow

A strong workflow for this topic is based on performance matching across the complete duty cycle, loss/thermal modelling and torsional or structural analysis of shafts, mounts, gears and interfaces rather than rating components from one peak number. Start with the simplest model that exposes the governing physics and use it to identify dominant parameters, limits and trade directions. Increase fidelity only when the additional detail can change a requirement, load, margin or architecture decision. At every level, preserve equilibrium, energy/power balance and interface consistency so the higher-fidelity model can be checked against an independent lower-order result. The output should not be a single number: useful engineering evidence includes trends, sensitivity, governing cases and the mechanism that creates the limit. This is especially important when optimisation is involved, because a numerical optimum at one assumed condition may disappear once uncertainty, manufacturing tolerance or another subsystem is included.

Governing Failure Modes, Limits & Sensitivities

The credible limits for Orbit Control, Δv Budget & Propellant Sizing include thermal derating, overspeed, torque transients, gear/bearing fatigue, shaft or mount overload, propulsive efficiency shortfall, cavitation/flow or plume/integration effects where applicable and control/protection trips. These mechanisms should be listed before detailed analysis so that the model is built to calculate the quantities that actually govern acceptance. Sensitivity should focus on parameters that can switch the governing mode: stiffness, damping, friction, preload, material modulus, temperature, timing, aerodynamic condition, battery state, tyre condition or manufacturing tolerance as relevant. If a small plausible change causes a large movement in margin, the engineering response should normally be to improve the evidence or make the design more robust rather than simply report the nominal result with greater numerical precision. Failure-mode thinking also helps distinguish a real design reserve from apparent margin created by a modelling assumption.

Modelling, FEA & Computational Fidelity

The numerical strategy should reflect the physics of the problem. For this topic, the natural starting point is performance matching across the complete duty cycle, loss/thermal modelling and torsional or structural analysis of shafts, mounts, gears and interfaces rather than rating components from one peak number. Where structural FEA is required, boundary conditions should preserve the real interface stiffness and load path, and mesh convergence should be assessed on the response used for the decision rather than on contour smoothness. Where controls, aerodynamics, thermal behaviour, electrical networks or multibody dynamics dominate, the corresponding system model should remain the master source of loads and states; detailed FEA should not invent a disconnected design condition. Submodelling is often preferable to making a complete vehicle, aircraft or spacecraft model excessively detailed. The objective is a hierarchy of models whose assumptions are visible and whose results can be cross-checked, not a single opaque model that is difficult to verify.

Interfaces & System-Level Consequences

This subject cannot be closed independently from the rest of the system. The most important interfaces include mass and inertia, power, thermal conductance, data rate, alignment, structural stiffness, launch loads and operational mode transitions. A design change should therefore be propagated through the adjacent budgets and models before it is accepted. For example, a stiffness increase can add mass and shift a mode; a larger actuator can increase power and thermal demand; a more conservative protective structure can alter packaging and centre of gravity; and a software change can alter the loads used for mechanical sizing. Interface reviews are most effective when they exchange quantitative quantities—forces, moments, stiffness, voltage, current, heat, latency, geometry and tolerances—rather than general statements of compatibility. Many expensive late changes are the result of locally valid designs whose interface assumptions were never reconciled.

Verification, Test Correlation & Model Updating

Confidence should be built through dynamometer or thrust-stand testing, efficiency mapping, thermal soak, transient torque/thrust events, endurance testing and installation-level correlation with the released control system. Test and analysis need to compare equivalent quantities: the same coordinate system, operating condition, filtering, configuration and measurement location. A strain gauge should be compared with strain in its actual direction; a thermal measurement should use the same heat input and ambient state; a dynamic response needs compatible bandwidth and boundary conditions. When disagreement appears, the first task is to identify whether the source is load, stiffness, damping, material data, sensor error, software logic or boundary condition. Model parameters should be updated only when a physical reason exists. Correlation is strongest when one justified model change improves several independent observations rather than forcing one trace to match.

Standards, Evidence & Configuration Traceability

The governing evidence for this topic should remain linked to the mission-assurance plan, applicable ECSS, NASA, customer and launch-provider requirements, interface-control documents and controlled parts/material/process requirements. Those documents define the project-specific context; this article should not be read as prescribing universal factors, margins or pass/fail values. The analysis record should identify the model revision, software version, material or supplier data, load-case source, safety/design factors, configuration and acceptance criterion used. Where requirements evolve, the impact on previous evidence should be assessed explicitly rather than assuming the old result remains valid. This traceability is particularly important when test, analysis and supplier evidence are combined, because all three can be individually correct yet refer to subtly different configurations. A reviewer should be able to move from requirement to input to model to result to verification evidence without reconstructing the engineering history from memory.

Engineering Judgement & Common Traps

The central judgement for Orbit Control, Δv Budget & Propellant Sizing is that the correct propulsion system is the one that delivers the required integrated mission or lap performance with thermal and durability margin; catalogue peak power is rarely the governing design quantity. Common traps include accepting a positive margin without confirming that the governing physical mode is represented, using independently enveloped loads that cannot occur simultaneously, applying supplier catalogue limits as exact boundary conditions, or increasing model fidelity before uncertainty in the inputs has been reduced. Another recurring problem is optimising a subsystem after its neighbours have effectively frozen the interfaces; this can produce impressive local results with little system value. A good technical review should ask three questions: what assumption could reverse the conclusion, what measurement would most reduce the remaining uncertainty, and whether the recommended change still makes sense when viewed across payload, structure, thermal control, electrical power, AOCS, propulsion, communications, avionics, mechanisms and launch-vehicle interfaces.