Fire Department Partially Encrypted Added from published reports

Seattle Fire Department

King, Washington

How we verified this

Seattle Fire's own Fire Line announcement (August 18, 2026) states encryption began August 18 and that channels 1, 2, 3, 6, 7 and 8 would be fully encrypted by August 31, with dispatch channels 4 and 5 remaining fully accessible. Recorded as partial: completion is announced, not independently confirmed; RadioReference's PSERN listing (sid 11628) still showed those talkgroups unencrypted on 2026-10-12.

Checked against a primary source on 2026-10-12: fireline.seattle.gov . Encryption status changes without notice — confirm the current picture on the live RadioReference database before relying on it.

What you can do right now

My city went dark — now what? Step-by-step guide for residents of newly encrypted areas. What you can still monitor Fire, EMS, and surrounding-jurisdiction channels often remain open. Request the recordings FOIA templates for Seattle Fire Department radio archives. Reverse the decision Tactics from cities that successfully reversed police encryption.

Encryption Details

Encryption Type Algorithm not published
Scope Encryption of select PSERN channels began August 18, 2026; Seattle Fire announced channels 1, 2, 3, 6, 7 and 8 would be fully encrypted by August 31, 2026, while dispatch channels 4 and 5 would remain fully accessible (Seattle Fire announcement, August 18, 2026). RadioReference had not marked these talkgroups encrypted when checked on 2026-10-12.

King County Context

King County is a mixed picture: 1 of 5 agencies we track here are fully encrypted (20%), which means some neighboring departments are still audible on a scanner.

See every agency we track in King County → County encryption overview →

What This Means

Some of this agency's traffic is encrypted and some is not. What you can hear depends on the channel and on what the department is doing at the time.

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

Other Agencies in King

Seattle Police
Algorithm not published
Bothell Police Department
Algorithm not published
Bothell Fire Department
Algorithm not published
Renton Police Department
Algorithm not published

Frequently Asked Questions

Is Seattle Fire Department radio encrypted?

Only in part — Seattle Fire Department encrypts some of its talkgroups while leaving others open (algorithm not published). Some of this agency's traffic is encrypted and some is not. What you can hear depends on the channel and on what the department is doing at the time.

Can I listen to Seattle Fire Department on a police scanner?

Partially. Seattle Fire Department encrypts some of its talkgroups while leaving others open, so some channels may still be accessible. Check RadioReference for specific talkgroup status.

Why did Seattle Fire Department encrypt their radio?

Departments typically point to officer safety and operational security. Neither claim tends to come with evidence specific to King County; what's verifiable is what's lost — journalists can't monitor the encrypted share of fire department activity in real time, and coordination with agencies that stay unencrypted gets harder.

Can Seattle Fire Department's encryption decision be reversed?

Yes. Whoever makes this call for an agency like Seattle Fire Department can also unmake it; there's no technical lock-in. The approach that has worked elsewhere combines public-records requests, direct council pressure, and a coordinated local coalition.

What can I do about Seattle Fire Department encryption?

Start local: show up when local officials discuss the budget for Seattle Fire Department, and ask specifically why encryption was chosen over a delayed feed. File a FOIA request for recordings or policy documents, and connect with others nearby who want the same information — a coordinated ask carries more weight than an individual one.

Data source: fireline.seattle.gov, fireline.seattle.gov

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