DND said the Wainwright fire “ignited” at 4 p.m. The military now says it was known for hours

Published 2050 MT, Sunday, Oct. 18, 2026.

By Kevin J.S. Duska Jr. | Prime Rogue Inc | Calgary, AB

This follows Prime Rogue’s satellite analysis, published at 2 a.m. MT Sunday: Satellites saw fire on CFB Wainwright range hours before DND says it ignited, and our 7 a.m. follow-up.

TL;DR/BLUF

In the first hours after four soldiers were killed at CFB Wainwright, the Department of National Defence told Canadians that a fire “ignited within the training area” at about 4 p.m. on Saturday.

On Sunday, the military gave a fuller account. Range Control at the base had been aware of a fire for several hours and was monitoring it, according to accounts of the briefing in Edmonton, and training continued. At about 4 p.m. the wind shifted, and a fire about a kilometre away reached soldiers of C Company, 3rd Battalion, Princess Patricia’s Canadian Light Infantry, in 30 to 60 seconds.

The written record from National Defence makes no mention of that earlier fire. Read alone, the release told the public the fire began at the moment it became deadly. The military’s own account on Sunday is that a fire was already burning, and already known, for hours.

DND has not said whether the fire Range Control was monitoring is the same fire that reached the troops, or what exactly “ignited” at 4 p.m.

What National Defence said, and when

Saturday, Oct. 17.

The Canadian Armed Forces’ first statement, issued Saturday evening, said: “At approximately 1600 on 17 October 2026, a fire was reported on the range at Canadian Armed Forces Base Wainwright. The fire has extended beyond the boundary of the training area and emergency services are responding.” That statement was later removed and replaced by National Defence’s overnight release.

Overnight, in a news release dated Oct. 18.

A National Defence news release, “Incident at Canadian Forces Base Wainwright,” said: “A fire ignited within the training area of Canadian Forces Base (CFB) Wainwright, Alberta, at approximately 4:00 p.m. (local time) on October 17, 2026. The fire spread rapidly beyond the boundaries of the training area.” It gave no cause.

Sunday, Oct. 18.

A second release named the exercise, Exercise APOLLO SHOOTER, and said the fire overtook the unit’s administrative area. This release stated that “On October 17, 2026, at approximately 1600 hrs (MDT), members of 1 Canadian Mechanized Brigade Group from the 3rd Battalion, Princess Patricia’s Canadian Light Infantry, were conducting live fire training at CFB Wainwright as part of Exercise APOLLO SHOOTER… While conducting training a fire ignited and high wind speeds enabled the fire to grow and spread very rapidly overtaking the unit administrative area.” The release carries no time of publication. Rutland announced the soldiers’ names at the briefing, which suggests the release followed it. If so, National Defence again described a fire that “ignited” during training, with no mention of the fire its own commander had just said was known for hours.

Sunday, 3 p.m. MDT briefing, Edmonton.

Maj.-Gen. Wade Rutland, commander of 1st Canadian Division, said range control “was aware there was a fire for several hours and were monitoring it.” CBC News reported that it was decided training “could carry on for a certain amount of time,” and CNN reported that range control considered the fire “contained” and not expected to move “anywhere near” the soldiers. “The fire was a kilometre away when the wind shifted,” Rutland said. “It is not normal for a fire to move a kilometre in 30 to 60 seconds.” He added: “I spoke to my commander on the ground last night and this morning, and he said within 30 seconds to a minute they saw no fire, and then there was a fire right on top of them.” Rutland said the fire “did originate within the training area, and did cross established fire guards before being contained.”

Prime Rogue infographic titled What happened that afternoon, and how National Defence described it. Panel A is a timeline of Saturday, Oct. 17, from 11 a.m. to 5 p.m. MT, with six numbered events: about 11 a.m., Environment Canada forecast gusts to 80 km/h; 12:17 p.m., 59 low-confidence Landsat 8 fire detections; 2:49 p.m., NOAA-20 VIIRS detects fire on the range with 8 detections; 3:03 p.m., wind warning continued with gusts to 90 km/h; about 3:30 p.m., a resident sees a wall of smoke, per The Globe and Mail; about 4 p.m., the wind swings northwest, gusting to 69 km/h, and a fire about 1 km away reaches C Company in 30 to 60 seconds. A green bar ending at 4 p.m. shows Range Control aware of a fire for several hours and monitoring it, with the start time not disclosed. Panel B shows four official statements in order: the Oct. 17 CAF statement, fire was reported on the range at approximately 1600, consistent with the briefing; the overnight DND release, a fire ignited within the training area at approximately 4:00 p.m., with no mention of an earlier fire; the Sunday DND release naming Exercise APOLLO SHOOTER and saying the fire overtook the unit administrative area, with no mention of an earlier fire; and the Sunday 3 p.m. briefing, Range Control aware of a fire for several hours and training continued, the first official account of the earlier fire. A footnote says satellites detect heat, not cause, and DND has not said whether the fires are the same.
Satellite, weather and witness accounts place fire and smoke on the base well before 4 p.m. National Defence’s written statements did not mention an earlier fire until Sunday’s briefing. (Sources: NASA FIRMS; Environment and Climate Change Canada; The Globe and Mail; CAF and DND statements, Oct. 17–18; military briefing, Oct. 18. Graphic: Copyright Prime Rogue Inc., 2026)

