Documented Incident Registry
Twenty-nine evidence-graded public cases spanning false stops, stale records, insider misuse, immigration access, reproductive-health search, protest surveillance, ethnic profiling, security breaches, and class-action litigation.
This registry records documented examples, not a national rate. Cases are selected because public sources establish a relevant failure mechanism. They are more likely to become visible when litigation is filed, video exists, a reporter investigates, or an oversight body releases logs.
Campaign position: documented harms and network-governance failures support ending routine police use of networked ALPRs, not treating case reports as a prevalence estimate.
Incident timeline
Figure 6 · Twenty-nine incidents positioned by date and harm class. The density after 2024 reflects improved audit-log access and investigative reporting, not necessarily an increase in underlying incidents.
Evidence grades
| Grade | Meaning |
|---|---|
| A | Primary or official source directly documents the core claim—for example a court opinion, government release, audit, settlement record, or linked public report. Independent corroboration is included when available. |
| B | Strong multi-source journalism or public-records analysis; the complete primary record is not in hand. |
Pending complaints and criminal charges remain allegations until adjudicated. A registry entry does not prove every disputed fact, and the corpus cannot estimate demographic disparity, vendor-specific risk, or frequency.
Fault-chain taxonomy
The incidents span nine broad failure mechanisms. Several cases involve more than one.
| Harm class | Cases | System layers involved |
|---|---|---|
| OCR / sensor error | FW-001, FW-003, FW-004, FW-012, FW-013, FW-014 | Camera read, matching interface, officer verification |
| Stale or corrupted database record | FW-002, FW-013 | Source database, hot-list maintenance |
| Data sharing / governance failure | FW-005, FW-006, FW-007, FW-015, FW-019, FW-020, FW-021 | Network configuration, purpose limitation, interstate policy conflict |
| Insider misuse / unauthorized purpose | FW-010, FW-011, FW-017, FW-018, FW-029 | Access control, audit logging, personnel oversight |
| Surveillance / profiling | FW-008, FW-009 | Query purpose, discretion, First Amendment activity |
| Security vulnerability / breach | FW-016 | Camera cybersecurity, vendor configuration defaults |
| Vendor deception / procurement failure | FW-022 | Vendor representations, heat-map disclosure, council review |
| Constitutional doctrine | FW-023 | Query authorization, warrant requirement, appellate review |
| Community contract termination | FW-024, FW-025, FW-026, FW-027, FW-028 | Procurement, council/board vote, deactivation |
Escalation pattern
Read chronologically, the registry shows an escalation from individual sensor errors causing one stop (2009–2022) toward systemic network failures affecting entire communities (2024–2026). The shift tracks the transition from isolated agency-owned cameras to dense, nationally networked commercial platforms.
False Positive / OCR Error
An ALPR alert allegedly confused one plate character and officers stopped Denise Green at gunpoint.
Reported consequence: Detention and high-risk stop
System layer: sensor and officer response
Court opinion documents allegations and procedural historyStale Hot-List Record
Brian Hofer's recovered rental vehicle remained on a stolen-vehicle list; officers conducted a gunpoint stop.
Reported consequence: Detention and reported hand injury
System layer: database and verification
First-person account corroborated by EFF summaryWrong-State / Vehicle Mismatch
A plate associated with a stolen motorcycle was matched to Brittney Gilliam's SUV despite a different state and vehicle type.
Reported consequence: Four children and two adults detained at gunpoint; $1.9M settlement
System layer: alert and verification
Settlement and city statements publicly reportedOCR Character Confusion
A camera reportedly read a 2 as a 7 and matched Jaclynn Gonzales's vehicle to a stolen plate.
Reported consequence: Gunpoint detention with children present
System layer: sensor and verification
News investigation and later EFF synthesisReproductive-Health Surveillance
A deputy searched more than 83,000 cameras across 6,809 networks for a woman in an abortion-related investigation.
Reported consequence: Nationwide location search across states with conflicting abortion laws
System layer: nationwide query and purpose limitation
EFF cites affidavit and court records; congressional letter corroborates scopeImmigration Access Through Sharing
Audit logs showed Denver camera data included in roughly 1,400 immigration-related searches initiated elsewhere.
Reported consequence: Local data used for out-of-jurisdiction immigration investigations
System layer: network governance
Count derived from city-released audit logsImmigration Access Through Sharing
Public records found direct, back-door, and agency-on-behalf-of-federal immigration searches across Washington ALPR networks.
Reported consequence: Local surveillance data exposed to federal immigration enforcement
System layer: network governance
University public-records research with linked methodologyEthnic Profiling
Audit-log analysis found hundreds of searches using 'roma' or an ethnic slur; many reasons named no suspected crime.
Reported consequence: Discriminatory database searches targeting Romani identity
System layer: query purpose and discretion
Aggregate public-records analysis; not a prevalence estimateFirst Amendment Surveillance
EFF found more than 50 agencies running hundreds of national-network searches connected to protests and activist activity.
Reported consequence: Location searches related to constitutionally protected activity
System layer: query purpose and discretion
Aggregate public-records analysis; individual searches vary in contextInsider Misuse / Stalking
Georgia investigators alleged a police chief used ALPR systems to harass and stalk multiple people.
Reported consequence: Arrest on stalking and misuse charges
System layer: access control
Charges are allegations until adjudicatedInsider Misuse / Stalking
Georgia investigators alleged a sheriff's employee repeatedly used the Flock account to search for two people she knew personally.
Reported consequence: Arrest on eight misuse counts and stalking-related charges
System layer: access control
Charges are allegations until adjudicatedOCR Character Confusion
A lawsuit alleges a Flock camera read a 7 as a 2 and officers escalated a stolen-plate stop involving Brandon Upchurch.
Reported consequence: Police-dog injury; arrest and jail alleged in complaint
System layer: sensor and officer response
Allegations are pending; no adjudicated findingCompound Data Loss and Network Propagation
An LAPD record and a Flock read each omitted different middle digits so distinct plates collapsed to the same shortened key.
Reported consequence: Multi-day tracking and four-cruiser high-risk stop of journalist Joel Feder and his wife
System layer: source database plus OCR plus verification
First-person account includes public police report and agency responsesFamily-Member Association Error
A Flock camera linked a father's car to his son's felony warrant; officers handcuffed the father in his driveway within 20 minutes.
Reported consequence: Wrongful driveway detention of a parent for a child's warrant
System layer: alert and verification
News investigation with body-camera footage; city later suspended Flock useUnlawful Interstate Data Sharing
California Attorney General Rob Bonta sued the City of El Cajon for sharing ALPR data with law enforcement in more than two dozen states in violation of California law.
Reported consequence: State AG lawsuit seeking writ of mandamus to cease out-of-state sharing
System layer: network governance
AG press release and court filing; city disputes allegationsSecurity Vulnerability / Exposed Feeds
Security researchers found Flock Condor PTZ cameras broadcasting live and archived footage to the open internet without authentication; at least 60 cameras exposed.
Reported consequence: Live surveillance feeds accessible to anyone including AI face-tracking of members of the public
System layer: camera cybersecurity
404 Media verified by driving to exposed cameras; Flock confirmed limited breachInsider Misuse / Stalking
Milwaukee police officer Josue Ayala was charged with misconduct after allegedly using the Flock database 179 times to track a dating partner and that person's ex-partner.
Reported consequence: Felony misconduct charges; 179 personal-purpose searches
System layer: access control
Criminal complaint filed; charges are allegations until adjudicatedInsider Misuse / Stalking
Milwaukee Police Detective Tehrangi Chapman was charged with misconduct after admitting to using the Flock system 20 times to track two people in violation of department policy.
Reported consequence: Second felony misconduct charge from the same department
System layer: access control
Criminal complaint filed; second officer from same departmentUnauthorized Nationwide Access
Mountain View Police Department suspended all Flock cameras after discovering the first camera had been set to nationwide sharing by Flock without the city's knowledge; hundreds of out-of-state and federal agencies accessed local data.
Reported consequence: City-wide ALPR suspension; chief stated loss of confidence in the Flock system
System layer: network governance
Police chief letter and city statement; Flock acknowledged configuration issueUnauthorized Interstate Data Access
Reporting revealed hundreds of out-of-state and federal agencies had accessed Palo Alto's Flock ALPR data since the system was deployed in late 2023.
Reported consequence: City audit revealed widespread unauthorized access; California law prohibits out-of-state sharing
System layer: network governance
News investigation based on city recordsClass Action Lawsuit
Gibbs Mura filed an amended class action against Flock Safety for allegedly tracking millions of Californians and sharing data with out-of-state and federal agencies in violation of state privacy law.
Reported consequence: Class action seeks injunctive relief and damages for all affected California drivers
System layer: data sharing and privacy
Lawsuit filed; allegations are contestedVendor Deception / Misrepresentation
Oshkosh City Council unanimously rescinded its Flock contract 24 hours after approval when police discovered Flock's CISO had falsely denied the system creates heat maps of individual movement patterns.
Reported consequence: Contract rescinded; council member stated "I don't know how I can make a decision if you lie to me"
System layer: vendor conduct and procurement
Council meeting minutes and multiple news sourcesWarrantless ALPR Search Ruling
A Norfolk Circuit Court judge ruled that access to the city's 172-camera Flock ALPR database required a warrant; the Virginia Court of Appeals later reversed that ruling.
Reported consequence: Trial court suppressed evidence; Court of Appeals reversed in 2025
System layer: constitutional doctrine
Official appellate opinion documents and reverses the 2024 trial-court warrant ruling; not current statewide precedentCommunity Contract Termination
Santa Cruz City Council voted 6-1 to terminate the city's Flock Safety ALPR contract, citing privacy and out-of-state data-access concerns while leaving open a possible replacement vendor process.
Reported consequence: Municipal contract termination (6-1); earliest end after notice ~Feb 2026 as reported
System layer: procurement and local governance
Multi-source journalism documents council vote; city council minutes not attached in this passCommunity Contract Termination
Oak Park Village Board voted 5-2 to cancel its Flock Safety contract and deactivate eight ALPR cameras rather than adopt a temporary 90-day pause.
Reported consequence: Contract cancellation; eight cameras shut off
System layer: procurement and local governance
Elected trustee first-person vote account plus contemporaneous local news; board vote 5-2 on 2025-08-05Community Contract Termination
City of Evanston deactivated 19 Flock Safety ALPR cameras and issued a contract termination notice after an Illinois Secretary of State audit and Flock admissions regarding federal-user pilot permissions.
Reported consequence: All 19 city cameras deactivated; termination notice effective 2025-09-26 per city bulletin
System layer: procurement and local governance
Official city GovDelivery bulletin is primary; later reinstall/dispute reporting noted as follow-on context onlyCommunity Contract Termination
City of Cambridge issued an official statement terminating its Flock Safety ALPR contract after unauthorized reinstallation of cameras and related governance concerns.
Reported consequence: Official municipal contract termination statement
System layer: procurement and local governance
Primary is city newsroom statement; secondary NPR survey article names Cambridge among cancellationsCommunity Contract Termination
Columbia Heights City Council voted unanimously to cancel contracts with Flock Safety and remove the city's 12 license-plate-reader cameras after resident privacy concerns.
Reported consequence: Unanimous council cancellation; staff directed to disconnect and remove 12 cameras
System layer: procurement and local governance
Multi-source local journalism; council minutes PDF not attached in this passInsider Misuse / Unauthorized Purpose
The GBI alleged that five former Albany Police Department officers accessed retained Flock license-plate data on multiple occasions for non-law-enforcement purposes.
Reported consequence: Five former officers arrested on misuse-of-license-plate-data and violation-of-oath charges
System layer: access control and audit
Official GBI release reports charges following an Albany Police Department internal audit; investigation active; charges are allegations until adjudicatedUse the underlying data
Each row includes the failure class, system layer, reported consequence, evidence grade, key source, corroboration, and a status note. Cite the original source—not this page alone.