3.5.53 · D3Guidance, Navigation & Control (GNC)

Worked examples — Powered descent guidance — G-FOLD algorithm (convex optimization)

4,149 words19 min readBack to topic

This page is a drill room. The parent note built the theory; here we exhaust every shape the problem can take: signs, degenerate inputs, limiting cases, a word problem, and an exam twist. Work each one before reading the steps.

Before we start, a one-line recap of the symbols we reuse everywhere (never used before being named):


The scenario matrix

Every powered-descent question is one (or a blend) of a small family of cells. Rather than memorise a table, picture the map below. It has two big branches — vertical (1-D) feasibility on the left and glide-slope geometry on the right — each splitting into sign cases, degenerate cases, and limits. Sketch of the map, so you can follow it without opening the image file:

Powered descent question

Vertical 1-D feasibility

Glide-slope geometry

C1 signs

C2 fit

C3 hover

C4 Tmin to 0

C5 bang-bang

C0 upward v

C6 offset

C7 cone limits

C8 log-mass fuel

C9 and C10 real and exam

Figure — Powered descent guidance — G-FOLD algorithm (convex optimization)

Figure (matrix): the same map drawn to scale — root at top, the blue vertical-feasibility branch (leaves C0–C5) on the left, the green glide-slope branch (leaves C6–C7) on the right, and the orange/red fuel-and-exam leaves (C8–C10) hanging off the bottom. Each leaf is one worked example below.

  • C0 — degenerate quadrant (still climbing): what happens if we start moving up? → Example 0
  • C1 — sign of net acceleration (thrust vs gravity): can we even fight gravity? → Example 1
  • C2 — stopping distance vs altitude: does the burn fit? → Example 2
  • C3 — degenerate (hover): what thrust just holds still? → Example 3
  • C4 — limiting (deep throttle): when does coast-then-burn appear? → Example 4
  • C5 — bang-bang timing: when to start the suicide burn? → Example 5
  • C6 — glide-slope offset (horizontal position): cone constraint → Example 6
  • C7 — degenerate cone and : limits of the funnel → Example 7
  • C8 — fuel via : log-mass bookkeeping → Example 8
  • C9 — word problem (real Mars/F9 numbers): put it together → Example 9
  • C10 — exam twist (infeasible input): recognise "no landing exists" → Example 10

Numbers reused across cells (Mars-ish): , , unless stated.


Example 0 — Initial upward velocity, the edge case (Cell C0)

Forecast: Guess whether the extra climb makes the eventual landing easier or harder.

  1. Coast up until . Using the sign convention, gravity decelerates the climb: extra height m. Why this step? A positive is a brand-new quadrant — the lander first moves away from the pad. Kinematics gives the turning point where upward speed hits zero.
  2. Peak height. m. Why this step? Peak is where all upward speed has been converted to height; from here the problem becomes an ordinary descent.
  3. Speed back at 100 m. By symmetry of free fall, it returns to m with m/s. Why this step? Energy conservation (no thrust, no drag) makes the down-trip mirror the up-trip — so an initial becomes an ordinary descent, which we already know how to land (Examples 2, 5).

Verify: m ✔; peak m; return speed m/s (magnitude) ✔.


Example 1 — Sign of net acceleration (Cell C1)

Forecast: Guess whether the lander can decelerate (slow its fall) at both throttle settings.

  1. Net at full throttle. (upward). Why this step? Newton adds accelerations as vectors; up is , gravity is , so we literally add the signed numbers.
  2. Net at min throttle. (downward). Why this step? At the throttle floor the engine can't out-push gravity — the sign flips negative, meaning it still accelerates downward.

Verify: ✔; ✔. Units: all . The min-throttle net being negative confirms the engine's floor cannot hover — see C3.


Example 2 — Does the burn fit? (Cell C2)

Forecast: Guess the stopping distance — more or less than 100 m?

Here is the vertical distance the lander travels while braking to a stop — measured downward from where the burn starts. Because the lander is directly above the pad, this is a drop in height, i.e. a change in : if the burn started at and used up all m, it would just touch down at . So comparing against the starting height is the whole feasibility test.

  1. Switch to magnitudes. Following the sign-convention box above, the signed state becomes entry speed m/s, and the signed net (up, opposing the fall) becomes braking deceleration . Why this step? Braking is a single straight downward segment where velocity and motion share a direction; the direction is already fixed by "up is ", so only sizes matter and we may drop the signs.
  2. Pick the tool: kinematics . Here is the speed at the end of braking (we want ), m/s, , and is the braking distance defined above. Why this tool? We know a start speed, a constant braking deceleration, and want the distance to reach . This equation links exactly those three with no time needed — the cleanest question-answerer here.
  3. Set final speed to zero and solve for . m. Why this step? is the "just stopped" condition; solving isolates the shortest possible stopping distance at max brake.
  4. Compare to the starting height . . ✔ Feasible. Why this step? is the height eaten up while stopping; if the lander reaches zero speed at or above the pad, so a soft landing is physically possible. If instead it would still be moving at ground level — a crash. The inequality is the feasibility criterion.

