Flock Tracked the Wrong Driver— 4 Cops Surrounded Him #policeaccountability #thinbluelies #bodycam

Our Take

Credit to Thin Blue Lies: Exposing Misconduct for surfacing this one, because it's the clearest illustration yet of what happens when a license plate reader hit is treated as gospel instead of a lead. Joel Feder wasn't driving a stolen car. He was driving a manufacturer press loaner with a plate that a national database had apparently entered wrong, dropping the middle digits so "34 10 DTM" became "34 DTM." That's not Feder's mistake, and it's not even necessarily Flock's mistake. It's a data-entry error somewhere upstream that got fed into a system built to generate automatic alerts, and once it did, it apparently kept flagging the same innocent driver for days.

The part that should bother everyone, including people who otherwise trust the police, is the sequence: four cars, a box-in, a "you are not free to leave" moment, and only afterward does anyone check whether the alert was accurate. Flock's own talking point is that these hits are supposed to be one input among many, not the whole investigation. But when the response to an alert is a felony-style stop before verification, that talking point isn't matching practice on the street. A wrong keystroke in a database shouldn't be able to summon four patrol units around a citizen who's done nothing.

This is exactly the kind of failure mode we track: opaque databases, automated alerts, and departments that lean on the technology as if it can't be wrong. If you want to see whether these cameras are watching roads near you, check our camera map, and if you want to push back on how your local agency uses this stuff, our take-action page is a good place to start.