Astronomy & Celestial Mechanics
the sky, computed
Concept

Turn angle — where it appears

The angle through which a flyby rotates a spacecraft's velocity relative to the planet, given by sin(δ/2) = 1/e. It depends on the aim point and the encounter speed and on nothing the vehicle does, and it is the entire freedom a single gravity assist has.

Named by 3 essays across 2 fields — each of them below, with the objects they name alongside it.

The aim point and the miss distance are the same number far out and nothing like it close in. Periapsis distance against aim point for a hyperbolic approach to Jupiter at v∞ = 5.6 km/s, both in planet radii. The diagonal is where the two would be equal — where gravity did nothing — and the curve falls below it everywhere, by more the closer in the aim is. A trajectory aimed at 10.68 radii grazes the surface, because gravitational focusing means the planet's effective size is √(1 + v_esc²/v∞²) times its radius. The slope of this curve is what a navigation team cares about: it is 0.208 at an aim of 12 radii and 0.936 at 150, so the same correction manoeuvre changes the periapsis distance by 4.5 times as much at one end of the range as at the other, while changing B by exactly the same amount at both; far outside this plot, where focusing has run out, it reaches 1.000 and the two numbers become the same one. That is why the aim point is the coordinate a manoeuvre is quoted in, why an error ellipse is published in the B-plane, and why the turn angle — 2 arctan(μ/Bv∞²), 156.0° at 12 radii and 77.8° at 70 — is thought of as a function of B rather than of anything the spacecraft does.

Aiming at a plane instead of at a planet

A spacecraft arriving at a planet is not aimed at a periapsis distance. It is aimed at a point in a plane perpendicular to its own incoming asymptote, because that is the one coordinate in which the miss distance responds linearly to a correction — and every navigation product ever published for a flyby is written in it.

orbits · Hyperbolic orbits Along a contour is free; across one costs, and 6 resonances sit on this one. Perihelion against aphelion, in units of Jupiter's orbit, with contours of constant v∞ — which is the Tisserand parameter through v∞² = (3 − T)v_p². Every contour crosses the line r_p = r_a = 1, because a spacecraft has to be at the planet's orbit to have an encounter there at all, and every point on one contour is reachable from every other point on it with no propellant: a flyby rotates the v∞ vector without changing its length, which moves the pump angle and slides the spacecraft along the curve. A burn is the only thing that moves it between curves, and that is the whole economy of a gravity-assist tour. The diagonals are resonant orbits — 1:1, 3:2, 2:1, 5:2, 3:1, 4:1 with the planet — and each is a straight line of slope −1 because a resonance fixes the semi-major axis and r_p + r_a = 2a. They matter because a spacecraft on one comes back to the same place at the same time as the planet, which is what makes a second encounter possible without waiting for a chance alignment. The marked points are where the v∞ = 0.3 contour meets each: a tour is a walk along the highlighted curve from one to the next, and the arithmetic that decides whether it can be walked is the turn one flyby delivers. At 1.35 Jupiter radii and 3.9 km s⁻¹ that turn is 163°, so the longest step drawn here needs 0.1 encounters — which is why a real tour has dozens of flybys and why the ones with the largest steps are the ones that need a deep-space manoeuvre in between.

The same planet, three times

A flyby cannot change the encounter speed, only its direction, so a tour has to be designed in the space of what is conserved. One pass moves a spacecraft along a single curve and no further than the planet can bend it — and reaching a distant target means walking that curve, returning to the same planet again and again.

spaceflight · Gravity assist Along a contour is free; across one costs, and 6 resonances sit on this one. Perihelion against aphelion, in units of Jupiter's orbit, with contours of constant v∞ — which is the Tisserand parameter through v∞² = (3 − T)v_p². Every contour crosses the line r_p = r_a = 1, because a spacecraft has to be at the planet's orbit to have an encounter there at all, and every point on one contour is reachable from every other point on it with no propellant: a flyby rotates the v∞ vector without changing its length, which moves the pump angle and slides the spacecraft along the curve. A burn is the only thing that moves it between curves, and that is the whole economy of a gravity-assist tour. The diagonals are resonant orbits — 1:1, 3:2, 2:1, 5:2, 3:1, 4:1 with the planet — and each is a straight line of slope −1 because a resonance fixes the semi-major axis and r_p + r_a = 2a. They matter because a spacecraft on one comes back to the same place at the same time as the planet, which is what makes a second encounter possible without waiting for a chance alignment. The marked points are where the v∞ = 0.3 contour meets each: a tour is a walk along the highlighted curve from one to the next, and the arithmetic that decides whether it can be walked is the turn one flyby delivers. At 1.35 Jupiter radii and 3.9 km s⁻¹ that turn is 163°, so the longest step drawn here needs 0.1 encounters — which is why a real tour has dozens of flybys and why the ones with the largest steps are the ones that need a deep-space manoeuvre in between.

A map of the transfers that are free

Drawn as contours of perihelion against aphelion, the invariant that survives an encounter becomes a map. A flyby slides a spacecraft along its own contour and costs nothing; a burn is the only thing that moves it between contours — so tour design is reading a graph.

spaceflight · Tisserand parameter

Named alongside it

The objects these essays reach for when they reach for this one.

Crank angleA deep-space manoeuvreLaunch energyPump angleResonant returnThe Tisserand graphTour designAim pointThe B-planeBroken plane manoeuvreDelivery ellipseEntry corridor

All concepts