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 Count: Scenario Ideas, Net Scripts, and What After-Action Reports Should Capture

ci_cover.jpg

Most of us agree that drills are supposed to prepare us for real events. In practice, a Simulated Emergency Test or a Field Day weekend can turn into a contact-count exercise where everyone has fun, the antennas go up, and nothing is learned about handling traffic for a served agency. I'd like to collect ideas on how to make these events better practice, and how to write up the results so the next drill is better than the last.

One way to start is to pick a scenario that stresses a different failure each time. A hurricane scenario stresses long-duration operations, fuel and battery logistics, shift rotation, and welfare traffic going out of the affected area. A wildfire scenario stresses evacuations that change quickly, repeater sites losing power or access, and the need to work with an incident command structure that is moving. Flooding tends to cut roads and strand people, so you can practice relaying between shelters and an EOC when your normal routes are blocked. An earthquake scenario means assuming that infrastructure is damaged without warning and that many of your usual contacts are unavailable. Tornado scenarios compress everything into a short window, which suits spotter nets and quick check-ins. A grid failure scenario tests what happens when the internet, cell service, and repeater backup power fail together.

Then there is the message side. Whatever the scenario, I think every exercise should push real formatted traffic, not just "test, test" exchanges. That means practicing both the ARRL radiogram format (number, precedence, station of origin, check, place of origin, filing time and date, addressee, text, signature) and the general message form your served agencies actually use, such as an ICS-213 if that's what they hand you. Writing a message clearly, counting words for the check, and reading it back accurately are skills that go stale quickly. The precedences (Routine, Welfare, Priority, Emergency) are also worth drilling, because operators often default to treating everything as urgent.

For net scripts, the best ones are short enough to read under stress. A useful script covers: who is net control and why the net is open, the type of net (directed, informal, resource, or tactical), a check-in method that keeps the frequency from being swamped (by region, by capability, or by priority traffic first), a clear place to call for emergency or priority traffic, and a clean close with a time for the next net. Tactical call signs or location names such as "Shelter North" or "County EOC" keep things straightforward when operators rotate. And remember to identify with your FCC call sign as required.

Finally, the after-action report. A report that says "it went well" is not much use. Better to record what was planned, what actually happened, what the gap was, and what the fix is, with an owner and a deadline for each fix. Useful questions include: how long did it take to get the first station on the air and the first message delivered, did the served agency know who to contact and what we could and couldn't do, where did the message handling break down, which equipment or power plan failed, and which operators were overloaded.

So, what scenarios have you found most useful for SET, what would you change about how Field Day is used as practice, and what do you include in your after-action reports?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing that makes Field Day more useful as practice is adding constraints that the contest format doesn't give you. For example, set up one station as an "EOC station" that only handles formatted messages, not contacts. Have a few volunteers write messages in advance, with a mix of precedences and some deliberately awkward text such as numbers, unusual place names, and a few with errors for the receiving operator to catch. Then see how long it takes to get a message from origin to delivery by voice, digital, or both. Another useful constraint is running some of the weekend on emergency power only, with a plan for who is responsible for fuel, batteries, and the changeover. The goal is to see where the weak points are while there's still time to fix them.

On net scripts, I'd also add a line for what to do if net control goes silent or loses power. A named alternate net control and a backup frequency, stated at the start, saves a lot of confusion.

  • Administrators

On served agencies, I think the biggest gap in many exercises is that the agency isn't really in the loop. If SET only involves radio operators talking to each other, you learn whether the radios work, but not whether the agency can use what you provide. If possible, ask the agency's emergency manager or a designated contact to write the scenario injects or at least review them. They know what information they would actually need, such as shelter occupancy, road status, a resource request, or a welfare check, and in what form. Ask them how they want messages delivered, whether on paper, by phone, or hand-carried, and who is authorized to sign off or accept them.

It also helps to be clear about roles. Amateur operators carry communications; they don't decide for the agency. Writing that expectation into the exercise and the after-action report prevents friction later. And when you write the report, include the agency's feedback alongside your own observations, since they may see problems you didn't, such as messages that were accurate but too long, or traffic that arrived with no clear action requested.

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.