Utah Hive Politics logoUtah Hive Politicsfrom the publisher of The Weber County HiveThe people's publication. We investigate what's best for the public as a whole, not any party or special interest.
Surveillance · SV 100.03← All Surveillance articles · ← Hive library (every repo)
Article 3 of 6

The Camera Said "Match." Police Drew Their Guns.

Flock alerts and vehicle-location records have helped police solve real crimes. They have also put innocent people at gunpoint. "Flock was wrong" isn't always technically accurate — sometimes the camera worked exactly as designed, and something else in the chain failed instead.

Posted Aug. 18, 2026 · Updated Oct. 7, 2026 · Page look updated Nov. 2, 2026

2×
gunpoint stops of the same innocent woman, one week apart
$25
value of the package a Rivian owner was accused of stealing
0
times any camera in these cases actually misread a plate
After
when audits happen relative to the stop
Start Here

What an alert actually establishes — and what it doesn't

Before the cases below, it's worth being precise about what a Flock match actually is.

An alert can establish:

  • A camera recorded a plate resembling a target plate
  • At a particular time
  • At a particular location
  • Associated with a database entry

It does not, by itself, establish:

  • Who was driving
  • Whether the database entry is still valid
  • Whether the plate was cloned
  • Whether the vehicle owner committed a crime
  • Whether the observation supplies reasonable suspicion or probable cause on its own
The Taxonomy

Not every failure is the same failure

Filter by category. The cases below map onto different rows in this table — which is the point.

OCR misread
The camera read the plate characters incorrectly.
Camera/Database
Wrong state
Correct characters matched a plate registered in a different state.
Camera/Database
Stale hotlist
A plate stayed flagged after it should have been cleared. (Newell)
Camera/Database
Vehicle transfer
Plate or vehicle ownership changed since the flag was entered.
Camera/Database
Database error
Incorrect information was entered into a hotlist in the first place.
Camera/Database
Human inference
The camera accurately recorded a car; police incorrectly concluded its owner committed the crime. (Elser)
Human judgment
Verification failure
Officers acted before independently confirming the alert.
Access & verification
Account/access failure
An unauthorized user searched accurate data for an improper purpose — a different problem from either case below.
Access & verification
Case 1

Amber Newell: stopped at gunpoint twice in one week

Brookfield, Wisconsin — August 6, 2026. The camera worked. The alert behind it didn't.

AN

Amber Newell

I-94, Brookfield, WI — Aug. 6, 2026, ~4:45 PM

"I haven't been asleep since this has happened. Every time I close my eyes, all I can see is guns."
— Amber Newell, to FOX6 Milwaukee
What happened: Video from I-94 showed multiple officers with guns drawn and a passenger's hands out the window. Brookfield officers contacted the Milwaukee Police Department to verify the homicide alert — MPD said the vehicle and its occupants were no longer of interest, and Newell and her passengers were released. This was the second time that week: Newell says she was stopped at gunpoint in Milwaukee days earlier, towed, and released with no explanation. Milwaukee police confirmed staff had failed to remove the wanted-vehicle alert from the system after the investigation no longer needed it — calling it a personnel issue, "not a Flock issue." Brookfield Police Chief Christopher Garcia defended the stop, saying his officers "clearly had sufficient information and objective facts to support taking the actions they did." Milwaukee Police Chief Jeffrey Norman has separately defended the technology generally. Flock told FOX6 its readers capture images in public view, don't use facial recognition, require documented search reasons, and create permanent audit records — all true statements that don't address why a cleared alert stayed live.
Case 2

Chrisanna Elser: "it is a lock, there is zero doubt"

Bow Mar / Fort Logan, Colorado — September 27, 2025. The camera worked here too. What failed was the conclusion an officer drew from it.

CE

Chrisanna Elser

Fort Logan, Denver, CO — Sept. 27, 2025

"You know we have cameras in that jurisdiction and you can't get a breath of fresh air, in or out of that place, without us knowing, correct? ... Just as an example, you've driven there about 20 times in the last month."
— Sgt. Jamie Milliman, Columbine Valley Police Dept., per Elser's doorbell camera (Colorado Sun)
What happened: Flock cameras in the town of Bow Mar had captured Elser's forest-green Rivian passing through between 11:52 a.m. and 12:09 p.m. on the day a $25 package was stolen from a porch. Sgt. Jamie Milliman told her, "It is locked in. There is zero doubt. I wouldn't have come here unless I was 100% sure," and handed her a court summons — without showing her the Flock footage or the doorbell video he claimed showed her stealing the package, and without reviewing the dashcam footage from her own Rivian that showed her exact route. She had, in fact, driven through Bow Mar that day — to a tailor appointment, more than a quarter mile from the theft the entire time. Weeks of her own evidence-gathering (tailor surveillance footage, her truck's onboard cameras, GPS logs) got the summons voided by the police chief, who wrote her: "After reviewing the evidence you have provided (nicely done btw), we have voided the summons." Milliman was later reprimanded for "rude" and "dismissive" behavior and ordered to complete de-escalation, community-relations, and interviewing training within 30 days.
Case 3

