Wildfire ICP Communications: Building a Reliable Incident Command Post Network

What an ICP Communications Network Actually Needs to Do

A wildland fire Incident Command Post can grow from a few folding tables under a canopy to a full camp with hundreds of personnel in 24 to 48 hours. The communications system needs to support all of it: voice radio coordination across multiple branches and divisions, internet access for ICS software and resource ordering, VoIP phone service for Finance and Logistics, video feeds from aerial resources, and data replication to the Geographic Area Coordination Center (GACC).

All of this has to be set up fast — often by a Communications Unit (COMU) with limited personnel — in a location chosen for proximity to the fire, not for its connectivity. That might be a gravel pit off a Forest Service road, a fairground in a rural county, or a pasture with no infrastructure within miles. The communications unit leader (COML) who arrives at an ICP expecting a network to already be there is in for a rough assignment.

The core requirements for a well-functioning ICP network:

• Backhaul to the outside world — reliable internet, typically via satellite, often with a cellular backup
• Local wired and wireless LAN — serving the command tent, finance/logistics trailers, and briefing areas
• VoIP telephone system — replacing the cell phones and shouting that characterize under-resourced ICPs
• Radio gateway integration — connecting tactical radio channels to the IP network for remote monitoring, recording, and patching
• Power reliability — UPS-backed core equipment so a generator hiccup doesn't take down the network mid-briefing

Backhaul: Why Starlink Changed ICP Communications

Before Starlink's low-earth orbit constellation became widely available, ICP backhaul was a genuine problem. Traditional geostationary satellite (VSAT) delivered 5–20 Mbps with 600ms+ latency — barely usable for ICS software, borderline unusable for VoIP without significant quality engineering, and impossible for video. Cellular coverage in the terrain where most large fires occur is inconsistent at best.

Starlink changed the equation significantly. A single Starlink terminal at an ICP delivers 80–200 Mbps with 20–40ms latency — sufficient for dozens of simultaneous ICS users, high-quality VoIP, and moderate video. Setup is under 30 minutes with a trained installer. The dish can operate on generator power and fits in the back of a pickup.

For 2026 deployments, the standard Richesin Engineering ICP backhaul architecture uses two Starlink terminals in a bonded configuration, providing 150–350 Mbps aggregate with automatic failover. If one terminal loses connectivity due to a smoke event, obstruction from an airtanker, or equipment issue, the second carries the full load transparently. A cellular modem on the best available carrier provides a tertiary backup for critical traffic — not enough bandwidth for general use, but enough to keep ICS software and radio logging running if both Starlinksterminalsgo down.

A single Starlink outage during an active air attack can delay retardant drop coordination. Bonded redundant backhaul is not a luxury for large fire ICPs — it's a minimum standard for Type 1 and Type 2 operations.

Local Network Architecture: Building It Right Under Pressure

The ICP local network connects everything at the incident base. The typical layout:

• Core router/firewall — connects the bonded backhaul links to the local LAN, enforces traffic policy (QoS for VoIP, rate limits for non-essential use), and provides DHCP/DNS for camp devices. A ruggedized unit in a weatherproof case, on UPS power.
• Managed switches — distributing wired connections to the command tent, finance trailer, logistics section, and medical unit. Wired connections are preferred over Wi-Fi for ICS workstations — more reliable, easier to troubleshoot.
• Wi-Fi access points — covering the briefing area, crew bus areas, and general camp for crew internet access. Separate SSID and VLAN from the operations network so crew personal device traffic doesn't impact ICS performance.
• VoIP PBX — running on a local server or a small appliance, providing internal extensions to every section and direct-dial to external numbers via SIP trunk over the Starlink backhaul. The Finance Section's ability to process resource orders by phone rather than relying on cell service alone is consistently one of the highest-value items on any large fire ICP.

Network segmentation matters on a fire ICP in a way it doesn't always register with incident management teams. Operations traffic — ICS, resource tracking, radio logging — should be on a separate VLAN from crew internet access. A crew member running a 4K video stream shouldn't be able to degrade the Dispatch desk's connection to ROSS (Resource Ordering and Status System).

Radio Integration: Connecting the Tactical Net to the IP World

The tactical radio network — the P25 or analog VHF/UHF channels assigned by the COML — is the lifeblood of field communications on a wildland fire. The ICP communications setup should interface with this radio network in several ways:

• Radio logging recorders — all tactical and command channels should be recorded digitally. This is a legal requirement on federally managed fires and critical for after-action review when things go wrong. IP-connected recorders (Baird Communications ProLog or equivalent) can archive to cloud storage via the Starlink backhaul.
• Radio-over-IP (RoIP) gateway — allowing remote IC staff, GACC coordinators, or aviation resources to monitor and participate in radio traffic via the internet. This is increasingly standard on Type 1 operations and valuable for coordinating with state or county EOCs that don't have radio interoperability.
• Interoperability patching — connecting otherwise incompatible radio systems through the IP network. Federal and state agency radios often operate on different systems (P25, VHF analog, 800 MHz) that don't talk directly. A properly configured RoIP gateway patches them together, enabling the kind of cross-agency coordination that prevents the communication breakdowns documented in post-fire reviews after major incidents.

Power Planning: The Communications Network Can't Run on Hope

ICP power comes from generators, and generators fail — they run out of fuel, they overheat in August, a forklift hits the distribution panel. The communications network must be designed to survive generator interruptions.

Core network equipment — the router, core switch, VoIP PBX, and backhaul terminals — should be on UPS with at least 30 minutes of runtime at full load. That's enough time to refuel a generator, transfer to a backup generator, or gracefully shut down ICS systems without data corruption or loss of active VoIP calls. Starlink terminals draw about 50–75W each; a router and managed switch add another 40W. A 1500VA UPS is adequate for a small ICP; larger operations should size up accordingly.

Generator fuel management is a logistics function, but the Communications Unit should have a direct line to the Logistics Section Chief to flag when fuel is getting low. An empty generator tank is a communications outage.

Pre-Season Preparation for Oregon, Alaska, and Hawaii Operations

Fire season readiness means having equipment staged and tested before the first dispatch, not assembled from whatever's in the warehouse when the call comes in. Richesin Engineering maintains pre-configured ICP communications kits — bonded Starlink backhaul, router, managed switches, VoIP PBX, and cabling — that can be on a truck within hours of a dispatch call and operational at an ICP in under three hours of arrival.

For Oregon operations, we coordinate with ODF (Oregon Department of Forestry) and USFS Region 6 communications units. For Alaska, logistics pre-positioning is critical given the access challenges — we stage equipment in Anchorage and Fairbanks for quick deployment to interior and coastal fires. Hawaii operations are coordinated through DLNR and County fire departments on the neighbor islands.

If your agency or incident management team is planning ICP communications for 2026, now — before the first Type 1 dispatch — is the time to get this sorted.