FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA265 · Bell 407

2 Aug 2024 · Raft River, ID, United States

Brainerd Helicopter Services Bell 407 · Accident: electrical system malfunction/failure en route

From Elko Regional Airport (EKO) to Pocatello Regional Airport (PIH)

Report a problem

Event

NTSB case
WPR24LA265
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
Event fatalities
Unknown
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
Government
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

Bell 407

Aircraft type
Bell 407
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
N20BH
Onboard fatalities
Unknown
Route
From Elko Regional Airport (EKO), Elko, NVTo Pocatello Regional Airport (PIH), Pocatello, ID
Aircraft age
About 26 years (built 1998)
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
Public Aircraft
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 · cruise
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
Electrical system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Environmental issues › Task environment
  • Personnel issues › Action/decision
  • Personnel issues › Physical
  • Personnel issues › Psychological

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 of the helicopter departed on the final stage of a multileg public use contract flight to reposition a helitack crew. The U.S. Forest Service (USFS) contract specified that operations were restricted to day visual meteorological conditions; the planned arrival time at the destination was about 30 minutes after sunset and just short of the 14-hour limit of the pilot’s duty day.

Review of onboard video recordings revealed that, about 18 minutes after takeoff while in level flight, the measured gas temperature (MGT) exceeded the limits allowed for cruise flight. The overtemperature indication triggered a “CHECK INSTR” annunciation and an exceedance recorded by the MGT gauge, which could only be reset by a mechanic after the flight. Following this, the pilot then appeared to reduce engine power and continued the flight.

About 30 minutes later, the barrier inlet filter caution light illuminated. The pilot found this indication unusual, because the filter had been serviced the week prior. He activated the filter bypass system and continued with the flight. Due to arrival time constraints, the crew discussed the option of diverting to an alternate airport and staying there overnight; however, they ultimately decided to continue to the destination.

Shortly thereafter, the MGT gauge began to indicate a temperature increase into the yellow range and then the red range, accompanied by another “CHECK INSTR” warning. The pilot perceived this indication, and the helicopter’s response as he began to troubleshoot, as evidence of an engine overspeed condition, and he chose to initiate a precautionary landing to an open field nearby. Review of the cockpit video, however, revealed that none of the other engine gauges corroborated the high MGT reading, consistent with an erroneous MGT indication. When his control inputs failed to arrest the perceived overspeed or restore normal engine response, the pilot entered an autorotation to a closer cornfield.

The autorotation was conducted during the diminishing ambient light conditions of dusk. The lighting conditions, combined with the height of the corn, obscured the pilot’s depth perception and limited his ability to accurately judge the timing of the landing flare, resulting in a hard landing. Impact forces were sufficient to cause separation of the main transmission, fragmentation of drive system components, and extensive secondary damage to the engine, including fragmentation of the turbine wheels after hard-body ingestion.

Postaccident examination revealed no evidence of pre-impact mechanical failure, fatigue, or thermal distress of the engine, and review of the engine control unit’s (ECU) non-volatile memory did not reveal any event indicative of an engine overspeed, overtemperature, or associated malfunction. Bench testing of the MGT gauge did not reveal any anomalies, and despite the in-flight display irregularities, the gauge recorded only one exceedance, which appeared to match the initial overtemperature indication observed earlier in the flight. However, the erroneous displays observed during the flight could be simulated during bench testing by lowering and then restoring the unit’s electrical supply voltage. Therefore, the condition was likely caused by an undetermined disruption in the electrical supply to the MGT gauge.

The accident sequence was initiated by compounding operational stressors. The accident occurred at the end of a long duty day for the pilot, who likely was beginning to feel the effects of fatigue, and the flight was conducted at a time of day that would have created significant time pressure. The pilot then allowed the engine to operate above normal MGT levels, possibly to expedite arrival. Although power was reduced and the flight continued, the overtemperature indication further increased the pilot’s cognitive workload, and the need for a mechanic to intervene later would have been an additional stressor.

The unexpected barrier inlet filter annunciation that followed likely increased the pilot’s anxiety, and although a diversion was discussed, the prospect of an overnight stop and the resulting logistical impacts contributed to plan continuation bias. Subsequent anomalous MGT indications became the triggering event that overwhelmed the pilot, who misdiagnosed the symptoms as a developing engine problem that he likely attributed to the earlier issues.

Probable cause

The pilot’s misdiagnosis of an erroneous engine instrument indication and his subsequent decision to enter an autorotation, which resulted in a hard landing due to degraded visual cues and low ambient light conditions. Contributing to the accident were the erroneous engine indications likely caused by an undetermined electrical supply disruption; time pressure, pilot fatigue, and plan continuation bias as daylight diminished and the crew aimed to complete the flight; and cognitive overload from multiple airframe and engine caution indications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA265
Event ID
20240805194840
Case number
WPR24LA265
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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-08-03.
  • API snapshot SHA-256: 2f88e7c3a36ed620ba3d337a3ba9c26ffd19551e4db061c22b1825e80480167d; retrieved 2026-09-16T19:07:40.772Z.