A police stop may begin with an alert that the driver never sees. An officer receives notice that a camera recorded a plate connected to a stolen vehicle, an outstanding warrant, a reported crime, or a prior investigation. Minutes later, the vehicle may be surrounded, searched, or followed to another location.
Flock cameras and automatic license plate readers can supply useful information, but a database match does not prove who was driving, why the vehicle was present, or whether the alert was accurate. A defense attorney should trace the alert to its source, compare it with the officer’s observations, and determine whether police had lawful grounds under state law for each action that followed.
An automated license plate recognition system, usually called an ALPR system, uses fixed or mobile cameras and computer software to read plates within view. It converts the plate image into text and associates it with the date, time, location, and camera number.
Flock Safety is one company that sells this technology. People often use “Flock camera” as a general name for roadside plate readers, but not every ALPR camera is a Flock device. The Los Angeles Police Department operates its own ALPR program.
According to LAPD’s Automated License Plate Recognition Usage and Privacy Policy, its cameras collect a plate photograph, the date, time, location, and camera number. The department permits ALPR use for criminal cases, missing-person investigations, public safety threats, and other authorized purposes. The camera records a vehicle’s plate. It does not identify the driver.
License plate reader cameras may be fixed along roadways or mounted on a patrol vehicle. LAPD procurement materials also refer to Axon Fleet 3 ALPR licensing. A business, shopping center, homeowners’ association, or local agency may install a camera near a parking lot entrance or neighborhood roadway.
Law enforcement agencies use plate readers in two main ways. A live system may compare passing plates with a “hot list” and notify an officer of a possible match. Investigators may also search historical data to learn where and when a plate was recorded.
A live alert may report that a vehicle was stolen, connected to a wanted person, or listed in another law-enforcement database. Historical searches may follow a robbery, burglary, shooting, drug investigation, or other reported offense.
One result may lead officers to conduct surveillance, seek a warrant, or stop the vehicle when it appears again. The defense should examine the source of the plate number and what police confirmed before acting.
LAPD’s policy states that ALPR data, by itself, does not establish probable cause to arrest. It directs personnel to conduct further investigation and attempt to verify information such as the vehicle’s make, model, and color before an investigative stop.
A computer alert is an investigative lead, not a final identification. The software may misread a plate, the hot-list entry may be stale, or the listed vehicle may not match the vehicle in front of the officer.
The Ninth Circuit addressed an erroneous alert in Green v. City and County of San Francisco. The system misread one digit of a woman’s plate and linked her burgundy Lexus to a stolen gray GMC truck. Officers did not visually confirm the plate before conducting a high-risk stop. The court held that a jury could find a Fourth Amendment violation.
The Ninth Circuit later relied on Green in Chinaryan v. City of Los Angeles, which also involved a mistaken stolen-vehicle report and a high-risk stop. Officers must account for conflicting information before escalating a detention.
Don't face
the prosecutor alone
ALPR systems rely on camera images and software interpretation. Dirt, glare, darkness, plate frames, damaged characters, temporary plates, similar letter-number combinations, and poor viewing angles may affect a read. A camera may capture the correct plate while the database supplies outdated information.
A stolen vehicle may have been recovered. A warrant may have been recalled. A plate may have been entered with one incorrect character. An agency should correct, cancel, or suspend an alert when the underlying basis no longer exists.
A defense review may seek:
The original image may show a software error. Dispatch traffic may establish that an officer received information contradicting the alert but continued with the stop. A later report may not mention that conflict.
A plate generally leads police to registration information. It does not establish that the registered owner was driving when the scan occurred. Family members share cars, and employees drive company vehicles. Rental cars, borrowed vehicles, and vehicles with multiple owners create added identification problems.
The United States Supreme Court held in Kansas v. Glover that an officer may, in some circumstances, infer that a registered owner is driving. The officer knew the owner’s license had been revoked and had no information indicating that someone else was behind the wheel. The Court also recognized that additional facts may weaken or defeat that inference.
The ruling does not make the owner responsible for everything connected to the vehicle. It does not prove who possessed an item inside, who drove earlier, or who committed an offense near a camera. The prosecution still needs evidence linking the accused person to the charged conduct.
A traffic stop is a seizure under the Fourth Amendment. Police generally need reasonable suspicion that a traffic or criminal violation occurred. The standard is lower than probable cause, but the suspicion must rest on objective information.
An accurate alert for a currently stolen vehicle may support a stop. A partial plate match to a common vehicle, an old investigative note, or a scan near a reported crime may require more. The officer’s knowledge at the moment of the stop controls. Information found later does not repair a detention that lacked lawful grounds when it began.
The defense should identify what the stopping officer knew. The officer may not have seen the source image, hot-list reason, or a warning that the alert needed confirmation. The report should be compared with dispatch messages, body-camera footage, in-car Axon video, and the original ALPR image.
Police may also follow a vehicle until they observe a traffic violation. Recordings may show that the reported violation did not occur or was added later.
Even when police lawfully stop a vehicle, they do not receive unrestricted authority to search it. Officers need consent, probable cause, a warrant, or another recognized exception.
An ALPR alert placing a vehicle near an earlier crime does not necessarily establish probable cause that evidence is currently inside. The time between the scan and stop, reliability of the report, vehicle description, and additional observations all affect the analysis.
Police may use an alert to ask questions, request consent, deploy a dog, or prolong the detention while another unit investigates. Each extension requires legal support. Under California Penal Code Section 1538.5, a defendant may seek suppression of evidence obtained through an unreasonable search or seizure.
A live alert differs from a database search covering weeks or months. Repeated scans can reveal visits to a home, workplace, medical office, religious institution, or political gathering.
The Ninth Circuit considered historical ALPR information in United States v. Yang. An inspector searched a commercial database and used a scan to locate an overdue rental vehicle. The majority held that the defendant lacked a reasonable expectation of privacy in that vehicle under the case’s facts. It did not resolve every Fourth Amendment issue raised by warrantless ALPR database searches.
As camera networks grow throughout Southern California, courts may distinguish a limited query from a detailed record of a person’s travel. The number of scans, search period, geographic range, data source, and investigative purpose may affect a challenge.
California regulates ALPR access, security, and sharing. Civil Code Section 1798.90.52 requires an operator that provides access to maintain a record showing the date and time, search terms, username, affiliated organization when applicable, and purpose of the access. Information may be used only for purposes authorized by the operator’s published policy.
Under Civil Code Section 1798.90.55, a public agency may share ALPR information only with another public agency and only when otherwise permitted. LAPD’s policy states that department data may be shared with local law-enforcement agencies that have an interagency agreement.
The California Attorney General has taken the position that “public agency” does not include federal or out-of-state agencies. In January 2026, the Attorney General continued litigation against El Cajon over allegations that its police department shared ALPR information with more than 100 out-of-state agencies. The state also alleges that data sent outside California can later reach federal agencies beyond California’s privacy controls. The allegations have not resulted in a final ruling on the merits.
These restrictions also have immigration consequences. California Department of Justice guidance states that law-enforcement databases, including ALPR systems, must be governed so their use for immigration enforcement is limited to the fullest extent practicable and consistent with state and federal law. A plate history may reveal where someone lives, works, worships, receives medical care, or takes children to school.
Improper sharing does not automatically require dismissal. It may affect discovery, suppression arguments, and how officers obtained the information.
California law and LAPD policy require records of database access. LAPD states that end-user activity, including queries, must be retained for at least five years. Its logs should identify the date and time, plate number or search terms, username, and authorized purpose.
These records may show who searched the plate, what was entered, which agency supplied the result, and whether an outside agency received the data. A query conducted before the event that supposedly justified it may indicate an unrelated investigation. Search histories may also expose gaps in the prosecution’s timeline.
A screenshot in a police report is not the complete ALPR record. The defense may need the native image, metadata, camera identifier, hot-list record, audit log, search results, and records showing how the information was exported or shared.
LAPD generally retains ALPR data for two years before logical deletion. Its policy provides for permanent deletion after five years, 24 hours, and one minute, subject to exceptions for prosecutions and administrative proceedings. Investigators may request extended retention when data has evidentiary value.
A preservation request may reduce the risk of routine deletion. Discovery should also address information held by Flock Safety, Axon, another vendor, a private camera operator, or another agency.
At trial, prosecutors must authenticate ALPR evidence under California Evidence Code Sections 1400 and 1401. They may need testimony or records explaining how the system operated and how the offered exhibit relates to the original data. Admission does not require the jury to accept the prosecution’s interpretation.
Flock cameras and license plate readers can shape a case before an officer contacts a driver. William S. Kroger Criminal Defense Attorney at Law can seek the source image, hot-list record, dispatch traffic, access logs, retention history, and records showing whether officers confirmed the alert before acting.
A Los Angeles criminal defense lawyer should review every stage between the first camera scan and the final search or arrest. Contact William S. Kroger by calling 323-655-5700 or using our contact form to discuss the surveillance used in the investigation and the available grounds for challenging the evidence.
Every case deserves
a strong defense
"*" indicates required fields
