TAD & Color Nets: Tactical Frequency Presets for Afghanistan Theater

One lesson learned from coalition operations in Afghanistan is that each JTAC must be assigned a discrete TAD frequency and must not share that TAD with other JTACs or, worse, other C2 agencies. Sharing TAD nets increases deconfliction burden, raises the risk of fratricide, and degrades the JTAC’s ability to control terminal attack precisely.

In 2003, one of the first "lessons identified" from Afghanistan was: each JTAC must be assigned a different TAD frequency.

Here, we don't want to discuss this particular lesson, but rather explain what exactly is a TAD net, who uses it, and why does it matter in military operations. So let's try to examines the rationale and history behind coded tactical frequencies, and apply it to the Afghan theater in DCS World.

I. Use of Coded Military Frequencies

I.1 - Origins

The need to codify radio frequencies arose rapidly as radios became central to cooperation in combat. Early military radios relied on fixed numeric frequencies, which were straightforward but exposed operations to interception, spoofing, and later jamming. By World War II and into the Cold War, militaries began developing procedural and technical solutions to protect tactical communications.

Assigning code names, slot numbers, and later using LPI (Low Probability of Intercept) waveforms such as HAVEQUICK allow forces to communicate effectively without broadcasting the exact frequency they're going to use over the air. The Tactical Air Direction (TAD) net concept was created as a standardized way of assigning tactical frequencies.

Each of the oblong shapes shown beneath the frequency scale in the middle of the picture represents a single hop of a transmission.

I.2 - Why Coded Frequencies Are Used

There are three primary drivers for using coded frequency names: human factors, operational security, and administrative efficiency.

From a human perspective, short, standardised labels such as "TAD-120" significantly reduce the time required to relay instructions over the radio and lower the chance of error. Saying “TAD-120” is faster, clearer, and less error-prone than “231.250 MHz,” particularly in noisy, high-stress environments where mishearing a single digit could result in serious consequences.

From an operational security standpoint, coded labels hide the numeric frequencies to unintended listeners. Even if a hostile force intercepts the call, knowing “TAD-120” does not reveal the actual UHF channel. This limits the effectiveness of passive collection, reduces the risk of spoofing, and complicates jamming attempts. Nonetheless, modern electronic warfare systems are capable of scanning large portions of the spectrum and can quickly identify active frequencies, making coding a procedural layer rather than a technical security measure.

Finally, the use of coded names simplifies administrative work and document maintenance. For example, SPINS (Special Instructions), operational orders, and mission briefs can consistently reference TAD or colour names. If numeric frequencies change due to theatre reassignment or spectrum management, only the frequency tables need updating, rather than every document where the net is mentioned. This single-point update capability is particularly valuable in coalition operations, where multiple services or nations may be operating on the same TAD nets under dynamic conditions.

II. NATO examples

II.1 TAD frequencies

TAD (Tactical Air Direction, and not Tactical Air Designator as often said) is originally a tactical voice net used to direct and coordinate aircraft in a local battlespace. The concept grew out of the need to separate high-tempo, time‑sensitive tactical chatter from higher‑level command nets and to give terminal controllers, airborne controllers or strikers a common frequency to exchange on the radio. The practice of slotting those nets into named TAD channels (TAD.001, TAD.002, etc...) provided a stable, brief label that both planners and aircrew could use even as the numeric frequency assignments changed between ATOs.

Example of TAD frequency table from DCS "Operation Inherent Resolve" mission.

In public monitoring lists you can see real life examples: several operational frequency list circulate among listeners and shows entries such as “257.800 TAD.002 NATO TOWER” and “362.300 TAD.005 NATO APPROACH,” which directly map a numeric MHz value to a TAD slot and a role (tower, approach). That is exactly the kind of mapping that the daily COMPLAN (Communication Plan) sent along with the SPINS or ATO provides to aircrew.

362.300 or "NATO 5" and 257.800 or "NATO 2" are TAD frequencies used by many military airfields for Approach and Tower respectively.

TAD nets use primarily the UHF band where tactical air‑to‑air and air‑to‑ground voice is standardised across NATO. That band is also where HAVEQUICK and SATURN frequency‑hopping systems operate to reduce jamming and interception risk. In theatre, commanders publish a table of TAD slots (often dozens of slots covering multiple purposes like strike, AWACS, tankers, JTAC, etc...) and the brief for a strike package will refer to the TAD name rather than the naked numeric frequency.

Obviously, flying with the most up-to-date frequency table is paramount...

II.2 Color frequencies

Color nets are a parallel convention to TAD slotting: instead of using sequential numeric slot names, planners assign short color names (Aqua, Khaki, Iron, Gray, etc.) to individual tactical nets so crews can say “switch to Aqua‑21” or “monitor Khaki-12” rather than read long frequency numbers. The purpose is exactly the same as numbered TAD slots: human factors for brevity and error reduction, plus an extra layer of OPSEC because an eavesdropper hearing “Khaki‑03” must possess the current frequency table to translate that to a numeric channel. Color naming is widely used in operational theaters, like in Afghanistan.

As briefly discussed in the introduction, In Afghanistan the coalition’s communications complexity (with many JTACs) reinforced the operational need to assign discrete nets to terminal controllers rather than force them to share a single net. Analyses and doctrinal fire planning from the period (and subsequent training publications) emphasise that JTACs should have dedicated net assignments to avoid talk‑over, deconfliction problems, and the risk of mis‑identifying the controller with authority to release weapons.

Obviously, full numeric mappings of colour names and slot tables for Afghanistan are sensitive and are not published unredacted in the open. Interestingly, as a non-native English speaker, I discovered that the most usual colors like "blue", "red", "pink", "orange", etc... were generally not used, and that exotic colors like "crimson", "tan" or "teal"were preferred!

Apparently, teal is the iceberg's color...

III. Application in DCS World

Bringing the TAD or color nets into DCS World requires a lot of discipline. Emulating the operational practice means assigning discrete TAD or colour-labelled frequencies to each JTAC and C2 agency, just as was emphasised in Afghanistan, and ensuring that AI and other ATC frequencies are not inadvertently assigned to tactical nets.

A practical approach is to build a theater-wide frequency annex, which can becomes the authoritative reference for all future missions. I will try to do this work for my Afghanistan mission template, and I encourage you to use these tables on your own missions if you want.

Note that, just as in real life, there will certainly be future updates to these tables, in order to take into account changes after DCS theater updates, or to answer new mission creation needs.

Example of color frequencies table, with FM, VHF and UHF nets.

Example of color frequencies for default DCS ATC at main military airfields on the Afghanistan theater.

Conclusion

Implementing coded color frequencies in DCS is probably a cosmetic realism feature, but in a multiplayer environment, it reduces radio errors, and provides players with a structured way to manage complex tactical communications. Beyond the in-game benefits, adopting this system also makes documentation easier to maintain over the long run: labels remain stable even if numeric frequencies change, so mission briefs or documents require fewer updates when the operational plan evolves.

The current frequency table is probably sufficient to cover the needs of most virtual squadrons and mission types. However, the system is easily expandable. Additional colors or numeric slots can be added without disrupting the existing structure.

For reference, attached are the four pages of color tables along with the DCS default ATC frequencies illustrated in the example above.

The most attentive readers may have noticed that the color frequencies discussed here were prefigured in the firing range documents.