Mesa - Portland
Flight / Schedule
Mesa - Portland
Aircraft
Piper PA-31 CheyenneRegistration
N93CN
MSN
31-8004029
Year of Manufacture
1980
Operator
Nothman Jerry Company TrusteeDate
December 15, 2012 at 10:00 AM
Type
CRASHFlight Type
Private
Flight Phase
Flight
Crash Site
Mountains
Crash Location
Ely Nevada
Region
North America • United States of America
Coordinates
39.2481°, -114.8917°
Crash Cause
Human factor
Narrative Report
On December 15, 2012 at 10:00 AM, Mesa - Portland experienced a crash involving Piper PA-31 Cheyenne, operated by Nothman Jerry Company Trustee, with the event recorded near Ely Nevada.
The flight was categorized as private and the reported phase was flight at a mountains crash site.
2 people were known to be on board, 2 fatalities were recorded, 0 survivors were identified or estimated. This corresponds to an estimated fatality rate of 100.0%.
Crew on board: 1, crew fatalities: 1, passengers on board: 1, passenger fatalities: 1, other fatalities: 0.
The listed crash cause is human factor. 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.
Aircraft reference details include registration N93CN, MSN 31-8004029, year of manufacture 1980.
Geospatial coordinates for this crash are approximately 39.2481°, -114.8917°.
Fatalities
Total
2
Crew
1
Passengers
1
Other
0
Crash Summary
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.
Cause: Human factor
Occupants & Outcome
Crew On Board
1
Passengers On Board
1
Estimated Survivors
0
Fatality Rate
100.0%
Known people on board: 2
Operational Details
Schedule / Flight
Mesa - Portland
Operator
Nothman Jerry Company TrusteeFlight Type
Private
Flight Phase
Flight
Crash Site
Mountains
Region / Country
North America • United States of America
