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 test what actually breaks: scenario design, message handling and after-action notes

ci_cover.jpg

Most of us treat the Simulated Emergency Test and Field Day as annual checkboxes, but they can be good rehearsals if we design them around the failures that tend to show up in real events. A drill where every station checks in, passes two tidy messages and goes home tells you very little. A drill that forces a handoff, a shift change, a lost repeater or an unclear request tells you a lot.

One way to start is to ask what each hazard stresses. Hurricanes tend to be long-duration problems: fuel, power, operator fatigue, shift rotation and comms with shelters or EOCs after infrastructure is damaged. Wildfires are fast-changing, with evacuations, lost repeater sites and shifting needs for resource and welfare traffic. Floods raise access problems and the question of whether your operators can reach the assignment at all. Earthquakes are no-notice events where you may have to assume phones and internet are unreliable, and where health-and-welfare traffic can swamp a net. Tornadoes are usually short and sharp, so the practice is mostly about spotter-style reporting and clean, brief traffic. Grid failures are a good test of whether repeaters, served-agency sites and your own stations can run on backup power for longer than the battery rating you remember.

That suggests the exercise should not just say 'there is an emergency.' Write a short scenario with injects on a timeline: a repeater goes offline, a shelter requests a resupply message, an agency wants a formal message sent to another county, a net control operator has to be replaced mid-exercise. Then see how the net handles it.

Field Day is a different kind of practice. It is a contest-style event, so it will not test served-agency coordination unless you add that on purpose. What it does well is power, antennas, setup speed, logging and operating under less-than-ideal conditions. If you want more from it, consider adding a message-handling table or a mock agency request so people practice both skills in the same weekend.

Questions for the group: how do you build injects without making the exercise unrealistic? What do you measure, and what ends up in your after-action report? And how much do you rely on a written net script versus letting net control adapt?

  • Replies 2
  • Views 21
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Message handling is where I would put the most effort, because it is easy to look good on voice checks and still fail at accurate traffic. A radiogram has a defined structure: a preamble (message number, precedence, handling instructions if any, station of origin, check, place of origin, time and date filed), then the address, text and signature. The check is the word count of the text, which gives the receiving station a basic way to notice if something was dropped. Practicing that discipline is worth it even if your served agency never asks for a radiogram, because it trains people to read slowly, spell tricky words phonetically and confirm what they received.

Where served agencies are concerned, find out what format they actually want. Many agencies use the ICS-213 General Message form, so a good drill might hand an operator an ICS-213 and make them send it by voice or digital mode to another site without rewriting it. Operators should not paraphrase or 'improve' the agency's message. If the wording is unclear, they ask the originator, not guess. Also, check in advance whether the agency prefers plain language or tactical call signs, and avoid assuming they use the same code set you do. Plain language is usually safer when a mixed group of responders is involved.

For the injects, I would include at least one message with a deliberately ambiguous detail, such as a street name or quantity, to see whether the receiving operator asks for a repeat or just writes something down.

  • Moderators

On the after-action side, the hardest part is capturing information while it is happening. If you wait until the debrief, people remember the dramatic moments and forget the small friction points. Give net control and a couple of observers a simple log with times: when the scenario inject was delivered, when it was acknowledged, when the message was delivered to its destination, and anything that caused a delay. A short list of 'what went well, what did not, what we will change, who owns the change' is usually more useful than a long narrative.

For net scripts, keep the script short enough that net control can actually use it under pressure. A workable skeleton might be: opening statement and purpose of the net, call for emergency or priority traffic, roll call by area or assignment, call for health-and-welfare or routine traffic, announcements, and closing with time and next check-in. Add a line at the top for the frequency plan and alternates, because that is the first thing people forget when the primary fails. Rehearse switching to the alternate during the drill instead of only listing it on paper.

For Field Day as practice, try a few small additions: run part of the event on battery or generator only, check that go-kits have what the checklist claims, and rotate people into roles they do not usually fill, like net control, logger or message handler. The point is not to turn a contest weekend into a formal exercise, just to leave with a few concrete things to fix before the next real activation.

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.