NIFOG and Mutual Aid Channels: Inter-Agency Communications That Actually Work

What NIFOG actually is (and isn't)

NIFOG stands for the National Interoperability Field Operations Guide. It is a small, pocket-sized reference document published by CISA (formerly under the DHS Office of Emergency Communications, now part of the Cybersecurity and Infrastructure Security Agency). Its full title in the current edition is the "National Interoperability Field Operations Guide" and it is available as a free PDF at cisa.gov/safecom. Paper copies are distributed at conferences and through state SWICs (Statewide Interoperability Coordinators).

What it contains: the frequencies, tones, channel names, and usage rules for every nationally-designated interoperability channel across the VHF low band, VHF high band, UHF, 700 MHz, and 800 MHz spectrum. It also carries a short section on incident radio operations, ICS-205 forms, and the tone standards used by the federal interoperability channels.

What it is not: a license. Carrying NIFOG in your pocket does not give your department permission to transmit on any of the channels it lists. You still need the underlying FCC Part 90 authority. More on that in the licensing section.

What it is also not: a replacement for your regional Tactical Interoperable Communications Plan (TICP) or your state's Statewide Communication Interoperability Plan (SCIP). NIFOG is the national baseline. Your region will have layered on top of it. If your county has a "Fireground 3" that is not in NIFOG, that channel is defined in a regional plan, and NIFOG will not help you find it.

The national interoperability channels, by band

The channels are grouped by band, and each band has a specific mix of "CALL" channels (for initial contact and coordination) and "TAC" channels (for tactical operations). Every one of them is defined in FCC Part 90 and has a nationally standardized name, frequency, and CTCSS/NAC tone. Here is the working overview.

VHF high band (150 to 174 MHz)

The VCALL/VTAC channels use a standard CTCSS PL tone of 156.7 Hz. VFIRE channels use varying tones depending on the state plan they came from. Confirm against the current NIFOG edition and your state plan before programming.

UHF (450 to 470 MHz)

UHF versions of these have both repeater and direct (simplex) variants. On the repeater versions, the mobile transmits 5 MHz below the base frequency listed. UCALL40D is the direct/simplex variant of UCALL40. Get the D wrong and your radio will key up looking for a repeater that isn't there.

700 MHz

700 MHz interoperability channels are all defined for narrowband P25 digital operation. They are broken into 8CALL and 8TAC-numbered channels in the 700 MHz public safety band, plus the 7CALL/7TAC group. These are designated by FCC rule for public safety interoperability only, and the tone standard is NAC (Network Access Code) 293 by default. If you are running a legacy analog VHF system and your mutual aid partner is 700 MHz P25, you are not going to talk to each other on the air. That's what a cross-band gateway or a console patch is for.

800 MHz

The 800 MHz interop channels went through rebanding a decade ago. Radios that were programmed before rebanding and never got refreshed will be on the old frequencies. If your department still has legacy 800 MHz radios in a spare kit, pull them out, put them on the bench, and verify against the current NIFOG.

CALL vs TAC: how they're supposed to be used

The distinction matters, and it is the thing most departments get wrong.

CALL channels are for initial contact. When a mutual aid unit arrives from three counties over and doesn't know your fireground assignments, they call your IC on VCALL10 (or UCALL40, or 8CALL90, depending on band). The IC answers, tells them "switch to VTAC12", and the working traffic moves off the CALL channel immediately.

TAC channels are for the actual work. Once units are on TAC, the CALL channel goes back to standby so the next arriving agency can use it to find you.

Where this breaks down: departments treating VCALL10 as a tactical channel. If you run a full working structure fire on VCALL10 for 40 minutes, no one else in the county can raise anyone on the calling channel. Every neighboring mutual aid asset that arrives will keep trying, get nowhere, and then default to their own dispatch channel. Interop dies at that point.

The correct pattern:

1. Incoming mutual aid unit arrives at scene perimeter, keys up on the appropriate CALL channel.
2. IC or comm officer answers, assigns them to a TAC channel and a division.
3. The unit acknowledges and switches to TAC.
4. CALL channel returns to standby.

Short. Boring. Correct.

Programming: names, tones, and the little details that trip people up

The most preventable failure in mutual aid comms is a radio that has the right frequency programmed under the wrong name, with the wrong tone. Here is what to get right.

Use the standard channel names, exactly

NIFOG standardizes the names: VCALL10, VTAC11, UCALL40, 8TAC91, ICALL. If you program VCALL10 as "MUTUAL-1" or "COUNTY CALL" on your local radios, then when a chief from three counties over says "switch to VCALL10" over the air, your firefighter is scrolling looking for something that doesn't exist by that name on their radio. Use the standard name in the display. If you must add a local prefix, do it as a suffix: VCALL10-CTY, not CTY-CALL1.

Program both the analog and P25 variants where applicable

Some of the interop channels have both analog and digital modes defined. 8CALL90 is P25 only. ICALL is analog only. But for the 700 MHz and some UHF channels, you may want both a digital and analog version programmed as separate channels. Label them clearly: UTAC41A For analog, UTAC41D For digital.

Get the tones right

NIFOG specifies both TX and RX tones for every channel. The most common error: programming carrier squelch on receive when the standard specifies a PL/NAC tone. Result: the radio hears every off-frequency user in a 60-mile radius and won't lock onto the actual incident traffic. The other direction is worse: programming a tone on TX that is not the NIFOG standard, so nobody on the interop channel can hear you at all.

Repeater vs direct

Most VTAC/UTAC channels have both repeater outputs and direct (simplex) operation defined. On scene, the IC decides which is in use, and every unit needs to be on the same one. If your channel plan is VTAC12R For repeat and VTAC12D For direct, make sure both are programmed and labeled clearly.

Bandwidth

All public safety land mobile radio operating below 512 MHz has been narrowband (12.5 kHz) since the FCC deadline in 2013. If you have a legacy radio that is still programmed wideband (25 kHz) on any of these channels, it is out of compliance under 47 CFR Part 90.209, and it will also cause interference to adjacent-channel users. Retire the radio or reprogram it.

FCC Part 90 licensing and who is allowed to use these

The national interoperability channels are governed under 47 CFR Part 90, specifically the public safety pool rules in Part 90.20. Here is the short version.

The channels are FCC-authorized for use by public safety agencies that hold a valid Part 90 license. You do not need a separate license for each interop channel if your agency's Part 90 license covers the appropriate radio service (fire, EMS, law enforcement, or emergency management). The interop channels are covered under blanket authorizations that FCC granted for public safety interoperability.

Where this trips up small volunteer departments:

• Your department needs an active Part 90 license. Not the county's, not the neighboring city's - yours. If your license expired five years ago and you never renewed, every transmission you make is technically unlicensed.
• Federal channels (VTAC17, UTAC44, and some 700 MHz assignments) have additional restrictions. These are shared with federal users and use standards defined in the DHS/CISA plans. Some require pre-coordination with a federal partner agency before use outside an actual incident.
• Testing and training use is allowed but should be brief. The FCC and CISA both encourage regular testing of interop channels. Extended training on a national CALL channel is not appropriate. Use a TAC for that, and keep it short.

For the current license status of any FCC callsign, check the FCC Universal Licensing System at wireless2.fcc.gov/UlsApp. Search by callsign or by frequency and confirm your renewal date. Part 90 licenses run 10 years and there is no grace period once expired.

On-scene: making the switch on a real incident

Interoperability is a training habit, not a technology feature. When the working fire has three towns responding, a state fire marshal en route, and the county EMS supervisor showing up in a Tahoe, someone has to make the call to go interop, and that someone is the IC or the assigned comm officer.

The pattern that works:

Step 1: Announce it early

As soon as the incident escalates to multi-agency status, the IC (or the assigned communications unit leader if the incident is big enough for one) announces on the primary dispatch channel: "Command to all responding units, switch and monitor VCALL10 for tactical assignment." Every incoming unit hears it and knows the plan.

Step 2: Assign TAC channels by function, not by agency

Do not assign VTAC12 to "Town A" and VTAC13 to "Town B". Assign VTAC12 to "Fire Attack" and VTAC13 to "Water Supply". The units on those channels are performing that function regardless of what patch is on their sleeve. This is what an ICS-205 is for, and it's why the ICS-205 belongs on the IC's clipboard before mutual aid arrives, not after.

Step 3: Document the plan on the ICS-205

The ICS-205 Incident Radio Communications Plan is a one-page form. Fill it out. Every function gets a channel, every channel gets a name that matches what's in the radios, and the form gets copied to every unit leader. NIFOG has a copy of the ICS-205 template in the back for exactly this reason.

Step 4: Have a fallback

The primary interop channel goes bad. Interference, coverage hole, congestion, radio failure. What's your fallback? The ICS-205 should list it. VTAC12 is primary, VTAC13 is backup. If both are unusable, revert to direct (simplex) on the same channel, or shift to the UHF equivalent. Everyone should know the fallback before it's needed.

Why mutual aid comms fail in practice

Here is the honest list of reasons interop fails on real incidents, ranked by how often it happens in small and mid-size department territory.

1. Nobody switched to the interop channel. The IC never made the call, mutual aid arrived on their own primary dispatch, and the two sides never talked directly on the air. Coordination happened face to face at the command post, which is fine at a house fire and terrible at a wildland incident.
2. The channel is programmed with the wrong tone. Analyst on the state SWIC team pulls a code plug during an after-action, finds VCALL10 programmed with PL 100.0 instead of 156.7. Every transmission was going out fine but nobody with correct programming could hear it.
3. Different bands, no gateway. Town A is VHF, Town B is 800 MHz P25 trunked. Both radios have their own interop channels programmed correctly. Neither radio can reach the other because they're on different physical bands. The county needs a cross-band gateway or a mutual aid channel that both sides have on a shared band. If neither exists, plan for runners.
4. Expired FCC license. Discovered during an FCC enforcement inquiry, not by the department itself.
5. Radio doesn't have the channel at all. Old radio, old code plug, never updated. This is the reason to run an interop check every time you accept a used radio into service and every time your radio tech does a fleet reprogram.
6. Radio is on wideband on a narrowband channel. Not just a compliance problem, this actively causes bleedover into the adjacent channel.
7. Nobody trained on the switch procedure. The channel is programmed, the tone is right, the license is current. And the driver of Engine 3 has never actually rotated to VTAC12 on this radio before, so on scene he's fumbling through 200 channels looking for it.

Drills and training that actually build the habit

The best departments treat interop like SCBA. You don't want the first time your firefighter dons a mask under stress to be at a working fire. You also don't want the first time a company officer rotates to VTAC12 to be at a working mutual aid incident. Here is what small-department training programs actually look like.

Monthly radio check

Once a month, every apparatus does a quick radio check on VCALL10 (or the appropriate band-CALL channel for your area). Dispatch or a designated station acts as the anchor. Every rig keys up, IDs, and confirms. Takes ten minutes for the whole department. Catches dead radios, wrong-tone radios, and unfamiliar operators.

Quarterly interop drill

Once a quarter, run a joint drill with a mutual aid partner department that involves actual channel changes on the air. Not a tabletop. Real radios, real switches. Start on your dispatch, get toned out, respond, and hit VCALL10 to check in with the joint IC. Move to VTAC. Practice the handoff. Debrief afterwards on what was clunky.

Annual regional exercise

At least once a year, participate in a regional exercise that involves the state SWIC, multiple counties, and multiple disciplines. This is where the gateway and cross-band problems show up. Do not skip these because they take a day. The lessons learned are the ones that keep a firefighter alive when the real incident happens.

New member checkoff

Every new member of your department, career or volunteer, should have to demonstrate the ability to switch to VCALL10 and back to primary dispatch on their assigned radio before they are cleared to run calls. Add it to the same checkoff sheet that has SCBA and hoseline operations. Ten minutes of training saves an hour of confusion on scene.

A field checklist for the comm tech

If you are the person in your department responsible for radio programming, maintenance, or comm planning, here is what should be on your annual review checklist.

• Current NIFOG PDF downloaded and printed for reference. Check the CISA site quarterly for a new edition.
• State SCIP and county TICP on file. Reviewed against your current fleet code plug.
• FCC Part 90 license current, renewal date noted, backup contact identified in case the license administrator retires.
• Every radio in the fleet has the standard national interop channels programmed with correct frequency, correct tone, correct bandwidth, correct name.
• Regional and state interop channels programmed per your TICP/SCIP.
• Cross-band gateway (if you have one) tested monthly with a real interop check.
• ICS-205 template printed and stored on every command vehicle.
• Monthly radio check on VCALL10 (or band-appropriate CALL channel) on the training schedule.
• Quarterly interop drill with at least one mutual aid partner.
• New member radio checkoff signed for every operational member.
• Code plug backup stored in at least two locations, one off-site.

That checklist covers about 90 percent of the reasons mutual aid comms fail in real incidents. Work through it once a year, and the next multi-agency call gets a lot easier to run.

Further reading

• CISA SAFECOM Technology page - source for the current NIFOG PDF and related interop resources.
• FCC Public Safety and Homeland Security Bureau - Part 90 rules and public safety licensing guidance.
• SAFECOM Interoperability Continuum - the framework most state SCIPs are built against.
• NFPA 1221 (now consolidated under NFPA 1225) - installation, maintenance, and use of emergency services communications systems.

Closing note

NIFOG is not a hard document. It is 130 or so pages of frequencies and rules that a comm tech can read in an afternoon. What is hard is the day-to-day discipline of keeping fleet programming correct, licenses current, and crews practiced. Departments that get interop right are not the ones with the most expensive radios. They are the ones where the newest volunteer knows exactly how to get to VCALL10 without thinking about it, and where the chief has an ICS-205 filled out before the mutual aid engine arrives.

Get the fundamentals right and the technology carries you the rest of the way.