Firefighting Helicopter Crashes at Utah Wildfire; Condition of Two Aboard Unknown
A Sikorsky S-64 working the Widemouth 2 Fire near Richfield went down with two people aboard, and the cause has not been determined.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Terrain elevation
- 846 ft
- Nearest aerodrome
- 3.2 miles W of Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (KMSP/MSP)
Sources
- A helicopter battling a Utah wildfire crashes as a blaze kills dozer operator in Oregonazfamily.com
- 1st LD Writethru: Firefighting helicopter crashes while battling wildfire in U.S. Utahbignewsnetwork.com
- Helicopter battling US wildfire crashes, fears for crewcanberratimes.com.au
- A helicopter battling a Utah wildfire crashes as a blaze kills dozer operator in Oregonclickondetroit.com
- Horror as helicopter battling raging fire caused by lightning crashesexpress.co.uk
- Firefighting helicopter crashes while battling large Utah wildfirefirerescue1.com
- Utah Wildfire: Heavy-Lift Helicopter Crashes While Battling Massive Blaze, Fate Of 2 Crew Unknownfreepressjournal.in
- A helicopter battling a Utah wildfire crashes as a blaze kills dozer operator in Oregonksat.com
- A helicopter battling a Utah wildfire crashes as a blaze kills dozer operator in Oregonlocal10.com
- Utah wildfire helicopter crashes as Oregon blaze kills operatorsiasat.com
- Helicopter Battling Utah Wildfire Crashes as Blaze Kills Dozer Operator in Oregontheepochtimes.com
- 1st LD Writethru: Firefighting helicopter crashes while battling wildfire in U.S. Utahutahindependent.com
- A helicopter battling a Utah wildfire crashes as a blaze kills dozer operator in Oregonwdio.com
Revision history
- Version 188 Aug 2026, 06:25current
No new facts; headline and dek added, text otherwise unchanged.
- Version 178 Aug 2026, 05:07
Added the 427 square kilometre fire size reported by canberratimes.com.au and broadened outlet attribution on the date and on the NTSB/FAA investigation lines.
- Version 168 Aug 2026, 04:12
Added the reported distance of Richfield from Salt Lake City and a summary dek; no change to casualty or investigation facts.
- Version 158 Aug 2026, 04:08
Added headline and dek; body unchanged in substance, with supplied Minnesota-based weather and location reference data omitted as not applicable to the Utah crash site.
- Version 148 Aug 2026, 03:42
Added ksat.com and siasat.com attributions to the date, souls-aboard and investigation lines, and noted the S-64's water/retardant tank capability.
- Version 138 Aug 2026, 03:22
Added clickondetroit.com to the date and investigation attributions and removed a duplicated metric fire-size figure; no new facts.
- Version 128 Aug 2026, 03:12
Added the sourced date disagreement, with siasat.com giving 2025 against the 2026 date reported by four other outlets.
- Version 118 Aug 2026, 02:58
No new facts from sources; supplied weather and geographic reference data were excluded because they geocode to Richfield, Minnesota, not the Utah fire area.
- Version 108 Aug 2026, 02:52
Added azfamily.com to the attribution for the NTSB/FAA investigation and noted the sources' differing wording on whether investigators may or might not reach the scene.
- Version 98 Aug 2026, 02:28
Added Sevier County Sheriff Nathan Curtis as the named source for teams being unable to reach the scene, and the fire's location near Kanosh, Utah.
- Version 88 Aug 2026, 02:07
Added firerescue1.com's detail that the helicopter had been working in an area of steep terrain.
- Version 78 Aug 2026, 02:03
Added firerescue1.com reporting that the crash started another fire and blocked responders Friday evening, that firefighting was paused and resumed, and Great Basin Incident Management Team's Tyler Hecht on flying conditions.
- Version 68 Aug 2026, 01:57
Added express.co.uk detail placing the fire on the Fishlake National Forest at 165 square miles, with more than 600 personnel and at least six structures destroyed.
- Version 58 Aug 2026, 01:48
Added the reported warning of potential dry thunderstorms to the fire-conditions paragraph; no other substantive changes.
- Version 48 Aug 2026, 01:23
Added reported red flag warnings of erratic winds, dry fuels and hot temperatures, and that the Sevier County Sheriff did not immediately respond to questions.
- Version 38 Aug 2026, 01:07
Added that the FAA and wildfire officials had no information on the condition of the two aboard, per canberratimes.com.au.
- Version 28 Aug 2026, 01:04
Added that the NTSB and FAA will investigate, that the helicopter was one of seven aircraft on the fire, the Canberra Times' fire-size figure, and the note that investigators may not reach the scene immediately.
- Version 18 Aug 2026, 00:57
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.