This is a Just the Facts (JTF) post: generated by AI from my own raw material (voice memos, session notes) and a short outline I wrote, then checked by me. What's a JTF?
Previously in this series: Police Scanner Traffic at the Command Line
I built scannerassist to pull police scanner traffic from the command line. Right after that, I read that police scanners around here are going quiet, so I wanted to work out whether I'd built a tool for a source that's about to disappear.
Did I just build a tool on a data stream scheduled to go dry?
scannerassistis a script for getting at police scanner traffic programmatically. It pulls calls from Broadcastify Calls, then transcribes and caches them.- Soon after I finished it, I came across ARLnow reporting on the shutdown: "Localities across the D.C. [area] have been quietly closing a key window into public safety communications under a region-wide plan to encrypt police dispatch calls. Arlington could be next ..."
- My own check of the region backs this up:
- DC: Broadcastify carries only Fire/EMS and hospital channels. MPD is encrypted.
- Fairfax County and Fairfax City: police dispatch has been encrypted since July 2026, and Fairfax isn't on Broadcastify Calls at all.
- Loudoun: all the Sheriff dispatch channels are encrypted.
- Arlington: police dispatch is still in the clear. The airport police at DCA and Dulles are too.
Maybe not, reason one: there's still plenty on the air besides police
- I pulled one hour of Arlington radio, Thursday 7 to 8 a.m., leaving out police and fire. The school bus channels were the busy ones: most of the calls that hour were bus traffic.
- Some of what happened in that hour:
- A bus broke down with students aboard. Dispatch arranged for another driver to pick them up and cover the rest of the route, and sent parents a delay notice.
- A bus with a known coolant leak went out anyway. In dispatch's words, it was "literally a last resort." It had to turn back partway through its run, and another driver picked up its high school stops.
- A route was missing from the routing app, and another driver's tablet wouldn't move on to the next stop.
- None of this is as serious as police activity. It's still real, almost nobody sees it, and if something newsworthy happened on a bus, this would be a primary source.
Maybe not, reason two: even for police incidents, radio shows you what nothing else does
- My example is the November 12 shooting at a gym in DC's Logan Circle.
- DC police radio is encrypted, but Fire/EMS dispatch isn't, and they respond to the same incidents.
- Radio isn't the truth. It's the fog of war: what responders believed in the moment. Some claims pan out, some don't, and some never get confirmed. That still makes it a valuable resource.
- In this case the radio was ahead of the news:
- 8:02 a.m.: Engine 9 and Tower 3 are dispatched to a commercial fire alarm on the 1500 block of 15th Street NW.
- 8:03 a.m.: a Deputy Fire Chief breaks in: "they have a shooting next door with active scene. Have them stage."
- 8:06 a.m.: the call is upgraded to "active shooter on Logan Circle," with a full assignment of units.
- WJLA's first story is stamped 8:27 a.m. MPD's "CRITICAL ALERT" on X came at 8:45 a.m., per NBC's live blog.
- Some of it matched later reporting. WTOP/AP puts the suspect on a high floor of a nearby apartment building, which fits the radio's report of shots on the seventh floor.
- Some of it I haven't seen confirmed anywhere I've read, so treat these as unverified:
- A report that the building was on fire.
- "30 people in the basement" of the gym, three of them having asthma attacks.
- Shots on the third floor.
- One thing needs no confirmation, because the dispatches themselves are the record: the size of the EMS staging. Between 8:53 and 9:08 a.m., wave after wave of ALS, BLS and AMR units were called in, more than 15 transport units in all.
- Radio gives you details the reporting doesn't. The facts it relays may turn out to be wrong, but there's no doubt this is what responders were hearing at that moment.
Conclusion: the tool didn't lose its value
- There's still plenty to listen to.
- What you hear is real, and most people never hear it.
- Arlington's police are still on the air, for now.
Code
$ # An hour of Arlington radio that isn't police or fire: county
# crews, the hospital, schools and school buses.
scannerassist -a transcript -g arl-civic \
-s '2026-11-12 07:00' -e '2026-11-12 08:00' > civic.txt
cut -d'|' -f2 civic.txt | sort | uniq -c | sort -rn
159 arl-bus-400
114 arl-bus-800
87 arl-bus-600
43 arl-parks
29 arl-bus-500
28 arl-bus-700
17 arl-solid-waste
6 arl-bus-900
$ PROMPT="This is one hour of Arlington County radio traffic, not police
or fire: one radio call per line, as time|channel|seconds|radio
id|audio file|transcript. Transcripts are machine-made and can
garble words; some are in Spanish. In 4 to 6 bullets, tell a
curious reader the most notable things that happened that hour,
across all channels. Skip routine check-ins. Don't name anyone,
and don't give stop locations or addresses."
chatgptassist -a ask -f civic.txt -p "$PROMPT" | block | fmt
- The biggest bus issue was a route 420 breakdown during the morning
run. Dispatch coordinated another driver to pick up the three students
already onboard, cover the remaining pickups, and send parents a delay
notice of roughly 30–35 minutes.
- A separate bus developed or was reported with a coolant leak, forcing
the driver to return to the lot after an initial drop-off. Staff scrambled
to find a usable replacement, considered swapping buses between drivers,
and lined up another bus for the afternoon.
- Several school-bus assignments were shuffled in real time: one route
was missing or incorrect in the navigation/Wayfinder system, another
driver’s tablet/ATS stopped advancing stops, and dispatch reassigned
coverage among routes including 712, 625, 918, and others.
- The call center handled a stream of “no pickup” reports: drivers
confirmed they had waited at scheduled stops, students did not appear,
and dispatch logged the misses or checked whether pickup times had
recently changed.
- Outside the bus channels, solid-waste crews coordinated landfill
arrivals and material dumping, while parks crews—mostly in
Spanish—talked through yard/truck movements and later reported finding
a small downed tree or branch in a traffic island, apparently not at
the originally expected spot.
$ # DC police radio is encrypted, but Fire/EMS dispatch isn't. The
# shooting near Logan Circle was reported a little after 8 a.m.
scannerassist -a transcript -g dc-ems \
-s '2026-11-12 07:55' -e '2026-11-12 09:15' > shooting.txt
awk -F'|' '$1 >= "2026-11-12 08:02" && $6 ~ /15th Street|shooting|shooter/ {
print substr($1, 12), $6
}' shooting.txt | block | head -6
08:02:35 Local alarm Engine 9 Tower 3, respond for the commercial fire alarm. 1500 block of 15th Street Northwest. Local alarm Engine 9 Tower 3, respond for the commercial fire alarm. 1500 block of 15th Street Northwest, cross of PPS and Poplar Street, operating on 02-0802.
08:03:42 Deputy Fire Chief, advise communications. Command, Deputy Fire Chief. So, sir, you just dispatched Engine 9 and Tower 3 on a commercial fire alarm at 1500 block of 15th Street Northwest. Advise the units that they have a shooting next door with active scene. Have them stage.
08:04:11 Medical local paramedic engine 33, ambulance 33 respond for the BLS accident at Walter Place Elementary School, 900 block of Walter Place Southeast, at Walter Place Elementary School. Cross of the number 93, TAC channel 011 and 0804. Engine 16, Medic 1, EMS 7, Battalion Chief EMS responding for the shooting, switch over to TAC channel 0 Bravo 3. Again, all units on this shooting, switch over to TAC channel 0 Bravo 3 at 0804.
08:04:25 Engine 9, can you repeat? We have a shooting. Engine 9, there's a shooting next to the location you're responding to, so make sure you and Tower 3 stage. Tower 3 copy.
08:05:38 Battalion 6, respond for the shooting, 1500 block of 15th Street Northwest. Battalion 6, respond for the shooting, 1500 block of 15th Street Northwest, cross of P Street and P Street. Operate on Tac 10-0 Bravo 3-0-8-0-5.
08:06:38 Engine 1, following alarm with Battalion 6, operate on TAC Channel 0 Bravo 3. Local alarm Engine 6, Engine 1, Truck 4, Squad 1, Battalion 4, Ambulance 16, Ambulance 9, AMR 82, Engine 24, Truck 11, Medic Ambulance 1, Medic Ambulance 2, Battalion 1 respond for the active shooter on Logan Circle, 1500 block of 15th Street Northwest. Local alarm Engine 6, Engine 1, Truck 4, Rescue Squad 1, Battalion 4, Ambulance 16, Ambulance 9, AMR 82, Engine 24, Truck 11, Medic Ambulance, Medic Ambulance 2, Battalion 1 respond for the upgraded active shooter at Logan Circle, 1500 block of 15th Street Northwest, cross of PPS and Puffer Street. Operate on TAC Channel 0 Bravo 3 at 0807.
Resources
- WJLA: first report on the Logan Circle shooting (8:27 a.m.)
- NBC News live blog: Logan Circle shooting, with MPD's 8:45 a.m. alert
- scannerassist: transcripts and cached audio for scanner calls
- chatgptassist: ask, transcribe, say and generate-image with OpenAI
- broadcastifyassist: the interface scannerassist expects
- Broadcastify Calls
Behind This Post
The outline I wrote
- Did I just build a tool on a data stream scheduled to go dry?
- I coded =scannerassist=, a script to programmatically access police
scanners, and then came across [[https://www.arlnow.com/2026/11/12/police-scanners-are-going-silent-across-the-d-c-area-could-arlington-be-next/][ARLnow]] reporting their shutdown:
"Localities across the D.C. [area] have been
quietly closing a key window into public safety communications
under a region-wide plan to encrypt police dispatch calls.
Arlington could be next ..."
- My own check of the region confirms this: DC, Fairfax and others
are encrypted or missing from Broadcastify.
- Maybe not, for two reasons
- Reason one: there's still plenty on the air besides police.
- Take a Thursday 7-8am, the school buses channel was
hopping. There was a breakdown with students aboard; a bus with
a known coolant leak sent out as a last resort, which had to
turn back mid-run and leave its high school stops to another
driver; and a routing app glitch. While not the same gravity as
police activity, it's still authentic, invisible to most and
should something newsworthy happen, this would be a primary
source.
- Reason two: even for a police incident, radio gives a view you
can't get anywhere else. The example: the November 12 shooting at
a gym in DC's Logan Circle.
- DC police radio is encrypted, but Fire/EMS dispatch isn't, and
they respond to the same incidents.
- Radio is the fog of war, not the truth. It's what responders
believed at the moment. Some claims pan out, some don't, some
never get confirmed. As a resource, that's still valuable.
- In this case, radio beat the news: the fire alarm and
"shooting next door, have them stage" at 8:02-8:03, and the
upgrade to "active shooter" at 8:06. WJLA's first story is
stamped 8:27, and MPD's "CRITICAL ALERT" on X came at 8:45 (per
NBC's live blog).
- Matched later reporting, at least in part: WTOP/AP has the
suspect on a high floor of a nearby apartment building, in line
with the radio's seventh floor.
- Not confirmed in anything I've read: the fire in the building,
the basement shelter count, shots on the third floor. Flag them
as unverified.
- Straight from the radio, no confirmation needed: the size of the
EMS staging, which shows up as the dispatches themselves.
- Radio provides details that reporting doesn't give you; the
facts relayed may not be true, but the moment undeniably is.
- Conclusion: the tool didn't lose its value.
- There's plenty to listen to
- What you hear is both real and novel
- Arlington's police are still on the air, for now.









