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 SET and Field Day count: what to test, how to script it, and what to put in the after-action report

ci_cover.jpg

Most clubs run Field Day and the Simulated Emergency Test (SET), and many walk away with a good time and a stack of logs but few changes to how they would actually respond. Here are some ideas for turning both events into practice that shows up in your next activation, and I'd like to hear what others have done differently.

Start with a scenario, not a band plan. Pick a plausible event for your area: a tornado outbreak that knocks out commercial power and cell service in two counties, a wildfire evacuation with the county EOC on generator, a river flood that isolates a shelter, or an earthquake that damages repeater sites. Then write down the questions the served agency would ask. Which shelters are open? Is the hospital reporting a bed count? Who needs a welfare check? Build the exercise traffic around those answers, not around whatever contacts are easy to make.

Treat Field Day as a drill in setup and endurance. It's a poor test of message handling because contest-style exchanges don't resemble real traffic. It is a good test of other things: how fast a team can deploy antennas and power, whether the go-kit has the adapters, fuses and logbooks it needs, how operators handle fatigue and shift changes, and whether you can run on generator or battery without noise problems. Consider adding a small 'served agency' station, such as a table where someone hands operators formal messages to send. That adds a real message-handling component to an otherwise unrelated event.

Net scripts should be short enough to use. A good script covers the preamble (purpose of the net, who is in control, how to check in), check-in categories (emergency or priority traffic first, then station types or locations), a way to call for traffic, and a close with the next net time. Write it so a backup net control operator can pick it up cold. Use tactical call signs tied to location or function (for example 'Shelter North' or 'EOC Liaison') so the operator can change while the function stays the same, and still give your FCC call sign at the intervals required. Leave out 10-codes and jargon. Plain language works better across agencies.

Message handling is where drills show weaknesses. Practice with both the ICS-213 general message form and the ARRL radiogram format, because served agencies and traffic nets may use either. Radiograms have a standard preamble: message number, precedence (Routine, Welfare, Priority, Emergency), station of origin, check (word count), place of origin, time and date filed, followed by the address, text, and signature. Common drill failures are miscounted checks, missing phone numbers in the address, messages that run too long, and operators who rewrite the sender's text. The rule is to send what is written, read back anything uncertain, and keep a log of when each message was received, sent and delivered.

Include the served agency, if they'll participate. Even a short conversation beforehand helps: what formats do they use, who is authorized to originate messages, where do operators check in on arrival, and what do they expect when something goes wrong? If they can't take part, ask whether they'd review your scenario for realism. Remember that your role is to supplement their communications, not to decide priorities, and that sensitive health or personal information has to be handled according to their direction.

Write an after-action report people will actually read. A hot wash right after the exercise, while memory is fresh, works well. Then write a short report with the exercise objectives, who participated, what worked, what didn't, and specific corrective actions with an owner and a deadline. 'Improve coordination' isn't an action item. 'Net control will keep a printed list of all tactical call signs and locations at the table; assigned to the net manager before the next meeting' is. Follow-up matters more than the document: check next quarter whether each fix was made and retest it.

What scenario has your group found most useful, and what's the one problem that keeps turning up exercise after exercise?

  • Replies 2
  • Views 15
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One thing I'd add to the 'treat Field Day as setup practice' point is to give people a role they don't usually fill. If your regular net control always runs the net, have someone else do it, with the regular as backup. The same goes for message handling: rotate who is the originator, who is the relay, and who is the delivery point. Real events rarely run with the people you'd have chosen, and a team that depends on one or two strong operators finds this out at the worst time.

For scenario injects, I like those that create a decision rather than just more traffic. For example, 'the primary repeater is down, switch to simplex or a backup,' or 'two shelters report the same supply request, who consolidates?' Those test your communications plan and your judgment, not just typing speed.

  • Moderators

On the after-action piece, I'd push back a little on writing a long report. A one- or two-page summary that leadership and the served agency will read is better than a ten-page one nobody opens. A simple layout works: what we set out to test, what we observed, what we're changing. Add a short appendix for raw logs and message counts.

It also helps to separate problems by type: equipment, procedures, training, and coordination with the agency. They have different owners. A dead battery is a kit-maintenance issue. Confusion over whether to use ICS-213 or a radiogram is a procedure and agency-liaison issue. If everything sits in one list, the harder items get dropped.

Finally, keep a standing 'known issues' list from one exercise to the next. Seeing the same item reappear three times is a good prompt to fix it properly rather than note it again.

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.