Bell 206L 1 N206KK
11 October 2013 · Seeley, California, United States · No injuries
Summary
On 11 October 2013 at about 19:44 local time, a Bell 206L 1 registered N206KK, operated by Blackhawk Helicopters Inc, was involved in an accident near Seeley, California, United States. 3 people were on board and nobody was injured. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 19:44
- Classification
- Accident
- Location
- Seeley, California, United States
- Coordinates
- 32.7019, -115.7728
- Aircraft
- Bell 206L 1
- Registration
- N206KK
- Category
- Helicopter
- Engines
- 1
- Operator
- Blackhawk Helicopters Inc
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Aerial Observation
- Phase of flight
- Not recorded
- Route
- Yuma → El Cajon
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR14LA014
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 3 | 0 | 0 | 0 | 3 |
Probable cause
The total loss of engine power due to the failure of the No. 4 bearing.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full 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.
Quoted verbatim from the NTSB record.
Other Bell 206 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Feb 2013 | Bell 206B | Acton, California, United States | Orbic Air | Fatal | 3 |
| 10 Feb 2013 | Bell 206B | Shandon, California, United States | Sycan Corp DBA | No injuries | - |
| 7 Jun 2013 | Bell 206B | San Luis PotosÃ, Mexico | - | Fatal | 4 |
| 7 Sep 2013 | Bell 206L-3 | Amistad, New Mexico, United States | State of Illinois | Minor injuries | - |
| 11 Feb 2013 | Bell 206B III | Ponderosa, New Mexico, United States | Aerowest Helicopter Svc | No injuries | - |
| 20 Apr 2013 | Bell 206B | Wells, Nevada, United States | Reeder Flying Service | No injuries | - |
All 1,732 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 9 Sep 2013 | Grumman American Avn AA 1C | Hemet, California, United States | William Ralph Eddings | Minor injuries | - |
| 12 Feb 2013 | St Clair LANCAIR 360 | Williams, California, United States | - | Serious injuries | - |
| 14 Feb 2013 | Avions Fairey TIPSY NIPPER T-66 | Winters, California, United States | Sharman Enterprises Inc | Fatal | 1 |
| 9 Sep 2013 | Cessna 172N | Long Beach, California, United States | - | No injuries | - |
| 11 Jun 2013 | Cirrus SR22 | Truckee, California, United States | - | No injuries | - |
| 11 Sep 2013 | Bell 47G5 | King City, California, United States | Wilbur-Ellis Co | No injuries | - |