Cheverly council hears pilot data and privacy concerns as police, vendor urge stop‑sign cameras

Mayor and council spent the bulk of their April work session debating automated stop‑sign enforcement after the Police Department and a vendor presented pilot data that officials said show widespread failures to obey stop signs.

Chief of Police (the "Chief") framed the technology as public‑safety tool and "a force multiplier," saying intersection crashes tied to stop‑sign noncompliance can produce serious injuries and fatalities. "Automated enforcement is an effective and, more importantly, an efficient tool," the Chief told the council during the briefing, urging elected officials to weigh safety benefits as a policy decision for the town.

Rob Carl, introduced by the Chief as Avio's representative, summarized about 12 weeks of beta testing and said the system recorded roughly 3,284 daily stop‑sign violations across nine pilot locations — an aggregate statistic the company used to illustrate the scope of noncompliance. Carl told the council that some individual intersections produced much higher counts: Newton Street and 57th Avenue showed about 1,300 daily violations in the vendor's test; 62nd and Kilmer recorded roughly 1,128 daily violations; Forest Road and Cheverly Avenue recorded several hundred per day at the time of testing. "The numbers are always shocking to me every time I see them," Carl said, arguing the cameras are intended to change driver behavior.

Vendor and police representatives described technical and contractual details the council asked for: the posted civil fine would be $40 under the model the vendor described; initial contract language commonly includes a monthly maintenance component (the vendor cited a maintenance figure in the presentation), a per‑violation processing fee and a cost‑neutral revenue model designed to cover operating costs rather than generate large net revenue for a municipality. The Chief and staff emphasized Maryland law and recent legislative changes that shape contract terms: the General Assembly moved automated enforcement from a percentage‑split model to a flat or cost‑neutral structure out of concern it otherwise acted like a bounty. The Chief said town staff's research indicates little net revenue to the town is likely under cost‑neutral contracts.

Privacy, data security and retention were central concerns from council members and residents. Council members asked what footage is retained, who owns the data, and how the town could respond to outside requests. The Chief said the town would own any data; Avio's representative said violation clips are captured, transmitted securely to cloud storage and retained for adjudicative needs while non‑violation footage is typically overwritten on a short cycle (the vendor described a 12–24 hour overwrite default for non‑violation video). The town attorney and police also referenced statutory retention limits and said a judicial subpoena would be required for third‑party access to non‑adjudicated material.

Council members pushed for more local community input and technical detail before a deployment. Some urged a cautious, incremental approach — citing houses in camera fields of view and the need for clear policies on signage, first‑offense warnings and whether neighbors get notice — while others said the early results suggest pilots can reduce risky driving quickly. The vendor cited early reductions in other municipalities (two locations showed 38–50% reductions in stop‑sign violations within eight weeks after warnings and enforcement were introduced), but several council members and residents asked for neighborhood‑level safety studies and longer follow‑up data.

Next steps: the council agreed by consensus to send the topic to the policy subcommittee to draft parameters for a pilot, include more resident engagement, and develop a policy that would later return to the full council for a vote. Staff and the vendor committed to provide additional technical documentation, example footage and more detailed cost/revenue scenarios to inform the subcommittee's work.

Why it matters: stop‑sign infractions are common and frequently occur near homes and crosswalks; council members said the tradeoffs between privacy and safety require clear rules and community buy‑in before the town adopts automated enforcement.