FirstAlerts
WildfiresVersion 3

McCully Fire in Oregon: Size Not Yet Established, Containment Varies by Report

The McCully Fire, sparked by lightning in Oregon, has no established size, with containment reported between 2% and 59%.

2 reports on this incident · first at Aug 31, 2026, 4:15 p.m. ET

By AI ReporterFirst reported Aug 30, 2026, 11:24 a.m. ETUpdated Sep 8, 2026, 1:24 p.m. ET
The in was discovered on August 22, 2026, and was , according to the Baker City Herald. The fire's size has not been established, as it is too new to have been measured. Containment figures range from 2% to 59%, according to conflicting reports from the Baker City Herald. Fire behavior has varied, with reports describing a major run on Tuesday, Sept. 1, when embers started a spot fire on the west side of Baldy Creek, and . Other reports describe the fire as , with , and remaining relatively quiet with .

Earlier reports

  1. Aug 31, 2026, 4:15 p.m. ETFirst report

    McCully Fire in Oregon Grows to 9,934 Acres; No Containment Figure Reported

    The McCully Fire in Oregon has burned 9,934 acres, but no containment figure has been reported yet, according to the Baker City Herald. The fire was discovered on August 22, 2026, and is moving slowly to the south, generally downhill, the newspaper reported.

    The cause of the fire has been reported as lightning by the Baker City Herald. The fire remains under investigation, and no further details have been released.

Was this report accurate and useful?

Sources

Revision history

  1. Version 38 Sept 2026, 17:24current

    Removed specific acreage figures and replaced with statement that size has not been established. Updated headline and dek accordingly.

  2. Version 22 Sept 2026, 03:23

    Removed specific acreage figures (9,934 and 12,561) and replaced with statement that size has not been established. Updated headline and dek accordingly.

  3. Version 131 Aug 2026, 20:22

    First published.

  4. Version 131 Aug 2026, 20:15current

    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.