Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Making SET and Field Day count: how do you turn drills into real disaster-comms practice?

ci_cover.jpg

Most of us agree that exercises are the only safe place to find out what breaks. The harder question is whether a drill produces anything we can use afterward. Here are some thoughts on scenario design, and I'd like to hear how other groups handle it.

Start with the hazard, not the radios. Each hazard stresses a different part of the comms plan. A hurricane is a long-duration event with warning time. That makes it a test of shift rotation, fuel and battery logistics, check-in routines for members in the affected area, and what happens when the net control station loses power on day three. A wildfire moves quickly and changes geometry: evacuation zones shift, repeaters and their links can be lost, and mobile and portable operation matters more than a fixed shack. Floods tend to produce gauge and road-closure reports, which suit short, structured messages. An earthquake raises the welfare-traffic problem and the question of which infrastructure still works. A tornado leaves almost no lead time, so the exercise question is often how fast you can get from a normal evening to an activated net. A grid failure is the slow burn. Cell sites and repeater sites run on batteries and generators with finite endurance, so the scenario should include things degrading over time, not one dramatic failure.

Use injects, not a fixed script. A scenario that says "Shelter A requests 40 cots" is fine for message handling. It teaches more when the exercise controller also injects "the primary repeater is down" or "your net control operator has to leave," and watches whether the group moves to simplex, a backup frequency, or an alternate NCS without confusion.

Treat the Simulated Emergency Test as a rehearsal of the whole chain. SET is an ARRL exercise that sections and local groups adapt to their own needs. It's most useful when it includes a real served-agency angle, such as a hospital, emergency management office, or shelter operator, and when the messages are originated by people who aren't hams, or at least on the agency's own forms. Handling traffic you wrote yourself in a format you like only tests part of the chain.

Field Day is practice, but only if you choose to make it so. It builds the basics: setting up antennas quickly, running on generator or battery power, working with unfamiliar gear, and operating in bad conditions. It is also easy to run purely as a contest. Groups that want emergency-comms value from it often add a separate message-handling table, practice formal radiogram format, test a digital path such as Winlink if their plan uses it, and rehearse a short check-in net. The rules include bonus categories related to message handling, so check the current rules rather than relying on memory.

Message handling is where the details bite. A standard radiogram has a preamble (message number, precedence, handling instructions if any, station of origin, check, place of origin, time and date), then address, text, and signature. The check is the word count of the text, so the receiving station can confirm nothing was dropped. Precedences run Routine, Welfare, Priority and Emergency, and a surprising amount of practice is just not using Priority for everything. Many served agencies work with ICS-213 General Message forms. Deciding up front how a 213 gets transcribed to radiogram format and back, and who is allowed to sign, saves a lot of confusion mid-event.

Net scripts should be short enough to read under stress. A good script usually covers the opening statement and purpose of the net, how to check in (emergency or priority traffic first, then others), how to request relay, and how the net closes or hands off. Fill-in-the-blank fields for date, frequency, and NCS callsign help. If the script takes a full minute to read before anyone can speak, expect people to start improvising.

After-action reports need owners. A useful AAR is more than a recap. The common structure is what was planned, what happened, what worked, what didn't, and corrective actions. Each corrective action should name a person and a rough deadline, or it tends to turn into a list of good intentions that is repeated the next year.

Questions for the group: What do you inject into your scenarios to force a plan change? How do you structure working with served agencies so you're supporting their communication needs rather than substituting your own procedures? And what is the one item that shows up in every after-action report but never seems to get fixed?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On served agencies, the main thing I'd stress is that the exercise should be built around their information needs, not ours. Before the drill, ask what they actually need to send and receive in an outage. It might be shelter census, supply requests, status of a facility, or a request for a runner. Then build message injects from that list. If their normal form is an ICS-213, have the exercise start there. The agency staff write or approve the message, the operator transmits it as written, and the receiving end delivers it on a matching form. You find out quickly whether the text survives the trip without someone "cleaning it up."

It also helps to settle the unglamorous questions in advance: who at the agency may authorize sending a message, who the operator reports to at that site, what the operator should and shouldn't discuss with the public or media, and what ID or credentials the agency expects. Those are the places where a drill with a friendly contact can look smooth and a real event with unfamiliar staff won't. A short written agreement or at least a written understanding of roles is worth having, and your local EMA may have its own requirements for volunteers.

One thing I'd add to your list of questions: does the agency know when we are not the right tool? If a phone call or a data link will do the job, it's fine to say so. Amateur radio earns its place by being the backup that works, not by insisting on being the primary.

  • Moderators

For injects, a few that tend to produce useful friction: the NCS has to hand off mid-exercise, a relay station can hear the net but can't be heard, a message arrives with a check that doesn't match the word count, and a served-agency contact asks for something nobody has a form for. None of these needs to be dramatic. They test whether people fall back on the plan or on habit.

On the after-action side, I'd keep the report short enough that people read it. A format that works is a page or two with four headings: what we set out to test, what we observed, what to sustain, and what to fix, with names on the fixes. It also helps to separate observations from opinions. "Three stations couldn't hear the NCS on the primary frequency" is something you can act on. "Communications were rough" isn't. If you have a few people acting as evaluators who aren't also operating, they'll see timing gaps, unclear handoffs, and misheard calls that the operators themselves are too busy to note.

As for what never gets fixed, power planning and message-form familiarity seem like safe bets in many groups. Both are tedious, and both are easy to put off until the next drill. If one corrective action gets an owner and a date after each exercise, that is probably better than a long list nobody tracks.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.