Fire Department Partially Encrypted

District of Columbia Fire and Emergency Medical Services

District of Columbia, District of Columbia

How we verified this

As of August 2026 DC Fire and EMS remains partly in the clear on the District of Columbia system — RadioReference shows "101 | 01 DISP | Fire Dispatch | D", "102 | 02 MAIN | Main Operations | D" and both EMS 1 and EMS 2 as plain D — while support, special-operations and administrative talkgroups, and contrary to some listings the Marine channel ("736 | 0C9 MARINE | Marine | D Enc"), are encrypted.

Checked against a primary source on 2026-08-09: radioreference.com . Encryption status changes without notice — confirm the current picture on the live RadioReference database before relying on it.

What you can do right now

Encryption Details

Encryption Type P25 AES-256
Scope All Operations except for Dispatch, Main Operations, EMS 1 & 2, Marine, and Incident 11-42.
Technical Details P25 AES-256

District of Columbia County Context

District of Columbia Fire and Emergency Medical Services isn't an outlier here: 3 of the 5 public-safety agencies we track in District of Columbia County are fully encrypted (60%), so most departments nearby have made the same move.

What This Means

This is a split system: certain talkgroups are encrypted while others remain in the clear, which means partial monitoring is still possible.

See encryption status nationwide Interactive map showing which US police departments have encrypted their radios. Open the encryption map →

Frequently Asked Questions

Is District of Columbia Fire and Emergency Medical Services radio encrypted?

Yes. District of Columbia Fire and Emergency Medical Services uses P25 AES-256 encryption. This is a split system: certain talkgroups are encrypted while others remain in the clear, which means partial monitoring is still possible.

Can I listen to District of Columbia Fire and Emergency Medical Services on a police scanner?

Partially. District of Columbia Fire and Emergency Medical Services encrypts some of its talkgroups while leaving others open, so some channels may still be accessible. Check RadioReference for specific talkgroup status.

Why did District of Columbia Fire and Emergency Medical Services encrypt their radio?

The standard justification nationwide is officer safety and operational security, regardless of whether a documented local incident ever required it. The tradeoff that follows is consistent too: public oversight drops, and reporters lose the ability to track fire department response as it happens.

Can District of Columbia County reverse the encryption decision?

It can. The radios support open and encrypted operation equally well, so this is a configuration and a policy, not a constraint — and policies set by District of Columbia County officials are policies those officials can revisit when constituents press for it.

What can I do about District of Columbia Fire and Emergency Medical Services encryption?

Put the question to whoever signs off on District of Columbia Fire and Emergency Medical Services's radio budget: why full encryption rather than a delayed feed or tactical-only channels? File for the recordings and the decision documents alongside it, and link up with neighbours and local reporters in District of Columbia County so the ask arrives as a group rather than a one-off.

Data source: RadioReference Wiki

Checked against a primary source on 2026-08-09 — see "How we verified this" above. Encryption status changes; confirm at RadioReference before relying on it.

Advertisement