This is Part 4 of a series on SAR and EMA mesh radio SOPs, built on field guidance from Kenny Cornett at Appalachiastan Technologies (AT-Labs). Part 1 covered the four rules for deploying LoRa mesh in the first place. Part 2 covered how that position data becomes a common operating picture. Part 3 covered which of the three platforms actually fits your operation. This one covers something every one of those platforms depends on: where you put the radio.
Catch up on Part 1 — Four Rules for Deploying LoRa Mesh in Emergency Management, Part 2 — A Common Operating Picture is Worth a Thousand Words, and Part 3 — The LoRa Wars if you haven't already.
If you found this helpful or interesting, consider picking up one of the ultra-rugged radios made by Appalachiastan Technologies on our store — browse the AT-Labs radio lineup.
Are you part of a government or volunteer SAR or EMA organization? You can apply for grant funding through our Funding Reach portal.
"What Kind of Range Does That Thing Get?"
Our favorite question (not really) is the range question. The RM-radios get best-in-class range, but plenty of factors affect it: geography, atmospheric conditions, weather, even solar storms. The biggest variable, by a wide margin, is elevation.
An AT-Labs RM-2 infrastructure node, placed at a well-chosen elevated position with a quality antenna, is currently achieving first-hop coverage in excess of 100 miles under real operational conditions. That's not a lab number or a controlled-environment claim — that's a deployed node punching across real terrain. The same radio at ground level in the same location covers a fraction of that distance. A small number of well-placed elevated nodes can deliver coverage that a much larger number of ground-level nodes never will, no matter how many you add.
Elevation as a Force Multiplier
Here's the variable that matters more than platform choice, more than hardware spec, more than almost anything else in this series: elevation.
Radio communication is a line-of-sight technology at its core. Terrain, vegetation, and structures all cut into signal, whether you're running traditional ham radio or mesh. The old saying holds: "Height is Might."
But mesh radios offer more flexibility than planners used to VHF or UHF coverage typically expect.
Tower sites, hilltops, water towers, fire towers, apparatus light towers — all of them are elevation opportunities worth identifying during network planning, at any scale, tactical or strategic. Antenna selection compounds the effect: on an elevated node, a quality directional or high-gain omnidirectional antenna is core to the design, not an accessory. Bottom line — mesh planning at any scale is a terrain problem before it's a radio problem. Figure out the topography of your AO, find the high ground in it, and design node placement around that before you worry about anything else.
Airwaves? The Sky's the Limit
Ground elevation isn't always available when you need it. Sometimes the highest point in the AO is still low, or it's an hour of hiking away from where the mesh actually needs to extend. That's where airborne nodes change the math entirely.
A small unmanned aerial system with a mesh node secured to the airframe is one of the most significant force multipliers available to a field communications team right now. It doesn't need to be a sophisticated platform to be effective — a capable consumer UAS carrying a node aloft can re-establish mesh connectivity across a significant area in minutes, in terrain that would otherwise take hours of ground work to cover, if it could be covered at all. A drone is simply the fastest way to get elevation when the ground doesn't offer any.
The planned version of this is more powerful still. AT-Labs' SignalReach network-planning tool supports modeling UAS nodes directly — flight profiles and node parameters evaluated against real terrain before an incident, alongside fixed infrastructure locations, so a drone launch during an actual response isn't a first-time experiment. It's execution of a plan that was already proven on a map.
AT-Labs Tool — SignalReach: Instead of placing a node and seeing what it covers, SignalReach starts from the area of operations — KML import or a drawn boundary — and works backward: available resources (radio types, transmit power, antenna characteristics, deployment height), fixed known node locations, must-cover areas and keep-out zones, and UAS airborne nodes with their own flight profiles. It evaluates topography against radio physics and returns a placement recommendation grounded in terrain analysis, not a coverage map generated after the fact. A regional disaster response organization and Cumberland County Rescue Squad both currently use it for network planning.
When the Mesh Doesn't Need to Be Continuous — Just Predictable
Elevation solves range. It doesn't solve every coverage gap — degraded meshes with intermittent nodes or hard terrain obstacles still happen, even with good planning. That's where delay-tolerant networking earns its place.
Delay-tolerant networking — implemented through store-and-forward nodes, sometimes called BBS systems — lets a message wait at an intermediate node until a path opens, rather than requiring sender and recipient to be reachable at the same moment. During the Hurricane Helene response, mesh coverage in the affected area was uneven: some corridors had solid connectivity, others didn't. Coordinators mapped where reliable coverage existed, established known rally points, and ran a scheduled store-and-forward workflow — messages composed in the field whenever ready, collected at coverage points on a set interval, forwarded when a path opened. Teams knew when and where to expect message pickup. Command knew when to expect field traffic. The mesh didn't need to be continuous to be useful. It needed to be predictable.
That's worth building into regional mesh planning from the start, alongside elevation and node placement — not discovering it as a workaround after the mesh is already standing.
Wrapping Up
Platform choice (Part 3) decides how data moves through your mesh. Delay-tolerant networking decides what happens when that mesh isn't continuous. And underneath both of those, elevation decides how far any of it reaches — whether that elevation comes from a tower, a hilltop, or a drone that got there in five minutes instead of an hour on foot. Plan the terrain before you plan the radio.
Coming Up Next
This series continues with a closer look at what LoRa mesh actually is — and isn't — underneath the marketing language: what it's good for, what it categorically doesn't replace, and where it fits next to the radios your team already trusts.
Working through the full series? Here's where to find the rest:
- Part 1 — Four Rules for Deploying LoRa Mesh in Emergency Management
- Part 2 — A Common Operating Picture is Worth a Thousand Words
- Part 3 — The LoRa Wars
Found this useful? Follow us on Instagram, Facebook, and X — sharing these guides goes a long way.
