Exercises — Autonomous GNC for reusable rockets — SpaceX approach overview
This page is a self-test ladder. Each problem states its level, gives clean numbers, and hides a full solution inside a collapsible callout. Try it, then reveal. Everything builds on the parent overview.
Before we start, one picture fixes every sign convention on this page. Read it with the definition below — each arrow is named there.

Level 1 — Recognition
Problem L1.1
Name the three letters of GNC and, in one phrase each, the question each one answers.
Recall Solution
- Guidance — Where do I want to go? (computes the desired trajectory / target state).
- Navigation — Where am I now? (estimates position, velocity, attitude from sensors).
- Control — How do I move the actuators to close the gap? (turns commands into gimbal / fin / thruster deflections).
Problem L1.2
A booster's minimum engine thrust gives a thrust-to-weight ratio (TWR) greater than 1 when nearly empty. Which single word describes why it cannot hover?
Recall Solution
TWR > 1 means minimum upward thrust force exceeds the weight force (, so ). Even at lowest throttle the net acceleration is upward — the rocket would accelerate up, not float. Hovering needs thrust exactly equal to weight (TWR = 1), which the engine cannot go low enough to reach. Hence it must do a single timed hoverslam instead.
Level 2 — Application
Problem L2.1
A booster is falling at downward speed . The engine can produce a net upward acceleration . At what altitude must it light the engine so that velocity reaches zero exactly at the ground?
Recall Solution
Why ? This kinematic relation has no time in it — it links speed directly to the distance travelled . We want the distance over which speed drops to zero, so this is the right tool (not the time-based ). Recall = stopping distance (the vertical distance the burn covers); here the burn runs all the way to the ground, so .
Set final speed over stopping distance : Plug in: Answer: m.
The next figure shows this exact case as a speed-versus-altitude curve. The horizontal axis is altitude in metres (0 at the pad, growing to the right); the vertical axis is speed in m/s. The accent-red line is the booster's speed as it brakes.

