A Close Look at LightningCast for the Application of DSS or TAF Support

On June 15th 2022, a dynamic setup was unfolding across Iowa, Minnesota, and Wisconsin with multiple hazards that NWS forecasters would have had to message and warn. For this case, we were on watch for a DSS event representing the Cranberry Blossom Festival in Wisconsin Rapids in the GRB CWA. The main concerns with the event were lightning and any severe storms, both of which seemed certain for this case and the name of the game was timing the oncoming convection.

LightningCast uses machine learning with numerous satellite inputs that yields the probability of lightning occurring at a location within the next hour. This product immediately jumps to the front of a forecaster’s mind to apply for decision support services (DSS) or assessing lightning probability for airport forecasting. Below is a table showing the probabilities from LightningCast versus the “time of arrival” tool that estimated storm timing based on the movement of storms:

First vicinity lightning strikes (within 10 mi of event): 4:21 PM
Arrival of storms (within 10 mi of event): 4:30 PM
Immediately the usability of this product is fantastic. It shows the probabilities of lightning occurring in a contour format, making it a great pairing with satellite imagery, lightning data, and radar. WIth this case being a very well forced event the main evaluation was the percentages and how they did with the advection of the storms. The LightningCast seemed to ebb and flow with the eastward acceleration and deceleration of the storms between 3 and 3:30 PM, while the next 15 minutes showed accelerating storms, giving a 61% chance of lightning within the next hour at 3:45 PM. With the acceleration of the storms, it was good to see the model adjust, with the 50% threshold being crossed before 3:45 PM. The 50% threshold is very important for forecasters, as values above that are typically  used in several products and gauges of confidence. The LightningCast model giving upwards of 40 minutes of lead time for advecting storms gives me a lot of confidence in the product, leaving me wishing it was already available within our datasets for immediate use.
– aerobeaver

Storm Movement and Severity at TAE

Down in Tallahassee, there are two boundary layers where storms are initiating or ongoing.  There is a lingering MCS that moved down from the Midwest overnight and a Sea Breeze. You can see the CAPE gradients along the both boundaries and how that progresses forward in time with both the boundaries interacting with one another.

17Z

18Z

19Z

This tracks very well when you overlay the visible satellite imagery with the PHS images as you can see the cumulus field along the CAPE gradient. This gives a good visualization of where storms are initiating along the Sea Breeze and the strongest storm movement along the MCS.
As these two boundaries move closer together they will be moving into a more favorable low level environment. It would be nice to have the Polar Orbiting Satellite NUCAPS sounding data available. This way we could verify lapse rates and what Prob Severe is giving us. While an upper level ridge is in place over the southern CONUS what sounding information we did have early on in the forecast period was very helpful as outside of the storm environment skies were clear. I was able to grab some gridded NUCAPS data that shows the diurnal destabilization of the low levels from 18Z. Now that it is 21Z, that data isn’t as helpful in either a warning or pre convective event because things could have changed drastically in the 3 hrs since the last Polar Orbiter moved through.
After overlaying Prob Severe with the PHS CAPE and Visible Satellite imagery, you can see your strongest storms along the CAPE gradient which tracks well. However, there are differences between Prob Severe Version 2 and Version 3.
A great example of the differences between PSv3 and PSv2 is with one of the strongest storms of the day for the Tallahassee CWA. Version 2 seems to try to highlight a hail threat at 48% while Version 3 has prob severe hail at 6%.  It seems that Version 2 is overestimating the Hail threat for this area. Especially given the subpar mid level lapse rates at 5 C/km or less, storm motion of around 5 kts or less and the upper level subsidence. The storm environment just is not conducive to produce quarter sized or larger hail.
– Cirrus Fields

LightningCast/NUCAPS and Isolated to Scattered Convection in FGF

Convection developed rapidly to the south of the main area of convection in an area of high instability. This was first picked up by higher probabilities in the LightningCast data. There was some rapid cumulus development that was picked up well by the algorithm. Probabilities went well above 75% around 5 minutes or so from the first GLM detection. NUCAPs data indicated MLCAPEs of around 2000 J/Kg in this area supporting the quick upscale growth.

