A wildland fire crew is operating in mountainous terrain over a five-day deployment. The
Incident Command Post is at the trailhead, three squad bases are spread across the
operations area, and a logistics camp is set up at the watering point two miles downhill.
Cellular is dead. The radios work for voice but can't carry the IC's map. Starlink is
unreliable under the canopy.
The crew deploys a netTAK at every site — five nodes in total, each in a Pelican case,
each running on a 12V battery. Each node powers on and joins the mesh on its own — no
central server, no keys to type, no console cable. Within a minute the cluster has
converged.
Operators connect their ATAK tablets, WinTAK laptops, and iTAK phones to
the closest netTAK's Wi-Fi. The IC drops a marker at the trailhead — every device across
the cluster sees it within seconds, even on the far side of the watershed. When the squad
logistics chief moves between camps, his ATAK tablet roams from one node to the next
without losing the picture.
And the voice net rides the same mesh. A netTAK Voice node in the command
tent gives the IC a hardware push-to-talk handset — keying to every other netTAK and to
every dismount's phone running ATAK's voice plugin. One channel, the whole crew, no repeater
and no separate radio net to stand up.
When one of the squad sites' uplink fails — antenna knocked over by a branch, battery low
— the mesh re-routes around it within seconds. The squad's TAK picture stays current.
Their chat lands at the IC's tent without anyone touching a config.
Five appliances. One self-healing mesh. A real LAN across miles of fire ground.