Jump to content
  • Member Statistics

    17,611
    Total Members
    7,904
    Most Online
    NH8550
    Newest Member
    NH8550
    Joined

January 10th-12th Winter Storm Potential


Thundersnow12
 Share

Recommended Posts

9 hours ago, Geoboy645 said:

Didn't Madison verify at least once last year? It's weird, I'm only 30 miles NE and I have verified warnings like 3 times since the beginning of last year.

Possibly, but it seems all the expected big dogs last winter (including the one at the end of April, lol) verified on the low end of expected totals.

  • Like 1
Link to comment
Share on other sites

Storm total at DTW was 2.56" and 0.3" snow.  That is a 48 hour total from approximately 4:00 a.m. January 10 to 4:00 a.m. January 12, however the brunt of the storm was January 11th. The calendar day rainfall on January 11th was 2.06", largest on record for any day in January, and this was exactly 2 months to the day after we set our largest November calendar day snowfall for any day at 8.5". 

 

Everything is iced over now with a fresh coating of snow. I too received 0.3" of snow at the end however my final precipitation total is estimated as my rain gauge is literally frozen to its stand and I cannot get it to budge to melt the remaining inside (my running total was 2.32 at 5pm yest).

Link to comment
Share on other sites

Locally the models did respectively well. The highlights were bright skys followed by a wall of wind with dark clouds. Temps dropping 13deg F in a near instant. A few minutes later, a nice flash of lighting with a good clap of thunder while rain poured. Flash freeze this AM. The amount of standing water today is actually very impressive. Such a waste of a moisture plume, imagine if that was all snow.

  • Like 2
Link to comment
Share on other sites

Several of the NWS offices, including mine, have done good post mortems on this event along with what went wrong in the forecast.

 

I'll try to address the various parts that the forecast didn't work out (or worked out okay but differently). I think convection played a noteworthy role in wreaking havoc throughout the forecast. It's likely too simplistic to focus on this factor alone, but I think helps hit the main ideas of what went wrong.

 

This event was essentially impossible to forecast well from a professional meteorologist perspective because the moving parts were constantly changing even in the shorter ranges when RAOBS typically help build the consensus. We rightly guessed that convection may ultimately modulate what happened.

 

There were a few "hunch" posts made about how the cold side of the system would be lackluster, and how Friday night would be primarily rain. Those were good calls clearly. Much of my forecast analysis generally didn't work out too well with the exception of holding onto idea of surface low tracking farther southeast for various reasons, including convection modifying mass fields. But hopefully was still informative for the meteorology beyond this event.

 

Friday Night Precip:

We had an unusually convectively active front for January along the inverted trough axis, due to the extreme warmth and moisture under the amplified southeast ridge. In more spring-like setups of this nature, we often look to areas within relatively close proximity to the boundary for the highest rainfall totals due to higher instability and getting the convective rates. It's common for precip to be less than forecast well up on the cold side of the boundary and the precip amount gradient usually ends up sharper than forecast. This is largely what happened, the heavy amounts of 2-3" verified but confined closer to the front in the southeast 1/3 of the LOT CWA.

 

The sharper cutoff northwest due to moisture transport robbing led to an earlier end to round 1 of precip and less snow and ice than earlier forecasts. That said, in the NWS, we never forecast the extreme ice amounts some of the models like the NAM kept showing with good reasoning to support why we didn't. That part of the forecast worked out, but then the earlier end and narrower zone of freezing temps still resulted in forecast ice accums in northwest CWA being overdone.

 

Saturday daytime and Saturday evening:

As of the Wednesday night/early Thursday model runs, the models had trended hard toward the 500 mb wave becoming negatively tilted and supporting a deepening 990s mb surface low lifting north-northeast. This is when I discussed potential similarities to the December 28, 2015 event and possibility of significant sleet amounts.

 

I think a good case can be made that Friday night's convection helped assure a completely separate round 1 precip by: development of multiple competing sfc low centers and delayed deepening of the system as main wave stayed positive tilt for longer. As a result most of the daylight hours Saturday were devoid of steady precip (except for the odd LES under the warm layer into NE IL), precluding any sig ice, sleet and snow accums as cold press from north deepened.

 

On Saturday PM, there was finally a respectable area of backside/deformation snows with the finally deepening mid-level trough streaming toward the area. Models had hinted at this and it seemed we'd finally get a solid period of snow. However, at the same time, an extensive intense squall line developed over the lower OH valley down to near the Gulf Coast. Despite the support for heavy precip rates that were expected to accompany the Saturday evening snow, it seems likely that the convection had to play at least some role in the deformation precip getting shredded like it did.

 

What part of the forecast did work out:

The lakeshore flooding forecast: based off reports, photos, and videos of impacts, likely the most significant lakeshore flood episode since the Feb 87 event, surpassing Halloween 2014 due to near record high lake levels. Calumet Harbor lake level gauge came within 1" of the all time record.

 

If anything, the lakeshore flooding was more significant, with inundation noted a few blocks inland in the South Shore neighborhood. We now have a good baseline for future higher end events in this near record high lake level regime.

 

Final Thoughts:

Based off the available ingredients for the system, the more significant potential outcomes were reasonable forecasts given the preponderance of the data at hand. One could probably have found ensemble members that mirrored the actual outcome, but those were thought to be outliers at the time. As NWS MKX showed in their what went wrong graphic, the snowfall ended up close to the 10th percentile of the ensemble distribution.

 

Perhaps we could have done more to collaboratively (with WPC and surrounding WFOs) tighten up the rain forecasts based on conceptual model of a convectively active front, and forecast a smaller footprint off of the charts extreme amounts for January. That would've helped produce better river forecasts.

 

