Making Field Day and SET Count: Building Disaster Comms Drills That Produce Useful After-Action Reports
- Replies 2
- Views 28
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Field Day and the Simulated Emergency Test are often treated as two separate things: Field Day as a social event with a contest score, SET as the serious exercise. They work better as one training cycle. Field Day tests stations, power, antennas and setup speed. SET tests whether the group can pass real traffic in a format a served agency can use. Most groups need both, and most groups can get more out of each than they do now.
Here is a framework for discussion. Please push back on any of it.
Start with the scenario, not the radios. A generic "the power is out" premise produces generic results. Each hazard stresses a different part of the system:
Hurricanes are long-duration events. The problems are shift rotation, fuel, operator fatigue, damaged repeaters, and traffic that moves from shelter logistics to health-and-welfare inquiries. The drill question is whether the net can run for days, not just for the two hours of an exercise.
Wildfires change fast. Evacuation zones move, roads close, and smoke and terrain break up line-of-sight paths. A useful inject is losing the primary repeater partway through, to see how quickly the group falls back to simplex, a secondary machine, or HF/NVIS relay.
Floods create isolated pockets and road closures. Operators may be unable to reach their assigned location. Test whether alternates are pre-identified and whether anyone is tracking who is where.
Earthquakes come with no warning. The first hours involve damage assessment and the question of who calls whom. An exercise might start with no activation notice at all, to see how the group self-organizes and whether the call-out tree works.
Tornadoes need short-notice response, spotter-style reporting, and a clear line between the weather-reporting role and the emergency-communications role. Practice staying out of the way of an already busy channel.
Grid failures are the quietest hazard and often the most revealing. Repeaters on battery or generator will eventually run down. Cellular service degrades as backup power at cell sites is exhausted. A drill can ask which links are on backup power, how long that lasts, and who refuels them.
Now Field Day as practice. A few small changes help. Set up some stations as if they were deployed rather than as contest stations: no commercial power, a battery-and-solar position, and a digital-modes position that tries to pass formatted messages instead of exchanging contest serials. Run one deliberate "served agency" station that originates and receives practice messages. Time the setup and teardown, and write the numbers down. Rotate people into roles they do not normally fill, such as net control, message logger, or station supervisor.
For message handling, the biggest gap in many groups is not the radio skill. It is the paperwork. Practice both formats: the ARRL radiogram (preamble with number, precedence, station of origin, check, place of origin, time and date, followed by address, text and signature) and the ICS-213 General Message form that many agencies use. Agree in advance which format your served agency expects, and practice converting between them. Counting words, spelling out unusual terms, and reading back the check are the habits that tend to fade between exercises. Remember the four precedences: Emergency, Priority, Welfare and Routine. Many drills use only one of them.
On net scripts, a good one is short enough to read under stress and flexible enough to survive a change in conditions. Typically it covers: the net's purpose and type (directed, informal, or resource), a call for emergency or priority traffic first, check-ins by category such as shelters, EOC, and mobile, then listed traffic, then routine business. Keep tactical call signs ("Shelter One", "EOC") in the script, with a reminder to identify with your FCC call sign as required. Printed copies should include fallback frequencies and the criteria for switching to them.
Working with served agencies is where many exercises either pay off or fall flat. Invite a staff member from emergency management, a hospital, a Red Cross chapter or a public works department to design one or two injects. They will write messages that reflect what they actually need to send, not what hams assume they need. Ask them afterward whether the format, the timing and the level of detail were useful. Check also whether your operators know the agency's own terminology, and whether the agency knows what amateur radio can and cannot do.
Finally, the after-action report. Many reports are narratives of what happened. A more useful structure asks four questions: What was supposed to happen? What actually happened? Why was there a difference? What will we change, who owns the change, and by when? Separate observations from recommendations, name a person for each corrective action, and carry unfinished items into the next exercise's objectives. Following the improvement-planning style used in formal exercise programs makes the report easier for an agency partner to read.
Questions for the group: What is the one inject that most reliably exposes weaknesses in your drills? How do you keep message-handling practice from becoming a box-ticking exercise? And what do you put in an after-action report that actually gets read?
Link to comment
https://www.hamradiobase.com/forums/topic/11422-making-field-day-and-set-count-building-disaster-comms-drills-that-produce-useful-after-action-reports/Share on other sites