134% above nearby days
Fireworks Possible
2000-01-01 Baltimore-Columbia-Towson, MD and Harrisburg-Carlisle, PA fireworks episode
Daily PM2.5 peaked at 62.3 µg/m³ near Baltimore across 2 covered metros home to 3.5 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 ≈ 2.3 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 8.0 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 “Fireworks”
The event falls exactly in the versioned New Year or Independence Day window and no competing event-specific cause was recovered.
Possible This is a transparent hypothesis supported by limited evidence or an explicit inference, not a definitive attribution.
Inference, not direct attribution
Holiday timing: The event falls in the July 3–5 or December 31–January 1 fireworks window. That makes fireworks a reasonable hypothesis, but no retained source directly attributes this event.
Sequence: Baltimore (Jan 1) → Harrisburg (Jan 1)
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.
- 1Inferred
Source or mechanism
Pattern-based explanation
Holiday timing. The event falls in the July 3–5 or December 31–January 1 fireworks window. That makes fireworks a reasonable hypothesis, but no retained source directly attributes this event.
- 2Research gap
Air-mass movement
The transport path has not been reconstructed
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.
- 3Documented
Local response
62.3 µg/m³ near Baltimore
EPA monitors recorded the event across 2 metros. The peak daily concentration is roughly 2.8 cigarette-equivalents at the outdoor daily rate.
Inspect the pollutant and weather signals ↓
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 “Fireworks” explanation; it does not assign the cause by itself.
Baltimore-Columbia-Towson, MD
Monitor comparison window 1999-12-29 to 2000-01-04 · PM2.5 target: Northwest Police Station
No adjacent-day comparison
Pollution fingerprint
Metro-wide median of reporting monitors PM2.5 56.3 µg/m³
134% higher than surrounding days
Before16.7 µg/m³ Event56.3 µg/m³ After20.9 µg/m³
PM10 37.5 µg/m³
No adjacent-day comparison
Before— Event37.5 µg/m³ After—
Carbon monoxide 2.01 ppm
129% higher than surrounding days
Before1.15 ppm Event2.01 ppm After0.646 ppm
Nitrogen dioxide 21.7 ppb
About the same as surrounding days
Before23 ppb Event21.7 ppb After21.1 ppb
Sulfur dioxide 7.92 ppb
14% higher than surrounding days
Before8.13 ppb Event7.92 ppb After3.83 ppb
Ozone 0.003 ppm
80% lower than surrounding days
Before0.008 ppm Event0.003 ppm After0.020 ppm
Atmospheric conditions
Nearby EPA weather observations12% higher than surrounding days
About the same as surrounding days
20% lower than surrounding days
Harrisburg-Carlisle, PA
Monitor comparison window 1999-12-29 to 2000-01-04 · PM2.5 target: Harrisburg
35% above nearby days
51% higher than surrounding days
Pollution fingerprint
Metro-wide median of reporting monitors PM2.5 40.5 µg/m³
35% higher than surrounding days
Before11.6 µg/m³ Event40.5 µg/m³ After30 µg/m³
Carbon monoxide 0.483 ppm
51% higher than surrounding days
Before0.321 ppm Event0.483 ppm After0.229 ppm
Nitrogen dioxide 15.2 ppb
About the same as surrounding days
Before14.8 ppb Event15.2 ppb After14.4 ppb
Sulfur dioxide 1.69 ppb
34% lower than surrounding days
Before4.42 ppb Event1.69 ppb After1.73 ppb
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
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.
Affected metros
| Metro | Peak PM2.5 | Cigarettes, whole event | Peak day | All-time standing |
|---|---|---|---|---|
| Baltimore-Columbia-Towson, MD | 62.3 µg/m³ | 2.8 | Jan 1, 2000 | #8 of its top days |
| Harrisburg-Carlisle, PA | 58.5 µg/m³ | 2.7 | Jan 1, 2000 | #15 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.
Holiday timing pattern
IAQng deterministic inference policy
The event peak falls on 2000-01-01 and the event lasts no more than two days. Under holiday_fireworks_possible.v1, that timing is consistent with a possible fireworks contribution.
What it supports
A possible fireworks contribution; this is a reproducible inference, not direct occurrence or causal evidence.
Limit
Pre-event and post-event temporal-shape data were not supplied.
No news search has been run for this episode. Its evidence is agency records only, and an absent article is not a finding that none exists.
What remains uncertain
- No exact local official attribution was recovered, so confidence remains possible.
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.