3.5.55 · D5Guidance, Navigation & Control (GNC)
Question bank — Autonomous GNC for reusable rockets — SpaceX approach overview
Every reveal below uses Question ::: Answer — read the left, think, then check the right.
True or false — justify
A booster can hover just above the barge to line up before touchdown.
False — a nearly-empty booster's minimum thrust exceeds its weight (TWR ), so the smallest possible push still accelerates it upward. It literally cannot balance at constant altitude, which is why it must do a timed hoverslam instead.
The hoverslam works because the engine can be throttled all the way down to zero thrust.
False — the constraint is that even the lowest usable throttle gives (TWR ). If it could throttle down to TWR it could hover; the whole problem exists precisely because it cannot.
Guidance and Control are two names for the same job.
False — Guidance decides where to go (the desired trajectory/target state), while Control decides how to move the actuators to close the gap to that trajectory. Navigation is the third: where am I now?
The Kalman filter is only needed because GPS is noisy.
False — it fuses two complementary flaws: the Kalman Filter blends a fast-but-drifting IMU with slow-but-drift-free GPS/radar, trusting each according to its uncertainty. Removing either source degrades the estimate.
Once the fuel-optimal descent trajectory is computed at engine ignition, it is followed to the ground unchanged.
False — it is recomputed many times per second (closed-loop). Winds, exact mass, and engine performance are never known exactly, so the trajectory is re-solved live from fresh state estimates.
The proportional term of a PID controller alone can eliminate a constant crosswind bias.
False — a pure proportional term needs a nonzero error to produce a correction, so it settles with a residual offset against a steady wind. The integral term accumulates that offset and drives the steady-state error to zero.
Convex optimization is used mainly because it is faster to code than PID.
False — it is used because convex problems have a guaranteed global optimum found in bounded time. That determinism is essential when a mission-critical decision must be produced every cycle; see Convex Optimization and Lossless Convexification.
Grid fins are the primary steering during the landing burn.
False — during any powered burn the engine gimbal dominates the steering torque. Grid fins provide aerodynamic steering during the atmospheric coast/descent, not when the engine is doing the work.
You could pilot the landing remotely if the video feed were fast enough.
False — even with a perfect feed, signal latency plus plasma blackout plus a ~250 ms human reaction time exceed the ~10 ms control loop the vehicle needs. The decision must be made onboard.
Spot the error
"To be safe, light the landing engine as high as possible so you have maximum braking distance."
The error: lighting early makes you reach zero velocity above the ground. Since TWR you can't then hover, so you rise again or dump fuel — the ignition altitude (with ) is a precise target, not a floor.
"The IMU integrates acceleration twice, so it alone gives us position — GPS is just a luxury."
The error: position is the double integral of acceleration, so a constant acceleration bias contributes to position — a small offset that balloons with time. GPS/radar is required to bound that drift, not as a luxury.
"The kinematic relation is used because it gives us the burn time."
The error: that relation contains no time — that is exactly why it is chosen. It links speed to distance directly, answering where speed hits zero; burn time comes separately from . See Kinematics — v²=v0²+2as.
"During the boostback burn the rocket cancels its vertical velocity to fall straight down."
The error: the boostback burn cancels or reverses horizontal velocity to aim back at the landing site. Vertical descent speed is bled off later by the entry and landing burns.
"Cold-gas thrusters are the strongest actuator, so they handle the flip and the landing."
The error: cold-gas thrusters are weak; they are used only in vacuum/coast when there is no air for fins and the engine is off. Torque authority is chosen by environment, not raw strength — gimbal for burns, fins for atmosphere.
"Because we want at , we set where is the total flight altitude."
The error: is the remaining stopping distance at the moment we evaluate it, not total altitude. The controller continuously recomputes with the current and current each cycle.
Why questions
Why can't the booster simply parachute down like earlier capsules?
A parachute gives no lateral steering precision and no way to hit a barge-sized target through wind, and a heavy booster needs enormous chutes. Propulsive landing lets the same engine that launched it also steer and brake to a pinpoint.
Why is the landing burn called a "suicide burn"?
Because there is no margin: with TWR you cannot pause to correct, so ignition must be timed so velocity hits zero exactly at zero altitude. A moment's error means stopping mid-air (then falling) or hitting the ground.
Why does the controller command rather than a fixed thrust?
Because the required deceleration is : braking harder is needed when speed is high or remaining height is small, and both change every instant. The cancels gravity so the engine's net effect equals that required value; a fixed thrust would over- or under-brake as and evolve.
Why use a quaternion for attitude instead of three angles?
Quaternions avoid the gimbal-lock singularities and discontinuities that Euler angles suffer near vertical orientations, which matters when the booster flips through large attitude changes; see Attitude Dynamics & Quaternions.
Why blend three different actuators instead of using the best one all the time?
Because each has authority only in its regime: gimbal needs the engine lit, grid fins need air, cold-gas needs neither but is weak. GNC schedules them by flight phase so some control is always available.
Why does the derivative term matter for a gimbal controller?
It responds to how fast the error is changing, damping the motion so the rocket doesn't overshoot the target attitude and oscillate. Without it, the proportional term alone tends to ring.
Edge cases
What does predict if the descent speed is zero?
It gives : with no speed to kill you never need to ignite for braking. The formula degenerates sensibly to "no burn required."
What happens to the required thrust as the remaining stopping distance with ?
The demanded thrust diverges to infinity — physically impossible. This is why ignition must happen early enough that is never squeezed toward zero while still moving fast.
What would a booster with TWR exactly be able to do that a real one cannot?
With its net acceleration , so it could truly hover, descending as slowly and gently as it liked and easing onto the pad. Real boosters sit above this hovering threshold (TWR ), which is the whole reason the precisely-timed hoverslam is forced.
If the engine's achievable suddenly drops mid-burn (underperformance), what does the closed loop do?
A smaller means the needed ignition altitude was higher than assumed, so the vehicle is now behind — it will command maximum available thrust, and if that still can't stop it in the remaining , no control law can recover. This is why margin is designed into the trajectory, not improvised.
In a perfect vacuum with the engine off, which actuator has any authority at all?
Only the cold-gas thrusters — there is no air for grid fins and no exhaust to gimbal. This is exactly the regime they exist for, such as the post-separation flip.
What if the target is directly below with zero horizontal error — is the gimbal still active?
Yes: even with zero lateral error it holds attitude against disturbances (wind gusts, thrust misalignment). A PID controller with still counters any that appears, keeping the correction ready.
At the exact instant velocity reaches zero at zero altitude, is the net acceleration zero?
No — net upward acceleration is still because TWR . That's why the engine must cut off precisely at touchdown; leaving it lit would push the booster back up.
Recall One-line summary of every trap
The recurring theme: TWR forbids hovering (so timing must be exact), the loop is closed (recomputed live, not replayed), sensors must be fused (IMU drifts), actuators are environment-scheduled, and convex optimization buys a guaranteed answer in bounded time.