On Flock License Plate Tracking Cameras

A recent viral incident involving a writer who was mistakenly identified, tracked, and arrested due to inaccurate data from Flock license plate recognition (LPR) cameras has ignited a significant debate surrounding the technology’s reliability, its implementation by law enforcement, and the broader implications for civil liberties. The case, which saw the individual detained for days based on a misread license plate, highlights critical vulnerabilities within the automated surveillance ecosystem.
The Incident: A Case of Mistaken Identity and Systemic Flaws
The core of the controversy lies in a misidentification involving a Jaguar Land Rover (JLR) media fleet vehicle. The vehicle in question was reportedly equipped with New Jersey manufacturer plates bearing the alphanumeric sequence "34 03 DTM." However, a police report, when entered into Flock’s system, was allegedly recorded with a truncated identifier: "34 DTM." This seemingly minor discrepancy proved to be the catalyst for the erroneous tracking and subsequent arrest.
Flock’s AI-powered LPR technology, designed to scan and log license plates, failed to account for the missing numeral in the middle of the plate. Instead of recognizing the partial string as incomplete or a potential anomaly, the system registered "34 DTM" as a match. This led to the Range Rover, driven by the writer, being flagged and alerts being issued to local law enforcement.
The writer, who detailed the experience in a widely circulated account, described the unsettling realization that the issue was not isolated to his vehicle. He discovered that numerous vehicles in JLR’s media fleet share a similar New Jersey manufacturer plate structure: "34 ## DTM." This meant that any JLR vehicle with this plate format, anywhere a police department partners with Flock, could potentially be misidentified as stolen. According to the account, Officer Ganshyn, who was involved in the incident, indicated that at least four other vehicles with the "34 ## DTM" plate structure were being tracked in Minnesota during the same week. The writer’s arrest marked the first instance where an individual was apprehended due to this particular systemic error.
The resolution of the situation hinged on the LAPD correcting the initial police report and updating Flock’s system, a process that Jaguar Land Rover was reportedly working to expedite following the writer’s detention and subsequent communication.
Flock’s Response: Blame and Justification
In the wake of the negative publicity, Flock Safety has issued statements attempting to address the concerns raised. Initially, the company affirmed that its systems were functioning as intended, shifting the onus onto the police departments that utilize their technology.
According to statements attributed to a Flock representative named Thomas, the machine learning (ML) algorithms correctly processed the data they were fed. When the system was instructed to search for "34 DTM," and it detected those characters, it returned a positive match. Thomas explained that the ML’s function in this instance was to determine if the requested characters were present, not necessarily to verify the entirety of a license plate or to flag discrepancies if more characters were present.
"The way that the ML [machine learning] works is it correctly read what it was supposed to read. It was fed those characters that you said, 34 DTM, and it spit back out [a result] with the characters, 34 DTM," Thomas stated. "It was asked, can you find this? And it did find that. It just didn’t say if there’s more here, then don’t do it. It just simply said, is it there? And the answer was yes."
Furthermore, Flock defended its system’s behavior by citing law enforcement practices. Thomas explained that law enforcement agencies often request alerts even when only partial plate information is available, particularly in the initial stages of an investigation. This approach, he argued, is intended to cast a wider net and provide officers with potential leads. "The way that law enforcement likes to use these tools is, if any of the characters that they have put into these hot lists get read, they want to get those alerts," he said.
However, Thomas also acknowledged the need for human verification, stating, "Now, what we try to train officers to do is to do what you said, which is to verify that 34 DTM is what I’m looking for, and what I’m seeing is 34 10 DTM." This statement implicitly suggests that while the system flagged a match, the responsibility for confirming the accuracy of that match before acting upon it lies with the law enforcement officer.
A Pattern of Controversy: CEO’s Apology and Broader Usage
This incident is not the first to draw scrutiny to Flock Safety. In a separate development, the company’s CEO issued an apology for previously labeling privacy advocates as "terrorists." This past rhetoric, revealed in another report, underscores a defensive posture taken by the company when confronted with criticism regarding its surveillance technology. The CEO’s subsequent apology suggests a potential shift in public relations strategy or a recognition of the damaging impact of such language.
Beyond the specific case of misidentification, the broader application of Flock’s camera network has also come under fire. An investigation by 404 Media revealed that police departments are utilizing Flock cameras not just for tracking vehicles, but also for searching for specific individuals based on descriptive characteristics. These searches have reportedly included terms such as "heavy-set male with a black and white hat," "person on skateboard," and "person wearing orange vest and construction hat." Some searches have even referenced a target’s race or indicators of political affiliation.
This expansion of Flock’s utility from vehicle tracking to personal surveillance raises significant concerns about potential overreach and the erosion of privacy. Such capabilities, when combined with the inherent risks of data errors, create a potent tool for unwarranted scrutiny.
The Shadow of Abuse: Surveillance Technology and Misuse
The documented instances of Flock cameras being used to track individuals, coupled with the recent misidentification incident, highlight a recurring theme in the deployment of police surveillance technologies: the potential for abuse. As with any powerful tool, the effectiveness of LPR systems and their associated data networks is intrinsically linked to the integrity of the data, the accuracy of the algorithms, and the discipline of the users.
Reports of unusual police database searches in Ohio, as flagged by an audit, further underscore this point. These audits often uncover instances where surveillance technology is used for purposes beyond its intended scope or in ways that deviate from established protocols. The lack of stringent oversight and accountability mechanisms can exacerbate these issues, creating an environment where errors can have severe consequences and misuse can go unchecked.
Implications for Public Trust and Privacy
The Flock camera controversy serves as a stark reminder of the complex trade-offs between public safety and individual privacy in the digital age. While LPR technology can be a valuable asset in law enforcement’s efforts to combat crime and locate stolen vehicles, its implementation must be accompanied by robust safeguards.
The incident raises several critical questions:
- Algorithmic Transparency and Accuracy: How can we ensure that the algorithms powering these surveillance systems are transparent, accurate, and designed to minimize false positives? The current case suggests that a "match" is not always a definitive identification, and the system’s design may prioritize broad detection over nuanced accuracy.
- Data Integrity and Error Correction: What protocols are in place to ensure the integrity of the data entered into these systems, and how efficiently can errors be corrected to prevent prolonged or unwarranted surveillance? The reliance on manual data entry and the potential for transcription errors present a significant vulnerability.
- Law Enforcement Training and Oversight: How are law enforcement officers trained to interpret and act upon alerts generated by LPR systems? The statement that officers are trained to verify matches implies a gap between system alerts and actionable intelligence, a gap that can be exploited by human error or negligence. Robust oversight mechanisms are crucial to prevent the misuse of this technology.
- Scope of Surveillance: The shift towards using LPR data for individual tracking, beyond vehicle identification, necessitates a serious public discussion about the acceptable limits of police surveillance and the potential for these technologies to create a pervasive surveillance state.
- Accountability and Redress: When errors occur, what mechanisms are available for individuals to seek redress and hold responsible parties accountable? The writer’s experience highlights the difficulty of rectifying such errors once they have led to an arrest and detention.
The viral nature of this story has amplified public awareness of the capabilities and potential pitfalls of LPR technology. As Flock and other companies continue to expand their networks and capabilities, ongoing scrutiny and a commitment to transparency, accuracy, and accountability will be essential to maintaining public trust and safeguarding fundamental civil liberties. The broader implications extend to all forms of automated surveillance, demanding a continuous societal dialogue about the balance between security and freedom.







