3.5.51 · D3Guidance, Navigation & Control (GNC)

Worked examples — Augmented proportional navigation — gravity compensation

2,701 words12 min readBack to topic

This page is a shooting gallery. We first draw a map of every kind of situation the augmented-PN gravity-compensation law can face, then we walk one fully-worked example through each square of that map. If you have read Augmented proportional navigation — gravity compensation, every symbol below is already yours; if a symbol still feels fuzzy, the parent note builds it from zero.

The one formula we keep firing:

Quick reminder of the plain-word meaning of each letter, so nothing is used unearned:

  • — the sideways ("lateral") push we command, in metres per second squared.
  • — the navigation constant, a plain unitless number, usually to .
  • — closing speed, how fast the gap between missile and target shrinks (m/s).
  • — how fast the line-of-sight (LOS) direction is rotating (rad/s); the little dot means "rate of change".
  • — the target's own sideways acceleration, the part pointed across the LOS (m/s²).
  • — the strength of gravity, i.e. how fast an object speeds up as it falls freely. Near Earth's surface (every second of free fall adds about m/s of downward speed). This single number is the whole reason the missile "droops". It is a fixed constant of the environment, not something we control.
  • — the slice of gravity that points across the LOS and therefore bends our flight (m/s²).
  • — the LOS elevation angle: = looking flat along the ground, = looking straight up.

The scenario matrix

Every worked example below is tagged [Cell N] so you can see we leave no square empty.

Cell Case class What is special Which example
1 Horizontal LOS, non-maneuvering target (worst gravity) Ex 1
2 Steep descending LOS, maneuvering target large small Ex 2
3 Degenerate: (momentary collision course) PN term vanishes, only acts Ex 3
4 Vertical shot, straight up () , gravity along LOS Ex 4
4b Vertical shot, straight down () too — completes the edge Ex 4b
5 Sign flip: LOS rotating the other way () commanded push flips sign Ex 5
6 Diving / negative elevation () still positive → Ex 6
7 Real-world word problem: dart-thrower geometry build from a picture Ex 7
8 Exam twist: acceleration limit saturates the command clip to autopilot cap Ex 8

Worked examples

Ex 1 — Horizontal LOS, worst-case gravity [Cell 1]

  1. PN term. . Why this step? This is what pure PN alone demands from the LOS spin — our baseline.
  2. Gravity term. . Why this step? Horizontal LOS means all of gravity points across the LOS — the most bending possible, the maximum .
  3. Assemble. . Why this step? We subtract so that when gravity later adds back on, the net across-LOS acceleration is exactly the intended .

Verify: effective normal accel — precisely the pure-PN demand. Units: (radians are unitless), and is already m/s², so every term adds cleanly in m/s². Answer smaller than 32, matching the forecast (we back off, because gravity does part of the pushing for us — but in the wrong direction, so it net-cancels).


Ex 2 — Steep descent onto a maneuvering target [Cell 2]

Figure — Augmented proportional navigation — gravity compensation
Figure s01 — Ex 2 geometry. The yellow arrow is the steeply-descending LOS (); the pink arrow is gravity pointing straight down; the dotted white arrow is the large slice of gravity lying along the LOS (harmless — it only changes closing speed); the short blue arrow is , the small slice lying across the LOS. The picture shows why steep geometry makes small.

  1. PN term. . Why this step? Small → modest baseline demand. Units: .
  2. Augmentation term. . Why this step? The feed-forward exactly pre-cancels the zero-effort-miss that a constant target maneuver would otherwise cause. Here is the time-to-go — the seconds remaining until impact; a constant maneuver builds a miss over that window, so the feed-forward is tuned to erase it whatever the current happens to be — see Zero-Effort-Miss (ZEM) guidance. Units: is unitless, so stays in m/s².
  3. Gravity term. . Look at the figure: the LOS points steeply down, so the pink gravity arrow lies mostly along the LOS; only the short blue stub is . Why this step? Steep geometry hides most of gravity inside the LOS direction, where it can't bend .
  4. Assemble. . Why this step? Gravity's contribution is now the smallest of the three — target maneuver rules.

Verify: . Forecast check: the augmentation term (45) dominates, as predicted. All three terms are in m/s², so the sum is a valid acceleration.


Ex 3 — Degenerate collision course, [Cell 3]

  1. Uncompensated PN. . Why this step? A pure-PN brain sees no LOS spin and relaxes — commands nothing.
  2. The trap. With zero command, gravity's acts unopposed → next instant the flight droops → becomes nonzero → PN scrambles to correct after the error appeared. Why this step? Shows the ghost: a "fixed" LOS is not stable without gravity handling.
  3. Compensated APN. . Why this step? The negative sign means "push upward across the LOS", exactly cancelling the impending droop so stays truly .

