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

Turning SET and Field Day into real disaster comms practice: what should we be testing, and how do we write it up?

ci_cover.jpg

Every year, many emergency communications groups run a Simulated Emergency Test (SET) and a Field Day, then file a short summary and go back to normal. The risk is that both turn into "we made contacts and the radios worked" without telling us whether we could actually support a served agency during a hurricane, wildfire, flood, earthquake, tornado or long grid outage.

I'd like to start a discussion on how to make these events more useful as practice, and how to capture lessons in an after-action report (AAR) that someone will read. Some starting points:

1. Pick a scenario that forces different problems. A hurricane exercise usually stresses long-duration operations, shelter traffic, and a possible loss of commercial power and internet. A wildfire stresses mobility, evacuation information, and repeater coverage in rough terrain. Floods tend to isolate areas and damage roads. An earthquake raises questions about damaged infrastructure and a sudden surge of welfare traffic. Tornadoes bring short-notice activation and spotter-style reporting. A grid failure tests battery plans, generator fuel, and how long your own repeaters can stay up. If every drill is "generic disaster," you only practice generic problems.

2. Treat message handling as the main skill, not a side activity. Field Day is excellent for setting up stations quickly, operating on generator or battery power, and working under less-than-ideal conditions. But a contact exchange is not the same as handling formal traffic. Consider adding practice messages: a shelter supply request, a status report from a hospital, a welfare inquiry. Check for the basics: Is the message complete? Does it have a clear originator and recipient? Was it copied exactly? Was it read back when needed? Was it delivered, and did anyone record the time?

3. Write net scripts that people can follow under stress. A good script is short, plain, and easy to read aloud. It should cover who the net control station is, the purpose of the net, how to check in (emergency or priority traffic first, then others), how to request relays, and when the net will close or change frequency. It helps to have a printed version at each station, plus a few variations: a directed net, an informal net, and a net where net control must be handed off partway through.

4. Practice working with the served agency, not just with each other. Whether it's emergency management, a Red Cross chapter, a hospital, or a shelter manager, the agency's needs drive the exercise. Ask them what information they actually need, in what format, and how quickly. Have them write some of the messages. Agree beforehand on who may authorize a message to be sent, and on what is confidential. Operators should be ready to say "I'm here to move your message, not to decide your response."

5. Capture lessons while they're fresh. A useful AAR is simple: what was planned, what happened, what went well, what didn't, and what specific actions will be taken, by whom, and by when. Avoid vague items like "improve communication." Instead: "Replace the shelter-station antenna feedline," or "Add a second trained operator to each shelter shift."

So, a few questions for the group: What do you include in your SET to make it more than a contact count? How do you adapt Field Day to practice emergency skills without spoiling the fun? And what has been the most useful change you've made to a net script or AAR template?

  • Replies 2
  • Views 56
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing that helps is separating the exercise into objectives before anyone touches a radio. For example: "Deliver ten formal messages with no transcription errors," "Bring up a station on battery power within 30 minutes," or "Switch to a backup frequency when the primary is declared unusable." Objectives like that make the AAR much easier, because you can mark each one met, partly met, or not met, and then explain why.

For Field Day, I'd suggest a small side activity rather than rewriting the whole event. Set aside a block of time where one station acts as a mock shelter and another as a mock emergency operations center, and have a handful of written messages passed between them through a relay station. People still get their contacts, but a few operators get real practice with message formatting, readbacks, and logging delivery times. It also exposes the awkward gaps, like whoever is copying doesn't know how to handle an unclear word, or the log doesn't have a place for the delivery time.

  • Administrators

On served agencies, I'd add that expectations should be written down before the exercise, even if it's only half a page. Cover things like who is the point of contact, what the agency expects volunteers to do and not do, what credentials or check-in procedure applies, and what happens when the agency's priorities change mid-event. Many frustrations I see described in AARs come from mismatched assumptions rather than from radio problems.

Also consider a "curveball" injects list. Have the exercise planner hold a few surprises: the net control operator becomes unavailable, a repeater is declared down, a message arrives with missing information, or a request comes in that is outside the group's scope. Then see how the team responds. It's a gentle way to test judgment, and the lessons can go straight into the next version of your net script and your AAR action items.

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.