Integrating LoRa Mesh with ARES/RACES
Overview
The Amateur Radio Emergency Service (ARES) and the Radio Amateur Civil Emergency Service (RACES) are the two primary organized frameworks through which licensed amateur radio operators support public safety and emergency management in the United States. LoRa mesh networks built on the Meshtastic platform are not a replacement for these established systems, but a powerful digital complement that fills capability gaps that voice HF and VHF radio alone cannot address.
ARRL ARES Structure
ARES is organized and administered by the American Radio Relay League (ARRL). Its hierarchy mirrors ICS/NIMS at the local, section, and national levels:
- Emergency Coordinator (EC) - Local (county or city) point of contact, recruits and trains volunteers, coordinates with served agencies.
- Section Emergency Coordinator (SEC) - State-level coordinator, maintains MOU relationships with state agencies.
- Assistant EC (AEC) - Functional leads for specific disciplines (digital, VHF, HF, public events).
- ARES Members - Licensed amateur operators who have completed enrollment and training requirements.
ARES groups typically maintain readiness on 2-meter FM simplex and repeater frequencies, HF voice and digital (Winlink/JS8Call), and increasingly on data mesh platforms. Training follows ARRL-published curricula and may align with FEMA IS-700/IS-100/IS-200 requirements set by served agencies.
RACES - Municipal Affiliation
RACES is a federally authorized program (47 CFR Part 97.407) that activates only under a declared emergency or formal civil defense exercise. Unlike ARES, which can operate at any time, RACES operation requires:
- A formal activation by the civil authority (city, county, or state emergency management office).
- Enrollment of operators with that civil authority - not just ARRL membership.
- Operation only on frequencies and in modes authorized by that civil authority under RACES rules.
Many operators hold dual ARES/RACES enrollment, enabling them to transition from ARES pre-activation operations to RACES operations upon a formal declaration.
How LoRa Mesh Fits Alongside HF/VHF Infrastructure
LoRa mesh on the 915 MHz ISM band (or 868 MHz in Region 1) operates independently of the amateur radio allocations used by HF/VHF operators. This creates a clean separation of roles:
| Capability | HF/VHF Voice | LoRa Mesh |
|---|---|---|
| Long-distance voice relay | Excellent (HF) | Not applicable |
| Structured digital forms (ICS213) | Via Winlink only | Native text/form transport |
| Position tracking (blue force) | Via APRS (separate system) | Native GPS position sharing |
| Welfare traffic (check-ins) | Voice net, slow | Asynchronous text, fast |
| License required | Yes (Technician+) | No (ISM band, Part 15) |
| Deployed infrastructure needed | Repeaters, linked systems | Self-forming ad-hoc mesh |
Mesh nodes excel at persistent, low-bandwidth data transport: ICS form relay, GPS tracks, welfare check-ins, and resource status messages. Voice radio remains superior for command coordination, situational awareness broadcasts, and long-haul links.
Digital Data Transport Use Cases
- ICS Forms: ICS 213 general messages and ICS 214 activity logs can be composed on a device, relayed over mesh hops, and delivered to an EOC node for printing or forwarding via Winlink.
- Position Tracking: Meshtastic built-in GPS position sharing provides a blue-force track of all mesh-equipped operators, visible on the map view of the Meshtastic app or on third-party integrations such as TAK server via atak-forwarder.
- Welfare Traffic: Mass-casualty or shelter-in-place events generate high welfare check-in volume. Mesh text messages allow operators to report status without consuming voice net time.
MOU Considerations with Served Agencies
A Memorandum of Understanding (MOU) between an ARES group and a served agency (hospital, Red Cross chapter, VOAD, county OES) should address LoRa mesh explicitly if it is part of the deployed communications plan. Key provisions to negotiate:
- Which frequency channel preset will be used and how frequency coordination is handled if the served agency operates nearby LoRa sensors.
- Who owns and maintains the fixed relay nodes installed at agency facilities such as a node on the EOC rooftop.
- Data handling: are mesh messages logged, and if so, where? Who has access to those logs?
- Activation triggers: under what conditions does the mesh network activate, and who issues the activation order?
- Training requirements: which agency staff will be issued Meshtastic devices, and what minimum proficiency is required?