Many readers aren’t aware that I’m an avid weather enthusiast. I’ve loved mother nature’s fury ever since our home was struck by a tornado when I was a child. I’ve been chasing/spotting severe storms for 10 years total, and 8 years on my own with various chase partners. I’ve chased all over the upper-plains from Wisconsin, Iowa, Minnesota and into the Dakotas. In addition to this life-long obsession, I’ve been an amateur radio operator, or “ham”, for four years. However, I’ve been involved in two-way radio communications and electronics since I was a child. Now I have premised my experience, let me get to the point of this blog!
This evening, a large area of severe weather struck Minnesota, eventually making its way into the Minneapolis/St. Paul area. The Minneapolis/St. Paul Metro SKYWARN swung into action taking check-ins from all over the twin cities metro. What sounded like an older female was acting as net control. This operator is my primary, but not only, criticism.
Coming into this evening, I’ve respected the professionalism and coordination the metro SKYWARN group has. However, now my confidence is shaken. The net control seemed to be lacking the skill set needed for this position. She couldn’t even keep the difference between watch and warning straight. I hope she understood the difference at least and was simply mixing them up. She often repeated “warnings” that did not exist, instead telling operators in outlying counties they had “tornado warnings” when really they were under a “tornado watch”. This happened at least seven times in a one and a half hour span. One time she was corrected by another operator on-air, just once. Otherwise stations simply ask for clarification because what she is saying doesn’t even make sense.
“Washington county under a tornado warning till 11 p.m.” She stated this at 9:15 p.m. for a squall line racing through.
Wait, an hour and forty-five minute tornado warning!?
Then she’d come back on the air 2 minutes later and say a list of counties like, “Washington, Hennepin, Chisago etc. under a tornado watch till 11 p.m.”
2 minutes later…
“The NWS out of Chanhassen has extended the tornado warning until 3 a.m.”
You can see how confusion can then add up and discredit much of the net.
In all this confusion, a local camp ground manager came on the net and asked for clarification. I don’t blame him one bit. He had obviously been tuned in listening to the net and was so twisted by listening to this female net controller, he had no idea what was occurring anymore. He informed net control he had over 100 campers piled into a safe area and wanted to know if a particular tornado warning had expired so he could release his campground from shelter. Instead of an answer, another net control station, possibly an emergency manager, told him in a very condescending and direct way to tune into his “AM/FM radio” for the answer. Are you kidding me? Is this how you treat a completely understandable request? Your net control can’t say hardly anything properly and this guy is overseeing the shelter and campers and your giving him a hard time? There was obvious tension on-air between the campground manager and the net controllers after this spat on the air. I side 110% with the campground manager. If your net controller is announcing watches and warnings over the net, reading statements, then they should be held accountable to provide clarification, and not snarky either.
Later into the evening, a station asked the female net control station where the area of interest was and if she had heard of any rotation in a particular storm. She replied,
“I’m looking at radar now and don’t see any rotation.”
You may ask, what’ s wrong with that? If she can’t distinguish between a watch and warning correctly, do I really trust her to interpret radar? I sure wouldn’t. Is she qualified in the least even as an “amateur radar observer” to know what she’s looking at, and what kind of software is she using?
Then the highlight of the evening. A station ID’d and checked into the net with a report of UFO’s over the metro. I laughed quite hard as this man described lights flying in unison across the sky. He was quite excited and perhaps even a bit liquored up, it was hard to tell. The net controller instructed this station to dial 911 and report the UFO phenomena. This led to another operator coming on-air repeatedly cursing the other operator out calling him a “stupid fuc*” and to “have another fuc*ing drink”. You can see how when your net isn’t properly controlled, things can get out of hand quickly. You can stop anyone from interrupting a net, but you can deter those by having a clean and well executed net.
So what have we learned? It is imperative you have the right person “behind the controls” when you need it most. Tonight’s net controller was obviously not that person and their net was really quite poor. From constant “repeating” of simple information that took up time and created extra traffic, to false information about warnings and watches and everything in-between, the net was a borderline disaster. The bright spot was collecting damage reports. Aside from some problems not being able to transcribe fast enough, most damage reports were handled quite well. One problem spot on damage reports I heard went like this…
“9463 damage…” operator
45 seconds go by
“9463 damage…” operator
“standing water…” net controller
10 seconds go by
“9463 DAMAGEEEEE”
“station all I heard was standing water over roadway”
I ask how in the world do you get “standing water” when the station is clearly stating his SKYWARN ID number and that he has a damage report. I’m not sure what in the world was going on here. Again, confusion.
I’m sorry Metro SKYWARN, I thought you were better than this. I heard bright spots of good, but a wholeeee lot of bad in there tonight. You and I provide a valuable service to the community and there needs to be professionalism through out the process. I know you mean well and I know were all volunteers. I hope you choose to do a debriefing on this net and find where the hiccups are and correct them. I might add a suggestion, look at net control from tonight first and go from there.