Industrial Possible
Daily PM2.5 peaked at 82.2 µg/m³ near Pittsburgh across 1 covered metro home to 2.4 million people. 1 metro placed a top-ten day in their record.
Counting the extra PM2.5 above each metro's typical day, this event handed the average affected resident ≈ 3.1 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 7.5 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 October 8 PM2.5 peak was concentrated at the Liberty monitor rather than spread across Pittsburgh: Liberty measured 82.2 micrograms per cubic meter while Lawrenceville measured 14.7. Same-day PM10 was also concentrated in the Mon Valley, reaching 109 at Liberty, 126 at Glassport, and 162 at Lincoln while most other county sites measured 25 to 36. Exact NWS discussions place high pressure over the area before the event and describe light winds and localized morning fog. Allegheny County's official Liberty-Clairton plan identifies the monitor as affected by both regional background and localized industrial sources and identifies nearby Mon Valley facilities as the dominant local source complex. The convergence supports broad industrial emissions at possible confidence, without assigning the day to one facility.
Possible This is a transparent hypothesis supported by limited evidence or an explicit inference, not a definitive attribution.
U.S. EPA AirData hypothesis
EPA's certified daily records show 82.2 micrograms per cubic meter of PM2.5 at Liberty (42-003-0064) and 14.7 at Lawrenceville (42-003-0008) on the same day. The large within-county contrast shows that the catalog peak was concentrated in the Liberty area rather than representative of the entire Pittsburgh metro.
National Weather Service Pittsburgh via Iowa Environmental Mesonet · Oct 8, 2004 hypothesis
NWS Pittsburgh reported high pressure dominating October 7, mainly clear skies and light winds overnight, localized river-valley restrictions and morning fog, and the ridge still over the area on October 8 before an approaching cold front. The exact surface record showed high pressure but moderate southerly wind later in the day.
U.S. EPA AirData hypothesis
EPA's same-day PM10 records show 109 micrograms per cubic meter at Liberty, 126 at Glassport, and 162 at Lincoln. Braddock measured 52, while Avalon, a site downwind from the former LTV facility, Flag Plaza, and Stowe Township measured 25 to 36. The coarse-plus-fine response was concentrated in the Mon Valley industrial corridor.
Inference, not direct attribution
exact_mon_valley_spatial_contrast_plus_official_industrial_source_regime_possible.v1: This inference is recorded in the catalog methodology.
Evidence path
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.
Source or mechanism
exact_mon_valley_spatial_contrast_plus_official_industrial_source_regime_possible.v1. This inference is recorded in the catalog methodology.
Air-mass movement
The retained record does not yet show how air traveled from the proposed source to these metros. A trajectory replay or dated plume analysis belongs here.
Local response
EPA monitors recorded the event across 1 metro. The peak daily concentration is roughly 3.7 cigarette-equivalents at the outdoor daily rate.
Inspect the pollutant and weather signals ↓Event autopsy
Before, during, and after the episode: nearby pollutant monitors and surface-weather stations show what changed. This context tests the “Industrial” explanation; it does not assign the cause by itself.
Pittsburgh, PA
Monitor comparison window 2004-10-05 to 2004-10-11 · PM2.5 target: Liberty
292% above nearby days
14 kt maximum
0 hours at or below 3 miles
292% higher than surrounding days
16% higher than surrounding days
73% higher than surrounding days
28% higher than surrounding days
About the same as surrounding days
23% higher than surrounding days
14 kt maximum · No calm observed hours
0 observed hours at or below 3 miles
48°F to 75°F
96% 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.
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
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.
No useful public camera views are currently available within 80 km of this metro.
| Metro | Peak PM2.5 | Cigarettes, whole event | Peak day | All-time standing |
|---|---|---|---|---|
| Pittsburgh, PA | 82.2 µg/m³ | 3.7 | Oct 8, 2004 | #9 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
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.
Allegheny County Health Department
Allegheny County's official plan says Liberty-Clairton is affected by regional background, Pittsburgh urban activity, and localized sources. Its source-apportionment and fine-grid modeling identify nearby Mon Valley facilities as those most likely to drive concentrations at Liberty; the listed major local sources include U.S. Steel's Clairton, Edgar Thomson, and Irvin plants along with other industrial facilities.
Context for the event; this item does not establish the attributed cause by itself.
The official source analysis uses a later modeling baseline and characterizes the recurring Liberty-Clairton source regime rather than October 8, 2004 alone.
National Weather Service Pittsburgh via Iowa Environmental Mesonet
NWS Pittsburgh reported high pressure dominating October 7, mainly clear skies and light winds overnight, localized river-valley restrictions and morning fog, and the ridge still over the area on October 8 before an approaching cold front. The exact surface record showed high pressure but moderate southerly wind later in the day.
This source supports a possible mechanism or occurrence; it does not establish the cause by itself.
The discussions support limited early ventilation but do not explicitly diagnose a temperature inversion or attribute the PM2.5.
U.S. EPA AirData
EPA's certified daily records show 82.2 micrograms per cubic meter of PM2.5 at Liberty (42-003-0064) and 14.7 at Lawrenceville (42-003-0008) on the same day. The large within-county contrast shows that the catalog peak was concentrated in the Liberty area rather than representative of the entire Pittsburgh metro.
This source supports a possible mechanism or occurrence; it does not establish the cause by itself.
The Pittsburgh label is metro shorthand; the strongest measured response was localized around Liberty and nearby Mon Valley monitors.
U.S. EPA AirData
EPA's same-day PM10 records show 109 micrograms per cubic meter at Liberty, 126 at Glassport, and 162 at Lincoln. Braddock measured 52, while Avalon, a site downwind from the former LTV facility, Flag Plaza, and Stowe Township measured 25 to 36. The coarse-plus-fine response was concentrated in the Mon Valley industrial corridor.
This source supports a possible mechanism or occurrence; it does not establish the cause by itself.
PM10 spatial contrast does not identify the emitting facility or determine how much of the PM2.5 was primary versus secondary.
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.