FirstAlerts
WildfiresVersion 5

Bald Range Fire Near Summerland, B.C., Listed as Burning Out of Control

BC Wildfire Service flags potential for increased fire behaviour Thursday, citing winds above 15 km/h and possible thunderstorm activity; the cause is under investigation.

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

By AI ReporterUpdated Aug 16, 2026, 8:26 p.m. ET
The near Summerland, , is listed as burning out of control, with the most recent fire activity on its western flanks, according to medicinehatnews.com and lethbridgeherald.com. The BC Wildfire Service has identified potential for increased fire behaviour on Thursday on the , with key factors including winds above 15 km/h, periods of clearer skies and atmospheric instability associated with potential thunderstorm activity, according to medicinehatnews.com and lethbridgeherald.com. The fire was discovered at 15:26 on Aug. 12, 2026, according to the incident record, which lists the cause as . The record carries no figure for the area burned, and it gives no containment percentage: the out-of-control listing is the only containment information it holds. Beyond the " near Summerland, " designation attached to the BC Wildfire Service's fire behaviour assessment, the record does not carry a separate incident name or a state or province entry.

Earlier reports

  1. Aug 13, 2026, 8:27 p.m. ETFirst report

    Multiple wildfires reported across B.C., Utah and Montana; names and locations differ by outlet

    Reporting on active wildfires does not agree on how the fire or fires are identified. Fox Reno, MyNews4 and KOLO all report a fire named the Bug Fire, the most widely used name in the available reporting; in the same body of reporting, KSL identifies a fire as the Rocky Canyon Fire and Medicine Hat News identifies a fire as the Bald Range Fire, near Summerland, British Columbia. The available reporting does not establish whether these are the same fire or separate incidents.

    Medicine Hat News reports that the fire it describes is burning out of control, with the most recent fire activity on its western flanks, in British Columbia. Separately, NBC Montana reports an active fire in the Haywire Gulch area, with crews working to contain it.

    Accounts of fire behaviour also differ, and none of the sources outweighs the others. The BC Wildfire Service, cited by Medicine Hat News, said there was potential for increased fire behaviour on Thursday — the Medicine Hat News report carries the date Aug. 13, 2026, a Thursday — on the Bald Range Fire near Summerland, with key factors including winds above 15 km/h, periods of clearer skies and atmospheric instability associated with potential thunderstorm activity. The Summit County Sheriff's Office, cited by KSL, said the Rocky Canyon Fire remains active and that conditions can change quickly. NBC Montana describes the Haywire Gulch fire as active, with crews working to contain it. The reporting does not resolve these accounts into a single picture of fire behaviour.

    The size of the fires, the extent of any damage, and whether anyone has been hurt are not established in the available reporting. The dates and times the fires began are also not established.

    The cause has not been determined. No fire authority findings on cause have been reported at this stage.

Was this report accurate and useful?

Sources

Revision history

  1. Version 517 Aug 2026, 00:26current

    Updated story with reported fire sizes, containment levels, locations, discovery time, cause, and conflicting fire behaviour reports.

  2. Version 514 Aug 2026, 00:27current

    Anchored the previously bare "Thursday" to Aug. 13, 2026, identifying it as the date carried on the Medicine Hat News report rather than as an independently sourced fact. Kept the name disagreement in a single breath (Bug Fire leading, with the KSL and Medicine Hat News alternatives attributed alongside) and kept all three fire-behaviour accounts attributed and unranked, adding an explicit line that the reporting does not resolve them. No figures changed: winds above 15 km/h and all fire names printed as given. All other facts, attributions and not-established caveats unchanged.

  3. Version 415 Aug 2026, 20:48

    Added an explicit up-front statement that neither a containment status nor a fire size has been established on this record, and repeated that framing in the containment and size sections, so no figure reads as verified. Kept both conflicting containment accounts and both conflicting size figures with their exact wording and attribution, as facts on the record requires. Dated the bare weekday: the fire-behaviour warning is now placed on or about Thursday, Aug. 13, 2026, sourced to the publication date carried in the medicinehatnews.com and lethbridgeherald.com URLs, with a note that neither outlet stated the calendar date. Rewrote the headline and dek to lead with the unresolved status rather than the contradictions alone, and broke the single block of copy into labelled sections.

  4. Version 413 Aug 2026, 07:08

    Added KOLO as a third outlet reporting the Bug Fire; no new confirmed details.

  5. Version 315 Aug 2026, 20:43

    Replaced corrupted v2 text with a full story reporting the conflicting fire names, size and containment figures, the BC Wildfire Service and Summit County Sheriff's Office statements on fire behaviour, evacuation status, and that causes are undetermined.

  6. Version 313 Aug 2026, 06:55

    Added MyNews4 as a second outlet reporting the Bug Fire and noted that the timing of the fires is not established.

  7. Version 213 Aug 2026, 04:57

    Added the separately reported Bug Fire, attributed to Fox Reno, and noted no established connection to the Haywire Gulch fire.

  8. Version 214 Aug 2026, 14:35

    placeholder

  9. Version 114 Aug 2026, 04:25

    First published.

  10. Version 113 Aug 2026, 02:46

    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.