3.3.45 · D3Rocket Propulsion

Worked examples — Rocket staging — series staging, parallel staging

3,744 words17 min readBack to topic

This page is the practice range for Rocket staging. Every tool it uses — the Tsiolkovsky rocket equation, the structural and propellant fractions, the thrust-weighted exhaust velocity — is used exactly as the parent note built it. If a symbol shows up in an example, we re-state what it means right there before we lean on it.


The scenario matrix

We use these symbols throughout (all from the parent note):

  • — the velocity a stage adds, in metres per second (m/s).
  • exhaust velocity: how fast, in m/s, the burnt gas leaves the nozzle. Bigger = more push per kilogram of fuel.
  • — mass at the start of a burn (structure + its own fuel + everything it carries).
  • — mass at the end of a burn (start mass minus the fuel it burnt).
  • payload mass: the useful cargo (satellite, capsule) a stage must deliver; from any stage's viewpoint it also includes every stage stacked above it. Measured in kg.
  • — the natural logarithm, the function that answers " to what power gives this number?" It appears because Tsiolkovsky is .
  • (propellant fraction) and (structural fraction): of one stage's hardware mass , the share that is fuel () versus tanks/engines (), with . See Structural fraction and propellant fraction.
  • thrust: the pushing force an engine or engine group produces, in meganewtons (MN). = core thrust, = one booster's thrust.
  • specific impulse, exhaust velocity measured in seconds: with . See Specific impulse.

The two figures on this page build the two ideas that are hardest to see: how mass falls in steps (figure s01) and how the mass ratio — not raw mass — controls (figure s02). We look at them as we reach them.

Cell Scenario class Worked in
A Clean multi-stage series sum Example 1
B Parallel boosters + thrust-weighted , two phases Example 2
C Degenerate: single stage () — the "no staging" baseline Example 3
D Zero / limiting input: (perfect tanks) and (dead-weight limit) Example 4
E Series vs parallel head-to-head on the same hardware Example 5
F Word problem: "how many boosters to hit a target ?" Example 6
G Exam twist: two students, one wrong mass ratio (spot the error) Example 7
H Unit / sanity trap: in seconds vs in m/s Example 8

Every cell A–H is covered below.


Example 1 — Cell A: clean two-stage series

Forecast: Guess before computing — will it clear the ~9400 m/s needed for low orbit? Write down yes/no now.

