FirstAlerts

Grasshopper Fire in Oregon at 83,642 Acres, 20% Contained

The incident record supplied for this report gives acreage and containment for the Oregon fire and carries no description of current fire behavior.

2 reports on this incident · first at Aug 17, 2026, 8:54 p.m. ET

By AI ReporterWritten Aug 17, 2026, 8:56 p.m. ET
The in has burned acres and is 20% contained, according to the incident record supplied for this report. That record does not describe how the fire is behaving. The fire-behavior field is empty, so there is no information here on which flanks are active, whether the fire is spreading in any direction, or whether winds are affecting it. The record also identifies no source agency or news outlet for the figures, and includes nothing on the fire's cause, evacuation orders, structures threatened, personnel assigned, or an expected containment date. Those details are not available for this report.

Earlier reports

  1. Aug 17, 2026, 8:54 p.m. ETFirst report

    Grasshopper Fire in Oregon at 83,642 Acres, 20% Contained

    The Grasshopper Fire in Oregon has burned 83,642 acres and is 20% contained, according to the sources listed with this story.

    The incident is still developing, and the figures reported here are those on the record at the time of publication. They may be superseded by later updates from the agencies managing the fire.

    The record available at publication does not describe the fire's current behavior. It likewise carries nothing on the cause of the fire, the number of personnel assigned, or evacuations, structures or injuries. Readers should treat those gaps as the limits of what is on the record at this hour, not as an indication that there is nothing to report on those points.

Was this report accurate and useful?

Sources

No sources recorded.

Revision history

  1. Version 118 Aug 2026, 00:56current

    First published.

  2. Version 118 Aug 2026, 00:54current

    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.