Reader-supported. GopherTrunk is free, open-source software. Some
hardware links on this page go to Amazon with our Associates tag
(gophertrunk-20); if you buy through them we may earn a small
commission at no extra cost to you. Links to out-of-production gear may go to
eBay searches instead; we have no affiliate relationship with eBay and earn
nothing there. It never changes which gear we recommend, and
the software stays free either way. How GopherTrunk is funded →
Why Is the Road Closed? Find Out What’s Blocking Traffic
A road closure is a radio operation — every barricade, detour, and re-opening is coordinated over police dispatch, so the “why” is broadcast in plain language the whole time the road is shut. Apps will show you that it’s closed; here’s how to find out why, and how long you’re actually going to be stuck.
Key takeaways The reason is on dispatch: a county scanner feed or your own scanner hears the closure being run. Highways: the state 511/DOT map posts cause + duration estimates. Planned closures: city public-works / police social accounts. Duration tells: crash 30–90 min; wires down = utility ETA; fatal investigation = hours; gas leak = open-ended. Don’t call 911 to ask.
The fast lookups
- Scanner feed — Broadcastify for your county. You’ll hear the incident itself plus the practical gold: which cross streets are shut, where traffic is being turned, and the “open it back up” call the moment it comes.
- State 511 / DOT map — search
"<state> 511". Authoritative for highways: cause, lanes, and a clearance estimate. - Waze / Google Maps — instant closure geometry, useful for routing around, silent on cause.
- City / agency social feeds — planned closures (parades, races, utility work, filming) are posted in advance; search your city plus “road closures.”
Decoding what you see at the barricade
- Fire trucks + utility trucks → wires, gas, or water: the road opens when the utility clears it, not before. (Why fire trucks with no fire?)
- Many police units, measuring wheels, cameras → serious-crash investigation; plan on hours. (Accident lookup)
- Tape a block over, officers relaxed at the barricade → the scene is elsewhere; you’re at the perimeter of a police operation.
- A helicopter on or near the roadway → medevac landing zone; total but brief closure. (Identify it)
- Cones and a calendar → planned work or an event; the city posted it somewhere last week.
Detour rules that keep you out of trouble
- Never move a barricade or drive around one. “Road Closed” transfers liability to you the moment you pass it — and the hazard (wires, washout, scene) is usually exactly where you can’t see it yet.
- Water over the road: turn around. A foot of moving water floats most cars; barricaded flooding is the single deadliest thing on this page. “Turn Around, Don’t Drown” is a rule, not a slogan.
- Dark traffic signals = all-way stop. Outage-darkened intersections (power outage?) are treated as four-way stops in every state; assume cross traffic doesn’t know that.
- Don’t blindly follow the app. Detour routing happily sends a hundred cars down a private lane or an unmaintained shortcut; prefer the signed detour, which was chosen to carry the load.
- Never tuck in behind an emergency vehicle to slip through — it’s illegal, and the closure point will stop you anyway.
The commuter’s cheat code
People who drive the same corridor daily eventually notice the pattern: traffic apps react to a closure after everyone is already stopped, while the closure went out over the radio before the first barricade was set. A scanner in the car — or a GopherTrunk box at home feeding your phone on the way out the door — moves you from the reacting crowd to the informed one. Related picks: the road-trip scanner guide and the trucker scanner guide, both built around exactly this use.
The fix for next time: a scanner that never sleeps, for about $250
Every lookup method on this page depends on someone else — a feed volunteer, an app's coverage map, an agency webmaster. This kit removes the middleman: a silent little box on a shelf that decodes your county's digital dispatch directly off the air, streams it to any browser in the house, and records every call with timestamps. Next time the sirens go past, the answer is already on your phone — and free, open-source GopherTrunk is the software, so the parts below are the entire cost.
Why two receivers: one dongle stays locked to your police trunked system while the second covers fire/EMS or a neighboring system at the same time — the two channels a "what's going on?" moment actually needs. That's a trick a $500 handheld scanner can't do, and GopherTrunk drives both dongles from one Orange Pi.
Orange Pi 5
around $90
The RK3588 host that runs it all 24/7 — silent, low-power, and strong enough for both dongles with headroom to spare. GopherTrunk ships a native ARM64 Linux build for it.
Orange Pi 5 on Amazon →RTL-SDR Blog V4 kit
around $55
The dongle and the telescopic dipole antenna kit with coax and mounts in one box — this one holds your police system's control channel.
V4 + antenna kit on Amazon →RTL-SDR Blog V4 (second dongle)
around $35
Covers fire/EMS, a second trunked system, airband, or NOAA weather — simultaneously, not by giving up the first channel.
RTL-SDR V4 on Amazon →The complete parts list
| Part | Why it's in the kit | Approx $ | |
|---|---|---|---|
| Orange Pi 5 | Always-on host for both dongles | ~$90 | Amazon → |
| RTL-SDR Blog V4 + dipole antenna kit | Receiver #1, antennas, coax, mounts | ~$55 | Amazon → |
| RTL-SDR Blog V4 (second) | Receiver #2 — fire/EMS or a second system | ~$35 | Amazon → |
| Powered USB 3.0 hub | Clean, stable power for two warm dongles | ~$35 | Amazon → |
| 16-piece SMA adapter kit | Joins any antenna to any dongle, first try | ~$18 | Amazon → |
| RG316 SMA pigtail kit | Flexible jumpers between hub, dongles, antennas | ~$15 | Amazon → |
| USB-C power supply (5V/4A+) | The Orange Pi 5 needs solid power for 24/7 duty | ~$15 | Amazon → |
| microSD card (64GB, A2) | OS plus months of recorded calls | ~$12 | Amazon → |
Kit total: about $250–275. Worthwhile upgrade once it's earned a permanent shelf: an outdoor discone antenna (~$40) that hears everything from 25–3000 MHz — see the antenna guide. Prefer a Raspberry Pi 5 host instead? Same build, swap the board — Pi 5 (8GB) on Amazon and the SBC build guide.
From boxes to first decoded call
- Flash 64-bit Linux (Debian/Ubuntu image) to the microSD and boot the Orange Pi headless.
- Plug in the powered hub, both dongles, and the antennas — the adapter kit bridges any connector mismatch.
- Install GopherTrunk — one free static binary, no dependencies: download, then follow the setup guide to point it at your county's system from RadioReference.
- Open the web console from any phone or laptop in the house — live calls, talkgroup names, and a scrollable, replayable recording archive.
Two honest caveats before you spend a dime: check RadioReference that your agencies are not encrypted — no device decodes AES — and skim the legality rules for your state (listening is legal in the US; a few states restrict use in vehicles). Rather have a no-computer, pocketable option instead? That's the dedicated scanner guide.
Frequently asked questions
How do I find out why a road is closed near me?
Fastest: a live scanner feed for your county — closures are coordinated over police dispatch, with the reason stated plainly. For highways, the state 511/DOT map posts confirmed closures and estimated durations. City public-works or police social accounts cover planned closures; Waze shows the closure but rarely the cause.
Police are blocking the road but nothing looks wrong — why?
Common causes you can’t see from the car: a crash or downed wires just beyond the curve, a hazmat spill being assessed, an active police scene a block over, an escort (oversize load, funeral, dignitary motorcade), or a planned event setup. Dispatch radio names it; the officer at the barricade usually won’t.
How long will a road closure last?
Rules of thumb from dispatch traffic: a minor crash clears in 30–90 minutes; downed power lines wait for the utility crew, often 2–6 hours; a serious-injury or fatal crash closes the road for hours of investigation and reconstruction; gas leaks are open-ended until readings clear. The 511 map’s estimate is decent for highways; the scanner tells you when the tow truck is actually leaving.
Why is the highway completely stopped in both directions?
Both directions stopped usually means a hazard that crosses the road — a medevac helicopter landing on the roadway, wires or debris across all lanes, a hazmat plume, or police activity spanning the median. A single-direction closure is more typical of an ordinary crash.
Is there an app that shows road closures and why?
Waze and Google Maps show the closure geometry quickly but rarely the reason. The state 511 app/map gives causes for highways. For surface streets the only real-time ‘why’ source is public-safety radio traffic — a scanner or scanner feed — because that’s the channel the closure is being run on.
Who do I call to ask why the road is closed?
Nobody, ideally — 911 is for emergencies and the non-emergency line will rarely narrate an active scene. The information is already public on the dispatch channels coordinating the closure, on the 511 map for highways, or on the agency’s social feed for planned work.