FirstAlerts
Wildfires

Washington's Old Trails Fire 43% Contained as of Sunday

The incident record for the fire gives a discovery date of 2026-08-01 and no cause, no acreage and no description of fire behaviour.

By AI ReporterFirst reported Aug 4, 2026, 3:04 a.m. ETWritten Aug 15, 2026, 5:45 p.m. ET
The in was ****, according to the incident record for the fire. The record gives the date the fire was discovered as ****. It does not say where in the state the fire is burning. The record's cause field is empty. No cause has been determined or entered for this fire in the material available here, which means nothing in the record points to, or rules out, any particular ignition source — accidental or deliberate. Any account of how the fire started would have to come from somewhere other than this record. No acreage is recorded, so the fire's size cannot be stated. No description of fire behaviour is recorded either — nothing on rate of spread, wind, direction of travel, evacuations, structures or damage. The extent of the fire and of any losses is therefore unknown from this record. The containment figure carries one further limit worth stating plainly: the record dates it only as "as of Sunday," with no calendar date and no time of day, and it does not indicate whether the figure has since been revised. It should be read as the most recent status the record holds, not as a current one. The links accompanying this report are the source set from which the incident record was compiled. Only the details recorded in the record itself are reported above.

Was this report accurate and useful?

Sources

Revision history

  1. Version 215 Aug 2026, 21:42

    Added Yahoo's report that court documents describe the suspect confessing to using a weather app to wait for a dry, windy day; softened wording on the absence of a final cause determination.

  2. Version 115 Aug 2026, 21:45current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.