🚀 go-pugleaf

Chris writes:

> I'm interested in hearing from people involved in SKYWARN groups that
> operate directly under emergency management, fire, or police agencies.
> I'd like to hear how these various groups interface with the NWS and
> ham radio and how they utilize their spotters.

One local EM sponsors our program, another is a board member. These two
EMs and one more provide the three EOCs and the RACES organizations that
staff them. The local association of EMs supports our program by funding
a mailing. The local Warning Coordination Meteorologist and a
forecaster, both hams, attend board meetings.

Operationally, we report directly to the NWS. There are three ARES/RACES
EOCs that rotate net responsibility. A third RACES organization mans an EOC
located at and sponsored by the MPX NWS office. This EOC handles traffic from
the Net Controls to the Lead Forecaster and vice versa. They also will
handle incoming reports from other Skywarn nets outstate as necessary.

Communication between the EOCs and the NWS is maintained primarily via
162 mhz radios. Outstate nets can report via a donated phone conference
bridge or packet. Some of the nearby nets can be accessed directly via
three 2m radios at the NWS EOC. Should there be multiple nets reporting,
all incoming reports may come in via the phone conference bridge which
will be handled like a on-air net. Hopefully, locally produced NWS weather
products will be forwarded to EOCs via packet and email starting this
year.

Metro Skywarn spotters are trained to activate themselves by watching
conditions and listenning to weather reports. Spotters are trained to
place themselves in good locations or spot from home. Placement of spotters
would likely be better, but liability concerns preclude any attempt at
placement. Reports are requested from locally trained spotters. But as
a practical matter, any report can be taken. Reports from non-trained
spotters are verified by trained spotters. This sort of a RACES "Lite"
operation. No codes are used. Two nets are run separately on two
different 2m repeaters. Another repeater will hopefully be linked in to
expand coverage to poorly covered areas. With this set up, we can cover
all but the outer fringes of 11 counties considered part of "Metro".

> [THIS IS NOT A FLAME, JUST MY OPINIONS BASED ON PERSONAL EXPERIENCE]
> With respect to comments about nets being exclusive (like RACES), this can
> be necessary in large meteo areas (like Dallas or Chicago) where there
> already exists a large body of trained spotters.  Further, anyone who has
> controlled a network before knows the frustration involved with talking
> to bad spotters (or people who are not spotters but want to get on the
> net and report what they are seeing because they think they're helping).

Thats why Metro Skywarn is a RACES organization. A local Emergency
Manager sponsors the program and he, the local NWS WCM, and all current
board members want to create an incentive to train every two years and
pass a simple qualifying test. Classes last 3-4 hours. The training
focuses on slides and video chosen to be both entertaining and
informative. The focus is on teaching how to make sense of where the
spotter is in the storm when things get confusing. So the concepts of
inflow and outflow are emphasized as is the need to watch scud. Spotters
are taught what a shelf cloud looks like, especially underneath and what
makes it different than the rainfree base. Some basic concepts about
types of storms, how they approach and where the severe weather occurs
is taught.

> kinds of erroneous things.  The most common problems are gross
> over-estimation of wind speeds, under-estimation of distances, and
> confusion/panic over ugly cloud  features.

We request reports of only wind damage: greater than 3 inch branches
down, roofs pealed back, damaged street signs, all the sort of damage
one would expect from greater than 58 mph winds. Distances are assumed
to be inaccurate and so are not emphasized. See above about confusing
clouds.

We also request only information on flash flooding: moving water, not
severe rain.

> Communication problems rate a close second, however.  If you ever
> do a lot of traveling and listening to other people's nets it's not uncommon
> to hear spotters (especially hams) making very long-winded, needlessly
> over-detailed reports when just a few words would do.  Part of the problem

We use a law enforcement like net procedure. Spotters are asked to check
in with their Skywarn ID number and a one word description of the
condition they wish to report, like wall cloud, hail, etc. That way the
NCO can prioritize when things get busy. Only severe weather reports are
requested. Of course, we get lots of "severe blue sky reports" still,
but we may try calling these spotters after the nets and gently review
procedures with them.

It all works pretty well. There could be more participation if we were
less formal, but the quality of reports would suffer.

Complete details of our program and a dozen others are posted on the
Metro Skywarn Homepage. There are lots of links to spotter education
materials too. I'm always looking for new info and links!

73

Dave Johnson N0KBD    East Bethel, Minnesota    Internet: daveej@winternet.com
 Amprnet: daveej@n0kbd.ampr.org         Packet: n0kbd@wb0gdb.#msp.mn.usa.noam
  Owner WXTALK Email/Pkt Server 145.67Mhz  ftp.winternet.com cd users/daveej/
    Owner of the Metro Skywarn Homepage http://www.winternet.com/~daveej