Recall the symbols we need: is the fuel share of a stage's own hardware , so fuel ; is the structure share, so structure . / are start/end masses, is the payload (here plus stage 2 when we look at stage 1), and .

  1. Work top-down: stage 2 first. Keep everything in fractions: structure ; fuel . Why this step? Stage 2 only ever carries the payload, never stage 1's dead mass, so its numbers are self-contained. Using (not raw masses) lets us re-use this for any .

  2. Stage 2 masses. Start . End (fuel gone) . Why this step? Tsiolkovsky needs the before/after mass; keeps only the structure plus payload once the kg of fuel is spent.

  3. Stage 2 . Why this step? turns the mass ratio into how many "-foldings" of shedding happened; scales that into speed.

  4. Stage 1 must lift stage-2 hardware + payload . Structure , fuel . Why this step? From stage 1's viewpoint, "payload" is everything above it, so here kg.

  5. Stage 1 masses and . , . Why this step? We apply Tsiolkovsky to stage 1 alone, exactly as to stage 2: its start mass is the whole stack, its end mass is stage-1 structure plus everything it still carries once its own fuel is gone. The equation is stage-agnostic — same law, new masses.

  6. Add them (series 's add because each stage starts at the speed the last one left it):

Recall Verify

Answer m/s > 9400 m/s target, so it reaches orbit. Units: . ✓


Example 2 — Cell B: parallel boosters, two phases

Before any algebra, watch the mass fall in steps. Figure s01 plots vehicle mass (vertical axis, tonnes) against time (horizontal axis). The magenta line is phase 1 (core + boosters burning together, mass sliding from t to t). At separation the orange dashed cliff drops the empty booster shells ( t). The violet line is phase 2 (core alone, t). Notice the timeline is not one smooth slide — the jettison cliff is the whole point of staging.

Figure — Rocket staging — series staging, parallel staging

Forecast: Will sit closer to the boosters' or the core's ? Guess which engine group "wins."

Symbols here: is core thrust and is one booster's thrust (force, in meganewtons MN), so two boosters give ; are the core and booster exhaust velocities (m/s); is the single "effective" exhaust velocity that stands in for both engine groups burning at once.

  1. Weight each by its thrust. The boosters push much harder ( vs MN), so they dominate the average. Why this step? Momentum bookkeeping: total thrust , and each engine contributes . Dividing total by total gives a thrust-weighted mean.

  2. Plug in:

  3. Read the geometry (figure s01): the annotation "uses vbar_e" sits on the magenta phase-1 line — this governs the whole combined burn. After the orange cliff, the annotation "uses v_e core" sits on the violet line — phase 2 reverts to the core's own .

Recall Verify

m/s lies between and , nearer as forecast — boosters carry more thrust. ✓


Example 3 — Cell C: single stage (degenerate baseline)

Forecast: With less mass to carry, will single-stage beat the m/s stage 1 gave in Example 1? Guess higher or lower.

Reminder: is the stage's own hardware mass; means of is structure, so fuel ; is the cargo.

  1. Masses. Fuel , structure . , . Why this step? is Tsiolkovsky with nothing to jettison — the simplest possible case, the baseline everything else must beat.

  2. :

  3. Interpret. A single stage tops out near m/s here — nowhere near orbital . This is why staging exists: to escape the structural dead weight that caps a single stage.

Recall Verify

m/s falls far short of m/s from the two-stage rocket, confirming the staging advantage. Units m/s ✓.


Example 4 — Cell D: zero and limiting inputs

Figure s02 is the visual heart of this example. It plots (vertical, m/s) against the structural fraction (horizontal, from to ) for stage 2. Trace the violet curve left-to-right: at it hits the magenta ceiling ( m/s), the real design sits at the orange dot (, m/s), and at the curve lands on the navy dot at zero. The curve is steep — small increases in dead structure cost a lot of .

Figure — Rocket staging — series staging, parallel staging

Forecast: In case (a) does blow up to infinity or hit a ceiling? In case (b), what should be?

Reminder: never changes here (hardware size fixed at ); only moves as changes.

  1. Case (a): . Then structure , so kg and . Why this step? is the theoretical best a given tank size can do — the ceiling. It is finite because the kg payload stops from reaching (the log would diverge only if ).

  2. Case (b): . No fuel, so . Why this step? — burning nothing changes nothing. This is the degenerate zero-input check, the navy dot in figure s02.

  3. Read the trend (figure s02): as climbs from toward , slides smoothly from down to ; the real design (, orange dot) sits high on that curve at m/s. This is the visual argument for chasing low structural fraction in Payload fraction optimization.

Recall Verify

(a) , gives m/s (finite, above the m/s real value). (b) exactly since . Both limits behave. ✓


Example 5 — Cell E: series vs parallel, same hardware

Forecast: Series avoids co-lifting dead weight — bet on which wins before computing.

Reminder: for every unit here , so structure kg and fuel kg per kg unit; kg is the final cargo.

Series layout (unit is a bottom stage that drops before the core burns):

  1. Bottom stage carries (core + payload) as its payload. ; .
  2. Core stage: ; .
  3. Series total . Why this step? Each dropped stage improves the next mass ratio — the compounding series advantage.

Parallel layout (both boosters + core burn in phase 1; boosters drop; core finishes): 4. Phase 1: all engines fire. Same everywhere so . We stipulate a cross-feed design in which the core's tanks stay full until separation — the boosters feed the core so only booster propellant is drawn in phase 1. Start mass core + two boosters + payload kg. Boosters burn all their fuel kg; core burns none yet: . Why this step? The "core burns nothing in phase 1" assumption is not arbitrary — it is the explicit cross-feed rule we chose so the two layouts start the core burn with identical full tanks, making the comparison fair. (Without cross-feed the core would also drain in phase 1, giving a different but similarly computable split.) 5. Separation. The boosters are now empty shells; jettison them. Their dropped mass is kg, so kg. Why this step? Separation removes booster structure only — the fuel already left as exhaust in phase 1. This cliff is what parallel staging buys you. 6. Phase 2: core burns its full kg. Start ; final . Why this step? After jettison the vehicle is just the core carrying the payload, so Tsiolkovsky applies to the core alone with its own untouched fuel. 7. Parallel total .

Compare: Series vs parallel m/s — parallel wins here.

Recall Verify

Series vs parallel m/s. Here parallel wins because in the series case the core had to lift the second unit's full fuel through the first burn as payload, hurting its ratio; the cross-feed parallel burn drains that fuel low and early. The "series is always more efficient" slogan holds only when stages are separately optimised — this shows why you must actually compute. ✓


Example 6 — Cell F: word problem, "how many boosters?"

Forecast: Guess : is enough, or do you need several — or is it even possible?

Reminder: = liftoff mass (fixed core + per booster); = mass at booster burnout ( minus the kg of booster fuel).

  1. We need . Why this step? The core already supplies ; boosters must cover the gap.

  2. Try : ; fuel burnt ; . Too small.

  3. Try : ; fuel ; . Still short — and note it grew slowly. Diminishing returns are showing.

  4. Take the limit . Write the ratio explicitly and divide top and bottom by : Why this step? As grows, the fixed core mass becomes negligible next to the booster terms that scale with , so the ratio is governed purely by booster fuel-to-total. The terms vanish, leaving the pure booster ratio . This is the ceiling.

  5. Conclusion: since even gives only m/s, no number of these boosters reaches the target. You must raise the booster or lower their structural mass, not add more.

Recall Verify

, , limit m/s, all below the required . Correct conclusion: unachievable with these boosters. ✓


Example 7 — Cell G: exam twist, spot the wrong mass ratio

Forecast: Which student double-counts the fuel already burnt in phase 1?

Reminder: = propellant burnt in phase 1; = propellant left for phase 2; = mass at the start of phase 2 (after boosters have gone).

  1. Split the propellant. kg. Remaining kg. Why this step? Phase 2 can only burn what's left — Student A's formula pretends the kg is still onboard.

  2. Correct phase-2 masses (Student B): ; final .

  3. Student A's wrong value. Using all kg: , giving — inflated by m/s of phantom fuel. Why this step? Comparing the two numbers pins the error: the surplus is exactly the the already-spent kg would falsely provide.

Recall Verify

Correct m/s (Student B). Student A's m/s overcounts the kg already spent — exactly the "whole-propellant" error the parent note flags. ✓


Example 8 — Cell H: unit trap ( seconds vs m/s)

Forecast: What did the student forget to multiply by?

Reminder: is exhaust velocity expressed in seconds; to feed Tsiolkovsky you need in m/s, related by with . See Specific impulse.

  1. Convert to exhaust velocity. . Why this step? Tsiolkovsky wants in m/s, not in seconds; using directly gives an answer in seconds(dimensionless) — the wrong units, off by the factor .

  2. Now apply Tsiolkovsky. The mass ratio .

  3. Student's raw error. — this is exactly , i.e. the right answer shrunk by the missing . Why this step? Recognising that the wrong number equals the right one divided by confirms the single cause was the dropped factor.

Recall Verify

m/s; m/s. The bad answer confirms the missing . Units check: for . ✓


Recall Self-test

Series total from Example 1 ::: about 9640 m/s Thrust-weighted in Example 2 ::: about 2966 m/s Why does give ? ::: no fuel, so and The unit slip in Example 8 ::: forgot

Related: Tsiolkovsky rocket equation · Gravity losses · Falcon Heavy · Saturn V · Payload fraction optimization.