Lindsey Isaacs: 13 days in jail over a car that wasn't damaged

Volusia County, Florida — crash Oct. 4, 2025; arrest April 17, 2026. Added Oct. 2026. Once again the camera recorded a real car. The conclusion drawn from it was wrong.

LI

Lindsey Isaacs

Near DeLand, FL — Florida Highway Patrol investigation

What happened, as reported by InvestigateTV/Gray Television (Sept. 14, 2026): Florida Highway Patrol investigators looking into a fatal Oct. 4, 2025 crash that killed three people focused on Flock camera captures of Isaacs' black Dodge Durango, including one camera about three miles west of the crash site. She was arrested April 17, 2026 on three counts each of vehicular homicide and leaving the scene of a deadly crash, was initially denied bond, and spent 13 days in jail. Her Durango had no damage. Paint transfer on the victims' vehicle and witness descriptions pointed to a maroon Durango, with a partial plate matching a different vehicle. All charges against her were dismissed May 22, 2026, and the driver of a maroon Durango was arrested; he has pleaded not guilty. Isaacs has filed a civil action against the two investigating troopers; those claims are allegations, not findings.
What Officers Are Supposed To Do

The verification step that's supposed to sit between an alert and a stop

Weber County's own current ALPR policy text wasn't found published online in this search — a direct GRAMA request is the way to confirm its exact language. What follows is the near-identical Lexipol template language used by Utah County Sheriff's Office, Emery County Sheriff's Office, Murray PD, and Nephi PD — all under the same statute, §41-6a-2003, that governs Weber County.

  • —"An ALPR may be used in conjunction with any routine patrol operation or official investigation. Reasonable suspicion or probable cause is not required before using an ALPR." — standard language across every Utah agency policy found in this research
  • —Utah Code §41-6a-2003 limits WHEN an ALPR can be used (active investigation, outstanding warrant, missing person, stolen vehicle) — it does not require verification before officers act on what the system returns
  • ✓"If practicable, the deputy should verify an ALPR response through the appropriate law enforcement database before taking enforcement action that is based solely upon an ALPR alert." — Utah County Sheriff's Office Policy 426(e), identical language in Utah DPS Policy 639
  • —"If practicable" is doing real work in that sentence — it is a should, conditioned on practicality, not a shall
  • —No Utah policy found in this research requires dispatch to independently reconfirm an alert's currency before officers are dispatched to a stop
  • —No policy found requires a second high-risk stop on the same person to trigger automatic review — which is exactly what happened to Newell
The Timing Problem

Why audits don't prevent the encounter

Utah requires a 5-year audit record of every search — crime type and incident number included, per §41-6a-2005. That record answers "who searched, and why" after the fact. It does the driver at gunpoint no good in the moment.

1Alert issued
2Officer receives it
3Stop occurs
4Person detained
5Report completed
6Audit, maybe, later

The audit trail can establish responsibility after the fact. It is not built to stop officers from acting on bad information in step 2.

What Each Fact Actually Proves

The evidence-strength ladder

Both cases show the same gap: a fact low on this ladder was treated as if it belonged near the top.

Plate imageA plate-like image was captured
OCR resultSoftware interpreted the characters
State matchSystem associated an issuing jurisdiction
Hotlist hitCharacters matched an entry — Newell's alert was accurate at match time, stale in substance
Vehicle descriptionVehicle may correspond with the entry
Registered ownerIdentifies legal registration — not necessarily the driver
Location historyVehicle appeared at recorded locations — this is all Elser's case ever had
Independent evidenceMay connect a specific person to criminal conduct — never obtained in Elser's case
Probable causeLegal basis for arrest or search
A plate match is the beginning of an investigation — not the conclusion.
The Throughline

No camera in these cases misread a plate. In Newell's case, an accurate camera fed a stale alert into a network with no automatic check on whether a cleared vehicle was still live. In Elser's case, an accurate location observation became a human conclusion nobody verified before a summons was issued. Lindsey Isaacs' case repeats Elser's: an accurate capture of the wrong car, treated as an answer instead of a lead, while the physical evidence pointed elsewhere. Different failures, same lesson: the technology can work exactly as designed and someone can still end up at gunpoint, or in court, over nothing.

Sources

Part of a nine-part series on ALPR and privacy oversight in Weber County. ← Article 2: Nobody Approves Each Search  |  Article 4: The GRAMA Gap →

Utah Hive Politicsfrom the publisher of The Weber County HiveIndependent · Accountability · Journalism

The Weber County Hive and Utah Hive Politics: the people's publication. We investigate what's best for the public as a whole, not for any party or special interest group. We report public records. You decide.

Send a tipTips we checkedSee a mistake? Tell us

We never name tipsters. When we correct a page, the fix and its date are shown on the page.

All Surveillance articles · Master Index (Hive library) · Read on Substack