Read it from right to left (falling means altitude decreasing): the black dot on the upper right sits at m, m/s — that is ignition. Follow the red curve down-and-left and it lands exactly on the origin, the second black dot at , — touchdown. Because the curve reaches zero speed at zero altitude and nowhere sooner, that single meeting point is a perfect hoverslam.
Problem L2.2
Same booster and burn (, ). How long does the burn last?
Recall Solution
Why the time-form now, not the distance-form? Figure s02 plotted speed against altitude — great for "where does speed hit zero" but it has no clock on it, so you cannot read seconds off it. The question asks how long, which is a clock question. The two kinematic tools split cleanly by what they leave out: has no time (use it for distances), while has no distance (use it for durations). Since we want seconds, we pick the one that actually contains .
Use with final : Answer: s. (Sanity check: average speed m/s over 6 s = 450 m = . ✓ — this bridge back to distance is exactly how the two forms agree.)
Problem L2.3
The booster mass at ignition is kg, and . Using , what thrust is required?
Recall Solution
Why ? From , solve for : the engine must first cancel gravity () and then supply the extra deceleration (). Answer: N (1044 kN).
Level 3 — Analysis
Problem L3.1
Using the numbers of L2.1 (, correct m), suppose the computer lights the engine early, at m, with the same . Where does the booster's velocity reach zero, and what physically happens next?
Recall Solution
With the same and same starting speed, the stopping distance (how far the burn takes to kill the speed) is fixed: Lighting at 600 m, the booster consumes 450 m of altitude braking and stops at m above the ground. Now it is momentarily at rest at 150 m with the engine still on and TWR > 1 → net upward acceleration → it rises back up. It cannot throttle to hover. So early ignition doesn't "add margin" — it strands the rocket in mid-air or forces a wasteful re-fall. Answer: velocity zero at 150 m altitude; then it accelerates upward (cannot hover).
Problem L3.2
Now it lights late, at m, same , same . What is the impact speed?
Recall Solution
The burn now has only a stopping distance of m available, but it needed 450 m. Use with : Answer: it hits the ground at m/s → crash. This is the razor-thin corridor: m of ignition-altitude error is the difference between rising away and slamming in at highway speed.
Problem L3.3
Explain why the IMU alone cannot navigate the whole descent, and give the growth law of a constant accelerometer bias in the position estimate. Then say what happens to the 3D position-error size if each axis has the same bias.
Recall Solution
First, notation: a bold letter like means a vector — a quantity with three components (an , a , a ), here the position in space; likewise is the acceleration vector. Bold just says "this has three numbers and a direction."
The IMU gives acceleration; position is recovered by integrating twice ( — first add up acceleration over time to get velocity, then add up velocity over time to get position).
Work one axis explicitly. Say the -accelerometer reads a fixed wrong offset (metres per second², constant). Integrate once for the velocity error: Integrate that once more for the position error: So on each axis the same algebra gives the same shape — nothing about was special, so and produce too. That is why "the argument is identical along each axis": the integration doesn't know or care which axis it runs on.
The 3D error size. If all three axes carry the same bias , the error vector is . Its length (Pythagoras in 3D) is still growing like — just times bigger than one axis alone.
Why this matters: the error grows with the square of time — small bias, long flight → huge error. So we fuse a drift-free but slow reference (GPS/radar) via a Kalman filter to bound the drift. Fast IMU + slow GPS = best of both.
Level 4 — Synthesis
Problem L4.1
A booster is at altitude m descending at m/s. The engine can deliver a net upward accel of . (a) Is it already past the point where a burn can save it? (b) What minimum would exactly stop it at the ground from here?
Recall Solution
(a) Required ignition altitude for (stopping distance ): Since the booster is at 1000 m, which is above 666.7 m, it is not past the point — it should keep falling and light later. It has margin.
(b) The minimum is the one that just barely stops it using the full 1000 m of stopping distance: Answers: (a) not past the point (h_ign ≈ 666.7 m < 1000 m); (b) minimum . Interpretation: any engine capable of can land it; a engine just lights lower and burns shorter.
Problem L4.2
For the case above, using and mass kg at ignition (), find (a) the burn duration and (b) the required thrust.
Recall Solution
(a) Ignition happens at m, speed still m/s. (b) Thrust: Answers: (a) s; (b) N (1114 kN).
Level 5 — Mastery
Problem L5.1 — Live closed-loop recompute
Real thrust isn't perfectly steady. Suppose the true burn under-performs, delivering only instead of a planned 20. The vehicle recomputes the commanded net accel every cycle from live state using . At the instant it lit (planned), it was at m/s, m. (a) What net accel does the closed-loop law demand at that instant? (b) If the engine can only reach 18, what does the guidance do, and is landing still possible? Reason it out.
Recall Solution
(a) At , : (b) The engine can only give 18, i.e. it under-brakes. So over the next cycle the vehicle sheds less speed than planned; at the new altitude the ratio climbs (speed too high for the shrinking altitude). The closed-loop law therefore demands more accel next cycle. As long as the engine's ceiling ( it can actually make, given throttle and mass) stays above the rising demand, it catches up and still nails at . If the demand ever exceeds the engine ceiling before touchdown, the case becomes the "late ignition" crash of L3.2. This is exactly why guidance is closed-loop: it re-solves each cycle instead of trusting one pre-scripted plan. For the fuel-optimal version of this recompute-under-constraints problem, SpaceX-style guidance solves a real-time convex optimization via lossless convexification, guaranteeing a global optimum in bounded time each cycle. Answer: (a) demands 20 m/s²; (b) it up-commands accel each cycle; landing survives iff engine ceiling stays above the rising demand.
Problem L5.2 — Degenerate / edge cases
Discuss what the ignition formula predicts in three limiting cases, and whether each is physical: (a) ; (b) ; (c) very large.
Recall Solution
(a) (already at rest). Substitute : . Physical meaning: if you already have zero speed you need no braking distance () — kinematically you could touch down right where you are. (Real gravity would then start pulling you down again, so you'd still need thrust to hold, but the pure "distance to kill the speed" is genuinely zero.) The formula is correct and sensible.
(b) (engine barely stronger than gravity). As shrinks toward zero from the positive side, the denominator while the numerator stays fixed, so . Physical meaning: a rocket that can barely decelerate needs an infinite runway to stop — i.e. within any real corridor it cannot stop the fall at all. This is the boundary where the engine is too weak (TWR just above 1); landing becomes impossible, and the formula correctly diverges to warn us.
(c) very large (extremely powerful burn). As , the denominator grows without bound, so . Physical meaning: an enormously powerful engine needs almost no stopping distance — you fall nearly all the way to the deck, then a violent, very-short burst stops you. Mathematically fine, but it demands near-perfect timing (a vanishingly small ignition window) and punishing g-loads, so real vehicles deliberately pick a moderate to keep both the timing corridor and the structural loads sane.
Takeaway: the formula behaves sensibly at every extreme — ; weak engine (impossible); strong engine (twitchy). No case surprises us, which is exactly why it's a trustworthy live decision rule.
The final figure plots the whole family: against the engine's for a fixed m/s. The horizontal axis is net accel in m/s², the vertical axis is ignition altitude in m, and the accent-red curve is the ignition law.

Trace the red curve: at the far left (small ) it shoots up toward infinity — that is case (b), the too-weak engine. At the far right (large ) it flattens toward zero — that is case (c), the twitchy super-strong engine. The two annotated ends are exactly the limits you reasoned about above.
Active recall
Recall One-line summary of the ladder
Everything above is one equation seen from five angles: . Recognition names it, Application plugs it, Analysis breaks it (early/late/IMU drift), Synthesis combines it with and burn time , and Mastery makes it live (closed-loop recompute) and robust (edge cases). Prerequisite tools live in Kinematics — v²=v0²+2as, Rocket Equation (Tsiolkovsky), PID Control, Thrust Vectoring (Gimbal), and Attitude Dynamics & Quaternions.