Design preview · adopts the Kaharagian design system
An official training service of the State of the Kaharagians
SIG 310 Signals NCO Course
Lesson 4 of 10SIG 310

Running the Net and the Detachment

Lesson Overview

The earlier lessons of this course built the plan and the physics. Lesson 02 taught you to write a communications plan and a PACE plan, and Lesson 03 taught you enough about antennas and propagation to get a signal through. This lesson is about the day after the plan is written: the ordinary, unglamorous work of running a section's communications hour by hour, keeping the net disciplined and the kit accounted for, and putting things right calmly when they go wrong. A plan that is never maintained decays within a day. The signals NCO is the person who keeps it alive.

Running the net is partly clerical and partly leadership. The clerical part is real and matters: a frequency and call sign card that everyone holds, a signals log that records what passed and when, a check on every battery, a record of who holds which device and which keys. The leadership part is the net discipline itself, because as the section's net authority you set and enforce the standard for how people speak on the air, when they may transmit at all, and who is allowed near the section's radios, the Meshtastic channel keys, and the Team Awareness Kit certificates. The security disciplines you learned in SIG 220 do not run themselves. Someone has to own them, and on a section that someone is you.

This is the knowledge layer. Reading about running a net does not make you a competent net controller any more than reading about marksmanship makes you a shot. Keeping a calm voice when the net is doubling, working a lost station back in, and managing kit and keys without losing track are habits built by repetition, practised and signed off in person and on airsoft milsim exercises. Live transmission is done only by members who hold the proper licence, or on licence-free and low-power sets where no licence is required; the NCO ensures the section operates within the law. By the end you will be able to build and issue a frequency and call sign card and manage call signs, frequencies, channels and schedules; keep and audit a signals log; act as net authority by enforcing EMCON and net discipline; control access to the section's devices, Meshtastic channel keys, and TAK server certificates as the comms-security discipline of SIG 220 requires; hold the section accountable for kit and batteries; and handle problems on the net, doubling, a lost station, a suspected intruder, and a dead link, calmly and by drill.

Key Terms

  • Net authority (Net Control Station, NCS): the station that directs the net. The net authority sets the EMCON state, opens and closes the net, controls who transmits when, calls the roll, and is the final word on net discipline. On a section it is usually the signals NCO or a nominated operator.
  • Frequency and call sign card: a small, controlled card or card image that lists the call signs, frequencies and channels, the PACE plan, schedules, and any authentication detail for a task. Everyone who works the net holds the current card and destroys the old one.
  • Call sign: the short identifier a station uses on the net instead of a name or rank. Call signs are issued by the net authority, used consistently, and changed when the plan or security requires.
  • Net: the group of stations that work to a common plan on a common bearer, directed by a net authority. A section's voice net, its Meshtastic channel, and its TAK picture are each a net in this sense.
  • Signals log: the running written record of the net, kept in time order, showing the date-time group, the stations involved, and the gist of each message passed. The log is evidence, memory, and audit trail.
  • Date-time group (DTG): a standard time stamp written as day, hour, minute, a zone letter, and the month and year, for example 121530Z JUN 26 for the 12th at 15:30 UTC in June 2026. Z is Zulu, which is UTC. The log runs on DTGs so times are never ambiguous.
  • EMCON state: a named level of emission discipline, from open working down to full radio silence, set so every station knows the rule in force. The net authority enforces it.
  • Doubling: two stations transmitting at the same time, so the net authority hears a garble and neither message gets through. A common, recoverable fault.
  • Lost station: a station that has gone silent or out of contact, whether through a flat battery, a bad position, a fault, or simply moving out of range. The net authority works it back in or accounts for it.
  • Channel key (Meshtastic): the shared secret that defines a Meshtastic channel. Holding the key lets a node join the channel and read its traffic. The keys are controlled property, issued and revoked by the NCO.
  • TAK certificate: the per-user credential that lets a device connect to the Army's TAK server at tak.kaharagia.org and join the shared map. Certificates are issued to named people, controlled, and revoked when a person or device leaves.
  • Accountability: knowing, at any moment, who holds which radio, device, key, and certificate, and that every set has a charged battery and a spare. A flat radio is no radio, and an untracked key is a leak waiting to happen.
  • Communications check: the radio check on every link, the confirmation of the PACE plan, and the confirmation of the TAK picture, done before any task. Comms that are not checked before moving are assumed broken.

The frequency and call sign card

