AIPolicyTracker

AI incident ·

Jackson Township Police in Stark County, Ohio Briefly Detained Driver After Flock Safety Alert Matched Vehicle to Stale Missing-Juvenile Hot-List Entry

1 news report Synced from source · record last edited 17 Sep 2026

In brief

An AI system built by Surveillance technology developers, Flock Safety and 1 other and deployed by Law enforcement, Jackson Township Police Department (Stark County and 1 other allegedly harmed Road users, Motorists and 2 others.

Risk domain
Not classified
Occurred
Coverage
1 reportApr 2024

What happened

In March 2023, Jackson Township police in Ohio briefly detained driver Michael Smith after a Flock Safety license-plate reader matched his vehicle to an NCIC hot-list entry from a missing-juvenile investigation that Cleveland police had closed two weeks earlier. Officers released Smith after confirming the juvenile had already been found. A federal court later held that Flock matched the plate to law-enforcement data but did not create the stale entry.

Laws that address this harm

No recorded instrument yet addresses this use case where it happened. See the open queue.

Matched from the record's risk domain and country to the instruments recorded here. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (1)

Titles link to the original publisher; report text is not reproduced here.

  1. Smith v. Flock Safety, Memorandum of Opinion and Order
    cases.justia.com · Benita Y. Pearson

Who was involved

Alleged harmed party
Road users Motorists Michael Smith (Ohio driver) Drivers

AI systems implicated

Surveillance technologyLaw enforcement databasesFlock Safety automated license plate reader systemAutomated license plate readers (ALPR)

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Linked by editors or by text similarity in the source dataset.

Other incidents involving Law enforcement

Source record: incident #1694 on the AI Incident Database · all 1 report