• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

MPX Metro Skywarn Net Meltdown

  • Thread starter Thread starter MattKaskavitch
  • Start date Start date
I too was monitoring the net traffic that evening and felt really frustrated by what I heard. More importantly, my wife who is a newly minted member of Skywarn, was listening in too. Her response?

"Why did we go through all that training?"

It's really no secret that this organization has been in a state of "flux" for a couple of years now. With any volunteer organization, you have very passionate individuals that want to guide the organization into the future.

The changes that occurred as a result, ran afoul of some of the long standing volunteer members and I have a feeling may have had an effect on present participation.

And I think the result is what we all heard that evening. An NCO that was clearly in over her head, with little if any apparent support, and multiple lines of storms moving through the area.

And then, the UFO report.

The NCO seemed to be more interested in answering peoples requests for information and at times, clearly did not disseminate information accurately.

And I point the finger squarely at the leaders of the organization for that. The NCO is the most "visible" member of the Skywarn net once it's activated for they "direct" the net activities. Unfortunately, even in a volunteer capacity you need to expect that the NCO has had appropriate training when they accept the position and responsibility.

I guess my wife said it best:

"Why make a report if she's just going to get it wrong?"


Pretty much says it all.
 
I wonder if the hamsexy folks have picked up on the meltdown yet? I still wish there was a recording online somewhere.
 
Back
Top