3.2.27 · D4Orbital Mechanics & Astrodynamics

Exercises — Pork chop plots — Δv vs launch - arrival date

3,570 words16 min readBack to topic

Level 1 — Recognition

L1.1 — Read the axes

On a pork chop plot, what physical quantity sits on the x-axis, what sits on the y-axis, and what do the closed contour "islands" represent?

Recall Solution
  • x-axis = launch date (departure from Earth).
  • y-axis = arrival date (at the target planet).
  • The islands are regions of low cost — the innermost contour is the ==minimum Δv (or minimum )== for that launch opportunity, the "sweet spot". There is nothing to compute here; the skill is knowing that each single cell is one Lambert problem and the whole picture is just its cost drawn over a grid. See Lambert's Problem.

L1.2 — from

A launch vehicle datasheet lists the trip as needing km/s. What is the ?

Recall Solution

— the definition, no gravity involved. Why square it? is energy per unit mass at infinity (, and ), and launch vehicles are rated by energy delivered, not speed.


Level 2 — Application

L2.1 — Departure Δv from a parking orbit

You must leave Earth with km/s from a circular parking orbit of radius km (a 300 km altitude orbit). Find the departure burn .

Recall Solution

Step A — circular speed (what you already have, and what means). Define == = the speed a spacecraft has while coasting on a circular orbit of radius == — the speed it is already moving at before any burn. Why does ? On a circle, gravity supplies exactly the centripetal force: gravitational pull must equal the centripetal requirement . Cancel and one power of : Numerically: Step B — perigee speed on the departure hyperbola (what you need). Why this formula? On the hyperbola the specific energy is , and energy is also . Setting them equal and solving: Step C — the burn (you only pay the difference between what you need and what you already have): See Hyperbolic Excess Velocity & C3 for why the term appears.

L2.2 — Mars capture Δv

On arrival at Mars the excess speed is km/s. You want to capture into a circular orbit of radius km ( km above Mars). Find .

Recall Solution

Same master formula, but with Mars' and km. The circular speed is the speed on the target circular orbit (same balance-of-forces derivation as L2.1, now with ): What it looks like: you arrive fast on a hyperbola passing Mars, and the burn at closest approach bends you down into a bound circle — that is the retro-burn cost.

L2.3 — Earth–Mars synodic period

Using d and d, find the synodic period and convert to years.

Recall Solution

Why this matters: cheap geometry (planets nicely spaced for a near-Hohmann shot) recurs every months, so pork chops arrive as a repeating family. See Synodic Period.


Level 3 — Analysis

L3.1 — Compare two cells

Cell A on the plot gives km/s; cell B gives km/s. Same parking orbit km. Compute each departure Δv and state which cell is cheaper and by how much.

Recall Solution

km/s (same for both). A is cheaper by km/s. Notice jumped from to (a energy rise) but Δv rose only — the term dilutes the difference. This is the Oberth-style leverage of doing the burn deep in the well; see Oberth Effect.

L3.2 — Payload cost of that 0.14 km/s

Using the Tsiolkovsky rocket equation with exhaust speed km/s, by what factor does the required mass ratio grow when Δv rises from to km/s?

Recall Solution

The mass ratio is . The factor between the two cases is A heavier stack for a Δv change that looked tiny — this is why mission designers chase the innermost contour. See Tsiolkovsky Rocket Equation.

L3.3 — Reading the ridge

Two candidate transfers have identical launch date but different arrival dates, one just below and one just above the diagonal ridge splitting the pork chop's two lobes. Explain physically why Δv spikes on that ridge, and which lobe is Type I vs Type II. Use the figure below to see the geometry.

Figure — Pork chop plots — Δv vs launch - arrival date
Recall Solution

First, define the transfer angle. Let == = the heliocentric angle swept between the two radius vectors==, i.e. the angle at the Sun between (Earth at launch) and (target at arrival). A short-way ("Type I") transfer has ; a long-way ("Type II") transfer has . The ridge is exactly .

Look at the figure. The Sun is at the centre; the teal dot is (Earth at launch) and the orange dots are two possible arrival points . The plum arc sweeps less than 180° (, Type I); the dotted arc sweeps more than 180° (, Type II). The thick faded orange line is the special case where and are anti-parallel — a straight sweep.

Why Δv spikes there — the correct reason. The transfer angle enters Lambert's geometry through the chord and, crucially, through the amount of angular momentum the transfer conic must carry. As , the two radius vectors line up, and the family of connecting ellipses degenerates: the minimum-energy ellipse's required semi-major axis pushes toward the point where the orbit becomes a nearly straight, radial "fall" between the two points. Physically the transverse (sideways) velocity needed to round the corner in the available time collapses, so the solver is forced onto an extreme conic whose departure and arrival speeds — and hence — grow rapidly. In the co-planar idealisation this shows up as a sharp energy spike; in the real 3-D problem the two planet orbits are slightly tilted, so at exactly the transfer plane is only weakly constrained and a modest tilt turns into a large required plane change on top of the energy spike. Either way the root cause is the degenerate transfer geometry as (angular momentum → its singular value, runs to its extreme), not "many planes through a line" alone.

  • Below the ridge (shorter TOF): sweep = Type I transfer.
  • Above the ridge (longer TOF): sweep = Type II transfer.

