3.5.46 · D3Guidance, Navigation & Control (GNC)

Worked examples — Reaction control system — thruster selection, plume impingement limits

3,164 words14 min readBack to topic

This page is the hands-on lab for the parent topic. We march through a matrix of every case class the topic can throw at you — signs, degenerate geometries, limiting distances, a real docking word problem, and an exam-style twist — and solve each one from scratch.

Before line one, four plain-word reminders so no symbol arrives unearned:

If any of or "" feels shaky, the parent note builds them; here we only use them.


The scenario matrix

Every worked example below is tagged with the cell it fills. Together they cover the whole table.

Cell Case class What makes it tricky Example
A Pure torque, single axis signs of the cross product Ex 1
B Off-CoM single thruster torque and unwanted drift Ex 2
C Quadrant sweep of which sign of per quadrant Ex 3
C0 Boundary: (on the -axis) force line through CoM ⇒ zero roll Ex 3b
D Degenerate: zero torque (force through CoM) Ex 4
E Plume falloff, on-axis worst case limiting behaviour Ex 5
F Plume off-axis, when a big- plume becomes safe Ex 6
G Real-world word problem: docking inhibit a thruster, re-allocate Ex 7
H Limiting values: , pressure Ex 8
I Exam twist: force + torque both commanded over-determined mini-allocation Ex 9

Ex 1 — Pure roll couple (Cell A)

Forecast: guess before computing — will the ship drift? Which way does it spin (about or )?

Figure — Reaction control system — thruster selection, plume impingement limits
Read the figure: the two orange arrows are the force vectors (pointing ) and (pointing ); notice they are equal length and opposite, so tip-to-tail they cancel. The purple curved arrow is the resulting spin about the -axis (into the page). The two teal squares are the thruster mounts at .

  1. Build each force vector. Using : and . Why this step? Torque needs the vector force, not just the magnitude, so we assemble first.

  2. Net force. Add the two force vectors. Why this step? A couple must have zero net force or the ship translates while it rotates. This matches the two opposite orange arrows cancelling in the figure.

  3. Torque of thruster 1. Use . Why this step? The cross product picks out the twisting part; the third component is the roll about . Sign is negative — thumb points into the page (the purple arrow).

  4. Torque of thruster 2. Why this step? We must check the second thruster twists the same way, else torques cancel like the forces did.

  5. Add. N·m. Why this step? Torques of a proper couple add; that's the whole point of a couple.

Verify: magnitude N·m ✓, and ✓. Units: N·m (force × lever). This is the parent note's "ideal attitude control": spin with zero drift.


Ex 2 — Single off-CoM thruster: torque and drift (Cell B)

Forecast: the parent's "steel-manned mistake" says one thruster is never pure torque. Predict the net force before you read on.

  1. Build the force vector. N — nonzero. Why this step? Nothing cancels it, so Newton's second law says the CoM accelerates: drift.

  2. Torque. N·m. Why this step? Confirms we still get a twist, so this jet does both jobs at once.

Verify: ✓. Compared to Ex 1 (couple), here — this is exactly the "one thruster is not a pure torque" trap. Fix: add an opposing jet to kill the N.


Ex 3 — Quadrant sweep: sign of everywhere (Cell C)

Forecast: the parent said tan/quadrant fixes matter because a formula can repeat. Here the sign of the torque flips with the quadrant. Guess which corners give negative .

Figure — Reaction control system — thruster selection, plume impingement limits
Read the figure: each coloured square is a thruster mount in one quadrant; every arrow points the same way (), because the force direction is fixed. The colour tells the sign of the resulting roll — orange squares (top half) give , teal squares (bottom half) give . Slide your eye left/right and nothing changes; slide up/down and the sign flips — that is the visual proof that only matters.

Start from the general force vector , so and . For the -component of the cross product is: In our scenario and , so the first term dies and this collapses to Why this step? We keep the general two-term formula visible, then substitute so the reader sees exactly why only the term survives: depends only on , the lever arm perpendicular to the -force.

  1. Q I : (clockwise, into page).
  2. Q II : same sign! Why? ignores ; both top corners give .
  3. Q III : (counter-clockwise).
  4. Q IV : — same as Q III.

Verify: top half () ⇒ negative roll, bottom half () ⇒ positive roll. The position never mattered because the force is along . This is why designers place roll jets far off-axis in for maximum .


Ex 3b — The boundary : on the -axis (Cell C0)

Forecast: Ex 3 said should give zero roll. Confirm it, and say why geometrically.

  1. Apply the same formula. . Why this step? This is the boundary case the quadrant sweep skipped over; it's where the sign of switches from (above) to (below), so it must pass through zero.

  2. Full cross product to be sure. . Why this step? and are parallel here (both along ), so the force line runs straight through the CoM — no lever arm, no roll.

Verify: ✓, and the full vector is ✓. Physically the jet just pushes the ship straight along with zero roll — the same "force through CoM" idea as Ex 4, now sitting exactly on the quadrant boundary. This completes every cell of the quadrant discussion: top, bottom, and the dividing line.


Ex 4 — Degenerate case: force through the CoM (Cell D)

Forecast: the lever arm and the force are on the same line. What must the torque be?

  1. Build the force vector, then cross. . Why this step? The cross product of two parallel (or anti-parallel) vectors is zero — geometrically the parallelogram they span has zero area.

  2. Interpret. Pure translation: N, no spin. Why this step? This is the parent's rule "force through CoM ⇒ zero torque, pure translation."

Verify: with ✓. Degenerate cell confirmed: this jet is a pure translator, useless for attitude.


Ex 5 — Plume falloff: on-axis worst case (Cell E)

