Piper PA 34-200T N82806
3 August 2016 · Flagstaff, Arizona, United States · Fatal
Summary
On 3 August 2016 at about 04:22 local time, a Piper PA 34-200T registered N82806 was involved in an accident near Flagstaff, Arizona, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 04:22
- Classification
- Accident
- Location
- Flagstaff, Arizona, United States
- Nearest airport
- Flagstaff Pulliam (FLG)
- Coordinates
- 35.1064, -111.7242
- Aircraft
- Piper PA 34-200T
- Registration
- N82806
- Category
- Airplane
- Year built
- 1980
- Engines
- 2
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Flagstaff → Mesa
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Night
- NTSB number
- WPR16FA158
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
A departure flight path that consisted of several unexplained turns during the initial climbout, and terminated in a high-speed descent and ground impact. The reason(s) for the turns and descent could not be determined due to lack of definitive evidence.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The airline transport pilot regularly used his twin-engine airplane to conduct volunteer flights for a non-profit organization dedicated to transporting medical cargo. On the day of the accident, he departed his home airport about 0945, made a planned interim stop at one airport, and then flew to a second airport, where he waited for his next cargo pickup. The cargo was delivered to him, as scheduled, about 2100, and he departed shortly thereafter on a night visual flight rules (VFR) cross-country flight. The air traffic control tower was closed at the time of the pilot's departure. The airport was situated in semi-rural, mountainous terrain, and both the sun and the moon had set about 2 hours before takeoff. Ground-based tracking radar data indicated that the airplane departed to the southwest, turned west, then south, and then north before it descended rapidly and impacted trees and terrain about 2.5 minutes after takeoff. The first segment of the radar-derived trajectory was consistent with a normal takeoff and initial climb. About 1 minute after takeoff, some undetermined occurrence(s) or circumstance(s) interrupted the climb and resulted in the course deviations and the extreme descent. Examination of the accident site indicated that the airplane was in a banked attitude when it impacted the trees. The available evidence indicated that both engines were developing significant power at impact, and that the propellers were operating normally. No evidence of a bird strike or an in-flight fire was observed. With the exception that one of the two instrument air pressure pumps were inoperative, the investigation did not discover evidence of any pre-impact mechanical deficiencies with the airplane or its equipment. However, the wreckage was highly fragmented, which could have masked or destroyed such evidence. The artificial horizon and the directional gyro were two of the flight instruments that were driven by the air pressure pumps. Although the two air pressure pumps and associated valving were designed to provide automatic continued normal system operation in the event of a single air pressure pump failure, the severity of the damage precluded determination of the pre-accident functionality of the instrument air system. Therefore, it is possible that a failure of the valving system could have resulted in the loss of valid artificial horizon and directional gyro information, which in turn, due to the dark night and scarcity of ground lights, could have resulted in the accident. Damage also precluded testing of the autopilot system. However, the pilot typically hand-flew the airplane to cruise altitude before engaging the autopilot; therefore, the accident was likely not due to an autopilot malfunction. Although the departure airport automated weather observation reported 10 miles visibility with no clouds less than 10,000 ft above the airport, the heavy rain earlier in the day, combined with nighttime cooling and the lack of a temperature-dew point spread, suggested the potential for localized low altitude clouds or fog. Given the dark night and the lack of significant ground lighting, pilot disorientation for a variety of reasons could not be discounted. The most likely possible reasons included: - Distraction from some unknown event inside or outside the airplane - Malfunction or failure of one or more flight instruments - Inadvertent encounter with localized instrument meteorological conditions The medical investigation of the pilot was significantly limited by the degree of injury, and it could not be determined whether the pilot experienced an acute medical event during the flight. Due to the pilot's age, his reported pre-existing medical conditions, and the paucity of autopsy findings, physiological impairment or incapacitation of the pilot could not be eliminated as a possible reason for the accident. Because it has no direct psychoactive effects, it is unlikely that the pilot's use of metoprolol contributed to the accident. The absence of ethanol in the kidney tissue indicates that the identified ethanol in muscle tissue was from post-mortem sources, and therefore did not contribute to the accident. Although the pilot was the president of the organization for which he was flying, and that the organization published flight operations guidance intended to ensure a minimum level of operational safety, the pilot's history demonstrated repeated deviations from that guidance. One of those deviations concerned the number of pilots on board. On the accident flight, as well as on most of his other night missions for the organization, the pilot flew solo, even though the guidance recommended that night flights use two pilots. Although the investigation was unable to determine the specific reason for the accident, it is possible that a second pilot might have been able to assist in some way to prevent the accident.
Quoted verbatim from the NTSB record.
Other Piper PA-34 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 7 Dec 2016 | Piper PA 34 | Denton, Texas, United States | U S Aviation Group LLC | No injuries | - |
| 11 Oct 2016 | Piper PA 34-200 | East Hartford, Connecticut, United States | American Flight Academy | Fatal | 1 |
| 13 Aug 2016 | Piper PA 34 | Fort Lauderdale, Florida, United States | ELI Air Center Inc. | No injuries | - |
| 15 Oct 2016 | Piper PA 34 | Springfield, Ohio, United States | - | No injuries | - |
| 7 Dec 2016 | Piper PA-34-200T | Alsace, France | - | Fatal | 1 |
| 25 Nov 2017 | Piper PA 34-220T | Ebensburg, Pennsylvania, United States | - | Serious injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 24 Nov 2016 | Cessna 182A | Safford, Arizona, United States | - | No injuries | - |
| 6 Apr 2016 | Bell 206 | Supai, Arizona, United States | Airwest Helicopters LLC. | Minor injuries | - |
| 6 Oct 2016 | Cessna 172 | Phoenix, Arizona, United States | UND Aerospace Foundation | No injuries | - |
| 24 Aug 2016 | Airbus AS350 | Peach Springs, Arizona, United States | Papillon Airways Inc. | No injuries | - |
| 25 Jan 2016 | Enstrom 280 | Phoenix, Arizona, United States | - | Minor injuries | - |
| 12 Oct 2016 | Rockwell 112A | Phoenix, Arizona, United States | SHO Co Kids LLC | Serious injuries | - |