Cases › operational mistake › LR-2026-0650
Flock camera misread leads to armed police stop of driver of a Range Rover in Plymouth, Minnesota
Preliminary Why: 1 report: Futurism · subject to change · 1 independent report
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: no action reported
No source states: loss or records, developer and model, agent tool, could do, deployer, industry.
Severity major: Test: many third parties (a stated count of two or more affected parties). Fact: the source states four other 34 ## DTM cars were being tracked around Minnesota that week.
A car reviewer testing a Range Rover went out for errands with his wife on a Sunday afternoon in late June in Minnesota. Police had been tracking the car for days using Flock license plate cameras and boxed it in at a Kohl's parking lot. The alert rested on a plate recorded as 34 DTM, while the car's New Jersey manufacturer plate was 34 03 DTM, and the system did not read the small middle number. Officers learned the cause after the driver reached Jaguar Land Rover by phone. The police report later recorded that the plate had been reported lost, not stolen, and that it was entered incorrectly. The sources state the driver and passenger were cooperative during the stop. Jaguar Land Rover then moved to have the originating police department correct its report so the Flock system would be updated.
What happened
What was done
No source states an action or fix.
Risks
Primary63 incidents
Rising: 5 vs 2.2 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
HarnessTool allow-list · Fail-closed defaults · Stop control
ApplicationHuman approval for high-impact actions · Change review and separation of duties · Least-privilege access for the agent · Production kept apart from test · Activity logs · Adversarial testing before deployment
Infrastructure / targetSimilar incidents
Evidence
- Cause a defect in its training or retrieval data
No source states: what the AI was doing, what it reached or did, how it was caught, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off, what was done.
Show the full account: 2 items from the primary sources
What happened, in order
- late June The driver took the Range Rover out for errands on a Sunday afternoon.
Not dated in the sources:
- Police tracked the car for days using Flock cameras.
Show every field, with its source and grade
The AI system
What happened
Impact
Notes on gaps
The sources do not state a remediation by Flock or by police for this incident; a Plymouth suppression step is mentioned only in the CEO interview and is not recorded as a remediation. Control links rely on the driver's account and the CEO interview. Control C3 is taken from the press account of the AI not registering the small number. No money, record counts or durations are stated and none are given.
LR-2026-0650 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON