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 412.9 km/s
Aurora 1
Updated 14:00 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

Turning SET and Field Day into real disaster-comms practice: what to test, what to write down, and how to make the after-action report useful

ci_cover.jpg

Most of us agree that exercises matter, but a lot of them end up as a pleasant afternoon on the air followed by a vague "it went well" summary. I'd like to start a discussion on how to get more value from the Simulated Emergency Test (SET), Field Day and local drills, so that what we learn actually changes how we respond to hurricanes, wildfires, floods, earthquakes, tornadoes and grid failures.

Here are a few starting points. Please push back, add your own, or tell us what you'd change.

1. Pick one or two objectives per exercise. Trying to test everything tends to test nothing. Examples of objectives that can be measured:

  • Can we activate a net and reach a minimum number of stations within a set time after a call-out?
  • Can we pass a formal written message (radiogram or an agency form) accurately from point A to point B, with a confirmed receipt?
  • Can a station run for several hours on battery, generator or solar without commercial power?
  • Can we move traffic when the primary repeater is "down" by switching to simplex, a backup repeater, or HF?

2. Treat Field Day as practice for deployment, not just a contest. Field Day is a good chance to rehearse setup speed, power, antennas, logging, shift changes and station layout. If you want it to double as emergency practice, add a few deliberate extras: a timed setup, a "no commercial power" rule, a message-handling table, and someone assigned to watch for problems (tangled cables, dead batteries, RF in the audio, missing adapters) and write them down.

3. Write net scripts that people can follow under stress. A good script is short, with plain language and blanks to fill in. Useful pieces include:

  • Opening: purpose of the net, who is net control, whether it is a directed or informal net, and any emergency or priority traffic call.
  • Check-in method: by category (for example, priority/emergency, agency liaison, relay, routine) rather than everyone at once.
  • Traffic handling: ask for stations with traffic, assign who takes it, and move the exchange off frequency if the net is busy.
  • Closing: a time for the next net or a statement about standby status.

Keep a backup copy on paper. Phones and tablets die, and printed scripts don't need power.

4. Practice message handling, not only voice checks. A checkin that says "I can hear you" is useful, but the real work is moving content accurately. Things worth drilling: writing the message exactly as given, reading back numbers and unusual words, using phonetics where needed, recording times, and avoiding paraphrase. Include a few messages that are inconvenient on purpose, such as ones with long lists, street addresses, medical supply quantities or names with odd spellings.

5. Bring the served agency into the planning. The best exercise is one a served agency (emergency management, a hospital, a shelter operator, the Red Cross, etc.) actually helps shape. Ask them what information they would need to send, to whom, how fast and in what format. Find out whether they'd want radio operators embedded at a location or only on call, what credentialing or identification is required, who is the point of contact, and what the chain of command looks like. We should be adapting to their forms and terminology rather than expecting them to learn ours. Plain language matters: avoid Q-signals and ham slang when speaking to agency staff.

6. Build scenarios around the failure, not just the hazard. A hurricane scenario might emphasize power loss, fuel and long-duration operations, evacuation and shelter reporting. Wildfire might stress changing conditions, smoke, repeater site access and evacuation route status. Floods bring blocked roads and isolated operators. Earthquakes raise questions about damaged infrastructure and sudden overload of the net. Tornadoes involve short timelines and spotter-style reports. A grid failure tests battery, generator and fuel plans, plus whether any of your repeaters have backup power. Inject realistic problems mid-exercise: a repeater drops, net control has to hand off, an operator has to leave, a message arrives with missing information.

7. Capture observations in real time. Appoint an observer or two and give them a simple form: time, what happened, what was expected, who was involved. Memory fades quickly, and the notes people take on the spot are far more useful than recollection a week later.

8. Make the after-action report short and specific. A structure that works well is: objectives, what happened, what worked, what didn't, root cause, and corrective actions with a named owner and a target date. "Improve communication" isn't an action. "Add a laminated frequency card to each go-kit and verify by the next quarterly meeting" is. Then, at the next exercise, check whether the previous items were closed.

Questions for the group:

  • What objectives have you found most revealing in SET or local drills?
  • How do you handle after-action items so they don't quietly disappear?
  • What has helped you work smoothly with served-agency staff who have little radio background?
  • Replies 2
  • Views 124
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing that has helped a lot of groups is separating "net skills" from "station skills" when you evaluate. A net can run beautifully while individual stations struggle with their own setup, or the other way round. If you score them separately, the fixes become obvious: net skills usually need scripts, training and net control rotation, while station skills point to go-kits, power, antennas and checklists.

On message handling, I'd also add a rule that the receiving station reads back the message in full on at least some of the traffic. It's slower, but it shows exactly where errors creep in. Numbers, similar-sounding names and street addresses are the usual culprits. If you run it as a timed drill and then as an accuracy drill, people see the trade-off between speed and correctness and learn when each matters.

For served agencies, a short joint tabletop before the on-air exercise can save a lot of confusion. Even a one-page sheet listing who sends what, in what format and to whom gives everyone something concrete to test.

  • Moderators

Good list. I'd add a point about handoffs, because that's where exercises tend to expose real weaknesses. Test shift changes at stations and at net control: does the incoming operator know which messages are pending, which stations are assigned where, which frequencies are in use and what's been promised to the agency? A simple handoff sheet or log summary makes a big difference. If your exercise runs only an hour or two, you may never see this problem, so consider a longer scenario or at least a forced mid-exercise swap of operators.

Another suggestion for after-action reports: record both the technical problems and the human ones, such as unclear roles, people not knowing whom to ask, or fatigue. Include what went right as well, so the group knows which practices to keep. And when an item is fixed, retest it in the next drill rather than assuming it's solved.

Finally, for Field Day, try designating one station as an "agency desk" where someone plays the role of the served agency and hands operators messages in the agency's own format. It makes the contest feel a bit more like the real job.

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.