Accident Bell 407 N11SP, Friday 31 August 2012
ASN logo
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Friday 31 August 2012
Time:10:45
Type:Silhouette image of generic B407 model; specific model in this crash may look slightly different    
Bell 407
Owner/operator:State Of New York
Registration: N11SP
MSN: 53530
Year of manufacture:2002
Total airframe hrs:2918 hours
Engine model:Rolls Royce 250-C47B
Fatalities:Fatalities: 0 / Occupants: 1
Other fatalities:0
Aircraft damage: Substantial
Category:Accident
Location:Steuben County, near Bath, NY -   United States of America
Phase: En route
Nature:Unknown
Departure airport:Batavia, NY (GVQ)
Destination airport:Batavia, NY (GVQ)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot stated that the accident helicopter was configured for single-pilot operation (the copilot controls had been removed for the assigned mission). While in cruise flight between 110 and 120 knots and about 2,500 feet mean sea level, the helicopter began pitching up and yawing right, because the force trim was the “off” position, which rendered the altitude hold feature inoperative, and the pilot responded by pushing the cyclic forward and left. The helicopter then pitched “severely” nose down and entered a right spin. At that time, the pilot saw a portion of the tail boom, tail rotor, and tail rotor gearbox falling away separately from the helicopter. The pilot entered an autorotation and landed in wooded terrain. About 1 year after the accident, another pilot for the operator performed a maintenance test flight in a similarly configured make and model helicopter. While in cruise flight and with the force trim in the “off” position, the pilot released the cyclic momentarily, and the helicopter pitched up and rolled right. The flight scenario was duplicated several times with the copilot controls installed on the helicopter and, when the pilot released the cyclic, it maintained its same relative position, even with the force trim in the “off” position. Therefore, it appears that aerodynamic forces drove the cyclic aft in the single-pilot configured helicopter because the added weight and lever arm in a dual-pilot configured helicopter was not available to neutralize the forces. The manufacturer should have known about this characteristic of the helicopter and warned pilots of unanticipated and unequal aft cyclic pressure in the single-pilot configured helicopter compared to the dual-pilot configured helicopter. Detailed examination and testing of the helicopter and its components revealed no preaccident anomalies and no evidence of foreign object damage.

Probable Cause: The pilot's improper recovery from an in-flight upset, which resulted in the main rotor striking and separating the tail boom. Contributing to the accident was the helicopter manufacturer's failure to warn pilots of unanticipated and unequal aft cyclic pressure in the single-pilot configured helicopter compared to the dual-pilot configured helicopter, which resulted in the in-flight upset when the pilot momentarily let go of the cyclic control.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA12TA538
Status: Investigation completed
Duration: 1 year and 9 months
Download report: Final report

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
01-Sep-2012 02:55 gerard57 Added
03-Sep-2012 00:43 Anon. Updated [Registration, Operator, Phase, Nature, Source]
05-Sep-2012 09:40 Geno Updated [Time, Cn, Location, Source, Damage, Narrative]
28-Jul-2013 16:53 TB Updated [Location, Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
21-Sep-2017 19:38 Anon. Updated [Source, Narrative]
28-Nov-2017 13:15 ASN Update Bot Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org