3.1 Traffic Studies & Engineering Data Collection
Key Takeaways
- A traffic control signal shall not be installed unless an engineering study indicates that the installation is justified and will improve safety or operations; satisfying a warrant does not legally mandate installation.
- Traffic signal justification studies require continuous 24-hour directional counts, 12-hour to 16-hour turning movement counts broken down into 15-minute intervals, pedestrian volume tallies, and speed distribution profiles.
- The 85th percentile speed of free-flowing traffic on the major street approach (or the statutory posted speed limit when validated by an engineering study) governs whether the high-speed 70% volume reduction factor applies.
- Collision analysis must isolate crash types susceptible to correction by signalization—predominantly right-angle collisions and opposing left-turn collisions—from non-susceptible crash types like rear-end impacts.
- A comprehensive physical inventory must capture intersection geometry, approach grades, sight distance triangles, lane channelization, lighting, transit stops, and proximity to highway-rail grade crossings.
3.1 Traffic Studies & Engineering Data Collection
[!IMPORTANT] MUTCD Legal Mandate for Signal Installation: Under the Manual on Uniform Traffic Control Devices (MUTCD) Chapter 4C (Section 4C.01), a traffic control signal shall not be installed unless an engineering study of traffic conditions, pedestrian characteristics, and physical environment demonstrates that installation is justified. Furthermore, the satisfaction of an MUTCD traffic signal warrant or warrants shall not in itself require the installation of a traffic control signal. Traffic signals installed without warrant satisfaction or without an engineering study create significant tort liability for operating agencies and frequently degrade corridor safety.
Traffic signals represent the most restrictive and expensive form of intersection control available to transportation agencies. When installed at appropriate, warranted locations, traffic signals provide orderly movement of conflicting traffic streams, allocate right-of-way, increase the traffic-handling capacity of an intersection, reduce the frequency and severity of right-angle collisions, and provide protected pedestrian crossing intervals. However, when installed at unwarranted locations—often as a knee-jerk reaction to public petitions, political pressure, or an isolated, non-correctable tragedy—traffic signals routinely produce adverse consequences. Unwarranted signals increase overall intersection delay, elevate rear-end collisions by 20% to 50%, encourage cut-through traffic on adjacent residential streets, and breed driver disrespect for traffic control devices, leading to red-light running.
For the IMSA Traffic Signal Senior Field Technician Level III, leading or participating in an intersection justification study requires absolute mastery of traffic data collection standards, statistical sampling techniques, geometric surveys, and collision record analysis.
Statutory Framework and Engineering Prerequisite
The Federal Highway Administration (FHWA) MUTCD establishes national standards for all traffic control devices across all public roadways open to public travel (23 CFR Part 655). Chapter 4C establishes nine distinct traffic signal warrants. State Departments of Transportation (DOTs) adopt the national MUTCD directly or adopt a state MUTCD that must be in substantial conformance with federal standards.
The Engineering Study Prerequisite
Every warrant evaluation begins with a comprehensive Traffic Engineering Study. Section 4C.01 specifies that:
- A traffic control signal should not be installed if an engineering study indicates that the installation will not improve the overall safety and/or operational efficiency of the intersection.
- Signals shall not be installed based solely on public petitions, political requests, or emotional appeals. Operating agencies that yield to political pressure without warrant compliance forfeit qualified governmental immunity in many jurisdictions, exposing the agency to severe legal liability in the event of subsequent crashes.
- Before committing to a full traffic signal installation, operating agencies must evaluate less restrictive operational remedies (such as geometric improvements, warning signs, sight triangle clearing, high-visibility crosswalks, or roundabout feasibility).
Core Engineering Data Collection Protocols
To conduct a legally defensible and technically thorough signal warrant analysis, technicians and traffic engineers must collect eight primary data sets under typical traffic conditions. Data must not be collected during abnormal conditions such as severe weather, construction detours, holidays, or major special events unless the study specifically evaluates peak seasonal operations.
+--------------------------------------------------------------------------------+
| MUTCD Chapter 4C Required Data Elements |
+--------------------------------------------------------------------------------+
| 1. 24-Hour Vehicular Volume Counts (Directional hourly profiles) |
| 2. 12-to-16-Hour Turning Movement Counts (15-min intervals, AM/Mid/PM peaks) |
| 3. Pedestrian & Bicycle Volume Counts (Crossing times, disabled, children) |
| 4. Spot Speed Studies (85th percentile speed on major-street approaches) |
| 5. Collision History Records (Minimum 12-month / standard 3-year diagrams) |
| 6. Physical Geometric Inventory (Sight triangles, grades, lane widths, ADA) |
| 7. Roadway Network & Transit Inventory (Signal spacing, bus dwell zones) |
| 8. Nearby Rail & Preemption Assessment (Within 140 ft of track crossing) |
+--------------------------------------------------------------------------------+
1. Vehicular Volume Data Collection
Vehicular volume data provides the foundation for Warrants 1, 2, 3, and 8:
- 24-Hour Directional Machine Counts: Automated Traffic Recorders (ATRs) utilizing pneumatic road tubes, temporary radar sensors, or non-intrusive video detection cameras are deployed for a minimum of 24 to 48 consecutive hours during mid-week conditions (Tuesday through Thursday). Directional volume is aggregated into 60-minute increments to establish daily diurnal flow curves and identify peak operational periods.
- 12-Hour or 16-Hour Turning Movement Counts (TMCs): Manual or AI-assisted video count systems record all turning movements (left, through, right, U-turn) on every approach, typically from 06:00 to 18:00 or 06:00 to 22:00. Data must be tabulated in 15-minute intervals to capture short-duration peaking characteristics, compute the Peak Hour Factor (PHF), and establish heavy vehicle percentages (FHWA Scheme F vehicle classification).
- Right-Turn Treatment: In Warrant 1, 2, and 3 evaluations, right-turning vehicles on the minor approach may be excluded from the minor-street approach volume count if an exclusive right-turn lane exists with adequate storage length, clear sight distance, and negligible delay, allowing right turns to merge freely into cross-traffic.
2. Pedestrian and School Child Counts
Pedestrian data is mandatory for Warrant 4 (Pedestrian Volume) and Warrant 5 (School Crossing):
- Pedestrian Crossing Volumes: Technicians count pedestrian crossings across each leg of the intersection, broken into 15-minute intervals over a 12-hour to 16-hour duration.
- Demographic & Mobility Profiling: Counts must explicitly document the number of young children, senior citizens (65+), and persons with mobility, auditory, or visual impairments. Technicians measure crossing walking speeds to verify whether the MUTCD baseline walking speed of 3.5 ft/sec (or a reduced speed of 3.0 ft/sec for slower populations) is appropriate.
- Pedestrian Delay and Gap Surveys: Technicians measure vehicular gaps on the major street. An adequate gap is a gap duration equal to or greater than the calculated pedestrian crossing time. Section 4C.01, Paragraph 19 lists gap distribution and pedestrian delay — at least two 30-minute peak pedestrian delay periods — among the desirable supplementary data. Note that the 11th Edition contains no numeric gap threshold for Warrant 4; the legacy "fewer than 60 adequate gaps per hour" test was deleted. Gap data still matters, because Section 4C.05, Paragraph 9 allows an agency to conclude that no signal is needed where adjacent coordinated signals already deliver adequate crossing gaps, and because Warrant 5 (School Crossing) does have an explicit gap test: fewer acceptable gaps than there are minutes in the crossing period.
3. Spot Speed Studies and Approach Grade Evaluation
Speed data determines whether high-speed warrant reduction thresholds apply:
- Spot Speed Survey Protocol: Conducted under free-flowing traffic conditions using a calibrated Doppler radar or LIDAR device. Technicians sample at least 100 free-flowing passenger vehicles per major-street approach, positioned far enough upstream of the intersection (typically 500 to 1,000 feet) to avoid measuring deceleration or queue stagnation.
- Critical Statistical Metrics:
- 85th Percentile Speed: The speed at or below which 85 percent of vehicles travel. It represents the legal operating benchmark for engineering design.
- 10 mph Pace Speed: The 10 mph band containing the largest percentage of sampled vehicles, measuring speed dispersion.
- Warrant Implication: If the 85th percentile speed on the major street exceeds 40 mph (65 km/h), the 70% high-speed volume reduction factor applies to Warrants 1, 2, and 3.
- Approach Grades: Technicians measure roadway longitudinal grades using a digital clinometer or surveyor's level. Steep downhill approach grades (>4%) significantly lengthen stopping distances, while steep uphill minor approaches (+4% to +8%) delay acceleration into traffic gaps, directly affecting sight distance requirements and clearance intervals.
4. Collision History and Diagramming
Collision records provide the statutory basis for Warrant 7 (Crash Experience):
- Analysis Period: Warrant 7 requires a minimum of 12 consecutive months of crash data, while standard municipal engineering practice requires a 3-year to 5-year historical analysis to eliminate regression-to-the-mean statistical anomalies.
- Collision Diagrams: Technicians plot every crash on a scaled intersection diagram, recording collision type, direction of travel, date, time of day, weather, surface condition (dry, wet, ice), and severity (Property Damage Only [PDO], personal injury, fatality).
- Susceptible vs. Non-Susceptible Crashes:
- Susceptible Crashes: Collisions that a traffic signal is designed to mitigate. Specifically, right-angle (broadside/T-bone) collisions caused by side-street vehicles failing to yield to cross-traffic, and opposing left-turn crashes involving vehicles turning across oncoming through traffic.
- Non-Susceptible Crashes: Collisions that traffic signals do not correct, and often exacerbate. Rear-end collisions on the major street typically increase following signal installation due to sudden red-phase stops. Single-vehicle run-off-the-road crashes, sideswipes, and backing collisions are also non-susceptible.
5. Physical and Geometric Roadway Inventory
A complete engineering study includes a physical inventory of the intersection:
- Cross-section dimensions: Number of lanes, approach lane widths (typically 10 to 12 feet), median widths, curb radii, and presence of raised medians or pedestrian refuge islands.
- Sight distance surveys: Field measurements of Stopping Sight Distance (SSD) and Intersection Sight Distance (ISD) along each approach, compared against AASHTO A Policy on Geometric Design of Highways and Streets (Green Book) criteria. Sight triangles must be inspected for sight-obscuring fences, retaining walls, dense landscaping, utility poles, or on-street parked vehicles.
- Operational environment: Street lighting illuminance levels, pavement marking retroreflectivity, signage inventory (STOP, YIELD, ADVANCE WARNING), transit stops (dwell times, bus pullouts), and adjacent traffic signals within 2,640 feet (0.5 miles) to evaluate coordination feasibility.
Engineering Data Elements and Sampling Standards
The table below summarizes the required engineering data elements, standardized collection methodologies, minimum sampling schedules, and operational thresholds governing MUTCD signal justification studies:
| Engineering Data Element | Collection Methodology / Tool | Minimum Sampling Duration / Schedule | Application to Signal Warrants & Analysis |
|---|---|---|---|
| Vehicular Volume (Total & Directional) | Pneumatic road tubes, radar counters, inductive loop ATRs | 24 to 48 consecutive hours (Tuesday-Thursday mid-week) | Identifies diurnal volume curves, highest 8 hours for Warrant 1, 4 hours for Warrant 2, and peak hour for Warrant 3. |
| Turning Movement Counts (TMCs) | Manual tally boards, electronic count boards, AI video processing | 12 to 16 hours (06:00-18:00 or 06:00-22:00) in 15-min intervals | Evaluates minor-street higher-volume approach, computes PHF, separates heavy vehicles, isolates right-turn bypass volumes. |
| Pedestrian Crossing Volumes | Manual visual counting or video tracking at all crosswalk legs | 12 to 16 hours continuous; 15-min intervals | Directly evaluated under Warrant 4 (100 peds/4 hrs or 190 peds/1 hr) and Warrant 5 (>20 school children). |
| Spot Speed Distribution | Calibrated Doppler radar, LIDAR gun, or dual-tube speed sensors | Minimum 100 free-flowing vehicles per major approach | Computes 85th percentile speed; if >40 mph, triggers 70% volume reduction thresholds for Warrants 1, 2, and 3. |
| Collision Records & Police Reports | State crash databases, certified police collision reports | Minimum 12 consecutive months (Warrant 7); recommended 3-5 years | Isolates susceptible crashes (angle and opposing turn); requires 5+ susceptible injury/PDO crashes in 12 months for Warrant 7. |
| Geometric & Sight Distance Survey | Total station, laser rangefinder, measuring wheel, digital clinometer | Full physical field inventory on all approaches | Compares measured ISD/SSD against AASHTO Green Book standards; calculates pedestrian crossing clearance distance ($W$). |
| Railroad Crossing Proximity | Physical measurement from stop line to nearest rail; track inspection | Site survey; rail operator daily train count data | Evaluates Warrant 9 if grade crossing is within 140 feet of intersection stop line; verifies preemption requirements. |
Field Technician Practical Procedures & Troubleshooting
When conducting data collection in the field, technicians must follow rigorous technical protocols to ensure data validity:
[!TIP] Pneumatic Road Tube Deployment Guidelines:
- Tube Spacing for Speed and Classification: When utilizing dual-tube counters for speed and vehicle classification, set the spacing between tubes precisely to manufacturer specifications (typically 2.0 feet, 4.0 feet, or 16.0 feet). An error of just 1 inch over a 24-inch tube spacing introduces a 4.2% error in speed calculation!
- Tensioning and Fastening: Anchor tubes using heavy-duty asphalt nails and nylon webbing sleeves. Maintain slight tension to prevent tube whipping under high-speed heavy truck traffic. Avoid placing tubes across potholes, expansion joints, or deep pavement ruts where tires cause air surges that produce false phantom axle counts.
- Sight Distance Measurement Technique: When conducting intersection sight distance (ISD) surveys, position the observer's eye height at 3.5 feet above the pavement surface at a set-back distance of 14.5 feet from the edge of the travel lane (simulating a driver's eye position in a stopped vehicle). The target height on the approaching roadway must be positioned at 3.5 feet (simulating the roofline of an approaching passenger car).
Which statistical speed metric is explicitly evaluated in traffic signal justification studies to determine whether the 70% high-speed warrant reduction factor may be applied?
Under the MUTCD 11th Edition, which crash types are counted when comparing an intersection against the Warrant 7 (Crash Experience) threshold tables?
What is the core principle established by MUTCD Chapter 4C regarding the relationship between warrant satisfaction and traffic signal installation?