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, Message Handling and Served-Agency Lessons

ci_cover.jpg

Most clubs run a Simulated Emergency Test or Field Day every year, but it's easy to treat them as participation events: make contacts, log them, take photos, go home. They can also be rehearsals for the things that go wrong in real activations. This thread is for comparing ideas on how to build exercises that expose weak points while the stakes are low.

A useful way to start is to pick a hazard and ask what it breaks, rather than which radios to bring. Each hazard stresses a different part of the communications plan:

Hurricanes give warning, so the problems tend to be about sustained operations. Think shift schedules, fuel and battery logistics, operators who evacuate or can't reach the shelter, and long-haul traffic when the local area is damaged. A good exercise injects a mid-event change, such as a shelter closing and its occupants moving to another site, and checks whether net control and the served agency's liaison hear about it at the same time.

Wildfires change fast, and repeaters on mountaintops can be lost to fire or power failure. Exercise a simplex fallback plan, route changes when a road closes, and what happens when an evacuation zone sits on top of your planned operating location. Check whether operators know where the agreed fallback frequencies are without looking them up on a phone.

Floods make access the main issue. Bridges, low roads and flooded parking lots can cut off a site from its operators. Scenario injects can include a gauge-reading report, a request for a welfare check, or a shelter that needs supplies. They also test whether your messages say exactly where something is rather than "the usual spot."

Earthquakes come without warning and may take out infrastructure in patterns that are hard to predict. The first hour is usually about check-ins and damage assessment, so practice a structured net that collects short, standardized reports instead of letting everyone call in at once. Also test whether people can reach their assigned site if their usual route is blocked.

Tornadoes are localized and quick. Spotter-style communication, clear reporting of location and direction, and a clean handoff between a weather-focused net and a post-event damage net are good things to test. The after-event phase often gets less practice than the warning phase.

Grid failures are good for testing the unglamorous parts: how long do your batteries really last under a realistic duty cycle, can you recharge, does anyone know the generator's fuel plan, and what happens when cell service and internet degrade together? A long outage scenario also reveals operator fatigue and the need for relief schedules.

Field Day is not an emergency exercise by itself, but it is excellent practice for the underlying skills: setting up quickly away from home power, solving antenna and interference problems, managing a station log, and working as a team. To get more from it, add an emergency-style element: a traffic-handling station that originates and delivers formal messages, a short drill where one station must set up in a different band or mode on short notice, or a rotation that makes someone who normally runs a station take on net control or logging duties.

For net scripts, short is usually better than clever. A script should cover the net's purpose, the call for emergency or priority traffic first, then check-ins by category, then routine traffic, then closing and next net time. Consider keeping a printed copy with a separate quick-reference card for new net control operators, containing the frequency plan, the agency contact list, and the rules for who may speak. If a script only works for the person who wrote it, it isn't really a script.

Message handling deserves its own drill. In the ARRL radiogram format, the preamble carries a message number, precedence, any handling instructions, station of origin, check (the word count), place of origin, and time and date filed, followed by the address, text and signature. The check matters because it gives the receiving operator a way to notice that something was dropped. Common precedences include Routine, Welfare, Priority and Emergency, and it helps if operators agree beforehand on what qualifies. Also practice the discipline of reading back figures and unusual names, spelling them phonetically, and not paraphrasing the text. The sender's wording is what the served agency actually wrote.

On working with served agencies, the most useful exercises are the ones where a real agency contact takes part, even in a limited way. Ask what information they actually need, in what form, and who is authorized to hand it to you. Agencies often want concise, verified, actionable reports rather than everything an operator hears. It helps to settle questions like these in advance: who tasks the volunteers, how are operators identified at the site, what is the policy on releasing information, and how do you hand off when a shift ends?

Finally, an exercise isn't finished until it produces an after-action report. A simple structure works: objectives, what actually happened, what went well, what didn't, causes (not blame), and specific corrective actions with an owner and a due date. Corrective actions that nobody owns tend to reappear unchanged next year.

Questions to get things going: What inject has most reliably exposed a weakness in your group's plan? How do you keep a scenario realistic without making it so complicated that participants spend the time reading instructions? And how do you get served-agency staff to take part in an exercise they may see as the club's event rather than theirs?

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On message handling, I'd argue the most valuable drill is also the plainest: have several people originate formal messages from scratch, pass them by voice to a relay station, and then compare the delivered text against the original word for word. The errors are usually predictable. Numbers get transposed, names get misspelled, and operators "clean up" the text without realizing they changed the meaning. The check count catches some of these, but not all of them.

One suggestion for net scripts is to build in a deliberate pause after the call for priority or emergency traffic, long enough that a station with a weak signal or a slow microphone can get in. Net control operators who rush through that part can easily miss someone. I'd also keep a separate, simple scratch format for tracking who has checked in, who has traffic, and who is tasked where. Even a basic table on paper beats trying to remember it all, especially when the net runs for hours and control rotates.

For Field Day, a traffic table that handles a few formal messages and a few plain-language welfare messages is a good addition because it exercises both forms. It teaches operators to match the format to the situation instead of using one style for everything.

  • Moderators

The served-agency point is where I'd put the most effort. A frequent gap is that the radio side and the agency side have different assumptions about what a "report" is. The operator thinks they're relaying what they saw, and the agency needs something it can act on, with a location, a time, a source and a level of confidence. Sitting down with the agency before the exercise and agreeing on a short report template can save a lot of confusion later. It also helps to make clear what the volunteer's role is not: operators generally shouldn't be making decisions that belong to agency staff, and a written understanding of who gives direction helps avoid that.

For after-action reports, I'd suggest separating observations from recommendations. Write down what happened in neutral terms first, such as "net control lost contact with the shelter for a period because the repeater was off the air and the simplex fallback wasn't announced." Then write the corrective action: "add the fallback frequency to the net script and the site go-kit card, and test it at the next meeting." That wording is harder to turn into blame and easier to assign.

One more idea for scenario design: include a scheduled communications failure. Take the primary repeater, a key operator or a power source out of play partway through, and see whether the group moves to its backup plan smoothly. If the backup plan only exists on paper, an exercise is a good, low-risk place to find that out.

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.