A wet start to the weekend this Friday with multiple rounds of rain moving through. Saturday shapes up to be a better day at least in terms of being dry. A second disturbance/low moves through Sunday bringing yet more chances for rain before skies clear up to start next week. Temperatures behind this second storm/cold front will be below normal for this time of year.
Rest of today – periods of rain during the afternoon as a warm front works its way across the area. Some thunderstorms possible. Second round of more focused/heavier rain later in the evening around 7-8PM as a trailing cold front pushes through. This front will have decent upper level support with some indications of a vorticity maxima at 500 mb and us being in the exit region of a 300 mb jet streak. High temperatures today topping out around the upper-50s even with the rain as we’re expected some time in the warm sector of the low bringing us this stormy weather. If the warm front below fails to push north through here though, we may only see temps in the mid-50s. Overnight lows should bottom out around 50°F.
Saturday – with the trailing cold front clearing the area tonight, precipitation should end and Saturday should end up being a decent day though with more clouds than sun. High temperatures should be able to get into the low-60s, edging into the mid-60s if more sun breaks out. Overnight lows noticeably cooler with a colder, drier airmass behind today’s cold front, in the mid-40s.
Sunday – a second low approaches from the Ohio Valley, again bringing some potential for rain. This rain is expected to be on the lighter side. Temperatures should reach into the upper-50s. Overnight lows in the low-40s.
Monnday – start of next week should be sunny, with Sunday’s storm system moving offshore. High temperatures will be below normal though, with the cold front associated with Sunday’s low bringing a reinforcing shot of cooler air. High temperatures probably topping out in the upper-50s. Overnight lows in the mid-40s.
A winter storm warning is in effect for NYC and the surrounding metropolitan region. This isn’t exactly how we’d all want to start March off! This storm is anticipated to bring some travel impacts to the area, however, for reasons discussed below, this won’t be a blockbuster snowmaker. Watch out for a slog of a morning commute tomorrow. This snow may also stick for a while – a frigid continental polar air mass from Canada will sweep in behind this storm bringing temperatures generally 10-15°F below normal for this time of year. High temperatures in the mid-30s should limit melting.
Headlines
Snowfall totals: I’m forecasting 4-6″ in parts of eastern Queens, southeastern Brooklyn, and lower totals further east into Long Island. Higher totals of 6-8″ are more likely to occur in Manhattan, the Bronx, and points further inland, particularly interior regions of Connecticut. Below are probabilistic forecast maps of various amounts of snow (>= 2″, >= 6″, and >= 8″).
Timing: Precipitation starting in earnest around 8PM. Starting out as a mix of rain/snow near the coast, but transitioning over to all snow later in the evening. The heaviest snow will happen overnight. Because of the fast-moving nature of this storm, precipitation is expected to end rather quickly between 4-6AM Monday morning in the city.
Uncertainties: There is still potential for a wobble in the storm track, further east and south would result in higher snow totals near the coast. Further west and closer to the coast would mean more mixing/rain at the coast and lower snow totals. There will be a rather sharp gradient of increasing snowfall totals spreading across the region (as seen in the previous probabilistic snowfall total forecasts). Mesoscale heavy snow bands will be difficult to pinpoint ahead of time. Some areas could see several inches more than neighboring areas just a few miles south and east.
Synoptic Set Up (The Big Picture)
A storm that’s currently unleashing severe storms with tornadoes across the Deep South now will slide up along the Mid-Atlantic and Northeastern coast of the US. As this storm progresses, it will move close to the 40°N/70°W benchmark, a spot that’s climatologically correlated to heavy snow events along the heavily populated I-95 corridor during the winter. This storm will continue to strengthen as it moves offshore. Snow is expected to develop ahead of the advancing warm front associated with this storm as its precipitation shield advances. Heavier snow is forecast to develop later on as strong isentropic lift associated with the warm front occurs, creating the potential for frontogenesis and some mesoscale bands of very heavy snow. The storm is expected to move quickly along the Northeast coast, such that the duration of precipitation in any one spot is expected to be less than 12 hours.
At the 500 mb level, a shortwave trough will provide positive vorticity and some additional lift/divergence, allowing the storm to continue strengthening. Finally, at the 300 mb level, the surface low will be close to the entrance region of a curved 300 mb jet streak. This will provide yet more divergence and lift, if only for a brief period.
Evolution of the Storm Track
Over the course of the last three days, forecast models have come into better agreement with this storm tracking close to the 40°N/70°W benchmark (circled in red in the images below). Note the increasingly tight clustering of storm center locations around the benchmark in progressive storm track forecasts from the Weather Prediction Center.
The tightening clustering of these forecast storm center locations lends greater confidence to the idea that the storm will track very close to the benchmark.
Ensemble Snowfall Totals
The two primary model ensembles (GEFS and SREF) have been edging ever so slightly upwards in their forecast mean snowfall totals, while the model spread has decreased over the weekend
These means/spreads were part of what informed my own forecast snowfall totals at the top of this post.
Factors Supporting Heavy Snow
Storm track over or very near the benchmark
Strong isentropic lift and possible frontogenesis (see images below). Strong lift is a critical ingredient for generating heavy precipitation
Possibility of mesoscale bands as a result of this lift, generating heavy snowfall rates
Temperatures probably supporting frozen precipitation through the atmosphere
Factors Suggesting Lower Snow Totals
Possibility still remains for storm track to shift further inland, introducing more warm air off the ocean, more rain than snow at the coast
Warm advection associated with the storm’s warm front possibly also affecting snow development. Note how close the overlapping temperature and dew point profiles in the forecast soundings above are to the freezing mark, the dashed blue line the middle of the image that is angled to the right at 45°. Evaporational cooling should help somewhat in staving off warming but if temperatures warm more than forecast, we could see more mixing
Mesoscale bands of heavy snow may not push far enough onshore
Surface temperatures ahead of the storm in the upper-30s near the coast, urban heat island effect could retard snow accumulation
Fast moving nature of the storm, total precipitation window only 12 hours
Small window for the best moisture support at the 850 mb level. No real evidence to suggest a low-level jet carrying a ton of moisture into the region.
For reference, here’s the post that triggered the following forecast post-mortem analysis. To start, here’s my forecast and the verified totals.
My Forecast High: 48°F | Low: 17°F | Max sustained winds: 35 mph | Total QPF: 1.40″ | Total snow accumulation: 1.00″
Verification High: 40°F | Low: 15°F | Max sustained wind: 38 mph | Total precipitation: 0.80″ | Total snow: 0.00″
Since I did decently at forecasting maximum sustained winds and the low temperature, this analysis will focus primarily on why I missed the mark on both total precipitation and the high temperature.
How I Verify Forecasts I haven’t explained in previous posts like this how I go about verifying the results of my own forecasts, though I do talk about METARs (hourly weather reports) and daily climate summaries from the National Weather Service as sources for verification data. There’s a reason why I choose to use the 06Z Day 1 to 06Z Day 2 (1AM/2AM Day 1 to 1AM/2AM Day 2 depending on Daylight Saving Time) time window to forecast, and that’s because this lines up well with METAR synoptic reports that occur every 6 hours (00Z, 06Z, 12Z, 18Z). This is something I picked up from my Weather Forecasting Certificate Program at Penn State World Campus. So, when I’m looking at the METAR data, I’m looking for specific data points at these synoptic times:
I won’t bore you with details of how to read METARs, which you can learn about here, but from these entries, I can get the maximum temperature from the highest value 1 group, low temperature from the lowest 2 group, and total precipitation from summing up the 6 groups for these synoptic times. So in this case, “10044” indicates a maximum temperature of 4.4C, which is converted from 40F. “21094” shows a minimum temperature of -9.4C, converted from -15F. “60060” translates to 0.60″ and “60020” likewise is 0.20″, and the sum gives us 0.80″ total precipitation.
Last, with max sustained wind, and in this case snow, I checked the NWS daily climate reports for LGA (see red outlined boxes).
Post-Mortem Analysis On this forecast, I ended up handling the low temperature and max sustained winds well, however, I was much too high on both the high temperature and total precipitation. So what happened here?
High Temperature In my forecast, I had confidence based on various model data that NYC would spend a decent amount of time in the warm sector of the low that would be responsible for the storm. Unfortunately, this simply just did not happen, and as a result, we never got into that warm southerly/southwesterly flow that would have propelled temperatures into the upper-40s. Instead, looking at the METARs for that day reveals that winds stayed consistently east-northeast to north-northeast overnight into the early morning hours before almost immediately shifting to the northwest by 11AM. This makes sense, given the orientation and location of the warm front just to our south to start.
Click the images below to see the Weather Prediction Center’s surface analyses at 7AM, 10AM, 1PM respectively for Sunday, January 20.
In the end, I should have heeded some signals that there was enough uncertainty in the storm track even on Saturday that we could miss the warm sector. The local forecast office for the NWS also indicated that there was a potential for this, which would keep temperatures suppressed due to persistent, cool, northeasterly flow. Their forecast high, which I believe was 42°F, factored this in, and ended up being a lot more accurate. The takeaway here for me is to not completely buy into model consensus even if there’s good agreement, when there’s a possibility of storm tracks shifting. I don’t think I would have gone as low as 40°F even with this in mind, but I might have forecast something like 44°F, which would have been closer.
Total Precipitation I missed the total precipitation forecast by more than 0.50″ – objectively a bad outcome. In this case, I think there were a couple reasons behind my own forecast bust. First, the storm progressed faster than data on Saturday suggested, resulting in heavier precipitation earlier in the overnight period, also meaning that the strongest frontogenesis/isentropic lift moved through quicker than anticipated. Secondly, the best moisture convergence stayed just offshore, leading us to miss out on some of the heavier rain.
Click the images below for enlarged versions of the archived radar image for 8AM Sunday, January 20, and the Storm Prediction Center’s moisture convergence analysis for the same time.
The fact that we never ended up in the warm sector for too long during the day Sunday also meant that the best moisture didn’t quite make it up to NYC. Note how the areas of strongest moisture convergence are also coincide well with the most intense radar echos. For precipitation with strong storms like this, it can always be a hit-or-miss proposition to pinpoint precipitation totals for one spot. My own personal forecast bias leads me to over forecast precipitation quite often. I should have consulted the daily average for precipitation to factor climatology into this as well before doing the forecast. For reference, the record precipitation total for KLGA on January 20th was 1.41″ – so I was, in essence, forecasting a near record-breaking precipitation event. That usually doesn’t pan out, as you see.