Columbus, Ohio, shut down its entire network of Flock license plate readers after a single officer allegedly ran the same plate more than 270 times over 14 months, and the department only found out when a newspaper started asking questions.
Officer Melvin Tellis, a member of the Columbus City Council Executive Protection Unit who joined the force in 2017, searched one license plate repeatedly between November 2023 and December 2024, a USA TODAY analysis of public records revealed. The reasons Tellis logged for the searches were "generally vague, often listed simply as 'location.'" Police Chief Elaine Bryant said the division believes the searches were not related to Tellis's job.
The Columbus Division of Police learned about the searches on September 1, one day after the Columbus Dispatch began asking questions about search history flagged as suspicious in the USA TODAY database. That sequence matters: the department's own oversight did not catch what a newspaper and a public-records analysis caught first.
Columbus police immediately halted the Flock program. Officers covered the cameras with bags to stop further data collection. The city ordered a full audit of every Flock search conducted by its police department.
Tellis was relieved of duty and required to turn in his gun, badge, and other equipment. He was reassigned to a desk job at police headquarters. He continues to be paid.
No charges have been filed. Bryant declined to identify the owner of the license plate in question or explain the nature of any relationship between Tellis and that person. Mayor Andrew Ginther called the allegations "deeply troubling" as the city moved to halt camera use.
Columbus City Council is now drafting legislation to govern how the Flock cameras can be used going forward, an acknowledgment that the rules governing this surveillance tool were inadequate before the scandal broke. The specifics of that legislation remain unclear.
Flock, the company that manufactures the automatic license plate readers used by Columbus and hundreds of other police departments, has tried to position itself as part of the solution. CEO Garrett Langley addressed the broader controversy in a CBS News interview, where he apologized to an alleged stalking victim tied to misuse of the company's technology:
"I apologize. It kills me that she went through that."
Langley rejected the idea that Flock bears responsibility for officers who abuse its tools:
"I don't think that Flock created police abuse. I think we're the first company to ever shine a light on it and build the tools to find it."
That claim deserves scrutiny. In Columbus, Flock's own system did not flag Tellis's 270-plus searches as suspicious. A newspaper did. A USA TODAY database did. The company that says it built "the tools to find" abuse was not the entity that found it.
Langley has also called for what he describes as a national conversation about balancing surveillance and civil liberties. In a previously published interview, he framed the issue as a matter of compromise:
"When people talk about just one of these, privacy or safety, they're prioritizing the wrong thing, and what we have to prioritize as a country is compromise."
He added: "How do we have our safety, and how do we balance privacy?"
Columbus is not the first Ohio jurisdiction to discover that shiny law-enforcement technology does not always deliver on its promises. Dublin, Ohio, a suburb roughly 20 miles northwest of Columbus, spent $128,080 on a Knightscope K5 security robot that patrolled a public parking garage from July 2024 until May 2025 and produced zero arrests, zero tickets, and zero criminal cases. Dublin expects a partial reimbursement of $60,500 from the manufacturer, leaving taxpayers with a net bill of roughly $67,500 for a machine that accomplished nothing.
Similar Knightscope pilots in New York City's Times Square subway station and San Antonio International Airport also encountered significant problems, including navigation failures and camera malfunctions. As cybersecurity analyst Kurt "CyberGuy" Knutsson put it: "When a city tests an expensive public safety tool, people deserve a clear way to judge whether it worked."
The pattern is consistent. Agencies adopt surveillance and AI-driven tools with enthusiasm, market them as force multipliers, and then struggle with basic questions of accountability, effectiveness, and oversight once the systems are in place.
Several critical facts remain unknown. Who owns the plate Tellis searched 270 times? What was his relationship, if any, to that person? Has he offered any explanation or denial? Bryant's refusal to provide details leaves the public guessing about whether this was personal obsession, harassment, or something else entirely.
The scope of the planned audit is also unclear. How many officers had access to the Flock system? How many total searches were conducted, and how many of those will be reviewed? If one officer's pattern went undetected for more than a year, the question is whether the oversight structure was designed to catch misuse at all, or whether the department simply trusted officers to police themselves.
And the legislation Columbus City Council is drafting raises its own questions. Will it impose hard limits on how many times an officer can search the same plate without supervisory approval? Will it require automatic alerts when search patterns become anomalous? Or will it amount to a paper policy that checks a box without changing behavior?
Conservative voters who support law enforcement should be the first to demand answers. Effective policing depends on public trust, and public trust depends on accountability. An officer who allegedly ran the same plate 270 times with no legitimate reason, and a department that did not notice until a reporter called, is not a story about one bad actor. It is a story about a system that had no guardrails.
Technology that gives government the power to track citizens' movements is only as trustworthy as the institutions that control it. Columbus just showed what happens when nobody is watching the watchers.
