Another view using GOES-16 “Red” Visible, Shortwave Infrared, “Clean” Infrared Window (10.3 µm) and the Cloud Top Temperature product (below) showed the pyroCb cloud as it drifted rapidly northeast over Nevada and Oregon, along with a second (albeit smaller) pyroCb cloud which developed around 0130 UTC. One standard parameter used for defining a pyroCb cloud is a minimum cloud-top longwave infrared brightness temperature of -40ºC (ensuring complete glaciation) — and in this case with 1-minute imagery, the multi-spectral Cloud Top Temperature (CTT) product (FAQ) indicated that the pyroCb cloud reached the -40ºC threshold 19 minutes earlier than the 10.3 µm infrared imagery. From that point forward, the CTT product was consistently at least 5-10ºC colder than the 10.3 µm brightness temperature; the CTT product eventually displayed a minimum value of -53.9ºC over northeastern California. Even as the 10.3 µm brightness temperature began to rapidly warm after about 0100 UTC, the CTT product continued to display values in the -45 to -50ºC range (shades of green) which allowed for unambiguous tracking of the pyroCb.In the case of the second (smaller) pyroCb cloud that formed from the Carr Fire after 0130 UTC, the 10.3 µm brightness temperature failed to reach the -40ºC threshold, while the CTT product again displayed values in the -45 to -50ºC range. The coldest CTT value of -53.9ºC (seen with the initial pyroCb) roughly corresponded to an altitude of 12.5 km or 41,000 feet according to 00 UTC rawinsonde data from Reno, Nevada (below). Strong upper-tropospheric winds of 80-90 knots rapidly transported the pyroCb anvil northeastward.
GOES-16 “Red” Visible (0.64 µm, left) and Shortwave Infrared (3.9 µm, right) images, with hourly plots of surface reports [click to play animation | MP4]
GOES-16 (GOES-East) “Red” Visible (0.64 µm) and Shortwave Infrared (3.9 µm) images (above) showed the smoke and pyrocumulus clouds as well as the thermal anomaly or “hot spot” (red pixels) associated with the Cranston Fire — located in the center of the images — which started southwest of Palm Springs, California (KPSP) around 1852 UTC or 11:52 am PDT on 25 July 2018. The large areas of red seen on the Shortwave Infrared images early in the animation were signatures of very hot sandy soil surfaces of the southern California deserts. Note the very warm airt temperatures seen across the region; Palm Springs had an afternoon high of 116ºF, and Thermal KTRM had a high of 119ºF.
A slightly different view — with the fire located in the lower left corner, southwest of KPSP — using GOES-16 “Red” Visible (0.64 µm), Shortwave Infrared (3.9 µm) and “Clean” Infrared Window (10.3 µm) images (below) revealed that the fire actually produced 3 distinct pulses of pyroCumulonimbus (pyroCb) cloud, where the 10.3 µm cloud-top infrared brightness temperature reached or exceeded the -40ºC threshold (lime green enhancement). Three specific times that these separate pyroCb clouds were evident were 2102 UTC, 2147 UTC and 2312 UTC.
GOES-16 “Red” Visible (0.64 µm, left), Shortwave Infrared (3.9 µm, center) and “Clean” Infrared Window (10.3 µm, right) images, with 4-letter airport identifiers plotted in yellow [click to play animation | MP4]
Another view of the pyroCb pulses was provided by a 4-panel view of GOES-16 “Red” Visible (0.64 µm), Shortwave Infrared (3.9 µm), “Clean” Infrared Window (10.3 µm) and Cloud Top Phase (below). The coldest 10.3 µm cloud-top infrared brightness temperatures were -55ºC as the primary pyroCb anvil drifted northeastward toward the California/Nevada border.
GOES-16 “Red” Visible (0.64 µm, top left), Shortwave Infrared (3.9 µm, top right), “Clean” Infrared Window (10.3 µm, bottom left) and Cloud Top Phase (bottom right) images [click to play animation | MP4]
There was also substantial lightning observed with these pyroCb clouds:
Loop of fire temperature RGB showing #CranstonFire in Southern California yesterday. Total lightning also overlaid showing pyrocumulus generated dry lightning. Areas of glint also seen towards end of the loop from solar farms reflecting light directly into the #GOESEast ABI pic.twitter.com/9wsBBeJsAu
— William Churchill (@kudrios) July 26, 2018
Below is a timelapse video of the first 8 hours of the fire, which shows the pyroCb evolution at the end.
===== 26 July Update =====
GOES-16 “Red” Visible (0.64 µm, top left), Shortwave Infrared (3.9 µm, top right), “Clean” Infrared Window (10.3 µm, bottom left) and Fire Temperature (bottom right) images [click to play animation | MP4]
Another pyroCb was produced by the Cranston Fire on 26 July, as shown by GOES-16 “Red” Visible (0.64 µm), Shortwave Infrared (3.9 µm), “Clean” Infrared Window (10.3 µm) and Fire Temperature images (above). Similar to the previous day, there appeared to be 2 pulses of pyroCb formation — with cloud-top infrared brightness temperatures cooling to -44ºC. Pyrocumulus from the smaller Ribbon Fire (just southeast of the Cranston Fire) could also be seen.
* GOES-17 images shown here are preliminary and non-operational *
The Ferguson Fire in central California produced a pyrocumulonimbus (pyroCb) cloud during the afternoon hours on 15 July 2018. GOES-16 (GOES-East) “Red” Visible (0.64 µm), Shortwave Infrared (3.9 µm) and “Clean” Infrared Window (10.3 µm) images (above) showed that the high-altitude portion of the pyroCb cloud then drifted northeastward toward the California/Nevada border, where cloud-top infrared brightness temperatures cooled to near -55ºC (orange enhancement) as it crossed the border around 0005 UTC on 16 July.
A comparison of Visible images from GOES-15 (0.63 µm), GOES-17 (0.64 µm) and GOES-16 (0.64 µm) is shown below — with the imagery displayed in the native projection of each satellite. Images from GOES-16/17 are at 5-minute intervals, while images from GOES-15 are every 5-15 minutes depending on the operational scan schedule of that GOES-West satellite. GOES-17 was at its post-launch checkout position of 89.5ºW longitude, so it offered a more direct view of the pyroCb cloud.A toggle between NOAA-19 Visible (0.63 µm), Shortwave Infrared (3.7 µm) and Infrared Window (10.8 µm) images (below) showed the pyroCb cloud southwest of the California/Nevada border (between Bridgeport KBAN and Mammoth KMMH) at 2327 UTC. In spite of a minimum cloud-top 10.8 µm infrared brightness temperature of -59ºC (red enhancement), note the darker (warmer) appearance of the cloud on the 3.7 µm image — this is due to reflection of solar radiation off the smaller ice particles of the pyroCb anvil. The -59ºC temperature roughly corresponded to an altitude of 13 km or 42.6 kft on the 00 UTC Reno, Nevada rawinsonde report (plot | data) A time lapse of the pyroCb was created by Sierra Fire Watch (below).
On Shortwave Infrared imagery, the thermal anomaly or “hot spot” appeared as a large cluster of red pixels — and the top of the pyroCb cloud took on a darker gray appearance than nearby high-altitude ice crystal clouds (due to enhanced solar reflectance off the smaller ice crystals of the pyroCb anvil). On 10.3 µm imagery, cloud-top infrared brightness temperatures cooled to around -50ºC (bright yellow enhancement) as the pyroCb drifted northeastward.On 1-km resolution NOAA-19 AVHRR Infrared Window (10.8 µm) imagery at 22:07 UTC (above), the minimum cloud-top brightness temperature was -53ºC — this temperature roughly corresponded to an altitude of 11.6 km according to 00 UTC rawinsonde data from Grand Junction, Colorado (below).
— Michael Charnick (@charnick_wx) June 9, 2018
As the pyroCb moved southeastward over western Ontario, the coldest GOES-16 cloud-top infrared brightness temperatures were around -55ºC (orange enhancement), which corresponded to altitudes around 10.3 to 10.8 km according the rawinsonde data from Pickle Lake, Ontario (below).In a comparison of 1-km resolution NOAA-19 Visible (0.63 µm), Shortwave Infrared (3.7 µm) and Infrared Window (10.8 µm) images at 2210 UTC (below), the minimum cloud-top infrared brightness temperature was -58.1ºC (darker orange enhancement), which roughly corresponded to altitudes of 10.6 to 11.0 km (just below the tropopause) on the Pickle Lake soundings.
4-panel comparisons of Suomi NPP VIIRS Visible (0.64 µm), Near-Infrared “Snow/Ice” (1.61 µm), Shortwave Infrared (3.74 µm) and Infrared Window (11.45 µm) images at 1936 UTC and 2029 UTC (below) revealed that the maximum differences between 3.74 µm and 11.45 µm cloud-top infrared brightness temperatures — at the same location on the pyroCb anvil — were 86ºC (+26ºC and -59ºC at 1936 UTC) and 91.5ºC (+27.5ºC and -63ºC at 2029 UTC).Lightning was detected from portions of the smoke plume, as well as the core of the pyroCb thunderstorm.
Serious weather nerd moment but absolutely amazing watching the #MallardFire form pyrocumulonimbus & severe thunderstorms over the Texas panhandle. Look at that lightning activity! Wow! #TXwx #PHwx #OKwx #TXfire pic.twitter.com/poozQuipF5
— Zach Stanford (@zachstanford) May 12, 2018
After dark, the thermal signature of the Mallard Fire was also apparent on GOES-16 Near-Infrared “Cloud particle size” (2.24 µm) imagery (below).
===== 12 May Update =====In a comparison of 250-meter resolution Terra MODIS True-color and False-color Red-Green-Blue (RGB) images from the MODIS Today site (above), the Mallard Fire burn scar was evident in the False-color. Both images showed a smoke plume from ongoing fire activity, which was drifting northward across the Texas Panhandle.
The corresponding Terra MODIS Land Surface Temperature product (below) indicated that LST values within the burn scar were as high as 137ºF (darker red enhancement), in contrast to values around 100ºF adjacent to the burn scar.