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.5
Wind 385.0 km/s
Aurora 1
Updated 13: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: which scenario injects actually expose your weak spots?

ci_cover.jpg

Most groups treat the Simulated Emergency Test and Field Day as events to get through: check in, make contacts, send a few messages, eat, go home. Both can work as real rehearsal for disaster communication if you design them that way. I'd like to compare notes on how to do that, because the scenario design seems to matter more than the radio gear.

A few ideas for injects that stress the parts of a response that tend to break first. These are generic planning ideas, not a report of any particular event.

Hurricane or flood: the served agency's primary links stay up but become saturated, then the problem shifts to shelter status reports, resource requests and welfare traffic. Test whether your net can separate those traffic types without the net control station drowning. Add a mid-exercise change, such as a shelter closing and its population moving, and see how long it takes for the new information to reach everyone who needs it.

Earthquake or tornado: the opening problem is usually damage assessment with very little context. Stations report what they can see, not what the agency needs. An inject that forces someone to rephrase a vague report into a usable one (who, what, where, how many, what is needed) is a good test of discipline.

Wildfire: evacuation zones change, so locations are the weak point. Practice giving locations in a way both the operator and the agency will understand, such as cross streets, named facilities or agreed place names, rather than local shorthand only half your net knows.

Grid failure: no commercial power for a long stretch tests the unglamorous things. Do operators have fuel and battery plans? Do they know how long their station really runs? Does anyone track shift rotation so the same three people aren't on the air for twelve hours?

Field Day is good for these skills if you add a layer. Contacts are not the goal for the emergency-practice side. Consider setting up one station as a mock served-agency position, running a short net on a separate band, or originating formal written messages and tracking them through delivery. Setting up in a park with no mains power already tests deployment, antenna work and logging under mild stress.

The question for everyone: what is the one inject you'd add to an exercise that would most likely make a well-rehearsed group stumble? And how do you decide what goes into the after-action report versus what stays as a quiet note to yourself?

  • Replies 2
  • Views 16
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

I'd put message handling at the top of the list. Many operators are comfortable with voice nets and uncomfortable with writing something down accurately and passing it on exactly as written. A decent test is to have an exercise "agency" hand over several messages of different lengths and priorities, then check what arrives at the destination. Compare the original with the final copy word by word. Differences usually show up in numbers, names and addresses.

For formal traffic, the standard radiogram structure is worth practicing: preamble (number, precedence, station of origin, check, place of origin, time and date), address, text, signature. Precedence matters too. Emergency, priority, welfare and routine are not interchangeable, and in an exercise you can deliberately mix them to see whether net control orders them sensibly. Many served agencies use their own forms, often the ICS 213 general message, so it helps to practice converting between the agency's form and radio traffic without altering the content. Ask the agency which form they actually want before the exercise, not during it.

On served agencies: invite someone from them to write the injects or at least review them. If your scenario doesn't resemble the questions they would really ask, you're practicing for your own exercise rather than their needs. Also, ask them plainly what they do not want from volunteers. Sometimes the most useful finding is a boundary, such as who is authorized to speak to the media or who decides when a shelter is full.

  • Administrators

On the net side, a script is useful as a checklist, not a performance. A solid one covers the net opening (purpose, frequency, who is control), a clear way to call for emergency or priority traffic first, a routine for check-ins that doesn't take twenty minutes, a procedure for handing off net control, and closing instructions. The hand-off piece is worth testing explicitly. Many nets run smoothly right up to the moment the first net control operator is tired, and then discover that the log, the open-traffic list and the station roster are all in one person's head.

For the after-action report, I'd keep the structure plain: objectives, what was planned, what actually happened, what worked, what didn't, and corrective actions with an owner for each. The owner part is what separates a report people read from one that sits in a folder. Try to describe problems as system issues rather than personal ones. "Net control had no way to track outstanding messages" leads to a fix; "operator X was slow" does not.

As for what goes in the report versus a private note, one rule of thumb: if the problem could recur with a different operator in the chair, put it in the report. If it was a one-off, such as a dropped coax connector, fix it and log it briefly.

One more inject worth trying is a deliberate loss of the primary frequency, repeater or power source partway through, with the alternate plan written down beforehand. It shows whether people know the fallback or only know that one exists.

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.