Washington DC Police Scanner: Democracy Behind Closed Doors
DC Metropolitan Police encrypted all radio communications in September 2011. The Capitol Police moved to an encrypted P25 system in 2014, and the Secret Service and other federal agencies have long been encrypted. In the city where the First Amendment was written and where Congress meets, there has been no public scanner access to local law enforcement for over a decade.
The Seat of Democracy: Fully Encrypted
September 2011: DC goes dark
In September 2011, the Metropolitan Police Department encrypted all radio. Then-Chief Cathy Lanier said criminals used scanners to evade police and that terrorists could exploit them. No evidence was offered for either claim.
"What we are not willing to do is to give the media radios or share the encryption key."
— Chief Cathy Lanier, testimony to the DC Council, November 4, 2011WAMU and local journalists objected, arguing that scanner access was irreplaceable for breaking news and accountability reporting. The department didn't budge.
The federal agency wall
DC has more law enforcement agencies per square mile than anywhere else in the country. Nearly all of them are encrypted:
Metropolitan Police (MPD)
Fully Encrypted3,300+ officers serving DC residents
Since September 2011US Capitol Police (USCP)
Fully Encrypted2,300+ officers protecting Congress
Since February 2014US Secret Service
Fully EncryptedWhite House and presidential protection
Historically encryptedUS Park Police
EncryptedNational Mall and federal parks
Encrypted like other federal agenciesFBI Washington Field Office
Fully EncryptedFederal investigations
Historically encryptedDEA, ATF, Marshals
Fully EncryptedVarious federal enforcement
Historically encryptedJanuary 6, 2021: the communication failures
The Capitol attack exposed serious failures in police communications. Senate investigations found radio breakdowns contributed to the delayed response that allowed rioters to breach the building.
"USCP leadership never took control of the radio system to communicate orders to front-line officers."
"I was horrified that NO deputy chief or above was on the radio or helping us."
DC Police requested backup at least 17 times in 78 minutes during the riot.
The public and journalists could not monitor events in real-time due to encryption.
Communications were described as "chaotic, sporadic, and, according to many front-line officers, non-existent." Two incident commanders responsible for relaying orders to front-line officers were pulled into direct confrontations with rioters, making it impossible to do their jobs.
Encryption was supposed to protect officers. On January 6, it contributed to a communications collapse that left officers isolated while the public had no way to understand what was unfolding.
The national press: reporting without scanners
DC has the country's most concentrated press corps. The Washington Post, New York Times, AP, Reuters, and every major network bureau lost scanner access in 2011.
What DC journalists lost
- Real-time awareness of breaking incidents
- Independent verification of police activity
- Ability to reach scenes as events unfold
- Monitoring of police response to protests
- Documentation of police communications
What the public lost
- Immediate awareness during emergencies
- Independent record of police actions
- Real-time information during protests
- Accountability for federal responses
- Transparency in the nation's capital
RTDNA has called encryption its top issue, and DC is the most consequential example of what reporters lose when a department goes fully encrypted.
DC Fire and EMS: the reversal
In December 2014, the outgoing administration encrypted most DC Fire and EMS talkgroups — a move pushed by then-Deputy Mayor Paul Quander over objections that it would complicate regional coordination and cut off the public.
In February 2015, the new Bowser administration reversed course. City Administrator Rashad Young said the issue had been under review since before the mayor's inauguration, and that going forward unencrypted channels would be used for standard operations, with encryption reserved for incidents involving sensitive communications.
The reversal let DC firefighters and medics communicate seamlessly with neighboring jurisdictions again — and put fire/EMS traffic back within public earshot, where it remains today (you can hear it on OpenMHz). DC Fire and EMS learned what MPD has not: blanket encryption creates more operational problems than it solves. A hybrid approach can protect sensitive communications while keeping the interoperability that emergency response depends on.
DC's crime surge: encryption made no difference
DC has been encrypted since 2011. If encryption improved public safety, the city should show it. Instead, DC saw a steep crime increase in 2023:
Thirteen years of encrypted radio did nothing to prevent the 2023 crime spike. It only prevented the public from monitoring how police were responding. By 2024, violent crime started declining—due to other interventions, not encryption—but residents had lived through the surge with no independent access to information about what was happening on their streets.
One-way surveillance
While DC blocks public monitoring of police radio, local agencies have expanded their own surveillance capabilities with limited oversight:
- Facial recognition systems
- Automated license plate readers
- Social media monitoring tools
- Cell site simulators
The Community Oversight of Surveillance DC coalition has noted that "significant decisions about surveillance are happening in secret." Police monitor the public with growing technology; the public cannot monitor police at all.
The Office of Police Complaints: limited tools
DC established an independent Office of Police Complaints in 1999. Four of the five Police Complaints Board members must have no MPD affiliation. But the OPC cannot monitor police radio in real time. After an incident, it depends on:
- MPD's own after-action reports
- Citizen complaints
- Body-worn camera footage, subject to departmental release policies
- Official MPD accounts
The ACLU of DC has identified the "culture of opaqueness and resistance to transparency that permeates MPD" as a primary obstacle to accountability—pointing to FOIA denials, failures to collect required data, and refusal to follow OPC recommendations.
Protest coverage in DC
DC draws more political demonstrations than any other American city. Before 2011, journalists covering protests could monitor police positions, track crowd control tactics, document arrests, and verify or challenge what officers said happened. All of that disappeared with encryption.
When federal officers used chemical agents to clear Lafayette Square in June 2020, there was no public scanner access to document how that operation was coordinated. Journalists and the public had only what the government chose to release.
Regional interoperability: the MOU that explains the problem
The National Capital Region maintains a regional interoperability agreement involving cities, counties, federal agencies, and transit authorities — formal machinery that exists in part because encryption complicates coordination between jurisdictions.
The fix was more encryption—but with shared keys and common protocols. Agencies can now talk to each other. The public still cannot listen. FOIA exists, but records only become available after an incident is resolved—useless for real-time accountability.
Why DC matters nationally
What happens in the capital affects accountability everywhere
DC's encryption has consequences beyond the District:
- Every major national outlet has DC journalists—encryption affects all of them equally.
- Real-time monitoring of federal agency communications aids congressional oversight during crises.
- When DC police radio went dark, significant national events lost independent contemporaneous documentation.
- DC's approach shapes encryption decisions at federal installations in other cities.
What you can do
- Contact DC Council members — the council has direct oversight of MPD policy.
- DC residents lack full congressional representation, but your senators and representatives can push for federal agency transparency.
- Support DC outlets covering police accountability.
- Community Oversight of Surveillance DC is working on surveillance accountability citywide — connect with them.
- File FOIA requests documenting how encryption affected specific incidents.
- Advocate for a credentialing program like San Francisco's media access model as a minimum step.
Take Action for Transparency
Your voice matters. Here are concrete ways to advocate for open police communications in your community.
Contact Your Representatives
Use our templates to email your local officials about police radio encryption policies.
Get StartedRead Case Studies
See how encryption has affected real communities - from Highland Park to Chicago.
View CasesSpread Awareness
Share evidence about police radio encryption with your network and community.
Public Testimony
Learn how to speak effectively at city council and public safety meetings.
Prepare to SpeakRelated Resources
Sources & Further Reading
- DC Metropolitan Police Department: "The Encryption of Metropolitan Police Department Radios" (2011)
- US Senate Homeland Security and Rules Committees: "Examining the U.S. Capitol Attack" (June 2021)
- US Capitol Police Inspector General Reports
- WAMU: "D.C. Police To Encrypt Radio Communications" (August 2011)
- Washington Post: "Last of the Scanners" (December 2018)
- CISA: "Ensuring Interoperable Encrypted Communications" (August 2024)
- Mayor's Office: "New Radio Encryption Protocol for First Responders" (2016)
- Council on Criminal Justice: "Crime in Washington, DC" (2024)
- ACLU of DC: Community Oversight of Surveillance
- CNN: "Radio Dispatches and Security Footage" from January 6 investigations