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: scenario design, net scripts, message handling and honest after-action reports

ci_cover.jpg

Most clubs run Field Day and the Simulated Emergency Test (SET) and walk away with a log, a few photos and a general feeling that it went fine. That feeling isn't much use when a real event hits. This thread is for swapping ideas on turning those events into practice that exposes weak spots while the stakes are still low.

Start with the scenario. "Hurricane" is too vague to drive anything. Pick the specific failures it causes: commercial power is out for days, cell sites are on battery and then go dark, the repeater site is on generator with limited fuel, and the EOC wants shelter status every few hours. Each hazard stresses different things. Floods cut roads, so you may need to relocate operators and pre-position them. Wildfires move fast, force evacuations of your own members, and fill the air with traffic from agencies that are not yours. Earthquakes mean damage assessment, welfare inquiries, and the question of which of your own antennas and repeaters are still standing. Tornadoes are short and sharp, so the practice is mostly spotter coordination and fast, clean reporting. A long grid failure is the slow one, and it tests shift schedules, fuel, batteries and operator fatigue more than any single radio skill.

Field Day is good practice for some things and poor for others. It teaches fast, portable setup, power management, antenna work in bad conditions, and working as a team under time pressure. It does not teach message handling, agency liaison or disciplined net operation unless you add those on purpose. Consider building a short side exercise into the weekend: a station that does nothing but originate, relay and deliver formal messages, or a mock served-agency request that arrives mid-event and has to be answered with a short report. Even something small, like losing the main generator or a key operator at a set time, shows how well your plan survives a surprise.

Net scripts deserve more attention than they usually get. A good script is short enough to read under stress and written so that a substitute net control can run it cold. Useful elements include a clear opening that states the purpose and whether the net is directed, a call for emergency or priority traffic before anything else, check-in categories (for example, stations with traffic, stations at served-agency locations, mobile or portable, general), a plan for how traffic gets passed, and a closing with the next scheduled net time. Practice the handoff to a relief net control, and practice a net where the primary repeater is declared unavailable and everyone moves to a simplex or backup plan. A script that has never been used with a backup frequency is a script with an untested assumption.

On message handling, there are two lanes worth drilling. Formal radiogram format (preamble with message number, precedence, station of origin, check, place of origin, time and date, then address, text and signature) is the NTS standard and works well for traffic that has to move through several hands without being altered. Agency forms like the ICS 213 General Message are what many served agencies actually hand you. Operators should know how to take an ICS 213 and, when needed, convert its content to radiogram form or pass it verbatim, and should know which one the agency expects. Practice precedence too: emergency, priority, welfare and routine are not interchangeable, and treating every message as urgent buries the ones that matter. Watch for the common failure points, which are word counts that do not match the check, abbreviations the receiver does not understand, and unclear signatures or addressees.

Served agencies are the part clubs most often leave to the last minute. Find out in advance what each agency wants from you and in what form: who is authorized to request support, where operators report, what identification they need, what the agency's own communications already cover, and who the point of contact is when you arrive. Invite the agency to take part in the exercise, even in a limited way, and ask them to write a realistic request instead of a polite hypothetical. Their feedback on what was useful and what was noise is worth more than your own log.

Finally, the after-action report. Keep it plain and specific. Record what the objectives were, what actually happened, what worked, what did not, and what will be changed, with a named owner and a date for each fix. Separate observations from opinions. "The net took twelve minutes to pass four messages" is more useful than "traffic handling was slow." Include equipment failures, gaps in the roster, and any confusion about who was in charge. Then, at the next exercise, check whether last time's items were actually fixed.

What have you built into your SET or Field Day plans that exposed something uncomfortable? And how do you handle the tension between formal message formats and the plain language that agencies often prefer?

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the formal-versus-plain question, it helps to treat the format as a tool for the path rather than a rule for its own sake. If a message is going to cross several relays, or sit in a queue before delivery, the radiogram structure protects it: the check catches dropped words, and the numbering lets people refer to it unambiguously. If it is a short request inside a single shelter-to-EOC link, a clean ICS 213 read out in plain language with a readback is often faster and less error-prone.

What I'd drill is the readback habit regardless of format. Names, numbers, street addresses and quantities should be repeated back, and phonetics should be used for anything that could be misheard. Plain language also means avoiding Q-signals and ham shorthand when talking to non-hams on the other end. A good exercise injects a deliberately messy message, such as one with a long street name, a medication list or a count of cots, and sees how many stations get it right the first time.

  • Moderators

One thing that makes after-action reports more honest is deciding the success criteria before the exercise. If the goal is "establish contact with the EOC from every shelter within thirty minutes of activation," you can measure it afterward. If the goal is "practice emergency communications," everything counts as a success.

It also helps to design a few planned problems tied to the hazard you chose. For a flood scenario, that might be a shelter that must relocate and re-establish contact from a new location. For a grid failure scenario, it might be a repeater that goes to a backup power source and then is declared down, so everyone must shift to the simplex plan. For an earthquake scenario, it might be a flood of welfare inquiries that has to be triaged against actual priority traffic. Afterward, write down not just what failed but why it was not caught earlier: was it a missing document, an untrained operator, or an assumption nobody had checked? That second question is where the real improvements come from.

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.