As for the winter side, once to headline phase, it's tougher to couch things with as much uncertainty, despite the inherent challenges with this forecast. I'm not sure we could've totally avoided a bust in this regard, aside from playing things a bit more conservatively because of the possibility that downstream convection would destructively interfere with the setup.

 

Have to say this too, that when the typically most reliable model and ensemble, the ECMWF struggles this mightily for an event, it does affect the quality of the forecasts. No model did extremely well, some less bad than others, namely the UKMET and GFS.

 

Despite the failures and frustrations, it's an interesting case to study and learn from for the future to do better next time. Sorry for this being so long, but thank you if you did take the time to read through it.

 

 

 

 

  • Like 9
  • Thanks 2
Link to comment
Share on other sites

^

Fantastic read. Not necessary, as we here all know how difficult it is to forecast, but certainly therapeutic to reevaluate how a system evolved and what caused a forecast to not unfold as anticipated. In my laymen's terms....we got screwed Saturday night from a 3-5 " fall by a transient squall line. In the end, we all took it on the shin with this one. Also, certainly more eloquent and disproves ALEK's "rainer" call. ;) Posts like this show why these boards can be extremely relevant and educational. Thanks, again. 

  • Like 2
Link to comment
Share on other sites

2 hours ago, RCNYILWX said:

Several of the NWS offices, including mine, have done good post mortems on this event along with what went wrong in the forecast.

I'll try to address the various parts that the forecast didn't work out (or worked out okay but differently). I think convection played a noteworthy role in wreaking havoc throughout the forecast. It's likely too simplistic to focus on this factor alone, but I think helps hit the main ideas of what went wrong.

This event was essentially impossible to forecast well from a professional meteorologist perspective because the moving parts were constantly changing even in the shorter ranges when RAOBS typically help build the consensus. We rightly guessed that convection may ultimately modulate what happened.

There were a few "hunch" posts made about how the cold side of the system would be lackluster, and how Friday night would be primarily rain. Those were good calls clearly. My forecast analysis generally didn't work out, but hopefully was still informative for the meteorology beyond this event.

Friday Night Precip:
We had a very convectively active front for January along the inverted trough axis, due to the extreme warmth and moisture under the amplified southeast ridge. In more spring-like setups of this nature, we often look to areas within relatively close proximity to the boundary for the highest rainfall totals due to higher instability and getting the convective rates. It's common for precip to be less than forecast well up on the cold side of the boundary and the precip amount gradient usually ends up sharper than forecast. This is largely what happened, the heavy amounts of 2-3" verified but confined closer to the front in the southeast 1/3 of the LOT CWA.

The sharper cutoff northwest due to moisture robbing led to an earlier end to round 1 of precip and less snow and ice than earlier forecasts. That said, in the NWS, we never forecast the extreme ice amounts some of the models like the NAM kept showing with good reasoning to support why we didn't. That part of the forecast worked out, but then the earlier end and narrower zone of freezing temps still resulted in forecast ice accums in northwest CWA being overdone.

Saturday daytime and Saturday evening:
As of the Wednesday night/early Thursday model runs, the models had trended hard toward the 500 mb wave becoming negatively tilted and supporting a deepening 990s mb surface low lifting north-northeast. This is when I discussed potential similarities to the December 28 2015 event and possibility of significant sleet amounts.

I think a good case can be made that Friday night's convection helped assure a completely separate round 1 precip by: development of multiple competing sfc low centers and delayed deepening of the system as main wave stayed positive tilt for longer. As a result most of the daylight hours Saturday were devoid of steady precip (except for the odd LES under the warm layer into NE IL), precluding any sig ice, sleet and snow accums as cold press from north deepened.

On Saturday PM, there was finally a respectable area of backside/deformation snows with the finally deepening mid-level trough streaming toward the area. Models had hinted at this and it seemed we'd finally get a solid period of snow. However, at the same time, an extensive intense squall line developed over the lower OH valley down to near the Gulf Coast. Despite the support for heavy precip rates that were expected to accompany the Saturday evening snow, it seems likely that the convection had to play at least some role in the deformation precip getting shredded like it did.

What part of the forecast did work out:
The lakeshore flooding forecast: based off reports, photos, and videos of impacts, likely the most significant lakeshore flood episode since the Feb 87 event, surpassing Halloween 2014 due to near record high lake levels. Calumet Harbor lake level gauge came within 1" of the all time record.

If anything, the lakeshore flooding was more significant, with inundation noted a few blocks inland in the South Shore neighborhood. We now have a good baseline for future higher end events in this near record high lake level regime.

Final Thoughts:
Based off the available ingredients for the system, the more significant potential outcomes were reasonable forecasts given the preponderance of the data at hand. One could probably have found ensemble members that mirrored the actual outcome, but those were thought to be outliers at the time. As NWS MKX showed in their what went wrong graphic, the snowfall ended up close to the 10th percentile of the ensemble distribution.

Perhaps we could have done more to collaboratively (with WPC and surrounding WFOs) tighten up the rain forecasts based on conceptual model of a convectively active front, and forecast a smaller footprint off of the charts extreme amounts for January. That would've helped produce better river forecasts.

As for the winter side, once to headline phase, it's tougher to couch things with as much uncertainty, despite the inherent challenges with this forecast. I'm not sure we could've totally avoided a bust in this regard, aside from playing things a bit more conservatively because of the possibility that downstream convection would destructively interfere with the setup.

Have to say this too, that when the typically most reliable model and ensemble, the ECMWF struggles mightily for an event, it does affect the quality of the forecasts. No model did extremely well, some less bad than others.

Despite the failures and frustrations, it's an interesting case to study and learn from for the future to do better next time. Sorry for this being so long, but thank you if you did take the time to read through it.



Sent from my SM-G965U using Tapatalk
 

quoted for a new page so it doesn't get lost, very nice recap

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...