Accident Socata TBM700N (TBM850) N850SY,
ASN logo
ASN Wikibase Occurrence # 138384
 
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:Monday 5 September 2011
Time:18:33
Type:Silhouette image of generic TBM8 model; specific model in this crash may look slightly different    
Socata TBM700N (TBM850)
Owner/operator:Green Plane LLC
Registration: N850SY
MSN: 546
Year of manufacture:2010
Total airframe hrs:217 hours
Engine model:P&W Canada PT6A-66 SER
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:Mt. Pleasant, WI -   United States of America
Phase: En route
Nature:Private
Departure airport:Mosinee, WI (CWA)
Destination airport:Waukegan, IL (UGN)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
During cruise flight, the pilot reported to an air traffic controller that the airplane was having engine fuel pressure problems. The controller advised the pilot of available airports for landing if necessary and asked the pilot's intentions. The pilot chose to continue the flight. GPS data recorded by an onboard avionics system indicated that the engine had momentarily lost total power about 20 seconds before the pilot reported a problem to the controller. About 7 minutes later, when the airplane was about 7,000 feet above ground level, the engine lost total power again, and power was not restored for the remainder of the flight. The pilot attempted to glide to an airport about 10 miles away, but the airplane crashed in a field about 3 miles from the airport.
GPS data showed a loss of fuel pressure before each of the engine power losses and prolonged lateral g-forces consistent with a side-slip flight condition. The rudder trim tab was found displaced to the left about 3/8 inch. Flight testing and recorded flight data revealed that the rudder trim tab displacement was consistent with that required to achieve no side slip during a typical climb segment. The GPS and flight data indicated that the lateral g-forces increased as the airplane leveled off and accelerated, indicating that the automatic rudder trim feature of the yaw damper system was either not engaged or not operating. The recorded data indicated autopilot system engagement, which should have automatically engaged the yaw damper system. However, the data indicated the yaw damper was not engaged; the yaw damper could have subsequently been turned off by several means not recorded by the avionics system. Testing of the manual electric rudder (yaw) trim system revealed no anomalies, indicating that the pilot would have still been able to trim the airplane using the manual system. It is likely that the pilot’s failure to properly trim the airplane’s rudder led to a prolonged uncoordinated flight condition. Although the fuel tank system is designed to prevent unporting of the fuel lines during momentary periods of uncoordinated flight, it is not intended to do so for extended periods of uncoordinated flight. Therefore, the fuel tank feed line likely unported during the prolonged uncoordinated flight, which resulted in the subsequent loss of fuel pressure and engine power.
The propeller and propeller controls were not in the feathered position, thus the windmilling propeller would have increased the airplane’s descent rate during the glide portion of the flight. The glide airspeed used by the pilot was 20 knots below the airspeed recommended by the Pilot's Operating Handbook (POH), and the reduced airspeed also would have increased the airplane’s descent rate during the glide. The flight and GPS data indicated that the airplane had a gliding range of about 16 nautical miles from the altitude where the final loss of engine power occurred; however, the glide performance was dependent on several factors, including feathering the propeller and maintaining the proper airspeed, neither of which the pilot did. Although the POH did not contain maximum range glide performance data with a windmilling propeller, based on the available information, it is likely that the airplane could have glided to the alternate airport about 10 miles away if the pilot had followed the proper procedures.
Probable Cause: The pilot’s failure to properly trim the airplane’s rudder during cruise flight, which resulted in a prolonged uncoordinated flight condition, unporting of the fuel tank feed line, and subsequent fuel starvation and engine power loss. Contributing to the accident was the pilot’s failure to feather the engine’s propeller and maintain a proper glide airspeed following the loss of engine power.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN11FA625
Status: Investigation completed
Duration: 2 years and 8 months
Download report: Final report

Sources:

NTSB
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=850SY

Location

Revision history:

Date/timeContributorUpdates
06-Sep-2011 01:39 gerard57 Added
06-Sep-2011 02:05 gerard57 Updated [Operator, Source]
06-Sep-2011 02:16 gerard57 Updated [Aircraft type, Source]
06-Sep-2011 03:33 RobertMB Updated [Aircraft type, Registration, Cn, Operator, Other fatalities, Location, Departure airport, Destination airport, Source, Narrative]
06-Sep-2011 03:56 RobertMB Updated [Cn, Operator, Location, Destination airport, Source, Narrative]
06-Sep-2011 05:26 Alpine Flight Updated [Time, Aircraft type]
06-Sep-2011 06:01 RobertMB Updated [Aircraft type, Narrative]
06-Sep-2011 06:16 RobertMB Updated [Aircraft type, Cn, Narrative]
07-Sep-2011 22:19 Geno Updated [Location]
14-Sep-2011 12:43 HH Updated [Location, Narrative]
13-Oct-2011 12:14 Anon. Updated [Source, Narrative]
31-Jul-2016 15:07 Dr.John Smith Updated [Time, Operator, Location, Departure airport, Destination airport, Source, Narrative]
31-Jul-2016 15:08 Dr.John Smith Updated [Source]
21-Dec-2016 19:26 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Nov-2017 17:13 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]
27-Aug-2018 15:47 wf Updated [Operator, Source, Damage]
12-Aug-2020 13:23 Captain Adam Updated [Other fatalities, Location]

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