NTSB CAROL · Event
Event ERA18LA031
Aircraft involved
Probable cause & findings
A partial loss of engine power for reasons that could not be determined based on the available information.
Factual narrative
On November 25, 2017, about 1315 eastern standard time, a Piper PA-46-500TP, N863RB, was substantially damaged when it experienced a loss of engine power during the initial climb from St. Pete/Clearwater International Airport (PIE), Clearwater, Florida. The airline transport pilot sustained minor injuries. The airplane was registered to and operated by a corporation as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident, and an instrument flight rules flight plan was filed for the flight that was destined for Pensacola International Airport (PNS), Pensacola, Florida.According to the pilot, he performed a preflight inspection of the airplane and engine runup with no anomalies noted. The takeoff roll and lift off from runway 36 were "normal;" however, when he initiated a landing gear retraction, the engine torque decreased to 300-400 [ft-lbs], and rpm remained at 2,000. The torque surged back toward full power; however, he could not recall how high. The pilot initiated a 20° right turn in anticipation to return to the runway, and throughout the engine continued to surge. The pilot attempted to return to the runway instead of landing in the water; however, the left wing of the airplane struck the ground and it came to rest near runway 18. Initial examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the left wing was impact separated. The right wing remained attached to the fuselage. The fuselage was partially separated at the cabin section of the airframe. The engine remained attached to the airframe and the propeller remained attached to the engine. According to the pilot, he held an airline transport pilot certificate with ratings for airplane multiengine land and instrument airplane. In addition, he held a flight instructor certificate with a rating for airplane single-engine. His most recent FAA first-class medical certificate was issued on October 11, 2017. He reported 15,000 hours of total flight time, of which, 25 hours were in the same make and model as the accident airplane. In addition, in the previous 90 days, he had accumulated 35 hours of flight time. According to FAA airworthiness records, the airplane was manufactured in 2005. It was powered by a Pratt & Whitney PT6A-42A, 850-shaft-horsepower engine equipped with a Hartzell constant-speed propeller. According to airplane maintenance logbooks, the most recent annual inspection was completed on April 1, 2017, at a total time of 1,341.0 hours and 912 cycles. Examination of the airframe revealed that the there were no blockages noted with the fuel system. The both electric fuel pumps were tested, and no anomalies were noted. In addition, fuel similar to Jet A was noted in the right-wing during recovery of the airplane. The left fuel tank was breached. The engine and propeller were removed from the airplane for further examination. Examination of the propeller revealed that all four propeller blades were bent aft, opposite the direction of rotation, and twisted towards a low pitch blade angle. Two blades fractured approximately 8 inches outboard of the blade shank and separated from the propeller assembly during the impact sequence. In addition, chordwise scratching and leading-edge gouging was noted. When the propeller was disassembled, all of the blades were not in a feathered position and the pitch change components were impact damaged. The beta ring was removed, and no anomalies were noted. There were no anomalies noted with the propeller that would have precluded normal operation prior to the accident. The engine was sent to the manufacturer for further examination and teardown. The first stage power turbine exhibited rotational scoring. The compressor turbine rotated with no binding or scraping. The disk and blade fir tree faces of the compressor turbine exhibited rotational scoring. The axial compressors were rotated without anomaly. They were all removed and examined. The turbine blades exhibited a small amount of rotational scoring. The two bleed valves were removed and could be actuated by hand. The o-rings and gaskets were examined with no cracking noted. There were no anomalies noted with the engine that would have precluded normal operation prior to the accident. The fuel pump, fuel control, fuel filter, torque controller, and propeller governor were removed and sent to Pratt & Whitney Canada for further examination . Each component was tested an no anomalies were noted. The data acquisition unit (DAU) was removed from the airframe and sent to the NTSB Recorders Laboratory for data download. The DAU was an engine instrument display system that also included dual instrument panel mounted displays and various engine and fuel tank sensors. It recorded engine condition trim monitoring data, exceedances, and fault data on two channels; both channels of the DAU were downloaded. There were no engine condition trend monitoring data nor exceedances recorded on the day of the accident. Two faults were recorded on the day of the accident which noted "oil press AtoD reversion failure" and "Torque AtoD reversion failure.; however, the faults could not be correlated to the accident. The pilot performed a preflight inspection of the turboprop airplane and an engine run-up with no anomalies noted. The takeoff roll and lift off from the runway were normal; however, when the pilot initiated a landing gear retraction, the engine torque decreased, but the rpm did not change. The torque then surged back to full power and continued to surge as the pilot attempted to return to the runway. The left wing of the airplane struck the ground, and the airplane came to rest in the grass on the side of the runway. Examination of the engine, engine accessories, and propeller revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation before the accident. The reason for the partial loss of engine power could not be determined based on the available information. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2017_ERA18LA031.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