← Air events

Temperature inversion Possible

2005-02-06 Buffalo-Cheektowaga-Niagara Falls, NY temperature-inversion pollution episode

February 6, 2005

Daily PM2.5 peaked at 47.1 µg/m³ near Buffalo across 1 covered metro home to 1.2 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 ≈ 1.8 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 2.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 “Temperature inversion”

Buffalo's three-monitor PM2.5 rise and compatible carbon-monoxide and nitrogen-dioxide increases occurred with 11 hours of haze, eight hours of mist, restricted visibility, and mostly calm or light wind. The exact-window NWS discussion independently documented an extreme inversion and little mixing during the event day. Together these support temperature-inversion trapping at possible confidence while leaving the trapped emissions unidentified.

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

U.S. EPA AirData hypothesis

Buffalo-Cheektowaga-Niagara Falls, NY joint pollution fingerprint, 2005-02-06

EPA records show median daily PM2.5 of 35 micrograms per cubic meter across 3 monitors, 1.411 times the adjacent-window level. Co-pollutants at least 10% above the adjacent-window comparison were carbon monoxide (2.209x), nitrogen dioxide (1.19x). Other measured comparisons were sulfur dioxide (0.719x).

National Weather Service surface observations via Iowa Environmental Mesonet · Feb 6, 2005 hypothesis

Buffalo-Cheektowaga-Niagara Falls, NY surface conditions, 2005-02-06

NIAGARA FALLS INTL recorded calm conditions during 63% of event hours and wind at or below three knots during 79%. Observations included 11 haze hours, 8 mist hours, minimum visibility 0.25 miles.

National Weather Service Buffalo via Iowa Environmental Mesonet · Feb 5, 2005 hypothesis

Area Forecast Discussion: extreme inversion and little mixing

The forecast issued before the event day described an inversion so extreme that fog could redevelop nearly anywhere and expected little mixing on February 6 despite a somewhat stronger southerly gradient.

Inference, not direct attribution

Documented inversion overlap: The event overlaps a documented inversion period, but the retained material does not directly attribute the measured PM2.5 episode.

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 inversion overlap. The event overlaps a documented inversion period, but the retained material does not directly attribute the measured PM2.5 episode.

    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

    47.1 µg/m³ near Buffalo

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

Observed context · not attribution

Buffalo-Cheektowaga-Niagara Falls, NY

Monitor comparison window 2005-02-03 to 2005-02-09 · PM2.5 target: NIAGARA FALLS

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

0% above nearby days

Air movement 0 kt median wind

15 calm hours observed

What observers saw 0.25 mi minimum visibility

Haze reported during 11 hours

Pollution fingerprint

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

About the same as surrounding days

Before39.7 µg/m³ Event35 µg/m³ After9.90 µg/m³
3 monitors · 24 HOUR
Carbon monoxide 0.990 ppm

59% higher than surrounding days

Before0.623 ppm Event0.990 ppm After0.273 ppm
2 monitors · 1 HOUR
Nitrogen dioxide 41.9 ppb

About the same as surrounding days

Before43.1 ppb Event41.9 ppb After27.3 ppb
2 monitors · 1 HOUR
Sulfur dioxide 5.96 ppb

24% lower than surrounding days

Before10.3 ppb Event5.96 ppb After6.25 ppb
3 monitors · 1 HOUR
Ozone 0.022 ppm

177% higher than surrounding days

Before0.007 ppm Event0.022 ppm After0.008 ppm
1 monitor · 8-HR RUN AVG BEGIN HOUR

Atmospheric conditions

NIAGARA FALLS INTL, 5.3 km from the PM2.5 target
Wind 0 kt median

8 kt maximum · 15 of 24 observed hours calm

Visibility 0.25 mi minimum

9 observed hours at or below 3 miles

Temperature 35.5°F median

17°F to 51°F

Humidity 71% median

92% 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
Buffalo-Cheektowaga-Niagara Falls, NY 47.1 µg/m³ 2.1 Feb 6, 2005 #10 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.

4 retained sources

Official record

New York recommendations for the 2006 PM2.5 designations

New York State Department of Environmental Conservation

New York's assessment of Buffalo's highest PM2.5 days in 2004-2006 found stable winds from the west through south, significant upwind-state transport, and a typical high-day composition of roughly half sulfate, indicating aged regional combustion pollution.

What it supports

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

Limit

The assessment characterizes Buffalo's high-PM days generally and does not identify February 6, 2005 as an analyzed example.

Official record

Buffalo-Cheektowaga-Niagara Falls, NY surface conditions, 2005-02-06

National Weather Service surface observations via Iowa Environmental Mesonet

NIAGARA FALLS INTL recorded calm conditions during 63% of event hours and wind at or below three knots during 79%. Observations included 11 haze hours, 8 mist hours, minimum visibility 0.25 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

Area Forecast Discussion: extreme inversion and little mixing

National Weather Service Buffalo via Iowa Environmental Mesonet

The forecast issued before the event day described an inversion so extreme that fog could redevelop nearly anywhere and expected little mixing on February 6 despite a somewhat stronger southerly gradient.

What it supports

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

Limit

The NWS discussion establishes an extreme inversion and limited mixing but does not identify the particle sources below it.

Official record

Buffalo-Cheektowaga-Niagara Falls, NY joint pollution fingerprint, 2005-02-06

U.S. EPA AirData

EPA records show median daily PM2.5 of 35 micrograms per cubic meter across 3 monitors, 1.411 times the adjacent-window level. Co-pollutants at least 10% above the adjacent-window comparison were carbon monoxide (2.209x), nitrogen dioxide (1.19x). Other measured comparisons were sulfur dioxide (0.719x).

What it supports

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

Limit

The pollution fingerprint does not uniquely apportion traffic, heating, industry, wood combustion, or secondary aerosol.

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.