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: Turning Exercises into Real Disaster Comms Practice

ci_cover.jpg

Most clubs and ARES/emergency communications groups run some version of the Simulated Emergency Test and Field Day every year. The question is whether those events actually change how the group performs when something real happens. It is easy to treat both as a checkbox: make contacts, pass a few practice messages, take a photo, go home. Here are some ideas for getting more out of them, and I'd like to hear what others have changed.

Start with Field Day. It is a contest-style event, so it rewards contact count, not disaster skills. But it still gives you a lot of practice if you add a few deliberate goals. Set up fast, under a time limit, with whatever the group would realistically carry. Run on generator, battery or solar for at least part of it. Rotate people into positions they don't normally hold. Use it to test antennas you'd need when the tower is down, and see who can actually build, tune and troubleshoot them. Put a message-handling table in the plan, even a small one, so someone is originating, relaying and delivering formal traffic while the rest are working stations. The "free" bonus points for a formal NTS-style message are an easy hook.

For SET, the biggest difference comes from the scenario. Instead of a generic "disaster happens, check in," try a specific one tied to local hazards: a river gauge climbing and two bridges closing, a wildfire forcing evacuation of a ridge where a repeater site sits, a hurricane landfall followed by a long period of no commercial power, an earthquake that jams the phone network with welfare inquiries, a tornado path that cuts a hospital's normal connectivity, or a multi-day grid failure where fuel and battery logistics matter more than the initial response. Each one stresses something different. Floods and fires stress mobility and changing locations. Hurricanes and grid failures stress endurance, shift changes and power. Earthquakes and tornadoes stress rapid damage reporting and the flood of welfare traffic.

Then there are the net scripts. A good script is short enough that a net control operator can follow it under stress and clear about priorities: emergency or priority traffic first, then agency-requested stations, then routine check-ins. Include the basics: purpose of the net, how to check in, how to identify (legal call sign at the required intervals, with a tactical call sign as the working label), and how to break in with urgent traffic. Does your script work if the net control operator is replaced halfway through? Does it work on a repeater, on simplex, on HF and on a digital mode? Those are different nets with different habits.

On message handling, practice the difference between a radiogram and what your served agency actually uses. Many agencies expect something like an ICS-213 general message or their own form. Radiogram format, with its precedence, handling instructions, station of origin, check, place of origin, time and date, address, text and signature, is still excellent for formal relay and for making sure nothing is garbled. But the useful skill is moving content accurately from one format to another without changing the meaning.

Finally, the after-action report. What does yours look like, and does anyone read it a month later? Please share templates, scenario ideas and the things you wish you had tested sooner.

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing that makes a big difference is building the exercise around injects instead of just "traffic." An inject is a timed event handed to a participant: a shelter reports a generator failure, a road is closed, a served-agency contact asks for a status update, the primary repeater goes "down" and everyone must move to a backup. It forces decisions. Without injects, a net can look busy while nothing is being tested.

For message handling specifically, vary the difficulty on purpose. Some messages should be short and clean. Some should have numbers, street names or medical terms where mistakes matter. Practice phonetics for those parts, read-backs for critical items, and the habit of saying "I'll repeat the numbers" without being asked. Also check the word count (the "check") on formal messages, because it catches dropped words on the receiving end.

Another useful twist: make some messages undeliverable. The addressee has moved, the shelter has closed, the phone number is wrong. The group then has to practice what to do with a message that can't be delivered: log it, notify the originator, and decide whether to retry. Real traffic does not always end neatly, and a message log that shows what happened to each message makes the after-action review much more honest.

One more point on scripts: keep tactical call signs tied to a location or function ("Shelter North," "County EOC") rather than a person, so operators can swap without confusing the net. And still identify with your FCC call sign as required. The tactical call does not replace that.

  • Administrators

The served-agency side is where I'd push hardest, because a technically perfect exercise can still miss what the agency needs. Before writing the scenario, ask the agency contact what they would actually want from volunteer radio operators: status from shelters, damage reports, resource requests, backup links between facilities, or something else. Then ask what format they want it in, who is authorized to ask for it, and who they want it delivered to. Agencies often have clear preferences, and sometimes they don't use amateur radio at all until other systems fail. Better to learn that in a planning meeting than in the middle of an incident.

It also helps to invite agency staff to write some of the injects or observe the exercise. They can tell you quickly whether a message is useful or whether it's too long, too vague or missing a location. Staying in a defined role matters too. Amateur operators carry messages and provide communications; the agency decides what to do with the information. Using plain language instead of ten-codes or club slang fits with how ICS-based agencies typically want communications handled.

For the after-action report, a simple structure beats an elaborate one. Describe the scenario, the objectives, what worked, what didn't, and then a corrective action list with an owner and a target date for each item. Hold a short hotwash right after the exercise while memories are fresh, then write the report within a few weeks. Examples of findings that tend to be worth recording: how long it took to establish the first net, whether backup power lasted, which locations had no one trained to operate, whether message logs were complete, and whether checklists matched actual equipment. Then, next year, open with the previous list and see which items were actually closed. That follow-up is what turns a report into improvement.

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.