AzShear and storm mode

An example where mode can be inferred using AzShear products. In the first image, we’re dealing with a nice linear segment without any ‘concerning’ rotational features.

Shortly after, the AzShear product clearly highlights threat areas for QLCS tornadic development in at least two distinct locations.

Having this product up in an SA perspective, you’d be able to quickly tell when you need to start being concerned with a structure change in the line.

Merged AzShear for Strength Trends

An example where AzShear data can show storm trends in one image without looping. As SAILS cuts come in you’re able to view rotational strength trends before the entire image is replaced by the next volume scan. Although this image is looping you can see the times when sails cuts would be overlain on one image.

THE 3 MARCH 2019 CASE FOR AZSHEAR – #3

For this embedded tornado, it wasn’t as obvious the circulation that was developing as compared to the supercell from the previous post. It starts out as a kink in the line, which definitely was something that grabbed my attention nonetheless. From there, you can clearly see the evolution of the circulation as it tightens. Would it provide me with additional lead time in a warning? It’s possible by maybe a scan or two, but would like to see more cases using this product first before making that determination.

~Gritty

Merged 3-6 AzShear picking up on mesocyclones early

A

In watching for convection knowing that later in the simulation there will be tornadoes produced in the FL Panhandle, I took a peak at each product prior to convection. Single radar AzShear is a little far away and doesn’t pick up on it but the merged products give an early indication that a supercell is developing and beginning to rotate. Knowing this storm will produce a tornado this is very helpful as a heads up.

 

— lakeeffect

THE 3 MARCH 2019 CASE FOR AZSHEAR – #2

Looking at the 0-2km merged AzShear product, my attention was drawn to the line stretching to the SW of the KMXX radar. While I see utility in using this product more for SA, the SAILS artifact of not having the images lined up properly could lead to false interrogations of what’s actually occurring. In this first image (below), the wind field is apparent. In the second image, it looks like the wind field has separated. In the last image, it’s very clear that a slice being merged into the product shows the wind field significantly separated.

~Gritty

The 3 March 2019 Case for AzShear

The single radar AzShear product made a rapidly developing tornado very apparent, forcing my attention to be pulled to it (first image, below). Additionally, it was very interesting to see the RFD so clearly (second image, below). However, as noted previously, I do have some reservations about the number of false alarms that it may be picking up, as seen in the last image (below). But, there is a lot of promise for this product to serve as an enhanced SA tool and/or increase confidence in the warning decision-making process.

~Gritty

Single Radar AzShear 3/03 Case

A

Seconds into this simulation it’s apparent that an embedded supercell is about to wreak havoc. It’s incredible how well you can examine the anatomy of the thunderstorm using the Single Radar AzShear product. It’s still apparent in the merged products that there’s an area of concern, but you can’t quiet examine the anatomy of the thunderstorm like you can in single radar.

B

In B, the merged 0-2km  it’s clear where we should be paying attention, but trying to diagnose the structure of or the maturity of the thunderstorm is much more difficult.

 

-lakeeffect

The Aggie Tornado From a Shower

PRIOR to the Milam/Burleson County tornado warnings that you can read about below in other blog posts there was a tornado near the Texas A&M Campus in College Station. See these tweets:

  • https://twitter.com/cgar1999/status/1121171711855034370
  • https://twitter.com/jeanette_wx/status/1121171983633350661
  • https://twitter.com/KAGSnews/status/1121205013236391938

If you looked at the image below you would not really be concentrating on the storm (I use the term ‘storm’ loosely) near College Station on the right side of each panel. Based on velocity, AzShear, Reflectivity your focus would be the bowing line segment to the west that would soon produce gate-to-gate velocity signatures south of Hearne.

If you were to zoom into Bryan-College Station though a few things begin to jump out at you. Mainly the high Spectrum Width, the relative maxima in AzShear, and a VERY weak couplet looking signature in velocity (look near the blue Tornado Icon). This is the time that the tornado was reported. The good news is that Spectrum Width picked up on the turbulence in the storm, and AzShear does have a local max, but the values are only 0.007 s^-1 compared to 0.014 s^-1 at the bookend vortex to the west. This scale only goes from 0 to .01 s^-1.

The velocity signature does get slightly better in the 2149z. This is probably a quick spin up due to boundary interaction, but it is shocking that this little SHOWER produce the tornado when the larger storms to the west produced NO reports as of  now (0026z). The good news is that there were local maxes in the AzShear and SW, but not enough that these would be your focus of course.

ProbSevere never pinged the storm…and there were other indications in velocity, AzShear, and SW with other showers that were similar to the tornadic College Station storm. Oh the joys of quick spin up tornadoes due to boundary interactions in Central Texas!

-Alexander T.