The radio record, honestly scoped

Scanner & Transcripts

This page starts with the fact that shapes everything else: most of Fort Wayne's public-safety radio cannot be listened to, by anyone. What can be heard is linked below — we link out to the feeds' own pages; we never embed, host, or rebroadcast audio. And the desk's transcript work follows two hard rules: no private information is ever published, and publishing is crime-only.

The encryption record — most of Fort Wayne's radio is closed

Encrypted since February 4, 2014

When the city/county APCO-25 public-safety system went live on February 4, 2014, Allen County's law-enforcement and city fire radio went fully encrypted. The Fort Wayne Police Department's own statement at the time, as published by the Journal Gazette:

“All radio communications will be encrypted rendering scanners and/or software applications incapable of monitoring City or County radio traffic.”

That is still the position. The FWPD, Allen County Sheriff, New Haven PD and Fort Wayne Fire talkgroups are carried in radio databases as encrypted, and scanner-community checks as recent as 2023 confirm Allen County law enforcement is “fully encrypted = unmonitorable.” There is no legal or technical way for the public — or for this desk — to receive that traffic, so:

FWPD dispatch — not monitorable; no public feed.
Allen County Sheriff dispatch — not monitorable; no public feed.
Fort Wayne Fire dispatch and operations — not monitorable; no public feed.
Ambulance dispatch (TRAA) and hospital/medical channels — not monitorable; no public feed.

Any “scanner transcript for all of Fort Wayne” is therefore bounded by what is actually broadcast in the clear. This page inventories exactly that — nothing more is claimed.

Sources: Fort Wayne Police Department statement, February 2014 (Journal Gazette, preserved on RadioReference); RadioReference, Allen County (IN) system database and wiki — consulted November 3, 2026.

What can be heard — the open channels

Two dispatch sources covering the Fort Wayne area are broadcast in the clear and publicly fed. Both links go to the feeds' own pages on Broadcastify; listening happens there, not here.

Allen County Fire — dispatch & operations

County Fire Dispatch and Fire Ops 11–14 — the in-the-clear channels of the county system. Every township and county fire department in Allen County is dispatched here, and those departments also answer EMS first-response calls, so county victim-response traffic is heard on this feed. Fort Wayne city fire is not on it — the city channels are encrypted.

Listen at Broadcastify — feed 32212 →

Fort Wayne Area Public Safety — read the fine print

This feed is programmed for the full county system — FWPD, Sheriff, New Haven PD, Fort Wayne Fire, county fire — but almost every one of those talkgroups is encrypted, and a scanner cannot decode them. Its receivable content is the same in-the-clear county fire set as the feed above. It does not carry FWPD or Sheriff audio, whatever its name suggests.

Listen at Broadcastify — feed 47033 →

Indiana State Police — District 22 (Fort Wayne) dispatch

ISP District 22 dispatch is broadcast in the clear on Indiana's statewide SAFE-T system (talkgroup 10734). There is no dedicated Allen County audio feed for it; it reaches the public through Broadcastify Calls, the per-call platform, via statewide SAFE-T nodes.

Open Broadcastify Calls →

What is not fed at all

To be plain about the negative space: no public feed carries FWPD dispatch, Allen County Sheriff dispatch, New Haven PD, Fort Wayne Fire, TRAA ambulance dispatch, or any hospital or medical channel. If a site claims to stream Fort Wayne police audio live, it is not describing these encrypted systems.

Feed inventory: Broadcastify, Allen County (IN) feed listings — broadcastify.com/listen/ctid/694 — checked November 3, 2026. Both audio feeds above were live at the check.

How the transcript desk works

Filed in full. The open channels above are transcribed, and the transcripts are filed in full as the desk's working record — every call, timestamped, kept.
Publishing is crime-only. A post runs only when the traffic has a basis that someone broke the law. An accident qualifies when it carries that basis — an OWI crash, a hit-and-run, a reckless-driving or pursuit crash. A plain accident, a medical call, or a victim-response run with no law-breaking basis is filed and never published.
Redaction before publication — no private information. Dispatch traffic routinely carries private information. Before anything from a transcript is published, the redaction step strips: victim and patient names; patient medical details; patient age and sex combined with an address or medical detail; exact residential street addresses (locations publish at road, intersection, or block level); dates of birth; driver license numbers and license plates read over the air; phone numbers; names of callers, witnesses and suspects broadcast before any official release; juvenile identifiers; and hospital destinations tied to an identifiable patient. Published excerpts show “[withheld]” where material was removed.
Raw records stay internal. Unredacted transcripts and any retained audio are working records. They are never published.
Terms are respected. Capture and transcription of Broadcastify's own streams requires Broadcastify's commercial license under its current Terms (§9) — so this desk's transcript work is scoped to traffic received directly off the air from the in-the-clear channels, which carries no such term. The link-out model on this page needs no license: the Terms do not prohibit linking to feed pages.

The incident post — small, sourced, updatable

What the public reads is not a transcript dump. It is a small post per incident — timestamp, agency/channel, public location, incident type, one factual line — with later transmissions appended to the same post as updates, and each post linked back to its filed transcript entry. One post per incident; repeat dispatches for the same call fold into it.

Format example — not a real incident

7:42 PM · ISP District 22 Dispatch — Vehicle pursuit, I-69 northbound; driver fled a traffic stop.
Update 7:49 PM — Vehicle stopped near the 312 exit; one driver in custody.

This example shows the post format only. It does not describe a real event, and no incident is ever posted in this shape without filed traffic — or an official release, labeled as such — behind it.

Because FWPD and Fort Wayne Fire traffic is encrypted, city incidents such as shots-fired calls and city structure fires can never be scanner posts. If this site reports one, the source is an official release (see the Police Spotter sources) and the post is labeled with that source — never presented as scanner-derived.

Sensors — gunshot detection in Fort Wayne

ShotSpotter: no deployment in Fort Wayne. No record of a SoundThinking / ShotSpotter deployment, proposal, or council debate in Fort Wayne was found in any source class checked for this desk: FWPD material, city-council coverage, local news, SoundThinking's own material, or the EFF Atlas of Surveillance (whose Fort Wayne entries document Flock Safety license-plate readers, and no gunshot detection).

What exists instead is a different vendor's pilot. In May 2026 FWPD announced a limited pilot of the Flock Safety Raven acoustic-detection system in select areas of the city, chosen from three years of reported gunfire and crash data; the coverage areas were not published. Per FWPD, the sensors detect gunfire (and fireworks, street takeovers, and certain sounds of distress) and alert officers — in 45 to 60 seconds, per the department's statement to WPTA — the system does not record conversations, and audio data is retained 21 days. No public alert data from the pilot is published: alerts go to officers through the vendor's platform, and there is no public feed, map, or dataset for this desk to republish or link.

Sources: Fort Wayne Police Department press release, May 2026 (republished by WayneDale News, May 24, 2026; covered by WPTA, May 11, 2026); EFF Atlas of Surveillance, Indiana entries — consulted November 3, 2026.