Interactive lab · projectile motion

Projectile motion: two independent axes.

Most projectile mistakes on the diagnostic come from mixing the two axes, like using the full launch speed to find the peak height, or the horizontal speed to find the fall time. Change the launch, watch the velocity components, then try problems that check for those exact mix-ups.

Model
aₓ = 0 · a_y = −g
Bench
live trajectory + vector readout
Practice
6 problem types · new numbers each time
Feedback
names the mistake · e.g. axes mixed up

Covers fall time, landing distance, peak height and time of flight. Each one starts by splitting the velocity into components.

Trajectory bench / two axes · one clock STANDBY
x
0 m
y
0 m
vₓ
11.6 m/s
v_y
13.8 m/s
range
32.6 m
peak
9.7 m

vₓ (green) stays the same because there is no horizontal force. v_y (amber) drops by 9.8 m/s every second, whatever vₓ is doing.

Predict first then test it

Two identical balls are launched from the ground at the same speed — one at 30°, one at 60°. Ignoring air resistance, which lands farther away?

Worked example one resolve, three answers

  1. 01

    Model

    A ball leaves level ground at v₀ = 20 m/s, 37° above horizontal. No air resistance, so the only force in flight is gravity: aₓ = 0, a_y = −9.8 m/s². We want air time T, range R, and peak height H.

Practice desk 0/6 solved

Numeric answers are accepted within ±2%. If your answer matches a common wrong method, the feedback names it.

A ball is launched horizontally at 24 m/s from a cliff 32 m above level ground. How long is it in the air? (g = 9.8 m/s², ignore air resistance)

next Next step

The problem ladder has harder projectile questions mixed in with other topics, so you have to recognise the setup yourself.