← Air events

Mixed causes Possible

2003-06-24 to 2003-06-25 Akron, OH, Columbus, OH, and 1 other metros mixed-source pollution episode

June 24, 2003 to June 25, 2003

Daily PM2.5 peaked at 49 µg/m³ near Akron across 3 covered metros home to 3.7 million people.

Counting the extra PM2.5 above each metro's typical day, this event handed the average affected resident ≈ 2.1 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 7.8 million cigarettes. An awareness illustration of outdoor exposure at 22 µg/m³ per cigarette (Berkeley Earth), counting only the event's ranked days; not a medical dose.

Why we think this happened

The basis for “Mixed causes”

Manual research connected 3 source events to one mixed-source pollution episode using the deterministic grouping rule.

Possible This is a transparent hypothesis supported by limited evidence or an explicit inference, not a definitive attribution.

U.S. Environmental Protection Agency archive · Jul 15, 2004 corroborates

June 25, 2003 Midwest ozone episode transport analysis

The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

U.S. EPA AirData hypothesis

Dayton, OH joint pollution fingerprint, 2003-06-24 to 2003-06-25

EPA records show median daily PM2.5 of 45.575 micrograms per cubic meter across 3 monitors, 2.45 times the adjacent-window level. Co-pollutants at least 10% above the adjacent-window comparison were carbon monoxide (1.451x), sulfur dioxide (2.661x).

National Weather Service surface observations via Iowa Environmental Mesonet · Jun 24, 2003 hypothesis

Dayton, OH surface conditions, 2003-06-24 to 2003-06-25

WRIGHT PATERSON recorded calm conditions during 0% of event hours and wind at or below three knots during 60%. Observations included 9 haze hours, 9 mist hours, minimum visibility 2 miles.

Inference, not direct attribution

documented_regional_polluted_airmass_overlap_possible.v1: This inference is recorded in the catalog methodology.

See every retained source and limitation ↓

Sequence: Dayton (Jun 24) → Akron (Jun 25) → Columbus (Jun 25)

Evidence path

From source to city

A cause is more convincing when the record connects three things: something happened, the air mass moved toward the region, and local instruments responded. Here is how much of that chain is documented for this event.

Open the evidence ledger ↓
  1. 1

    Source or mechanism

    Mixed causes

    The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

    View supporting source ↗
    Documented
  2. 2

    Air-mass movement

    Transport into the affected region is documented

    The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

    View transport source ↗
    Documented
  3. 3

    Local response

    49 µg/m³ near Akron

    EPA monitors recorded the event across 3 metros. The peak daily concentration is roughly 2.2 cigarette-equivalents at the outdoor daily rate.

    Inspect the pollutant and weather signals ↓
    Documented

Event autopsy

What the instruments saw

Before, during, and after the episode: nearby pollutant monitors and surface-weather stations show what changed. This context tests the “Mixed causes” explanation; it does not assign the cause by itself.

Observed context · not attribution

Akron, OH

Monitor comparison window 2003-06-22 to 2003-06-28 · PM2.5 target: East HS

5 pollutant signals
Fine-particle pulse 47.9 µg/m³

96% above nearby days

Air movement 6 kt median wind

8 calm hours observed

What observers saw 4 mi minimum visibility

Haze reported during 9 hours

Pollution fingerprint

Metro-wide median of reporting monitors
PM2.5 47.9 µg/m³

96% higher than surrounding days

Before24.4 µg/m³ Event47.9 µg/m³ After23.4 µg/m³
3 monitors · 24 HOUR
PM10 62 µg/m³

44% higher than surrounding days

Before43 µg/m³ Event62 µg/m³ After29 µg/m³
2 monitors · 24-HR BLK AVG
Carbon monoxide 0.650 ppm

About the same as surrounding days

Before0.827 ppm Event0.650 ppm After0.444 ppm
2 monitors · 1 HOUR
Sulfur dioxide 22.5 ppb

201% higher than surrounding days

Before6.43 ppb Event22.5 ppb After7.48 ppb
2 monitors · 1 HOUR
Ozone 0.082 ppm

30% higher than surrounding days

Before0.072 ppm Event0.082 ppm After0.050 ppm
2 monitors · 8-HR RUN AVG BEGIN HOUR

Atmospheric conditions

Akron, 2.9 km from the PM2.5 target
Wind 6 kt median

10 kt maximum · 8 of 24 observed hours calm

Visibility 4 mi minimum

0 observed hours at or below 3 miles

Temperature 76°F median

64°F to 87°F

Humidity 66% median

90% maximum

Source: U.S. EPA AirData daily observations and, where available, nearby ASOS/AWOS surface observations. Values are descriptive medians over the retained monitor set; missing measurements remain missing. Transport and source evidence remain separate layers because this instrument pattern does not assign a cause by itself.

Measured daily PM2.5 at EPA monitors, as cigarette-equivalents
EPA monitors sit in metro areas, so the colour clusters there. Land between and beyond them is unmeasured, not clean: this map shows where IAQng has readings, not the extent of the smoke.

Episode peak

-- cigarettes

The smoke map's scale, replayed over this event: the surface interpolates between covered metros' daily records, framed to the affected region. Hover for a reading, click a metro to pin it to the card. Days a monitor did not report draw nothing.

Views from the selected metro

Camera views near

Browse the camera map →

