MPD's license-plate cameras are scanning 400,000 tags a day. Nobody in D.C. will say who looked at the data, or why.

Every day, Metropolitan Police Department cameras scan roughly 400,000 license plates across Washington, D.C., logging tags, vehicle descriptions, and location data into a database that sits for up to 90 days. Who pulls from that database, and for what reason, is a question the department has refused to answer in any detail. This week, the refusal got harder to maintain.

The DC Police Union went public Thursday with an accusation that should unsettle D.C. drivers: MPD management, the union says, used data pulled from the city's Flock automated license-plate reader network to track a union member during an Internal Affairs investigation, without, the union argues, proper legal justification. The union filed a class grievance demanding the practice stop. MPD denied the grievance. Now the dispute heads to arbitration, and the union is doing something it almost never does: asking the D.C. Council to intervene.

What Flock actually is, and how big it already is

MPD operates 67 Flock automated license-plate readers across the District that scan roughly 400,000 tags a day, storing tag details and vehicle features in a database for up to 90 days, according to NOTUS. That retention window is longer than many jurisdictions allow.

The cameras read plates automatically, in real time, on streets throughout the city. The AI-powered license-plate readers can track vehicles across vast geographical areas in real time. There is no official map accessible to the public detailing where and how many police surveillance systems have been installed in the District. An independent tracker called Flock Camera Locations puts the number at at least 144 in the District.

The system has been in place since 2025. Until earlier this year, access to D.C.'s plate database was not limited to D.C. officers. For the entire year prior, MPD had allowed thousands of officers across the country nearly unfettered access to its database. And to this day, the department has declined to detail who has used the city's data, and why.

How this blew up

The police union says it filed misconduct complaints after discovering management had improperly used Flock camera data in July 2026. The union reportedly submitted a class grievance demanding that the violations stop, but managers denied the allegations.

MPD's response was terse. In a statement, MPD said their department has "a stringent policy regarding the use of license plate reader technology (LPR) that was updated in April 2026." The department confirmed a grievance was filed and added a line that the union found infuriating: the department's position is that the use of LPR in the misconduct investigation was appropriate, and this grievance involves a union matter that will be resolved through arbitration between MPD and the DC Police Union.

The grievance was denied. DC Police Union noted that the same day the grievance was denied, MPD issued a new teletype restricting department-wide access to the system. The union read that timing as an implicit concession, an acknowledgment that something needed fixing, even as management refused to investigate the people accused of crossing a line.

As the union put it: "Management responded by denying the grievance and refusing to investigate managers who were alleged to be violating the system."

The union's misconduct complaints remain active as of Thursday. The denied class grievance is proceeding to arbitration.

The union wants the Council. The union almost never wants the Council.

DC Police Union president Gregg Pemberton has spent years at war with the D.C. Council over police accountability laws. His call this week for the Council to step in is an unusual reversal.

He admitted even he's surprised he's asking for the D.C. Council, a legislative body the union has frequently clashed with, to weigh in on the matter.

He is calling on the D.C. Council to hold a public hearing and pass legislation to regulate the use of the data. His framing put the problem squarely on MPD management, not the cameras themselves. "For years, thousands of cameras have been operating across this city. The problem is not the camera," said Pemberton. "The problem is that the full capabilities of this system remain unknown, and the guardrails needed to prevent misuse have not been properly negotiated or implemented by MPD."

An email sent to the office of Brooke Pinto, the chair of the public safety committee, was not responded to.

Henderson: 'The police union has access to information the Council does not'

At-Large Councilmember Christina Henderson has been tracking Flock longer than most of her colleagues. At the start of 2026, after inquiries by Henderson, MPD stopped allowing other police departments to access its license-plate reader data directly. It now requires them to specifically request data from D.C., part of an effort to ensure the city's information is used for legitimate criminal investigations. MPD also instituted a new license-plate reader policy in April that requires an annual audit of the data for possible policy violations.

But Henderson says the reforms so far are not enough. "I think we're going to have a lot more questions, particularly when the council gets back about this issue because it does appear as though the Police Union has access to information the Council does not have at this point," said Henderson.

Henderson says MPD conducted an audit of the system's logs in August and she's awaiting those results. She'd also like MPD to audit logs prior to April's updated policy. That pre-April period matters: it covers the months when outside agencies could pull D.C. plate data freely, with no mechanism for accountability.

"Now we need to get to the transparency part of this in terms of sharing what you found," said Henderson. "This new revelation from the police department union will force the department to have these conversations sooner vs. later."

Henderson cautioned against getting rid of Flock cameras altogether, saying they can be important tools to help law enforcement investigate crimes. Her position is narrower: the cameras may stay, but the city needs real rules about who can search the database, on what basis, and with what consequences for misuse.

Why residents should care, beyond the surveillance debate

D.C. residents pay for this system, and their plates are in it. Every car parked on a public street, every commuter traveling through a Flock zone, generates a record. Pemberton says that currently the database can only be accessed when there is suspicion that a specific individual or vehicle is involved in criminal activity. The union's allegation is that management broke that rule when it turned the cameras on a union member in an Internal Affairs inquiry.

If true, that creates a second problem beyond civil liberties. It means the system built to catch criminals was used to surveil a police officer the department wanted to investigate. The union calls that abuse. MPD calls it appropriate. Neither answer is reassuring for residents whose tags are sitting in the same database.

The lawsuit landscape around these systems is also moving fast. The civil rights group Institute for Justice has filed federal class-action lawsuits against San Jose, California, and Norfolk, Virginia, arguing that Flock's camera networks amount to unconstitutional warrantless mass surveillance, per CBS News. D.C. currently has no local law governing how long plate data can be retained, who can access it, or what happens when access is abused.

The Council returns from recess on September 22. Henderson has already signaled this is on her list. Whether Brooke Pinto's public safety committee moves quickly is another question. As the union put it: "Public trust cannot be built through secrecy about this technology, and officer trust cannot be built by tightening rules on the rank-and-file while refusing to investigate the officials who abused the system."

The union is also considering additional challenges over how the new access rules are enforced and who is held accountable. That means more filings, possibly more public pressure, and a Council that will have to decide how much it wants to know about a surveillance system it never formally authorized through legislation.

What D.C. Residents Should Watch

• Brooke Pinto's public safety committee: The chair did not respond to the union's request for a hearing before the recess. Watch whether she schedules one after September 22, and whether the committee asks MPD to hand over the August audit results.
• Christina Henderson's audit demand: Henderson wants MPD to review Flock access logs going back before April 2026, the period when outside agencies had nearly open access. If MPD hands those logs over, the scope of use could look very different from what the department has described publicly.
• The arbitration: The union's class grievance is now in formal arbitration with MPD. That process is not public, but any ruling will set a precedent for whether management can use surveillance tools against the officers those tools are supposed to serve.
• No public map, no public policy: D.C. has not published a map of its Flock camera locations and has no legislation governing the system. A resident who wants to know whether a camera on their block logged their plate last Tuesday has no legal mechanism to find out.
• The Institute for Justice cases: Federal rulings in the San Jose and Norfolk suits could directly shape what D.C. is legally permitted to do with plate data, regardless of what the Council decides locally.

Sources

• Washington Post, Sept. 12, 2026
• WUSA9, Sept. 12, 2026
• WUSA9 (second report), Sept. 10, 2026
• NOTUS, Sept. 2026
• Hoodline, Sept. 11, 2026
• DC News Now, Sept. 10, 2026
• NBC4 Washington, Sept. 11, 2026
• Yahoo News / WAMU, Sept. 10, 2026