FirstAlerts
WildfiresVersion 2

Modrite Fire in Washington Burns Roughly 57,000 Acres After Lightning Ignition

The Modrite Fire in Washington was caused by lightning miles away and has burned roughly 57,000 acres since its discovery on July 17, 2026.

2 reports on this incident · first at Aug 13, 2026, 6:04 a.m. ET

By AI ReporterFirst reported Aug 13, 2026, 3:00 a.m. ETUpdated Aug 17, 2026, 11:24 a.m. ET
Developing · checked 33h ago

Fire size and containment change through the day and the earliest figures are the least certain. Check your local emergency management agency for anything you need to act on.

We last searched for new coverage of this at Aug 17, 2026, 12:10 a.m. ET — checked 33h ago.

The in was discovered on July 17, 2026, according to military.com. Both adn.com and military.com reported that the wildfire was started by lightning miles away, and military.com reported that it has burned . Reporting outlets gave differing accounts of the fire's behavior. Adn.com reported a crown fire in ponderosas spewing embers that raced toward Inchelium, consuming homes and everything in its path. Military.com described an active fire that backed, flanked, and torched through timber, with homes and infrastructure in its path. No containment figure has been reported for the fire.

Earlier reports

  1. Aug 13, 2026, 6:04 a.m. ETFirst report

    Modrite Fire in Washington Has Burned Roughly 57,000 Acres

    A wildfire in Washington state known as the Modrite Fire has burned roughly 57,000 acres, according to Military.com. The fire was discovered on July 17, 2026.

    Military.com reported the fire was still active, and that it had backed, flanked and torched through timber, with homes and infrastructure in its path. The outlet reported the fire was caused by lightning.

    The situation is developing. Military.com's report does not state how much of the fire has been contained, whether evacuation orders are in place, or whether anyone has been hurt or any structures lost, and none of those things should be assumed either way. How far the fire has advanced since it was discovered is not described in the available reporting.

Was this report accurate and useful?

Sources

Revision history

  1. Version 217 Aug 2026, 15:24current

    Updated to include conflicting fire behavior descriptions from adn.com and military.com, and added attribution to adn.com for the cause.

  2. Version 113 Aug 2026, 10:07

    First published.

  3. Version 113 Aug 2026, 10:04current

    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.