Bald Range Wildfire in British Columbia Remains Out of Control
The fire, discovered Aug. 7, continues to burn out of control, with conflicting reports on its size.
3 reports on this incident · first at Aug 22, 2026, 4:11 p.m. ET
Earlier reports
Aug 25, 2026, 5:56 p.m. ET
Bald Range Wildfire in British Columbia Remains Out of Control
The Bald Range Wildfire in British Columbia remains out of control, according to caledoniacourier.com and vernonmorningstar.com. The fire's exact size has not been confirmed, and fire behaviour has not been detailed in available reports. The cause of the fire has not been determined.
Aug 22, 2026, 4:11 p.m. ETFirst report
Bald Range Wildfire in British Columbia Covers 24,820 Hectares
The Bald Range Wildfire in British Columbia has burned 24,820 hectares, according to a report from Castanet. Fire behaviour and activity have been dampened over the last several days due to heavy smoke, the outlet reported.
Safety concerns continue to limit access to properties damaged by the fire, Castanet reported. The cause of the fire has not been determined.
Was this report accurate and useful?
Sources
- Safety concerns continue to limit access to Bald Range wildfire-damaged propertiescastanet.net
- Rain provides cool relief to firefighting efforts at Bald Range blaze - Vernon Morning Starvernonmorningstar.com
- No growth on Summerland's Bald Range wildfire, evaction orders remain - Fort St. James Caledonia Couriercaledoniacourier.com
- Wildfire evacuees continue to return in Meadow Valleycastanet.net
- Wildfire evacuees continue to return bordering Greater West Bench and Fauldercastanet.net
- Rising temperature could increase activity at Bald Range blaze by Summerland - Campbell River Mirrorcampbellrivermirror.com
- Faulder remains evacuated as crews work to repair water system damaged by Bald Range wildfirecastanet.net
- Penticton evacuation reception centre to close as Summerland recovery progressescastanet.net
- A painful homecoming: Faulder residents return to see what the Bald range fire left behind | Globalnews.caglobalnews.ca
Revision history
- Version 528 Aug 2026, 03:53current
Removed specific size figures and replaced with statement that size has not been established, per complaint.
- Version 325 Aug 2026, 21:56current
Updated to reflect conflicting reports on fire size and behaviour, and clarified that the cause remains undetermined.
- Version 224 Aug 2026, 02:52
Updated size to reflect conflicting reports; added fire behaviour details and containment status.
- Version 122 Aug 2026, 20:24
First published.
- Version 122 Aug 2026, 20:11current
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.