Fire Department Partially Encrypted

Mount Morris Township Fire

Genesee, Michigan

What you can do right now

Encryption Details

Encryption type Algorithm not published
Scope Most Operations except for Dispatch/Paging

Talkgroup Data Under Review

Our October 2026 audit removed 1 talkgroup because it could not tie it to Mount Morris Township Fire by RadioReference category (1 naming another agency or town). Those found on RadioReference are filed under Isabella County (37) (1). Totals and percentages computed from that list are withheld.

2 talkgroups remain, filed under RadioReference category Genesee County (25) Fire:

View 2 talkgroups
DEC Alpha tag Description RadioReference category Status
2479 25F37 Mount Morris Twp. Fire: Proprietary Tactical Genesee County (25) Fire Encrypted
2484 25F44 Mount Morris City Fire: Proprietary Tactical Genesee County (25) Fire Encrypted

Current list: RadioReference, Genesee County.

Verification Status

The scope above comes from the community-maintained RadioReference Wiki; no human-reviewed source has been recorded, so treat it as unconfirmed.

If you monitor Mount Morris Township Fire directly or have more current information, the RadioReference Wiki entry is where the listing this page started from can be corrected.

Shared Radio System

This page is one of 32 built from the same underlying radio record: fire department here shares Michigan's Public Safety Communications System (MPSCS) with 31 other departments in Genesee County; encryption is set per talkgroup, so what a scanner hears can differ from one of those pages to the next.

See all 32 agencies on this system in Genesee County →

Genesee County Context

Genesee County is a mixed picture: 10 of 38 agencies we track here are fully encrypted (26%), which means some neighboring departments are still audible on a scanner.

What This Means

This agency is listed as encrypting some communications while leaving others open. The per-channel breakdown is unverified — check RadioReference for current status.

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

Frequently Asked Questions

Is Mount Morris Township Fire radio encrypted?

Mount Morris Township Fire is listed in our records with encryption (algorithm not published) — a listing we haven't yet verified against live talkgroup data. This agency is listed as encrypting some communications while leaving others open. The per-channel breakdown is unverified — check RadioReference for current status.

Can I listen to Mount Morris Township Fire on a police scanner?

Possibly. Our database lists Mount Morris Township Fire as encrypting some of its talkgroups while leaving others open, which would leave some channels accessible. The listing is unverified — check RadioReference for specific talkgroup status.

Why do agencies like Mount Morris Township Fire encrypt their radio?

Ask why, and the answer is usually officer safety, sometimes operational security. What is harder to obtain is any documented case in Genesee County where an open channel caused harm. The costs need no such documentation: reporting on the encrypted share of fire department response slows down, and mutual-aid coordination gets more awkward, immediately.

If Mount Morris Township Fire is encrypted, can that be reversed?

Yes. Encryption is a policy choice made by department leadership or elected officials, not a technical requirement, so it can be reversed the same way. Public pressure, city council advocacy, and organized local coalitions have reversed encryption decisions elsewhere.

What can I do about Mount Morris Township Fire encryption?

Ask for the paperwork first — the policy that authorised encryption for Mount Morris Township Fire, and the recordings themselves — because a specific request is harder to wave away than a general complaint. Then take what you learn to a council meeting, and bring others from Genesee County with you.

Data source: RadioReference Wiki

This information is compiled from community-reported data and may not reflect the most current status.