Orbits

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.

Assumes Hyperbolic orbits, Patched conics and Gravity assist.

The rung below settled what classifies an open orbit: not the eccentricity but the hyperbolic excess speed, the residual velocity a body still has after the primary has finished pulling on it.

Getting a spacecraft to a particular open orbit is a different problem, and it has an answer that looks arbitrary until the reason is stated. A trajectory is not targeted by its closest approach distance, and it is not targeted by its periapsis latitude or its arrival time. It is targeted by a point in a plane — and the plane is defined by the trajectory itself.

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.
Fig. 1 The reason, in one curve. Periapsis distance against aim point for an approach to Jupiter at 5.6 km/s, both in planet radii, with the diagonal marking what the two would be if gravity did nothing. The slope of this curve — how much the closest approach moves when the aim moves — is 0.21 at one end of the useful range and 0.94 at the other. The same correction manoeuvre changes the miss distance by four and a half times as much in one place as in another, and changes the aim point by exactly as much everywhere.

What the plane is

Take the incoming asymptote of the hyperbola: the straight line the spacecraft would follow if the planet had no gravity, running along the direction S^\hat{S} of the incoming velocity v\mathbf{v}_\infty.

The B-plane is the plane through the centre of the target body perpendicular to S^\hat{S}. The aim point B\mathbf{B} is the vector from the body’s centre to the point where that asymptote pierces it — which is the impact parameter of the encounter, the perpendicular distance from the centre to the undeflected path.

Two axes are laid out in the plane by convention. T^\hat{T} is taken parallel to some reference plane, usually the target’s orbit plane or the ecliptic; R^=S^×T^\hat{R} = \hat{S}\times\hat{T} completes the set. Every arrival is then quoted as a pair of numbers, BT^\mathbf{B}\cdot\hat{T} and BR^\mathbf{B}\cdot\hat{R}, in kilometres.

1I/ʻOumuamua: an orbit at e = 1.201, and the angle it turned through. The open branch of a conic at eccentricity 1.201 and periapsis 0.2559 AU, with the Sun at the occupied focus. Two numbers fix everything else: |a| = q/(e−1) = 1.273 AU, an impact parameter b = |a|√(e²−1) = 0.847 AU, an asymptote at ν∞ = arccos(−1/e) = 146.37° from periapsis, and a deflection of δ = 2ν∞ − 180° = 112.74° — which is the same statement as sin(δ/2) = 1/e. The asymptotes cross at |a|e = 1.529 AU from the Sun on the periapsis side, where a bound orbit's centre would be on the other. The speed left over at infinity is √(μ/|a|) = 26.40 km/s. Schematic in one respect: the drawing runs at about 119 px to the AU, so the Sun's own disc would be far smaller than its marker.
Fig. 2 The geometry the plane is built on. A hyperbolic passage with its two asymptotes and the turn between them: the incoming asymptote is what S^\hat{S} points along, and the perpendicular distance from the focus to it is B=ae21B = |a|\sqrt{e^2-1}. The turn angle follows from the eccentricity alone, and since the eccentricity of an approach at fixed vv_\infty is fixed by BB, the aim point and the turn are the same information written twice.

Why not aim at the periapsis distance

The obvious coordinate would be the closest approach distance rpr_p, which is what a mission actually cares about. The relation between it and the aim point is exact:

rp=μv2(1+(Bv2μ)21).r_p = \frac{\mu}{v_\infty^2}\left(\sqrt{1 + \left(\frac{B v_\infty^2}{\mu}\right)^2} - 1\right).

Far from the planet, where Bv2/μ1Bv_\infty^2/\mu \gg 1, that reduces to rpBr_p \to B: with focusing negligible, the aim point is the miss distance. Close in, where the same quantity is small, it reduces to rpB2v2/2μr_p \approx B^2 v_\infty^2/2\mu — quadratic in BB.

So rpr_p is a strongly nonlinear function of the thing a manoeuvre controls, and its sensitivity varies by a factor of several across any real targeting range. That is fatal for a linearised control problem: the partial derivative rp/Δv\partial r_p/\partial \Delta v is not a constant, so a correction computed from one linearisation is wrong by the amount the derivative has changed since.

