Accident Piper PA-32-300 Cherokee Six N2966X,
ASN logo
ASN Wikibase Occurrence # 176959
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Sunday 14 June 2015
Time:07:46
Type:Silhouette image of generic PA32 model; specific model in this crash may look slightly different    
Piper PA-32-300 Cherokee Six
Owner/operator:Limb-a-nator Llc
Registration: N2966X
MSN: 32-7940233
Year of manufacture:1979
Total airframe hrs:3956 hours
Engine model:Lycoming IO-540
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:Cuba Municipal Airport (KUBX), Cuba, MO -   United States of America
Phase: Approach
Nature:Private
Departure airport:Branson West, MO (FWB)
Destination airport:ST LOUIS, MO (1H0)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot was conducting a personal cross-country flight and had filed an instrument flight rules flight plan. The flight was en route to the destination airport, and the pilot was in radar and radio contact with air traffic control (ATC) personnel. While the airplane was in cruise flight at 5,000 ft mean sea level, the pilot checked in with an air traffic controller who alerted the pilot of “moderate to extreme precipitation” 50 miles ahead and about 30 miles in diameter. The pilot acknowledged the information and stated that he would maintain communications with ATC and that he had “a scope onboard.” About 30 minutes later, the pilot reported to the controller that he was in the middle of the precipitation and was not experiencing any bumps. He also stated that his weather scope was showing some returns right of his position. About 1 minute later, radar contact with the airplane was lost, and despite multiple attempts, the controller was unable to make radio contact with the pilot. One witness reported that the airplane emerged from the clouds and that one wing had separated from the airplane before impact. Another witness reported observing the airplane above the tree line with pieces of the airplane falling toward the ground as the airplane spun and descended until impact.
Postaccident examination of the engine and airframe revealed no preimpact mechanical malfunctions or anomalies that would have precluded normal operation. The wreckage distribution and signatures and the witnesses’ reports were consistent with an in-flight breakup. A review of the weather and radar data showed that, during the final moments of the flight, the airplane made a right, descending turn near an area of moderate-to-high thunderstorm activity, which can include extreme updrafts and downdrafts. Although the turn did not occur within a convective storm cell, it occurred in an area that would have been very dynamic and surrounded by hazardous weather conditions. This encounter with thunderstorm activity likely led to the pilot’s loss of airplane control and the exceedance of the airplane's design limits and its subsequent in-flight breakup. Further, based on the pilot’s communication with the air traffic controller, he was attempting to use onboard weather radar to maneuver through an area of storms that he should not have been flying through in the first place.

Probable Cause: The pilot's continued flight into thunderstorm activity, which resulted in his loss of airplane control, the exceedance of the airplane's design limits, and its subsequent in-flight breakup. Contributing to the accident was the pilot's reliance on onboard weather equipment to navigate through severe weather.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN15FA268
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=2966X

Location

Revision history:

Date/timeContributorUpdates
14-Jun-2015 15:57 Geno Added
14-Jun-2015 16:05 Geno Updated [Time, Aircraft type, Source, Damage, Narrative]
14-Jun-2015 22:54 Geno Updated [Aircraft type, Registration, Cn, Operator, Phase, Nature, Departure airport, Destination airport, Source, Narrative]
15-Apr-2016 17:11 Anon. Updated [Departure airport]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
01-Dec-2017 13:43 ASN Update Bot Updated [Cn, Operator, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org