A growing share of Tampa Bay traffic stops begin with a camera rather than an officer’s observation. Automated license plate readers, most of them made by Flock Safety, photograph every passing vehicle, log the plate with the vehicle’s make, model, color, and location, and alert officers when a plate matches a hot list. St. Petersburg alone operates a citywide network of these cameras as of this writing. When a stop starts with a machine, the machine’s work becomes evidence, and evidence can be tested.
What the system actually does
A plate reader is a camera paired with software that converts an image into a plate number and checks it against lists: stolen vehicles, stolen plates, wanted persons, missing persons, and entries officers add themselves. When the software believes it has a match, it pushes an alert to officers in the area. Everything in that chain is recorded: the photograph, the read, the list entry that triggered the alert, the alert itself, and the searches officers later run against the stored data.
The alert is a claim, not a fact
Software misreads characters, confuses states, and alerts on entries that should have been removed. An alert is the beginning of the inquiry, and the officer’s job between alert and stop is verification: does the plate on the car actually match the plate on the list, is the entry current, and does the vehicle description fit. A stop still requires reasonable suspicion, and suspicion built on an unverified machine read is exactly the kind of foundation a motion to suppress exists to test. If the stop fails, what followed it usually falls with it.
The records the alert leaves behind
This is a records case before it is anything else, which is the way this office likes it. The alert record, the photograph the system took, the hot list entry and when it was added, the audit log showing who searched the plate and the reason they documented, and the agency’s retention policy on the date of the stop. As of this writing, St. Petersburg’s policy purges footage after thirty days and requires a documented purpose for every search, and outside agencies must make a written request for access. Those records reach the defense through discovery, and Florida’s public records law reaches much of the rest. The gap between what the report says and what the system logged is where these cases move.
Pretext, extension, and what the stop becomes
A lawful alert can still produce an unlawful encounter. A stop justified by a plate issue does not automatically authorize a search, a drug dog, or a DUI investigation, and dragging a plate stop out while officers fish for more runs into the rules on prolonged detention and pretext. Each step after the stop needs its own justification, and each step is tested separately.
The Constitutional Fight That Is Coming
Beyond any single stop sits a larger question: whether assembling a searchable, retrospective record of everyone’s driving is itself a Fourth Amendment search. The Supreme Court keeps moving in one direction on questions like it. In Carpenter v. United States, 585 U.S. 296 (2018), it held that accessing historical cell phone location records is a search, because people have a reasonable expectation of privacy in the whole of their physical movements. And in Chatrie v. United States, 609 U.S. ___ (2026), decided June 29, 2026, it extended that holding to Google Location History, describing the danger as retrospective surveillance that requires no effort, runs against everyone rather than only suspects, and travels back in time.
Every word of that description fits a plate reader network. No court has settled whether Carpenter and Chatrie reach ALPR databases, which means the argument is live, and a case built on a warrantless trawl through months of stored plate captures is a case where it belongs in the motion. That is a different attack than challenging the individual stop, and the two run together.
What This Summer’s Arrests Proved About the Logs
In roughly five weeks of 2026, three Florida officers were criminally charged over alleged misuse of these systems, one sheriff suspended his county’s Flock cameras outright, and one department learned about its own officer’s alleged conduct from a newspaper. The full account is in the firm’s Flock camera breakdown. Two things from those cases matter permanently on this page.
First, the charges themselves. The officers face counts under section 815.06, which makes it a felony to use a computer system in a way that exceeds authorization, and section 838.022, official misconduct by falsifying an official record. The falsified record in these prosecutions is the justification the officer typed when running the search. The State’s own charging theory treats the search reason field as an official record, and an official record is exactly the kind of thing a defendant is entitled to obtain and test.
Second, the granularity. The investigations reconstructed one officer’s searches going back to 2024, down to the count and the typed reason on each one. Whatever else those cases prove, they prove the logs are complete, detailed, and readable. An agency cannot produce that record to convict its own officer and then call it unavailable in discovery.
What We Demand When a Camera Started the Case
- The capture itself: the photograph, the plate read, the timestamp, and the location.
- The alert record, and the hot list entry behind it: what list, who added the plate, when, and whether it was still valid on the day of the stop.
- The search and audit log for the plate: every user who queried it, when, and the reason each one entered.
- The agency’s ALPR policy and retention schedule in force on the date of the stop.
- The officer’s account of verifying the plate against the vehicle before acting on the alert.
- Any records of misreads, maintenance, or known error patterns for the cameras involved.
The sequence the records reveal is the case. An alert on a misread plate, a stale entry nobody removed, or a stop that ran ahead of any verification is a defective foundation, and everything built on a defective foundation is subject to challenge.
Questions About Plate Reader Stops
Are Flock cameras and plate readers constitutional?
The courts have not settled it. The Supreme Court held in Carpenter v. United States in 2018 that accessing historical cell phone location records is a Fourth Amendment search, and in June 2026 it extended that reasoning to Google Location History in Chatrie v. United States. A plate reader database raises the same underlying issue, a warrantless retrospective record of a person’s movements. Whether those cases reach ALPR networks is one of the live constitutional questions in criminal courts right now, and it can be raised alongside a challenge to the individual stop.
What do the 2026 officer arrests mean for my case?
Three Florida officers were charged in 2026 over alleged misuse of plate reader and driver databases, and every one of those cases was built from the system’s own search log. That matters for defendants because it proves the logs exist, record who searched what and the reason entered, and are detailed enough to reconstruct years of activity. The same records exist behind the alert or search in an ordinary criminal case, and they can be demanded.
What is a Flock camera and what does it record?
Flock is the brand of automated license plate reader used across Tampa Bay, including a citywide network in St. Petersburg. The cameras photograph every passing vehicle and log the plate number, the make, the model, the color, and distinguishing details, with a timestamp and location. The system then checks plates against hot lists and alerts officers to matches.
Is a plate reader alert enough for police to stop me?
An alert by itself is a machine’s claim, and machines misread plates, mix up states, and act on stale entries. The stop still has to satisfy the Fourth Amendment, which means the officer needs reasonable suspicion connected to what is actually true. Whether the officer confirmed the plate visually before the stop, and whether the alert itself was accurate and current, are the first questions to test.
Can I find out whether a plate reader was used in my case?
Yes. The alert, the underlying hot list entry, the audit log of who searched what and why, and the retention policy are all records. They can be reached through discovery in the criminal case, and much of it is also subject to Florida public records law. A stop that looks spontaneous in the report often starts making sense once the ALPR record shows what the officer knew and when.
How long do agencies keep plate reader data?
It depends on the agency’s policy. As of this writing, St. Petersburg purges its Flock footage after thirty days, and searches require a documented law enforcement purpose. Retention and audit rules vary between agencies, which is exactly why the policy in force on the date of your stop is one of the records worth demanding.
Do plate readers matter in DUI cases?
They can. A DUI stop that begins with a plate alert rather than observed driving raises its own questions, because the reason for the stop shapes everything that follows, including whether the officer had any basis to extend the encounter into a DUI investigation. The same records discipline applies: get the alert, get the log, and test the stop against the rule that governs it.
In the News
Flock cameras in Tampa Bay: the misuse arrests, the runoff fight, and what the search logs mean
This page is general information about Florida law and police technology as of this writing, not legal advice, and it does not create an attorney-client relationship. Camera networks, retention policies, and agency procedures change; the policy that matters is the one in force on the date of your stop.