Convection developed rapidly to the south of the main area of convection in an area of high instability. This was first picked up by higher probabilities in the LightningCast data. There was some rapid cumulus development that was picked up well by the algorithm. Probabilities went well above 75% around 5 minutes or so from the first GLM detection. NUCAPs data indicated MLCAPEs of around 2000 J/Kg in this area supporting the quick upscale growth.

LightningCast and GLM at 2131 UTC

DCP RGB and LightningCast  2131 UTC

MRMS -10 Reflectivity and LightningCast first GLM detection at 2135 UTC

So let’s take a look at some NUCAPS soundings as we had three overpasses right before the convection initiated in the above examples.  Here is the first overpass with the sounding point selected with the red arrow:

NUCAPS Sounding at 1823 Z

Not too shabby with a MLCAPE value of 2094 J/kg.  (And why mixed-layer? Hank likes ML because very few times do parcels start at the surface for SB, and MUCAPE is just fun to look at).

The next overpass was 2003 UTC (about an hour and a half after the previous overpass) to see if the environment has changed much:

MLCAPE of 1235.  Hmmmm…that’s quite a drop in MLCAPE compared to previous overpass.  Two things to remember; this is on the edge of the field-of-view (matter of fact, the eastern edge).  Luckily we have a Modified NUCAPS for the same profile point which adjusts the boundary layer:

Yeah, that looks much more reasonable based on observational trends (few clouds to change the mid-atmospheric profile, increasing surface T/Td conditions) with 2185 J/kg MLCAPE.  But wait, there’s more!  We also have a:

NUCAPS AQUA Overpass

This was almost directly under NADIR so we should have much better profile retrieval.  Sure enough, MLCAPE value is almost 3000 J/kg in between the 1823 and 2003 UTC NOAA-20 sounding retrievals.

How does this all tie into the weather for FGF today?  This is what the SPC Mesoanalysis graphics had for 2100 UTC MLCAPE values:

They all combine to increase confidence on what conditions COULD be in areas where the models are saying one thing and an observational system is indicating potential reality (remember, it’s still a remote sensing platform with their own set of issues). In our case, the bulls-eye of 3000 J/kg in east central Minnesota is likely real and needs to be an area to watch…and that is where the Lightning Cast product at the start of our post indicated the potential for new activity to develop.  Pretty cool stuff…

– Marty McFly/Hank Pym

Where is the new convection going up?

The GLM can be used to help find where new convection is developing under a cirrus canopy.  Here’s an example of this!

Top left – LightningCast with Day Land Cloud Convection and Flash Extent Density (FED).  Top Right is Minimum Flash Area (MFA). Bottom left is MRMS 1km Reflectivity.

We can see that there are some returns developing in the center of the field of view on the MRMS reflectivity but it is hard to tell whether this is real or not.  Five minutes later, we have this image:

Hmm, that could be new convection developing on the Top Left panel because it looks like there is a tower coming through the cirrus shield.

And then the next frame we have:

And there we go!  Flashes starting to show up so it looks like this area of convection will need to be watched.  (Should also note that it would also be helpful to time match to the GLM 1-minute FED instead of the 5-minute RGB!)

-Hank Pym

Metwatch for Wilmington DSS event

Metwatch for Wilmington NC started with modified NUCAPS soundings and a comparison with NAM BUFKIT profiles:

Looking at 700mb temperatures, BUFKIT has about 8C for that layer, and here is the gridded NUCAPS 700mb temperature layer. Note: not a lot of advection noted at 700mb, with low level dry advection (not shown)

Watching this cell just outside the CWA pulse and then fall apart…PWV3 never exceeds 4% with this pulse. LightingCast also showed a rapid drop in probabilities.

Not much happened today, but just along the coast was this little area of enhanced CAPE (3000j/kg)…so you’re saying there’s a chance…

