Making SET and Field Day test what actually breaks: scenario design, message handling and after-action notes
- Replies 2
- Views 21
- 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 treat the Simulated Emergency Test and Field Day as annual checkboxes, but they can be good rehearsals if we design them around the failures that tend to show up in real events. A drill where every station checks in, passes two tidy messages and goes home tells you very little. A drill that forces a handoff, a shift change, a lost repeater or an unclear request tells you a lot.
One way to start is to ask what each hazard stresses. Hurricanes tend to be long-duration problems: fuel, power, operator fatigue, shift rotation and comms with shelters or EOCs after infrastructure is damaged. Wildfires are fast-changing, with evacuations, lost repeater sites and shifting needs for resource and welfare traffic. Floods raise access problems and the question of whether your operators can reach the assignment at all. Earthquakes are no-notice events where you may have to assume phones and internet are unreliable, and where health-and-welfare traffic can swamp a net. Tornadoes are usually short and sharp, so the practice is mostly about spotter-style reporting and clean, brief traffic. Grid failures are a good test of whether repeaters, served-agency sites and your own stations can run on backup power for longer than the battery rating you remember.
That suggests the exercise should not just say 'there is an emergency.' Write a short scenario with injects on a timeline: a repeater goes offline, a shelter requests a resupply message, an agency wants a formal message sent to another county, a net control operator has to be replaced mid-exercise. Then see how the net handles it.
Field Day is a different kind of practice. It is a contest-style event, so it will not test served-agency coordination unless you add that on purpose. What it does well is power, antennas, setup speed, logging and operating under less-than-ideal conditions. If you want more from it, consider adding a message-handling table or a mock agency request so people practice both skills in the same weekend.
Questions for the group: how do you build injects without making the exercise unrealistic? What do you measure, and what ends up in your after-action report? And how much do you rely on a written net script versus letting net control adapt?
Link to comment
https://www.hamradiobase.com/forums/topic/11597-making-set-and-field-day-test-what-actually-breaks-scenario-design-message-handling-and-after-action-notes/Share on other sites