An Active Start to 2024

January Began and Ended With Unusual Severe Weather Across the Forecast Area.

2023 was an unusual year for severe weather across the Columbia, SC forecast area, with significant breaks in the action in our normal active season (Spring and early Summer). However, 2024 has rocketed off to a very fast start.

January 9th Severe Weather and Wind

A remarkably well forecast and intense, large scale system developed across the eastern CONUS in the days leading up to January 9th. Ensemble guidance as early as a week in advance began to hint at a series of systems developing and impacting us during the second week of January. This was expected to culminate in a more significant system on January 9th across the eastern US.

The GFS (along with other guidance) was picking up on the magnitude of this system 7-8 days in advance. On the left, you have the GFS forecast from January 2nd; on the right, what was initialized on January 9th. Slide right or left to see the difference between the two images. Source: Colorado State

Given the well-forecast nature of the system, the national and local centers all began to message the system days in advance. This was a multi-hazard system, with intense non-thunderstorm winds expected, along with a strong line of severe thunderstorms pushing through with the front. Ensembles were consistently signaling one of the most intense wind events we have seen locally in years, which added confidence to the system occurring.

The ECMWF EFI is a tool that we use internally to find areas of opportunity in the long range forecast. Values >0.7 indicate unusual weather, and values >0.9 indicate potential for extreme weather. The Signal for wind gusts on Jan 9th is one of the more impressive signals that we have seen locally in our time using this product. h/t ECMWF

The meteorology behind this system was fascinating as an intense upper level trough dug into the western US, taking on a negative tilt as it approached the eastern 1/3rd of the CONUS.

300 mb heights and winds and divergence. Source: SPC.

This overspread the OH and TN Valleys with intense upper level divergence, which caused rapid lift across a large area of the country. When divergence aloft develops, it creates a deficit in air where it overspreads. This causes winds at lower levels in the atmosphere to fill the void, lowering pressure more and causing stronger winds as a result.

This is certainly reflected when looking at mid-level and low-level heights and winds, where we had 500 mb winds over 100 mph and 850 mb winds over 90 mph. This created an extremely favorable wind shear environment across the area, fostering a potential line of strong to severe storms. Additionally, an intense low-pressure system developed in the Mid-Mississippi Valley and pushed into the Great Lakes Region by the overnight hours. A secondary low developed along the lee side of the Appalachians through the day. The combination of rapid surface pressure falls across our area led to intense non-thunderstorm wind gusts that approached 60 mph.

500 mb heights/winds, 850 mb heights/winds/dewpoints, and mean sea level pressure on January 9th. The wind field being as intense as it was fostered intense winds and severe weather. Source: SPC.

The big question with this event was not whether or not we would have non-thunderstorm wind gusts. It was really whether we would get just enough instability to foster severe thunderstorms. There was significant forcing for lift from the large scale system, which likely offset the need for significant CAPE. The uncertainty didn't preclude the SPC from having an excellent forecast several days in advance.

SPC outlooks from Day 5 to Day 1 (left to right). This severe weather event was very well anticipated and forecast. Source: SPC

RAP Reanalysis sounding from 1/9/24 at 2p revealed a sufficiently unstable environment with significant lift and extremely anomalous low-level wind shear. Reanalysis sounding made via the SounderPy program.

As the day approached, hi-res guidance showed increasing chances that we would destabilize enough to support severe convection given the wind fields and lift along the front. The intense wind fields allowed moisture to advect into the region, creating enough destabilization to yield strong wind gusts and isolated tornadoes within the squall line. The line pushed through the area beginning late morning and cleared the eastern part of the forecast area by mid-afternoon. This produced widespread wind damage across the area, in addition to two tornadoes.

The radar loop of the event as it pushed through the area between 1130a and 5p. Radar data visualized through GRAnalyst.

This event was impactful and interesting from a meteorological perspective. For starters, we had multiple tornadoes produced by this line, in addition to strong wind gusts with the line. More unusual than that is the constant wind gusts near or above 50 mph preceding the line due to the strong pressure gradient. Even more unusual than that? CAE saw its 3rd largest drop in surface pressure over a 24h period, only behind The "Storm of the Century" in 1993 and Hurricane Hugo.

From left to right: the info and track of the Lake Murray & Bamberg tornadoes, the SPC Storm reports from 1/9, a plot from Iowa Environmental Mesonet showing the largest 24 hour pressure falls in the history of CAE, and the highest recorded wind gusts from the day.

The Bamberg tornado was brief and strong, striking downtown Bamberg directly during the early afternoon hours. Rated EF2, it quickly pushed through the city and caused significant damage to the downtown areas. Thankfully, there were no injuries!

Bamberg County Tornado Video courtesy Anthony Hurley

The radar loop of the Bamberg tornado as it pushed through. Visualized using GR Analyst.

All in all, this was a really impactful way to begin the new year.

January 27 Tornadoes and Supercells

We will go from one of the better forecasts by models in recent memory to one that was a real struggle for forecast guidance to pick up on until right before the event itself. The January 27 severe weather event was unique, including the development of multiple classic supercells that pushed across the region.