The aim point has no such problem. A small velocity change Δv\Delta\mathbf{v} applied a time tt before arrival displaces the asymptote by very nearly Δvt\Delta \mathbf{v}\,t resolved into the plane, whatever B\mathbf{B} happens to be. The partial derivatives are essentially constant over the whole region of interest, and the targeting problem becomes a two-by-two linear solve.

A coordinate is chosen for the behaviour of its derivatives, not for its physical meaning, and that is the whole content of the B-plane.

The delivery ellipse

Navigation does not deliver a point. It delivers a distribution, and the distribution is drawn in the B-plane as an ellipse: the projection of the trajectory’s covariance onto the two coordinates that matter.

Four corrections, and a delivery ellipse that shrinks by 186 in one coordinate. The B-plane of a Jupiter arrival, in kilometres, with the aim point and its three-sigma delivery ellipse after each of four trajectory-correction manoeuvres. B·T and B·R are the two coordinates of the plane, defined from the incoming asymptote and the target's orbital plane, and they are the ones every navigation product is written in — a manoeuvre is designed as a displacement in this plane, an uncertainty is published as an ellipse in it, and the corridor a mission must arrive inside is a box drawn on it. The sequence converges geometrically: the ellipse's semi-axes fall from 2.6·10⁵ × 4.4·10⁵ km to 1400 × 2200, a factor of 186, and each step is small because each step is cheap only if the previous one was accurate. The shaded box is the arrival corridor; the final ellipse is inside it at three sigma, which is the criterion an arrival is actually approved against. Nothing here is a distance from the planet — the aim point is a distance from the asymptote, and the periapsis it produces is a separate calculation.
Fig. 3 Four corrections and their delivery ellipses, in kilometres. Each manoeuvre moves the aim point towards the target and shrinks the ellipse, and the sequence converges geometrically because each step is only as good as the tracking that preceded it. The shaded box is the arrival corridor — the region an instrument or an entry requires — and the criterion an arrival is approved against is that the final ellipse fit inside it at three sigma, not that the nominal aim be correct.

The shape of that ellipse is informative in itself. It is usually long in one direction and short in the other, and the long axis points along the direction the tracking is worst at — which for a spacecraft tracked by Doppler alone is the direction across the line of sight. Adding an interferometric measurement rotates and shortens it, which is why deep-space navigation budgets pay for angular data even though the ranging is a thousand times more precise.

The manoeuvre schedule follows from the same arithmetic. A correction applied early is cheap, because a small velocity change has a long time to act: the displacement per unit Δv\Delta v is proportional to the time remaining. It is also imprecise, because the trajectory is not yet well known. A correction applied late is expensive and accurate. Every mission therefore has a sequence, each step smaller than the last, and the total propellant is dominated by the earliest one and the final accuracy by the latest.

What the aim point buys

Three quite different things are all specified as a location in this plane, which is a large part of why it is used.

A turn. For a flyby whose purpose is to change the heliocentric orbit, what matters is the deflection angle, and

tanδ2=μBv2.\tan\frac{\delta}{2} = \frac{\mu}{B v_\infty^2}.

Choosing the aim point chooses the turn. There is a hard limit — the planet has a surface, or an atmosphere — so the largest available turn corresponds to the smallest safe BB, and everything a tour can achieve at a given encounter speed is bounded by it.

A gravity assist with a 70° turn. The velocity triangle of a flyby. In the planet's frame the spacecraft's speed is unchanged and only its direction turns; adding the planet's own velocity converts that turn into a gain in speed measured from the Sun.
Fig. 4 What the turn is worth. The velocity triangle of a flyby: in the planet’s frame the speed is unchanged and only the direction turns, and adding the planet’s own motion back converts that turn into a change in heliocentric speed. The aim point sets the angle at the vertex, so it sets the whole of the gain — and since the circle’s radius is vv_\infty, which no flyby can change, the aim point is the only thing an encounter has to work with.

