Mapping the Gaps: How Radio Operators Are Crowdsourcing Coverage Dead Zones—And Why You Should Help

There's a stretch of road outside Knoxville, Tennessee, where a local ARES group discovered something during a county-wide exercise a few years back: three separate repeaters showed full signal on paper but delivered nothing usable in a valley between two ridgelines. Handhelds dropped out. Mobile units struggled. The gap wasn't on any map anyone was working from.

It wasn't until operators physically drove the route, logged the failures, and compared notes that the picture emerged. A dead zone about two miles long, right across a road that emergency vehicles use regularly. The county emergency manager hadn't known. The repeater trustees hadn't known. Nobody had systematically looked.

That kind of gap exists in virtually every community in the country. The difference between communities that know about their gaps and communities that don't is usually just one thing: somebody decided to go find them.

Why Dead Zones Exist in the First Place

Before you can map a problem, it helps to understand why it exists.

Radio propagation is not a tidy circle radiating outward from an antenna. It's shaped by terrain, building density, vegetation, atmospheric conditions, and the interaction between all of these things at once. A repeater sitting on a hilltop might deliver excellent coverage over flat farmland in every direction while completely failing to reach a river valley two miles away that's shielded by a natural ridgeline.

In urban environments, the culprits are different. High-rise buildings create RF shadows. Underground parking garages, concrete-and-rebar structures, and subway infrastructure all attenuate signals dramatically. Even dense tree cover can absorb VHF and UHF signals in ways that surprise operators who've never tested in those conditions.

Frequency matters too. VHF (the 2-meter band) tends to behave better in hilly terrain and can sometimes bend around obstacles. UHF (70 cm) is more line-of-sight and gets absorbed more aggressively by physical barriers—but it also penetrates buildings better in some cases. A dead zone on one band may not be a dead zone on another.

And then there are the gaps that exist purely because nobody has ever deployed infrastructure to cover them—rural areas with no repeaters within range, suburban fringe zones that fall between two adjacent repeater footprints, industrial areas nobody thought to include in coverage planning.

What a Systematic Test Actually Looks Like

The difference between useful dead zone data and noise is methodology. Random reports of "my radio didn't work here once" aren't particularly actionable. Consistent, repeatable test results are.

Here's a practical field-testing framework that produces genuinely useful data:

Choose your test parameters first. Decide which band and which specific repeater or simplex frequency you're evaluating. Document your radio model, antenna type, and power level. Keep these consistent across all tests in a session—changing variables mid-test muddies the data.

Use a grid-based approach. Rather than just driving around and noting problems, divide your area into a rough grid and test at consistent intervals. A quarter-mile grid in a suburban area will give you granular data. Half-mile intervals work for rural coverage surveys. Apps like Google Maps or dedicated field mapping tools let you drop pins with notes as you go.

Record signal quality, not just presence or absence. "I could hear the repeater" is less useful than "S5 signal, readable but with noise" or "S2, barely audible, unable to complete a transaction." Many radios display an S-meter reading; use it. If yours doesn't, develop a simple personal scale—5 for full quieting, 1 for barely audible, 0 for nothing.

Test at different times of day. Atmospheric conditions affect propagation, especially on VHF. A spot that works fine at noon might be marginal at dusk. Early morning atmospheric ducting can create coverage that disappears by midday. Note your test time.

Include GPS coordinates. This is non-negotiable if you want your data to be useful to others. Even just dropping a pin in Google Maps and recording the coordinates takes seconds and transforms your notes from personal observations into shareable intelligence.

Where to Put What You Find

The good news is that the infrastructure for sharing this kind of data is already out there and growing.

RepeaterBook (repeaterbook.com) is the most widely used amateur repeater database in North America, and its community notes feature lets operators log coverage observations tied to specific repeaters. If you test a repeater and find a significant dead zone in its supposed coverage area, noting it there helps every operator who uses that database.

APRS (Automatic Packet Reporting System) is a real-time tactical network that some operators use for automated coverage testing. A mobile APRS station transmitting position beacons while you drive generates a passive coverage map—every successful position report is evidence of connectivity; the gaps in the track are dead zones. The APRS.fi website visualizes this automatically.

Local ARES and RACES groups are often the most direct audience for this kind of data. Most county emergency communications groups are genuinely hungry for systematic coverage assessments and may already have templates or databases for logging exactly this kind of information. Connecting with your local EC (Emergency Coordinator) and offering to contribute structured dead zone data is almost always welcomed.

Shared spreadsheets and community mapping tools like Google My Maps let informal groups build collaborative coverage pictures without needing dedicated software. A simple shared map with pins, signal quality ratings, and test conditions is more useful than most operators realize.

What the Data Actually Changes

This isn't just an academic exercise. Aggregated dead zone data has real downstream effects.

For emergency planners, knowing where communication gaps exist before a crisis means being able to plan around them—staging relay operators, pre-positioning portable repeaters, or routing response teams along paths where communications will remain reliable.

For repeater trustees, coverage gap reports can inform antenna adjustments, power level changes, or the case for adding a linked node in an underserved area.

For individual operators, knowing your local dead zones means you can plan your own backup strategies in advance. If you know that the valley road near your house is a consistent dead zone on 2 meters, you can pre-program a simplex fallback frequency, test a different band, or identify a relay point before you need one.

The Knoxville group that found their valley gap ended up working with the county emergency manager to position a portable repeater at a key high point along that route—something that's now part of their standard activation protocol. It happened because someone drove the road, logged the data, and shared it with the right people.

Your neighborhood has gaps. Somebody needs to go find them. It might as well be you.