Comparison between parallax corrected and uncorrected lightning cast. You can see the image above and to the right (corrected) has some higher percentages getting into the 20 mi range ring compared to the non corrected data which just has the 25% grazing the 20 mi range ring. Having the corrected data could be more beneficial to providing DSS support.

– Mr. Bean

– Noctilucent

LBF HWT Blog Day 4

We didn’t have too many storms occur during operations today, but that allowed us to be able to focus more on CI.

LightningCast for CI

Was able to use LightningCast for convective initiation today as LBF was waiting for storms to fire back up for the afternoon and evening. Initially we were thinking storms would form first over the southern portion of the CWA based off of modeled convective parameters but at 2101Z, a 25% chance of lightning popped up via LC for the north-central portion of the forecast area. This 25% contour appeared a few minutes before radar reflectivity started showing up for the same area. Seeing even the 10% contour show up earlier on, clued me into the fact that we needed to shift our focus further north than we originally thought. These storms seemed to be forming along a shear gradient and weak boundary.
Of note, I am using the parallax corrected LC.
LC, GLM FED, and DCPD at 2100Z
LBF radar at 2109Z
By 2116Z, both GLM and ENTLN showed the first flash of lightning, allowing for around 15 minutes of lead time off of the 25% contour.
For comparison, these storms were forming ahead of the highest PHS CAPE and ahead of any of its stronger gradients.
21Z:
22Z:
As our day was winding down, LC continued to indicate areas to watch before it showed up on radar, but I did not grab additional images.

NUCAPS:

Tried to compare NUCAPS soundings today as we did have an overlap, but unfortunately ran into technical issues within my CAVE so was not able to do much with it. Another limiting factor was that the only “green” soundings from Aqua within our CWA fell within the far western scans which we were told by one of the developers they would next expect good data from, being on the limb. But for comparison, here are Aqua (1911Z) and NOAA-20 (1953Z) sounding from points NW of North Platte.
Points selected were both NW of the town of North Platte, circled below. The NE point of the two is Aqua and SW point is NOAA-20
– Matador

ILN HWT Blog Day 3

NUCAPS

Did finally get a chance to check out NUCAPS for today’s case as the timing and location of the data was more compatible. It was good info ahead of the storms as it showed the low LCL values (mainly noticed in the modified soundings), below 1000 ft which is what you want to see for potential tornadoes. Overall, liked getting to dig into the NUCAP soundings, but given the finicky timing and data quality, it’s not something I could use on a regular basis for warning operations. Would be better suited for short term forecasting or possibly as the mesoanalyst.

GLM & LightningCast

For GLM, I set the max value at 130. I originally set it to 65 as I had been using in the high plains the past few days, but for these midwest storms it seemed too sensitive. 130 was a good value for today, likely because of the larger and more numerous storms than I dealt with today versus the previous days.
Also tried out the parallax corrected LightningCast today. Liked that it gave a more accurate location when using it for a specific location such as today’s DSS event. While it was made to pair with radar, it was still useful when using it with satellite products – just had to take a few seconds to make the mental adjustments at the beginning.

PHS

Prior to entering the ILN CWA, the PHS STP showed an area of high STP values in and near Rush County, Indiana. The actual IND office did issue a tor warning for this area at 4 PM ET.
Over time, I did notice that for STP, really just the current hour and the next couple of hours were useful. Jumping to 3 or 4 hours ahead it seemed that the data was missing for areas I expected to see higher values. Once the next run came in and I went back and looked, the data was much better. For an example below, there was a vast difference for 21Z between the 18Z run and the 20Z run where the 18Z run for that time did not seem realistic but the 20Z run was more what I expected to see.
08.18 run for 21Z

ProbSevere

After talking with one of the ProbSevere people, was able to learn that the threshold for ProbTor is lower than that for Wind or Hail. For training purposes, it would be good to include this information to give a mental threshold for forecasters, such as an ongoing tornado would likely see a max of around 60% for ProbTor. It makes sense that the probs would be lower for tors just as they are for SPC outlooks where the tor percentages are also lower than that for wind or hail.
– Matador

Northeast Colorado Supercells

