3.4.4 · D5Rocket Flight Mechanics

Question bank — Equations of motion — 3DOF point mass (trajectory analysis)

1,781 words8 min readBack to topic

Before we start, one picture we'll refer to repeatedly — the velocity frame where every force gets split into a piece along the velocity arrow and a piece across it.

Figure — Equations of motion — 3DOF point mass (trajectory analysis)

The arrow is . "Along" () changes the arrow's length (speed). "Across" () changes its direction (turns it). Weight points straight down and splits into along and across. Keep this in view.


True or false — justify

Cover the answer, decide true/false, then say why.

"3DOF" means the rocket moves in three spatial dimensions .
False — the "3" counts degrees of freedom of translation (in the planar model: , , and position). It is about how many independent motions we track, not the number of spatial axes; here it's a 2D vertical plane.
In the tangential equation, weight's contribution is .
True — is measured from the horizontal, so the piece of "straight down" that lies along the velocity is ; at vertical flight () it becomes full weight, which is correct.
If thrust is exactly along the velocity and there is no lift, gravity is the only thing that can turn the trajectory.
True — ; with and contributing nothing across , only remains to bend the path. This is precisely a Gravity Turn Trajectory.
A rocket flying perfectly vertically () can still have its flight-path angle change on its own.
False — . With zero across-component of weight, a vertical path stays vertical; it only turns if a sideways force (lift or off-axis thrust) is added.
Increasing speed makes the trajectory bend faster.
False — has in the denominator, so faster flight bends more slowly. A fast rocket resists gravity's turning; a slow one is whipped over quickly.
At the very top of a coasting arc (), gravity does nothing to the speed.
True — the along-component is , so gravity neither speeds up nor slows the rocket at that instant; it acts entirely across the path (maximal turning, ).
The mass cancels out of all four trajectory equations.
False — it cancels from the shape equations (, , ) but not from , where the thrust-and-drag term depends on . Heavier vehicle, smaller acceleration.
If drag exceeds thrust , the rocket immediately starts falling.
False — only makes possibly negative (slowing down). "Falling" is about direction (), which is governed by the separate equation; a slowing rocket can still be climbing.

Spot the error

Each item contains a mistaken statement or step. Name the flaw and correct it.

", because cosine handles the along-track direction like in projectile motion."
The error is : weight's along-velocity piece is , not . Sanity check at — all weight should oppose the climb, and gives that; would wrongly say gravity is irrelevant when going straight up.
"Since Earth rotates, I'll add Coriolis and centrifugal terms to my flat-Earth planar 3DOF."
Those fictitious forces belong only to a rotating round-Earth model. In a flat-Earth planar analysis the frame is (approximately) inertial and non-rotating, so those terms are absent. Mixing models double-counts effects.
"Thrust always points straight up, so I'll put in the equation."
The kinematic equations , contain no forces at all — they only convert speed and direction into position rates. Thrust enters via (which changes ), never directly into .
"I'll integrate treating as constant since it's 'the rocket's mass'."
Propellant burns, so and shrinks continuously. Holding it constant underestimates late-flight acceleration — the same thrust on a lighter vehicle gives much larger near burnout.
" came out negative, so I must have a sign mistake — the rocket is climbing, angles should grow."
Negative is correct and expected: gravity's across-component always curves the velocity arrow downward, decreasing over time. Climbing (positive ) and a decreasing flight-path angle coexist happily.
"For a gravity turn I need a control system to command the pitch-over the whole way."
The whole point of a Gravity Turn Trajectory is that after a tiny initial pitch-over, gravity alone rotates toward horizontal via — no continuous control effort, hence minimal steering losses.
"Drag is ."
Missing the factor : . The half comes from the dynamic-pressure definition ; see Drag and Atmospheric Models.

Why questions

Explain the reasoning, not just the fact.

Why do we resolve forces in the velocity frame rather than the ground frame?
Because a velocity vector has exactly two independent things to change — its length and its direction — and the velocity frame splits force cleanly into one piece per job (along = length, across = direction), turning one vector equation into two decoupled scalar ones. See Flight-Path Angle and Velocity Frame.
Why does appear in the speed equation but in the turning equation?
is measured from horizontal, and weight points down. The angle between "down" and "backward along " makes the along-piece ; the perpendicular piece is what's left, . "S-along, C-across."
Why is the perpendicular acceleration written as ?
Turning the velocity vector at rate while it has length is exactly circular-motion geometry: the tip sweeps sideways at speed , so the across-acceleration is and the across-force is .
Why can we ignore rotational (attitude) dynamics and still get a good trajectory?
Range, altitude, and burnout speed depend only on the motion of the centre of mass (translation). Rotation matters for pointing and stability — that's when you upgrade to 6DOF Rigid-Body Dynamics.
Why must these four/five ODEs be solved numerically rather than by a neat formula?
They are coupled and nonlinear depends on (and on ), divides by , changes in time — so no closed form exists in general; we step them forward with a scheme like Numerical Integration of Trajectories (RK4).
Why does the vertical-flight case connect to the Tsiolkovsky equation?
At with no drag, , and integrating with reproduces the ideal velocity gain minus a gravity-loss term — the regime of the Tsiolkovsky Rocket Equation.
Why does the same thrust give ever-larger acceleration as the flight proceeds?
In , mass shrinks as propellant burns. Dividing a roughly steady thrust by a smaller mass yields a growing acceleration — burnout acceleration is dramatically higher than liftoff.

Edge cases

The scenarios that break lazy formulas — state what actually happens.

(rocket momentarily at rest, e.g. apex of a vertical hop): what happens to ?
It blows up (division by zero) — the model of "turning the velocity arrow" is undefined when there is no arrow. Physically the direction is momentarily ill-posed; near zero speed one switches to tracking velocity components directly, not .
(level flight): what do the along/across weight pieces become?
Along-piece (gravity doesn't slow you), across-piece (full weight bends the path down at maximum rate ). Level flight is where gravity turns you hardest.
(straight-down dive): sign of and gravity's effect on speed?
(descending), and so — gravity now adds to speed. Signs of automatically carry the direction; no special-casing needed.
and (pure coast in vacuum): what shape does the trajectory take?
The equations reduce to , , , — exactly a projectile parabola. The 3DOF set contains free-fall as a limiting case.
large enough to make : is that allowed?
Yes — if lift exceeds , then and the path curves upward. Nothing in the model forbids it; it's how a winged vehicle pulls up. Ballistic rockets just usually have .
Drag as : does drag vanish, and why does that matter at liftoff?
Yes — as , so at the instant of liftoff drag is negligible and . Drag only becomes important once speed builds; see Drag and Atmospheric Models.
High altitude where : which term in disappears and what remains?
Air density makes , so — the vacuum tangential equation. This is why upper-stage burns are so efficient: no atmospheric drag loss.
Recall One-line self-test

Cover everything and answer aloud: which equation changes speed, which changes direction, and which two change position — and which single trig function ( or ) of sits in each? Answer ::: Speed: with . Direction: with . Position: , .


Connections