500 mb heights, winds, and temperatures between 10a and 10p on Jan 27. The trough took on a negative tilt as the day went along, providing more lift by the evening. Source: SPC.

The setup was a weaker version of one we have seen multiple times this winter already, with a 500 mb shortwave trough pushing into the Mid-MS Valley and OH Valley through the day, gradually taking on a negative tilt. Wind fields were not nearly as impressive as they were with the January 9th system, which will play a role in the kind of storms and severe weather we had this day.

850 mb heights, winds, temperature, and dewpoints. Winds in the 15-30 knot range aren't typical for winter severe weather locally, but high dewpoints help yield anomalous instability. Source: SPC

The lack of strong upper-level winds did lead to weaker winds as a whole in the lower portion of the atmosphere, with 850 mb flow generally 15-30 knots during the day, which is much weaker than we see with typical winter time severe weather systems.

We had been very warm in the days preceding this, and with few fronts pushing through, rich moisture was able to build in advance of this system.

The surface warm front was a critical feature in this event, creating an area of enhanced low-level shear for supercells to thrive along. Source: SPC.

The combination of anomalously high 850 hPa dewpoints, surface dewpoints in the low to mid-60s, and some breaks in the clouds allowing temps to rise to near 70F led to fairly significant instability being realized south of the front. This is especially true when you put it in the context of this being a January event!

MLCAPE, 3km CAPE, and a RAP Reanalysis Sounding just south of Columbia. Considering the time of year, this level of instability is more than sufficient to support supercells. Source: SPC, SounderPy

As unusual as this is, the biggest question was the quality of the wind shear present. The day saw multiple supercells at different parts of the day, with the earlier storms being well ahead of the best deep layer shear and forcing. And this bears itself out when you look at the RAP analysis that day, or even the sounding above! Wind shear profiles were very poor anywhere not right next to the warm front. And luckily for us, the warm front was sitting directly over or near the radar that day. This gave us a good look into what the vertical wind profile looked like in the vicinity of the front.

KCAE Vertical Wind Profile (VWP) hodograph at 239p and 340p. The second image is closest to the time of the Elgin tornado, revealing more than sufficient low-level helicity. Use the slider bar to compare the two images. Source: Autumn Sky

This wind profile is much different than the wind profile in the RAP sounding (taken in the warm sector) above, revealing the impact that the warm front had on the storm intensity and organization. This also explains why these storms didn't do anything other than produce tornadoes (3 weak, brief tornadoes each in the vicinity of the warm front) - deep layer shear was weak, with almost all of it confined to the lowest 1km.

The storms really struggled to get going until they got within a certain distance of the surface warm front. Several supercells developed within enhanced shear and instability. Source: UCAR Radar Archive

Elgin Tornado & Supercell

The first tornado of the day was associated with a supercell that slowly organized over an hour before interacting with the warm front. It began to ingest much better low-level shear as it approached the Columbia Metro area, organizing into a supercell in central Lexington County. About 1 hour later, it produced a brief, EF1 tornado near Elgin SC.

The storm slowly developed a mesocyclone as it progressed through Lexington & Richland Counties, strengthening enough by the time it approached Elgin that it produced a weak tornado. The low-level shear environment was favorable enough near the warm front to yield actual tornadogenesis. Radar visualized through GRAnalyst software.

Stats on the Elgin tornado.

This supercell was the first of several to develop and move across the forecast area on January 27th, and produced one of 3 brief tornadoes from this day.

Lexington County Supercell

While this storm followed quickly behind the Elgin storm, it did not produce a tornado. However, that doesn't mean it wasn't a strong storm in its own right. The storm was on the southern end of a cluster of storms that began to intensify once interacting with the warm front draped across the central Midlands. ZDR (differential reflectivity - helps differentiate between precipitation particle size and shape) is a very useful radar parameter and can reveal where very intense updrafts are before reflections of high radar reflectivity materialize. In this storm, a ZDR column had formed and extended above the -20C line in the atmosphere - indicating a very strong updraft, even while reflectivity was only high below 20,000 feet.

The ZDR column can reveal where strong updrafts are. Swipe to see a comparison of the ZDR vs the regular reflectivity. The storm was not very impressive at this point, as the updraft had just shot up. (Radar visualized through GRAnalyst software.)

A radar loop of the storm as it pushed through Lexington County. It had a deep and persistent mesocyclone but didn't produce a tornado like the Elgin storm did. (Radar visualized through GRAnalyst software.)

The updraft acquired extra low-level shear and became a mesocyclone as it pushed into the greater Lexington area. This storm was so close to the radar, that it proved pretty difficult to get good radar scans on it at lower elevations. We normally like to look at much lower scans like 0.5 degrees and 0.9 degrees for these storms, but because of the proximity to the radar, looking higher up in the storm was the best way to see its true structure. The radar loop on the right is from radar scans at the 3.1-degree tilt, meaning the storm was being sampled between 1800' and 3600', losing some of the clutter that the lowest scans are impacted by. As it moved over the populated areas of Lexington and Richland counties, it yielded some incredible pictures.

