Atlanta – Pine Mountain
Flight / Schedule
Atlanta – Pine Mountain
Aircraft
Socata TBM-850Registration
N536EM
MSN
536
Year of Manufacture
2010
Operator
TBM 850 536Date
October 5, 2014 at 12:55 PM
Type
CRASHFlight Type
Private
Flight Phase
Flight
Crash Site
Plain, Valley
Crash Location
Fayetteville Georgia
Region
North America • United States of America
Coordinates
33.4487°, -84.4549°
Crash Cause
Human factor
Narrative Report
On October 5, 2014 at 12:55 PM, Atlanta – Pine Mountain experienced a crash involving Socata TBM-850, operated by TBM 850 536, with the event recorded near Fayetteville Georgia.
The flight was categorized as private and the reported phase was flight at a plain, valley crash site.
2 people were known to be on board, 0 fatalities were recorded, 2 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 1, crew fatalities: 0, passengers on board: 1, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. The private pilot was conducting a personal cross-country flight. The pilot reported that, during cruise flight at 6,000 ft mean sea level, he observed a crew alerting system oil pressure message, followed by a total loss of engine power. An air traffic controller provided vectors to a local airport; however, the pilot reported that the airplane would not reach the runway. He did not attempt to restart the engine. He feathered the propeller and placed the power lever to "idle" and the condition lever to "cut off." The pilot subsequently attempted a forced landing to a sports field with the gear and flaps retracted. The airplane collided with trees and the ground and then came to rest upright. Examination of the engine revealed that it displayed contact signatures to its internal components and evidence of ingested unburned organic debris, consistent with the engine likely being unpowered and the engine gas generator and power sections wind-milling at the time of impact. No evidence of any preimpact mechanical anomalies or malfunctions to any of the engine components was found that would have precluded normal operation. Recorded GPS flight track and systems data showed that the loss of engine power was preceded by about 5 minutes of flight on a constant heading and altitude with an excessive lateral g force of about 0.17 g and a bank angle between about 8 and 10 degrees, consistent with a side-slip flight condition. The airplane then entered a right turn with the autopilot engaged, and it lost power at the end of the turn. The data indicated that, even though the autopilot was engaged, 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 not engaged. Given that the yaw damper system operated normally after the flight, it is likely that the pilot inadvertently and unknowingly disengaged the yaw damper during flight with the autopilot engaged. During a postaccident interview, the pilot stated that he was not aware of a side-slip condition before the loss of engine power. Although the fuel tank system was designed to prevent unporting of the fuel lines during momentary periods of uncoordinated flight, it was 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 engine power. If the pilot had recognized the side-slip condition, he could have returned to coordinated flight and prevented the engine power loss. Also, once the airplane returned to coordinated flight, an engine restart would have been possible.
Aircraft reference details include registration N536EM, MSN 536, year of manufacture 2010.
Geospatial coordinates for this crash are approximately 33.4487°, -84.4549°.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
The private pilot was conducting a personal cross-country flight. The pilot reported that, during cruise flight at 6,000 ft mean sea level, he observed a crew alerting system oil pressure message, followed by a total loss of engine power. An air traffic controller provided vectors to a local airport; however, the pilot reported that the airplane would not reach the runway. He did not attempt to restart the engine. He feathered the propeller and placed the power lever to "idle" and the condition lever to "cut off." The pilot subsequently attempted a forced landing to a sports field with the gear and flaps retracted. The airplane collided with trees and the ground and then came to rest upright. Examination of the engine revealed that it displayed contact signatures to its internal components and evidence of ingested unburned organic debris, consistent with the engine likely being unpowered and the engine gas generator and power sections wind-milling at the time of impact. No evidence of any preimpact mechanical anomalies or malfunctions to any of the engine components was found that would have precluded normal operation. Recorded GPS flight track and systems data showed that the loss of engine power was preceded by about 5 minutes of flight on a constant heading and altitude with an excessive lateral g force of about 0.17 g and a bank angle between about 8 and 10 degrees, consistent with a side-slip flight condition. The airplane then entered a right turn with the autopilot engaged, and it lost power at the end of the turn. The data indicated that, even though the autopilot was engaged, 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 not engaged. Given that the yaw damper system operated normally after the flight, it is likely that the pilot inadvertently and unknowingly disengaged the yaw damper during flight with the autopilot engaged. During a postaccident interview, the pilot stated that he was not aware of a side-slip condition before the loss of engine power. Although the fuel tank system was designed to prevent unporting of the fuel lines during momentary periods of uncoordinated flight, it was 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 engine power. If the pilot had recognized the side-slip condition, he could have returned to coordinated flight and prevented the engine power loss. Also, once the airplane returned to coordinated flight, an engine restart would have been possible.
Cause: Human factor
Occupants & Outcome
Crew On Board
1
Passengers On Board
1
Estimated Survivors
2
Fatality Rate
0.0%
Known people on board: 2
Operational Details
Schedule / Flight
Atlanta – Pine Mountain
Operator
TBM 850 536Flight Type
Private
Flight Phase
Flight
Crash Site
Plain, Valley
Region / Country
North America • United States of America
