• A friendly and periodic reminder of the rules we use for fostering high SNR and quality conversation and interaction at Stormtrack: Forum rules

    P.S. - Nothing specific happened to prompt this message! No one is in trouble, there are no flame wars in effect, nor any inappropriate conversation ongoing. This is being posted sitewide as a casual refresher.

Becoming an Effective Net Control Station

Joined
Jul 17, 2017
Messages
11
Location
United States
I'm interested in becoming a net control station for the local ARES outlet. I don't have the time commitment for the FEMA EmComm courses, but after watching some of K9TSU's videos on YouTube of the Rochelle, IL EF-4, I feel comfortable enough to be able to run a net. There aren't many operators out here, and I've been given the go-ahead by the ARES coordinator to bring up nets should the need arise. Even though I'm only using an HT, I'm a mile from the repeater so line-of-sight isn't an issue.

That said, what are some tips that can be used to effectively run a Skywarn net?

Kyle
 
Lots of ARES/RACES/Skywarn groups have resources online about how they run nets. Here are 2 examples:
http://www.collinares.net/ccares-fog/skywarn
http://www.dallasraces.org/ccrm

It may not be an issue if you only have a few operators, but the biggest problems I see in the DFW area where we have a lot of operators is reports that don't meet minimum criteria. In both of the examples above you will see how the net control sets minimum reporting criteria and the key to being a successful net control is tactfully reminding folks and enforcing it. The reason minimum criteria is set is a net control doesn't need dozens of "me-too" pee sized hail reports that can prevent more urgent reports from making it thru.

If you going to be a net control (or even a mobile spotter). You really need more than an HT. It may work great today, but when all heck breaks lose you may need the extra power.
 
Randy,

I've been net control for the last three years down here in SW Oklahoma for the LIRA group. We have always recommended operators at least attend the spotter training put on by the Norman office every year, but we accept any and all reports from operators in the area or passing through (paging Daniel Shaw).

Over the last three years, it's become clear to me that there are two important factors in running a smooth severe weather net.
1. don't be too rigid, be flexible with reporting criteria, keep it open and inclusive
2. streamline your process of taking reports and relaying to NWS or what ever agencies you plan to serve

On point one, we always allow all operators in the area to check in to the net and participate. It doesn't seem like a good idea to require membership or a certain level of training in order to participate, because you never know ahead of time who might be in position to observe and report what they see. You also never know what chasers/spotters might be in the area for a big event. Those people can provide really great information and bring a ton of experience to the net. Having said that, over time you'll get an idea of which operators give reliable reports and can be counted on to provide accurate and relevant information. Our policy is to take all reports and then try to corroborate them against radar data, NWS guidance, spotter network data, other reports, etc... If it meets the NWS reporting criteria for the particular event, it matches the action in the area and we have some sense of the experience of the operator, we put the report into NWS chat. If it doesn't make sense or is not complete, we either filter it out, ask for more information or provide guidance to the operator on how to make better reports. Just always be respectful and helpful. Remember, most operators are just trying to help out and they don't know what they don't know.

One other note about being flexible about report criteria, if it's not a major event, we'll take everything from rain fall totals to structure reports and general weather nerdery. If there is potential for tornadoes in a storm in our area, we'll limit it to more traditional severe reporting criteria (hail 1" or better, 60MPH wind, wall clouds, funnels, etc...). Just be clear and communicate when it's game time and operators will understand.

On point two, practice, practice, practice. When there is a major event going on, the faster you can provide accurate information to NWS, the better. I wrote some software to make this process really fast for us and we practice with it every week by having a rag chew net. These nets keep my skills sharp, not only in operating the radio, but controlling traffic and recording information into the software. I try to get down as much of what the stations checking into the rag chew nets into our software as possible. This exercises the software and my brain as well as keeping a nice record of all the nets.

Speed and accuracy is the key. If you can get information about reporting stations ahead of time, do that and use it. We have a lot of operators that provide reports from home, we know where they are and confirm that when a net starts so that we don't have to get that information when they provide reports.

That's just a little advice I can give off the top of my head. Good luck!

-stephan kg5icz
 
Randy,

I've been net control for the last three years down here in SW Oklahoma for the LIRA group. We have always recommended operators at least attend the spotter training put on by the Norman office every year, but we accept any and all reports from operators in the area or passing through (paging Daniel Shaw).

