Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
weathe r
Last year, we got to 200 pages.
Now, we're going for 15. We can do this!
2017 was probably the most boring year for severe weather and tornadoes since 2009 (I've heard some people say 2009 was worse but I only started following severe weather around January/February 2014 so I can't confirm). I wouldn't even say this year is as bad as 2017.I can only imagine how bad 2017 was. This year has had 3 moderate risks significantly underperform (so far...). 2017 had that but instead of Moderate they were HIGH.
Agreed. Also, this forum is heavily focused on Alabama/Southern States. If this were centered on Columbus, MS then you'd have a lot more people involved in the lead up.given the track-record of this year's tornado-driven moderates I can understand why people aren't champing at the bit
weathe r
If there happens to be many favorable mergers that grow into one healthy supercell, then that LCL/updraft size won't matter. All we need is one supercell to utilise that intense tornado threat. I feel like that scenario is the most likely. If I'm correct, temps rising higher create a better cap/inversion of sorts to prevent crapvection, right?Late spring thermos are no joke, especially when there’s a strong LLJ involved, temps have already climbed to the 80s immediately southwest of the MCS.
Something tells me surface scraping LFC limiting updraft size won’t verify so easily.
View attachment 53229
weathe r
That’s the thing though, when your individual updraft size is too small, combine with extremely high shear, it’s very difficult to get a descent sized storm even with mergers.If there happens to be many favorable mergers that grow into one healthy supercell, then that LCL/updraft size won't matter. All we need is one supercell to utilise that intense tornado threat. I feel like that scenario is the most likely. If I'm correct, temps rising higher create a better cap/inversion of sorts to prevent crapvection, right?

I don't like taking these runs as gospel but considering the HRRR is modeling the MCS better in recent runs, this isn't a great sig now that it's modeling convection better. Peak intensity is 140-160 on my method,for todayThat’s the thing though, when your individual updraft size is too small, combine with extremely high shear, it’s very difficult to get a descent sized storm even with mergers.
But alas, at this point im really not seeing a surface scraping LFC verifying anymore.
The latest hrrr run reflects this as it has multiple beefy updrafts which are actually able to take advantage of the parameter space, and well… it speaks for itself.
View attachment 53230
The crazy thing about 2017 is that the 1/22/2017 set-up checked just about every box you’d want to see checked for a major outbreak. That wasn’t the case with the other two high risk days that year (still have no idea what they were thinking with the 4/5 high risk specifically). Yet, we really only saw one supercell do anything of note that day which was the very long-track EF-3 that impacted Albany, GA.2017 was probably the most boring year for severe weather and tornadoes since 2009 (I've heard some people say 2009 was worse but I only started following severe weather around January/February 2014 so I can't confirm). I wouldn't even say this year is as bad as 2017.
not happy with two straight days of 30% wind probs though.I guess we're also in a slight risk here today, most of the DMV is still in D1/D2 drought so I wouldn't say no to some rain.
I lost power yesterday and I was only in a TSTM risk. Funnot happy with two straight days of 30% wind probs though.
Last year I lost power twice. One of them was 5/16, which was a 15%.
It's not even severe warned anymore. This is the beginning of our event. Whether we reach the ceiling some models have said remains to be seen but i see something in the middle today.Has my Radarscope just gone dumb or are there no longer any warnings on the MCS?
Has my Radarscope just gone dumb or are there no longer any warnings on the MCS?