BELL 427 near Indiantown, FL — 2012-06-04
- Date
- 2012-06-04
- Location
- Indiantown, FL, USA
- Aircraft
- BELL 427
- Registration
- N427AL
- Category
- Helicopter
- Highest injury
- Minor
- Fatalities
- 0
- Phase of flight
- Maneuvering
Probable cause
The inflight collision with birds, resulting in damage to the rotor head assembly and a subsequent forced landing and rollover.
NTSB narrative
The pilot reported that, about 25 minutes into the flight, he maneuvered the helicopter to avoid large birds. The pilot felt something impact the upper right side of the helicopter near the main rotor mast area. The helicopter began shaking violently and became difficult to control. He immediately decided to abort the flight. During the landing attempt, helicopter control was lost; the helicopter entered a left spin, impacted the ground, and rolled over. The main and tail rotor systems and the fuselage sustained substantial damage. The immediate decision to abort the flight after impact with the birds most likely aided the pilot in executing an emergency landing. Evidence of bird remains were present on components of the rotor head, two of the four pitch change rods, and the tail rotor. Both pitch change rods with bird remains were separated from one of their attach points. The bird remains were removed and sent to the Smithsonian Institute for identification. According to the report, male and female Black Vulture DNA was found on the pitch control rods, pitch control linkages, and the tail rotor. Examination of the rotor head parts found two pitch change links failed in tensile overstress; one of these exhibited an inward bending that could have been caused by a bird strike. The damage to the other pitch change link was most likely caused by the dynamic rollover as the rotor blades impacted the ground or other helicopter components. The accident sequence most likely initiated when the birds struck the pitch change rods.
Analysis
- Primary failure mode
- Environmental
- First missed decision gate
- Pilot could have chosen a different route to avoid bird strike.
NTSB coding
Evidence available
- FDR / data
- Photos
- 16 docket documents
Docket documents16
- Evidence Control Form. (FAA)form
- Other Pertinent Forms and Reportsform
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Witness Statementinterview
- Maintenance Record Excerpts.other
- Materials Laboratory 15 - Factual Report 12-108 (with 1 embedded image)photos
- Photo 1: Bird remains present on the Blue Diamond Blade. (Courtesy of FAA)photos
- Photo 2: Bird remains present on the green circle blade. (Courtesy of FAA)photos
- Photo 3: Overview of fuselage and tail. (Courtesy of FAA)photos
- Photo 4: #1 Pitch control link with hair samples attached. (Courtesy of FAA)photos
- Photo 5: Rotor head and pitch link damage. (Courtesy of FAA)photos
- GPS 17 - Specialist's Factual Reportreport
- NVM 18 - Attachment 1 - PWC Download Reportreport
- NVM 18 - Specialist's Factual Reportreport
- Wreckage Diagram. (Courtesy of FAA)wreckage
- Wreckage Release.wreckage
Related mishaps
- PIPER PA-28-180
2026-03-29 · Greenville, SC
- PIPER PA28R
2025-09-27 · Okeechobee, FL
- BELL HELICOPTER TEXTRON 206L-1
2024-10-27 · Canal Winchester, OH
- BELL 206
2024-01-21 · Hydro, OK · 3 fatalities
- PIPER PA-28
2023-07-11 · Gray, GA
- AIRBUS HELICOPTERS EC 130 T2
2022-12-13 · Yuba City, CA