The first statement and the briefing are consistent with each other. A fire “reported” at about 4 p.m. can describe the moment it reached the soldiers. “Ignited” says something different: that the fire started then.

Two readings, one unanswered question

There are two ways to reconcile the release with the briefing, and DND has not said which is right.

One fire.

The fire Range Control was monitoring is the fire that reached C Company. If so, it did not ignite at 4 p.m. It had been burning for hours, and 4 p.m. is when the wind turned it onto the troops. On this reading, the release gave the public a start time that the military’s own account does not support.

Two fires.

A separate grass fire started near the section attack range at about 4 p.m., while another fire elsewhere on the base was being monitored. The Sunday release’s wording, “while conducting training a fire ignited,” is the only official language that could support this reading. No account of the briefing describes a second fire: Rutland described one fire, burning about a kilometre away, that the wind drove onto the soldiers. If there were two fires, the release still left out that a fire was already burning on the base, a fact the military itself put at the centre of Sunday’s briefing.

Prime Rogue infographic titled One fire or two? Either way, the first account left something out. Reading 1, one fire: the fire Range Control was monitoring is the fire that reached C Company; the sequence is fire burning for hours, wind shift at about 4 p.m., fire reaches soldiers; for the release, this means the fire did not ignite at 4 p.m. and the release gave a start time the military's own account does not support. Reading 2, two fires: a separate grass fire started near the range at about 4 p.m. while another fire was being monitored; the sequence is Fire A monitored for hours, Fire B starts at about 4 p.m., Fire B reaches soldiers; for the release, ignited may be accurate for Fire B, but the release left out a known fire burning on the base. Bottom line: DND was asked what ignited at 4 p.m. and referred Prime Rogue to Sunday's briefing, which did not say. A footnote says these are Prime Rogue's characterizations and neither has been confirmed by National Defence.

Two ways to reconcile DND’s release with the military’s briefing. Accounts of the briefing describe a single fire; National Defence has not said which reading is correct. (Analysis and graphic: Copyright Prime Rogue Inc., 2026)

Either way, the first public account from National Defence omitted the fact that now matters most: a fire was known, and training went on.

The “two fires” reading would raise its own questions: where the monitored fire was, and whether the 4 p.m. fire was started by the training itself. Rutland said “a multitude of ordnance” was in use in the training area that day, “grenade launcher, grenades, small arms, ammunition,” and that the cause “could have been any of that, or none of it.”

What the satellite record shows

NASA satellite data, analyzed and published by Prime Rogue at 2 a.m. Sunday, recorded fire on the CFB Wainwright range at 2:49 p.m. Saturday, from eight detections by the NOAA-20 satellite’s VIIRS sensor. Fifty-nine low-confidence Landsat 8 detections at 12:17 p.m. likely show fire earlier still. Four satellite passes overnight found no active fire at the base.

That record is consistent with a fire burning on the range for hours before 4 p.m., as the military now describes. It cannot show whether the fire NASA detected is the fire that reached the soldiers, and it cannot show cause. Satellites detect heat.

Annotated NASA FIRMS map of part of CFB Wainwright in the Time Based view, captured at 1:09 a.m. MDT on Oct. 18 over satellite imagery. Orange squares mark VIIRS detections from the NOAA-20 pass at 2:49 p.m., coloured as detected 6 to 12 hours before the capture. Thin pale-yellow lines mark Landsat 8 detections at 12:17 p.m. in the same area, coloured as detected 12 to 24 hours before. Callouts explain the colour coding and note the Landsat detections are lower confidence. A 1-kilometre scale bar is shown.
NASA’s FIRMS map colours each detection by how long ago it was made. Captured at 1:09 a.m. MDT, the orange VIIRS squares (2:49 p.m.) and pale-yellow Landsat lines (12:17 p.m.) match the acquisition times in NASA’s data files. The large squares are VIIRS pixels and overstate the area burned. (Imagery and data: NASA FIRMS. Annotations: Copyright Prime Rogue Inc., 2026)

Environment Canada’s station at the base recorded a sharp wind shift at 4 p.m.: the wind swung to the northwest, gusting to 69 km/h, and the temperature fell about 10 degrees.

