Fire Department Fully Encrypted

Lake County Fire/EMS

Lake, Indiana

What you can do right now

Encryption Details

Encryption Type P25 AES-256
Scope All Encrypted Countywide Fire operations talkgroups
Technical Details P25 Phase II AES-256

Verified Talkgroup Data

Verified Mar 6, 2026 Moderate confidence
188 Total Talkgroups
6 Encrypted
3 Mixed
179 Unencrypted
4% Encrypted
Radio System: Diga-Talk, Lake County Public Safety (IN), Indiana Project Hoosier SAFE-T
View 9 talkgroups
DEC Alpha Tag Description Status
307 PatientReports 1 Fire/EMS: Patient Reports (Encode) (Ch 1) Encrypted
308 PatientReports 2 Fire/EMS: Patient Reports (Encode) (Ch 2) Encrypted
309 PatientReports 3 Fire/EMS: Patient Reports (Encode) (Ch 3) Encrypted
310 PatientReports 4 Fire/EMS: Patient Reports (Encode) (Ch 4) Encrypted
311 PatientReports 5 Fire/EMS: Patient Reports (Encode) (Ch 5) Encrypted
10276 27-EMS OPS EMS: Operations Mixed
10370 32M-HRH EMS-to-Hendricks Regional ER Mixed
10372 32M-IUW EMS-to-IU Health West ER Mixed
12664 76-MED 1 EMS-to-Hospital ER - MED 1 Encrypted

Verification Status

We don't yet have per-talkgroup data for Lake County Fire/EMS from the RadioReference API. The encryption scope and type above come from the RadioReference Wiki, which is community-maintained rather than independently confirmed channel-by-channel. Our automated matching put this at moderate confidence (70%) based on how closely the wiki listing matches this agency's name and county.

If you monitor Lake County Fire/EMS directly or have more current information, the fastest way to fix this is to update the RadioReference Wiki entry — our data pulls from there and from the RadioReference API on a regular refresh cycle.

Lake County Context

Lake County is a mixed picture: 2 of 7 agencies we track here are fully encrypted (29%), which means some neighboring departments are still audible on a scanner.

What This Means

Our records list every channel this agency runs as encrypted, including day-to-day dispatch. That listing hasn't been verified against live talkgroup data, so confirm it at RadioReference before relying on it.

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

Frequently Asked Questions

Is Lake County Fire/EMS radio encrypted?

Our database lists Lake County Fire/EMS as using P25 AES-256 encryption, though this listing is unverified. Our records list every channel this agency runs as encrypted, including day-to-day dispatch. That listing hasn't been verified against live talkgroup data, so confirm it at RadioReference before relying on it.

Can I listen to Lake County Fire/EMS on a police scanner?

Likely not, if the listing is accurate: our database lists Lake County Fire/EMS as fully encrypted using P25 AES-256, which no consumer scanner can decode. The listing is unverified — check the live RadioReference database for current status.

Why do agencies like Lake County Fire/EMS 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 Lake County reverse the encryption decision?

Nothing technical prevents it. Lake County Fire/EMS operates encrypted because someone decided it should, and decisions of that kind get revisited when councils hear sustained, organised pressure rather than isolated complaints.

What can I do about Lake County Fire/EMS encryption?

Put the question to whoever signs off on Lake County Fire/EMS'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 Lake County so the ask arrives as a group rather than a one-off.

Advertisement