
specify the criteria and constraints for a yellow-light duration or school-zone speed limit, use a stopping-distance model to set a design value, and defend it with a sensitivity analysis.
Phase 5: Prove It
Do Now. A light turns yellow as you approach at 35 mph. Too far back to go through, too close to stop: what is that zone called, and how can signal timing remove it?
Using y = tr + v/(2a) with tr = 1.0 s and a = 3.0 m/s2, what yellow duration does the model give for a 45 mph approach?
The engineering problem. When a signal turns yellow, a driver approaching at speed must either stop comfortably before the line or continue through before the light turns red. Engineers choose the yellow change interval so that every driver has one safe choice. Your task is to specify a design value, either a yellow duration or a school-zone speed limit, with explicit criteria (what counts as success) and constraints (limits you must work within). That is the first step of engineering design (HS-ETS1-1).
A kinematic model of the yellow light. A driver who is just far enough back to stop comfortably needs time to react and then time to brake. The design time is the reaction time plus the time to cover the braking distance at the average speed v/2:
y = tr + v/(2a)
The widely used Institute of Transportation Engineers form of this model takes tr = 1.0 s and a comfortable deceleration of 10 ft/s2 (about 3.0 m/s2) on level ground. With those values:
| Approach speed (mph) | v (m/s) | Model yellow y (s) | Comfortable stopping distance (m) |
|---|---|---|---|
| 25 | 11.2 | 2.86 | 32 |
| 35 | 15.6 | 3.61 | 56 |
| 45 | 20.1 | 4.35 | 88 |
| 55 | 24.6 | 5.10 | 125 |
At 35 mph: y = 1.0 + 15.65/(2 × 3.0) = 3.61 s. At 25 mph the model gives 2.86 s, which is below the federal MUTCD guidance that yellow intervals be about 3 to 6 seconds. That constraint wins, so the design value is 3.0 s. A good report shows when a constraint, not the model, sets the answer.
Option B: a school-zone speed limit. Suppose a driver can first see a mid-block crosswalk from 30 m away (illustrative sight distance), with tr = 1.5 s and a = 5.0 m/s2 on damp pavement (illustrative). The criterion is that stopping distance must not exceed sight distance: v2/(2a) + trv = 30, or 0.1v2 + 1.5v − 30 = 0. The quadratic formula gives v = 11.37 m/s = 25.4 mph, so a 25 mph limit meets the criterion here, with little margin.
Trade-offs and sensitivity. Every design balances competing goals. A longer yellow reduces red-light running but lengthens every signal cycle. A lower limit shortens stopping distance but slows traffic. Test your design by changing one assumption at a time (reaction time, pavement, approach speed) and report how much the answer moves. State which assumptions are illustrative and which come from a published source.
Check your method before you draft.
Draft, review and revise across the three sessions.
Peer review: recompute your partner's design value, check units and sources, and test one assumption. Write two specific notes.
Final: submit your 1,000–1,400 word report with the model, calculations, a sensitivity graph, the comparison with published guidance and a trade-offs section, then present or record your five-minute defense.
Task: Specify a design value for one traffic-safety question for the city’s school-safety team. Build a stopping-distance model from the constant-acceleration equations, state every assumption with its source or label it illustrative, compute your design value, and graph how it changes with one assumption (reaction time, deceleration or speed). Compare your value with published guidance: the federal MUTCD range of about 3 to 6 seconds for yellow intervals, and the stopping sight distances in a national highway design reference such as AASHTO’s A Policy on Geometric Design of Highways and Streets. Safety: never collect data by standing in or near traffic.
Choose one. All three earn full credit and are the same difficulty.
Option A — your own site. Pick a signalized intersection or a school-zone crosswalk on a road you know. Read the posted speed from the sign, say whether the approach is level, uphill or downhill, and get the sight distance either by pacing it on the sidewalk or from the scale bar on any free online map. Set the yellow duration or the speed limit for that site.
Option B — the three sites in this lesson. These are illustrative sites written for this task, not surveys of real intersections.
| Site | Design question | Approach speed | Sight distance | tr | a |
|---|---|---|---|---|---|
| 1. Mid-block school crosswalk, flat residential street | Speed limit | 30 mph now | 30 m (parked cars block the view) | 1.5 s | 5.0 m/s2, damp |
| 2. School crosswalk on a wide, open arterial | Speed limit | 40 mph now | 45 m | 1.5 s | 5.0 m/s2 |
| 3. Signalized intersection, level approach | Yellow duration | 35 mph | — | 1.0 s | 3.0 m/s2, comfortable |
Checks: site 1 gives 11.4 m/s = 25.4 mph, so 25 mph just meets the criterion; site 2 gives 15.0 m/s = 33.6 mph, so 30 mph meets it with margin; site 3 gives y = 1.0 + 15.65/(2 × 3.0) = 3.61 s.
Option C — the public record. Take your inputs from a published highway design reference: record the stopping sight distance it lists for three design speeds, then work backward to the reaction time and deceleration that make your model reproduce those numbers. Recommend a school-zone limit for the design speed with the shortest sight distance. Cite the source and the date you read it; label any value you could not find as illustrative.
| Criterion | What proficient looks like |
|---|---|
| Criteria and constraints (HS-ETS1-1) | Specific, measurable criteria and realistic constraints, including safety, traffic flow and published limits; the problem’s significance is described with numbers. |
| Kinematic and force model (HS-PS2-1) | Reaction and braking stages modeled correctly from the constant-acceleration equations, with units; the deceleration is explained as Fnet/m. |
| Mathematical reasoning | Correct calculations, including solving a quadratic or rearranging a formula; answers rounded sensibly. |
| Sensitivity and trade-offs | Shows how the design value changes with an assumption and weighs at least one trade-off between stakeholders. |
| Use of sources | Published guidance and data are cited and compared; illustrative values are labeled. |
| Defense | Explains and justifies the design clearly and answers questions about assumptions accurately. |
Your recommendation is in the client’s hands. Next: the unit checkpoint.
Exit ticket: which Wonder Board question can you now answer with a number? Write the question and your answer.
How confident are you that you can I can specify criteria and constraints and use a stopping-distance model to justify a traffic-safety design value.
Timing: three sessions, as in Poly: plan and model; peer review; final and defense. Presentations may run into the checkpoint day’s warm-up.
Materials: rubric copies, the Option B site table, devices or graph paper, a timer.
Setup: invite a staff member or family volunteer to play the school-safety team; a video call works. Sites and values are generic and illustrative.
Listen for: design values with no criterion; constraints confused with criteria; sources not labeled.
Support / stretch: provide a report outline with section headings and a worked site. Stretch: add a downhill approach and explain how the grade changes the deceleration (preview of Unit 2).
Reading: OpenStax Physics (high school), chapters 2 and 3.