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 →
Accident Near Me? How to Find Out What Happened
A crash is dispatched over the radio within seconds of the first 911 call — location, lanes blocked, injuries, extrication — long before any map turns red or any article posts. Whether you heard the bang from your kitchen or you’re staring at brake lights on the highway, here’s how to get the real answer, in the order the sources actually update.
Key takeaways Seconds: county scanner feed — the crash is dispatched with location and severity. Minutes: state 511/DOT map (highways), Waze/Google markers, agency active-calls page. Hours/never: news — most crashes are cleared without a word published. Severity tells: ambulance = injuries; “extrication/jaws” = serious; medevac helicopter = major. Hear it yourself next time: a two-dongle GopherTrunk box carries police and fire/EMS at once.
Right now: the radio has it first
Every crash response — police, fire, EMS — is coordinated on dispatch channels that are legal to hear and usually unencrypted (fire/EMS especially). Within the first minute you’ll hear:
- Location — street and cross-street or highway milepost.
- Severity — “property damage only,” “injury accident,” or “extrication” (someone trapped; the serious ones).
- Lane status — what’s blocked and for roughly how long.
A Broadcastify feed for your county carries this if a volunteer runs one; your own scanner carries it always.
Minutes later: the traffic layer
- State 511 / DOT map — every state runs one (search
"<state> 511"). Confirmed highway incidents, lane closures, and clearance estimates; surface streets mostly absent. - Waze / Google Maps — crowd-reported crash pins and the red slowdown trail. Fast on busy roads, blind on quiet ones, and never says what happened.
- Agency active-calls page — the CAD entry (“MVA,” “10-50,” “TC”) with a
block address; search
"<county> active calls".
Reading severity from your window
The response tells the story before any report does: one police cruiser is a fender-bender; an engine and ambulance mean reported injuries; a second ambulance, rescue company, or a helicopter overhead mean a major incident; and a slow trickle of arriving units usually means it sounded worse on the 911 call than it was.
Earlier today or last night?
Crashes leave records you can walk back through — CAD logs, 511 archives, scanner-feed archives, and eventually the crash report itself. The full method (it works for any incident, not just crashes) is in what happened near me last night.
If you’re close to it — witness, first on scene, or worried
- First on scene: stop beyond the wreck if safe, hazards on, call 911 with location and lane before anything else. Don’t move injured people unless fire or traffic makes staying deadly; do turn off a wrecked car’s ignition if reachable.
- You saw it happen: offer your name to the officer or call the non-emergency line later — dashcam clips are gold, and fault disputes often hang on the one independent witness who bothered.
- Driving past: slow down, move over a lane, and don’t film — secondary crashes in the gawker slowdown are a real, common event.
- Worried someone you know was involved? Don’t go to the scene. Call their phone, then the police non-emergency line (they can confirm a name was or wasn’t involved once the scene clears), then area hospitals. Serious-injury notifications come from officers in person — no news is usually good news.
Why crash-curious neighbors end up with a scanner
Crashes are the single most common “what was that?” event — frequent, hyper-local, and almost never covered anywhere. They’re also the perfect two-channel problem: the police side handles the traffic investigation while fire/EMS handles the patients, on different channels. That’s exactly why the kit below runs two receivers at once — and why it answers this question permanently, for every siren, not just today’s.
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 about an accident near me right now?
The fastest sources, in order: a live police/fire scanner feed for your county, where the crash is dispatched with location and severity within seconds; your state DOT’s 511 traffic map, which posts confirmed incidents on highways; Google/Waze incident markers, which appear once drivers report or slow down; and the agency’s active-calls page. News coverage arrives only for major crashes, often an hour or more later.
I heard a crash outside — how do I know if it was serious?
Listen to what gets dispatched. On a scanner feed, a minor fender-bender draws one police unit; injuries add an engine and an ambulance; a serious wreck adds extrication (‘rescue’ or ‘jaws’) and sometimes a medevac helicopter. The dispatch traffic in the first two minutes tells you more than an hour of looking out the window.
Why is there nothing online about the accident I just saw?
Most crashes never make the news or even the DOT map — property-damage-only wrecks on surface streets are handled and cleared in under an hour with no public posting beyond the CAD log. The dispatch radio is usually the only place they’re ever described in real time.
What does it mean when a helicopter comes to an accident?
A medevac (air ambulance) landing means at least one patient with injuries serious enough that flight time beats ground transport — a strong signal of a major crash. You’ll typically hear the landing-zone coordination on fire/EMS channels, and you can watch the aircraft itself on a flight tracker.
How can I find out about an accident that happened earlier today?
Check the agency’s calls-for-service log for the time and block, your state’s 511/DOT incident archive for highway crashes, and local news for anything major. For the full picture, scanner-feed archives (Broadcastify premium) let you replay the dispatch audio from the exact time of the crash.
Do police report accidents to some public website?
Not in real time. Crash reports become public records days later through the agency or state crash-report portal, sometimes for a fee. Real-time visibility is dispatch radio, CAD logs, and DOT maps; the paper record follows well behind.