Verify: net across-LOS accel . Units: both terms m/s², difference m/s² → the LOS rate has zero forcing → stays fixed → a genuine, held collision course. Answer: , not zero — the forecast "free to command zero" is wrong.


Ex 4 — Straight-up shot, gravity fully harmless [Cell 4]

  1. PN term. . Why this step? Standard baseline from LOS spin. Units: .
  2. Gravity term. . Why this step? Straight up, gravity points along the LOS, so it only slows the closing speed — it cannot bend the LOS. Nothing to cancel.
  3. Assemble. .

Verify: as expected for a vertical LOS. Command equals raw PN, in m/s². Forecast answer: zero compensation, correct.


Ex 4b — Straight-down shot, completing the edge [Cell 4b]

  1. PN term. . Why this step? The LOS-spin term does not care which way the LOS points; same baseline as Ex 4.
  2. Gravity term. . Why this step? is even, so . Whether we shoot straight up or straight down, gravity lies entirely along the LOS — no across-LOS slice exists.
  3. Assemble. .

Verify: identically, matching the straight-up case. Units m/s². This closes the geometry map: at both and gravity is harmless. Forecast answer: no change — up and down are symmetric here.


Ex 5 — LOS spinning the other way, [Cell 5]

  1. PN term. . Why this step? A negative means the LOS is swinging the opposite way, so PN pushes the opposite direction — the sign is carried through honestly. Units: .
  2. Gravity term. (still positive: gravity always pulls the same physical way regardless of how the LOS spins). Why this step? Gravity's direction is set by the world, not by 's sign — do not accidentally flip it.
  3. Assemble. .

Verify: effective normal accel , matching the pure-PN demand of . Units m/s² throughout. The command sign is dominated by the PN term but the gravity term is not flipped. Answer .


Ex 6 — Diving engagement, negative elevation [Cell 6]

Figure — Augmented proportional navigation — gravity compensation
Figure s02 — Ex 6. Two LOS arrows are drawn, one tilted above horizontal (blue stub) and one tilted below (pink stub). Because is an even function, the two blue/pink stubs are exactly the same length: a downward-tilted LOS needs the same gravity compensation as an upward-tilted one at the same angle.

  1. Gravity term. . Why this step? Cosine is an even function: . Whether the LOS tilts up or down by the same angle, the amount of gravity lying across it is identical — the figure shows both the up-tilt and down-tilt giving the same stub length.
  2. PN term. . Why this step? Baseline from LOS spin. Units: .
  3. Assemble. .

Verify: came out positive (8.496), because ignores the sign of the tilt — forecast "negative " is wrong. . Both terms m/s², difference m/s².


Ex 7 — Word problem: the falling-dart geometry [Cell 7]

Figure — Augmented proportional navigation — gravity compensation
Figure s03 — Ex 7. The yellow arrow is the shallow climbing LOS at . Gravity (pink, straight down) is split by dropping perpendiculars into a slice along the LOS (, dotted white) and a slice across the LOS (, blue). At shallow tilt the blue slice is nearly the full — almost worst-case bending.

  1. Read the geometry. In the figure the LOS is the yellow arrow tilted ; gravity (pink) points straight down. Drop a perpendicular from the LOS: the piece of gravity across the LOS is , the piece along it is . Why this step? Only the across-LOS slice bends the flight, so that is what we cancel.
  2. Gravity term. . Why this step? Shallow tilt → cosine near 1 → almost all of gravity still bends the LOS (near worst case).
  3. PN term. .
  4. Augmentation term. . Why this step? The drone is maneuvering, so we feed-forward its miss with (same -independent logic as Ex 2).
  5. Assemble. .

Verify: , close to the full — forecast "nearly full-strength" confirmed. . All terms m/s².


Ex 8 — Exam twist: autopilot acceleration limit [Cell 8]

  1. Compute the unclipped demand. (from Ex 7). Why this step? The guidance law runs first; the limiter acts on its output.
  2. Apply the cap. Since , the delivered command is clipped to . Why this step? The airframe/structure can physically pull only so hard; anything beyond is impossible.
  3. Lost authority. Shortfall . Why this step? This deficit is what causes a residual miss — and it is exactly the argument for not wasting g-capacity chasing gravity: had we skipped compensation the gravity ghost would eat even more of the cap.

Verify: clipped value . Lost , in m/s². The compensation term () is inside the number being clipped, so at saturation the fight against gravity is partially sacrificed along with everything else — forecast "still gets through fully" is false. This is why staying below the cap (Ex 1–4 style) matters.


Recall Fast self-test

Horizontal LOS makes equal to what? ::: The full (because ) — worst case. A negative elevation gives what sign of ? ::: Positive, since is even (). If and target is inertial, what does compensated APN command horizontally? ::: , pre-empting the droop. Straight-up AND straight-down shots need how much compensation? ::: Zero in both, because . Where does the autopilot limiter act — before or after the guidance law? ::: After: it clips the law's output .


Connections