FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20LA159 · Pilatus PC12 47

23 Apr 2020 · Mesquite, TX, United States

Boutique Air Pilatus PC12 47 · Accident: loss of engine power (partial) en route

From Dallas Fort Worth International Airport (DFW) to Northwest Alabama Regional Airport (MSL)

Report a problem

Event

NTSB case
CEN20LA159
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 PC12 47

Aircraft type
Pilatus PC12
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
N477SS
Operator
Boutique Air
Onboard fatalities
Unknown
Route
From Dallas Fort Worth International Airport (DFW), Dallas, TXTo Northwest Alabama Regional Airport (MSL), Muscle Shoals, AL
Aircraft age
About 13 years (built 2007)
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
En route · climb to cruise
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
Loss of engine power (partial)
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff the pilot reported to the air traffic controller that he was losing engine power. The pilot then said he was going to divert to a nearby airport and accepted headings to the airport. The pilot then reported the loss of engine power had stabilized, so he wanted to return to his departure airfield. A few moments later the pilot reported that he was losing engine power again and he needed to go back to his diversion airport. The controller reported that another airport was at the pilot’s 11 o’clock position and about 3 miles. The pilot elected to divert to that airport. The airplane was at 4,500 ft and too close to the airport, so the pilot flew a 360° turn to set up for a left base. During the turn outbound, the engine lost all power, and the pilot was not able to reach the runway. The airplane impacted a field, short of the airport. The airplane’s wings separated in the accident and a small postcrash fire developed.

A review of the airplane’s maintenance records revealed maintenance was performed on the day of the accident flight to correct reported difficulty moving the Power Control Lever (PCL) into reverse position. The control cables were inspected from the pilot’s control quadrant to the engine, engine controls, and propeller governor. A static rigging check of the PCL was performed with no anomalies noted. Severe binding was observed on the beta control cable (propeller reversing cable). The cable assembly was removed from the engine, cleaned, reinstalled, and rigged in accordance with manufacturer guidance.

During a post-accident examination of the engine and propeller assembly, the beta control cable was found mis-rigged and the propeller blades were found in the feathered position. The beta valve plunger was extended beyond the chamfer face of the propeller governor, consistent with a position that would shut off oil flow from the governor oil pump to the constant speed unit (CSU). A wire could be inserted through both the forward and aft beta control cable clevis inspection holes that function as check points for proper thread engagement. The forward beta control cable clevis adjustment nut was rotated full aft. The swaging ball end on the forward end of the beta control cable was not properly secured between the clevis rod end and the push-pull control terminal and was free to rotate within the assembly.

Before takeoff, the beta valve was in an operational position that allowed oil flow to the CSU, resulting in normal propeller control. Vibration due to engine operation and beta valve return spring force most likely caused the improperly secured swaging ball to rotate (i.e. “unthread”) forward on the beta control cable. The resulting lengthening of the reversing cable assembly allowed the beta valve to stroke forward and shut off oil flow to the propeller CSU. Without propeller servo oil flow to maintain propeller control, the propeller faded to the high pitch/feather position due to normal leakage in the transfer bearing. The reported loss of power is consistent with a loss of thrust due to the beta control cable being mis-rigged during the most recent maintenance work.

Probable cause

The loss of engine power due to a mis-rigged beta control cable (propeller reversing cable), which resulted in a loss of thrust inflight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20LA159
Event ID
20200423X81031
Case number
CEN20LA159
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. 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: 5dc0da2b39cc0e40da25c2ba2b443e48bfe2905b2698bc0c73c6ac69f2de9388; retrieved 2026-09-16T11:30:31.673Z.