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: Scenarios, Message Handling, and After-Action Reports That Get Used

ci_cover.jpg

Field Day and the Simulated Emergency Test (SET) are both useful, but they test different things. Field Day shows whether you can get stations, power, and antennas working in a hurry. SET, or any local drill, should test whether the communication works: whether traffic gets from a shelter or EOC to its destination, accurately and in a form the receiving party can use. If both events get treated as the same thing, you can come away with a good score and no better prepared.

Here are some ways to use each one, and I'd like to hear what others have tried.

1. Treat Field Day as an equipment and setup rehearsal, then add one deliberate constraint. Run on generator, battery, or solar only. Power up a station from a cold start with no one who normally runs it. Deploy an antenna from a written checklist rather than memory. Handle a few formal messages in between contacts. The contest exchange is easy to do on autopilot, so the constraint is what makes it practice.

2. Build SET scenarios around a specific loss, not just a hazard name. "Hurricane" is a theme. "Commercial power is out across the county, the primary repeater is on a generator with limited fuel, and the hospital needs a supply status relayed to the EOC" is a scenario. Some starting points:

  • Hurricane or flood: shelter status and resource requests, damaged repeater sites, evacuation of a net control station, and traffic going out of the affected area to a distant station for welfare inquiries.
  • Wildfire: rapidly changing evacuation zones, smoke and road closures that cut off a relay site, and a need for clear, repeatable location descriptions.
  • Earthquake: widespread simultaneous failure, damage assessment reports from many small locations, and the need to prioritize when everyone calls at once.
  • Tornado: short warning times, spotter-style reports, and a quick shift from watch to post-event damage and casualty-related traffic.
  • Grid failure: a long-duration event where fuel, battery rotation, operator fatigue, and shift scheduling matter more than any single message.

3. Practice message handling as a skill with its own failure modes. A standard ARRL radiogram has a number, precedence, handling instructions, station of origin, check (word count), place of origin, time and date filed, addressee, text, and signature. Precedences run Emergency, Priority, Welfare, and Routine. The ICS-213 General Message form is also common with served agencies. The usual problems are not exotic: illegible handwriting, a wrong word count, a message that is really three requests, a missing callback number, and operators who paraphrase instead of copying exactly. A good drill includes at least a few messages designed to expose those problems, such as an ambiguous address or a text full of numbers that must be copied verbatim.

4. Write the net script for tired people. A script should help a new net control station who has been up for hours. Include the opening statement, how to call for emergency or priority traffic first, how to take check-ins (and whether to ask for capabilities), a short way to assign traffic, a repeating reminder about stand-by procedures, and closing language. Keep it to one or two pages. Add a pre-printed log sheet so the operator is not inventing a format under stress.

5. Do an after-action report even for a small drill. A simple structure works: what was planned, what happened, what went well, what needs improvement, and who will do what by when. The homeland-security exercise tradition (HSEEP) frames this around strengths, areas for improvement, and corrective actions. The corrective actions are the part groups skip. "Improve comms" is not an action. "Rewrite the shelter report form so the occupant count is the first field, and review it at the next meeting" is.

Questions for discussion:

  • What constraint would you add to Field Day that makes it a better emergency practice without ruining it as an event?
  • How do you test relay of written traffic across more than one net or mode (VHF/UHF to HF, or voice to digital) without turning it into a puzzle?
  • What does your group do with after-action items after the report is written?
  • Replies 2
  • Views 15
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On working with served agencies, the biggest improvement usually comes from agreeing on the product before the drill. Ask the agency, ahead of time, what they actually want to receive: a specific form, a certain format for shelter counts, a named person who authorizes outgoing traffic. Then build your scenario messages in that format. If the agency uses ICS-213 and you hand them a radiogram, or the reverse, you have learned something, but you want to learn it in an exercise.

It also helps to clarify who owns the message. Operators carry traffic; the agency official owns the content and signs it. A simple rule that many groups adopt is that the operator does not edit meaning, only fixes format, and checks anything unclear with the originator. Practice that exchange directly, since it feels awkward in a real event if nobody has done it before.

Finally, invite someone from the agency to observe or play a role, such as a shelter manager or a duty officer. Their feedback on whether the information was useful and timely is often different from what radio operators think went well. Check with your own agency about its policies for volunteer participation, credentialing, and what you are permitted to relay, because those differ widely between places.

  • Administrators

One thing I'd add for the after-action side: record observations during the drill, not afterward. Assign someone as an observer or evaluator who is not also running a station. Have them note times, such as when a message was originated, when it was received, and when delivery was confirmed. Those timestamps turn a vague "it felt slow" into a finding you can act on, like "the delay was between the shelter and net control, not on the relay leg."

For longer scenarios like a grid-failure drill, include things that are easy to forget on a short exercise: a shift change with a written handoff, a fuel or battery check-in, a point where a key operator is declared unavailable, and a station that must be replaced mid-net. Those are the points where real operations tend to break down, and they rarely come up in a two-hour event.

For scenario variety, rotate the stressors rather than inventing a new disaster every time. One year the repeater is down and you go to simplex. Another year the net control station has to relocate. Another, traffic volume is higher than your operators can handle and you must apply precedence and say no to low-priority messages. Keeping a short list of "injects" you can pull from also makes it easier for volunteers to run the exercise without a large planning team.

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.