Stagnant pollution mixture Possible
Daily PM2.5 peaked at 55.5 µg/m³ near Washington across 2 covered metros home to 9.3 million people.
Counting the extra PM2.5 above each metro's typical day, this event handed the average affected resident ≈ 4.2 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 39 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
Manual research connected 2 source events to one stagnant mixed-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.
MARAMA / Maryland Department of the Environment · Sep 30, 2004 official
MARAMA's official assessment lists the exact July 2 PM2.5 values for Washington and Baltimore and describes July 1-4 as a widespread multi-day episode in which an upper-level ridge, weaker winds, suppressed precipitation, and regional buildup produced high PM.
See every retained source and limitation ↓
Sequence: Washington (Jul 2) → Baltimore (Jul 2)
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
MARAMA's official assessment lists the exact July 2 PM2.5 values for Washington and Baltimore and describes July 1-4 as a widespread multi-day episode in which an upper-level ridge, weaker winds, suppressed precipitation, and regional buildup…
View supporting source ↗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 2 metros. The peak daily concentration is roughly 2.5 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 “Stagnant pollution mixture” explanation; it does not assign the cause by itself.
Washington-Arlington-Alexandria, DC-VA-MD-WV
Monitor comparison window 2002-06-29 to 2002-07-05 · PM2.5 target: RIVER TERRACE
124% above nearby days
17% higher than surrounding days
124% higher than surrounding days
17% higher than surrounding days
About the same as surrounding days
53% higher than surrounding days
23% higher than surrounding days
About the same as surrounding days
About the same as surrounding days
Baltimore-Columbia-Towson, MD
Monitor comparison window 2002-06-29 to 2002-07-06 · PM2.5 target: Oldtown
107% above nearby days
About the same as surrounding days
107% higher than surrounding days
About the same as surrounding days
51% higher than surrounding days
46% higher than surrounding days
11% higher than surrounding days
About the same as surrounding days
About the same as surrounding days
About the same as surrounding days
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 |
|---|---|---|---|---|
| Washington-Arlington-Alexandria, DC-VA-MD-WV | 55.5 µg/m³ | 5.3 | Jul 2, 2002 | #11 of its top days |
| Baltimore-Columbia-Towson, MD | 54.1 µg/m³ | 4.8 | Jul 2, 2002 | #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
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.
MARAMA / Maryland Department of the Environment
MARAMA's official assessment lists the exact July 2 PM2.5 values for Washington and Baltimore and describes July 1-4 as a widespread multi-day episode in which an upper-level ridge, weaker winds, suppressed precipitation, and regional buildup produced high PM.
An official source supports the attributed cause for the stated place and dates.
The assessment identifies a regional accumulation mechanism, not a single emitting source or source-specific daily mass.
MARAMA / Maryland Department of the Environment
MARAMA's official assessment lists the exact July 2 PM2.5 values for Washington and Baltimore and describes July 1-4 as a widespread multi-day episode in which an upper-level ridge, weaker winds, suppressed precipitation, and regional buildup produced high PM.
An official source supports the attributed cause for the stated place and dates.
The assessment identifies a regional accumulation mechanism, not a single emitting source or source-specific daily mass.
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.