ERA16LA082 · Pilatus Aircraft Ltd PC-12 47E
PlaneSense Pilatus Aircraft Ltd PC-12 47E · Accident: flight instrument malfunction/failure during initial climb
From Savannah Hilton Head International Airport (SAV) to Blue Grass Airport (LEX)
Event
- NTSB case
- ERA16LA082
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Pilatus Aircraft Ltd PC-12 47E
- Aircraft type
- Pilatus PC-12
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N978AF
- Operator
- PlaneSense
- Onboard fatalities
- Unknown
- Route
- From Savannah Hilton Head International Airport (SAV), Savannah, GATo Blue Grass Airport (LEX), Lexington, KY
- Aircraft age
- About 8 years (built 2008)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Flight instrument malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The two airline transport pilots reported that takeoff acceleration in the single-engine, turboprop-equipped airplane was normal; however, shortly after rotation and during initial climb, a crew alerting system (CAS) warning activated. The CAS indicated excessively high engine torque. According to the copilot, who was the pilot flying, when he looked down, he saw a torque value of 5.3 pounds per square inch (psi). The pilot, who was monitoring from the left seat, reported that he saw a "low torque CAS message." He added that the copilot told him to "declare an emergency and run the checklist." With about 2,700 ft of runway remaining and the airplane at 200 ft mean sea level, the copilot chose to land immediately and executed a 90° left descending turn to land in grass. The airplane touched down and rolled about 600 ft before impacting a ditch, which resulted in substantial damage to the airplane and a postimpact fire.
Data retrieved from the airplane's modular avionics unit revealed that all engine indications and parameters were normal throughout the takeoff roll and rotation; however, during the initial climb, the torque indication increased rapidly from about 45.0 to 71.0 psi; fault history data confirmed that the engine torque caution and warning were displayed during this time and that the other engine parameters remained normal. Four seconds later, the torque decreased to 47.3 psi, which coincided with a simultaneous drop in other engine parameters, consistent with the copilot reducing engine power following the CAS warning. The CAS was not equipped to display warnings for low torque values; a CAS warning or caution would only activate if an exceedance of torque tolerances occurred. Therefore, although both pilots reported seeing a low torque indication, given that the CAS is not equipped to display warnings for low values and that the data did not indicate a low torque condition occurred during the flight, it is likely that the pilots misinterpreted the CAS warning.
Examination of the engine and torque indicating system revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation, and the cause of the high torque indication could not be determined. Given that no anomalies were found with the engine and torque indicating system during postaccident examination and that all other engine parameters remained normal throughout the flight, it is likely that the high torque indication was erroneous.
The Pilot's Operating Handbook for the airplane stated that, following a CAS warning or caution for engine torque, engine power should be reduced if the torque value was above 44.3 psi. It also stated that, if the CAS warning or caution remained after the engine power was reduced, then the airplane should be landed as soon as possible using minimum power. Despite the pilots' misinterpretation of the torque indication, they should have followed the POH guidance on how to respond to an engine torque indication. However, the pilots chose to declare an emergency and immediately land after seeing the CAS warning during a critical phase of flight rather than troubleshooting the CAS message by reducing engine power to determine whether the CAS message could be resolved and despite onboard data indicating that the reduction in power resulted in the torque value returning to normal. The pilots reacted by reducing engine power substantially, which left them with no option but to conduct an off-runway emergency landing.
Probable cause
The pilots’ failure to follow proper procedures in response to a crew alerting system warning for high engine torque values, which necessitated an off-runway emergency landing during which the airplane sustained substantial damage due to postimpact fire. Contributing to the accident was the erroneous engine torque indication for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16LA082
- Event ID
- 20160106X32926
- Case number
- ERA16LA082
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e7573777c92d501cab663894b899d5e974715a6542b8c9920d4581f0d89c0b89; retrieved 2026-09-16T03:04:34.401Z.