← Air events

Stagnant pollution mixture Possible

2000-10-29 to 2000-10-30 Tampa-St. Petersburg-Clearwater, FL stagnant mixed-pollution episode

October 29, 2000 to October 30, 2000

Daily PM2.5 peaked at 75.3 µg/m³ near Tampa across 1 covered metro home to 3.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 ≈ 4.8 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 16 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 “Stagnant pollution mixture”

Exact-window NWS discussions document persistent haze under weak flow and blocking high pressure. Certified EPA observations independently show simultaneous elevations across PM2.5, PM10, CO, NO2, and SO2. This supports a mixed-pollution accumulation mechanism, but not a dominant source.

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

National Weather Service Tampa Bay via Iowa Environmental Mesonet · Oct 30, 2000 hypothesis

Area Forecast Discussions: persistent haze under light flow and blocking high pressure

Across the October 29-30 event window, NWS Tampa Bay repeatedly described lingering or patchy haze, light or nearly calm low-level winds, an omega blocking pattern and upper ridge, surface high pressure, and a weak front expected to stall or dissipate. Haze was still present early October 31.

U.S. EPA AirData hypothesis

Tampa multi-monitor pollution fingerprint, October 29-30, 2000

IAQng's reproducible aggregation of certified EPA rows found that Tampa-area PM2.5 rose during October 29-30 along with PM10, carbon monoxide, nitrogen dioxide, and sulfur dioxide. Event-window averages were approximately 44.9 µg/m³ PM2.5, 64.5 µg/m³ PM10, 0.88 ppm CO, 22.2 ppb NO2, and 4.9 ppb SO2, all above the immediately preceding comparison window; one PM2.5 site reached 75.3 µg/m³.

Inference, not direct attribution

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

See every retained source and limitation ↓

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

    Pattern-based explanation

    documented_stagnation_overlap_possible.v1. This inference is recorded in the catalog methodology.

    Inferred
  2. 2

    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.

    Research gap
  3. 3

    Local response

    75.3 µg/m³ near Tampa

    EPA monitors recorded the event across 1 metro. The peak daily concentration is roughly 3.4 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 “Stagnant pollution mixture” explanation; it does not assign the cause by itself.

Observed context · not attribution

Tampa-St. Petersburg-Clearwater, FL

Monitor comparison window 2000-10-26 to 2000-11-02 · PM2.5 target: DUNEDIN HIGHLAND MIDDLE SCHOOL

6 pollutant signals
Fine-particle pulse 44.9 µg/m³

127% above nearby days

PM10 64.5 µg/m³

50% higher than surrounding days

Pollution fingerprint

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

127% higher than surrounding days

Before13.5 µg/m³ Event44.9 µg/m³ After16.9 µg/m³
4 monitors · 24 HOUR
PM10 64.5 µg/m³

50% higher than surrounding days

Before23 µg/m³ Event64.5 µg/m³ After41 µg/m³
1 monitor · 24-HR BLK AVG
Carbon monoxide 0.884 ppm

15% higher than surrounding days

Before0.581 ppm Event0.884 ppm After0.771 ppm
6 monitors · 1 HOUR
Nitrogen dioxide 22.2 ppb

21% higher than surrounding days

Before9.67 ppb Event22.2 ppb After25.5 ppb
3 monitors · 1 HOUR
Sulfur dioxide 4.89 ppb

61% higher than surrounding days

Before1.77 ppb Event4.89 ppb After2.65 ppb
10 monitors · 1 HOUR
Ozone 0.045 ppm

17% higher than surrounding days

Before0.039 ppm Event0.045 ppm After0.035 ppm
9 monitors · 8-HR RUN AVG BEGIN HOUR

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
Tampa-St. Petersburg-Clearwater, FL 75.3 µg/m³ 5.6 Oct 30, 2000 #2 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.

2 retained sources

Official record

Area Forecast Discussions: persistent haze under light flow and blocking high pressure

National Weather Service Tampa Bay via Iowa Environmental Mesonet

Across the October 29-30 event window, NWS Tampa Bay repeatedly described lingering or patchy haze, light or nearly calm low-level winds, an omega blocking pattern and upper ridge, surface high pressure, and a weak front expected to stall or dissipate. Haze was still present early October 31.

What it supports

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

Limit

The discussions establish a locally relevant weak-ventilation and haze setting but do not chemically identify the particles or name the dominant emissions source.

Official record

Tampa multi-monitor pollution fingerprint, October 29-30, 2000

U.S. EPA AirData

IAQng's reproducible aggregation of certified EPA rows found that Tampa-area PM2.5 rose during October 29-30 along with PM10, carbon monoxide, nitrogen dioxide, and sulfur dioxide. Event-window averages were approximately 44.9 µg/m³ PM2.5, 64.5 µg/m³ PM10, 0.88 ppm CO, 22.2 ppb NO2, and 4.9 ppb SO2, all above the immediately preceding comparison window; one PM2.5 site reached 75.3 µg/m³.

What it supports

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

Limit

The fingerprint demonstrates a mixed pollution episode but does not apportion the PM2.5 to particular sources.

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.