Fire Department Partially Encrypted

Lake County Fire/EMS

Lake, Indiana

How we verified this

Lake County Public Safety IN (sid 8384), category 'Fire/EMS': Fire Disp South/East/West, alarm, ops 01-12 all 'T' (clear); Patient Reports 1-5 'T Enc'. EMS category LCEMS 1-4 clear. Checked ctid737/trs. As of October 2026.

Checked against a primary source on 2026-10-13: radioreference.com . Status changes without notice: confirm on the live RadioReference database.

What you can do right now

Encryption Details

Encryption type Algorithm not published
Scope Some talkgroups encrypted; others remain in the clear.

Talkgroup Data Under Review

Our October 2026 audit removed 4 talkgroups because it could not tie them to Lake County Fire/EMS by RadioReference category. Those found on RadioReference are filed under Hendricks County (32) (2), Grant County (27) (1) and Steuben County (76) (1). Totals and percentages computed from that list are withheld.

5 talkgroups remain, filed under RadioReference category Fire/EMS:

View 5 talkgroups
DEC Alpha tag Description RadioReference category Status
307 PatientReports 1 Fire/EMS: Patient Reports (Encode) (Ch 1) Fire/EMS Encrypted
308 PatientReports 2 Fire/EMS: Patient Reports (Encode) (Ch 2) Fire/EMS Encrypted
309 PatientReports 3 Fire/EMS: Patient Reports (Encode) (Ch 3) Fire/EMS Encrypted
310 PatientReports 4 Fire/EMS: Patient Reports (Encode) (Ch 4) Fire/EMS Encrypted
311 PatientReports 5 Fire/EMS: Patient Reports (Encode) (Ch 5) Fire/EMS Encrypted

Current list: RadioReference, Lake County.

Shared Radio System

Lake County Fire/EMS isn't on a radio system of its own: Lake County Public Safety (IN) also carries 1 other agency in Lake County, Indiana. Encryption on a shared system is set talkgroup by talkgroup, so agencies on it can differ.

Lake County Context

Of the 7 public-safety agencies we track in Lake County, 7 are listed as partially encrypted and none as fully encrypted.

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 →

Frequently Asked Questions

Is Lake County Fire/EMS radio encrypted?

Partly. Lake County Fire/EMS uses encryption (algorithm not published) on some of its talkgroups while leaving others open. 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 Lake County Fire/EMS on a police scanner?

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

Why did 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 the encrypted share of fire department response as it happens.

Can Lake County Fire/EMS's encryption decision be reversed?

Nothing technical prevents it. Agencies like Lake County Fire/EMS encrypt because someone decided they 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 encryption rather than a delayed feed or keeping routine dispatch open? 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.

Data source: RadioReference Wiki + checked against RadioReference database

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