An entry corridor. For a probe that must survive an atmosphere, the requirement is a band of entry flight-path angles, and that band maps directly to an annulus in the B-plane. The Galileo probe’s corridor at Jupiter was a few tens of kilometres wide out of an aim point of tens of thousands, delivered from a release six months earlier. A prohibition. Planetary-protection rules for missions carrying unsterilised hardware past a possibly habitable moon are written as a probability of impact, and the calculation is exactly the one an impact probability for an asteroid uses: a distribution in the target plane, a capture cross-section, and an integral. Cassini’s end-of-mission disposal into Saturn was designed against a requirement of that shape — a bound on the chance that an uncontrolled spacecraft would eventually strike Enceladus or Titan, computed decades forward through a covariance.

Those three requirements pull in different directions, and reconciling them is most of what an arrival design consists of. A larger turn wants a smaller aim point; an entry corridor wants a specific narrow annulus; a prohibition wants the delivery ellipse to have no overlap with a forbidden region at all. All three are drawn on the same two axes, in kilometres, which is exactly why those axes are the ones everybody works in — a plane in which every requirement, every measurement and every manoeuvre can be drawn as a region is worth more than a plane with a tidier physical meaning.

How the aim point is known

Nothing in this subject is measured directly, and the aim point is a good example of how far a quantity can be from the observation that fixes it.

A deep-space spacecraft is tracked in three ways, and none of them measures a position.

Two-way Doppler measures the rate of change of the distance to the tracking station, by comparing the frequency of a signal returned by the spacecraft’s transponder with the one sent to it. The precision is extraordinary — a few hundredths of a millimetre per second over a few minutes — but it is a rate, and along one direction only.

Ranging measures the round-trip light time of a coded signal, giving a distance good to about a metre at any distance. Also one-dimensional.

Delta-differential one-way ranging compares the arrival time of the spacecraft’s signal at two widely separated antennas against the arrival time of a quasar’s, which cancels most of the media and clock errors. It measures an angle, to a couple of nanoradians — which at five astronomical units is about a kilometre and a half.

The aim point is then a fitted parameter, in exactly the sense the rest of this field uses the word: an orbit determination takes weeks of those three data types, fits a trajectory, propagates it to the encounter, and reports where the asymptote lands. Nobody ever measures B\mathbf{B}; it is the output of a solution, with a covariance, and the delivery ellipse is that covariance drawn.

The Earth’s own rotation is what makes the geometry work. A station’s line of sight to the spacecraft swings through a day, so a series of Doppler measurements over several hours samples the trajectory from a range of directions and recovers information about the two coordinates the instantaneous measurement cannot see. It is the same trick as an orbit determination from angles alone, with the roles of the observer and the target exchanged.

What that machinery has actually delivered

The numbers are worth stating, because they are the argument for the whole apparatus.

Voyager 2 reached Neptune in August 1989 after twelve years and four and a half billion kilometres, and arrived within about thirty kilometres and a few seconds of its aim. New Horizons reached Pluto in July 2015 after nine and a half years, and arrived inside a target box seventy kilometres and a minute across — a requirement set by the need to point instruments at a body whose position was itself uncertain by hundreds of kilometres before the approach imaging began.

Neither number is a statement about propulsion. Both are statements about a fit: the trajectory was determined, the residual aim error was computed in the B-plane, a manoeuvre of a few centimetres per second was designed to remove it, and the process was repeated. The final corrections on both missions were smaller than the noise on a domestic bathroom scale expressed as a velocity.

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 Earth at v∞ = 3 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 19.87 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.151 at an aim of 30 radii and 0.745 at 220, so the same correction manoeuvre changes the periapsis distance by 4.9 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∞²), 162.7° at 30 radii and 109.2° at 140 — is thought of as a function of B rather than of anything the spacecraft does.
Fig. 5 The same plane at the other end of a mission, where the target is the planet the craft came from. An Earth return arrives slowly — three kilometres a second against Jupiter’s five and a half — and a slow arrival is focused hard: the gravitational focusing pulls the periapsis in so far that an aim point below about twenty Earth radii is not a close approach at all but an impact, and the generator refuses to draw one. Everything in the targeting is done in this plane rather than in the sky, because a B-plane offset maps almost linearly onto the periapsis and a pointing angle does not.

Aiming deliberately at the wrong place

There is a practice in arrival design that looks like an error and is the opposite of one.

