Search and Rescue Integration

Search and Rescue teams operate in exactly the environments where cellular infrastructure fails: remote canyons, dense forest, cliff bands, and high alpine terrain. LoRa mesh via Meshtastic can provide a lightweight, rapidly deployable, best-effort, supplementary communications layer that complements existing SAR tools and can improve situational awareness for field teams and command staff. It complements - but does not improve the life-safety reliability of - licensed SAR radio, and must never replace it.

Best-effort caveat: Meshtastic is best-effort with no guaranteed delivery - messages and positions can be delayed, stale, or missing, and coverage requires powered nodes in RF range. SAR does not monitor Meshtastic by default. Use it only as a supplement to the incident's licensed radio system, PLBs/satellite messengers, and established ICS procedure.

Subject Tracking

Passive subject tracking works only under narrow preconditions: the missing subject must be carrying a pre-configured Meshtastic node, set to the team's channel, with position enabled, AND be within RF range of a team or relay node. This is a rare precondition, not a general SAR capability - most lost subjects are not carrying such a device. When those conditions are met, GPS position packets transmitted at the configured interval can appear on team members' maps and help narrow the initial search area - but packets are best-effort, not guaranteed, and absence of a position does not mean absence of a person. Teams may consider distributing pre-configured nodes (Heltec V3 at ~$20 each, as of 2026-06-08) to high-risk populations such as elderly day hikers, youth groups, and solo adventurers on challenging routes - but only as a supplemental aid, never as a substitute for a PLB or satellite messenger for high-risk individuals.

Team Member Position Sharing

Unified Command loses situational awareness as searchers fan into terrain. Meshtastic can maintain a map of equipped team members that are within mesh range. The Incident Commander at the Command Post can see field teams that are reachable on the mesh without requiring radio calls, reducing channel congestion and aiding tactical reassignment. Note that position updates are best-effort, and teams that move out of mesh range will not appear - do not treat presence (or absence) on the map as proof of a team's status; confirm by radio per ICS procedure. Each team member carries a node set to CLIENT role with GPS enabled; the CP runs a node connected to a laptop running the Meshtastic Python CLI or a mapping application.

Command Post Communications

In areas without cell coverage, the CP can relay Meshtastic traffic to outside incident management via a satellite uplink (Iridium modem, Starlink terminal) connected to an MQTT broker. Field teams communicate via LoRa mesh, the CP aggregates data, and the EOC sees position updates over the internet (as received - best-effort, not guaranteed real-time). MQTT forwards only to subscribers of that broker/channel; it does not alert any agency that is not subscribed. Configuration requires a device in MQTT gateway mode pointing to a private broker.

Integration with CalTopo and SARTopo

Meshtastic waypoints and position history can be exported via the Python API or third-party tools and imported into CalTopo as GPX files. The workflow: connect a laptop to the CP node via USB or Bluetooth, run a logging script writing received position packets to a GPX track file, import the GPX into the active CalTopo map every 15-30 minutes, then annotate and share with wider incident management.

Unified Command Considerations

When a mesh operates alongside traditional radio nets, document the channel PSK in the Incident Action Plan communications annex. Designate COML responsibility for mesh infrastructure. Treat the mesh as a supplementary data and messaging layer - not a replacement for ICS radio. Do not allow the mesh to substitute for primary command communications.

Training SAR Volunteers

Training should cover device power-on, channel verification, GPS status check, and basic messaging. A 30-minute tabletop exercise followed by a field practicum simulating a lost-hiker scenario achieves operational proficiency. Keep laminated quick-reference cards in each node go-bag. The Meshtastic Android and iOS apps require a smartphone with Bluetooth; verify volunteers have compatible devices or carry a standalone node with E-Ink display for message reading without a phone.

SAR Go-Bag Node Kit

Store kits in Pelican 1010 micro cases. Rotate power banks into charging after every deployment. Assign one kit per field team and two to the Command Post.


Revision #3
Created 2026-05-03 06:19:20 UTC by Mesh America Admin
Updated 2026-06-10 00:24:36 UTC by Mesh America Admin