atrainguy
Member
Damage pic of the house is from Marbury, AL.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Probably many little factors. I'm kindve upset with the SPCs choices of risk areas and such though, maybe it was hard to see maybe not. I had mentioned last night that maybe long track supercells need to be looked into and that the event might over perform just based off last night's data. It was clear at 12 hours out before this morning that there was more potential than what SPC said. It put many at risk. My niece and nephews school was barely missed north of Montgomery from that tornado from my guess lack of forewarning and communication of actual threat.This system had a very strong cold pool. I think that may have been one the driving forces behind some of the violent long track tornadoes we saw today.
Yes at least they did nail down the location. There was risk and it overperformed. We need to figure out why.This event overperformed., but it seemed like the core of the severe weather was over the center of the enhanced risk. The enhanced risk should have been farther westward a bit.
Huh? Those photos just show some tree damage and debris. There’s nothing in them indicative of any specific intensity, other than the fact that there isn’t any major debarking.Close to ef 4 damage if not ef4
Lol NWS uses tree damage as a indicator you can get a gist by a picture of the tree damage. Snapping of trees etc.Huh? Those photos just show some tree damage and debris. There’s nothing in them indicative of any specific intensity, other than the fact that there isn’t any debarking.
Yeah but that isn’t what EF4 tree damage looks like. Not even close.Lol NWS uses tree damage as a indicator you can get a gist by a picture of the tree damage. Snapping of trees etc.
I thought debarking happened at ef4. Hmm lol my bad.Yeah but that isn’t what EF4 tree damage looks like. Not even close.
The lack of debarking means EF3 would be as high as they could go.
That gets addressed in the next EF revision. No real standards on it right now but it usually receives consideration.Doesn't it rely on the different type of trees though as well?
So far no deaths reported.