Helicopter Transport Services CH-54A accident near Cove Fort, Utah, August 7, 2026
On August 7, 2026 at about 4:44 pm local time, a 1967 Helicopter Transport Services CH-54A, registered N793HT, was destroyed in an accident during maneuvering near Cove Fort, Utah. It was a firefighting flight under external-load helicopter rules (Part 133). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 7, 2026 · about 4:44 pm local time
- Place
- Cove Fort, Utah · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Helicopter Transport Services CH-54A, built 1967 · all CH-54As on the register
- Registration
- N793HT · registry record · serial 67-18427
- Damage
- Destroyed
- Flight
- Firefighting flight · external-load helicopter rules (Part 133)
The NTSB's narrative preliminary · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Unknown or undetermined during maneuvering defining event
The aircraft
- Airframe total time: 7,667.8 hours
- Last inspection: approved inspection programme, August 1, 2026
- Maximum gross weight: 42,000 lb
- Seats: 3
- Landing gear: fixed
- Fire on the ground
- Operator: Helicopter Transport Services
The flight
- Departed from: KRIF Richfield UT at 4:21 pm
- Destination: KRIF Richfield UT
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 220° at 13 knots, gusting 22
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 48°F (9°C)
- Altimeter: 30.24 inHg
- Observation at 11:00 am from KMLF, 30 miles away
Weather report (METAR): METAR KMLF 071652Z AUTO 22013G22KT 10SM CLR 30/09 A3024 RMK AO2 SLP158 T03000094
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