Select a metro on the map to see nearby cameras. Where an operator archive reaches the event, drag the divider to compare two moments, adjust either date and time, or play the available event-day frames. Camera imagery is visual context, not an air-quality measurement or proof of smoke.

Affected metros

MetroPeak PM2.5Cigarettes, whole eventPeak dayAll-time standing
Akron, OH 49 µg/m³ 2.2 Jun 25, 2003 #15 of its top days
Columbus, OH 48.9 µg/m³ 2.2 Jun 25, 2003 #19 of its top days
Dayton, OH 48.6 µg/m³ 4.3 Jun 25, 2003 #13 of its top days

"Cigarettes, whole event" totals a metro's ranked event days at 22 µg/m³ per cigarette: what a person outdoors there breathed across the event, as the illustration. "All-time standing" is where this episode's days sit in each metro's ranked record (worst-area measure, since 1999). Full local context is on each metro's Air Records page.

Public evidence library

What supports this account

Each card states what a source supports—and what it does not. Official records, research, reporting, community observations, and transparent inferences remain visibly different kinds of evidence.

9 retained sources

Official record

June 25, 2003 Midwest ozone episode transport analysis

U.S. Environmental Protection Agency archive

The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

What it supports

A retained source supports the attributed cause for the stated place and dates.

Limit

The analysis addresses ozone and Southeast Michigan; it supports regional transport on the exact date but cannot apportion Ohio PM2.5.

Official record

June 25, 2003 Midwest ozone episode transport analysis

U.S. Environmental Protection Agency archive

The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

What it supports

A retained source supports the attributed cause for the stated place and dates.

Limit

The analysis addresses ozone and Southeast Michigan; it supports regional transport on the exact date but cannot apportion Ohio PM2.5.

Official record

June 25, 2003 Midwest ozone episode transport analysis

U.S. Environmental Protection Agency archive

The archived regional analysis concludes that the unusually widespread June 25 ozone episode was dominated by transported pollution, supported by back trajectories showing the affected air mass moving through the region.

What it supports

A retained source supports the attributed cause for the stated place and dates.

Limit

The analysis addresses ozone and Southeast Michigan; it supports regional transport on the exact date but cannot apportion Ohio PM2.5.

Official record

Haze over the Atlantic Seaboard on June 24, 2003

NASA Earth Observatory

NASA reported that SeaWiFS observed thick haze along the U.S. eastern seaboard on June 24, concentrated around an offshore low, and described Canadian-fire smoke as a possible contributor.

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

NASA used tentative language about smoke and did not attribute ground-level PM2.5 at any of the catalog metros.

Official record

Dayton, OH surface conditions, 2003-06-24 to 2003-06-25

National Weather Service surface observations via Iowa Environmental Mesonet

WRIGHT PATERSON recorded calm conditions during 0% of event hours and wind at or below three knots during 60%. Observations included 9 haze hours, 9 mist hours, minimum visibility 2 miles.

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

A single surface station documents weak ventilation and obscuration but not the full vertical profile or particle source mix.

Official record

Dayton, OH joint pollution fingerprint, 2003-06-24 to 2003-06-25

U.S. EPA AirData

EPA records show median daily PM2.5 of 45.575 micrograms per cubic meter across 3 monitors, 2.45 times the adjacent-window level. Co-pollutants at least 10% above the adjacent-window comparison were carbon monoxide (1.451x), sulfur dioxide (2.661x).

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

The broad multi-pollutant response does not apportion traffic, heating, industry, wood combustion, or secondary aerosol.

Official record

AQI Toolkit for Weathercasters: Midwest ozone progression on June 25, 2003

U.S. Environmental Protection Agency AirNow

EPA's teaching case preserves the hour-by-hour Midwest ozone maps for June 25, 2003, including Dayton and Columbus in the mapped regional air-quality progression.

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

The maps are for ozone, not PM2.5, and establish a regional polluted-air episode rather than a particulate source allocation.

Official record

AQI Toolkit for Weathercasters: Midwest ozone progression on June 25, 2003

U.S. Environmental Protection Agency AirNow

EPA's teaching case preserves the hour-by-hour Midwest ozone maps for June 25, 2003, including Dayton and Columbus in the mapped regional air-quality progression.

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

The maps are for ozone, not PM2.5, and establish a regional polluted-air episode rather than a particulate source allocation.

Show 1 more retained source

Official record

Air Quality Trends Report: June 23-25, 2003 Northeast Ohio ozone exceedances

Northeast Ohio Areawide Coordinating Agency

NOACA's historical trend table records widespread eight-hour ozone exceedances across Northeast Ohio on June 23, 24, and 25, with seven to ten monitors exceeding the standard on each day.

What it supports

This source supports a possible mechanism or occurrence; it does not establish the cause by itself.

Limit

Ozone documents a regional photochemical-pollution episode but does not determine the composition or source fractions of the simultaneous PM2.5.

What remains uncertain

Status and provenance

Possible This is a transparent hypothesis supported by limited evidence or an explicit inference, not a definitive attribution.

This episode was grouped from the monitor record by the catalog pipeline and given its cause from the evidence listed above. It has not been individually reviewed and signed off, so its boundaries, cause, and name may change as evidence accumulates. Grouping policy common_sense_root_cause_grouping.v2. The cause label reflects the assembled evidence above, not an IAQng detection formula. If it is wrong, tell us.