Dispatcher Fired Over Tornado Siren Delay
- Thread starter Adam Reagan
- Start date
Rob H
EF5
You have to dig into the previous story that this was a follow up from before you find out the reason:
The SPC reports for 7/26 don't list anyone as being injured, but reports had 2x4s as missiles - so it must have been a decently powerful tornado. Glad to hear this error didn't result in anyone's harm.
The SPC reports for 7/26 don't list anyone as being injured, but reports had 2x4s as missiles - so it must have been a decently powerful tornado. Glad to hear this error didn't result in anyone's harm.
Mike Smith
They need WeatherData's SelectWarn® system. It prompts the dispatcher so he/she only needs to respond with one click of the mouse. For siren systems that allow individual sirens to be triggered, it sounds them only in the polygon and a locally selectable buffer around the polygon.
www.weatherdata.com/products/selectwarn.pdf
www.weatherdata.com/products/selectwarn.pdf
Think Sedgwick Co could use this system. One of these days a large tornado is going to come barreling through some part of town there and kill a bunch of people b/c people are so used to the damn sirens going off for a warning in any part of the county. And quite frankly I cant say I blame them for half ignoring the sirens with them being a countywide system and not broken off into sections.
*shakes head*
Adam Reagan
EF2
It was an EF1 tornado that touched down between North Nashville and Goodlettsville in the Belshire community from a renegade cell that quickly got it's act together.
You're right it is very fortunate no one got hurt I was watching live coverage of the storm on local TV and nothing was mentioned about sirens till after the second tornado warning was issued for Downtown Nashville.
Similar threads
