SOCATA TBM 700 near Mt. Pleasant, WI — 2011-09-05
- Date
- 2011-09-05
- Location
- Mt. Pleasant, WI, USA
- Aircraft
- SOCATA TBM 700
- Registration
- N850SY
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 1
- Phase of flight
- Descent
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.
Contributing factors
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.
NTSB 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.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have diverted to available airports after first loss of engine torque.
NTSB coding
Evidence available
- ATC audio
- ADS-B / radar
- Photos
- 29 docket documents
Docket documents29
- ATC Transcript (CWA)atc
- ATC Transcript (MKE)atc
- Plots of recorded accident flight datafdr
- Additional Maintenance informationform
- Excerpt from Pilot's Information Manualform
- Release of Aircraft Wreckage and evidence control formsform
- Accident flight data from G1000 systemother
- Airplane Maintenance Manual Excerptsother
- Airplane maintenance recordsother
- Engine examination notes (Pratt & Whitney)other
- Flight data download from test flightother
- Pilot logbook recordsother
- Pilot training records from Turbine Solutions Inc.other
- Plot of aircraft flight pathother
- Plot of aircraft flight path 2other
- Socata-G1000 cockpit reference guide excerptother
- Photo 1 - Left side view of wreckagephotos
- Photo 10 - View of engine after removalphotos
- Photo 2 - Front view of wreckagephotos
- Photo 3 - Right side view of wreckagephotos
- Photo 4 - Rear view of wreckagephotos
- Photo 5 - View of rudder and trim tabphotos
- Photo 6 - View of front of fuselagephotos
- Photo 7 - View of propellerphotos
- Photo 8 - View from main wreckage looking south toward the initial impact pointphotos
- Photo 9 - View from initial impact point toward wreckagephotos
- Toxicological Reportreport
- Wisconsin State Police Reconstruction Reportreport
- Wreckage Examination Noteswreckage
Related mishaps
- CESSNA U206F
2026-04-16 · Juneau, AK
- CESSNA 152
2026-03-03 · Thonotosassa, FL
- ZENITH 750
2025-12-23 · Yacolt, WA
- CIRRUS DESIGN CORP SR22T
2025-09-11 · Racine, WI
- BEECH E33
2025-02-25 · Lenoir, NC
- QUICKSILVER AERONAUTICS LLC L-S2S
2025-02-17 · Geyserville, CA