A spacecraft carrying hardware that has not been sterilised must not impact a body that might be habitable, and the requirement is a probability rather than an intention. So the trajectory is not aimed at the target until quite late: it is biased, aimed at a point in the B-plane far enough from the body that even a total loss of control leaves the spacecraft missing.

The bias is removed in stages. As the tracking improves and the delivery ellipse shrinks, successive manoeuvres move the aim point closer to the intended one, and at each stage the aim is chosen so that the residual impact probability — computed from the current ellipse, not the eventual one — stays below the requirement.

That converts the manoeuvre sequence from a convergence into a negotiation. An early correction cannot simply target the final aim point even if it could reach it, because doing so would put an impact inside the current uncertainty; and a late correction cannot be deferred indefinitely, because the propellant needed grows as the time remaining falls.

The clearest applications are the Jupiter missions, where a flyby of Europa is scientifically valuable and an impact on it is prohibited, and the arrival design has to deliver a close pass from a trajectory that was, weeks earlier, aimed at empty space.

The same logic applies to the end of a mission. A spacecraft that has run out of propellant is a spacecraft whose trajectory can no longer be corrected, so its final state has to be one from which no plausible perturbation produces an impact for decades or centuries — which is a statement about a distribution in a target plane propagated forward through a chaotic multi-body system.

A requirement expressed as a probability is met by aiming somewhere the mission does not want to go, and unwinding that bias on a schedule is a substantial part of what an arrival campaign consists of.

The linearisation, and where it fails

The whole apparatus rests on the assumption that the map from a small Δv\Delta \mathbf{v} to a displacement of B\mathbf{B} is linear. Three things break it.

A close approach on the way. If the trajectory passes another body between the manoeuvre and the arrival, the map is no longer linear — the intermediate encounter amplifies some directions and compresses others, sometimes by orders of magnitude. Multi-flyby tours are therefore targeted encounter by encounter rather than end to end.

An aim point close to the capture radius. The relation between BB and rpr_p is steep there, so although B\mathbf{B} is still well behaved, the requirement expressed in rpr_p becomes brutally tight. A mission aiming at a periapsis of one planet radius has to control BB far better than one aiming at ten.

A long lever arm. The displacement per unit Δv\Delta v grows with the time remaining, which sounds like an advantage and is also an error multiplier: an execution error in the manoeuvre is magnified by the same factor. Early manoeuvres therefore need clean-up manoeuvres, and the sequence in the figure above is not conservatism but arithmetic.

There is a fourth failure that is not a linearisation problem at all. The B-plane is defined by the incoming asymptote, and the incoming asymptote is a property of the trajectory being corrected — so the coordinate system moves when the trajectory does. For a small correction that is a second-order effect and ignorable. For a large one it is not, and the standard practice is to re-derive the plane after each manoeuvre rather than to keep targeting in the old one. A correction quoted in a stale B-plane is quoted in a frame that no longer exists, which is the sort of error that survives every check because both numbers are individually correct.

Speed against distance, for four conics through the inner solar system. Vis-viva, v = √(μ(2/r − 1/a)), on a logarithmic distance axis, for four orbits: 1P/Halley (q = 0.5859 AU, e = 0.96714), a parabolic comet (q = 0.2559 AU, e = 1), 1I/ʻOumuamua (q = 0.2559 AU, e = 1.201), 2I/Borisov (q = 2.006 AU, e = 3.356). The bound orbit's curve stops, at aphelion and at a speed of 0.91 km/s rather than at zero. The parabola's falls towards zero and takes forever to get there. Each hyperbola flattens onto a speed it never loses: 26.40 km/s for 1I/ʻOumuamua and 32.28 km/s for 2I/Borisov. That number is what makes an interstellar object interstellar, and it is fixed by |a| alone.
Fig. 6 And the quantity that fixes everything above. Speed against distance for four conics through the inner solar system: the bound ones tend to zero far out and the unbound ones tend to vv_\infty. Since the turn angle depends on Bv2B v_\infty^2, a fast arrival is a hard one to steer — 2I/Borisov’s excess speed of 32 km/s would give almost no deflection at any aim point a planet could offer, which is the same reason interstellar objects cannot be captured.

