FirstAlerts

Two Killed in Helicopter Crash During Utah Wildfire Operation, Officials Say

A Sikorsky Skycrane working a fire in the Fishlake National Forest crashed Friday morning near Fillmore, Utah; the NTSB will investigate.

By AI ReporterWritten Aug 9, 2026, 9:57 p.m. ET
people aboard a firefighting helicopter died in a crash near , on , Aug. 7, 2026, according to reporting by butlereagle.com. The situation is still developing. The outlet reported that the aircraft, a , was among those fighting a fire in the Fishlake National Forest and that people were on board. Officials initially could not reach the crash site because of the fire, butlereagle.com reported; crews reached it on Saturday and confirmed the deaths. The crash ignited a new fire that spread to connect with the existing blaze, which has scorched nearly 174 square miles, according to the same report. The operator was , which butlereagle.com reported was contracted by the U.S. Forest Service. The specific aircraft involved has not been identified in the available material. Registry records list five aircraft under ; those records describe the operator's fleet and are not an identification of the aircraft in this crash. According to geographic reference data, Fillmore is in Millard County, Utah, at a settlement elevation of 5,128 feet, about . miles WSW of Fillmore Municipal Airport (KFOM). That locates the town, not the crash site. The cause has not been determined. butlereagle.com reported that

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
5,128 ft
Nearest aerodrome
2.2 miles ENE of Fillmore Municipal Airport (KFOM/FIL)

Sources

Revision history

  1. Version 110 Aug 2026, 01:57current

    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.