Making SET and Field Day count: how do you turn drills into real disaster-comms practice?
- Replies 2
- Views 33
- Created
- Last Reply
Top Posters In This Topic
-
Admin_Terry 1 post
-
Mod_Nancy 1 post
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 exercises are the only safe place to find out what breaks. The harder question is whether a drill produces anything we can use afterward. Here are some thoughts on scenario design, and I'd like to hear how other groups handle it.
Start with the hazard, not the radios. Each hazard stresses a different part of the comms plan. A hurricane is a long-duration event with warning time. That makes it a test of shift rotation, fuel and battery logistics, check-in routines for members in the affected area, and what happens when the net control station loses power on day three. A wildfire moves quickly and changes geometry: evacuation zones shift, repeaters and their links can be lost, and mobile and portable operation matters more than a fixed shack. Floods tend to produce gauge and road-closure reports, which suit short, structured messages. An earthquake raises the welfare-traffic problem and the question of which infrastructure still works. A tornado leaves almost no lead time, so the exercise question is often how fast you can get from a normal evening to an activated net. A grid failure is the slow burn. Cell sites and repeater sites run on batteries and generators with finite endurance, so the scenario should include things degrading over time, not one dramatic failure.
Use injects, not a fixed script. A scenario that says "Shelter A requests 40 cots" is fine for message handling. It teaches more when the exercise controller also injects "the primary repeater is down" or "your net control operator has to leave," and watches whether the group moves to simplex, a backup frequency, or an alternate NCS without confusion.
Treat the Simulated Emergency Test as a rehearsal of the whole chain. SET is an ARRL exercise that sections and local groups adapt to their own needs. It's most useful when it includes a real served-agency angle, such as a hospital, emergency management office, or shelter operator, and when the messages are originated by people who aren't hams, or at least on the agency's own forms. Handling traffic you wrote yourself in a format you like only tests part of the chain.
Field Day is practice, but only if you choose to make it so. It builds the basics: setting up antennas quickly, running on generator or battery power, working with unfamiliar gear, and operating in bad conditions. It is also easy to run purely as a contest. Groups that want emergency-comms value from it often add a separate message-handling table, practice formal radiogram format, test a digital path such as Winlink if their plan uses it, and rehearse a short check-in net. The rules include bonus categories related to message handling, so check the current rules rather than relying on memory.
Message handling is where the details bite. A standard radiogram has a preamble (message number, precedence, handling instructions if any, station of origin, check, place of origin, time and date), then address, text, and signature. The check is the word count of the text, so the receiving station can confirm nothing was dropped. Precedences run Routine, Welfare, Priority and Emergency, and a surprising amount of practice is just not using Priority for everything. Many served agencies work with ICS-213 General Message forms. Deciding up front how a 213 gets transcribed to radiogram format and back, and who is allowed to sign, saves a lot of confusion mid-event.
Net scripts should be short enough to read under stress. A good script usually covers the opening statement and purpose of the net, how to check in (emergency or priority traffic first, then others), how to request relay, and how the net closes or hands off. Fill-in-the-blank fields for date, frequency, and NCS callsign help. If the script takes a full minute to read before anyone can speak, expect people to start improvising.
After-action reports need owners. A useful AAR is more than a recap. The common structure is what was planned, what happened, what worked, what didn't, and corrective actions. Each corrective action should name a person and a rough deadline, or it tends to turn into a list of good intentions that is repeated the next year.
Questions for the group: What do you inject into your scenarios to force a plan change? How do you structure working with served agencies so you're supporting their communication needs rather than substituting your own procedures? And what is the one item that shows up in every after-action report but never seems to get fixed?
Link to comment
https://www.hamradiobase.com/forums/topic/11321-making-set-and-field-day-count-how-do-you-turn-drills-into-real-disaster-comms-practice/Share on other sites