A verified record of the fires that burned into the city of Spokane on August 1, 2026 — what happened, what the air did to three towns across one state, and why. Every number here carries a source. Where no source could be verified, this site says so instead of guessing.
Verified only. Every figure is attributed to a named source and stamped with the time it was reported. Wildfire numbers change hourly, so an acreage figure without a timestamp is close to meaningless.
Where credible sources disagree — and on this event they disagree a lot — both numbers are printed. Nothing is averaged into a tidy single answer. Today's clearest example is Spokane's own air quality, where two views of the same monitor returned 63 and 183 within hours of each other. Both are on the page.
Gaps stay visible, they do not all get filled, and the ones that get filled are usually filled by something breaking. On the air quality page you will see days marked NO VERIFIED DATA. Those are real gaps in the public record, left open on purpose. August 8, August 9, August 13 and August 16 were each published with no fire figures at all because no federal situation report existed on those mornings; all four have been backfilled onto their own dates, as have the August 20, August 22 and August 25 editions, and now the September 3 and September 4 ones. August 24, August 26, August 28 and now September 4 and September 5 are completely blank for air quality in all three cities, and nothing is interpolated across them. September 4 and September 5 are the first two consecutive blank days in this record, which matters for how the chart reads: the line between September 3 and September 6 spans seventy-two hours and two unsampled days, and that segment is drawn, not measured. The repair for all five is the clean air agency’s monthly quality-assured report; the August file is still not posted, checked again today for a fourth time, but the July one confirms the format — daily AQI by date and by station, across twenty-two county monitors — so the fix is real and is waiting on a file. September 4 and September 5 also lost their weather, which had survived every previous missed day but one. The forecast version window is the only route to a missed day’s meteorology, and when it was walked on September 6 every version returned an Area Forecast Discussion instead of a Fire Weather Planning Forecast. That is the mirror of a failure logged three days earlier, when the discussion URL served a planning forecast; both directions of the same crossing have now been seen, and both were seen in one run. It cost two days of weather and it paid for one thing in return: the discussion it served by mistake is the first NWS product this site has read that names debris flows near burn scars. An absence here is always phrased as what could not be read, never as what does not exist.
The Sources & Methods page lists exactly which data could not be obtained and why — and which of this site's own working assumptions have since been proved wrong.
It ends when the fire does — and this week another fire showed exactly how a fire can leave this report without ever ending on paper. This record closes when the Autumn Lane Fire — the largest of the three — reaches 100% containment. Nineteen consecutive national situation reports, August 18 through September 5, have now been read, and not one names Autumn Lane, Old Trails or Fairview anywhere; sixteen of the nineteen were read on two or more independent paths, and none contains the bare word Spokane. Three of those nineteen were read in a single sitting on September 6, because this site did not run on September 4 or September 5 — which is also why two of them rest on one path each. The corroboration was not unavailable. It was missed. The prediction published here in advance came back a hit for a twelfth time: Black Fox, Sandy and 4V were all printed at 100% on the September 2 edition and all three are absent from the next one. Every one of the twelve went the same way — printed at 100% once, then gone. Autumn Lane did not do that. It was printed at 97% on August 17 and was simply absent the next morning. AND THIS WEEK THE OTHER HALF OF THAT QUESTION FINALLY GOT AN ANSWER. Kaiser Canyon — 138,293 acres, the third-largest fire in Washington — stood at 99% on September 2, at 98% on September 4, and is absent from September 5. It never printed a 100. So reaching full containment is sufficient for leaving this table, and it is not necessary. For eighteen editions this site argued that Autumn Lane’s silence could not be read as containment, and that was a refusal to infer. It is now an observation about a fire in the same table, the same region and the same week. The rule this site understands well runs one way only, and running it backwards would have put a 100% on this page that no source has ever published. Still 97%. This record stays open.
So the most likely explanation for the silence is not that this fire was finished, but that it stopped being federally reported — most plausibly transferred off federal incident management back to state or local control, which is ordinary at this stage of a fire and which the situation report does not announce. That is an inference, it is labelled as one, and it is not a containment figure. This page keeps both honest readings and weights them unequally. One: a federal product drops an incident when it is finished, so fourteen read editions of removal amount to a statement of completion. That reading is the weaker of the two by a wide margin, because the product demonstrably marks completion by printing 100% first — watched four times, once against a prediction made in advance — and it never printed 100% here. Two: the published figure is 97%, no source anywhere has said this fire is contained, controlled or out, and the Spokesman-Review’s four-byline one-month feature of August 30, updated August 31, states no containment status either. This site will not manufacture a number it has never seen. The closing rule was written on the assumption that the number would be published, and that assumption has now failed for twenty-four days. Today added a reason for caution about all of it. Re-reading two editions this site had already read turned up a fourth fire at 100% that yesterday’s run missed entirely, corrected a regional count from zero to three, and showed two ways of questioning the same PDF returning different answers. The absence claim survives that, because it asks whether a name occurs anywhere in a document rather than trusting a table to be listed completely — and knowing exactly which of your claims survives a bad extraction is the difference between a record and a rumour.
Incident commander Tom Clemo, on August 2: “Probably the largest, most destructive fire in Washington's history occurred yesterday afternoon.”
The Spokane Area Fires complex ignited on Saturday, August 1, 2026, the day after the National Weather Service issued a fire-weather warning it had never used in Washington before. This is the record as it was reported, day by day, with the weather that drove each one. Twenty-three of these days were first published with an empty fire column — August 8, August 9, August 13, then August 18 through September 6. The first three have since been backfilled from federal editions that appeared later, as have August 16, August 20, August 22 and August 25. The nineteen editions from August 18 to September 5 cannot be backfilled, because there is nothing to backfill them with: every one exists, every one has been read, sixteen of the nineteen on two or more independent paths, and none contains a figure for any of these fires. September 3 and September 4 rest on a single path each, and September 6 was read on two. August 23, September 3 and September 4 are the three days still resting on one path — and two of those three are single-path because this site was not running when they were live, not because a second path was unavailable. September 6 is empty for the ordinary reason: today’s edition has not been published yet. August 27 was the exception for three days — no edition for that date appeared anywhere — until the archive published five editions at once on August 30 and it turned out to have existed all along. That is the distinction this timeline is built to keep: what could not be read, never what does not exist.
The three fires were consolidated under the designation Spokane Area Fires at 7:30 a.m. on August 2 and managed as a single complex by California Interagency Incident Management Team 7, a Type 1 national team. Sources also call it the Spokane Complex. A fourth fire near Medical Lake, the Espanola Fire, burned at the same time but is not part of the complex.
State: Gov. Bob Ferguson declared a state of emergency on Saturday, August 1, including a statewide burn ban through September 30, 2026.
Federal: President Trump approved an Emergency Declaration on Tuesday, August 4 — not a Major Disaster Declaration. It covers six counties and three tribal nations and provides a 75% federal cost share for emergency measures such as evacuation support, shelters, food and water, and search and rescue. Debris removal was requested but not approved. A Major Disaster Declaration request was expected to follow after damage assessments; as of August 10 no such declaration has been reported, and its damage assessment is the thing that would eventually reconcile the five competing structures counts on this site.
The final federal cost figures. NIFC’s Aug 17 report puts spending at $18 million on Old Trails and $13.1 million on Autumn Lane; Fairview’s $1.4 million is its Aug 16 figure, after which the fire left the table. $32.5 million across the complex — and it did not move on Aug 16 or Aug 17, which breaks the one pattern this site had watched hold on every single report of the event. The run was $17.15M (Aug 8), $20.45M, $23.01M, $25.1M, $26.5M, $29.1M, $30.2M, $32.5M on Aug 15 — and then flat, twice. Cost had risen on every prior report, including the one on which staffing fell 77%. Two flat reports at the end are consistent with a complex whose remaining work is mop-up rather than suppression; they are also the last cost figures anyone will publish for these fires. Old Trails remains the most expensive fire of the three and the most destructive; it was never the largest.
On the evening of August 4, three Washington Department of Ecology monitors read 151 in Spokane, 121 near Kirkland and 31 near Chimacum — a spread of about five times. By the morning of August 9 the same three instruments read 179, 16 and 14: a spread of about thirteen times. On the morning of August 14 they read 30, 28 and 16 — a spread of 1.9 times, and all three inside the Good band on the same day for the first time in this event. August 15 has only one of the three. Spokane returned to Moderate at 58 — a Spokane Regional Clean Air Agency county-wide maximum stamped 1:35 p.m., flagged on the point because it is not the Augusta Ave instrument that carries the rest of this line. Kirkland and Chimacum have no August 15 value at all: this record’s run executed at 01:30 on August 16, their feeds serve only the current hour, and Sunday readings are not published on Saturday’s row. Spokane’s 30 on August 14 remains the only Good reading it has produced anywhere in this record, and it comes from the cleanest comparison this chart carries: the same station and the same 08:00 hour label as yesterday’s 65. The two proxy stations were sampled an hour later, at 09:00, so the three-way comparison is close but not the exact match August 13 managed — and both proxies read identical numbers to yesterday, which is flagged on the rows rather than smoothed over, because an unchanged figure is exactly what a cached one looks like. Two of the four station pages consulted today were in fact serving cached figures as current — one three days old, one four days old. The reading hour caught one and the category word caught the other, which is why this site reads two views of every station. And the agency that publishes Spokane’s official number is back online after yesterday’s outage, but its index still shows Thursday’s 89. That stale figure did the most useful work of the day: it is a county-wide maximum for Thursday morning, and it confirms to the point the 89 this site published yesterday over a station page that was serving 158. A city’s air is not a number. It is an instrument, at an hour, with a name.
Category names are printed everywhere alongside the colors, so the scale never depends on color alone.
The scale ends at 500. Any number above 500 is an unofficial extrapolation, not an EPA AQI. This matters for one figure on this event — see the caveat below the chart.
Smoke concentration at any given place is not really about how big the fire is. It is about how much air the smoke gets mixed into, and where that air is going. Four things set that: the depth of the mixing layer, the wind, the terrain, and whether an inversion has put a lid on the whole thing.
The Spokane Regional Clean Air Agency describes a surface temperature inversion as “a layer of warmer air above cooler air near ground-level,” which traps pollutants “in cooler air near the surface.” Inversions form under “calm winds, clear skies, and long nights,” and “calm winds prevent warmer air above the surface from mixing down to the ground.” Critically for this event: “Spokane's topographical features can enhance the formation of inversions, especially in valley locations,” and inversions “can persist as long as several days” when a strong high-pressure system develops. That is exactly the pattern that set up over eastern Washington on August 3. And it is still operating on the best day of the event: on August 10, with an afternoon ventilation index of 971, the overnight figure still collapses to 47. The daytime air improved by 116 points; the nights have not changed at all.
Kirkland sits on the wrong side of the Cascades to receive eastern Washington smoke — normally. On August 4 that reversed. Ridge amplification plus a thermal trough along the coast produced offshore easterly flow, which carried smoke westward through the Cascade gaps into the Puget Sound basin. The smoke arrived aloft first. NWS Seattle: “A shallow inversion aloft will break as surface temperatures warm, allowing smoke to mix down.” That sentence is the whole mechanism by which smoke 250 miles away became air that people in Kirkland breathed by Tuesday afternoon. Then the wind turned. By Saturday, August 8, NWS Spokane's transport wind was due west; on Sunday and Monday it was southwest, and on Monday twice as fast — either way, pushing smoke away from Puget Sound. The Bellevue proxy read 38 on Saturday and 16 on both Sunday and Monday, its lowest of the event. Same fires, opposite wind, opposite result.
Wind, an inversion, humidity and terrain are the four levers that decide where smoke goes and how bad it gets. Move them and watch the plume, the fire's behavior, and the air in all three towns respond. Start with a real day from this event, then change one variable at a time.
This is a simplified physical model, not measured data and not a forecast. It is built to make relationships visible — inversion depth versus concentration, wind direction versus plume path, terrain versus transport. The arithmetic is printed in full at the bottom of this page so you can check it, argue with it, or break it. The measured readings live on the Air Quality page; those are the real ones. On August 10 this model was wrong by a factor of 3.5 on Spokane — its largest miss of the event — and the reason is printed with it rather than tuned away.
A model you cannot inspect is not worth trusting. Here is all of it.
Deliberately left out: fuel type and fuel moisture, fire size and heat output, plume rise from buoyancy, chemistry and particle aging, precipitation, diurnal heating cycles, and the fact that real terrain is three-dimensional. A real smoke forecast — NOAA's HRRR-Smoke, for example — carries all of these. Anyone who tells you the whole story fits in six lines of arithmetic is selling something.
Fast-moving disasters produce contradictory reporting. That is not a failure of journalism; it is what a partial view of a moving event looks like. Rather than hide the disagreements, they are all listed here — including the ones that have since resolved, because how a disagreement ends is part of the record, and including the ones where this site's own reasoning turned out to be wrong.