Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Traffic Safety topic
No spam. Unsubscribe anytime.
Monroe council delays decision on piloted automated speed cameras, asks for more data and community input
Summary
City staff recommended a phased pilot of automated speed‑safety cameras at two school zones and urged inclusion in the 2027–28 budget; council members raised operational, budget and equity concerns and asked staff to return with comparative data on non‑camera traffic‑calming measures and expanded public outreach.
Get email alerts on the Traffic Safety topic
No spam. Unsubscribe anytime.
City staff recommended that Monroe include a piloted automated speed‑safety camera program in the mayor's 2027–28 budget, but the council declined to approve the plan on June 16 and instead instructed staff to gather more data and pursue broader community engagement.
Liam Mccoral, who presented the item, framed the council's immediate choice as twofold: "Does council want to move forward with an automated traffic safety camera program?" and, if so, "what is the tentative recommended approach to include in the mayor's recommended budget?" He summarized public outreach (a program webpage, social posts and an informational meeting on May 7 with six attendees) and said staff recommended a phased pilot and suggested placing stationary cameras at Parkplace Middle School and Frylands Elementary School because prior location analyses showed higher potential violation rates in those school zones.
Supporters on the council cited crash and speed data and urged action. "We have to do something…we're just basically gambling with people's lives in my opinion if we don't increase enforcement," Council Member Gamble said, arguing a pilot could reduce dangerous speeds. Several members said they had seen high speeds on Main Street and other corridors and that cameras were one of the few scalable tools when patrol capacity is limited.
Opponents and cautious members focused on costs and long‑term commitments tied to a camera program. Staff warned the council that a camera program could require an extra full courthouse day—an increase to judicial compensation estimated in the staff discussion at roughly $47,000—and one or two additional court clerks. Council members said they worried that the program’s success would reduce infractions and revenue over time while leaving the city with permanent staffing and contract costs. Members also asked for a comparison between camera costs and alternatives such as rapid rectangular flashing beacons, additional signage, speed humps and targeted patrols.
Why it matters: the cameras are intended to improve pedestrian and school‑zone safety by automating enforcement where speeding is frequent. The city faces tradeoffs between potential safety gains and upfront and ongoing operational costs that could remain even if citations decline.
What comes next: council did not authorize the staff recommendation. Members asked staff to return with additional comparative data on non‑camera traffic‑calming measures (pre/post performance where the city previously installed them), a clearer budget model including conservative revenue projections and projected long‑term court and staffing costs, and to convene broader stakeholder engagement before any final decision during the biennial budget process.

