Projectile Motion Without Memorising

🧠 Projectile Motion Without Memorising: The 4-Point Framework

Projectiles look dramatic in exam questions — curved paths, angles everywhere, velocities splitting into components like someone tipped a physics drawer over. That’s usually where panic starts.

But once you stop trying to memorise formulas and instead run one reliable structure, the entire topic settles. That’s what we’re doing today: one framework, four moves, usable on every projectile question.

Think of this as a mental script you can run even with shaky hands in an exam hall. No panic. No blank moments. Just a process you trust. And yes — one diagram ends up doing most of the heavy lifting.

If you’ve just come off kinematics or forces, this is often where the A Level Maths methods examiners expect start knitting together, and the algebra feels lighter once the picture takes the load.

We’re building habit today, not memory.

🔙 Previous topic:

If friction felt manageable once you reduced it to just three clear cases, projectile motion works the same way — strip away the surface detail and you’re left with a small number of rules that run every question.

🧭 Where examiners like to test this

Projectile questions tend to appear early in Mechanics papers, often before friction or connected particles. The styles vary, but the underlying structure doesn’t.

Common patterns include:

launch at an angle → find time or range
horizontal launch → find height or impact speed
showing symmetry using vertical motion
finding the angle needed to hit a target
mid-flight interception (walls, platforms, roofs)
checking whether a path clears an obstacle

They look different. They feel different. But they’re all clones wearing new clothes. Every one can be solved with the same cycle:

Split → SUVAT → time link → target variable

Once that becomes automatic, difficulty drops sharply.

📦 Quick model build

One line. One rule. Everything else follows.

For projectiles, the key idea is that
$\text{horizontal and vertical motions are independent}$ .

That gives you:

horizontal → constant velocity
vertical → constant acceleration due to gravity

If you forget everything else, remember that sentence. It builds the whole topic.

🧲 Let’s break this apart slowly

🧩 Step 1 — Split velocity into components

If the projectile is launched with speed $u$ at angle $\theta$ :

Horizontal component: $u\cos\theta$
Vertical component: $u\sin\theta$

There are no shortcuts here. If you skip this step, you’re trying to solve two problems at once — and that’s where mistakes creep in.

A small verbal hook that helps:

horizontal = adjacent → cosine
vertical = opposite → sine

Say it quietly if you need to. Memory sticks better to sound than silence.

🧷 Step 2 — SUVAT lives in the vertical world only

This is one of the most common exam traps.

Horizontally, there is no acceleration. So no SUVAT. Just constant speed.

That gives:

Horizontal displacement:
For example, $x = (u\cos\theta)t$

Vertically, gravity acts constantly downward:

Vertical displacement:
For example, $y = (u\sin\theta)t – \frac{1}{2}gt^2$
Vertical velocity:
For example, $v_y = u\sin\theta – gt$

Horizontal thinking is straight-line logic. Vertical thinking is curved, time-dependent logic. Keep them separate early — mix them later.

🧲 Step 3 — Time is the bridge

This is the step that feels like magic when it clicks.

You almost never solve horizontal and vertical independently to the end. Instead:

use vertical motion to find time
substitute that time into horizontal motion

Examples where this wins immediately:

finding range
finding where a projectile lands
finding where two projectiles meet
showing symmetry
checking obstacle clearance

If you’re stuck, pause and ask: can I find t first?
Nine times out of ten, that’s the unlock..

🧿 Step 4 — Decide what the question actually wants

Projectile questions don’t want everything. They want one thing.

Usually it’s one of:

time of flight
maximum height
range
impact speed
impact angle

Pick the target early. Aim your algebra at that target only.

For example:

want range → time first
want height → vertical only
want impact speed → combine final components using
$v = \sqrt{v_x^2 + v_y^2}$

Half of good exam technique is ignoring things that don’t help.

🪢 Mid-body reality check

If this already feels calmer than the textbook approach, good — that’s the point. This is A Level Maths revision done properly, diagram-first and symbol-second, so the structure carries the thinking.

Try five small projectile questions — three minutes each. The framework becomes habit, not something you consciously remember.

🪄 A worked logical example (no numbers needed)

