Difference between revisions of "EE Events by EPA Region old"

From Earth Science Information Partners (ESIP)
Line 62: Line 62:
  
 
Smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14) --- [deleted from this email]. These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule.  
 
Smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14) --- [deleted from this email]. These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule.  
*[[Media:Wildfire Smoke Impact on Ozone Levels 1-1-.pdf| Wildfire Smoke Impact on Ozone Levels part 1]]
+
*[http://datafedwiki.wustl.edu/index.php/Image:Wildfire Smoke Impact on Ozone Levels 1-1-.pdf Wildfire Smoke Impact on Ozone Levels part 1]]
*[[Media:Wildfire Smoke Impact on Ozone Levels 2-1-.pdf| Wildfire Smoke Impact on Ozone Levels part 2]]
+
*[http://datafedwiki.wustl.edu/index.php/Image:Wildfire Smoke Impact on Ozone Levels 2-1-.pdf Wildfire Smoke Impact on Ozone Levels part 2]]
 
 
 
I see that Rudy explicitly addresses stratospheric ozone intrusion; I would definitely like to see something done on smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. The attached is Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14). These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule. I would be interested in an independent look at this fire and the ozone. Let me know if I can be of more help. Richard
 
I see that Rudy explicitly addresses stratospheric ozone intrusion; I would definitely like to see something done on smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. The attached is Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14). These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule. I would be interested in an independent look at this fire and the ozone. Let me know if I can be of more help. Richard
  

Revision as of 00:02, October 10, 2007

Exceptional Events by EPA Region

Back to EE Analysis main page

Events in Region 1

Contacts:

Events in Region 2

Contacts:

Events in Region 3

Contacts:

Events in Region 4

Contacts:

Smoke impacts on TN/GA/SC. See Husar's 2005 report "Exceptional PM2.5 Event Analysis for TN, GA, and SC, 2002-2004"

Events in Region 5

Contacts:

Events in Region 6

Contacts:

The principal contact for this in Region 6 is Jim Afghani, who reviews these for us, although I'll attend the call as well. I've forwarded the invitation for the call to him. In addition, if you are interested in more types of documentation for exceptional events, here's a link to the TCEQ's site, which has some pretty impressive levels of documentation for some of the events. Note, we were just looking at some of the dust events. Looking at this documentation, the web cams and satellite animations really work for us - seeing those huge dust clouds roll in and totally obscure things is amazing. Maybe this could be suggested as both the level of documentation and an example of how to present it?

Events in Region 7

Contacts:

Events in Region 8

Contacts:

Exceptionally high wind PM events April 15, 2002 (power went out at all Utah monitors before a complete sampling run could complete except Lindon, Utah (49-049-4001). Peak hourly average winds at the monitor were 18 knots, but area winds may have reached 60 mph at other sites. The PM monitor (PM2.5?) recorded 288 mg/m3.

April 1 and 2, 2003. Monitors in Salt Lake City recorded as follows:

April 1, 2003:
   49-035-0012 358 mg/m3
   49-035-1001 421 mg/m3
   49-035-3006 360 mg/m3
April 2, 2003
   49-035-0012 209 mg/m3
   49-035-1001 No sample (1 in 3)
   49-035-3006 120 mg/m3

Of particular interest in this one would be reasons why 49-035-0012 and 49-035-3006 were nearly identical on April 1, but quite different on April 2. Winds on these days were on the order of 30 knots hourly average, with gusts up to 50 or 60 mph.

Of more recent interest, July 26, 2006 was flagged at 49-035-0012 as a high wind day. Only this monitor in north Salt Lake City had an exceedance or a flag; the State identified microbursts in the area due to a line of thunderstorms as the culprit. Salt Lake International Airport recorded a peak gust of 53 mph and peak 2 minute winds of 44 mph 3.4 miles west of the monitor. This might be good to look at shorter averaging times than for the large frontal passage sustained winds of the previous two examples. 49-035-0012 recorded 164 mg/m3 on July 26, 2006.

Smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14) --- [deleted from this email]. These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule.

I see that Rudy explicitly addresses stratospheric ozone intrusion; I would definitely like to see something done on smoke impacts to ozone. Utah has flagged about 50% of its ozone exceedances since 2000 as being due to wildfire smoke; we concurred on most of the 2000 flags, but have nonconcurred since. The attached is Utah's documentation for flagging ozone data on July 12-14 at 49-011-0004, 49-035-2004 (July 12-13); 49-049-0002, 49-049-5008 and 49-049-5010 (July 14). These days did include ozone readings far outside the historical norm for some of these monitors (1 hour exceedances at 3 of them, all time highs at 49-049-0002 and 49-049-5010). The State, however, did not show significant smoke present, let alone significant impact on ozone from the smoke (requirement of EPA-454/R-98-017, Dec. 1998); they are far short of the "but for" demonstration of the rule. I would be interested in an independent look at this fire and the ozone. Let me know if I can be of more help. Richard

Events in Region 9

Contacts:

Southern California: A PM10 series of wildfires events to use involves the following sites in 10/2003:

Calexico - Ethel Street (06-025-0005)  10/24/03 and 10/30/03
Calexico - Grant Street  (06-025-0004) 10/24/03
El Centro - 9th Street  (06-025-1003)  10/30/03
Brawley - Main Stree  (06-025-0003     10/30/03
Westmoreland  (06-025-4003)            10/30/03
Niland  (06-025-4004)                  10/30/03
Escondido  (06-073-1002)         10/29/03
El Cajon  (06-073-0003)          11/23/03
San Diego  (06-073-0006)         11/23/03
Victorville  (06-071-0306)       10/30/03
Rubidoux  (06-065-8001)          10/27/03

Example from BAAQMD: There was a N. California fire event that potentially drove the Concord and Fairfield monitoring sites above the 8-hr ozone standard. This occurred on Sept 30, 1999. You can see all the BAAQMD final ozone numbers at http://gate1.baaqmd.gov/aqmet/aq.aspx (and AQS, of course) as well as all of the meteorological data at http://gate1.baaqmd.gov/aqmet/met.aspx. A substantial amount of analysis was done on this event because it didn't fit the normal exceedance pattern. For example, the Suisun met station only got up to 92°F during the nearby Fairfield exceedance and all northern sites were unusually elevated. Previous AZ examples of R9 concurred events provided to me by Bob P.

Events in Region 10

Contacts:

Three examples of high wind documentation in which the Region had agreed the dates qualified as high wind events. Noted are the easy-to-interpret figures, graphics, and tables (e.g., axes were properly labeled, legends include, etc.) and the inclusion of National Weather Service weather observations, pictures of the event, newspaper articles, and where appropriate, filter analysis.