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

From Earth Science Information Partners (ESIP)
m ([BOT] Misspelling correction: | occuring -> occurring)
 
(7 intermediate revisions by 2 users not shown)
Line 35: Line 35:
 
Contacts: The principal contact for this in Region 6 is Jim Afghani
 
Contacts: The principal contact for this in Region 6 is Jim Afghani
  
The Texas Commisssion of Environmental Quality is maintaining a [http://www.tceq.state.tx.us/compliance/monitoring/air/monops/sigevents07.html comprehensive list of air pollution events] occuring in Texas. The event documentation begun in 2000 and include ozone, fire as well as dust events from local (TX/NM/Mexico) and distant (Sahara) sources. There is extensive documentation provided from satellite (incl. animations) and surface pollutant monitors, wether data, webcams and other data sources. The Texas collection is an outstanding, rich resource for event selection.   
+
The Texas Commisssion of Environmental Quality is maintaining a [http://www.tceq.state.tx.us/compliance/monitoring/air/monops/sigevents07.html comprehensive list of air pollution events] occurring in Texas. The event documentation begun in 2000 and include ozone, fire as well as dust events from local (TX/NM/Mexico) and distant (Sahara) sources. There is extensive documentation provided from satellite (incl. animations) and surface pollutant monitors, wether data, webcams and other data sources. The Texas collection is an outstanding, rich resource for event selection.   
  
 
Candidate events from New Mexico.
 
Candidate events from New Mexico.
Line 56: Line 56:
 
Contacts:  
 
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, 2003Monitors in Salt Lake City recorded as follows:
+
April 15, 2002: 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, 2003:
+
* April 1, 2003: Monitors in Salt Lake City recorded as follows: 49-035-0012 358 mg/m3, 49-035-1001 421 mg/m3, 49-035-3006 360 mg/m3
    49-035-0012 358 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
    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 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.  
+
July 26, 2006: Monitor 49-035-0012 recorded 164 mg/m3, was flagged 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.  
  
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.
+
Potential smoke impacts to ozone.  
*[http://datafedwiki.wustl.edu/index.php/Image: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_2-1-.pdf Wildfire Smoke Impact on Ozone Levels part 2]]
+
*[http://datafedwiki.wustl.edu/index.php/Image:Wildfire_Smoke_Impact_on_Ozone_Levels_1-1-.pdf Potential Wildfire Smoke Impact on Ozone Levels part 1]]
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
+
*[http://datafedwiki.wustl.edu/index.php/Image:Wildfire_Smoke_Impact_on_Ozone_Levels_2-1-.pdf Potential Wildfire Smoke Impact on Ozone Levels part 2]]
  
 
== Events in Region 9 ==
 
== Events in Region 9 ==
Line 93: Line 87:
 
  Rubidoux  (06-065-8001)          10/27/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.  
+
'''Example from BAAQMD''': On Sept 30, 1999 there was a N. California fire event that potentially drove the Concord and Fairfield monitoring sites above the 8-hr ozone standard - see all the final ozone numbers at [http://gate1.baaqmd.gov/aqmet/aq.aspx BAAQMD] and [http://gate1.baaqmd.gov/aqmet/met.aspx met data]. Substantial 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.
+
 
 +
'''Examples from Arizona:'''
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_9_Phoenix_area_exceed_August_13_2004.pdf Phoenix area exceedance, August 132004]]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_9_Phoenix_area_exceed_August_13_2004.pdf Phoenix area exceedance, August 132004]]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_9_ADEQ_Buckeye_exceedance_Sept18_2004.pdf ADEQ Buckeye exceedance, Sept18_2004]]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_9_ADEQ_Buckeye_exceedance_Sept18_2004.pdf ADEQ Buckeye exceedance, Sept18_2004]]
Line 101: Line 96:
 
Contacts:  
 
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.  
+
Three examples of high wind events in Region 10. The documentation is below:
  
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10__Coeur_d_Alene_ID_09-25-01.pdf Coeur d'Alene, Idaho - September 25, 2001 PM10 natural event]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10__Coeur_d_Alene_ID_09-25-01.pdf Coeur d'Alene, Idaho - September 25, 2001 PM10 natural event]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10_Burbank_WA_10-30-03.pdf Burbank, Washington - October 30, 2003 PM10? natural event]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10_Burbank_WA_10-30-03.pdf Burbank, Washington - October 30, 2003 PM10? natural event]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10__Kennewick_WA_10-23-01.pdf Kennewick, Washington - October 23, 2001 PM10? natural event]
 
* [http://datafedwiki.wustl.edu/index.php/Image:EE_10__Kennewick_WA_10-23-01.pdf Kennewick, Washington - October 23, 2001 PM10? natural event]

Latest revision as of 06:42, December 20, 2007

Exceptional Events by EPA Region

Back to EE Analysis main page

This is not an official list of exceptional events

A goal of this wiki space is to provide a forum for illustrating Exceptional Events as defined the the EE Rule. For the illustrations, specific events need to be selected that are both illustrative and relevant. This page contains an evolving list of candidate air qualitiy events that may have characteristics of Exceptional Events as defined the the EE Rule. Some of the listed events have already been handled by the regulatory process.

Events in Region 1

Contacts:

Events in Region 2

Contacts:

Events in Region 3

Contacts:

Events in Region 4

Contacts:

In the prepapratory phases of the EE Rule, considerable analyses were conducted to evaluate a list candidate exceptional events submitted by the States GA/TN and SC. All the requested exemptions were attributed to smoke impacts. These analyses, conducted by Husar et. al.(2005), were incuded in the Docket of the EE Rule.

Events in Region 5

Contacts:

Events in Region 6

Contacts: The principal contact for this in Region 6 is Jim Afghani

The Texas Commisssion of Environmental Quality is maintaining a comprehensive list of air pollution events occurring in Texas. The event documentation begun in 2000 and include ozone, fire as well as dust events from local (TX/NM/Mexico) and distant (Sahara) sources. There is extensive documentation provided from satellite (incl. animations) and surface pollutant monitors, wether data, webcams and other data sources. The Texas collection is an outstanding, rich resource for event selection.

Candidate events from New Mexico.

Events in Region 7

Contacts:

Events in Region 8

Contacts:


April 15, 2002: 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, 2003: Monitors in Salt Lake City recorded as follows: 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.

July 26, 2006: Monitor 49-035-0012 recorded 164 mg/m3, was flagged 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.

Potential smoke impacts to ozone.

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: On Sept 30, 1999 there was a N. California fire event that potentially drove the Concord and Fairfield monitoring sites above the 8-hr ozone standard - see all the final ozone numbers at BAAQMD and met data. Substantial 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.

Examples from Arizona:

Events in Region 10

Contacts:

Three examples of high wind events in Region 10. The documentation is below: