FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA385 · Pilatus Aircraft Ltd PC-12/47

7 Jun 2012 · Lake Wales, FL, United States

Roadside Ventures Pilatus Aircraft Ltd PC-12/47 · Accident: loss of control in flight en route

From Treasure Coast International Airport (FPR) to Freeman Field (3JC)

Report a problem

Event

NTSB case
ERA12FA385
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
6 · 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
Instrument Meteorological Cond

Pilatus Aircraft Ltd PC-12/47

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
N950KA
Onboard fatalities
Unknown
Route
From Treasure Coast International Airport (FPR), Fort Pierce, FLTo Freeman Field (3JC), Junction City, KS
Aircraft age
About 6 years (built 2006)
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 control in flight
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

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Personnel issues › Action/decision

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

NTSB narrative

The instrument-rated pilot activated the autopilot shortly after takeoff and proceeded in a west-northwesterly direction while climbing to the assigned altitude of flight level (FL) 260. Light-to-moderate icing conditions were forecast for the area; the forecast conditions were well within the airplane's capability, and the pilot of a nearby airplane reported only encountering light rime ice at the top of FL260. About 26 minutes 35 seconds after takeoff, the airplane's central advisory and warning system (CAWS) recorded activation of Pusher Ice Mode at FL247, consistent with pilot's activation of the propeller de-ice and inertial separator; the de-ice boots were not selected. Less than a minute after the activation of Pusher Ice Mode, an air traffic controller cleared the flight to deviate right of course due to adverse weather well ahead of the airplane. The airplane then turned right while on autopilot in instrument meteorological conditions (IMC) at FL251; about 4 seconds into the turn, with the airplane indicating about 109 knots indicated airspeed and in a right bank of less than 25 degrees, the autopilot disconnected for undetermined reasons. The pilot allowed the bank angle to increase, and about 13 seconds after the autopilot disconnected, and with the airplane descending in a right bank of about 50 degrees, the pilot began a test of the autopilot system, which subsequently passed. Recovered data and subsequent analysis indicate that the pilot allowed the bank angle to increase to a minimum of 75 degrees while descending; the maximum airspeed reached 338 knots. During the right descending turn, while about 15,511 feet and 338 knots (about 175 knots above maximum operating maneuvering speed), the pilot likely applied either abrupt or full aft elevator control input, resulting in overstress fracture of both wings in a positive direction. The separated section of right wing impacted and breached the fuselage, causing one passenger to be ejected from the airplane. Following the in-flight break-up, the airplane descended uncontrolled into an open field.

Examination of the separated structural components revealed no evidence of pre-existing cracks on any of the fracture surfaces. Postaccident examination of the primary flight controls and engine revealed no evidence of preimpact failure or malfunction. The flaps were found in the retracted position, and the landing gear was extended; it is likely that the pilot extended the landing gear during the descent. The horizontal stabilizer trim actuator was positioned in the green arc takeoff range, the impact-damaged aileron trim actuator was in the left-wing-nearly-full-down position, and the rudder trim actuator was full nose right. The as-found positions of the aileron, rudder trim, and landing gear were not the expected positions for cruise climb. Examination of the relays, trim switch, and rudder trim circuit revealed no evidence of preimpact failure or malfunction, and examination of the aileron trim relays and aileron trim circuit revealed no evidence of preimpact failure or malfunction; therefore, the reason for the as-found positions of the rudder and aileron trim could not be determined. Impact-related discrepancies with the autopilot flight computer precluded functional testing. The trim adapter passed all acceptance tests with the exception of the aural alert output, which would not have affected its proper operation. The CAWS log entries indicated no airframe or engine systems warnings or cautions before the airplane departed from controlled flight. A radar performance study indicated that the airplane did not enter an aerodynamic stall, and according to the CAWS log entries, there was no record that the stick pusher activated before the departure from controlled flight.

Before purchasing the airplane about 5 weeks earlier, the pilot had not logged any time as pilot-in-command in a turbopropeller-equipped airplane and had not logged any actual instrument flight time in the previous 7 years 4 months. Additionally, his last logged simulated instrument before he purchased the airplane occurred 4 years 7 months earlier. Subsequent to the airplane purchase, he attended ground and simulator-based training that included extra flight sessions in the accident airplane, likely due to his inexperience. The training culminated with the pilot receiving his instrument proficiency check, flight review, and high-altitude endorsements; after the training, he subsequently logged about 14 hours as pilot-in-command of the accident airplane. Although the pilot likely met the minimum qualification standards to act as pilot-in-command by federal aviation regulations, his lack of experience in the make and model airplane was evidenced by the fact that he did not maintain control of the airplane after the autopilot disengaged. The airplane was operating in instrument conditions, but there was only light rime ice reported and no convective activity nearby; the pilot should have been able to control the airplane after the autopilot disengaged in such conditions. Further, his lack of experience was evident in his test of the autopilot system immediately following the airplane's departure from controlled flight rather than rolling the airplane to a wings-level position, regaining altitude; only after establishing coordinated flight should he have attempted to test the autopilot system.

Probable cause

The failure of the pilot to maintain control of the airplane while climbing to cruise altitude in instrument meteorological conditions (IMC) following disconnect of the autopilot. The reason for the autopilot disconnect could not be determined during postaccident testing. Contributing to the accident was the pilot's lack of experience in high-performance, turbo-propeller airplanes and in IMC.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA385
Event ID
20120607X54234
Case number
ERA12FA385
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: e785e1ba042d1597a86fe1f912c37a4a73299995fbbf712ac5b3d4b9665e32a4; retrieved 2026-09-13T22:25:48.780Z.