Wildfire evidence study · Alberta, Canada · 2011
Documentary review · Sources checked 2 November 2026 · Historical case, not current emergency guidance.
The Slave Lake emergency shows why evacuation cannot be reduced to one warning time and one departure time. Different communities faced different triggers, road conditions changed, and the later return depended on services as well as fire status. This review examines the municipal retrospective as a source with valuable detail and explicit limitations.
A sequence involving several fires
The Lesser Slave River timeline describes two fires detected east of Slave Lake on 14 May 2011, followed by escalating conditions on 15 May. It places a wind shift and aircraft grounding at 2:30 p.m. on the latter day, then describes route closures and infrastructure failures later that evening. These are times reported by the retrospective, not independently synchronized observations produced by Tecnobosque. [1]
Warning duration is not travel time
The municipality’s evacuation account says some communities received a two-hour notice. It describes differing levels of awareness among residents and reports roughly 400 municipal-district evacuees on the evening of 14 May, increasing to more than 1,600 by noon the following day. The page states that its figures were assembled from media, provincial statistics and people on the ground. [2]
Those population figures refer to the municipal district and dated stages of the emergency. They should not be presented as the final total for the Town of Slave Lake or every affected community. They also should not be added together without knowing whether the later figure includes earlier evacuees.
A nominal two-hour notice does not demonstrate that every household had two hours of usable travel time. Warning receipt, preparation, access to transport and changing road availability must be measured separately. Nor does a regional timeline establish the minute at which an individual street became unsafe.
How to build a defensible evacuation chronology
| Field | Reason to preserve it |
|---|---|
| Community and geographic boundary | An order may cover only part of the affected region. |
| Issuance and receipt times | Sending a message does not establish when it reached a resident. |
| Road segment and closure interval | Availability can change during evacuation. |
| Source type and uncertainty | A later recollection differs from a timestamped operational log. |
The appropriate next step would be to compare the retrospective against dispatch records, original orders and road-control logs. Until those are examined, calculating precise clearance times or assigning responsibility for delay would go beyond the evidence reviewed here.
Return and recovery are different milestones
The municipality’s aftermath account describes service personnel returning first, followed by essential businesses and then residents. It identifies work on gas, electricity and water infrastructure. [3] That sequence explains why a house surviving the flames does not by itself establish that its occupants can return immediately.
For a recovery comparison, record access permission, service restoration, habitability and rebuilding separately. The first return is a meaningful milestone, but it is not a measure of completed household recovery.
Preserve the scope of casualty statements
The timeline distinguishes the absence of deaths in the flames from a fatal firefighting helicopter crash on 20 May. [1] A summary that drops the qualifier could wrongly turn a narrow statement about direct fire exposure into a claim of no deaths associated with the response.
Limits
This is a documentary review of municipal retrospective pages. It does not establish an ignition mechanism, reconstruct individual movements, verify every timestamp or evaluate the aircraft accident. The interpretation is Tecnobosque’s; the underlying historical statements remain attributed to the municipality.
Sources
- Lesser Slave River: Disaster Timeline — retrospective chronology and casualty scope.
- Lesser Slave River: Evacuation Efforts — notice periods, dated district counts and stated source provenance.
- Lesser Slave River: The Aftermath — phased return and services.
Continue the investigation
Tantallon: evacuation triggers and evidence dates · McDougall Creek: recovery dependencies · Evidence-review methodology · Canadian case studies
Cite this record
Tecnobosque. “Slave Lake Fires 2011: Evacuation Timelines, Road Access and Phased Return.” Documentary review, 2 November 2026. Permanent record.