WPR14LA014 · Bell Helicopter Textron 206L 1
Blackhawk Helicopters Bell Helicopter Textron 206L 1 · Accident: fire/smoke (non-impact) while maneuvering
From Yuma International Airport / Marine Corps Air Station Yuma (NYL) to Gillespie Field (SEE)
Event
- NTSB case
- WPR14LA014
- 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
- 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
Bell Helicopter Textron 206L 1
- Aircraft type
- Bell 206
- 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
- N206KK
- Operator
- Blackhawk Helicopters
- Onboard fatalities
- Unknown
- Route
- From Yuma International Airport / Marine Corps Air Station Yuma (NYL), Yuma, AZTo Gillespie Field (SEE), El Cajon, CA
- 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 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
- Maneuvering · low-altitude flying
- 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
- Fire/smoke (non-impact)
- 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 from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during cruise flight, he heard a loud pop and that, immediately after, the engine lost power. The pilot subsequently performed an autorotation. During the autorotation, the left front door opened, and the cabin then filled with black smoke. The pilot subsequently landed the helicopter upright in an open area, and he and the passengers egressed. The pilot stated that, upon exit, he saw fire originating from about 2 ft aft of the right forward door; the fire consumed most of the helicopter.
Examination of the helical power train drive assembly revealed that the No. 4 bearing rollers were exposed to intense heat and that one of the rollers exhibited evidence of flat spotting, consistent with a skidding roller. The No. 4 bearing separator was fractured through one roller pocket at three locations, and the fracture surfaces were oxidized, which prevented the identification of a specific fracture mode. Signatures observed on the No. 4 bearing and the pinion gear were consistent with damage generated from the bearing spinning on the pinion gear. It is likely that the failure of the No. 4 bearing generated heat, which caused the expansion and softening of the aft end of the power train pinion gear and resulted in the gear disconnecting from the turbine shaft-to-pinion gear coupling splines. As a result of this disconnection, the load on the power turbine was suddenly removed, which resulted in an overspeed of the 3rd- and 4th-stage turbine wheels and the subsequent separation of their shrouds and blades, some of which were liberated from the engine. Several exit holes caused by high-energy debris were found in-line with the fuel control unit and power turbine governor, which likely was the source of the in-flight fire. Oil filters that had been retained by the operator's mechanic during previous troubleshooting were examined, and they contained particles consistent with two different alloys used to manufacture the pinion gear and bearing races, respectively, indicating that a problem existed before the accident flight.
About 15 years before the accident, the manufacturer issued a service bulletin (SB) that outlined the replacement of both the Nos. 3 and 4 bearings with updated bearings before the end of 2002, which was 11 years before the accident. During engine disassembly, the No. 3 bearing was found to have been replaced with the updated bearing as outlined in the SB; the maintenance logbooks did not indicate when this bearing was replaced. However, the No. 4 bearing was found to have the same serial and part numbers as the original bearings installed in the engine about 17 years before the accident. If the No. 4 bearing had been replaced in accordance with the SB, it likely would not have failed in flight, and the accident could have been prevented.
Probable cause
The total loss of engine power due to the failure of the No. 4 bearing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14LA014
- Event ID
- 20131016X31510
- Case number
- WPR14LA014
- 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. 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: 1d98a3709d80ed5370d46ad5dfab8159f3414e1370c5075a056b7555fecb0d3b; retrieved 2026-09-15T22:57:18.363Z.