Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Public Safety topic
No spam. Unsubscribe anytime.
Oregon City staff to study red‑light and automated speed cameras after data briefing
Summary
Staff presented crash data and legal requirements for automated enforcement; commissioners asked staff to solicit one or two vendors to analyze candidate intersections, privacy protections and revenue use, with a view to returning with vendor reports and recommended next steps.
City staff briefed the commission on the mechanics, legal requirements and local crash statistics related to red‑light and automated speed enforcement and asked for direction on whether to pursue vendor studies.
"These cameras are always monitoring when we're not there," the staff presenter said, framing automated enforcement as a way to change driving behavior and reduce severe angle and intersection crashes. Staff reviewed Oregon law requirements, ODOT guidance for state intersections and a five‑year crash pull (2020–2024) showing 1,977 reported crashes in Oregon City during the selected period, including 94 serious (A‑level) injury crashes and nine fatalities.
Staff noted trade‑offs: automated enforcement tends to reduce severe side‑impact (T‑bone) crashes but can increase rear‑end collisions as drivers brake; it also requires public outreach, signage and administrative capacity to vet vendor citations and manage court and records functions. State rules set thresholds for automated speed enforcement (typically 11 mph above the posted limit under current law) and require vendor engineering reports and, for state‑controlled intersections, ODOT approval.
Privacy and administration questions surfaced. Commissioners asked how license and DMV data are protected; staff said DMV and criminal justice information rules (CJIS) and vendor agreements govern access and retention and noted that departments commonly hire court staff and trained reviewers to process citations.
What the commission directed: Commissioners expressed general support for pursuing a feasibility study. Staff was asked to solicit one or two vendors to mount temporary monitoring, produce engineering and incident reports for candidate intersections (examples cited: Highway 213 at Beavercreek, 99E at 14th, and Malala/Molalla corridors), and return with recommendations that include privacy safeguards, staffing needs and proposed uses for any revenue generated (members suggested directing fines toward traffic‑calming and pedestrian‑safety projects).
Sources: Staff presentation and discussion at the Oregon City work session, May 12.