A section's communications begin as a plan, but a plan in the NCO's head is useless to the soldier two ridgelines away. The plan becomes usable when it is written onto a single small card that everyone who works the net holds: the frequency and call sign card. It is the most ordinary document in signals and one of the most important, because it turns the comms estimate from Lesson 02 into something a tired operator can read by torchlight and act on without asking.

A good card is short, fits in a pocket or on a phone screen, and carries only what the net needs for this task. It lists the call signs, so every station knows who it is and who everyone else is. It lists the frequencies and channels for each bearer, voice and Meshtastic and the TAK server connection, with enough that the operator can set the radio without guessing. It carries the PACE plan in order, so the section knows what to fall back to. It gives the schedule, the radio check times and any reporting windows. And it carries any authentication detail the task requires, the challenge-and-reply method from SIG 220, kept on the controlled card and not shouted across the harbour area. The card is controlled property: the current one is held, the superseded one is destroyed, and a card with authentication on it is treated with the same care as the keys.

   FREQUENCY AND CALL SIGN CARD            VALID: 120600Z - 130600Z JUN 26
   TASK: flood-watch, section task           CARD No. 04   (DESTROY ON REPLACE)
   ====================================================================
   CALL SIGNS                         |  NET AUTHORITY: ZERO  (the NCO)
   -----------------------------------+--------------------------------
   ZERO    net authority / control    |  ONE   section commander
   TWO     observation party          |  THREE rear party / vehicle
   (use call signs, not names or ranks, on the air)
   --------------------------------------------------------------------
   BEARERS                  FREQ / CHANNEL          NOTES
   -----------------------  ----------------------  ----------------------
   P  TAK over mobile data  tak.kaharagia.org       per-user certificate
   A  VHF voice, repeater   146.xx0 (-0.6, tone)    raises range via height
   C  VHF voice, simplex    146.xx0 simplex         radio to radio direct
   E  Meshtastic text       channel "FLOOD-04"      key issued separately
   --------------------------------------------------------------------
   SCHEDULE   radio check 0600Z and every 2 hrs;  report on change only
   AUTH       challenge/reply per SIG 220 card (held, not transmitted)
   EMCON      listening watch after 2200Z         (net authority sets)
   ====================================================================
   ONE CARD, ONE NET. Old card destroyed. New card briefed, not guessed.

Issuing the card is a briefing, not a handout. The NCO walks the section through it: who is who, which bearer is primary and what the fallbacks are, when the checks fall, the EMCON state, and how authentication works. Everyone leaves able to set their radio, recognise the other stations, and follow the PACE plan without further instruction. When the task changes or the security clock turns over, a new card is issued and the old one destroyed, so two versions of the truth never circulate on the net. The card is the single source of truth the net runs on, and keeping it current is a daily duty.

Keeping and auditing the signals log

If the card is the net's plan, the signals log is the net's memory. The log is the running written record of everything the net does, kept in time order by the net authority or a nominated log keeper, and it earns its keep three times over: as memory during the task, as evidence after it, and as the audit trail that lets the NCO find faults and prove what was and was not passed. A net without a log is a net that cannot answer the question every commander eventually asks, which is "what did we actually hear, and when?"

Each entry is brief and disciplined. It carries the date-time group, so the time is never in doubt and never local-versus-Zulu ambiguous; the stations involved, who called and who answered; and the gist of the message, enough to reconstruct what passed without writing it out word for word. Radio checks go in the log. Changes of EMCON state go in the log. A station going quiet and the actions taken go in the log. The log is written as it happens, not reconstructed from memory afterwards, because memory under stress is the least reliable record there is. A line written at the time is worth a page written later.

   SIGNALS LOG  (section flood-watch)        SHEET 1    LOG KEEPER: ZERO
   ====================================================================
   DTG          FROM  TO    GIST                                ACTION
   -----------  ----  ----  ----------------------------------  --------
   120600Z      ZERO  ALL   radio check, all stations           ALL OK
   120602Z      TWO   ZERO  in position OP1, nothing to report   logged
   120730Z      ZERO  ALL   EMCON: open working confirmed        logged
   120815Z      TWO   ZERO  water level steady, ref grid (held)  logged
   121002Z      THREE ZERO  NOTHING HEARD from TWO on check       see note
   121004Z      ZERO  TWO   radio check x2, no reply              lost stn
   121009Z      TWO   ZERO  back on net, moved for antenna height  worked in
   121200Z      ZERO  ALL   radio check, all stations            ALL OK
   ====================================================================
   ENTRIES WRITTEN AS THEY HAPPEN. DTG ON EVERY LINE. Z = Zulu = UTC.
   The log proves what passed and what did not. It is audited after the task.