Whoa Nelly Racing on Twitter

Billy Bowling on Twitter

Billy Bowling on Twitter

An image one of our meteorologists took of the storm as it passed west and north of the office. The wall cloud is discernable just above the airport, with the rotating updraft tilting northeastward due to the effects of shear. A radar image around the time of this picture is shown in the bottom right, with the classic 'Hook-Echo' signature outlined in white.

So...why did this storm have similar characteristics to the Elgin storm but not produce a tornado? Well, as we found out after the event, the low-level air was way too stable due to widespread rain that had preceded this and pushed the warm front just a bit too far south. This stability was marked by reports of ground fog in central Lexington County. What all of this means is that the storm wasn't able to lift enough air in the updraft to successfully yield tornadogenesis, and thus it was just another unusual and pretty storm!

Saluda County Tornadoes

As the parent upper-level trough slowly worked its way toward the forecast area, it brought a bit more forcing toward the area. As an area of decaying prefrontal convection pushed into Georgia, instability developed ahead of it. With an increase in forcing & instability, thunderstorms developed within the previously decaying area of showers. As these storms were closer to the upper level forcing, better deep layer shear allowed for the storms to have consistent mesocyclones even away from the warm front.

A radar loop following the two long-lived supercells that tracked over the western Midlands. They both would produce weak tornadoes in Saluda County as they encountered the warm front. (Radar visualized through GRAnalyst software.)

The information and track of the tornado that developed northeast of Saluda.

But the warm front was critical in both of these storms producing tornadoes, as they only achieved this as they approached the warm front which was still draped across Saluda county. Thankfully the tornadoes were very weak and short-lived. Overall, these two storms and tornadoes capped off an odd event that models did not anticipate well until the day of. It was also odd that the supercells produced no severe weather outside of the three tornadoes that developed on this day.

The second, weak tornado that occurred in the northern part of the county south of the Saluda River. This was rated EF0.

The GFS (along with other guidance) was picking up on the magnitude of this system 7-8 days in advance. On the left, you have the GFS forecast from January 2nd; on the right, what was initialized on January 9th. Slide right or left to see the difference between the two images. Source: Colorado State

The ECMWF EFI is a tool that we use internally to find areas of opportunity in the long range forecast. Values >0.7 indicate unusual weather, and values >0.9 indicate potential for extreme weather. The Signal for wind gusts on Jan 9th is one of the more impressive signals that we have seen locally in our time using this product. h/t ECMWF

300 mb heights and winds and divergence. Source: SPC.

RAP Reanalysis sounding from 1/9/24 at 2p revealed a sufficiently unstable environment with significant lift and extremely anomalous low-level wind shear. Reanalysis sounding made via the SounderPy program.

The radar loop of the event as it pushed through the area between 1130a and 5p. Radar data visualized through GRAnalyst.

The radar loop of the Bamberg tornado as it pushed through. Visualized using GR Analyst.

500 mb heights, winds, and temperatures between 10a and 10p on Jan 27. The trough took on a negative tilt as the day went along, providing more lift by the evening. Source: SPC.

850 mb heights, winds, temperature, and dewpoints. Winds in the 15-30 knot range aren't typical for winter severe weather locally, but high dewpoints help yield anomalous instability. Source: SPC

The surface warm front was a critical feature in this event, creating an area of enhanced low-level shear for supercells to thrive along. Source: SPC.

KCAE Vertical Wind Profile (VWP) hodograph at 239p and 340p. The second image is closest to the time of the Elgin tornado, revealing more than sufficient low-level helicity. Use the slider bar to compare the two images. Source: Autumn Sky

The storms really struggled to get going until they got within a certain distance of the surface warm front. Several supercells developed within enhanced shear and instability. Source: UCAR Radar Archive

The storm slowly developed a mesocyclone as it progressed through Lexington & Richland Counties, strengthening enough by the time it approached Elgin that it produced a weak tornado. The low-level shear environment was favorable enough near the warm front to yield actual tornadogenesis. Radar visualized through GRAnalyst software.

Stats on the Elgin tornado.

The ZDR column can reveal where strong updrafts are. Swipe to see a comparison of the ZDR vs the regular reflectivity. The storm was not very impressive at this point, as the updraft had just shot up. (Radar visualized through GRAnalyst software.)

A radar loop of the storm as it pushed through Lexington County. It had a deep and persistent mesocyclone but didn't produce a tornado like the Elgin storm did. (Radar visualized through GRAnalyst software.)

An image one of our meteorologists took of the storm as it passed west and north of the office. The wall cloud is discernable just above the airport, with the rotating updraft tilting northeastward due to the effects of shear. A radar image around the time of this picture is shown in the bottom right, with the classic 'Hook-Echo' signature outlined in white.

A radar loop following the two long-lived supercells that tracked over the western Midlands. They both would produce weak tornadoes in Saluda County as they encountered the warm front. (Radar visualized through GRAnalyst software.)

The information and track of the tornado that developed northeast of Saluda.

The second, weak tornado that occurred in the northern part of the county south of the Saluda River. This was rated EF0.