Forecast: doubling the distance — does the pressure halve, or drop by four?

  1. On-axis shape factor. . Why this step? Dead-centre is the worst case — we always test the constraint at first.

  2. At m. Pa. Why this step? Plug the shell-conservation law; number density thins as the same gas crosses ever-bigger spheres.

  3. At m. Pa. Why this step? Confirms the quadratic drop.

Verify: ratio ✓ — doubling distance quarters the pressure, the signature of . (See Rarefied Gas Dynamics / Plume Modeling for the shell derivation.)


Ex 6 — Off-axis plume: when a tight plume becomes safe (Cell F)

Forecast: a tighter plume () is more focused on axis — so off-axis it should be weaker. Predict which keeps the panel safe.

  1. Base on-axis value at . From Ex 5, Pa before the angle factor. Why this step? Separate the distance part from the angle part so we vary only .

  2. : . Pa violation. Why this step? A broad plume still dumps lots of gas at .

  3. : . Pa → still violation (barely). Why this step? Even a tight plume isn't enough at just m; you'd need more angle or distance.

  4. How far off-axis for to be safe? Solve . Why this step? This is the keep-out half-angle for the tight plume — anything beyond is allowed.

Verify: , and Pa ✓ (just meets the limit). So bigger shrinks the danger cone but doesn't zero it.


Ex 7 — Docking word problem: inhibit then re-allocate (Cell G)

Forecast: from Ex 5 you already know at . Guess whether the forward jet passes.

  1. Check the forward jet. Pa. Why this step? On-axis worst case at the exact target distance.

  2. Compare to limit. inhibit the forward jet (). Why this step? Hardware safety outranks fuel; the parent's keep-out rule forbids this firing.

  3. Set up the re-allocation. Use two canted jets, each pointing off , one canted toward and one toward (so their plume centrelines sweep past the target). Each thrust has an along- part and a sideways part . Summing the pair: Why this step? We deliberately choose a symmetric pair so the two lateral components are equal and opposite — they cancel, leaving only the commanded push. This kills any unwanted drift, exactly like the couple in Ex 1 cancels net force.

  4. Solve for the per-jet thrust. Set the along- sum equal to the command: Why this step? Only the -projection does useful work toward the N command, so we divide it out to recover the magnitude each jet must fire. This is the solve over the remaining feasible thrusters (see Control Allocation & Pseudo-inverse).

  5. Check the canted-jet plume at the target. The target lies at angle off each canted jet's centreline, still at m. So Why this step? "Missing the target" must be proven, not assumed — we compute the actual impingement pressure at the off-axis angle.

  6. Compare to limit. safe ✓. Why this step? Now the re-allocation is legitimate: both canted plumes stay under the Pa target limit.

  7. Propellant penalty. Total thrust used N vs the ideal N. Penalty more. Why this step? Quantifies the cost of safety — the canted jets waste effort sideways.

Verify: along- force N ✓; sideways ✓; canted plume pressure Pa Pa ✓. Safety achieved, fuel penalty accepted.


Ex 8 — Limiting values: pressure vanishes (Cell H)

Forecast: both should send the pressure toward zero — but for different geometric reasons.

  1. (a) . . Why this step? At the surface is on the plume's edge/back — no gas travels sideways in this idealized cone.

  2. Numeric near-limit. At : , , so Pa — effectively nothing. Why this step? Shows the approach is smooth and fast (fourth power crushes small cosines).

  3. (b) . . Why this step? Infinitely far, the same gas is spread over an infinite sphere — density . This is why far targets are automatically safe.

Verify: ✓ and ✓. Both degenerate limits confirm the constraint is only ever binding close and on-axis — precisely the docking regime of Ex 7.


Ex 9 — Exam twist: force and torque both commanded (Cell I)

Forecast: a couple gives torque with zero force; a common push gives force with zero torque. We need a mix. Guess whether both stay non-negative.

  1. Write the two allocation equations. Each force vector is . The net force along is ; the roll of each is (from the rule of Ex 3, where and ). So: Why this step? This is the parent's written out for the small system — two equations, two unknowns, so it's exactly determined. (I use — the -components of — to stay consistent with the bold-vector names.)

  2. Solve. From and , add the equations: , then . Why this step? Elementary elimination; the influence matrix is invertible here, so there is exactly one solution.

  3. Feasibility check. and ✓. Why this step? The one-sided constraint () matters — a jet can't suck. Had a value gone negative we would have had to fire the opposite jet instead; here both are physical, so the command is directly achievable.

  4. Interpret. The solution is a common push of worth ... more precisely, decompose it: the shared part N on both jets is a pure N push with zero torque; the extra N on jet 2 alone supplies the N·m roll (and the remaining N of push). Force and torque both delivered by one asymmetric firing. Why this step? Seeing the answer as "symmetric push + asymmetric twist" connects it back to Ex 1 (the couple) and Ex 2 (the single off-CoM jet) — this exam twist is just those two building blocks superposed.

Verify: net force N ✓; net torque N·m ✓. Both magnitudes non-negative ✓. This ties directly to Attitude Dynamics — Euler's Equations (the N·m torque feeds ) and Rocket Equation & Specific Impulse (the total N sets the propellant mass rate).


Recall Self-test

Q: In Ex 3, why does the -position of the thruster not affect ? ::: Because the force is along (so ); only the perpendicular lever arm produces roll (). Q: In Ex 7, what mathematically forces the fuel penalty? ::: The canted jets waste thrust in their sideways components; only of each goes toward the commanded axis. Q: Why is the plume constraint only ever binding close and on-axis? ::: Ex 8 — pressure as (spread over huge spheres) and as ().