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 Scenarios Expose Real Weak Points Before a Disaster Does

ci_cover.jpg

Many emergency communication exercises go smoothly because they were designed to go smoothly. Everyone checks in on the usual repeater, the net script runs in order, a few messages get passed, and the after-action discussion is mostly "that went well." That feels good, but it tells you little about how the group would cope when the repeater site has lost power, the served agency wants something you did not plan for, and half the roster is unavailable.

I'd like to compare notes on how to build scenarios that stress the right things. Here is a starting framework, and I'd like to hear where it breaks down.

Start with the hazard, then work out the communication failure it causes. A hurricane suggests long-duration power loss, damaged infrastructure, shelter support, and welfare traffic. A wildfire suggests evacuations, shifting road closures, smoke, and communications from remote or mountainous terrain. Floods raise questions about access, shelter locations, and which bridges your operators can still cross. Earthquakes and tornadoes tend to be sudden and local, so the early problem is often getting a few trained people to a few key places quickly. A grid failure tests whether your "backup" really is a backup. Each hazard breaks different links, so the same exercise run every year will keep testing the same assumptions.

Inject failures instead of announcing them. Rather than telling the group "the primary repeater is down," have net control simply stop using it, or make it unavailable partway through. Do the operators know the fallback, whether that is simplex, a second repeater, or an HF path? Can they get there without being walked through it? The same goes for a served-agency liaison who is "unreachable" or a station that has to hand off its role in the middle of the exercise.

Use the Simulated Emergency Test as a test, not a demonstration. The ARRL's SET is typically run on a local or section basis, which gives you room to tailor it. Some elements worth building in:

  • Messages that must be formatted, passed, and delivered to a real or role-played recipient, not just read over the air.
  • At least one message that needs clarification, so operators have to ask for a repeat or a verification instead of guessing.
  • A tactical-call setup (for example, location- or function-based names) so people practice using them instead of personal call signs, with legal station identification still handled properly.
  • A shift change, so logs, open messages, and net status have to be handed over in writing.
  • A resource-request message that requires a reply, so you see how well the loop closes.

Treat the net script as a living document. A good script covers the preamble, the purpose and scope of the net, priority or emergency traffic calls first, then check-ins by category, then routine traffic and a clear close. It is much more useful if it also has short decision prompts: what to do if net control is lost, how to hand off, when to move to a different frequency, and who can authorize that. If your script only works when the person who wrote it is running the net, it needs another pass.

Write the after-action report while it's fresh. A format that works well for small groups is: what we intended to test, what actually happened, why it happened, what to sustain, and what to change, with a named owner and a date for each change. Specific observations ("three stations did not know the fallback frequency") are more useful than general conclusions ("communication could be better"). Include a note on what the served agency actually needed, since that may differ from what you assumed.

Which failure injects have taught your groups the most, and which ones turned out to be too artificial to be worth the trouble?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

I'd put message handling near the top of the list. It's easy to run a net where everyone checks in cleanly but no one has ever had to move a written message from an originator to a recipient without it changing along the way.

A few things worth building into the exercise:

First, use both formats your group is likely to encounter. A served agency may hand you a form such as ICS-213, while the formal radiogram format has its own structure: message number, precedence, handling instructions, station of origin, check (the word count), place of origin, filing time and date, addressee, text, and signature. Having operators convert between the two, without altering the meaning, is a good skill test. Check counts are a useful habit as well, since a mismatch tells the receiving station something went wrong in transit.

Second, practice precedence honestly. Emergency, priority, welfare, and routine mean different things, and in an exercise people tend to label everything priority. Include a deliberate mix and see whether net control can sort it. Welfare inquiries in particular behave differently from agency traffic, so decide beforehand how your group would handle them and who it would coordinate with.

Third, make the message text awkward on purpose: numbers, street names, unfamiliar surnames, medical supply names. Phonetics and "say again all after" get exercised quickly. Ambiguity at the originating end is a common cause of bad messages, so it's worth having the originator practice writing clearly as well.

On served agencies, it helps to agree in advance, preferably in writing, on what they will ask for, who is authorized to hand you traffic, and what you are not going to be responsible for. An exercise that includes a real conversation with the agency contact often reveals gaps that a purely internal drill never would.

  • Moderators

I'd add Field Day to the practice list, with the caveat that it only helps if you deliberately use it that way. As a contest-style operating event, it's built around making contacts. That has value, since it forces you to set up antennas, power, and stations in the field, often on generators, batteries, or solar, and to do it under a time limit. But the scoring doesn't reward the things that matter in a deployment, so you have to add them.

Some ways to turn Field Day into useful practice:

Treat setup as the exercise. Time it, and note what was forgotten: adapters, extension cords, fuel, logging supplies, a working copy of the net script. Also, who knew where things were stored? If the answer is "only one person," that's a finding.

Run a short, informal traffic-handling segment alongside the contacts. Even a handful of formatted messages passed between stations will show whether people remember the procedure. Many Field Day rules also include credit for message handling, but check the current rules for the exact details instead of relying on memory.

Rotate people into roles they don't usually fill, such as logger, net control, or the person handling the written message queue, so the group doesn't depend on the same few operators.

Then actually write the after-action notes before everyone goes home or the next morning. Details fade quickly. Short bullets on power, antennas, operating positions, comfort and fatigue, and what you would carry differently are enough. Fatigue and weather are underrated: a station that works fine for two hours in good conditions may be a different story overnight.

One caution: Field Day success can create false confidence. Good HF contacts under open conditions don't prove you can support a hospital, shelter, or emergency operations center, where the constraints are mostly about people, procedures, and relationships. Pair it with a separate, agency-facing drill so the two kinds of practice cover different gaps.

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.