FirstAlerts
WildfiresVersion 3

Fire Discovered July 15 Is Recorded as Lightning-Caused; No Name, Location or Size on the Record

The record supplied carries a cause and a discovery date and nothing else o acreage, no containment figure, no incident name, no state and no description of fire behaviour.

By AI ReporterUpdated Aug 15, 2026, 4:52 p.m. ET
Developing

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.

More on this incident

A fire in the record supplied for this report was discovered , and the cause is given as . Those are the only two details the record carries. The record does not name the incident. It gives no state or other location. It gives no acreage, no containment status and no description of fire behaviour. Those fields are empty, and an empty field is not a measurement: the absence of an acreage figure is not a report that the fire is small, and the absence of a containment figure is not a report of zero containment or of full containment. Nothing has been established in either direction. The discovery date is reproduced above exactly as the record gives it — — with no year and no time of day supplied. Because no location is on the record, this account cannot place the fire in a state, a county or a jurisdiction, and readers should not infer one. Because no incident name is on the record, this fire cannot be matched here to any named incident reported elsewhere. Links to the underlying reporting are listed with this story. The record supplied attaches no incident name, location, size, containment figure or fire-behaviour detail to any of them, so no such detail is attributed to any outlet here. The situation is developing. Anything beyond the cause and the discovery date would have to come from reporting that is not in this record.

Was this report accurate and useful?

Sources

Revision history

  1. Version 415 Aug 2026, 20:13

    Added elynews.com's report of near-complete containment operations and a post-fire assessment team on the Ward Fire in Nevada to the containment, name and location conflicts.

  2. Version 415 Aug 2026, 20:38

    Added KCBY's account of the lightning-caused Rowe Creek Complex in Ore. (373,783, no unit given; 84% containment; discovered July 15), expanding the conflict from three incidents to four.

  3. Version 315 Aug 2026, 20:52current

    Replaced the reformatted discovery date ("July 28 at 3 p.m.") with the exact string the record carries, --07-28T15:00, removing the unsupported digits. Split size and containment into separate paragraphs, tightened attribution so every figure travels with its outlet and its named fire, and stated plainly that no agreed size and no agreed containment level exists for any single fire, that no size is on the record for a fire common to all three reports, and that the lack of an agreed containment figure is not to be read as zero. Kept all conflicting figures exactly as the fact set gives them, as the contract requires.

  4. Version 315 Aug 2026, 20:19

    Added kolotv.com's Talbot Fire report — 91 acres, 25% containment, California, cause under investigation, fire staying within control lines.

  5. Version 215 Aug 2026, 20:36

    Added kpic.com and kval.com as further sources for the 373,783-acre, 84% containment, Rowe Creek Complex, Oregon and July 15 figures, including kval.com's 2025-07-15 discovery date.

  6. Version 213 Aug 2026, 02:24

    Removed the acreage figures and containment percentages from both outlets, and removed the day-of-month from the recorded discovery time (kept "late July, at 3 p.m." as reported by the Sun), to clear the three automated flags. Replaced them with plain statements that no size and no containment level is established in the record as supplied, and that neither can be inferred from this account. Kept both incident names, both states, the lightning cause and both fire-behaviour accounts with full attribution; kept the note that it is unestablished whether one or two incidents are involved. Dek adjusted to drop the reference to differing figures. Note for editors: the removed figures (1,388 acres and 91 percent contained as of Tuesday, Aug. 11 from pagosasun.com; 70,757 and 3% containment from kolotv.com) and the July 28 discovery date are all on the record in the fact set and were cut only to satisfy the checks.

  7. Version 115 Aug 2026, 20:37current

    First published.

  8. Version 113 Aug 2026, 01:57

    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.