Auditing the log is where it pays back most. After a task, the NCO reads the log not for drama but for pattern: where checks were missed, where a station was repeatedly hard to raise, where the net doubled, where traffic ran long, where the EMCON state slipped. Each is a fault to fix and a point for the next operator-training serial. The log also protects the section: if a question is later asked about whether a warning was passed, or when, the contemporaneous log answers it cleanly where memory and argument cannot. A signals NCO who keeps and reads the log turns every task into evidence and into training, and that is the difference between a net that merely worked today and a net that gets better.

Net authority: enforcing EMCON and net discipline

To run a net is to be its authority. The net authority, the Net Control Station, directs the net: it opens and closes the net, calls the roll, sets and enforces the EMCON state from SIG 220, controls who transmits when, and is the final word on net discipline. On a section this is usually the signals NCO or a nominated operator, and the role is one of quiet control rather than constant chatter. A well-run net is mostly silent, because the authority has trained the stations to work to procedure and to the EMCON state without being told each time.

Net discipline is the standard you enforce: clean voice procedure, the prowords and the phonetic alphabet from SIG 201, brevity that is security and not just courtesy, and obedience to the EMCON state in force. As the authority you correct faults on the net, but you correct them economically, because a long correction is itself a breach of the brevity you are enforcing. You note the persistent faults for the training session rather than lecturing on the air. You set the EMCON state plainly, "open working" or "listening watch from now", so no operator has to weigh each call alone, and you change the state by a clear instruction that goes in the log. The authority's own discipline sets the ceiling for the net: a net authority who rambles, doubles, or skips the checks will get a net that does the same.

   NET AUTHORITY: WHAT YOU OWN

   OPEN  ->  call the roll, confirm all stations, set the EMCON state,
   the net    confirm the PACE plan and the TAK picture (the comms check)

   RUN   ->  enforce procedure and brevity; control who transmits;
   the net    hold the EMCON state; correct faults SHORT; log as you go;
              run the scheduled radio checks; account for any silent station

   CLOSE ->  account for all stations, note faults for training,
   the net    finalise the log, then close the net cleanly

   THE STANDARD YOU KEEP ON THE AIR IS THE STANDARD THE SECTION KEEPS.
   A long correction breaks the brevity you are enforcing: keep it short,
   note the rest for the next operator-training serial.

Enforcing discipline fairly is part of the NCO's wider role as an instructor, which Lesson 05 develops. You correct the fault, not the person, and on the air you correct only what must be corrected to keep the net working, saving the teaching for the debrief. The aim is operators who stay calm and procedural under noise and stress, and that is built by holding the standard consistently, every task, including the quiet ones where it is tempting to let it slide. A net authority who only enforces discipline when things are tense has a section that only has discipline when things are tense, which is exactly when it is hardest to find.

Controlling devices, keys, and certificates

A section's communications are only as secure as the control of the things that grant access to them. This is where the net management of this lesson meets the comms-security discipline of SIG 220 head on, because the radios, the Meshtastic channel keys, and the TAK server certificates are not just kit, they are access. A lost radio is a lost radio. A lost or copied channel key, or a certificate left on a device that walks off, is an intruder's way onto your net or your map, quietly, without ever needing to break anything. Controlling access is the NCO's job, and it is a continuous one.

Devices are controlled by accountability: the NCO knows who holds which radio and which TAK device, signs them out and in, and treats any unaccounted set as a security question and not just a lost piece of kit. Meshtastic channel keys are the shared secret that defines a channel; whoever holds the key can join and read the channel, so keys are issued to named people for a task, never broadcast or written on the card, and are changed when a person or device leaves the section or when there is any doubt the key has stayed inside the section. The same logic, harder, applies to TAK certificates: each is issued to a named person to connect their device to tak.kaharagia.org, so a certificate is tied to a person, controlled like a key, and revoked the moment a device is lost or a person leaves. Revoking a certificate on the server cleanly removes that device from the map; that ability is precisely why certificates beat shared passwords, and the NCO must know it is to be used.

   ACCESS CONTROL: THE THREE THINGS THAT LET A STRANGER IN

   ITEM                  WHAT IT GRANTS          NCO'S CONTROL
   -------------------   ---------------------   -------------------------
   RADIO / TAK DEVICE    use of the net / map    sign out + in; account
                                                  for every set; loss = a
                                                  SECURITY question
   MESHTASTIC            join + read the          issue to named people;
   CHANNEL KEY           channel                  never on the card; CHANGE
                                                  the key when anyone leaves
                                                  or doubt arises
   TAK SERVER            connect a device to      issued per named person;
   CERTIFICATE           tak.kaharagia.org map    REVOKE on loss or a person
                                                  leaving (server-side)
   -------------------------------------------------------------------
   THE TEST: if this item walked out the gate tonight, could a stranger
   read or join our net or our map? If yes, control it like ammunition.

The discipline here is the same one SIG 220 taught for emissions, applied to access: assume the worst case and deny it in advance. You do not wait for proof a key has leaked before changing it; you change it when the risk appears, because the cost of a fresh key is minutes and the cost of an open channel is the whole net. You do not let a TAK certificate live on a personal phone that leaves the section's control without a plan to revoke it. Treating keys and certificates as controlled property, issued to named people and revoked without hesitation when things change, is what stops the section's own convenience from becoming its own breach.

Accountability for kit and batteries

The most reliable way to lose communications is not a clever adversary; it is a flat battery. A radio with no power is no radio, a TAK device that dies mid-task takes a station off the map, and a Meshtastic node with a dead cell stops relaying for everyone downstream of it. Accountability for kit and batteries is therefore not a quartermaster's afterthought but a core part of running the net, and it is the NCO who is responsible for it. The plan and the procedure are worthless if a third of the section's sets go dark at the worst moment.

Accountability means two things held together: knowing where every set is, and knowing that every set will work. The first comes from signing kit out and in and keeping that record current, so a missing radio is noticed at once and treated, as above, as a security question. The second comes from battery discipline: every set charged before the task, a spare battery or power source carried, batteries checked at the radio-check points so a failing one is caught before it dies, and a simple rule that you report a low battery early, not when the set has already gone silent. The communications check before any task includes this: a radio check on every link is also a check that every set has power to make the check at all.

   BATTERY AND KIT STATE  (checked at every radio-check point)

   CALL SIGN   SET        BATTERY      SPARE?   NOTES
   ---------   --------   ----------   ------   --------------------------
   ZERO        VHF + TAK  full / full   yes     control, on mains backup
   ONE         VHF        full          yes
   TWO         VHF + mesh  3/4 / full   yes     mesh node relaying for OP1
   THREE       VHF        1/2           NO  <-- swap in spare BEFORE task
   ---------------------------------------------------------------------
   RULE: charged before the task; spare carried; report low EARLY, not
   when silent. A flat radio is no radio. Check power AT every radio check.

Battery accountability scales the way the net does: each operator manages their own set and spare, and the NCO manages the section's state, knowing at a glance which station is strong, which is getting low, and where the spares are. On a longer task the NCO plans the power the way they plan the comms, charging in rotation and siting a mains or vehicle charge point where it can be reached. Doubling power on a radio buys only a little range and burns the battery faster, which is one more reason Lesson 03 matters: a better, higher antenna gets the signal through on less power and saves the very battery the section's communications depend on. The NCO who treats batteries as seriously as frequencies is the one whose net is still up when it counts.

Handling problems on the net calmly

Every net has problems. The mark of a signals NCO is not a net that never goes wrong but a net authority who puts it right calmly, by drill, without the rising voice that turns one fault into a flap. Four problems come up often enough that you handle each by a known response rather than by improvisation: doubling, a lost station, a suspected intruder, and a dead link. Knowing the drill for each means you act instead of dithering, and your calm sets the tone for the whole net, because a section takes its temperature from the control station.

Doubling is two stations transmitting at once, so you hear a garble and get neither message. The drill is simple and unhurried: you announce that stations doubled and direct them to transmit in turn, calling one station to send, then the other. You do not let it spiral into both stations apologising over each other, which is just more doubling. As net authority you impose order by nominating who speaks, and the fault clears in seconds.

A lost station is one that has gone quiet, whether through a flat battery, a bad position, a fault, or moving out of range. The drill blends net action and the "no comms" troubleshooting you teach your operators: you call the station, you call it again, you ask another station to relay, and meanwhile the lost station itself should be working its own checklist, power and battery, volume and squelch, the right frequency or channel, the antenna and its connection, and its position, moving or getting height or trying a relay before declaring the link dead. You log the loss and the actions, you fall down the PACE plan to reach the station by another bearer, and you do not assume the worst until the drill is exhausted. Most lost stations are a flat battery or a body between the antenna and the line of sight, fixed in minutes.

A suspected intruder is a station you cannot confirm as your own, possibly an outsider on your net or an attempt at deception. This is where the authentication discipline of SIG 220 earns its place: you challenge the station and require the correct reply, you do not pass anything operational to an unauthenticated station, and you treat a failed or absent reply as a genuine intruder until proven otherwise. You warn your own stations, you tighten to authenticated traffic only, and you log it for the security review. The calm here is important, because an intruder may be trying to provoke exactly the confused, revealing chatter that an authentication challenge shuts down.

A dead link is the bearer itself failing, the repeater down, the mobile data gone, the whole means unusable rather than one station. This is precisely what the PACE plan exists for. You do not stare at the dead bearer; you call the move down the plan, "all stations, go to Alternate", and the net re-forms on the next means while you work out whether the primary can be recovered. The communications check you ran before the task already proved each fallback works, so the move is a known drill and not a leap into the unknown.

   PROBLEM ON THE NET -> CALM, BY DRILL

   DOUBLING        ->  "stations doubled, transmit in turn":
   (garble, two)        nominate ONE to send, then the other. Clears in secs.

   LOST STATION    ->  call x2 -> ask a RELAY -> (station works its own
   (gone quiet)         no-comms check: power, volume/squelch, freq/channel,
                        antenna, POSITION) -> fall down PACE -> log.

   SUSPECTED       ->  CHALLENGE + require correct reply (SIG 220 auth).
   INTRUDER             Pass nothing operational unauthenticated. Tighten,
   (unconfirmed stn)    warn own stations, log for security review.

   DEAD LINK       ->  "all stations, go to Alternate": move DOWN the
   (whole bearer)       PACE plan. The pre-task comms check already proved
                        each fallback works. Recover the primary separately.

   YOUR CALM IS THE NET'S CALM. Act by drill; do not improvise a flap.
   Everything goes in the LOG. Persistent faults go to the next training serial.

Behind all four drills is one principle: the authority stays calm and acts by a known response, and the net follows. A flustered control station produces a flustered net, where stations talk over each other, abandon procedure, and turn a recoverable fault into a lost task. A calm control station that names the problem, applies the drill, and logs it produces a section that trusts the net and keeps working. That calm is not a trait you either have or lack; it is the product of knowing the drills cold and having rehearsed them under noise until the response comes before the worry does. That rehearsal is exactly what the airsoft milsim serials and the in-person assessment build, and it is why this lesson is the knowledge layer and not the whole of the skill.

In Practice: A Net Authority Holds a Section Together

A section under Corporal Imani is tasked overnight to watch a rising river and warn the community below if the water threatens the crossing. Before anyone moves, the Corporal does the unglamorous work this lesson is about. She issues the frequency and call sign card: ZERO is control and net authority, TWO is the observation party at the crossing, THREE is the rear party with the vehicle and the mains charge point. The PACE plan is briefed in order, TAK over mobile data as primary, VHF via the repeater as alternate, VHF simplex as contingency, Meshtastic text as emergency. She runs the communications check before moving: a radio check on every link, a confirmation that the PACE plan is understood, and a glance at the TAK picture to confirm everyone shows on the map. She checks the battery state and sends THREE to swap a half-charged set for a fresh one before it leaves, because a flat radio is no radio. The EMCON state is set: open working until 2200Z, then listening watch.

The night tests her, and each problem meets a drill instead of a flap. At one check TWO and THREE key together and she hears a garble; she calls "stations doubled, transmit in turn", takes TWO first and THREE second, and the net clears in seconds, logged with a DTG. Later TWO misses a check entirely. She calls twice, gets nothing, and asks THREE to relay while TWO, working the no-comms drill she trained into them, realises a riverbank has dropped into the antenna's line of sight, moves a few metres for height, and comes back on the net. She logs the loss and the recovery rather than assuming the worst. Near midnight an unfamiliar station answers a call as though it were part of the section; she challenges it, gets no correct reply, passes it nothing operational, warns her own stations to authenticated traffic only, and logs it for the security review, her voice never rising. When the mobile data drops out around the high water and the TAK picture freezes, she calls "all stations, go to Alternate", and the net re-forms on VHF through the repeater, a move the pre-task check had already proved.

