I was actually wondering that too. A few NWS offices really seem to have gotten sloppy in the last year or two. It is a damned if they do, damned if they don't situation - too much crying wolf has led to people getting killed in the past, but obviously they don't want to be too conservative and not warn a supercell that actually does produce a tornado, either. The 6/7/16 Eureka, KS tornado was violent (causing near-EF4 damage in extremely rural areas), but there wasn't even a watch issued.Yeah, they don't look that impressive. I wonder if NWS Memphis is just forgetting to add "capable of" in front of "producing"
Normally if the tornado is a radar confirmed, the warning will say that there is a debris signature.
wow you have a direct line with them. ImpressiveAlright, I asked NWS Memphis if the tornado warned storms over north MS were producing tornadoes and they said:
"The rotation is radar indicated, which prompted the warning. We have not had confirmation of a tornado on the ground with these storms."
So obviously the warning text was messed up.
NEXRAD radars have different modes. When the radar measures a lot of reflectivity (i.e. storms, rain, etc.) it switches to precipitation mode. Precipitation mode is sensitive and so it can pick up a lot of false return, and that false return can mess with the radar picking up winds.what do u mean
The NWS in Huntsville is saying that the radar data is in an area obscured due to Trees. It is causing issues with the radar data but the storms should be moving out of that area soon.Precipitation mode is really screwing with the velocity on the Columbus AFB radar.
Yeah, that's probably issue rather than precipitation mode. I forgot that there is an issue with trees around that radar site.The NWS in Huntsville is saying that the radar data is in an area obscured due to Trees. It is causing issues with the radar data but the storms should be moving out of that area soon.