Nowcasting Supercell storm entering CWA: The loop of instability and SigTor highlight the southeast/south central CWA east of Colorado Spring, ahead of an already ongoing storm. North of this storm an environment of favorable instability exists up to about the latitude of Denver, with a significant drop off to the north.

When it comes to high and northern plains – parallax becomes an issue. In this case lighting was occurring just on the other side of the border with the CWA, so here are the two LightningCasts (with/without parallax correction) for comparison:

ProbSevere v3 increases correlating to entering a favorable environment

PHI localized CAPE corridor

New area of MFA suggesting spitting storm with new updraft core of the established cell. (1950 UTC)

Storm cell split denoted by MFA with two distinct areas of MFA in upper right panel. (2000 UTC)

Focused on the cell east of Denver – this cell and subsequent others that developed are in the favorable area of instability. Just to the north of Boulder we spotted a few cells that attempted to develop, however in the lower instability environment movement off the higher terrain resulted in these cells falling apart. Through the rest of the afternoon this area remained convection free.

Sig Tor blip. A SRVE like feature was observed but at this time convergence associated with this feature wasn’t favorably located under the updraft.

Cell developing east of Denver, noted by the MFA  in the upper right panel. (2020 UTC)

Cell rapidly develops in an area of localized higher instability denoted by the PHS values discussed earlier on.(2034 UTC)

The LightningCast has identified the left turning nature of the storm(s) east of Denver

An interesting note was comparing the differences between GOES East (left panel) and GOES West (right panel). These subtle differences can  be effective in analyzing the strengthening of a thunderstorm.

In the middle of METWATCH – NUCAPS became available (about 1 hour latency). The sounding below is a modified NUCAPS profile, depicting the environment in which our storms developed. Storm mode was supercellular with frequent spitting of cells.

-Mr. Bean

-2%hatched

CYS HWT BLOG Day 2

LightningCast for storm approaching Scottsbluff

First instance of 50% contour 1831 Z
The lightning cast did build before backing off for a few frames, dropping below 50%, but jumps back up above at 1851 Z. From then until the first flashes of lightning, the probabilities continued to increase.
First instance of 75% contour 1906 Z
GLM denotes flash 1915 Z
So, lightningcast was able to indicate well ahead of time that we needed to keep an eye on that storm for lightning production as it approached the city.

GraphiCasts with ProbSevere and PHS

For today’s GraphiCast, decided to overlay ProbSevere V3 over visible satellite data to indicate the location of the stronger storms amongst all the clouds. The concern with using it for public graphics is whether the public will understand it. Went with a brief description that it indicates stronger storms for today, but would be curious to see how others message what probsevere means and then how the public may respond to it. I do like how it clearly shows the cells to watch out for.
To determine the time that storms would continue through, I only used the hourly PHS data which dropped off at 23Z. The images below show 20Z PHS vs 23Z. This timing for storms ending for the CYS CWA worked out well as the strong to severe storms exited the CWA by 2256Z with only a few isolated showers remaining for a short time afterwards.
20Z:
23Z: 
– Matador

Potential LightningCast limitations under convective debris

The first day of familiarization with the tools for the hazardous weather testbed and we were assigned the Louisville CWA to test a number of products on. The synopsis of the area’s weather features a line of convection moving in from the west with a Severe Thunderstorm Watch in place and several storms had already been warned on.

On the other side of the CWA, a few weaker cells had developed under a mix of sun and high clouds. It’s this convection across the eastern CWA that became the focus for today’s blog. We chose to target the LightningCast product because we noticed that although the -10C MRMS data would suggest lightning, the LightningCast data was actually much lower than anticipated (below 10 percent). Why was this the case?

After speaking with John Cintineo about this, and looking at the training that was provided for this testbed, it was surmised that this may be a case where convective debris or high clouds could mask the signal of weaker convection.

Eventually LightningCast did highlight this area with a lightning risk, but this case is relevant because if we are using this tool to aid in DSS to our partners, we must also identify some potential limitations.

Noctilucent/Mr. Bean