FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC26FA079 · Helicopter Transport Services CH-54A

7 Aug 2026 · Cove Fort, UT, United States

Helicopter Transport Services CH-54A · Accident while maneuvering

From Richfield Municipal Airport (KRIF) to Richfield Municipal Airport (KRIF)

Report a problem

Event

NTSB case
ANC26FA079
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Helicopter Transport Services CH-54A

Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N793HT
Onboard fatalities
Unknown
Route
From Richfield Municipal Airport (KRIF), Richfield, UTTo Richfield Municipal Airport (KRIF), Richfield, UT
Aircraft age
About 59 years (built 1967)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 133: Rotorcraft Ext. Load
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Maneuvering
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On August 7, 2026, about 1044 mountain daylight time, a Helicopter Transport Services (Sikorsky) CH-54A Skycrane Helitanker, N793HT, was destroyed when it was involved in an accident near Cove Fort, Utah. The pilot and copilot were fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 133 aerial firefighting flight. The helicopter, owned and operated by Helicopter Transport Services, was conducting aerial fire suppression operations under an exclusive-use contract with the United States Forest Service (USFS) in support of the Wide Mouth 2 Fire in central Utah. It was equipped with a 2,650-gallon water tank and a retractable hover-snorkel system. According to the USFS, the helicopter departed Richfield Municipal Airport (RIF) about 1021 and proceeded toward the Wide Mouth 2 Fire to begin firefighting operations. After departure, the flight crew established radio communications with the aerial supervisor and received authorization to enter the temporary flight restriction (TFR) area surrounding the fire. The aerial supervisor briefed the crew on the initial firefighting objectives, which included coordinated aerial water-drop operations. The helicopter proceeded to a predetermined water source, filled its tank, and then continued to the designated drop area as directed. As the helicopter approached the drop site, the aerial supervisor transferred communications to the ground supervisor, who provided specific instructions regarding the target area. According to the ground supervisor, the helicopter arrived from the northwest, and he directed the crew to the location where water was needed. The helicopter then flew over the area to verify the target, and the flight crew confirmed they had identified the correct location. The crew subsequently reported that they would make another pass before releasing the water load. While maneuvering in a right turn, the helicopter disappeared behind a knoll. The ground supervisor then heard a radio transmission stating, “Oh (expletive), we have a problem,” followed about one second later by, “Mayday, mayday, mayday.” No further communications were received from the helicopter. The helicopter impacted rising terrain, and a post-crash fire consumed much of the airframe (see figure 1).

Figure 1. Aerial overview of accident site. (U.S. Forest Service Drone Photo) The investigator-in-charge from the NTSB’s Alaska Regional Office, accompanied by an NTSB aerospace engineer and helicopter specialist, responded to the accident site and examined the wreckage on August 9, 2026. During the on-scene investigation, components were retained for further examination and testing. The results of those examinations are pending. Recovery of the wreckage will take place when fire conditions and logistical considerations allow. A detailed examination of the airframe and engines is pending.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ANC26FA079
Event ID
20260807203546
Case number
ANC26FA079
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: f215a219b66c7ed5730876b81d6150cb5528003cc949da340003521fecba5614; retrieved 2026-09-15T09:19:25.438Z.