The bias is therefore a schedule as much as a geometry, and it is set at design time rather than negotiated in flight.

The same plane, for something nobody is steering

The coordinate was built for spacecraft and it is used just as heavily for objects that are not being flown, and the transfer is nearly exact.

An asteroid approaching the Earth has an incoming asymptote, an excess speed and an aim point, and its uncertainty is a distribution in the same plane. The impact probability is the integral of that distribution over the region whose aim points lead to a strike — which, with focusing, is a disc of radius R1+vesc2/v2R\sqrt{1 + v_{\text{esc}}^2/v_\infty^2} rather than the Earth’s own radius.

Two differences of practice are worth noting. For a spacecraft the distribution is nearly Gaussian, because the uncertainty comes from measurement noise on a well-modelled trajectory over a short interval. For an asteroid observed over years and propagated over decades, the uncertainty region is stretched and curved by the nonlinear dynamics, so the “ellipse” is a long thin arc and integrating over it requires sampling rather than a covariance.

And the asteroid case has a second target plane in use — one defined not by the object’s own asymptote but by the perpendicular to the Earth’s velocity, which is more convenient when the encounter is slow and the focusing is strong. Reports quoting a miss distance in one plane and an uncertainty in the other are a known source of confusion.

What survives unchanged is the reason for using a plane at all. An impact probability is an integral over a region, and a region is only well defined in coordinates where the dynamics are approximately linear — so the argument that made the B-plane the right choice for aiming a spacecraft makes it the right choice for deciding whether something is going to hit.

The plane is the same construction at every target, and the two things that change between targets are worth drawing.

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 Saturn 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.
Fig. 7 The aim plane at Saturn rather than Jupiter. The contours of periapsis distance are more widely spaced, because Saturn’s gravity focuses less strongly at the same approach speed — so the same navigation error translates into a larger miss, and the delivery requirement is tighter.
Four corrections, and a delivery ellipse that shrinks by 186 in one coordinate. The B-plane of a Jupiter arrival, in kilometres, with the aim point and its three-sigma delivery ellipse after each of four trajectory-correction manoeuvres. B·T and B·R are the two coordinates of the plane, defined from the incoming asymptote and the target's orbital plane, and they are the ones every navigation product is written in — a manoeuvre is designed as a displacement in this plane, an uncertainty is published as an ellipse in it, and the corridor a mission must arrive inside is a box drawn on it. The sequence converges geometrically: the ellipse's semi-axes fall from 2.6·10⁵ × 4.4·10⁵ km to 1400 × 2200, a factor of 186, and each step is small because each step is cheap only if the previous one was accurate. The shaded box is the arrival corridor; the final ellipse is inside it at three sigma, which is the criterion an arrival is actually approved against. Nothing here is a distance from the planet — the aim point is a distance from the asymptote, and the periapsis it produces is a separate calculation.
Fig. 8 And the correction schedule for an Earth return rather than a giant-planet arrival. The corridor is narrow relative to the planet, the last correction has to be late, and the cost of being late is that the manoeuvre itself is larger — which is the trade every entry navigation plan is built around.

Where this ladder goes next

This rung has established the targeting coordinate and why it is the one used: linear in the control, exactly related to the turn, and the natural home for a delivery ellipse.

The rung above is the tour, where the aim point at one encounter determines the arrival conditions at the next, and where the design problem becomes a search over sequences of B-plane targets. What one flyby can reach is bounded by the invariant it cannot change, and the aim point is the only free variable inside that bound.

Beside it lies the capture problem: what has to be given up, in propellant or in atmosphere, to convert a hyperbolic arrival into a bound orbit — and why the cheapest place to do it is the periapsis the aim point has just chosen.

And below it, the habit this rung is really about: the right coordinate is the one whose derivatives are constant. Aiming at the quantity a mission cares about is natural, comfortable, and the reason a targeting problem becomes ill-conditioned.

What links here

Essays that link to this one from their own argument.

The objects this essay names

Each one links to every other essay that touches it.

Aim pointThe B-planeDelivery ellipseEntry corridorGravitational focusingHyperbolic excess speedImpact parameterIncoming asymptoteLinearisationPlanetary protectionA trajectory-correction manoeuvreTurn angle