← Air events

Temperature inversion Likely

2007-01-26 to 2007-01-30 Ogden-Clearfield, UT, Provo-Orem, UT, and 1 other metros temperature-inversion pollution episode

January 26, 2007 to January 30, 2007

Daily PM2.5 peaked at 86.6 µg/m³ near Salt Lake City across 3 covered metros home to 2.7 million people. 2 metros 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 ≈ 11.0 cigarettes. Across everyone living in the affected metros, that is the collective equivalent of ≈ 30 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”

Manual research connected 2 source events to one temperature-inversion pollution episode using the deterministic grouping rule.

Likely Applicable reporting or a supported inference makes this the best current causal explanation.

KSL / Associated Press · Jan 30, 2007 corroborates

Utah valleys smothered by inversion

Contemporaneous reporting says a Wasatch Front inversion trapped exhaust and particles from factories, furnaces, and fireplaces during the supplied January 26-30 episode.

KSL · Jan 30, 2007 corroborates

A Good Wind, Please: Utah Waits for Clear Air

KSL reported on January 30 that northern Utah's valleys were under a persistent inversion trapping car exhaust, industrial emissions, furnace particles, and fireplace smoke, with unhealthy air persisting through much of January.

Daily Kos · Jan 27, 2007 hypothesis

Salt Lake inversion community report

An exact-date community account independently describes the prolonged Salt Lake inversion and Code Red PM2.5 conditions on January 26-27.

See every retained source and limitation ↓

Sequence: Salt Lake City (Jan 26) → Ogden (Jan 27) → Provo (Jan 27)

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

    Temperature inversion

    Contemporaneous reporting says a Wasatch Front inversion trapped exhaust and particles from factories, furnaces, and fireplaces during the supplied January 26-30 episode.

    View supporting source ↗
    Documented
  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

    86.6 µg/m³ near Salt Lake City

    EPA monitors recorded the event across 3 metros. The peak daily concentration is roughly 3.9 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

Salt Lake City, UT

Monitor comparison window 2007-01-23 to 2007-02-02 · PM2.5 target: Hawthorne

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

24% above nearby days

PM10 105 µg/m³

About the same as surrounding days

Pollution fingerprint

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

24% higher than surrounding days

Before45.4 µg/m³ Event78 µg/m³ After11.9 µg/m³
7 monitors · 24 HOUR
PM10 105 µg/m³

About the same as surrounding days

Before83 µg/m³ Event105 µg/m³ After32.5 µg/m³
4 monitors · 24 HOUR
Carbon monoxide 1.71 ppm

12% higher than surrounding days

Before1.57 ppm Event1.71 ppm After0.754 ppm
3 monitors · 1 HOUR
Nitrogen dioxide 62.5 ppb

14% higher than surrounding days

Before54.9 ppb Event62.5 ppb After31.4 ppb
2 monitors · 1 HOUR
Sulfur dioxide 2.42 ppb

7% higher than surrounding days

Before2.88 ppb Event2.42 ppb After1.50 ppb
3 monitors · 1 HOUR
Ozone 0.006 ppm

About the same as surrounding days

Before0.003 ppm Event0.006 ppm After0.016 ppm
1 monitor · 8-HR RUN AVG BEGIN HOUR

Atmospheric conditions

Nearby EPA weather observations
Humidity 76.4 %

About the same as surrounding days

Temperature 23.3 °F

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.

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
Salt Lake City, UT 86.6 µg/m³ 18.5 Jan 27, 2007 #3 of its top days
Ogden-Clearfield, UT 76.8 µg/m³ 6.5 Jan 30, 2007 #3 of its top days
Provo-Orem, UT 74.8 µg/m³ 6.7 Jan 27, 2007 #21 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.

3 retained sources

News report

Utah valleys smothered by inversion

KSL / Associated Press

Contemporaneous reporting says a Wasatch Front inversion trapped exhaust and particles from factories, furnaces, and fireplaces during the supplied January 26-30 episode.

What it supports

A retained source supports the attributed cause for the stated place and dates.

Limit

The report identifies the trapping mechanism but does not apportion the emissions mixture.

News report

A Good Wind, Please: Utah Waits for Clear Air

KSL

KSL reported on January 30 that northern Utah's valleys were under a persistent inversion trapping car exhaust, industrial emissions, furnace particles, and fireplace smoke, with unhealthy air persisting through much of January.

What it supports

A retained source supports the attributed cause for the stated place and dates.

Limit

The story discusses northern Utah's multi-valley episode and specifically cites Salt Lake and Davis counties rather than publishing separate Provo and Ogden source apportionment.

Community report

Salt Lake inversion community report

Daily Kos

An exact-date community account independently describes the prolonged Salt Lake inversion and Code Red PM2.5 conditions on January 26-27.

What it supports

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

Limit

Community reporting corroborates timing and conditions but is not an official attribution.

What remains uncertain

Status and provenance

Likely Applicable reporting or a supported inference makes this the best current causal explanation.

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.