ⓘ 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 count: turning exercises into real disaster comms readiness
Most of us agree that exercises matter, but it is easy to run a Simulated Emergency Test or Field Day, log a lot of contacts, and come away without changing anything. I'd like to compare notes on how groups get more out of these events, and on how scenario choice, message handling and served-agency relationships fit together.
Start with the scenario. A hurricane, wildfire, flood, earthquake, tornado outbreak and extended grid failure each stress communications differently. Hurricanes and ice storms give you advance warning, so you can pre-position people and test batteries and generators. Earthquakes and tornadoes give you little or no notice, and the first hour is mostly about who can get on the air with what they have. Wildfires and floods often cut off roads, so the question becomes how you move traffic between shelters, EOCs and field teams when travel is unreliable. A grid failure is probably the most useful baseline, because it forces you to ask what still works with no commercial power: repeaters on backup power, battery capacity, and the HF and VHF/UHF paths that don't depend on the internet.
The second point is that a scenario should be built around a communication problem, not just a headline. "A hurricane hits" doesn't give anyone a job. "The county EOC has lost its primary link to two shelters, and the health department needs a resource request relayed to the state" does. Tie each injected message to a plausible need such as a shelter census, a welfare inquiry, a supply request or a road-status report, and make sure some of it has to cross a net boundary or change modes, say from voice to a written form to digital and back. That is where handling errors show up.
On message handling, Field Day is better practice than it gets credit for, as long as you use it deliberately. The standard exchange is simple, but you can add a formal message element. Many groups send a radiogram to the section manager as part of the bonus points. Use that to practice the format: preamble (message number, precedence, handling instructions, station of origin, check, place of origin, time and date), address, text, and signature. The check is the word count of the text, so counting words carefully and reading back numbers are good habits to build when nothing is at stake. Beyond that, practice taking the same content on an ICS-213 general message form, since many served agencies work in that format rather than in radiogram.
Net scripts deserve more attention than they usually get. A good script is short enough that a net control station under stress will actually use it. It should cover the net's purpose, the call for emergency or priority traffic first, then check-ins by category, then a clear way to assign liaison and relay tasks. It should also say how and when to close or hand off the net. The same script should work for a voice net on a repeater and for a simplex or HF net. Test it with someone who didn't write it, because that reveals any ambiguity quickly.
Then there's the after-action report. The format that seems most useful is the plain one: what was planned, what happened, what went well, what needs improvement, and a specific owner and due date for each fix. Vague findings like "improve coordination" go nowhere. "Two stations used different message numbering and the log couldn't be reconciled" can be fixed with a one-page procedure. Separate observations about people from observations about systems, so the report doesn't turn into a performance review of individual volunteers.
Finally, served agencies. The best exercises involve them directly, even if only as a message originator or an evaluator. Ask them what they want the messages to look like, what they consider a priority, who is authorized to send traffic on their behalf, and what credentials or training they expect, such as ICS courses. Don't assume your assumptions match theirs. Their answers often change the exercise design more than anything on the amateur side.
Questions for the group: What injects have you found expose weak spots fastest? How do you handle the tension between a realistic scenario and giving newer operators a chance to succeed? And what is the one change from an after-action report that actually stuck?
Most of us agree that exercises matter, but it is easy to run a Simulated Emergency Test or Field Day, log a lot of contacts, and come away without changing anything. I'd like to compare notes on how groups get more out of these events, and on how scenario choice, message handling and served-agency relationships fit together.
Start with the scenario. A hurricane, wildfire, flood, earthquake, tornado outbreak and extended grid failure each stress communications differently. Hurricanes and ice storms give you advance warning, so you can pre-position people and test batteries and generators. Earthquakes and tornadoes give you little or no notice, and the first hour is mostly about who can get on the air with what they have. Wildfires and floods often cut off roads, so the question becomes how you move traffic between shelters, EOCs and field teams when travel is unreliable. A grid failure is probably the most useful baseline, because it forces you to ask what still works with no commercial power: repeaters on backup power, battery capacity, and the HF and VHF/UHF paths that don't depend on the internet.
The second point is that a scenario should be built around a communication problem, not just a headline. "A hurricane hits" doesn't give anyone a job. "The county EOC has lost its primary link to two shelters, and the health department needs a resource request relayed to the state" does. Tie each injected message to a plausible need such as a shelter census, a welfare inquiry, a supply request or a road-status report, and make sure some of it has to cross a net boundary or change modes, say from voice to a written form to digital and back. That is where handling errors show up.
On message handling, Field Day is better practice than it gets credit for, as long as you use it deliberately. The standard exchange is simple, but you can add a formal message element. Many groups send a radiogram to the section manager as part of the bonus points. Use that to practice the format: preamble (message number, precedence, handling instructions, station of origin, check, place of origin, time and date), address, text, and signature. The check is the word count of the text, so counting words carefully and reading back numbers are good habits to build when nothing is at stake. Beyond that, practice taking the same content on an ICS-213 general message form, since many served agencies work in that format rather than in radiogram.
Net scripts deserve more attention than they usually get. A good script is short enough that a net control station under stress will actually use it. It should cover the net's purpose, the call for emergency or priority traffic first, then check-ins by category, then a clear way to assign liaison and relay tasks. It should also say how and when to close or hand off the net. The same script should work for a voice net on a repeater and for a simplex or HF net. Test it with someone who didn't write it, because that reveals any ambiguity quickly.
Then there's the after-action report. The format that seems most useful is the plain one: what was planned, what happened, what went well, what needs improvement, and a specific owner and due date for each fix. Vague findings like "improve coordination" go nowhere. "Two stations used different message numbering and the log couldn't be reconciled" can be fixed with a one-page procedure. Separate observations about people from observations about systems, so the report doesn't turn into a performance review of individual volunteers.
Finally, served agencies. The best exercises involve them directly, even if only as a message originator or an evaluator. Ask them what they want the messages to look like, what they consider a priority, who is authorized to send traffic on their behalf, and what credentials or training they expect, such as ICS courses. Don't assume your assumptions match theirs. Their answers often change the exercise design more than anything on the amateur side.
Questions for the group: What injects have you found expose weak spots fastest? How do you handle the tension between a realistic scenario and giving newer operators a chance to succeed? And what is the one change from an after-action report that actually stuck?
Link to comment
https://www.hamradiobase.com/forums/topic/10760-making-set-and-field-day-count-turning-exercises-into-real-disaster-comms-readiness/Share on other sites