ⓘ 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 — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Making SET and Field Day Scenarios Expose Real Weak Points Before a Disaster Does
Many emergency communication exercises go smoothly because they were designed to go smoothly. Everyone checks in on the usual repeater, the net script runs in order, a few messages get passed, and the after-action discussion is mostly "that went well." That feels good, but it tells you little about how the group would cope when the repeater site has lost power, the served agency wants something you did not plan for, and half the roster is unavailable.
I'd like to compare notes on how to build scenarios that stress the right things. Here is a starting framework, and I'd like to hear where it breaks down.
Start with the hazard, then work out the communication failure it causes. A hurricane suggests long-duration power loss, damaged infrastructure, shelter support, and welfare traffic. A wildfire suggests evacuations, shifting road closures, smoke, and communications from remote or mountainous terrain. Floods raise questions about access, shelter locations, and which bridges your operators can still cross. Earthquakes and tornadoes tend to be sudden and local, so the early problem is often getting a few trained people to a few key places quickly. A grid failure tests whether your "backup" really is a backup. Each hazard breaks different links, so the same exercise run every year will keep testing the same assumptions.
Inject failures instead of announcing them. Rather than telling the group "the primary repeater is down," have net control simply stop using it, or make it unavailable partway through. Do the operators know the fallback, whether that is simplex, a second repeater, or an HF path? Can they get there without being walked through it? The same goes for a served-agency liaison who is "unreachable" or a station that has to hand off its role in the middle of the exercise.
Use the Simulated Emergency Test as a test, not a demonstration. The ARRL's SET is typically run on a local or section basis, which gives you room to tailor it. Some elements worth building in:
Messages that must be formatted, passed, and delivered to a real or role-played recipient, not just read over the air.
At least one message that needs clarification, so operators have to ask for a repeat or a verification instead of guessing.
A tactical-call setup (for example, location- or function-based names) so people practice using them instead of personal call signs, with legal station identification still handled properly.
A shift change, so logs, open messages, and net status have to be handed over in writing.
A resource-request message that requires a reply, so you see how well the loop closes.
Treat the net script as a living document. A good script covers the preamble, the purpose and scope of the net, priority or emergency traffic calls first, then check-ins by category, then routine traffic and a clear close. It is much more useful if it also has short decision prompts: what to do if net control is lost, how to hand off, when to move to a different frequency, and who can authorize that. If your script only works when the person who wrote it is running the net, it needs another pass.
Write the after-action report while it's fresh. A format that works well for small groups is: what we intended to test, what actually happened, why it happened, what to sustain, and what to change, with a named owner and a date for each change. Specific observations ("three stations did not know the fallback frequency") are more useful than general conclusions ("communication could be better"). Include a note on what the served agency actually needed, since that may differ from what you assumed.
Which failure injects have taught your groups the most, and which ones turned out to be too artificial to be worth the trouble?
Many emergency communication exercises go smoothly because they were designed to go smoothly. Everyone checks in on the usual repeater, the net script runs in order, a few messages get passed, and the after-action discussion is mostly "that went well." That feels good, but it tells you little about how the group would cope when the repeater site has lost power, the served agency wants something you did not plan for, and half the roster is unavailable.
I'd like to compare notes on how to build scenarios that stress the right things. Here is a starting framework, and I'd like to hear where it breaks down.
Start with the hazard, then work out the communication failure it causes. A hurricane suggests long-duration power loss, damaged infrastructure, shelter support, and welfare traffic. A wildfire suggests evacuations, shifting road closures, smoke, and communications from remote or mountainous terrain. Floods raise questions about access, shelter locations, and which bridges your operators can still cross. Earthquakes and tornadoes tend to be sudden and local, so the early problem is often getting a few trained people to a few key places quickly. A grid failure tests whether your "backup" really is a backup. Each hazard breaks different links, so the same exercise run every year will keep testing the same assumptions.
Inject failures instead of announcing them. Rather than telling the group "the primary repeater is down," have net control simply stop using it, or make it unavailable partway through. Do the operators know the fallback, whether that is simplex, a second repeater, or an HF path? Can they get there without being walked through it? The same goes for a served-agency liaison who is "unreachable" or a station that has to hand off its role in the middle of the exercise.
Use the Simulated Emergency Test as a test, not a demonstration. The ARRL's SET is typically run on a local or section basis, which gives you room to tailor it. Some elements worth building in:
Treat the net script as a living document. A good script covers the preamble, the purpose and scope of the net, priority or emergency traffic calls first, then check-ins by category, then routine traffic and a clear close. It is much more useful if it also has short decision prompts: what to do if net control is lost, how to hand off, when to move to a different frequency, and who can authorize that. If your script only works when the person who wrote it is running the net, it needs another pass.
Write the after-action report while it's fresh. A format that works well for small groups is: what we intended to test, what actually happened, why it happened, what to sustain, and what to change, with a named owner and a date for each change. Specific observations ("three stations did not know the fallback frequency") are more useful than general conclusions ("communication could be better"). Include a note on what the served agency actually needed, since that may differ from what you assumed.
Which failure injects have taught your groups the most, and which ones turned out to be too artificial to be worth the trouble?
Link to comment
https://www.hamradiobase.com/forums/topic/11498-making-set-and-field-day-scenarios-expose-real-weak-points-before-a-disaster-does/Share on other sites