ASN Wikibase Occurrence # 170310
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: | Sunday 5 October 2014 |
| Time: | 12:55 |
| Type: |  Socata TBM700N (TBM850) |
| Owner/operator: | TBM 850 536 LLC |
| Registration: | N536EM |
| MSN: | 536 |
| Year of manufacture: | 2010 |
| Total airframe hrs: | 719 hours |
| Engine model: | P&W PT6A66D |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | SE of Atlanta Regional Airport-Falcon Field (KFFC), Atlanta, GA -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Atlanta-DeKalb Peachtree Airport, GA (PDK/KPDK), |
| Pine Mountain Airport, GA (PIM) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Probable Cause: The pilot’s inadvertent deactivation of the yaw damper in flight, which resulted in a prolonged side-slip condition that led to fuel starvation and the eventual total loss of engine power. Contributing to the accident was the pilot’s failure to attempt to restart the engine.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N536EM/history/20141005/1600Z/KPDK/KPIM
Location
Images:
(c) Keith Knowlton 5-10-2014
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 05-Oct-2014 20:23 | Geno | Added |
| 05-Oct-2014 20:36 | Geno | Updated [Operator, Source] |
| 06-Oct-2014 18:03 | harro | Updated [Aircraft type] |
| 06-Oct-2014 19:05 | Anon. | Updated [Aircraft type] |
| 07-Oct-2014 06:39 | RobertMB | Updated [Aircraft type, Narrative] |
| 05-Nov-2014 09:22 | Anon. | Updated [Photo, ] |
| 19-Jan-2016 20:33 | Anon. | Updated [Damage] |
| 19-Jun-2016 05:52 | Anon. | Updated [Source] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 31-Aug-2017 16:29 | Aerossurance | Updated [Time, Operator, Nature, Source, Damage, Narrative] |
| 31-Aug-2017 16:30 | Aerossurance | Updated [Source] |
| 30-Nov-2017 19:29 | ASN Update Bot | Updated [Time, Other fatalities, Departure airport, Destination airport, Source, Damage, Narrative] |
| 01-Feb-2022 16:50 | Captain Adam | Updated [Operator, Other fatalities, 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:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation