# NTSB CEN13LA195: New Piper PA-46-500TP, N665KC, Brenham, TX, March 13, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: March 13, 2013, 10:40 local (15:40 UTC) - Place: Brenham, TX - Coordinates: 30.219722, -96.374443 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=30.2197&lon=-96.3744&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report July 30, 2014 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA Flight Standards, Pratt & Whitney Canada - NTSB case key (mKey): 86431 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13LA195 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86431/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86431 - Page: https://openairdocs.org/ntsb/CEN13LA195 ## Probable cause A lack of available engine power during an attempted go-around for reasons that could not be determined because the postaccident engine examinations did not reveal any anomalies consistent with an inability to produce rated power. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342) (defining event); cases with it: [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Approach: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The flight instructor reported that the purpose of the flight was to practice engine failure procedures and power-off approaches. The accident occurred during the third approach of the flight as he was demonstrating the power-off approach technique. He noted that he had climbed to 3,500 feet, reduced engine power, and began a spiral over the airport to enter the left traffic pattern to the runway. During final approach, the airplane started descending at a higher rate. The flight instructor stated that he attempted to increase engine power but that he did not "hear or feel an indication of [engine] power increasing." The airplane subsequently impacted terrain about 165 feet short of the runway. Flight and engine data recovered from the avionics were consistent with a power-off approach. The engine gas generator speed, torque, interturbine temperature, and oil pressure parameters were stable at the end of the recorded data and were consistent to the same parameters recorded during the initial power-off approach. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with an inability to obtain engine power. Functional testing and subsequent teardown examinations of the fuel pump, fuel control unit, and fuel oil heat exchanger also did not reveal any anomalies that would have precluded normal operation. Variations from standard production component settings were consistent with field adjustments. ## Factual narrative On March 13, 2013, at 1040 central daylight time, a New Piper Aircraft model PA-46-500TP airplane, N665KC, was substantially damaged when the airplane impacted short of runway 34 (6,002 feet by 75 feet, asphalt) at the Brenham Municipal Airport (11R), Brenham, Texas. The pilot, flight instructor, and passenger were not injured. The airplane sustained substantial damage to the fuselage and wings. The airplane was registered to and operated by N665KC, LLC, under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The flight originated from the West Houston Airport (IWS), Houston, Texas at 1000. The flight instructor reported that the purpose of the flight was to practice engine failure procedures and power-off approaches. The accident occurred during the third approach of the flight. The initial power-off approach necessitated a go-around and the second approach was terminated in a full-stop landing. On the third approach the flight instructor was demonstrating power-off approach technique. He noted that he had climbed to 3,500 feet, reduced engine power, and began a spiral over the airport for left traffic to runway 34. During the final approach, the airplane started descending at a higher rate. The flight instructor stated that he attempted to increase engine power, but he did not "hear or feel an indication of [engine] power increasing." The airplane subsequently impacted the terrain short of the runway. Ground marks were consistent with the airplane impacting about 165 feet short of the runway. The airplane ultimately came to rest on the runway pavement oriented on south heading. Both main landing gears separated during the accident sequence. The fuselage remained intact; however, the lower fuselage skin exhibited scraping damage aft of the passenger door. Both the left and right wings exhibited damage consistent with ground impact. Flight and engine data were recovered from the avionics units installed in the airplane. The flight data indicated that after the initial takeoff, the airplane climbed to approximately 6,000 feet pressure altitude. About 1015, a descent began that continued uninterrupted until the go-around. About 1019, the flight data indicated initiation of a climb to about 3,200 feet pressure altitude. A second descent was initiated about 1025, which terminated about 1029. Airspeed and altitude data during that timeframe were consistent with a full stop landing. The flight data indicated that the final, accident takeoff was initiated about 1033. The airplane climbed to approximately 3,200 feet pressure altitude and reached a maximum airspeed of about 160 knots. At 1037, immediately after reaching an approximate pressure altitude of 3,300 feet, a descent was initiated. During the descent, the airspeed varied between about 100 knots and 120 knots; the rate of descent varied between about 125 feet perminute (fpm) and 250 fpm. About 1040:10 (hhmm:ss), the flight data noted an abrupt change in heading from about 350 degrees to 170 degrees which was consistent with ground impact. Recorded airspeed data decreased from about 90 knots to zero during that time. Recorded engine data indicated a reduction in propeller speed beginning about 1039:00, from about 2,000 rpm to 1,700 rpm. During this timeframe, the engine torque and gas generator speeds decreased from about 150 foot-pounds to about 30 foot-pounds and from about 80 percent to about 65 percent, respectively. The profile of this reduction appeared similar to the propeller speed profile that began about 1015, apparently in conjunction with the initial simulated power-off approach. The gas generator speed, torque, inter-turbine temperature, and oil pressure parameters were stable at the end of the recorded data. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with an inability to obtain engine power. The propeller assembly and engine cowling appeared intact with no observed propeller blade damage. The engine housing, installed components, fuel and pneumatic lines appeared intact with no observed discrepancies. The engine rotated freely. A borescope examination did not reveal any evidence of internal blade damage. Engine control continuity was confirmed. The power lever reverse lockout was functional at the time of the examination. Normal operation of the electric fuel boost pump was confirmed. The fuel bowl, fuel lines, and fuel filter were unremarkable. Recovered fuel appeared clean and free of sediment or contaminants. Functional testing and subsequent teardown examinations of the fuel pump, fuel control unit, and fuel oil heat exchanger did not reveal any anomalies. Variations from standard production component settings were consistent with field adjustments. At the time of the accident, the airplane had accumulated 734.7 hours total time. A review of the maintenance logbooks revealed that the most recent annual inspection was completed on January 30, 2013, at 725.3 hours total airframe time. At that time, the engine had accumulated 725.3 hours since new, with 583 cycles. An engine borescope inspection was completed on February 12, 2013, at 726.0 hours engine time, with no anomalies noted. The Pilot's Operating Handbook (POH) noted that in the case of an engine failure in-flight an airspeed of 108 knots should be maintained, with the power lever at idle, the condition lever at cut-off, and the propeller feathered. Regarding a maximum range descent after an engine failure, the POH denoted an airspeed of 108 knots, with landing and wing flaps retracted. The handbook noted that if the landing gear and/or wing flaps are extended, glide distance will be "severely" reduced. A power-off landing should be accomplished from the best glide airspeed of 108 knots. Landing gear and wing flaps should be extended once committed to landing. The POH specifiedthat a "spiral pattern" be established and, if altitude was available, to maintain 108 knots with flaps extended 10 degrees in the traffic pattern. The airplane was not equipped with, nor was it required to be equipped with, a cockpit voice or flight data recorder. In addition, the parameters that were recorded by the cockpit avionics did not included power or condition lever positions. As a result, the investigation was unable to confirm or exclude any movement of the power lever in an attempt to increase engine power before impact. ## Aircraft - Registration: N665KC (not matched to a registry record) - Reported make and model: NEW PIPER AIRCRAFT INC PA-46-500TP - Category: Airplane - Serial number: 4697265 - Airframe hours: 725 - Engines: P&W CANADA PT6A-42A 850 horsepower turbo prop - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: N665kc LLC - Registered owner: N665kc LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 30, 2013, 9 hours before - Departed: IWS, Houston, TX - Destination: 11R, Brenham, TX - Airport: 11R, Brenham Municipal, runway 34, 6,003 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review June 13, 2012; seat: left; flight hours: 12,862 total, 750 in this make and model, 12,413 as pilot in command, 302 in the last 90 days, 103 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 80° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 32 °F - Altimeter: 30.45 inHg - Observed at: 11R ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130313009009A](https://openairdocs.org/incident/20130313009009A), Mar 13, 2013: New Piper Aircraft Inc PA-46-500TP, Brenham, TX, Substantial damage. On approach (without flaps selected) to runway 34 aircraft impacted surface approximately 165 feet prior to runway. Aircraft bounced and then impacted at a… ## Docket (8 files) The files NTSB released with the investigation on July 7, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86431. 7.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 415 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413997&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Primary Flight Display/Multi-Function Display Data Plots (item 2, .PDF, 490 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413998&FileExtension=.PDF&FileName=Primary%20Flight%20Display%2FMulti-Function%20Display%20Data%20Plots-Master.PDF - Airframe Maintenance Logbook (item 3, .PDF, 3.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40413999&FileExtension=.PDF&FileName=Airframe%20Maintenance%20Logbook-Redacted.PDF - Engine Maintenance Logbook (item 4, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414000&FileExtension=.PDF&FileName=Engine%20Maintenance%20Logbook-Redacted.PDF - Propeller Maintenance Logbook (item 5, .PDF, 34 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414001&FileExtension=.PDF&FileName=Propeller%20Maintenance%20Logbook-Redacted.PDF - Airworthiness Directive Log (item 6, .PDF, 406 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414002&FileExtension=.PDF&FileName=Airworthiness%20Directive%20Log-Redacted.PDF - Pilot Operating Handbook -- Excerpts (item 7, .PDF, 476 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414003&FileExtension=.PDF&FileName=Pilot%20Operating%20Handbook%20--%20Excerpts-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 8, .PDF, 372 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414004&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.