Time of Flight Projectile Motion Calculator
How long will your projectile stay airborne before hitting the ground?
Enter your launch conditions — speed, angle, and starting height — to find exactly how long a projectile stays in the air, how far it travels, how high it peaks, and how fast it hits the ground. Works for sports, engineering checks, and physics problems.
—
Send feedback
💡 Share your idea or report a problem
✓ Thanks! We'll take a look.
Learn more
How It Works
The formula, explained simply
Imagine throwing a ball off a bridge. The moment it leaves your hand, two completely independent things happen simultaneously: it keeps moving forward at the same horizontal speed it had when you released it, and it starts falling downward under gravity. Those two motions never interact — gravity does not slow the horizontal travel, and your throwing speed does not delay the fall. Time of flight is entirely determined by the vertical component.
The vertical motion follows a simple rule: the projectile accelerates downward at 9.81 meters per second every second it is in the air. If you launch upward at an angle, the projectile first fights gravity until it runs out of upward velocity, reaches its peak, then falls back down. The time to peak and the time falling back to ground height add up to total flight time. When you add an initial height above the ground, the projectile gets extra fall distance after returning to launch height, which extends flight time further.
The math behind this is a quadratic equation. Set up the vertical position equation — height equals initial height plus vertical velocity times time minus half of gravity times time squared — and solve for when height equals zero. The quadratic formula gives two solutions; the positive one is your time of flight. Every other output follows from that single number: multiply by horizontal velocity to get range, find the time when vertical velocity hits zero to get peak height, and reconstruct velocity components at impact to get impact speed.
When To Use This
Right tool, right situation
Use this calculator when you need a quick answer to a trajectory question and air resistance is small relative to the forces involved — low-speed launches, dense objects, or when an order-of-magnitude estimate is acceptable. Physics coursework, sports science sanity checks, gaming physics design, and amateur rocketry planning at low altitudes are all good fits.
Also appropriate when comparing trajectories: if you want to know whether angle A or angle B produces greater range given a fixed speed, the vacuum model gives the right ranking even if the absolute numbers are off. Relative comparisons are often useful even when absolute predictions are not.
Do not use this calculator as the sole reference for engineering decisions where impact location precision matters, such as artillery trajectory tables, civil engineering projectile hazard zones, or any application where air resistance, spin, wind, or altitude changes are significant. At speeds above roughly 50 m/s for light objects (baseballs, golf balls), or any speed for very low-density objects (shuttlecocks, foam balls), drag will meaningfully reduce range. In those cases, treat this result as a theoretical ceiling, not a prediction.
Common Mistakes
Why results sometimes look wrong
The most common mistake is confusing total speed with vertical velocity. People intuitively feel that a faster throw means longer air time, but time of flight depends only on the vertical component of velocity. Two throws at 30 m/s — one at 20 degrees, one at 70 degrees — travel the same horizontal distance but the steeper one stays airborne nearly three times longer.
A second frequent error is forgetting that 45 degrees only maximizes range on flat ground from ground level. As soon as you add initial height, the optimal angle drops. Launching from even 2 meters above ground pushes the optimal angle to around 44 degrees; launching from a cliff changes it dramatically. The calculator outputs the true optimal angle for your specific height.
The third mistake is applying vacuum results directly to sporting or engineering problems. A baseball pitcher throwing at 40 m/s sees roughly 15 percent less range than the vacuum prediction due to drag. A shuttlecock at the same speed might lose 50 percent or more. The calculator is accurate for physics problems and useful as an upper bound for real-world problems, but should not be used as a direct engineering specification where drag matters.
The Math
Worked examples and deeper derivation
The core equations use standard kinematic relationships under constant gravitational acceleration.
Vertical position at time t: y(t) = h0 + vy0 * t - (1/2) * g * t squared, where h0 is initial height, vy0 is vertical component of launch velocity (speed times sine of angle), and g is gravitational acceleration. Setting y(t) = 0 and applying the quadratic formula gives time of flight: t = (vy0 + sqrt(vy0 squared + 2 * g * h0)) divided by g.
Horizontal range: R = vx0 * t, where vx0 = speed times cosine of angle. Maximum height occurs when vertical velocity reaches zero: t_peak = vy0 / g, giving max height = h0 + vy0 squared / (2g). Impact speed combines both velocity components at t: impact speed = sqrt(vx0 squared + (vy0 - g * t) squared). Note that horizontal velocity never changes — only vertical velocity accelerates. Impact speed always equals launch speed when initial height is zero, because energy is conserved in the absence of air resistance.
Expert Unlock
The thing most explanations skip
The formula assumes uniform gravitational acceleration, which holds to better than 0.5 percent up to about 20 km altitude. Above that, both g and atmospheric density change enough to matter. The model also treats the Earth as flat — for ranges beyond about 50 km, Earth curvature adds measurable range for ballistic trajectories. At the other extreme, the formula breaks for very short times of flight (under about 10 milliseconds) where structural dynamics and deformation of the projectile interact with trajectory in ways the point-mass model cannot capture.
What does the time of flight result actually tell you?
Need something this doesn't cover?
Suggest a tool — we'll build it →