Turning SET and Field Day into real disaster-comms practice: what are you testing, and how do you capture it?
- Replies 2
- Views 8
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
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?
Link to comment
https://www.hamradiobase.com/forums/topic/11833-turning-set-and-field-day-into-real-disaster-comms-practice-what-are-you-testing-and-how-do-you-capture-it/Share on other sites