
measure position against time for a cart on a ramp with phone video, show by linearizing that distance grows with time squared, and compare the measured acceleration with g sin θ using an uncertainty estimate.
Phase 2: Investigate
Do Now. A car with its engine off rolls toward a crosswalk on a downhill street. It speeds up. If it covers 1 m in the first second, how far will it have gone after 2 s and after 3 s, if its acceleration is constant? Write your guess and your reasoning.
A cart starts from rest on a ramp. If the time doubles, the distance it has rolled…
Why a ramp? A car rolling toward a crosswalk on a downhill street speeds up even with the engine off. A ramp slows this motion down enough to measure it with a phone. Today you test a prediction: if acceleration is constant, distance from rest grows with the square of time.
Where the prediction comes from. An object starting from rest with constant acceleration a has velocity v = at. Its velocity-time graph is a straight line through the origin, and the area under it after time t is a triangle: ½(t)(at) = ½at2. So x = ½at2, and x ∝ t2. Doubling the time should give four times the distance. Tripling it should give nine times. Galileo noticed the same pattern: in equal successive time intervals an object starting from rest covers distances in the ratio 1 : 3 : 5 : 7.
Measuring time with video. A phone records a fixed number of frames per second (fps). If the cart is released at frame 0 and crosses a tape mark at frame n, then t = n/fps. At 30 fps each frame is 1/30 s = 0.033 s. Slow-motion modes (often 120 or 240 fps) shrink that step. Check the real frame rate of your file, because some phones vary it. Your timing uncertainty is about ±1 frame, which is much better than a hand stopwatch, where the reaction time of the person pressing the button is typically 0.1–0.3 s.
Worked example (illustrative data). A toy car on a 2.00 m board raised 0.15 m at one end, filmed at 30 fps:
| x (m) | frame | t (s) | t2 (s2) |
|---|---|---|---|
| 0.20 | 23 | 0.767 | 0.588 |
| 0.40 | 33 | 1.100 | 1.210 |
| 0.80 | 46 | 1.533 | 2.351 |
| 1.20 | 56 | 1.867 | 3.484 |
| 1.60 | 65 | 2.167 | 4.694 |
A graph of x against t curves upward, which is hard to test by eye. So we linearize: graph x against t2. If x = ½at2, this graph is a straight line through the origin with slope ½a.
A least-squares line through the origin gives slope 0.341 m/s2, so a = 2 × 0.341 = 0.68 m/s2. The points lie close to the line, which supports constant acceleration.
The model to compare with. On a frictionless incline at angle θ, only the component of gravity along the slope speeds the object up, so a = g sin θ. (You will derive this from forces in Unit 2.) Here sin θ = 0.15/2.00 = 0.075 (θ ≈ 4.3°), so the model predicts 9.8 × 0.075 = 0.735 m/s2. The measurement is 7.1% lower. That is a physical result, not only an error. Friction in the wheels and axles and air resistance both reduce the acceleration, and they always act in that direction. Notice the cause-and-effect link: a steeper ramp means a larger pull along the slope, and the model predicts a proportionally larger acceleration.
Misconception: a ball is not a cart. A solid ball rolling without slipping has to spin up as well as speed up, so its acceleration is only (5/7)g sin θ, about 0.525 m/s2 on this ramp. Use a wheeled cart or toy car if you want to test g sin θ, or state the ball model if you use a ball.
Uncertainty. One frame is 0.033 s. At the first mark (0.767 s) that is about 4% of the time, but at the last mark only about 1.5%. That is why the longest distances carry the most reliable information. Report your acceleration with an uncertainty range, and repeat each run at least three times.
Question. Does a cart released from rest on a ramp travel a distance proportional to the square of the elapsed time, and how does its measured acceleration compare with the model a = g sin θ?
Materials. A smooth board, shelf or two taped meter sticks about 1.5–2.0 m long; books or blocks to raise one end 10–20 cm; a low-friction toy car or dynamics cart; masking tape, a marker and a meter stick; a phone or tablet camera and any free video player that steps frame by frame; a folded towel as a soft stop; a stopwatch as a backup timer.
| Mark x (m) | Frame, run 1 | Frame, run 2 | Frame, run 3 | Mean t (s) | t2 (s2) |
|---|---|---|---|---|---|
| 0.20 | |||||
| 0.40 | |||||
| 0.80 | |||||
| 1.20 | |||||
| 1.60 |
No equipment? Use these two illustrative run sets (teaching data, not real measurements), both on a 2.00 m board at 30 fps with the same marks. Set 1, h = 0.15 m: frames 23, 33, 46, 56, 65. Set 2, h = 0.30 m: frames 16, 23, 32, 40, 46. You should get about 0.68 and 1.36 m/s2, against models of 0.735 and 1.47 m/s2. Or use the PhET Projectile Motion sim with air resistance off and launch speed 0 m/s, dropping from 2, 4, 6, 8 and 10 m: the steepest possible ramp, θ = 90°, where the model is a = g.
Answer as your team collects data. Use the worked example to check your method.
Write the lab analysis in your Design Notebook.
Write your lab analysis: state your claim about whether x ∝ t2, give your measured a with an uncertainty range, compare it with g sin θ as a percent difference, and explain two sources of error and which direction each pushes your result. Did doubling h double the acceleration? Include both graphs.
We measured a real acceleration and tested a model. Next, we use the constant-acceleration equations to argue about stopping distance.
Exit ticket: your measured acceleration was 6% below g sin θ. Explain why that is a physical result and not just a mistake.
Timing: Poly ran this lab as 2 × 50 min. Run it over two periods: period 1 for setup and filming, period 2 for frame counting, graphs and the analysis.
Materials: per team: a 1.5–2.0 m smooth board, books, a toy car or dynamics cart, tape, meter stick, a phone with frame-step playback, a towel, goggles. A free spreadsheet for the fit.
Listen for: fitting x against t with a straight line; using a ball and comparing with g sin θ; treating the 7% gap as “human error”.
Support / stretch: pre-fill the t and t2 columns for one mark. Stretch: estimate the friction “loss” as an effective deceleration (model − measured) and compare it across two heights.
Reading: OpenStax Physics (high school), chapter 2; OpenStax College Physics 2e, chapter 2.