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 are you actually practicing, and how do you write it up?

ci_cover.jpg

Most clubs treat the Simulated Emergency Test and Field Day as annual events. Both can be better practice for disaster communication if you decide beforehand which skills you want to test. Contacts logged and band points earned are not the same as served-agency readiness.

Field Day is good for power, antennas, setup speed, logging, operating in poor conditions and working as a team. It says little about message handling unless you add that on purpose. A simple way is to have the station captain or a "served agency" volunteer hand out a few written messages in ICS-213 or radiogram format and require that they be sent, received, copied, and delivered. Check them for accuracy at the end. Common errors include a wrong check count, a missing addressee phone number, and text that was paraphrased instead of sent as written.

SET is the better place to test the net structure. A solid net script covers the following:

  • Opening: purpose of the net, who is in control, and how to check in.
  • Check-in order: emergency or priority traffic first, then stations with traffic, then stations without, then general check-ins.
  • Traffic handling: who is assigned to relay, which frequency or mode the relay moves to, and how delivery is confirmed.
  • Relief: a backup net control and a plan for shift change.
  • Closing: a final traffic call, thanks, and the next scheduled net.

A script is only useful if the people running it have read it before the exercise starts.

Different scenarios stress different things. A hurricane is a long-duration event with fuel, rest rotation, shelter communications and welfare traffic. A wildfire changes quickly, can take out repeaters and power, and creates evacuation and shelter traffic. A flood tests access, gauge or road-closure reports and moving between sites. An earthquake can take down telephone, cell and repeater infrastructure at the same time, which tests simplex and initial damage reporting. A tornado is short-fuse, so activation speed and spotter reporting matter, with damage assessment afterward. A prolonged grid failure tests batteries, generator logistics and how long repeaters and cell sites can stay up.

When you write the after-action report, keep it plain. State the objectives, what was planned, what happened, what worked, what didn't, and corrective actions with a named owner and a due date. A hot wash right after the exercise, while memories are fresh, helps. An after-action report that lists problems but assigns no owners tends to repeat the same problems next year.

Working with served agencies is the other half. Learn what they need: for example, an emergency management office may want situational reports in a certain format, while a shelter may need supply requests and welfare lists. Use plain language with them instead of Q-signals or club slang, and follow their chain of command. Do not self-deploy unless your agreement says you can.

So what do you build into your exercises beyond making contacts? What has been hardest to test realistically?

  • Replies 2
  • Views 21
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

One thing I'd add is to test failure on purpose. Pick a point in the exercise where the primary repeater is declared "down", the net control station's power is lost, or the main logging computer is unavailable. Then see whether people actually switch to the backup frequency, a simplex plan, or paper logs without being prompted. A plan on paper is easy to approve. A plan that survives a mid-exercise disruption is the one worth knowing about.

On message handling, I'd keep a small set of practice messages that range from simple to awkward: numbers, unusual place names, a long text, a message with the wrong addressee format. Ask the receiving operator to read it back, and compare the received copy to the original. Phonetics and the check count catch most errors, but only if people use them.

  • Moderators

For the served-agency side, the most useful exercise is often a short tabletop before any radio is keyed. Sit down with the agency contact and ask what information they would want in the first hour, who is authorized to send requests, and where the operators will physically sit. Misunderstandings about roles tend to show up there, before anyone is standing in a shelter with a handheld.

It also helps to practice writing short, sendable messages. Agency staff often hand over long paragraphs or phone-style requests. A good operator can condense the request into a clear message with who, what, where, how many and how urgent, then confirm it with the originator before sending. Doing that in an exercise builds the habit.

I'd also keep the after-action report brief and easy to share. A one-page summary with three to five corrective actions will get read. A long report might not.

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.