Skip to content
🎯 Projectiles: Range, Maximum Height & Time of Flight Problems
🎯 Projectiles: Range, Maximum Height & Time of Flight Problems
Right — today we’re doing projectiles properly. Not the “plug formula, punch calculator, hope the examiner is kind” approach. I mean the way mechanics teachers think about it when we’re scribbling all over a board with last period on a Friday. Slow, conversational, slightly chaotic around the edges — that’s where understanding lives.
Picture throwing a ball. It arcs naturally — but the maths doesn’t follow the arc directly. We slice the motion into two films running at the same time: one horizontal, one vertical. The horizontal is calm and predictable; the vertical is fighting gravity every second. Once that picture settles in your head, a surprising amount becomes obvious.
This is really the moment projectiles stop feeling like a trick chapter and start becoming part of the A Level Maths concepts you must know for mocks, revision days, and real paper pressure. It’s not new maths — just a new way of looking.
🔙 Previous topic:
If you want to loop back first, our SUVAT Masterclass: How to Recognise the Correct Formula sets you up perfectly here because every projectile question still starts with the same SUVAT decision flow before the motion splits into horizontal and vertical parts.
📘 Where These Questions Usually Hide
Almost every exam board loves projectile questions. They look gentle, but they hide layers — angle components, symmetric motion, uneven landing heights, maximum range conditions, parametric descriptions. Half the marks go to students who draw the components before they even think about formulas.
📐 Setting Up the Classic Projectile Model
A particle is projected with speed u at angle θ above the horizontal. Find expressions for:
• Maximum height
• Time of flight
• Horizontal range
🧠 The Core Thinking Behind Projectile Motion
🔧 First Move — Splitting the Launch Speed Cleanly
Before anything else, we break the initial velocity into horizontal and vertical pieces:
Horizontal component: u cosθ
Vertical component: u sinθ
The real insight: horizontal motion cruises at constant speed; vertical motion fights gravity minute by minute. Same time, different behaviours.
We might express horizontal displacement using x = (u\cos\theta)t,
and vertical velocity via v = u\sin\theta – gt.
Those two lines alone carry most of the projectile modelling.
🚀 Maximum Height — Found the Moment Vertical Motion Stalls
At the top of the arc, vertical velocity becomes zero. That’s the key.
So vertically:
Initial velocity = u sinθ
Final velocity at top = 0
Acceleration = −g
This gives time to the top via something like t_{\text{up}} = \frac{u\sin\theta}{g}.
Maximum height then fits a clean displacement relationship:
We might write H = \frac{(u\sin\theta)^2}{2g}.
Simple, logical, unforced.
🕒 Total Flight Time — Up, Peak, and Back Down
If the projectile lands back at the same height, total time is twice the up-time:
T = \frac{2u\sin\theta}{g}.
If landing height changes, symmetry breaks — then we solve vertically with full SUVAT. No shortcuts there.
🛣️ Range — The Distance Covered While Time Ticks On
Horizontal speed stays constant, so:
Range = horizontal speed × time of flight
Which becomes:
(u cosθ) × (2u sinθ / g)
and simplifies naturally to:
We write R = \frac{u^2\sin2\theta}{g}.
Clean, elegant, everywhere in exams.
🧭 The Sweet-Spot Angle for Maximum Range
Since R depends on sin2θ, maximum range occurs when sin2θ = 1.
→ 2θ = 90° → θ = 45°.
Level ground, no drag, 45° is the sweet spot.
🔍 Quick Check — Are Your Horizontal and Vertical Stories Apart?
Horizontal is constant speed.
Vertical is acceleration.
Time is shared.
Equations are separate.
Students who separate the components cleanly often gain speed and confidence fast, and this is exactly the kind of clarity that fits the A Level Maths revision approach examiners like when they’re marking projectile questions.
⚡ Classic Mistakes That Quietly Break Projectile Solutions
- Treating horizontal motion like SUVAT even though a = 0.
- Getting signs wrong — if up is positive, gravity is negative.
- Using up-time instead of full flight time.
- Assuming symmetry when landing height changes.
- Skipping the diagram — and getting lost in direction logic.
One allowed LaTeX snippet fits neatly here: vertical modelling assumes a = -g.
🏔️ Unequal Landing Heights — When Symmetry Disappears
Here’s where exams separate method-users from memorizers.
If the landing height differs, symmetry disappears.
The vertical motion follows something like:
We might write s = (u\sin\theta)t – \tfrac{1}{2}gt^2.
This gives a quadratic in t — two times: one on the way up, one on the way down.
Range then becomes x = (u cosθ) × chosen t.
Not harder — just deeper.
🧮 Parametric View — The Cleaner Algebraic Version
Later on, we recast projectiles as parametrics:
x(t) = (u\cos\theta)t
y(t) = (u\sin\theta)t – \tfrac{1}{2}gt^2
It’s the same physics, just tidier algebra.
🌍 Real-World Link
Football crosses, basketball arcs, long jump, rugby kicks, volleys — projectile physics everywhere. A Level keeps life clean (no drag) so your intuition grows before reality messy-fies things.
🚀 Next Steps
If you want projectile problems to feel instinctive — diagram drawn, components separated, time chosen confidently — the A Level Maths Revision Course packed with exam tricks builds those habits through guided practice, repetition drills, and exam-board modelling until it feels natural rather than lucky.
📏 Recap Table
- Split velocity → u cosθ (horizontal), u sinθ (vertical)
- Max height → vertical velocity goes to zero
- Time of flight → 2 × up-time (if levels match)
- Range → horizontal speed × total flight time
- Heights differ → solve vertical displacement fully
Author Bio – S. Mahandru
I teach mechanics like a conversation — arrows everywhere, velocity split in half, gravity tapping the motion downward. Once you see projectiles as two linked films instead of one curve, you stop guessing and start modelling.
🧭 Next topic:
Projectiles questions train you to break motion into clean stages, and that same habit carries straight over into moments questions on non-uniform rods, beams and equilibrium, where everything has to be balanced carefully.
❓ Quick FAQs
Why separate horizontal and vertical motion in the first place?
Because acceleration only acts vertically — and if you mix the two directions, you completely lose that structure. The horizontal motion is a simple constant-speed model, and treating it that way reduces the mental load of the problem dramatically. Students who blend the directions often invent forces that don’t exist or try to apply SUVAT horizontally even though a = 0 there.
Separating motion also helps you keep time consistent — one t shared between two independent stories. Draw the diagram, slice velocity into components, and run each direction through its own logic. If you ever feel stuck mid-solution, it’s almost always because the components weren’t separated clearly at the start. Projectile clarity begins the moment you split the velocity arrow in two.
Do I always need sin2θ for range problems?
Not at all — sin2θ is just a shortcut that appears naturally when you’ve already multiplied (u cosθ) by (2u sinθ / g). Many students try to jump straight to sin2θ because they’ve memorised a single formula, but that often leads to misuse when the landing height is different or when the path isn’t symmetrical. The fundamentals — component splitting and time selection — matter far more.
If the question gives a non-zero landing height, sin2θ becomes irrelevant because the flight time must be found from a quadratic instead of symmetry. Think of sin2θ as a nice finishing touch, not the starting point. Its real purpose is simplification, not modelling.
Why do answers collapse halfway through a projectile problem?
Most collapses come from using the wrong time — students often use the time to reach the peak rather than the total flight time. Another common error is mixing signs: calling upward positive but then accidentally substituting g as +9.8. Direction errors are small but catastrophic. Some students also try to reuse horizontal working inside vertical equations, which instantly derails the logic because the vertical acceleration changes everything.
A quieter cause: forgetting that displacement in vertical motion is signed, so landing below the start means s is negative. Once you slow the diagram down and keep horizontal and vertical lines of thought separate, almost all those failure points disappear. Physics hasn’t gone wrong — the bookkeeping has.