Edge case — multi-revolution () solutions. Everything above is the zero-revolution () family, where the spacecraft flies straight from to without completing a full loop of the Sun. But for long times of flight Lambert's equation admits extra solutions in which the spacecraft loops the Sun full turns before arriving. Each opens its own pair of Type I / Type II branches, so a full pork chop plot over a wide TOF range can show additional islands stacked at longer flight times, each with its own ridge. Practical Earth–Mars plots usually stay in the family (looping the Sun wastes propellant and time), but a complete treatment must acknowledge these multi-rev branches so you are never surprised by an extra contour cluster high on the plot. See Lambert's Problem.

You pick a lobe and stay off the ridge. See Lambert's Problem and Hohmann Transfer (the ideal Hohmann case is cheap only because it is coplanar by construction, dodging the tilt penalty).


Level 4 — Synthesis

L4.1 — Full round-cell cost

For one grid cell, Lambert's solver returns departure excess km/s and arrival excess km/s. Parking orbit at Earth km; capture at Mars into km. Compute the total mission Δv for this cell.

Recall Solution

Why we can add the two burns at all — the patched-conic idea. The trip is really governed by three bodies (Earth, Sun, Mars), which has no clean solution. The Patched Conic Approximation cuts the journey into three separate two-body problems: (1) a hyperbola escaping Earth's gravity, (2) an ellipse around the Sun, (3) a hyperbola captured by Mars. They are "patched" at the edges of each planet's sphere of influence, where the leftover speed is exactly . Because each piece is a distinct burn in a distinct gravity well, their Δv's do add — but only after each is computed in its own well. That is why we can treat departure and arrival independently below.

Departure (Earth, ) — the master burn formula, because you are climbing out of Earth's well from a circular parking orbit: Arrival (Mars, ) — same formula, now dropping into Mars' well to a circular capture orbit: Total (patched-conic sum): This single number is one contour value — the plot is this computation repeated across every (launch, arrival) cell.

L4.2 — Heliocentric Hohmann sanity check

As a lower-bound reference, compute the ideal Hohmann transfer Δv between Earth's and Mars' circular heliocentric orbits ( km, km, ). Report the two heliocentric burns and their sum. (This is the heliocentric ideal, ignoring the planetary gravity wells.)

Recall Solution

Why vis-viva? We need the speed of the spacecraft at two points on the Sun-centred transfer ellipse. Conservation of energy on any orbit says the specific energy is constant and equals . Solving for gives the vis-viva equation — it answers "how fast am I moving at radius on an orbit of size ?" without needing the full trajectory. That is exactly the question a Hohmann burn asks.

Circular speeds of the two planets (each on its own circle, so , and vis-viva reduces to ): The transfer ellipse touches Earth's circle at perihelion and Mars' circle at aphelion, so its semi-major axis is the average radius: Transfer speeds at each end, from vis-viva: Burns (each is the speed gap between the planet's circle and the transfer ellipse at that radius): Sum — the total heliocentric Hohmann Δv: This is the theoretical cheapest heliocentric transfer — the pork chop's deepest island sits near it. See Hohmann Transfer.


Level 5 — Mastery

L5.1 — Design a launch-window count

A mission can launch to Mars only within a -day window around each opportunity. Over a 10-year exploration campaign, roughly how many distinct Mars launch opportunities occur, using d?

Recall Solution

Opportunities recur every synodic period. Number in 10 years ( d): (The counts the window open at .) Each opens a fresh pork chop; the -day window is a vertical strip you slide inside each island to find the cheapest cell. Design insight: with only shots per decade, missing a window costs months — this is why Δv margin and schedule are negotiated together.

L5.2 — Trade fast-vs-cheap

Opportunity A offers a cell with km/s but TOF days. Opportunity B offers km/s with TOF days. Same parking orbit km. Compute both departure Δv's and the Δv penalty per day of flight-time saved by choosing the faster route.

Recall Solution

Extra Δv for B: km/s. Days saved: d. Reading it: you pay m/s of Δv for each day of flight-time you shave off. For a crewed mission (radiation dose scales with TOF) that may be worth it; for a cheap probe it is not. This is precisely the fast-vs-cheap trade the pork chop plot exists to visualize.

L5.3 — Where is the minimum, geometrically?

Explain, using the shape of the plot, why the minimum-Δv point sits inside a lobe rather than on the shortest-TOF diagonal, and connect it to the near-Hohmann geometry. Sketch the Δv-vs-TOF trend to justify your answer.

Recall Solution

Look at the figure below, which plots departure Δv against time of flight along a single launch column (a vertical slice through one lobe).

Figure — Pork chop plots — Δv vs launch - arrival date

Left end of the curve (short TOF). To reach in very little time the spacecraft must sweep the heliocentric arc fast, which demands a highly eccentric, high-energy conic. High energy means large , and through that means large Δv. So the curve is high on the left (plum note).

Middle of the curve (near-Hohmann). As TOF grows toward roughly days for Earth–Mars — half the period of the minimum-energy transfer ellipse — the required conic relaxes toward that minimum-energy ellipse. The transfer angle is near the ideal Hohmann geometry (planets well-spaced), bottoms out, and Δv reaches its minimum: the orange dot, the "eye" of the pork chop.

Right end of the curve (long TOF). Push TOF longer still and the geometry becomes awkward again: the transfer must loiter, the arc overshoots toward the Type-II regime and eventually toward the ridge singularity of L3.3, so and Δv climb back up.

The three regimes together make a bowl, whose bottom sits at intermediate TOF — never on the shortest-TOF diagonal (that is the expensive left edge). On the 2-D pork chop plot this bowl is what closes the contours into an island: the innermost ring is the bowl's floor, off both TOF extremes.