Suppose a projectile is launched with speed $u$ at angle $\theta$ .

To find time of flight:

At maximum height, vertical velocity is zero.
So we have $u\sin\theta – gt = 0$ .
This gives $t_{\text{up}} = \frac{u\sin\theta}{g}$ .
Total time is double this.

To find range:

Horizontal speed is constant, so
range = horizontal speed × total time.
This leads to
$\frac{u^2\sin(2\theta)}{g}$ .

Notice what just happened. We reached the famous formula without memorising it — just by following the framework.

⚙️ Variant 1 — Horizontal launch

Here the angle is zero, so there’s no initial vertical velocity.

That gives:

Horizontal: for example, $x = ut$
Vertical: for example, $y = -\frac{1}{2}gt^2$

The object falls like a dropped weight, but drifts sideways.
Classic modelling question: “a stone rolls off a cliff”.

Vertical gives the time. Horizontal uses it. End of story.

🧲 Variant 2 — Finding the launch angle

These look intimidating, but they follow the same loop.

Typical process:

find time from horizontal motion
substitute into vertical equation
solve for $\theta$

Often two angles work — a high lob and a low skim. That’s not a trick. That’s physics being honest.

🧿 Variant 3 — Clearing an obstacle

A favourite examiner style.

Method:

find time when projectile is horizontally level with the obstacle
substitute into vertical equation
compare height with obstacle height

No memorisation. Just cycle the framework again.

🧲 Velocity at impact (the sleeper topic)

At impact:

horizontal velocity remains $u\cos\theta$
vertical velocity becomes $u\sin\theta – gT$

Final speed uses Pythagoras:
$v = \sqrt{v_x^2 + v_y^2}$

Direction comes from:
$\tan\phi = \frac{|v_y|}{v_x}$

One triangle. Two components. Nothing exotic.

❗ Where marks fall apart

not splitting motion early
using SUVAT horizontally
forgetting gravity’s sign
solving both dimensions separately
over-deriving instead of targeting
panicking when no formula is obvious

When the framework is automatic, these disappear.

🌍 Why this matters beyond exams

Football arcs, fireworks, hosepipes, long-jump trajectories — all projectiles. You’re learning to see structure in motion, not just answer questions.

🚀 Next step forward

If you want projectile motion to feel instinctive rather than technical, the structured A Level Maths Revision Course drills angle launches, obstacle problems, and mid-flight intercepts until your diagram does the thinking for you.

Framework → habit → speed.

📏 Recap table

Split motion into x and y
Use SUVAT vertically only
Let time connect dimensions
Solve for the target, not everything

Stick this near your desk. It replaces pages of notes.

Author Bio – S. Mahandru

A Level Maths teacher, long-time Mechanics specialist, and firm believer that maths becomes easier when you stop memorising results and start modelling situations properly.

🧭 Next topic:

Once projectile motion feels secure without relying on memorised formulas, the next step is to generalise that reasoning to all constant-acceleration problems, using the kinematics motion equations as a structured framework that examiners expect to see applied confidently across mechanics questions.

❓ FAQ — 3 Quick Clears

🤔 Do I need to memorise the range formula?

No — and in many cases, memorising it actually causes problems. Students often misapply it to situations where the projectile doesn’t land at the same height or where the launch isn’t symmetrical. The four-step framework works in every situation, not just ideal ones.

If you trust the process, you can re-derive the range in under half a minute, even under pressure. That’s far more reliable than hoping a memorised formula fits the situation.

🧠 Why can’t I use SUVAT horizontally?

Because SUVAT assumes constant acceleration — and horizontally, there isn’t any. Horizontal motion is constant speed, not accelerated motion.

Using SUVAT sideways often gives answers that look algebraically neat but are physically wrong. Keeping SUVAT strictly vertical prevents a whole class of silent errors that cost method marks without obvious warning.

🧮 Is the projectile path always symmetrical?

Only if the projectile lands at the same height it was launched from. In that case, time up equals time down and speed magnitudes match.

If it lands higher or lower, symmetry breaks — but the framework still works unchanged. That’s another reason the structure beats memorisation: it adapts automatically.

Projectile Motion Without Memorising