ⓘ 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
Turning Field Day and SET into real disaster comms practice: what are you actually testing?
Field Day and the Simulated Emergency Test are the two events most clubs already have on the calendar. Both are often run as contests or social events with an emergency label on them. That's not a criticism, since Field Day is a good chance to get stations and antennas up. But if the goal is to be useful when a hurricane, flood, or grid failure takes out normal communications, a few small changes can turn the same weekend into much better practice.
Start with one question: what is the one thing we want to find out this time? "Can we make contacts?" is too vague. Better examples: Can we pass a formatted message from a shelter to the EOC in under 20 minutes? Can we run for eight hours on batteries and generator without a gap in coverage? Can a new operator take a net control shift with only a script and a printed frequency plan? A narrow objective makes the after-action report much easier to write.
Scenario choice matters too, because each hazard stresses a different part of the system. Hurricanes and ice storms mean long outages and fuel logistics, and operators are often affected themselves. Floods and wildfires tend to cut off roads and force evacuations, so you may need to relocate stations while keeping the net running. Earthquakes put the focus on damage assessment and the first hours, when repeaters and commercial networks may be overloaded or down. Tornadoes are fast and local, so spotter reports, SKYWARN-style coordination, and post-event welfare traffic matter most. A widespread grid failure tests everything on your own power, including repeater sites, which have limited backup runtime.
Injects are what make an exercise feel real. Instead of just running a net, hand the net control station a small stack of scenario messages at planned times: a shelter requesting cots, a hospital reporting a generator problem, a request for a licensed operator at a new location, a repeater site on battery with an estimated time remaining. Then change a condition midstream. Declare the primary repeater unavailable, or tell a station its antenna is down. How people adapt shows you more than a smooth run does.
For message handling, make people use the actual forms. A radiogram has a number, precedence, handling instructions if needed, station of origin, check (word count), place of origin, time and date filed, addressee, text, and signature. Served agencies often prefer their own format, such as an ICS 213 General Message, so practice both and know how to move text between them without changing its meaning. Keep a log, such as an ICS 309 communications log or a simple net log, so every message can be tracked as received, relayed, delivered, or undeliverable.
Finally, write it down while it's fresh. A one-page after-action report is enough: objective, what happened, what worked, what didn't, and two or three specific changes with names and dates attached. A report that says "communication could be better" gets filed and forgotten. One that says "the check count was wrong on four of nine messages; we will run a 15-minute message drill at the next meeting" actually gets used.
What have other clubs and ARES/RACES groups built into their SET or Field Day plans that made them more than a routine operating event? And what tends to get skipped, even though everyone knows it matters?
Field Day and the Simulated Emergency Test are the two events most clubs already have on the calendar. Both are often run as contests or social events with an emergency label on them. That's not a criticism, since Field Day is a good chance to get stations and antennas up. But if the goal is to be useful when a hurricane, flood, or grid failure takes out normal communications, a few small changes can turn the same weekend into much better practice.
Start with one question: what is the one thing we want to find out this time? "Can we make contacts?" is too vague. Better examples: Can we pass a formatted message from a shelter to the EOC in under 20 minutes? Can we run for eight hours on batteries and generator without a gap in coverage? Can a new operator take a net control shift with only a script and a printed frequency plan? A narrow objective makes the after-action report much easier to write.
Scenario choice matters too, because each hazard stresses a different part of the system. Hurricanes and ice storms mean long outages and fuel logistics, and operators are often affected themselves. Floods and wildfires tend to cut off roads and force evacuations, so you may need to relocate stations while keeping the net running. Earthquakes put the focus on damage assessment and the first hours, when repeaters and commercial networks may be overloaded or down. Tornadoes are fast and local, so spotter reports, SKYWARN-style coordination, and post-event welfare traffic matter most. A widespread grid failure tests everything on your own power, including repeater sites, which have limited backup runtime.
Injects are what make an exercise feel real. Instead of just running a net, hand the net control station a small stack of scenario messages at planned times: a shelter requesting cots, a hospital reporting a generator problem, a request for a licensed operator at a new location, a repeater site on battery with an estimated time remaining. Then change a condition midstream. Declare the primary repeater unavailable, or tell a station its antenna is down. How people adapt shows you more than a smooth run does.
For message handling, make people use the actual forms. A radiogram has a number, precedence, handling instructions if needed, station of origin, check (word count), place of origin, time and date filed, addressee, text, and signature. Served agencies often prefer their own format, such as an ICS 213 General Message, so practice both and know how to move text between them without changing its meaning. Keep a log, such as an ICS 309 communications log or a simple net log, so every message can be tracked as received, relayed, delivered, or undeliverable.
Finally, write it down while it's fresh. A one-page after-action report is enough: objective, what happened, what worked, what didn't, and two or three specific changes with names and dates attached. A report that says "communication could be better" gets filed and forgotten. One that says "the check count was wrong on four of nine messages; we will run a 15-minute message drill at the next meeting" actually gets used.
What have other clubs and ARES/RACES groups built into their SET or Field Day plans that made them more than a routine operating event? And what tends to get skipped, even though everyone knows it matters?
Link to comment
https://www.hamradiobase.com/forums/topic/11157-turning-field-day-and-set-into-real-disaster-comms-practice-what-are-you-actually-testing/Share on other sites