ASN Wikibase Occurrence # 151247
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: | Saturday 15 December 2012 |
| Time: | 10:00 |
| Type: |  Piper PA-31T Cheyenne I |
| Owner/operator: | Private |
| Registration: | N93CN |
| MSN: | 31T-8004029 |
| Year of manufacture: | 1980 |
| Total airframe hrs: | 5725 hours |
| Engine model: | Pratt & Whitney PT6A |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | 19 miles SE of Ely, NV -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Mesa, AZ (FFZ) |
| Portland, OR (TTD) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The private pilot and passenger departed on the 875-nautical-mile cross-country flight and leveled off at a cruise altitude of 24,000 feet mean seal level, which, based on the radar data, was accomplished with the use of the autopilot. About 1 hour 40 minutes after departure, the pilot contacted air traffic control personnel to request that he would “like to leave frequency for a couple of minutes.” No further radio transmissions were made. About 20 seconds after the last transmission, the airplane banked to the right, continued in a spiral while rapidly descending, and subsequently broke apart. At no time during the flight did the pilot indicate that he was experiencing difficulty or request assistance. Just prior to departing from the flight path, the pilot made an entry of the engine parameters in a flight log, which appeared to be consistent with his other entries indicating the airplane was not experiencing any difficulties.
Portions of the wings, along with the horizontal stabilizers and elevators, separated during the breakup sequence. Analysis of the fracture surfaces, along with the debris field distribution and radar data, revealed that the rapid descent resulted in an exceedance of the design stress limits of the airplane and led to an in-flight structural failure. The airplane sustained extensive damage after ground impact, and examination of the engine components and surviving primary airframe components did not reveal any mechanical malfunctions or failures that would have precluded normal operation.
The airplane was flying on a flight path that the pilot was familiar with over largely unpopulated hilly terrain at the time of the upset. The clouds were well below his cruising altitude, giving the pilot reliable external visual cues should the airplane have experienced a failure of either the flight instruments or autopilot. Further, no turbulence was reported in the area.
The airplane was equipped with a supplemental oxygen system, which the pilot likely had his mask plugged into and available in the unstowed position behind his seat; the passenger’s mask was stowed under her seat.
The airplane’s autopilot could be disengaged by the pilot by depressing the appropriate mode switch, pushing the autopilot disengage switch on the control wheel, or turning off the autopilot switch on the control head. All autopilot servos were also equipped with a clutch mechanism that allowed the servo to be manually overridden by the pilot at any time.
It is likely that the reason the pilot requested to “leave the frequency” was to leave his seat and attend to something in the airplane. While leaving his seat, it is plausible he inadvertently disconnected the autopilot and was unable to recover by the time he realized the deviation had occurred.
Probable Cause: The pilot’s failure to regain airplane control following a sudden rapid descent during cruise flight, which resulted in an exceedance of the design stress limits of the aircraft and led to an in-flight structural failure.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=93CN
4. https://flightaware.com/live/flight/N93CN/history/20121215/1630Z/KFFZ/KTTD/tracklog
Location
Images:
Photo(s): NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 16-Dec-2012 01:16 | Dmitriy | Added |
| 16-Dec-2012 19:30 | Geno | Updated [Time, Source] |
| 18-Dec-2012 16:08 | Geno | Updated [Location, Source, Damage, Narrative] |
| 08-Jan-2013 11:35 | dorean m holzer | Updated [[Location, Source, Damage, Narrative]] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 07-Aug-2017 13:38 | TB | Updated [Aircraft type, Operator] |
| 18-Sep-2017 22:31 | Dr. John Smith | Updated [Time, Operator, Location, Departure airport, Destination airport, Source, Narrative] |
| 18-Sep-2017 22:33 | Dr. John Smith | Updated [Source] |
| 28-Nov-2017 14:02 | ASN Update Bot | Updated [Time, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 24-Feb-2020 21:15 | Captain Adam | Updated [Other fatalities, Location, Source, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation