Troubleshooting and When Communications Fail

Lesson Overview

Communications fail. However good the operator, however sound the set, sooner or later a link will go down, a message will not get through, the net will fall silent, and the test of an operator is not whether this happens but what they do when it does. This lesson is about exactly that: the calm, systematic finding and fixing of a communications fault, and the disciplined fallback for when the fault cannot be fixed in time. It brings together the set of Lesson 06 and the propagation of Lesson 07 into the operator's most practical skill, the recovery of a failed link, and it adds the resilience that keeps a team functioning even when the radio cannot be recovered at all: the planned fallback through other means, and the lost-communications drill that lets a team carry on without panic.

Two ideas govern the lesson. The first is that most communications failures are simple and the operator's to fix, so a failed link is usually not a crisis but a fault to be worked, calmly and in order, from the obvious to the obscure. The flat battery, the wrong channel, the loose antenna, the squelch set too tight, the far station not listening, these account for most "no comms", and an operator who checks them methodically fixes most failures themselves, on the spot. The second is that a team that has planned and drilled for lost communications does not depend on the radio working, because it has a fallback ready, a pre-arranged plan to drop to other means or to act on the last orders, so that the radio failing is an inconvenience absorbed rather than a disaster. Together these turn communications failure from a thing that defeats a team into a thing a trained team handles in its stride.

This is the knowledge layer. It teaches you how to troubleshoot a failed link systematically, how to use the radio check to isolate a fault, the PACE plan that gives a team a fallback, and the lost-communications drill, so that you understand how communications are recovered or worked around. The real skill of fault-finding on the actual sets, and the drilled fallback as a team, is built hands-on and on exercise under qualified supervision and certified in person. Read this to know how failure is handled; the calm hands and the drilled team are built in person.

By the end you will be able to troubleshoot a failed link systematically from the obvious to the obscure, use the radio check to isolate whether the problem is you, the far station, or the path, apply a PACE plan to fall back through other means, carry out a lost-communications drill, and stay calm and methodical when the net goes down.

Key Terms

• Troubleshooting: the systematic finding and fixing of a fault, worked from the simplest and commonest causes to the more complex.
• Common fault: one of the handful of simple, frequent causes of failed communications (flat battery, wrong channel, loose antenna, squelch, far station not listening) that account for most "no comms".
• Radio check: a transmission by procedure to confirm a station is heard and how well, used here as the operator's chief diagnostic tool.
• Readability: how clearly a station is heard, reported on a simple scale, used to judge the quality of a link and isolate a fault.
• Isolating the fault: narrowing down whether a failure is in your set, the far station, or the path between, by changing one thing at a time.
• PACE plan: a planned order of communications means, Primary, Alternate, Contingency, Emergency, so that when one fails the team drops to the next without confusion.
• Lost-communications drill: the pre-arranged actions a team takes when communications fail entirely, including acting on the last orders and meeting at a set time and place.
• Last orders stand: the principle that, with no communications, a team continues on the most recent orders it received, so that silence does not mean paralysis.
• Unserviceable: the state of a set that is faulty and cannot be relied upon, which is reported and replaced or repaired rather than bodged.
• Calm and method: the operator's disposition in a failure, working the fault in order rather than panicking, which is what actually recovers the link.

Most failures are simple: troubleshoot in order

The first thing to know about communications failure is reassuring: most of it is simple, caused by one of a handful of common faults, and fixable by the operator on the spot. The temptation when the net goes silent is to assume something serious and complex, or to panic, or to give up; the discipline is to do the opposite, to assume the fault is probably simple and to work through the common causes methodically, from the obvious to the obscure. An operator who troubleshoots in order fixes most failures in seconds, because most failures are, in truth, small and self-inflicted.

The method is to check the simple and common things first, because they are both the most likely causes and the quickest to check, so working in this order finds most faults fast. The operator's mental checklist runs roughly: Is the set on, and the battery good, not flat or loose? Is it on the right channel for the net? Are the volume and squelch set right, the volume up, the squelch not so tight it is cutting off the signal? Is the antenna connected, firm, and undamaged? Am I sited to get through, high and clear enough, as Lesson 07 taught, or am I in a dead spot? And is the far station actually on, listening, and able to hear me, or is the silence theirs and not mine? Only when all of these are checked and sound does the operator suspect a genuine equipment fault needing a technician. The great majority of "no comms" is resolved somewhere in that list, which is why running it, calmly and in order, is the operator's first and most valuable troubleshooting skill.

The reason for working simplest-first is efficiency and calm: checking the battery and channel takes seconds and fixes most problems, so doing it first means the operator is usually back on the net before they have even begun to worry, and the methodical order itself steadies the mind, replacing panic with a task. The operator who instead leaps to the worst conclusion, fiddles randomly, or gives up, often has a flat battery or a wrong channel they never checked.

   TROUBLESHOOTING: SIMPLE AND COMMON FIRST

   1. POWER        set on? battery good (not flat/loose)?
   2. CHANNEL      on the RIGHT channel for the net?
   3. VOLUME/      volume up? squelch not so tight it cuts the signal?
      SQUELCH
   4. ANTENNA      connected, firm, undamaged?
   5. SITING       high and clear enough? in a dead spot? (Lesson 07)
   6. FAR STATION  are THEY on, listening, able to hear me?
   ----------------------------------------------------------------
   only THEN suspect a real equipment fault for a technician.

   Most "no comms" is fixed somewhere in 1-6, in seconds. Work it in
   ORDER and CALMLY: the order finds the fault fast and steadies you.

Isolating the fault with the radio check

The operator's chief diagnostic tool is the radio check, the procedure transmission that asks "do you hear me, and how well?", because it tells the operator not just whether a link works but where it is failing. By asking the far station, or another station, "how do you read me?", and reporting readability in return, the operator gathers the evidence to isolate the fault: to work out whether the problem is in their own set, in the far station, or in the path between, which points to different fixes.

The logic of isolation is to change one thing at a time and see what happens. If no one at all answers a radio check, the fault is likely the operator's own, the set, the channel, the antenna, so they work their own checklist. If one station hears them but another does not, the operator's set is probably fine and the problem is the second station or the path to it, so the effort moves there, perhaps to a relay (Lesson 07). If a station hears them faintly or broken, the link exists but the path is poor, so the operator improves their siting, raises the antenna, or moves, and checks again to see if readability improves. Each check, changing one variable, narrows the problem down, which is far quicker than changing several things at once and never knowing which mattered. The radio check turns troubleshooting from guesswork into a guided search: ask, listen to the readability, change one thing, ask again, until the fault is found.

This is also why the radio check at setting-up (Lesson 06) is so valuable: it establishes that the link worked before it was needed, so that if it later fails, the operator knows something changed, and recent changes, a move into worse ground, a battery run down, a knocked antenna, are the first suspects. An operator who knows their link was good an hour ago troubleshoots a fresh failure far faster than one who never confirmed it worked in the first place.

When you cannot fix it: the PACE plan

Sometimes a link cannot be recovered in the time available: the set is genuinely broken, the far station is down, the ground will not allow it, or there is simply no time to fix it. For this, the resilient answer is not a better set but a plan made in advance for communications to fail, and the standard form of that plan is PACE: a planned order of communications means, Primary, Alternate, Contingency, and Emergency, so that when one means fails the team drops to the next in a known, drilled sequence rather than falling into confusion.

The idea is that a team does not rely on a single means of communicating, which is a single point of failure, but arranges several in order of preference: the Primary means it normally uses, an Alternate to switch to if the primary fails, a Contingency further fallback, and an Emergency means of last resort. For a section these might run from the digital net or main radio, down through a simpler or different radio, down to plain voice or whistle and field signals, down to a pre-arranged rendezvous; the specific means matter less than that there is an ordered, briefed, drilled sequence. When the primary fails, the team moves to the alternate; if that fails, to the contingency; and so on, each move already decided and practised, so the failure of any one means is a smooth step down rather than a crisis. This is the resilience thinking that runs through the whole speciality, and it is why the operator's lawful tools of Lesson 05 and the digital tools of Lesson 10 are arranged into a PACE plan: not as competitors, but as layers that fall back on one another.

The crucial point is that a PACE plan is only worth anything if it is briefed and drilled in advance, because the moment a means fails is not the moment to invent the fallback. A plan that lives only on paper, or only in the leader's head, fails when the screen freezes and no one knows the next step; a plan that every member can recite and has practised means the whole team drops to the next level in the same breath, calmly and together. The operator's part is to know the PACE plan for their net cold, and to make the fallback automatic, so that a means failing changes the how of communicating without interrupting the that.

   THE PACE PLAN  (don't rely on one means)

   PRIMARY        the means normally used        (e.g. digital net / main radio)
        | fails
   ALTERNATE      switch to this                 (e.g. a simpler/different radio)
        | fails
   CONTINGENCY    fall back to this              (e.g. plain voice / whistle + signals)
        | fails
   EMERGENCY      last resort                    (e.g. pre-arranged rendezvous + time)

   Each move DECIDED, BRIEFED, and DRILLED in advance, so the team drops
   a level calmly and TOGETHER. A PACE plan only on paper is no plan.

The lost-communications drill

When communications fail entirely and even the fallbacks are exhausted, or while they are being re-established, a trained team is not paralysed, because it has a lost-communications drill: a set of pre-arranged actions for exactly this, so that silence produces orderly action rather than confusion. The drill rests on two ideas.

The first is that the last orders stand. With no communications, a team continues to act on the most recent orders it received, carrying on the task as briefed, because the alternative, stopping and waiting for instructions that cannot come, is paralysis. This is why good orders always include what to do if communications are lost, so that a unit cut off from the net still knows the commander's intent and can act on it. Silence is not a new order; it is the absence of one, and the team acts on the last clear direction it has.

The second is the pre-arranged rendezvous and timings: a plan, briefed beforehand, that if communications are lost the team will meet at a set place at a set time, or take some other agreed action, so that members separated and unable to talk can still come back together in good order. This, the emergency level of many a PACE plan, is the ultimate fallback, a way of regaining control that needs no working radio at all, only that everyone knew the plan in advance. A team that has briefed its lost-comms rendezvous can lose every radio and still reassemble, on time, at the right place, because the plan was in their heads, not on the dead net.

Both depend, again, entirely on prior briefing and drill: the lost-communications actions, like the PACE plan, are decided and rehearsed before the task, because they are needed precisely when it is too late to arrange them. The operator and the team that have drilled lost comms treat a total communications failure as a contingency they have a plan for, not a catastrophe, which is the whole aim of this part of the lesson.

Faults, reporting, and staying calm

Two final disciplines complete the operator's handling of failure. The first concerns genuine faults: when troubleshooting reveals that a set really is broken, unserviceable, the operator reports it and has it replaced or repaired rather than bodging it or struggling on with a set that half-works, because a set quietly limping is a link that will fail again at the worst moment, and an unreported fault is a hazard to the whole net. Reporting unserviceable kit honestly is part of the accountability for equipment of Lesson 06, and it keeps the net's reliability real rather than pretended.

The second, and the thread through the whole lesson, is calm and method. The operator's enemy in a communications failure is not usually the fault, which is generally simple, but panic, which makes the operator fiddle randomly, skip the checklist, miss the obvious, and spread alarm. The disciplined operator, when the net goes down, does the opposite: stays calm, works the troubleshooting checklist in order, uses the radio check to isolate, falls back through the PACE plan if the link cannot be recovered, and reverts to the lost-comms drill if all else fails, all without fuss. Their calm is itself functional, because it keeps them thinking clearly and reassures the team, where panic would defeat both. The message of this lesson is finally that communications failure is normal, mostly simple, and provided for: the operator who knows this, and meets a dead net with calm method rather than alarm, recovers most links quickly and handles the rest in stride, which is exactly what carrying the net for a team requires.

In Practice: The Net Goes Down

A section signaller of the Royal Kaharagian Army is carrying the net when, at a critical moment, it goes silent: he can raise no one. A weak operator panics, jabs at the set, assumes disaster, and reports a crisis. The College's signaller meets it with calm and method, exactly as this lesson teaches.

He works the troubleshooting checklist in order, simplest first: the set is on and the battery good; he checks the channel and finds, in fact, it is correct; volume and squelch are fine; the antenna is firm; but he is in a dead spot, low behind cover, so he moves to better ground as Lesson 07 taught, and tries again. Still patchy, so he uses the radio check to isolate the fault: one station reads him faintly, another not at all, which tells him his own set is working and the problem is the path and the far station, not his radio. He improves his siting once more and raises the antenna, and the readability comes up. Most of his trouble is solved in under a minute, calmly, because he worked the fault in order instead of panicking.

For the station he still cannot reach, the link cannot be recovered in time, so he falls back through the PACE plan his section briefed and drilled: from the primary net to the alternate means, and, when that too is thin, the section drops without fuss to the contingency, clean voice on the section net, every member knowing the move because it was rehearsed. Had everything failed, the lost-communications drill was ready: the section would have acted on its last orders and met at the pre-arranged rendezvous at the set time, regaining control with no working radio at all. He notes the one set that proved genuinely unserviceable to be reported and replaced, not bodged. Nothing was lost and no one was cut off, not because nothing failed, things failed, but because the failures were met with calm troubleshooting, a drilled fallback, and a lost-comms plan, which is the whole of handling communications failure well.

Check Your Understanding

1. Explain why "most communications failures are simple and the operator's to fix," and set out the troubleshooting checklist in order (power, channel, volume/squelch, antenna, siting, far station). Why is working simplest-first both efficient and calming?
2. Explain how the radio check and readability are used to isolate a fault, the principle of changing one thing at a time, and how the answers point to whether the problem is your set, the far station, or the path. Why is a radio check at setting-up so valuable later?
3. Describe the PACE plan and why a team should not rely on a single means of communicating, and the lost-communications drill (the last orders stand; the pre-arranged rendezvous). Why do both depend entirely on prior briefing and drill?

Reflection (write a short paragraph): This lesson argues that the operator's real enemy in a failure is usually not the fault, which is generally simple, but panic. Think about a time something you depended on failed suddenly and you reacted with alarm rather than method: did you miss an obvious, simple cause because you panicked? Why does working a calm checklist, simplest-first, both find the fault faster and steady the mind? Then picture carrying the net for your section when it goes dead at a vital moment: what would you check, in order, and what fallback would you want to have briefed and drilled beforehand, so that the failure was a contingency you had planned for rather than a crisis?

Summary

• Communications will fail, and the operator's job is to recover them or work around them. Most failures are simple and the operator's to fix, so a dead net is usually a fault to be worked calmly, not a crisis.
• Troubleshoot in order, simplest and commonest first: power and battery, right channel, volume and squelch, antenna, siting (dead spot?), and whether the far station is on and listening, before suspecting a real equipment fault. The methodical order finds most faults in seconds and steadies the mind.
• Use the radio check and readability to isolate the fault by changing one thing at a time: no one answers points to your own set; one hears you and another does not points to the far station or path; a faint or broken read points to the path, so improve siting and check again. A setting-up radio check makes a later failure faster to diagnose.
• When a link cannot be recovered, fall back through a PACE plan (Primary, Alternate, Contingency, Emergency): an ordered, briefed, drilled sequence of means, so the team drops a level calmly and together rather than relying on a single point of failure.
• When communications fail entirely, the lost-communications drill applies: the last orders stand (act on the most recent direction; silence is not paralysis) and the pre-arranged rendezvous and timings let a team reassemble with no working radio. Report a genuinely unserviceable set rather than bodging it, and meet every failure with calm and method, not panic.
• This is the knowledge layer; fault-finding on the real sets and the drilled team fallback are built hands-on and on exercise under qualified supervision and certified in person. This lesson brings together the set of Lesson 06 and the propagation of Lesson 07, applies the PACE thinking of Lessons 05 and 10, and uses the voice procedure of Lesson 02.

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