WPR23LA306 · Boeing CH-46E
Sky Aviation Boeing CH-46E · Accident: loss of engine power (partial) en route
From Show Low Regional Airport (KSOW) to an unrecorded destination
Event
- NTSB case
- WPR23LA306
- 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
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Boeing CH-46E
- Aircraft type
- Boeing CH-46
- 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
- N461WY
- Operator
- Sky Aviation
- Onboard fatalities
- Unknown
- Route
- From Show Low Regional Airport (KSOW), Show Low, AZTo not recorded
- Aircraft age
- About 55 years (built 1968)
- 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 91: General Aviation
- 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
- En route
- 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
- Loss of engine power (partial)
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot in command (PIC) reported that the crew had performed firefighting water drop activities for about 2 hours. After they had filled the bucket with water and began to climb, they heard an extremely loud horn in their helmets—loud enough that it was difficult to understand what was being said. The pilot noticed that the No. 2 engine torque indicator was “maxed out” and the No. 1 torque indicator was about 60%. The pilot released the water in the bucket and initiated a turn to an open field. The pilot then slowly retarded the No. 2 engine control lever out of the FLY position (which took it out of the governing range and into manual mode) to match the torque. He noted that the torque for both engines matched about 90%. Upon turning final for his intended landing field, the pilot noticed that the descent rate increased. The pilot told his copilot to jettison the bucket as he placed the No. 2 engine control lever back into the FLY position. Subsequently, the helicopter landed hard and rolled onto its right side. The engines were shut down and the co-pilot and crew chief assisted the pilot in exiting the helicopter while a postimpact fire ensued. Postaccident examination of the wreckage showed no evidence of a preimpact engine failure or anomaly that would have precluded normal engine operation. The examination determined that a flex shaft failure did not occur because the cockpit torquemeter displayed Nf values on both engines and each engine’s flex shaft continuity was confirmed. The No. 2 engine signal conditioner, torquemeter relay box, and both torquemeters were destroyed in the post-crash fire and could not be examined. Helicopter performance calculations for the conditions at the time of the accident show that each engine was only capable of producing a maximum of 85% torque. Neither engine could produce the 100% torque required to trigger the aural overtorque tone, nor was capable of producing the 107% or higher torque required to activate the overtorque indicators on the torque meter. Accordingly, a maximum beep failure did not occur, because neither engine could produce the torque required to trigger the overtorque alarms. When the PIC heard the overtorque alarm and saw a split in the torque needles, he diagnosed the problem as a “high side failure,” meaning that the engine was producing uncommanded maximum/topping power. However, neither pilot said that they looked to see if either rotation speed of the power turbine (Nf) needles were at zero; in fact, the PIC saw that both Nf needles were reading accurate power turbine speeds. After the PIC retarded the No. 2 engine, the overtorque tone did not go away once the engines were indicating less than 100% torque. Because the pilot’s torquemeter (which records overtorque events generated by the No 2 engine signal conditioner) indicated 143% overtorque, and all 3 overtorque indicators were red, the No. 2 engine signal conditioner likely malfunctioned and provided false torque readings and overtorque warnings. Once the PIC took the No. 2 engine out of its governing range, the No. 2 engine was at minimum power, and performance calculations show that the helicopter was not single-engine capable in level flight or hover. The PIC subsequently made a steep landing approach that required more power than was available with one engine. Realizing the need for additional power, the PIC moved the No. 2 engine rapidly to the FLY position; however, that rapid movement likely activated the fail-freeze circuitry, freezing the engine at the minimum power position and switching it to manual mode. Without additional power from the No. 2 engine, the landing approach descent rate could not be arrested and resulted in a hard landing.
Probable cause
The flight crew’s misidentification of a No. 2 torque sensing system signal conditioner malfunction when both engines were performing normally, which resulted in their attempt to execute a single-engine steep approach and landing without sufficient engine power. Contributing to the accident was the failure of the torque sensing system signal conditioner.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA306
- Event ID
- 20230807192818
- Case number
- WPR23LA306
- 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, cause areas. 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: 1905ac4f8c123a1a46449f7a3bbafee5116971c53d9098dc0f7275cfe91d5206; retrieved 2026-09-16T17:58:34.635Z.