Over the last three years, it's become clear to me that there are two important factors in running a smooth severe weather net.
1. don't be too rigid, be flexible with reporting criteria, keep it open and inclusive
2. streamline your process of taking reports and relaying to NWS or what ever agencies you plan to serve

On point one, we always allow all operators in the area to check in to the net and participate. It doesn't seem like a good idea to require membership or a certain level of training in order to participate, because you never know ahead of time who might be in position to observe and report what they see. You also never know what chasers/spotters might be in the area for a big event. Those people can provide really great information and bring a ton of experience to the net. Having said that, over time you'll get an idea of which operators give reliable reports and can be counted on to provide accurate and relevant information. Our policy is to take all reports and then try to corroborate them against radar data, NWS guidance, spotter network data, other reports, etc... If it meets the NWS reporting criteria for the particular event, it matches the action in the area and we have some sense of the experience of the operator, we put the report into NWS chat. If it doesn't make sense or is not complete, we either filter it out, ask for more information or provide guidance to the operator on how to make better reports. Just always be respectful and helpful. Remember, most operators are just trying to help out and they don't know what they don't know.

One other note about being flexible about report criteria, if it's not a major event, we'll take everything from rain fall totals to structure reports and general weather nerdery. If there is potential for tornadoes in a storm in our area, we'll limit it to more traditional severe reporting criteria (hail 1" or better, 60MPH wind, wall clouds, funnels, etc...). Just be clear and communicate when it's game time and operators will understand.

On point two, practice, practice, practice. When there is a major event going on, the faster you can provide accurate information to NWS, the better. I wrote some software to make this process really fast for us and we practice with it every week by having a rag chew net. These nets keep my skills sharp, not only in operating the radio, but controlling traffic and recording information into the software. I try to get down as much of what the stations checking into the rag chew nets into our software as possible. This exercises the software and my brain as well as keeping a nice record of all the nets.

Speed and accuracy is the key. If you can get information about reporting stations ahead of time, do that and use it. We have a lot of operators that provide reports from home, we know where they are and confirm that when a net starts so that we don't have to get that information when they provide reports.

That's just a little advice I can give off the top of my head. Good luck!

-stephan kg5icz

What kind of software is this? I’ve been looking for software of this nature but it doesn’t look like there are any available that fit what I’m looking for.


Sent from my iPhone using Tapatalk
 
Thanks for the link! I’ll be sure to use this. And thanks for the tips. Hopefully I’ll be a decent NCS come severe weather season.


Sent from my iPhone using Tapatalk
 
Lots of ARES/RACES/Skywarn groups have resources online about how they run nets. Here are 2 examples:
SKYWARN - CollinARES
CCRM - Dallas RACES

It may not be an issue if you only have a few operators, but the biggest problems I see in the DFW area where we have a lot of operators is reports that don't meet minimum criteria. In both of the examples above you will see how the net control sets minimum reporting criteria and the key to being a successful net control is tactfully reminding folks and enforcing it. The reason minimum criteria is set is a net control doesn't need dozens of "me-too" pee sized hail reports that can prevent more urgent reports from making it thru.

If you going to be a net control (or even a mobile spotter). You really need more than an HT. It may work great today, but when all heck breaks lose you may need the extra power.

I don't even bother with the local net here.
Too much chatter and not knowing what to report.

I do think they went to the local class, but didn't pay attention and didn't take the online tests required.

Kyle, if you do put up a decent station (antenna and radio for skywarn), i would sure tell any operator calling a report that does not meet criteria for reporting, tell that operator real quick about it.

Yes, it's a hobby. Still not reason to not to run it in a professional manor.
 
I'm interested in becoming a net control station for the local ARES outlet. I don't have the time commitment for the FEMA EmComm courses, but after watching some of K9TSU's videos on YouTube of the Rochelle, IL EF-4, I feel comfortable enough to be able to run a net. There aren't many operators out here, and I've been given the go-ahead by the ARES coordinator to bring up nets should the need arise. Even though I'm only using an HT, I'm a mile from the repeater so line-of-sight isn't an issue.

That said, what are some tips that can be used to effectively run a Skywarn net?

Kyle
My ears were ringing. I'm K9TSU. How did the season go for you?
 
My ears were ringing. I'm K9TSU. How did the season go for you?
Better late than never, I guess, but the season went okay. Didn't get a ton of chances to go out and look, and there was only one severe thunderstorm warning that a net could have been brought up on (although that's not a bad thing). I'm sorry, I thought this thread had died before you replied.
 
Back
Top