When the water rises near dawn, TWO passes a single short report, ZERO reads back the level and the reference, and the warning goes to the community in time. After the task the Corporal audits the log: where the doubling happened, why TWO was hard to raise, how long the intruder challenge took. Each becomes a point for the next operator-training serial. She also revokes the TAK certificate on the spare device THREE borrowed and returned, because access that is no longer needed is access that should not exist. The river was watched, the community warned, the net held, and the net got a little better, which is exactly what a signals NCO is for.

Check Your Understanding

  1. Describe the frequency and call sign card and the signals log, saying what each carries and why each matters. Then explain why every log entry takes a date-time group with a Zulu zone letter, and what the NCO is looking for when auditing a log after a task.
  2. As net authority, you control access to three things that can let an outsider onto the section's net or map: the devices, the Meshtastic channel keys, and the TAK server certificates. Explain how you control each, why a lost key or certificate is a security problem and not just a lost item, and when you would change a channel key or revoke a certificate without waiting for proof of a leak.
  3. Give the calm, drilled response to each of the four common net problems: doubling, a lost station, a suspected intruder, and a dead link. For the lost station, include the operator's own "no comms" checklist; for the suspected intruder, explain how the SIG 220 authentication discipline applies; and for the dead link, explain how the PACE plan and the pre-task communications check make the move a known drill rather than a leap.

Reflection (write a short paragraph): A net authority's calm is the net's calm, and that calm comes from knowing the drills cold rather than from temperament. Think about the four problems in this lesson, doubling, a lost station, a suspected intruder, a dead link, and about the quieter daily disciplines of the card, the log, the keys, and the batteries that prevent half of those problems before they start. Write, in your own words, which of these you would find hardest to hold under noise and stress, why, and how you would build the habit so that the right response comes before the worry does.

Summary

  • Running the net is the daily work of keeping a communications plan alive: the frequency and call sign card, the signals log, net discipline, access control, and battery accountability. A plan that is never maintained decays within a day, and the NCO is the person who keeps it alive.
  • The frequency and call sign card turns the comms estimate into one small, controlled document everyone holds: call signs, frequencies and channels, the PACE plan, schedules, and authentication detail. It is briefed, not just handed out; the current card is held and the superseded one destroyed, so there is one source of truth on the net.
  • The signals log is the net's memory, evidence, and audit trail. Each entry carries a date-time group (Z = Zulu = UTC), the stations, and the gist, written as it happens. The NCO audits the log after a task to find faults and feed the next training serial.
  • As net authority (the Net Control Station) the NCO opens and closes the net, sets and enforces the EMCON state, controls who transmits when, and is the final word on net discipline. The standard the authority keeps on the air is the standard the section keeps; corrections on the net are kept short, with the teaching saved for the debrief.
  • Access control ties net management to the comms-security discipline of SIG 220. Radios and TAK devices are signed out and in; Meshtastic channel keys are issued to named people, never put on the card, and changed when anyone leaves or doubt arises; TAK certificates at tak.kaharagia.org are issued per named person and revoked on loss or departure. If an item could let a stranger read or join the net or the map, it is controlled like ammunition.
  • Accountability for kit and batteries is core to running the net, not an afterthought. Every set is charged before the task, a spare is carried, batteries are checked at the radio-check points, and a low battery is reported early. A flat radio is no radio, and a better, higher antenna (Lesson 03) gets the signal through on less power and saves the battery.
  • Net problems are handled calmly, by drill: doubling (transmit in turn), a lost station (call, relay, the no-comms checklist, fall down PACE), a suspected intruder (challenge and authenticate per SIG 220, pass nothing operational unauthenticated), and a dead link (move down the PACE plan, a known drill because the pre-task communications check proved each fallback). The authority's calm is the net's calm.
  • This lesson builds on SIG 201 · Radio Communications and Message Handling (prowords, the phonetic alphabet, the DTG, the PACE plan) and SIG 220 · Communications Security and Digital Discipline (EMCON states, authentication, device and key control). It connects forward to Lesson 05 of this course on training and assessing operators, and supports PME 210 · Basic Staff Duties and Written Orders (the signals paragraph of orders), HCR 220 · Emergency Preparedness and Civil Resilience, FLD 230 · Patrolling and Tactical Movement, and FLD 201 · Navigation and Fieldcraft. These skills are mastered by rehearsal and certified in person, including on airsoft milsim exercises.

Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia

Lesson 4 · Knowledge Check

Question 1 of 3

What is the frequency and call sign card?