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 are you testing, and how do you capture it?

ci_cover.jpg

Most of us agree that the Simulated Emergency Test and Field Day are good for the hobby. The harder question is whether they make us better at disaster communication, or whether we just enjoy them and go home. Here is a framework for discussion, and I'd like to hear how other groups handle it.

Start with a scenario that stresses a specific failure. "Hurricane" is a backdrop, not a test objective. Better objectives sound like this: the county EOC loses commercial power and its primary repeater site is on generator with limited fuel; a wildfire evacuation closes the road to your usual net control location; a flood cuts the only bridge between a shelter and the hospital; an earthquake takes out telephone and internet, so your Winlink gateway is unreachable and you need a backup path. Each of these forces a different decision. Do you shift to simplex? Do you relocate net control? Do you move traffic by VHF relay, HF NVIS, or a packet or Winlink path that does not depend on the internet?

Treat Field Day as a skills rehearsal, not a contest only. Field Day is a good time to practice what a deployment needs: setting up on emergency power, getting antennas up quickly with whatever is on hand, logging cleanly, and working in noise and weather. You can add a small served-agency-style layer on top. For example, designate one table as the "shelter" and have it originate a few formal messages that must be routed to another table. The contest exchange keeps running, but people also practice handling real message formats. Be honest in your notes about what the bonus-point activities did and did not teach.

Message handling is where groups tend to be weakest. Radio operators can pass signal reports all day and still stumble when a 40-word message needs to be copied accurately and delivered to a person. Two formats are worth drilling. The ARRL radiogram has a preamble (message number, precedence, station of origin, check, place of origin, time and date filed), then address, text, and signature. The check is the word count of the text. Precedences are Routine, Welfare, Priority, and Emergency. Agencies commonly use ICS-213 General Message forms, so many groups practice converting between a form and a radiogram without changing the meaning. Practice reading numbers and unusual words with phonetics, and agree in advance on when you say "break" and "fill" so that the receiving station can ask for repeats without confusion.

Net scripts: shorter is better. A good net script is not a speech. It gives net control a consistent opening (purpose of the net, whether emergency or priority traffic has precedence, frequency and any alternates), a call for priority traffic first, then check-ins by category such as stations with traffic, stations with resources, and stations that are mobile or at a served-agency location. It should also include a plan for when net control goes silent or off the air: who is the alternate, and on what frequency do you meet? Print the script on one page and put it in the go-kit. Review it after each exercise and cut whatever people skipped.

Served agencies change the exercise. If you work with the Red Cross, emergency management, a hospital, or a shelter team, the most useful practice is often not radio at all. Learn who the point of contact is, what information the agency actually needs, what they do not want you to say on air, and how they prefer to receive a message: written, verbal, or via a runner. Ask whether your operators will be badged or credentialed, who gives them tasking, and how the agency will let you know when your help is no longer needed. Those expectations are better settled before an event than during one.

After-action reports are where practice becomes improvement. A useful report is short and structured: the objectives, what happened, what worked, what did not, and the corrective action with a name and a date attached. Avoid vague items such as "improve communication." Write "two operators could not find the alternate frequency in their kit; add the frequency card to the kit checklist and verify at the next monthly meeting." Record timing too: how long to get net control on the air, how long to first message delivered, how many messages needed to be resent, and how many were delivered without errors. Those numbers help you compare one exercise with the next without relying on memory.

Questions for the thread: What failure scenario do you most want to rehearse this year? How do you keep SET from becoming a routine check-in net? And what is the one item on your after-action list that keeps coming back?

  • Replies 2
  • Views 8
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the "what keeps coming back" question, the usual suspect in many groups is power and logistics, not radio technique. Things like dead batteries, a missing adapter, no spare coax, no paper and pencil, or nobody knowing who has the key to the building. One fix is a simple kit checklist that is checked off during an exercise rather than assumed. Then the after-action report can say "checklist found three missing items" instead of leaving it to memory.

For SET specifically, I would add injects: small surprises delivered by whoever is playing the served agency. For example, the primary repeater is declared "down" at a set time, or a message arrives with an unclear address, or the shelter manager changes the request halfway through. These test decision-making and not only the ability to follow a script. Keep the injects realistic and modest, so that the exercise is a stretch rather than a collapse.

  • Moderators

I would add a point about message accuracy. When a group runs a drill, it is tempting to count messages passed. A better measure is whether the received text matches the original, and whether the right person got it in a reasonable time. A simple method is to have the originator keep a copy and compare it with the delivered copy afterward, marking each discrepancy as a dropped word, a changed number, a wrong name, or a missing signature.

On net scripts, I like the idea of a separate short script for "net control lost" and for "switch to alternate frequency or mode," because those are the moments when people improvise. Also be careful about plain language with agencies. Ten-codes and ham shorthand can confuse non-radio partners, so many groups practice saying exactly what they mean in ordinary words. And for the served-agency side, ask the agency to critique the exercise as well. Their view of what was useful may differ from yours, and that belongs in the after-action report.

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.