IMSA Traffic Signal III common mistakes
IMSA Traffic Signal III · Understand the traps and how to avoid them.
Computing the yellow change interval with a simplified rule of thumb (e.g., 'one second per 10 mph') instead of applying the full kinematic equation, and ignoring approach grade when the approach is on a significant downgrade.
The shortcut is easy to memorize and works on flat, low-speed approaches, so candidates default to it under time pressure and forget that the ITE equation includes perception-reaction time plus a braking term with a grade adjustment.
What to do instead
Write the equation out from memory every time: Y = t + v/(2a + 2Gg). Identify each variable, convert speed to ft/s, keep the grade term's sign correct (a downgrade reduces the available deceleration and lengthens the interval), and sanity-check the result against the range used in practice before committing to an answer.
Approving a pedestrian clearance interval that is calculated only as crossing distance divided by walking speed, with no walk interval, or with the walk interval tacked on as an arbitrary '7 seconds.'
Candidates conflate 'pedestrian clearance' with 'total pedestrian time,' and answer choices often present a clean division result that looks right.
What to do instead
Separate the two components explicitly: WALK is set by engineering judgment with a typical minimum of 7 seconds (3 seconds only where a very short crossing distance and heavy vehicle demand justify it), and the flashing DON'T WALK must equal crossing distance divided by the design walking speed (3.5 ft/s, or 3.0 ft/s where a slower pedestrian population is present). Add them to get the total time that constrains the minimum green and cycle length.
Treating the MUTCD warrants as a pass/fail checklist that automatically mandates a signal, and selecting warrant results without documenting the engineering study that justifies the installation.
Warrants are numeric and satisfy an exam-style 'calculate and conclude' instinct, so candidates stop at 'Warrant 1 is satisfied, therefore signalize' and skip the qualitative judgment the manual actually requires.
What to do instead
State the sequence correctly: a traffic signal is justified only by an engineering study that considers the applicable warrants plus factors such as crash history, roadway geometry, speeds, and available alternatives; satisfying a warrant is necessary, not sufficient. When a question asks whether a signal 'should' be installed, look for the answer that includes the engineering study and the option of less restrictive measures.
Using NEMA TS-1, NEMA TS-2, and Type 170 controller terminology interchangeably, including cabinet connector types, communication protocols, and rack architecture.
All three are 'traffic signal controllers' in casual reading, and the distinctions are learned on a specific agency's equipment rather than from a comparison table.
What to do instead
Build a one-page comparison you can reproduce: TS-1 uses the A, B, and C harness connectors and parallel discrete signaling; TS-2 replaces those with a serial bus (SDLC) between the controller and the detector/load-bay racks, reducing wiring; Type 170 is a different, often longer-used architecture with its own connector set and field wiring conventions. Answer equipment-identification questions by naming the architecture first, then the component.
Blurring the roles of the controller's internal watchdog and the external conflict monitor (MMU), for example stating that the controller detects conflicting green outputs and drops to flash itself.
Both are 'safety' devices inside the cabinet and both cause a flash condition, so the functional boundary is easy to lose under exam phrasing.
What to do instead
Anchor on the location and the monitored quantity: the MMU is a separate unit wired to the field output terminals that monitors for conflicting greens, red-enable faults, low or missing AC voltage, and similar field-side conditions, and it forces the cabinet to flash when it trips. The controller watchdog monitors controller operation (cycle timing, program execution). If the question says 'field output' or 'conflicting greens,' the answer is the MMU.
Recommending a detection type or loop geometry without matching it to the required function - specifying presence detection where only passage (point) detection is needed, or a long loop configuration for a stop-bar presence call.
Textbook descriptions of loops, video, radar, and magnetometer are learned as a list of technologies rather than as function-matching decisions, so candidates pick the 'most advanced' or 'most common' option.
What to do instead
Start every detection question by naming the required output: presence at the stop bar for a standing vehicle, passage/pulse detection upstream for extension, or a count/presence signal for a specific lane. Then select the technology and geometry that reliably produces that output for the site conditions (lane width, pavement, shadows, overhead clearance, bicycles). Justify the choice in one sentence tied to the function.
Signing off a new installation as ready for turn-on after confirming the controller runs, without performing and documenting the flash-transfer test of every signal head and the load-switch/field-output verification.
The controller display showing a normal cycle is visually persuasive, and field verification requires walking the intersection and coordinating a second person at the cabinet.
What to do instead
Treat turn-on as a formal sequence: verify each signal head and pedestrian head from the field for every phase, confirm the MMU and flash transfer operate on a simulated fault, confirm each load switch drives only its intended field circuit, and record the results. On the exam, when a scenario shows a 'working' controller with an unverified field, the correct answer includes the field verification step.
Skipping or under-specifying grounding and surge protection during installation review - accepting a single ground rod, omitting the neutral-to-ground bond requirements at the service, or leaving the equipment ground and cabinet ground unbonded.
Grounding is invisible after construction and is often treated as an electrician's scope rather than part of the signal installation inspection.
What to do instead
Verify the grounding electrode system, the single-point ground/bonding of the cabinet, controller, and surge arrestors, and the surge protection on field wiring and communications entries as part of the inspection checklist. Understand why: an unbonded or high-resistance ground produces intermittent, hard-to-diagnose faults and is the leading cause of lightning and surge damage to controllers and detection.
Troubleshooting an intermittent flash or call failure by swapping controllers, load switches, or detector cards one at a time without first retrieving and reading the MMU event log and the controller's fault/status records.
Part swapping is the habit formed in the field under pressure, and the exam's maintenance scenarios describe symptoms rather than logs, so candidates jump to the component named in the symptom.
What to do instead
Establish a fixed diagnostic order: read the MMU event log to see what condition caused the flash and in what order, then check the controller status/fault display, then the power and ground, and only then substitute components. On the exam, when a question describes repeated unexplained flash events, select the answer that begins with reviewing the monitor's recorded fault history rather than replacing hardware.
Reviewing a temporary traffic signal in a work zone as if it were a permanent signal - carrying over normal cycle lengths, clearance intervals, and detection assumptions - without adjusting for one-lane alternating operation, reduced speeds, or the temporary condition's duration.
Work-zone signal questions look like ordinary signal-timing questions, and the temporary nature of the installation is easy to treat as a formality.
What to do instead
Identify the control strategy first (flagger, one-lane alternating temporary signal, or portable signal), then set timing to the reduced posted work-zone speed, confirm sight distance to the signal from the approach, and confirm the temporary device itself meets the applicable MUTCD work-zone provisions for mounting height, visibility, and power/backup. Treat the posted work-zone speed - not the original roadway speed - as the basis for clearance intervals.