FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Panther Helicopters Bell 407 accident

7 Dec 2019 · Gulf of Mexico, GM, United States

Bell 407 · Accident: powerplant system/component malfunction/failure en route

From Oil Platform WD109, GM to Oil Platform WD73, GM

Report a problem

Event

NTSB case
CEN20FA035
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
2 · 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
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
N79LP
Onboard fatalities
Unknown
Route
From Oil Platform WD109, GMTo Oil Platform WD73, GM
Aircraft age
About 23 years (built 1996)
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
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
Powerplant system/component 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
Destroyed

Cause areas

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The helicopter was flying over the Gulf of Mexico between two oil platforms. Flight track data showed the helicopter in cruise flight at 700 ft mean sea level (msl) before it gradually descended to 375 ft msl. Just before the data ended, the helicopter entered a left turn, descended to 150 ft msl, and slowed from about 115 knots (kts) groundspeed to about 75 kts groundspeed. The helicopter impacted the water and sank to the sea floor. The main wreckage was eventually located on the sea floor about 350 ft southwest of the last recorded flight track point.

Examination of the engine revealed that the power turbine pinion gear teeth were significantly worn and smeared, which ultimately resulted in the engine’s inability to provide power to the rotor system. While the majority of the No. 3 bearing was not recovered, the significant thermal damage and loss of material of the power turbine pinion gear shoulder, to which the No. 3 bearing inner race was installed, indicated that the bearing likely failed first, but the cause of the No. 3 bearing failure could not be determined because the bearing was not recovered. The failure of the No. 3 bearing could result in misalignment of the gear mesh between the power turbine pinion gear and the torquemeter gear, which likely caused the pinion gear teeth to rapidly degrade and/or fracture. The initial failure of the No. 3 bearing would have resulted in the failure of the No. 4 bearing and the power turbine pinion gear. The reasons why damage to the Nos. 3 and 4 bearings and the power turbine pinion gear did not result in an engine chip light or oil filter contamination, leading to a filter bypass indication, could not be determined based on the available evidence.

The blockages observed in the oil delivery tube and oil nozzle were consistent with corrosion, likely due to postaccident saltwater immersion; therefore, whether there were any preexisting anomalies of the oil delivery tube jets and/or the oil nozzle, such as oil coking, could not be determined. However, the remainder of the recovered engine bearings and gears did not show evidence of damage associated with a widespread lubrication issue.

Analysis of the caution and warning panel bulb filaments showed that several annunciator lights were illuminated at the time of impact, consistent with the effects of a loss of engine power due to a failure of the power turbine pinion gear. The main rotor rpm warning light would have illuminated within a second of the loss of engine power as main rotor speed (Nr) decreased, and the hydraulic system and transmission oil pressure annunciator lights would have illuminated once Nr decreased to critical levels. The data downloaded from the helicopter’s engine control unit was also consistent with a loss of engine power and subsequent loss of Nr.

While collective pitch was reduced for a few seconds after the loss of engine power, collective pitch was subsequently increased, which led to a quicker decay of Nr. The substantial decrease in Nr would have affected controllability of the helicopter and ultimately resulted in a loss of control. The pilot’s cyclic and pedal inputs, as well as the helicopter’s attitude and airspeed, at the time of the loss of engine power were not known. Therefore, it could not be determined if the pilot successfully entered autorotation or the reasons why the pilot increased collective control about 3 seconds after the loss of engine power. There was no evidence that the emergency flotation system was deployed. While flight track data for the accident flight was available, the last few data points were discontinuous and could not be reliably matched with the recorded engine data; therefore, it could not be determined if the pilot was in a position to deploy the emergency flotation system following the loss of power.

Probable cause

A total loss of engine power due to the failure of the engine’s Nos. 3 and 4 bearings and the power turbine pinion gear, and subsequent loss of main rotor rpm, which resulted in a loss of control and impact with the water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20FA035
Event ID
20191209X55719
Case number
CEN20FA035
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, 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: dff8da92b1e02dd6f545d80688ddd044887e98051c551a0549ccebce4b56fe67; retrieved 2026-09-15T07:09:27.321Z.