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.
Mesh is a supplement, not a lifeline. LoRa mesh is best-effort with no guaranteed delivery: messages can silently fail to arrive, the shared half-duplex channel saturates under load, and coverage depends on powered relay nodes being in range. It is not a replacement for 911, NWS alerts, or licensed amateur/voice nets. Assign assured-delivery and life-safety traffic to voice with confirmed receipt (or Winlink for a record copy); use mesh for supplemental status, position, and welfare data.
ARRL ARES Structure
ARES is organized and administered by the American Radio Relay League (ARRL). It has four organizational levels - national, section, district, and local - and interfaces with / operates under ICS during activations rather than literally mirroring ICS/NIMS at every tier:
- Emergency Coordinator (EC) - Local (county or city) point of contact, recruits and trains volunteers, coordinates with served agencies.
- District Emergency Coordinator (DEC) - District-level coordinator overseeing several local ECs within a section.
- Section Emergency Coordinator (SEC) - Section-level coordinator (assistant to the Section Manager for emergency preparedness); ARRL Sections do not always correspond to states - several states contain more than one Section.
- Assistant EC (AEC) - Functional leads for specific disciplines, for example digital, VHF, HF, or public events. These discipline assignments are examples set locally by the EC, not a fixed national list (see the ARRL ARES manual).
- 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 authorized under 47 CFR §97.407 and operates only at the direction of the responsible civil-defense / emergency-management official - during emergencies and during authorized drills and tests. Routine RACES training drills and tests are expressly permitted (limited to a total of 1 hour per week without a declared emergency, with longer drills only by approval of the responsible official). Unlike ARES, which can operate at any time, RACES operation requires:
- Direction or authorization by the responsible civil authority (city, county, or state emergency management office) - either for an emergency or for an authorized drill/test.
- 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 activation.
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. While 902-928 MHz is a shared band, this unlicensed Part 15 operation is independent of Part 97 amateur authority, creating a clean separation of roles:
| Capability | HF/VHF Voice | LoRa Mesh |
|---|---|---|
| Long-distance voice relay | Excellent (HF) | Not applicable |
| Structured digital forms (ICS213) | Commonly via Winlink or other digital forms tools (FLMSG), or relayed by voice using formal message-handling procedures | Plain-text only; ICS form data must be manually condensed into ~230-character messages (no native structured-form transport) |
| Position tracking (blue force) | Via APRS (separate system) | Native GPS position sharing |
| Welfare traffic (check-ins) | Voice net, slow | Asynchronous text, fast (best-effort) |
| License required | Yes (Technician+) | No, IF operated under Part 15 (FCC-certified equipment, 1 W / 30 dBm conducted max, must accept interference and cause no harmful interference). Default-encrypted Meshtastic cannot lawfully move to amateur frequencies. |
| Deployed infrastructure needed | Repeaters, linked systems | Self-forming ad-hoc mesh |
Mesh nodes are useful for low-bandwidth supplemental data: ICS form text, GPS tracks, welfare check-ins, and resource status messages. Note that mesh transport is best-effort with no guaranteed delivery and very limited store-and-forward; assign assured-delivery traffic (formal ICS forms needing a record) to Winlink/voice and use mesh for supplemental, confirm-when-it-matters data. Voice radio remains superior for command coordination, situational awareness broadcasts, and long-haul links.
Under FCC Part 15, the 915 MHz limit is on conducted transmitter output power - up to 1 W (30 dBm) for frequency-hopping/digital systems per 47 CFR §15.247 - with separate provisions governing antenna gain and EIRP (antennas above 6 dBi require a dB-for-dB reduction in conducted power). "1 W EIRP" is not the correct phrasing for the limit.
Digital Data Transport Use Cases
- ICS Forms: ICS 213 general messages and ICS 214 activity logs can be sent as plain-text messages (manually entered, or via external tooling - there is no built-in ICS-form module) over mesh hops toward an EOC node for printing or forwarding via Winlink. Mesh delivery is best-effort and not guaranteed, so a form sent this way is not assured to arrive; use Winlink/voice when a record copy must be delivered.
- 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 a TAK server via atak-forwarder. Note atak-forwarder is a third-party project; verify it is still maintained and compatible with your current Meshtastic firmware before relying on it (as of this writing).
- 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 - on a best-effort basis.
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?
- Liability and risk allocation: limitation of liability, mutual indemnification, insurance/coverage expectations, and an explicit clause stating that mesh is a supplemental, best-effort capability with no guaranteed delivery and is not to be relied upon as a primary or life-safety channel. Have counsel review any MOU before signing.