Verify: ✔, and . Units: ✔.


Example 3 — Hover, the degenerate case (Cell C3)

Forecast: Guess the number before computing.

  1. Hover means zero net acceleration. Require . Why this step? "Hold still" is the degenerate case where velocity never changes, so the net must be exactly zero — thrust cancels gravity.
  2. Check the box. Is ? Yes. Why this step? A command outside is physically impossible; here it sits just above the floor, so hover is achievable.

Verify: ✔ and ✔.


Example 4 — Limiting case (Cell C4)

Forecast: Does zero-floor throttle make more or less altitude available for coasting?

  1. Max brake unchanged. Full-throttle net is still ; stopping distance still m. Why this step? The upper limit sets braking power; lowering the floor doesn't change max deceleration.
  2. What the floor controls. With the engine may switch fully off, giving a pure coast at net . Why this step? Recall the parent note's obstacle: the constraint forbids all thrust vectors shorter than , i.e. it bans the inside of a ball of radius in thrust-space, leaving only the region outside that sphere — a non-convex hole. Sending shrinks that forbidden ball to a point, so the hole vanishes and is free to reach (engine fully off).
  3. Coast distance available. From , the ship coasts freely, then must have m left to brake. So it may coast up to m before the mandatory burn. Why this step? This is the geometric meaning of bang-bang: coast as long as possible, brake at the last legal instant.

Verify: m of coast ✔; ✔.


Example 5 — When to fire: bang-bang timing (Cell C5)

Figure — Powered descent guidance — G-FOLD algorithm (convex optimization)

Figure (Example 5): height on the vertical axis (m) versus speed on the horizontal axis (m/s). The blue curve is the free-fall coast (speed grows as height drops); the red curve is the full-throttle brake (speed shrinks to zero). They meet at the orange dot — the burn-start handoff at m/s, height m. The blue dot top-right is the start (v=20, r=100); the green dot at the origin is the soft touchdown (v=0, r=0). In words: read it right-to-left in time — the ship slides up the blue coast curve gaining speed, hits the orange corner, then rides the red brake curve down to the green origin.

Forecast: Guess whether the coast lasts more or less than 2 seconds.

  1. Speed when braking begins. Let be the speed at the moment the burn starts. The brake segment must bleed off all of over the remaining height: (height remaining). Why this step? Total altitude is shared between coast and brake segments; we match speed and height at the handoff point (the orange dot in the figure).
  2. Set up the two segments. Coast drops height gaining speed . Brake needs . Why this step? Two equations, two unknowns () — the geometry of the red brake curve meeting the blue coast curve in the figure.
  3. Solve. Substitute: m. Then m/s. Why this step? Algebra finds the exact handoff altitude — the corner in the figure.
  4. Coast time. s. Why this step? Under constant coast accel, speed grows linearly, so time is the speed gain over the accel.

Verify: m, m/s, and ✔. Coast time s ✔.


Example 6 — Glide-slope cone, horizontal offset (Cell C6)

Figure — Powered descent guidance — G-FOLD algorithm (convex optimization)

Figure (Example 6): side view of the glide-slope funnel. Horizontal axis = horizontal radius (m); vertical axis = height (m). The two blue lines are the cone walls; the shaded band between them is the allowed funnel. The red dot marks the lander at radius m, height m — sitting exactly on the wall. The green dot at the origin is the target. In words: a cone is a perfect "V" whose walls rise one metre up for every metre out, so at height 200 m the widest legal position is exactly 200 m out.

Forecast: Guess whether at 200 m clears a 45° funnel.

  1. Write the cone constraint. . Why this tool? measures the funnel's steepness; the cone says "your horizontal distance may not exceed what that slope allows at your height." (Same "opposite over adjacent" as the parent's arctan story.)
  2. Compute the horizontal radius. m. Why this step? Pythagoras turns two horizontal offsets into one radius — the quantity the cone limits.
  3. Compute the allowance. m. Why this step? At 45° the allowed radius equals the height exactly.
  4. Compare. on the cone surface, i.e. just barely legal. Why this step? Equality means the lander sits on the funnel wall; any further out is infeasible.

