July 15–20, 2026 Great Lakes and eastern U.S. wildfire-smoke episode
July 15, 2026 to July 20, 2026 · Origin: Canada; Northern Minnesota
Daily PM2.5 peaked at 387.8 µg/m³ near Toledo across
32 covered metros home to 86 million people.
14 metros recorded their worst day on record; 27 placed a top-ten day.
Counting the extra PM2.5 above each metro's typical day, this event handed the
average affected resident ≈ 13.0 cigarettes.
Across everyone living in the affected metros, that is the collective equivalent of
≈ 1.1 billion 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 “Wildfire smoke”
The supplied evidence supports wildfire smoke and documents an overlapping or continuing regional occurrence across the proposed members. The supplied evidence supports wildfire smoke and documents an overlapping or continuing regional occurrence a
Agency determinationA government body issued a record naming this cause for this event: an NWS air-quality alert, a NOAA Storm Events record, or a state or local official archive.
U.S. EPA Air Quality System and the submitting air monitoring agency · Jul 17, 2026official
EPA AQS carries an agency-submitted informational qualifier (IF, Fire - Canadian.) on 4 PM2.5 samples in the candidate CBSA on 2026-07-17, identifying wildfire smoke as affecting the samples. An informational qualifier is an official submitting-agency flag, not a request for exclusion or an EPA-concurred determination.
Michigan Department of Environment, Great Lakes, and Energy · Jul 16, 2026official
Michigan EGLE's July 16 update kept a PM2.5 alert in effect through July 17 and explicitly attributed the fine particles to wildfire smoke; this directly covers Detroit. IEM is the archive, not the official system of record.
Michigan Department of Environment, Great Lakes, and Energy · Jul 16, 2026official
Michigan EGLE issued a July 16-17 fine-particle alert explicitly due to wildfire smoke, directly covering Grand Rapids. IEM is the archive, not the official system of record.
Sequence: Detroit (Jul 15) → Milwaukee (Jul 15) → Minneapolis (Jul 15) → New York (Jul 15) → Rochester (Jul 15) → Toledo (Jul 16) → Chicago (Jul 16) → Grand Rapids (Jul 16) → Cleveland (Jul 16) → Columbus (Jul 16) → +22 more metros
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.
EPA AQS carries an agency-submitted informational qualifier (IF, Fire - Canadian.) on 4 PM2.5 samples in the candidate CBSA on 2026-07-17, identifying wildfire smoke as affecting the samples. An informational qualifier is an official…
Contemporaneous reporting identified heavy smoke from fires primarily in Canada and northern Minnesota extending from the Great Lakes to the East Coast.
Before, during, and after the episode: nearby pollutant monitors and surface-weather
stations show what changed. This context tests the “Wildfire smoke” explanation; it does
not assign the cause by itself.
Observed context · not attribution
Detroit-Warren-Dearborn, MI
Monitor comparison window 2026-07-12 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Akron, OH
Monitor comparison window 2026-07-12 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Cleveland-Elyria, OH
Monitor comparison window 2026-07-12 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Toledo, OH
Monitor comparison window 2026-07-12 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Milwaukee-Waukesha-West Allis, WI
Monitor comparison window 2026-07-12 to 2026-07-22
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Chicago-Naperville-Elgin, IL-IN-WI
Monitor comparison window 2026-07-12 to 2026-07-22
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Grand Rapids-Wyoming, MI
Monitor comparison window 2026-07-12 to 2026-07-22
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Columbus, OH
Monitor comparison window 2026-07-13 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Pittsburgh, PA
Monitor comparison window 2026-07-13 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Madison, WI
Monitor comparison window 2026-07-13 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Minneapolis-St. Paul-Bloomington, MN-WI
Monitor comparison window 2026-07-12 to 2026-07-19
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Harrisburg-Carlisle, PA
Monitor comparison window 2026-07-13 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Philadelphia-Camden-Wilmington, PA-NJ-DE-MD
Monitor comparison window 2026-07-13 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Baltimore-Columbia-Towson, MD
Monitor comparison window 2026-07-13 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Washington-Arlington-Alexandria, DC-VA-MD-WV
Monitor comparison window 2026-07-13 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
New York-Newark-Jersey City, NY-NJ-PA
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Albany-Schenectady-Troy, NY
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Allentown-Bethlehem-Easton, PA-NJ
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Bridgeport-Stamford-Norwalk, CT
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Hartford-West Hartford-East Hartford, CT
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
New Haven-Milford, CT
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Scranton--Wilkes-Barre--Hazleton, PA
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Rochester, NY
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Buffalo-Cheektowaga-Niagara Falls, NY
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Syracuse, NY
Monitor comparison window 2026-07-12 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Richmond, VA
Monitor comparison window 2026-07-14 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Virginia Beach-Norfolk-Newport News, VA-NC
Monitor comparison window 2026-07-14 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Dayton, OH
Monitor comparison window 2026-07-14 to 2026-07-20
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Boston-Cambridge-Newton, MA-NH
Monitor comparison window 2026-07-15 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Springfield, MA
Monitor comparison window 2026-07-15 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Worcester, MA-CT
Monitor comparison window 2026-07-15 to 2026-07-21
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
Indianapolis-Carmel-Anderson, IN
Monitor comparison window 2026-07-16 to 2026-07-22
0 pollutant signals
No comparable co-pollutant or weather observations were available.
The PM2.5 event remains in the catalog, but the surrounding monitoring record cannot supply a defensible instrument fingerprint for this place and date.
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.
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.
"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.
U.S. EPA Air Quality System and the submitting air monitoring agency · Jul 17, 2026officialgovernment
EPA AQS carries an agency-submitted informational qualifier (IF, Fire - Canadian.) on 4 PM2.5 samples in the candidate CBSA on 2026-07-17, identifying wildfire smoke as affecting the samples. An informational qualifier is an official submitting-agency flag, not a request for exclusion or an EPA-concurred determination.
Michigan Department of Environment, Great Lakes, and Energy · Jul 16, 2026officialgovernment
Michigan EGLE's July 16 update kept a PM2.5 alert in effect through July 17 and explicitly attributed the fine particles to wildfire smoke; this directly covers Detroit. IEM is the archive, not the official system of record.
Michigan Department of Environment, Great Lakes, and Energy · Jul 16, 2026officialgovernment
Michigan EGLE issued a July 16-17 fine-particle alert explicitly due to wildfire smoke, directly covering Grand Rapids. IEM is the archive, not the official system of record.
Illinois EPA issued a July 17 Air Quality Action Day explicitly for wildfire smoke and PM2.5, directly covering Chicago. IEM is the archive, not the official system of record.
West Virginia Department of Environmental Protection · Jul 17, 2026officialgovernment
West Virginia's alert attributed unhealthy to very unhealthy fine-particle concentrations during July 17-18 to wildfire smoke. It supports only the West Virginia portion of the Washington regional metro candidate. IEM is the archive, not the official system of record.
Indiana Department of Environmental Management · Jul 19, 2026officialgovernment
Indiana's July 19 alert tied observed and forecast high PM2.5 to wildfire-smoke exposure and applied to Indianapolis. IEM is the archive, not the official system of record.
Illinois EPA's July 19 alert linked observed and forecast elevated PM2.5 to wildfire smoke, directly covering Chicago. IEM is the archive, not the official system of record.
New Jersey Department of Health · Jul 17, 2026officialgovernment
New Jersey Health reported that smoke from ongoing Canadian wildfires was drifting across the state and region, causing unhealthy air quality and hazy skies.
Pennsylvania Department of Environmental Protection · Jul 17, 2026officialgovernment
Pennsylvania DEP attributed the prior day's Code Purple and Code Red conditions, including southeastern Pennsylvania, to wildfire smoke from Canada and the northern U.S.
Contemporaneous reporting identified heavy smoke from fires primarily in Canada and northern Minnesota extending from the Great Lakes to the East Coast.
The supplied evidence does not identify or quantify every specific source contributing across all proposed members.
Status and provenance
Agency determinationA government body issued a record naming this cause for this event: an NWS air-quality alert, a NOAA Storm Events record, or a state or local official archive.
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.
Recent days are preliminary AirNow readings and re-rank once EPA certifies them. 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.