Flock Camera Got It Wrong — Police Stopped the Wrong Person #flocksafety #flockcameras #flockcameras
The short version: A viral clip from OMFnG Tee's shows how a bad Flock ALPR match escalated straight to a police stop of an innocent driver — proof that 'the algorithm flagged it' isn't probable cause.
Our Take
Credit to OMFnG Tee's for putting a face on what watchdogs have been warning about for years: these camera networks don't just passively log plates, they actively generate suspicion, and that suspicion gets acted on by officers with guns and handcuffs before anyone double-checks the data. A misread plate, a stale hotlist entry, a similar-looking car — any of it can turn a commute into a felony stop. The tech is marketed as precision policing, but the reality is a probabilistic guess dressed up as certainty.
The deeper issue isn't just that Flock's system got one match wrong. It's that there's no meaningful friction between an automated alert and a human being being pulled over at gunpoint. Departments treat the hit as confirmation rather than a tip that still needs verification, and the driver on the receiving end has zero visibility into why they were stopped, what database flagged them, or how to get it corrected. That asymmetry — a black-box system on one side, a person with no recourse on the other — is exactly why 'if you've got nothing to hide' arguments fall apart. Everyone is exposed to the same error rate.
If you want to know whether your own neighborhood is wired up with this kind of always-on tracking, check our camera map, and if you'd rather do something about it than just worry about it, our take-action page has concrete steps for pushing back at the city council level, where these contracts actually get approved.
This is DeFlock The USA’s original commentary. The video above is the work of OMFnG Tee's, published on YouTube — full credit to the creator.