Verify: ✔; ✔; ✔.


Example 7 — Degenerate cones: and (Cell C7)

Figure — Powered descent guidance — G-FOLD algorithm (convex optimization)

Figure (Example 7): same side-view axes (horizontal radius in m vs height in m). Three cone walls are drawn from the origin: red = (a narrow near-vertical chute), blue = , green = (a wide, near-flat funnel). The orange dot is the test point at radius m, height m; the dashed gray line marks radius . The point sits inside the green cone, outside the red one. In words: shrinking tips the wall toward vertical (a straw you must descend straight down); growing it tips the wall toward flat (almost anything allowed).

Forecast: Which one traps the lander in a near-vertical chute?

  1. Case (a) (wide funnel). Allowed radius m. Since , deeply feasible. Why this step? As , : the cone opens flat, allowing almost any horizontal position — no protection from hills.
  2. Case (b) (narrow chute). Allowed radius m. Since , infeasible — the lander is outside a steep vertical funnel. Why this step? As , : the cone collapses to a vertical line, forcing an almost purely vertical descent.

Verify: ✔; ✔; , ✔.


Example 8 — Fuel via log-mass (Cell C8)

Forecast: More or less than 40 kg of propellant?

  1. Recall the log-mass law. From the parent note, . With constant this integrates to , where . Why this tool? The substitution turns the messy into a straight line — integration is trivial when is constant.
  2. Assemble the numbers. , and . So . Why this step? Direct substitution of the three given quantities ( from , , ) into the linear law.
  3. Undo the log. kg, because means . Propellant used kg. Why this step? The exponential recovers real mass from log-mass; subtracting gives fuel spent.

Verify: ; ; kg; burned kg ✔ (< 40, as forecast). Units: dimensionless ✔ (as must be).


Example 9 — Word problem, Falcon-9 style (Cell C9)

Forecast: Real boosters land with tiny margins — guess whether 500 m is enough.

  1. Net brake. . Why this step? Same signed-sum as C1 but Earth gravity.
  2. Stopping distance. Switching to magnitudes (, ), m, the vertical braking drop. Why this tool? Kinematics again — known speed, known brake, want distance.
  3. Feasibility. — fits comfortably. Why this step? is the height used up while stopping; means it stops above the pad.
  4. Hover check. Need ; box is . , so hover is impossible — the engine's floor exceeds gravity. Why this step? Real high-thrust boosters cannot hover; they must land in one continuous fast burn (this is why Falcon 9 does a hoverslam, never a hover).
Recall Why can't Falcon 9 hover?

Its minimum throttle acceleration () exceeds Earth gravity (), so any thrust makes it climb — it must time a single decelerating burn to arrive at zero speed exactly at the pad. ::: The engine floor is above , so hover thrust is below the throttle box.

Verify: ; m; ; hover ✔.


Example 10 — Exam twist: recognise infeasibility (Cell C10)

Forecast: Trap alert — does the burn fit in only 20 m?

  1. Stopping distance at current max brake. Net ; with , m. Why this step? The feasibility test from C2 — compute the braking drop first.
  2. Compare. infeasible. The rocket needs m to stop but has only m of height, so it is still moving fast when it reaches the pad: it crashes. Why this step? When the braking drop exceeds the altitude , no thrust profile within limits can land softly — the SOCP returns infeasible.
  3. Required max thrust. Demand the burn just fits, : . Then . Why this step? Invert the stopping-distance formula to find the minimum net brake that fits, then add gravity back to convert net acceleration into required thrust.

Verify: m (infeasible) ✔; required ; ✔.


Recall

Recall Which cell does each example cover?

C0→Ex0, C1→Ex1, C2→Ex2, C3→Ex3, C4→Ex4, C5→Ex5, C6→Ex6, C7→Ex7, C8→Ex8, C9→Ex9, C10→Ex10. ::: One example per scenario cell — the matrix is fully covered.

Sign of net accel decides brake vs fall?
⇒ can brake; ⇒ keeps falling.
Feasibility test in one line?
braking drop must be altitude .
What defines the glide-slope angle ?
the angle between the descent-cone wall and the ground; horizontal offset must be .
An initially upward — new machinery needed?
no; coast to peak, then it falls back through the start point at the same speed reversed.
Why can't a high-thrust booster hover?
min-throttle acceleration exceeds , so any thrust climbs.

Related: Tsiolkovsky Rocket Equation (the mass law), Second-Order Cone Programming (the glide-slope cone), SpaceX Falcon 9 Landing and Mars EDL (Examples 9–10), Apollo Lunar Descent Guidance (bang-bang heritage).