ⓘ 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 Practice
Most clubs and ARES/emergency communications groups run some version of the Simulated Emergency Test and Field Day every year. The question is whether those events actually change how the group performs when something real happens. It is easy to treat both as a checkbox: make contacts, pass a few practice messages, take a photo, go home. Here are some ideas for getting more out of them, and I'd like to hear what others have changed.
Start with Field Day. It is a contest-style event, so it rewards contact count, not disaster skills. But it still gives you a lot of practice if you add a few deliberate goals. Set up fast, under a time limit, with whatever the group would realistically carry. Run on generator, battery or solar for at least part of it. Rotate people into positions they don't normally hold. Use it to test antennas you'd need when the tower is down, and see who can actually build, tune and troubleshoot them. Put a message-handling table in the plan, even a small one, so someone is originating, relaying and delivering formal traffic while the rest are working stations. The "free" bonus points for a formal NTS-style message are an easy hook.
For SET, the biggest difference comes from the scenario. Instead of a generic "disaster happens, check in," try a specific one tied to local hazards: a river gauge climbing and two bridges closing, a wildfire forcing evacuation of a ridge where a repeater site sits, a hurricane landfall followed by a long period of no commercial power, an earthquake that jams the phone network with welfare inquiries, a tornado path that cuts a hospital's normal connectivity, or a multi-day grid failure where fuel and battery logistics matter more than the initial response. Each one stresses something different. Floods and fires stress mobility and changing locations. Hurricanes and grid failures stress endurance, shift changes and power. Earthquakes and tornadoes stress rapid damage reporting and the flood of welfare traffic.
Then there are the net scripts. A good script is short enough that a net control operator can follow it under stress and clear about priorities: emergency or priority traffic first, then agency-requested stations, then routine check-ins. Include the basics: purpose of the net, how to check in, how to identify (legal call sign at the required intervals, with a tactical call sign as the working label), and how to break in with urgent traffic. Does your script work if the net control operator is replaced halfway through? Does it work on a repeater, on simplex, on HF and on a digital mode? Those are different nets with different habits.
On message handling, practice the difference between a radiogram and what your served agency actually uses. Many agencies expect something like an ICS-213 general message or their own form. Radiogram format, with its precedence, handling instructions, station of origin, check, place of origin, time and date, address, text and signature, is still excellent for formal relay and for making sure nothing is garbled. But the useful skill is moving content accurately from one format to another without changing the meaning.
Finally, the after-action report. What does yours look like, and does anyone read it a month later? Please share templates, scenario ideas and the things you wish you had tested sooner.
Most clubs and ARES/emergency communications groups run some version of the Simulated Emergency Test and Field Day every year. The question is whether those events actually change how the group performs when something real happens. It is easy to treat both as a checkbox: make contacts, pass a few practice messages, take a photo, go home. Here are some ideas for getting more out of them, and I'd like to hear what others have changed.
Start with Field Day. It is a contest-style event, so it rewards contact count, not disaster skills. But it still gives you a lot of practice if you add a few deliberate goals. Set up fast, under a time limit, with whatever the group would realistically carry. Run on generator, battery or solar for at least part of it. Rotate people into positions they don't normally hold. Use it to test antennas you'd need when the tower is down, and see who can actually build, tune and troubleshoot them. Put a message-handling table in the plan, even a small one, so someone is originating, relaying and delivering formal traffic while the rest are working stations. The "free" bonus points for a formal NTS-style message are an easy hook.
For SET, the biggest difference comes from the scenario. Instead of a generic "disaster happens, check in," try a specific one tied to local hazards: a river gauge climbing and two bridges closing, a wildfire forcing evacuation of a ridge where a repeater site sits, a hurricane landfall followed by a long period of no commercial power, an earthquake that jams the phone network with welfare inquiries, a tornado path that cuts a hospital's normal connectivity, or a multi-day grid failure where fuel and battery logistics matter more than the initial response. Each one stresses something different. Floods and fires stress mobility and changing locations. Hurricanes and grid failures stress endurance, shift changes and power. Earthquakes and tornadoes stress rapid damage reporting and the flood of welfare traffic.
Then there are the net scripts. A good script is short enough that a net control operator can follow it under stress and clear about priorities: emergency or priority traffic first, then agency-requested stations, then routine check-ins. Include the basics: purpose of the net, how to check in, how to identify (legal call sign at the required intervals, with a tactical call sign as the working label), and how to break in with urgent traffic. Does your script work if the net control operator is replaced halfway through? Does it work on a repeater, on simplex, on HF and on a digital mode? Those are different nets with different habits.
On message handling, practice the difference between a radiogram and what your served agency actually uses. Many agencies expect something like an ICS-213 general message or their own form. Radiogram format, with its precedence, handling instructions, station of origin, check, place of origin, time and date, address, text and signature, is still excellent for formal relay and for making sure nothing is garbled. But the useful skill is moving content accurately from one format to another without changing the meaning.
Finally, the after-action report. What does yours look like, and does anyone read it a month later? Please share templates, scenario ideas and the things you wish you had tested sooner.
Link to comment
https://www.hamradiobase.com/forums/topic/10825-making-set-and-field-day-count-turning-exercises-into-real-disaster-comms-practice/Share on other sites