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 412.9 km/s
Aurora 1
Updated 14:00 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 SET and Field Day Exercises Worth the Time: Scenarios, Net Scripts, Message Handling and AARs

ci_cover.jpg

Most emergency communications groups run some version of a Simulated Emergency Test, a Field Day, or a tabletop each year. The part that tends to get skipped is turning what happened into changes before the next one. I'd like to collect ideas on how to build exercises that reveal weak spots instead of just confirming that the radios turn on.

Here is a scenario sketch to react to. It is a hypothetical, not a report of a real event. A winter ice storm takes down commercial power across a county. The main repeater is on a generator with limited fuel. A shelter has lost its internet connection. The emergency manager's office wants a status report from every shelter every two hours and a resource request for cots and a generator tech. The exercise runs four hours with scheduled injects: the repeater goes down at hour one, a shelter manager asks for something outside the agreement your group has with the agency at hour two, and a relief operator arrives who has never seen your net procedures at hour three.

A few questions I'd like to hear thoughts on:

1. What injects are most useful? Equipment failure is easy to write, but people problems seem to show the most: shift handoffs, an unfamiliar net control station, a vague message that needs clarifying, an operator who wants to freelance.

2. How detailed should the net script be? A script helps a new NCS keep order and capture check-ins, but it can turn into reading aloud. A one-page version with check-in format, traffic precedence, and a standard line for stating that the net is an exercise may be enough.

3. How do you handle message handling practice? Do you use ICS-213 forms, radiograms, Winlink messages, or whatever the served agency prefers? Whatever you pick, someone should be checking that what arrives matches what was sent.

4. How do you write the after-action report so it gets used? The goal is a short list of findings, each with an owner and a date, rather than a long narrative that nobody opens again.

Share what has worked for your group, or what you'd design differently.

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On message handling and served agencies, the biggest gain is usually agreeing on formats and expectations before the exercise, not during it. If the agency uses ICS-213 for general messages, practice with that. If a hospital or shelter has its own request form, find out what it is and whether they want it transcribed or just summarized. Ask the agency what a good message looks like to them, then build the exercise around it.

Plain language matters more than people expect. Q-signals and ham shorthand are fine between operators in some modes, but on voice nets that relay agency traffic, say what you mean: 'Shelter needs forty cots,' not an abbreviation the recipient has to decode. Keep messages short, read back numbers and names, and keep an ICS-309 communications log so you can reconstruct what was sent, to whom and when.

One inject worth adding is a request that is out of scope, such as a request for something your group has no authority to do or a message that should go through another channel. It lets operators practice saying 'I'll pass that to the person who can answer' rather than improvising. Also check your agreements with the agency to see who is allowed to tell you to deploy, and rehearse not self-deploying.

  • Moderators

Field Day is good practice for the physical side: setting up antennas and power quickly, running on generator or battery, logging accurately, and rotating operators through stations. It is less naturally good at the served-agency side, so it helps to bolt something onto it. Some groups add a message-handling station where operators originate and relay formal messages. The Field Day rules have historically offered bonus credit for that kind of activity, but check the current rules rather than relying on memory. Another option is a short drill during Field Day with a scripted net where a new person serves as NCS and someone else keeps the log.

For the AAR, a simple structure helps: what we planned, what actually happened, why the difference, what we change, who owns the change, and by when. Gather input at a hot wash right after the exercise, while memory is fresh, and then pull data from the logs. Separate observations (the backup battery lasted ninety minutes) from conclusions (we need a bigger battery or a lower-power plan). Include what went well so those practices don't quietly disappear.

Finally, put the open items on the agenda of your next meeting and report on them. An AAR with six findings and three completed fixes does more for readiness than a thorough one that is filed and forgotten.

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.