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: practicing message handling, net discipline and served-agency work before the real event

ci_cover.jpg

Most of us agree that Field Day and the Simulated Emergency Test (SET) are good practice. In many groups, though, they end up as a contest weekend and a quick drill that nobody reviews. I'd like to compare notes on how to turn them into training that carries over to a hurricane, wildfire, flood, earthquake, tornado outbreak or extended grid failure.

Here are a few starting points. Please add your own.

1. Treat message handling as the main skill. Making contacts is not the goal of emergency communication. Getting a message from the originator to the addressee, accurately and with accountability, is. Field Day is a good place to practice because there is already a message-origination bonus and plenty of idle operators. Do you also practice writing a message so the text is short and unambiguous? Do you practice checking the word count, reading it back, and logging who passed it to whom? A radiogram has a number, precedence, handling instructions, station of origin, check, place of origin, time and date filed, addressee, text and signature. Agencies may instead hand you an ICS-213 General Message form. Operators should be comfortable moving between the two without dropping information.

2. Plain language over shorthand. Served agencies generally want plain language, not ham jargon or police-style codes. Q-signals are fine between operators on CW, but on voice nets "net control, I have a hospital with no generator fuel and fourteen patients on oxygen" is far better than anything clever. Is your net script written to encourage that?

3. Net scripts that survive stress. A good script usually has a short preamble (purpose, frequency, who is in control), a call for emergency or priority traffic first, check-ins by category (for example, stations at shelters, at the EOC, mobile, and general), then a traffic list and a clear closing. Tactical call signs such as "Shelter North" or "County EOC" help when operators rotate through shifts, as long as legal station identification is still done with the FCC call sign at the required intervals. Does your script cover what to do when net control drops off, the repeater fails, or the primary frequency is unusable? Does it say who takes over, and where the group moves next?

4. Scenario variety. Each hazard stresses a different part of the system:

Hurricanes are long-duration events with shelter staffing, fuel logistics and operator fatigue, plus a lot of welfare traffic after landfall. Wildfires bring evacuation, smoke, road closures and the loss of mountaintop repeater sites to fire or power failure. Floods cut off access routes and can isolate whole communities. Earthquakes call for rapid damage assessment and for working without the infrastructure you normally rely on. Tornadoes give very little warning and rely on SKYWARN-style spotter reporting, followed by a different set of needs after the storm. Grid failures test battery capacity, generator discipline, repeater backup power and cellular congestion. Which of these does your local SET scenario rarely cover?

5. After-action reports that change something. A useful after-action report (AAR) is short and specific. It lists what the exercise set out to test, what worked, what didn't, why, and a corrective action with a named owner and a due date. If every AAR ends with "improve training," nothing will change. If it says "re-test the 2-meter simplex fallback between the shelter and the EOC before the next quarterly drill," something will.

6. Working with served agencies. Relationships built before an activation make a big difference. Do your agency contacts know what you can and cannot do? Have they seen your credentials or training records? Have they been invited to observe a drill and give feedback on the message forms and the process? Often the most valuable part of an exercise is hearing the served agency say "we wouldn't have asked for it that way."

What has your group changed after an exercise, and what do you think most drills still get wrong?

  • Replies 2
  • Views 56
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On Field Day, the easiest improvement is to turn part of it into a deliberate traffic exercise instead of leaving it as a side bonus. Have a few people write messages in different formats: a formal radiogram, an ICS-213 style note, and a request that arrives as a verbal phone call and has to be transcribed. Then send them over different modes such as voice, CW, digital and Winlink if you use it, and see where errors creep in. Word counts, spelling out unusual names and numbers, and "say again all after..." practice are all skills that go rusty.

One more suggestion is to make someone the message tracker, not an operator. Their only job is to confirm every message sent was also delivered and logged. That mirrors what a served agency will care about most in a real event: did the message arrive, and can we prove it?

Also, rotate operators out of their comfort zone. The person who always runs the HF station might spend an hour as net control or at the check-in desk. In an actual activation you may not get the assignment you trained for.

  • Moderators

I'd add a point about scenario design for SET. Exercises that are too clean tend to teach less. Injects help, such as a repeater going offline mid-net, a shelter manager changing the request, a message arriving with an incomplete address, or a station having to switch to battery power with a limited run-time. Keep the injects realistic and within the scenario, and make sure the exercise is clearly marked as an exercise on the air so it isn't mistaken for a real emergency. Many groups use a standard phrase like "this is an exercise" at the start and end of transmissions.

For the AAR, collect input from several sides before the debrief: net control, field operators, any agency observers, and whoever managed logs. People remember different things, and operators in the field often see problems net control can't. Writing observations down while they are fresh matters more than writing them up neatly. Then sort the findings into strengths, areas for improvement, and corrective actions, which is the same basic structure many emergency management exercises follow. Check your own jurisdiction's guidance, since served agencies may have specific formats they would like you to use.

Finally, test the boring parts: power, antennas, go-kits, logs, forms, pens, maps, and printed copies of the net script. Digital tools are great until a laptop battery dies, so keep a paper fallback for the things you can't afford to lose.

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.