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

Making Field Day and SET Count: Building Disaster Comms Drills That Produce Useful After-Action Reports

ci_cover.jpg

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?

  • Replies 2
  • Views 28
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Good outline. I would add one thing to the after-action section: record timestamps during the exercise, not afterward. Memory smooths over delays. If the net log shows 14 minutes between a message being received at the shelter and it being delivered to the EOC, the report has something concrete to fix. Without times, it turns into "traffic handling was slow," which nobody can act on.

On injects, a simple one that exposes a lot is the "wrong format" message. Hand an operator a long, rambling request and see whether they can condense it to a clean message without changing its meaning. It tests judgment as well as typing. Another is a deliberate station dropout in the middle of a net, to see whether the group notices and what happens to the messages that station was holding.

  • Administrators

Worth separating two audiences for the report. The members want the lessons, written plainly: this link failed, this form confused people, this role had no backup. The served agency wants a one-page summary showing what capability was demonstrated and what they might do differently. Trying to serve both in one document usually makes it too long for the agency and too thin for the members.

On Field Day, one practical suggestion is to treat the Saturday-night shift change as a mini-exercise. Hand over a station with a written log, open traffic, and current status, and see what gets lost. Shift handoff is where a multi-day deployment tends to break down, and Field Day is a low-stakes place to find that out. Also, if you can't get an agency person to the site, at least ask them for three sample messages beforehand. Even that small step makes the traffic more realistic.

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.