Three-panel chart of hourly weather at the CFB Wainwright Environment Canada station from 10 a.m. Oct. 17 to 1 a.m. Oct. 18, Mountain Time. Wind: southwest winds rose from about 12 km/h at noon to 31 to 32 km/h with gusts to 46 km/h at 2 and 3 p.m., then at 4 p.m. swung to the northwest at 51 km/h with a peak gust of 69 km/h, easing to about 17 to 24 km/h by late evening. Temperature: rose to 23.3 degrees Celsius at 3 p.m., then dropped to 12.9 degrees at 4 p.m. Relative humidity: fell to 16 per cent at 2 p.m., then jumped to 43 per cent at 4 p.m. Dashed lines mark the satellite fire detections at 12:17 p.m. and 2:49 p.m., and a solid line marks DND’s stated ignition time of about 4 p.m.
Hourly observations from the Environment Canada weather station at CFB Wainwright. Through the early afternoon, conditions were hot, dry and windy from the southwest; at about 4 p.m. the wind swung to the northwest, gusting to 69 km/h, and the temperature fell 10°C. The weather record provides context for fire behaviour; it does not show what caused the fire. (Data: Environment and Climate Change Canada. Graphic: Copyright Prime Rogue Inc., 2026)

The weather that day

Rutland said that despite the forecast for wind, conditions were “within standard procedures to conduct training exercises,” with winds below 50 km/h. Environment Canada’s station at the base supports that for the early afternoon: gusts peaked at 45 to 46 km/h at 2 and 3 p.m. But relative humidity at the station had fallen to 16 to 17 per cent, very dry conditions for grass, and a Canadian Armed Forces memo reported by Global News said the fire index was low.

Environment Canada forecasts issued at about 5 a.m. and 11 a.m. Saturday called for gusts to 80 km/h in the afternoon, The Globe and Mail reported. At 3:03 p.m., about an hour before the shift, Environment Canada continued a yellow wind warning for Lloydminster – Wainwright – Vermilion – Provost, forecasting gusts to 90 km/h.

Around 3:30 p.m., Wainwright resident Tanya Porter saw a wall of smoke, The Globe and Mail reported.

Whether the forecast wind shift was weighed in the decision to keep training is one of the questions a Board of Inquiry will need to answer.

Why the wording matters

The first official account of a disaster shapes how the public understands it. For about 14 hours, from the overnight release to Sunday’s briefing, National Defence’s written account described a fire that ignited at 4 p.m. and spread rapidly. That account fits a sudden, unforeseeable event. The account given on Sunday, of a fire known for hours and a decision to continue training, raises questions about decisions made before anyone was hurt.

Prime Rogue is not suggesting that the release was written to mislead. It was issued within hours of a mass-casualty event, when information inside the military was still incomplete. But National Defence has not corrected or clarified it, and the military now knows, and has said publicly, that the fire had been monitored for hours.

A Board of Inquiry will examine the events of Oct. 17; Rutland said it could take at least a month. The Canadian Forces National Investigation Service and the 1st Military Police Regiment’s incident response team are investigating, working with the RCMP.

Questions for National Defence

On Sunday morning, Prime Rogue asked National Defence what “ignited” at 4 p.m., and whether Range Control knew of fire in the training area earlier in the afternoon, with a deadline of 6 p.m. MT. DND’s media relations office replied by directing Prime Rogue to the afternoon briefing. The briefing addressed the second question: Range Control knew. It did not explain the first. Prime Rogue sent DND a follow-up asking whether the two are the same fire, and will update this story with any response.

Questions National Defence has not answered:

  • Is the fire Range Control was monitoring the same fire that reached C Company? If not, where was each fire, and when did each start?
  • What does “ignited within the training area” at approximately 4 p.m. refer to?
  • At what time did Range Control first become aware of fire on the range on Oct. 17, and is that recorded in the Range Control log?
  • Who decided training would continue, and on what information?
  • Was the Environment Canada wind warning, continued at 3:03 p.m., known to Range Control or the exercise chain of command?
  • Will National Defence correct or clarify its Oct. 18 release?

Prime Rogue has also filed requests under the Access to Information Act for recordings, dispatch records and imagery from the incident, and for initial casualty reporting and communications to Ottawa.

The soldiers

The four soldiers killed were Sgt. Morgan Wong, of the Loyal Edmonton Regiment, serving with 3rd Battalion, PPCLI, and Pte. Shaun Farrell, Pte. Aidan Goulding and Pte. Hayden Lykkemark, all of 3rd Battalion, PPCLI. Thirty-nine people received hospital care; Acute Care Alberta said 19 were in critical condition. Prime Rogue extends its condolences to their families, and our thanks to the soldiers and first responders who went toward the fire.

Ongoing coverage: CFB Wainwright fire: live updates.

Support

CAF Family Information Line (24/7): 1-800-866-4546. Canadian Forces Member Assistance Program: 1-800-268-7708.

Sources

4 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Verified by MonsterInsights