3.5.51 · D5Guidance, Navigation & Control (GNC)
Question bank — Augmented proportional navigation — gravity compensation
Setting the stage — every symbol earned first
Before any trap, here is the picture the whole page lives in. Two things move in a vertical plane: the missile and the target. The straight arrow from missile to target is the line of sight (LOS) — imagine a taut string joining them.

Now build the second-order dynamics that make "cancel " mean something.

Quick refresher of every symbol used below:
- = LOS angular rate; = its rate of change; = LOS elevation angle (up from horizontal).
- = LOS-normal direction; = magnitude of perpendicular gravity.
- = commanded accel projected onto ; = target accel projected onto .
- = navigation constant; = closing speed; = target accel LOS; = time-to-go.
- Net perpendicular dynamics: , with .
- Full law: .
True or false — justify
The commanded acceleration already includes the effect of gravity, so we do not need the term.
False — is only what the autopilot commands; gravity acts on top of it. The physical normal accel is , so we must pre-subtract to make that sum equal the pure-PN demand .
Gravity compensation makes the missile fly a straight line.
False — it makes the effective guidance loop behave as if gravity-free; the missile still physically droops, but the guidance no longer misreads that droop as target motion.
If the target never maneuvers, the augmentation term vanishes but the term generally does not.
True — kills augmentation, yet gravity keeps bending the LOS unless the shot is vertical, so compensation is still required.
Over a full ballistic arc gravity averages out, so ignoring it costs nothing during homing.
False — during terminal homing the missile is actively closing; the continuous downward produces a persistent that accumulates into a steady miss, it does not average away.
A larger navigation constant increases the target-maneuver term but leaves the gravity term untouched.
True — the gravity term is , independent of ; only the PN and augmentation terms scale with .
Compensation is reactive: it fixes the miss after the droop appears.
False — it is predictive; by supplying in advance it holds so the droop-induced error is never allowed to appear.
For a purely vertical (straight-up) engagement the gravity-compensation term is zero.
True — gravity then lies entirely along the LOS (), so and nothing perpendicular needs cancelling.
The component of gravity along the LOS is harmless to guidance.
True (for ) — only changes closing speed ; it does not rotate the sightline, so it does not corrupt the LOS-rate that PN steers on.
In the transverse equation , leaving inside still lets settle to zero.
False — an uncancelled acts as a constant forcing term, so (hence ) never reaches a steady zero; that is precisely the persistent rate PN wastefully chases.
Spot the error
"Set ."
Wrong sign — gravity must be subtracted. Adding would double the droop instead of cancelling it, since real gravity already contributes to the physical normal accel.
"Compensate with the full : write ."
Over-correction — only the LOS-normal part bends the sightline. Subtracting full would fight a phantom perpendicular pull that isn't there and waste control authority.
"Since is negative, the compensation term should be from a plain dot product."
Half-right, half-trap — the dot product is negative because points opposite 's tilt, but is defined as the projection's magnitude , and the command carries gravity's downward direction through the explicit minus sign ; mixing the two conventions double-counts the sign.
"At LOS elevation , use ."
Wrong trig function — in this convention ( measured up from horizontal) : horizontal LOS () gives the maximum since , whereas would wrongly say no compensation is needed.
"Because right now, no command is needed at all, gravity term included."
Error — with an inertial target and momentarily fixed LOS, pure PN gives , but gravity would immediately create a droop; the compensation still commands to keep at zero.
"APN's handles gravity too, since gravity is just another acceleration."
Error — that term feed-forwards the target's known maneuver via zero-effort-miss; gravity is a self acceleration acting on the missile and needs its own separate term.
"The in comes from averaging up and down gravity."
Error — it comes from the kinematic ZEM of the target maneuver; the cancels against the command gain to leave , nothing to do with gravity.
" can be treated as a fixed constant throughout the engagement."
Error — shrinks to zero at impact; treating it as fixed would mis-scale any ZEM-based feed-forward as the range collapses.
Why questions
Why does only the perpendicular component of gravity affect the LOS rate?
Because in only the transverse accel drives ; a force along enters the radial equation and only lengthens/shortens the range, never rotating the sightline.
Why is horizontal LOS the worst case for gravity compensation?
With the entire gravity vector is perpendicular to the LOS, so — the maximum possible bending of the sightline.
Why does uncompensated gravity waste the missile's g-capacity?
PN continuously commands lateral accel to null the gravity-induced , so precious acceleration budget is spent fighting a ghost instead of the real target.
Why must be recomputed as the engagement evolves rather than fixed once?
The LOS elevation changes throughout the flight, so changes; a stale value would over- or under-compensate as the geometry rotates.
Why do we express gravity via a projection onto instead of just using its vertical value?
Because guidance acts in the LOS frame ; only the projection onto the LOS-normal direction enters the dynamics — see Coordinate frames & projections.
Why does the half-factor survive as a clean number, free of ?
Because the target miss grows as while the ZEM-to-command gain carries a compensating ; the two cancel, leaving only .
Why does making the loop "effectively gravity-free" guarantee intercept on a non-maneuvering target?
Because pure PN in a gravity-free frame drives , which is the constant-bearing, decreasing-range collision condition — the sightline stops rotating so the paths meet.
Edge cases
LOS elevation exactly (target directly overhead, straight-up shot).
; no compensation term acts, but the along-LOS gravity still slows closing speed — harmless to but real for energy.
Closing velocity (missile no longer closing, ).
The PN term collapses and , so the command is dominated by ; geometrically this is a degenerate near-parallel engagement where PN loses its intercept guarantee. If the range is growing — an overshoot/opening pass.
Target maneuver unknown / unestimated ( set to though the target is turning).
The law reduces to PN plus gravity compensation; it will still lag the true maneuver and leave a residual miss, since the feed-forward can only cancel what estimation provides.
with an inertial target and horizontal LOS.
Pure PN and augmentation both give , yet ; the command is exactly , the maximal predictive push that keeps the true collision course from drooping.
Descending LOS where the target is below the horizontal ().
Since is even, — the sign of does not change the magnitude of compensation, only the geometry; a shallow depression ( small) still needs nearly full , a steep dive () needs almost none.
LOS elevation beyond (, target above-and-behind).
turns negative, so the projection flips direction along ; carried through the convention the compensation push reverses sign automatically — the geometry is handled by the cosine, not by hand.
Very short time-to-go ( at impact).
The ZEM-based augmentation stays finite while can spike; gravity's contribution over the vanishing interval becomes negligible, so the term matters least right at the end.