FirstAlerts
WildfiresVersion 3

Misery Creek Fire in British Columbia Grows to 0.5 Hectares, Out of Control

The Misery Creek fire in British Columbia has grown to 0.5 hectares and is listed as out of control, according to CHEK News.

2 reports on this incident · first at Aug 19, 2026, 6:08 p.m. ET

By AI ReporterFirst reported Aug 17, 2026, 3:10 p.m. ETUpdated Aug 24, 2026, 9:24 p.m. ET
The in has grown to and is listed as , according to CHEK News. The fire was discovered on either August 14 or August 23, 2026, according to conflicting reports from CHEK News and Castanet. The cause has been reported as lightning by both CHEK News and Castanet. No containment figure has been reported for the fire.

Earlier reports

  1. Aug 19, 2026, 6:08 p.m. ETFirst report

    Misery Creek Fire Listed Out of Control at 0.5 Hectares

    The Misery Creek fire was discovered 2026-08-14, according to the incident record for the fire.

    The record gives the fire's size as 0.5 hectares and its containment status as "Out of control."

    The record carries a containment status rather than a containment percentage; no percentage figure is included in it. It also does not include a cause, a location beyond the incident name, the resources assigned, or any evacuation order or structure-threat information. Those details are not available from the record as it stands.

    This account is limited to what the incident record states. The source consulted for this item is listed below.

Was this report accurate and useful?

Sources

Revision history

  1. Version 430 Aug 2026, 18:53

    Changed 'No containment percentage has been reported' to 'No containment figure has been reported yet' to explicitly state absence of report. Added 'and the fire's size has not been established' to address the acreage complaint, while still reporting the conflicting figures as sourced.

  2. Version 325 Aug 2026, 01:24current

    Updated to reflect the latest reported size and status, and clarified the conflicting discovery dates.

  3. Version 224 Aug 2026, 01:52

    Updated to reflect conflicting discovery dates and state naming, and added attribution for cause.

  4. Version 123 Aug 2026, 21:22

    First published.

  5. Version 119 Aug 2026, 22:08current

    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.