Constant-Acceleration Motion
Know three of the five quantities, and the problem is already solved.
Before this Lesson
A car doing 30 mph can stop in about 60 ft. Put the same car on the same road at 60 mph, with the brakes working exactly as hard. How far now? Your gut says 120 ft. At the 120 ft mark, that car is still doing more than 40 mph.
The reason is one straight line on a velocity-time graph, the same line behind every problem in this Lesson.
One straight line, five quantities
Constant acceleration means velocity changes by the same amount every second, so the velocity-time graph is a straight line. You know how to read that graph from Position, Velocity, and Acceleration: slope is acceleration, and area is displacement. Every equation here is that sentence, written out for one line.
Five quantities describe the picture: the starting velocity , the ending velocity , the acceleration , the elapsed time , and the displacement . Read the picture three ways:
- The slope is rise over run, , which rearranges to .
- The area as a trapezoid is the average height times the width: .
- The area as a rectangle plus a triangle is plus : .
Solve the first for and put it into the second, and time disappears: . Here they all are, sorted by what each one is missing.
| Equation | Leaves out |
|---|---|
Adapted from the FE Reference Handbook, Particle Rectilinear Motion
The Handbook prints the first four, in the column headed "Constant ", with for the acceleration and for . The last one reads the picture as the rectangle minus the triangle. It isn't printed, and you'll rarely miss it.
So the method is bookkeeping. Write down what's given and what's asked. With three given and one asked, the fifth quantity is neither, so use the equation that leaves it out, and you have a single unknown. Asked for two? Take them one at a time. Why are three numbers enough? A straight segment is fixed by where it starts, how steep it is, and how long it runs. Any three of the five pin it down, and the other two are just read off.
Braking to rest, in the right units
Speedometers read mph or km/h, and accelerations come in or . Mix them and the arithmetic runs fine and the answer is nonsense, so the first move on any vehicle problem is to convert the speed. The Handbook's conversion table gives 1 mph = 88.0 ft/min, and dividing by 60 gets you to feet per second. It has no row for km/h to m/s, but that's just 1,000 m every 3,600 s.
Now brake to rest. Make the direction of travel positive, so is negative and ends at zero. The graph is a triangle: its height is the starting speed, its slope is the deceleration (call its size ), and its width is the stopping time. Put into the table:
The Handbook doesn't print these two, so they're yours to derive from its equations, which takes a line. This is braking alone, on level ground. Stopping Sight Distance adds the driver's reaction distance and the road's grade, and Newton's Second Law explains where a deceleration comes from.
Double the speed, and then what?
Back to the car from the start, and its braking triangle. Same brakes means the same slope. Now start twice as fast, and picture what that does to the triangle: how tall it gets, and how long the line takes to come down to zero at that slope.
Free fall: gravity supplies the acceleration
Let go of a ball and, ignoring air, it accelerates toward the ground at a constant . The Handbook's Constant Acceleration section says so directly: for a free-falling body, , downward. Its Fundamental Constants table lists as 32.174 ft/sec² and 9.807 m/s². Rounding to and , as this Lesson does, is close enough for the exam.
So free fall needs no new equations, only a sign convention, and you should stick to one. Take up as positive. Then for the whole flight: rising, at the top, and falling. Measure from the launch point, so a landing below it has a negative . One equation can then span the whole trip, top and all.
A ball thrown upward is a braking problem with gravity as the brakes. Its height above the launch point is a stopping distance, , reached at . Then the same straight line carries on through zero, and the ball falls. The way down mirrors the way up, so it's back at launch height at , moving at downward. And dropped means exactly .
Motion in phases
Plenty of trips have constant acceleration only in pieces. On the velocity graph each piece is a straight segment, so each one gets the table to itself. Two rules hold the pieces together: the end of one phase is the start of the next, and each phase has its own acceleration.
Take a train that starts from rest, speeds up at for 30 s, cruises for 120 s, then brakes at to a stop.
The first phase ends at 30 m/s, after 450 m. That 30 m/s is the whole cruise, which adds , and it's also where braking starts, which takes 20 s and . The trip is 4,350 m in 170 s.
A chase: same place, same time
In a chase, put both bodies on one axis and one clock, and write each one's position. They meet when their positions match. The tempting mistake is to set their speeds equal, and the picture shows what that really finds.
Until the car's speed matches the truck's, the truck is still pulling away. Equal speeds mark the moment the car is as far behind as it will ever get. Only after that does it start to close the gap.
A projectile is two problems on one clock
Roll a ball off a table at the moment you drop another from the same height. They hit the floor together. It feels as though the sideways speed ought to hold the ball up for a while, and it doesn't. Gravity pulls straight down, so it changes only the vertical velocity. With no air, nothing pushes sideways, so the horizontal velocity never changes at all.
So split the motion in two: constant velocity sideways, free fall vertically. The two share nothing but the clock. That's the entire strategy. Find the time from whichever direction has enough information, and carry it to the other.
A horizontal launch from height starts with no vertical velocity, so the fall is just a drop. The drop sets the time, and the time sets everything else. The impact velocity has both components, so its size comes from Pythagoras and its angle below the horizontal from the tangent. Here stands for the size of the downward velocity.
Launching at an angle
From Vectors and Components: a vector of size at angle above the horizontal has a horizontal component and a vertical component .
An angled launch adds one step at the start: split the launch speed into components. Use itself in either direction and you've launched a different projectile. After that, the Handbook's Projectile Motion section writes out the two problems, with positive upward:
The Handbook stops there, with no formula for height, flight time, or range, but over level ground each takes a line. At the top, , which gives the height and the time to get there. The flight time is twice that climb, and the range is the horizontal speed times the flight time, tidied up with .
For the height at a given horizontal distance, the sideways motion gives the time, , and the equation does the rest.
A target at another elevation is where those shortcuts fail, because and assume the landing is at launch height. Go back to the equation with the target's height relative to launch, positive above and negative below, and solve the quadratic for with your calculator's polynomial solver. For a target below, one root is negative and belongs before the launch. For one above, both are positive: the first on the way up, the second on the way down.
What the range formula gives away
In , the launch angle does all its work through one factor, . Two facts about sine settle most of what you'll be asked. It tops out at 90°. And it takes the same value at 60° and 120°, or at any angle and 180° minus it.