Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Traffic Curran Dartmoor topic
No spam. Unsubscribe anytime.
Council reviews traffic study for Dartmoor/Curran intersection; asks staff for pricing on 4‑way stop, lane closures and signal
Summary
City staff presented an H.R. Green traffic study finding the intersection does not meet signal warrants but meets 4‑way stop crash warrant; council directed staff to get prices for a 4‑way stop (with striping/delineators), temporary lane closures and a traffic signal (engineer estimate ~$500,000) and return with numbers.
Get email alerts on the Traffic Curran Dartmoor topic
No spam. Unsubscribe anytime.
The McHenry City Council on March 17 received a traffic study by H.R. Green and staff that examined the Curran Road/Dartmoor intersection and directed staff to return with pricing for three options: (1) implement a 4‑way stop with associated re‑striping and delineators to close turn lanes, (2) temporarily close or stripe off existing right‑turn lanes and monitor the result, and (3) install a traffic signal (city‑funded; no IDOT funding identified).
Russ Adams, who presented the study, told council the study evaluated crash history, current and projected traffic volumes and the eight standard signal warrants. "The intersection does not meet warrants by any of the criteria, any of the 8 warrant standards, not now, not with anticipated development and not with projected 2,050 traffic volumes," Adams said. He said the study found the intersection meets the warrant for a 4‑way stop under crash criteria (seven crashes over a three‑year span) but that a 4‑way stop would worsen delay on Curran Road (downgrade level of service) and could cause noticeable queues during peak periods.
Alternatives examined in the study included removing some of the turning lanes, installing a full traffic signal (engineer estimate cited in the meeting: roughly $500,000 for a signal), and an expensive roundabout (rough estimate cited: $4.5 million). Adams and other staff recommended staging lower‑cost and reversible changes first (striping, temporary delineators) before permanent pavement removal, so the intersection can be reconfigured back if a signal becomes necessary later.
Council members and the police chief discussed sight lines, the straight geometry of Curran Road that encourages high speeds, and the limits of tree‑trimming alone to fix the problem. Chief Burke said many collisions are not speed‑related but stem from the intersection configuration and that leaving multiple approach lanes while converting to a 4‑way stop could create confusion and new crash modes.
Several residents who live near the intersection spoke. Kyle Hill, a Legend Lakes resident, argued a signal was the long‑term solution given planned nearby development and predicted traffic increases. Jay Colbert, another resident, said a 4‑way stop could be a “nightmare” and suggested eliminating some turning movements and improving visibility as interim steps.
After extended discussion the council generally supported moving forward with pricing and analysis. The mayor asked staff to obtain contractor quotes and estimated costs for: installation of a 4‑way stop (signs, advanced warning signage, striping), striping/delineators to close off turn lanes as a reversible test, and a full traffic signal including options for overhead lighting or flashing signal treatment; staff said they would also estimate timelines and discuss whether the project could be added to existing pavement‑marking contracts. Staff estimated the 4‑way stop/striping/delineator option in the low five‑figures ($10,000–$25,000) while a traffic signal was estimated in the mid six‑figures (~$500,000). Council directed staff to return with formal pricing and recommended implementation scenarios for council consideration in the coming months, with an aim to report back by May so changes could take effect before summer.
Ending: Staff will solicit quotes, model lane closure/striping options and cost overhead lighting or flashing stop devices as part of the pricing effort; council did not vote on a permanent configuration at the March 17 meeting.

