A Colorado man without a warrant is repeatedly flagged by Flock ALPR cameras as wanted; police have now removed him from their hot list.
Key Takeaways
Flock Safety cameras flagged a Colorado man’s plate as matching an active warrant repeatedly, causing police stops despite no warrant existing.
Police chief confirmed the man was manually removed from the Flock hot list, implying no automated correction occurred.
The fix was reactive and manual, not systemic, leaving the underlying data integrity problem unaddressed.
Hacker News Comment Review
The root cause is a Colorado law enforcement practice of entering plates in warrant databases with both letter-O and zero variants, producing false hits; commenters argue this is a data hygiene failure, not a camera or AI failure.
Commenters note ALPR systems triggering stops based on missing or mismatched third-party data (registration, warrants) is not rare; at least one commenter reports two prior stops from the same class of ALPR error.
Skepticism about Flock’s accountability: commenters suggest multi-million dollar libel suits targeting C-suite and board members as the only meaningful lever, given no automated remediation exists.
Notable Comments
@pj_mukh: Colorado practice of dual O/zero plate entries in warrant lists is the proximate bug; headline obscures this as a Flock problem.
@kevin_thibedeau: Reports two personal ALPR-triggered stops over invalid registration data; argues libel suits against executives are the right remedy.
