FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW03FA148 · Bell 407

11 May 2003 · Gulf Of Mexico, United States

Bell 407 · Accident: airframe, component or system failure en route

From EI 380, GOM, GM to Franklin Foundation Hospital Heliport (9LA7)

Report a problem

Event

NTSB case
FTW03FA148
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
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
Charter & commuter
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
N491PH
Operator
Unknown
Onboard fatalities
Unknown
Route
From EI 380, GOM, GMTo Franklin Foundation Hospital Heliport (9LA7), Morgan City, LA
Aircraft age
Not recorded
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 135: Air Taxi & Commuter
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
First occurrenceThe 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
Airframe, component or system 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

  • Electrical system › Failure
  • Electrical system › Shorted

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

NTSB narrative

The helicopter, which had a FADEC controlled turboshaft engine installed, was in cruise flight (about 800 feet AGL) over open ocean water when the FADEC FAIL aural warning sounded, followed closely by sound of the LOW ROTOR RPM horn. Simultaneously, the LOW ROTOR RPM, FADEC FAIL, and FADEC FAULT cockpit caution lights illuminated. The 8,300-hour helicopter pilot attempted to regain the RPM's with no result. The FADEC AUTO/MANUAL indicator light/button showed the engine control mode to be in the "AUTO" condition. The pilot recalls that the Ng was approximately 89%. The pilot stated that about 10 seconds elapsed from the onset of the event to cross checking the Ng. The pilot then depressed the AUTO/MANUAL button and switched to the MANUAL mode. He then increased the throttle above the 90% detent to try to regain rotor RPM's. He recalled that the light displayed "MANUAL", and that the FADEC FAIL aural warning ceased after the button was depressed. While descending, on three separate occasions, the pilot attempted to increase the throttle which were accompanied by three uncommanded right yaws, approximately 1-2 seconds apart. During the third uncommanded yaw, the ENGINE OUT audio sounded and the ENGINE OUT light illuminated (these occur when Ng drops below 55%). The pilot then entered a full autorotation, deployed the skid mounted emergency float system and landed upright on the water. Metallurgical examination of the 1st thru 4th stage turbine wheels and 1st thru 3rd stage turbine nozzles, revealed that all associated damage was due to extreme over-temperature operation. The manual mode schedule of the Hydro-mechanical Unit (HMU) was found within limits, and the auto mode schedule had a flow shift of +10 to +15 PPH. Evaluation and testing of the Electronic Control Unit (ECU) and its sub-components revealed a shorted condition on the ECU -15V power supply. Disassembly of the ECU and tests of the Interface (IF) and Power (PWR) circuit boards revealed that the C321 capacitor (p/n CDR33BX104AKUR) on the IF board was found thermally distressed and was measured at .58 ohms. The C321 is a high frequency bypass capacitor from -15V to ground. The PWR board was also visually inspected and the CR423 diode was found thermally stressed. According to the manufacturer, the CR423 diode provides rectification on the -15V power supply and was likely stressed as a result of the shorted C321 capacitor. The C321 capacitor was removed from the IF board and there was no longer a short on the -15V power supply. The ECU was re-assembled, operated, and passed a functional acceptance test after removal of the C321 capacitor. The shorted condition of the C321 capacitor forced the -15V power supply to a low voltage condition and a significant current draw, resulting in the rectifying diode to overheat. According to the manufacturer, the -15V power failure of the ECU resulted in the HMU to revert to manual fuel metering. In the manual mode, the engine would have overspeed protection, but not overtemperature protection.

Probable cause

The short circuit of the C321capacitor in the Electronic Control Unit (ECU) that resulted in a single-point failure of the ECU's -15V power supply which disengaged/reverted the Hydro-mechanical Unit (HMU) from automatic to manual fuel control. Factors contributing to the accident were the pilot's attempted remedial actions in the manual mode that resulted in the engine over temperature and loss of power, and the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW03FA148
Event ID
20030519X00686
Case number
FTW03FA148
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 4d7c33c834483ce52f3012c43f231fd92cca65d79546e51c1e40bd7f3cdea4e1; retrieved 2026-09-18T15:49:13.853Z.