ALPR and Flock Camera Stops in Florida: When a Plate Reader Starts the Case

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.

That is not a hypothetical risk. In August 2026, body camera video from Wisconsin showed officers stopping a family at gunpoint on an interstate after a Flock alert flagged their car as connected to a homicide investigation. The vehicle had already been investigated and cleared, and Milwaukee police said human error had left the alert in the system. Nobody in the car had anything to do with the case. Whether an entry is current, who created it, and when it should have come out of the system are questions the system’s own records answer, and they are on the demand list below.

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. That thirty days is now a question rather than a safe assumption. On August 13, 2026 Flock cut its DEFAULT retention from thirty days to seven, and existing agencies keep whatever period they already had unless they opt into the new standard, so two departments on the same network can be holding the same week of captures for very different lengths of time. The only reliable answer is the retention setting that agency had in force on the date of the stop, which is a discovery question rather than something to be assumed in either direction. 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 camera on private property, and the statute that does not reach it

Florida does have plate reader statutes, and they cover less ground than their names suggest. Section 316.0777 authorizes an automated license plate recognition system to be installed within the right of way of a road on the State Highway System, at the request of a law enforcement agency, and it forbids using one to write a traffic citation. The confidentiality it creates, and the retention limit it borrows from section 316.0778, attach to records held by an agency.

That word is doing the work. A homeowners association is not an agency. Neither is a condominium board, an apartment company, or the management firm that runs a retail lot. When the camera at the gate belongs to the property rather than the police, the installation rules in 316.0777 were not written for it, the public records exemption was not written for it, and the retention schedule was not written for it. The rules that apply instead are the lease, the association documents, and the vendor contract, and none of those are voted on by the people being recorded. As Rory put it to Jacksonville Today in August 2026: “There are statutes that govern Flock for public roads, but there are not for HOAs, condominiums, apartments. If you are an apartment tenant, you cannot opt out.”

For a case, the practical difference is where the records live and how you reach them. When a public agency runs the camera, the data sits with a government body, the statutory retention cap applies, and the ordinary discovery and public records paths are open. When a private operator runs it, the images and the search history sit with a company and its vendor, the retention period is whatever the contract says, and getting any of it takes a subpoena aimed at the right party. The first question in a case that started with a plate alert on private property is therefore not what the camera saw. It is who owns the camera, who was given access to it, and how long anything is kept.

The scale is not small. Jacksonville Today reported in August 2026 that the Jacksonville Sheriff’s Office operates roughly 150 Flock devices in Duval County, that Flock has about 120,000 devices nationally, and that Fundrise, a company managing roughly 9,000 residential units and holding about $23 million in Flock investments, has cameras at two of its Jacksonville properties. A tenant in that situation may be living behind a camera operated by a landlord with a financial stake in the network.

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.

The pressure on the network is no longer only judicial. On August 26, 2026, Governor DeSantis called license plate reader use in Florida “out of control,” saying the technology has expanded far beyond toll collection into criminal surveillance, and warned against creating a surveillance state. He said statewide restrictions would have to come from the Legislature, and that he is reviewing another state’s approach as a possible model. The rules on who may search, for what reason, and for how long the data lives are now an open legislative question in Tallahassee.

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.

If a plate reader stop led to charges in St. Petersburg, see our St. Petersburg DUI and criminal defense page for help with the case.

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.

The plate reader that flies, and why it is a different legal question

Everything above describes a camera bolted to a pole. As of this writing the same company sells an autonomous drone, and it changes what a plate reader is.

The system is marketed for what the industry calls Drone as First Responder, meaning the aircraft launches on a dispatched call and arrives before a patrol unit does. The manufacturer states the aircraft is American made, flies at speeds up to sixty miles per hour, and carries a camera that can read a vehicle license plate from two thousand feet. It reports deployment across more than two hundred agencies.

Closer to home, agencies around Tampa Bay have moved to expand drone programs, with county agendas describing the purpose in terms of locating offenders, apprehension operations, and coordinated federal enforcement activity. At the federal level the technology is under review rather than under rule. In August 2026 the President said the question was being studied and that an administration position would follow. No ban was announced and no position was stated. The company’s own chief executive has described the environment as very little state regulation and zero federal regulation outside of air safety.

Why the aerial version is not just a higher pole

The older aviation cases that permit police observation from the air were decided on facts that look nothing like this. They involved a human being in a manned aircraft, flying where any member of the public could lawfully fly, looking down during a discrete overflight, and seeing what was plainly visible. The reasoning turned on the exposure of a thing to public view from a place the public could occupy.

A persistent autonomous aircraft that reads and records plates from two thousand feet is a different proposition, and it makes the Carpenter and Chatrie argument described above stronger rather than merely restating it. Aggregation is the first reason. A single overflight reveals a moment, and a camera that flies every day builds exactly the retrospective record of movement those cases treat as a search. The second is that the public exposure rationale assumes a member of the public could have seen the same thing, and no member of the public reads plates from two thousand feet, at sixty miles an hour, automatically, and stores the result. The third is cost. The older cases assumed surveillance was self limiting because it was expensive, and automation removes that limit.

None of this is settled in Florida. It is the argument, and it has to be preserved in the trial court to be worth anything later.

The records an aerial stop leaves, which are not the records a pole leaves

A drone initiated contact generates a different file than a fixed camera does, and the requests have to be written for what actually exists. That includes the dispatch record that launched the flight and the reason recorded for it, the flight log with times, altitudes and track, the video and still imagery from the aircraft rather than only the plate photograph, the retention and deletion schedule that applies to aerial footage as opposed to fixed camera data, the operator identity and certification, and the audit trail showing who later searched or exported any of it.

Ask for all of it early. Aerial footage is frequently held under a shorter retention schedule than the plate database, and a record that is gone by the time it is requested cannot be examined by anyone.

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.

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.