Crash of a Piper PA-31-350 Navajo Chieftain in Durant

Date & Time: Aug 21, 2023 at 1048 LT
Operator:
Registration:
N3589X
Survivors:
Yes
Schedule:
Tulsa - Tulsa
MSN:
31-8052138
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot, sole on board, departed Tulsa-Richard Lloyd Jones Jr. (Riverside) Airport in the morning on an on-demand special mission. After a pass over Sand Springs, west of Tulsa, the airplane continued to the south then the pilot completed three circuits over McAlester before continuing to the southwest. In unclear circumstances, the airplane caught fire in flight and the pilot diverted to Durant-Eaker Field. After landing on runway 17, the pilot stopped the airplane and was able to evacuate without injuries. The airplane was totally destroyed by fire.

Crash of a Piper PA-31-350 Navajo Chieftain in Hillcrest

Date & Time: Apr 7, 2023 at 0605 LT
Operator:
Registration:
VH-HJE
Flight Type:
Survivors:
Yes
Schedule:
Bankstown – Brisbane
MSN:
31-7852074
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1473
Captain / Total hours on type:
204.00
Circumstances:
On 7 April 2023, the pilot of a Piper Aircraft Corporation PA-31-350 Chieftain (PA-31), registered VH-HJE and operated by Air Link, was conducting a freight charter flight from Archerfield, Queensland. The planned flight included one intermediate stop at Bankstown, New South Wales before returning to Archerfield, and was conducted under the instrument flight rules at night. The aircraft departed Archerfield at about 0024 local time and during the first leg to Bankstown, the pilot reported an intermittent fault with the autopilot, producing uncommanded pitch changes and associated rates of climb and descent of around 1,000 ft/min. As a result, much of the first leg was flown by hand. After landing at Bankstown at about 0248, a defect entry was made on the maintenance release; however, the pilot was confident that they would be able to hand fly the aircraft for the return leg and elected to continue with the planned flight. The aircraft was refueled to its maximum capacity for the return leg after which a small quantity of water was detected in the samples taken from both main fuel tanks. Additional fuel drains were conducted until the fuel sample was free of water. The manifested freight for the return leg was considered a light load and the aircraft was within weight and balance limitations. After taking off at 0351, the pilot climbed to the flight planned altitude of 9,000 ft. Once established in cruise, the pilot changed the left and right fuel selectors from the respective main tank to the auxiliary tank. The pilot advised that, during cruise, they engaged the autopilot and the uncommanded pitch events continued. Consequently, the pilot did not use the autopilot for part of the flight. Approaching top of descent, the pilot recalled conducting their normal flow checks by memory before referring to the checklist. During this time, the pilot completed a number of other tasks not related to the fuel system, such as changing the radio frequency, checking the weather at the destination and briefing themselves on the expected arrival into Archerfield. Shortly after, the pilot remembered changing from the auxiliary fuel tanks back to the main fuel tanks and using the fuel quantity gauges to confirm tank selection. The pilot calculated that 11 minutes of fuel remained in the auxiliary tanks (with an estimated 177 L in each main tank). Around eight minutes after commencing descent and 28 NM (52 km) south of Archerfield (at 0552), the pilot observed the right ‘low fuel flow’ warning light (or ‘low fuel pressure’) illuminate on the annunciator panel. This was followed soon after by a slight reduction in noise from the right engine. As the aircraft descended through approximately 4,700 ft, the ADS-B data showed a moderate deceleration with a gradual deviation right of track. While the power loss produced a minor yaw to the right, the pilot recalled that only a small amount of rudder input was required to counter the adverse yaw once the autopilot was disconnected. Without any sign of rough running or engine surging, they advised that had they not seen the annunciator light, they would not have thought there was a problem. Over the next few minutes, the pilot attempted to troubleshoot and diagnose the problem with the right engine. Immediately following power loss, the pilot reported they:
• switched on both emergency fuel boost pumps
• advanced both mixture levers to RICH
• cycled the throttle to full throttle and then returned it to its previous setting without fully closing the throttle
• moved the right fuel selector from main tank to auxiliary
• disconnected the autopilot and retrimmed the aircraft. This did not alter the abnormal operation of the right engine, and the pilot conducted the engine roughness checklist from the aircraft pilot’s operating handbook noting the following:
• oil temperature, oil pressure, and cylinder head temperature indicated normally
• manifold absolute pressure (MAP) had decreased from 31 in Hg to 27 inHg
• exhaust gas temperature (EGT) indicated in the green range
• fuel flow indicated zero.
With no indication of mechanical failure, the pilot advised they could not rule out the possibility of fuel contamination and chose not to reselect the main tank for the remainder of the flight. After considering the aircraft’s performance, handling characteristics and engine instrument indications, the pilot assessed that the right engine, while not able to generate normal power, was still producing some power and that this would assist in reaching Archerfield. Based on the partial power loss diagnosis, the pilot decided not to shut down and secure the engine which would have included feathering the propeller. At 0556, at about 20 NM south of Archerfield at approximately 3,300 ft, the pilot advised air traffic control (ATC) that they had experienced an engine malfunction and requested to maintain altitude. With maximum power being set on the fully operating left engine, the aircraft was unable to maintain height and was descending at about 100 ft/min. Even though the aircraft was unable to maintain height, the pilot calculated that the aircraft should have been able to make it to Archerfield and did not declare an emergency at that time. At 0602, about 12 minutes after the power loss on the right engine, the left engine began to run rough and the pilot observed the left low fuel flow warning light illuminate on the annunciator panel. This was followed by severe rough running and surging from the left engine which produced a series of pronounced yawing movements. The pilot did not run through the checklist a second time for the left engine, reporting that they completed the remaining item on the checklist for the left engine by switching the left engine’s fuel supply to the auxiliary tank. The pilot once again elected not to change tank selections back to mains. With both engines malfunctioning and both propellers unfeathered, the rate of descent increased to about 1,500 ft/min. The pilot advised that following the second power loss, it was clear that the aircraft would not be able to make it to Archerfield and their attention shifted from troubleshooting and performance management to finding somewhere to conduct a forced landing. ADS-B data showed the aircraft was at about 1,600 ft when the left engine malfunctioned. The pilot stated that they aimed to stay above the minimum control speed, which for VH-HJE was 72 kt. The aircraft was manoeuvred during the brief search), during which time the ground speed fluctuated from 110 kt to a low of 75 kt. It was calculated that in the prevailing wind, this would have provided an approximate indicated airspeed of 71 kt; equal to the aircraft’s clean configuration stall speed. The pilot declared an emergency and advised ATC that they were unable to make Archerfield Airport and would be conducting an off-airport forced landing. With very limited suitable landing areas available, the pilot elected to leave the flaps and gear retracted to minimize drag to ensure they would be able to make the selected landing area. At about 0605, the aircraft touched down in a rail corridor beside the railway line, and the aircraft’s left wing struck a wire fence. The aircraft hit several trees, sustaining substantial damage to the fuselage and wings. The pilot received only minor injuries in the accident and was able to exit through the rear door of the aircraft.
Probable cause:
The following contributing factors were identified:
- It is likely that the pilot did not action the checklist items relating to the selection of main fuel tanks for descent. The fuel supply in the auxiliary tanks was subsequently consumed resulting in fuel starvation and loss of power from the right then left engine.
- Following the loss of power to the right engine, the pilot misinterpreted the engine instrument indications as a partial power loss and carried out the rough running checklist but did not select the main tanks that contained substantial fuel to restore engine power, or feather the propeller. This reduced the available performance resulting in the aircraft being unable to maintain altitude.
- When the left engine started to surge and run rough, the pilot did not switch to the main tank that contained substantial fuel, necessitating an off‑airport forced landing.
- It is likely that the pilot was experiencing a level of fatigue shown to have an effect on performance.
- As the pilot was maneuvering for the forced landing there was a significant reduction of airspeed. This reduced the margin over the stall speed and increased the risk of loss of control.
- Operator guidance material provided different fuel flow figures in the fuel policy and flight crew operating manual for the PA-31 aircraft type.
- The operator’s fuel monitoring practices did not detect higher fuel burns than what was specified in fuel planning data.
- The forced landing site selected minimized the risk of damage and injury to those on the ground and the controlled touchdown maximized the chances of survivability.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Middlefield

Date & Time: Jan 18, 2023 at 0903 LT
Registration:
N101MA
Survivors:
Yes
Schedule:
Youngstown – Detroit – Minneapolis
MSN:
31-7752186
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9275
Captain / Total hours on type:
750.00
Aircraft flight hours:
17154
Circumstances:
While enroute in instrument meteorological (IMC) conditions, the pilot of the twin-engine, piston-powered airplane declared an emergency following a loss of power to the right engine. The pilot secured the engine and was provided vectors by air traffic control for an instrument approach procedure at the nearest airport, which he successfully completed. The pilot reported that he flew the approach and landing with the wing flaps retracted and visually acquired the runway about 500 ft above the ground. The airplane touched down on the first third of the runway at 120 knots. The pilot knew he would not be able to stop the airplane on the 3,500-ft long runway but committed to the landing rather than risking a single-engine go-around in IMC. After landing, the airplane continued beyond the departure end of the runway and impacted a berm, collapsing the landing gear and resulting in substantial damage to the airplane. Examination of the engine revealed catastrophic damage consistent with detonation and oil starvation. The damage to the No. 5 cylinder was consistent with a subsequent over pressurization of the crankcase, which likely expelled the crankshaft nose seal and the oil supply. Detonation of the cylinder(s) can create excessive crankcase pressures capable of expelling the crankshaft nose seal. The crankshaft nose seal displacement likely created a rapid loss of oil and the resulting oil starvation of the engine. The fractured connecting rod and high-temperature signatures were consistent with oil starvation. No source or anomaly that would result in engine detonation was identified. According to the Pilot’s Operating Handbook (POH) for the accident airplane, during a single engine inoperative approach, the pilot should maintain an airspeed of 116 kts indicated (KIAS) or above until landing is assured. Once landing is assured, the pilot should extend the gear and flaps, slowly retard the power on the operative engine, and land normally. The airplane’s best single-engine rate of climb speed (blue line) was 106 KIAS, and its minimum controllable airspeed with one engine inoperative (Vmca) was 76 KIAS. The maximum speed for full flap extension (40°) was 132 KIAS. The POH also stated that a single-engine go-around should be avoided if at all possible. The pilot’s decision to commit to the landing was reasonable given the circumstances and the guidance provided by the POH; however, it is likely that his decision to conduct the landing without flaps and the airplane’s excessive airspeed at touchdown resulted in the runway overrun.
Probable cause:
A runway overrun during a precautionary landing following a total loss of right engine power due to detonation and subsequent oil starvation. Contributing was the pilot’s failure to lower the flaps and the excessive airspeed at touchdown.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Medellín: 8 killed

Date & Time: Nov 21, 2022 at 1015 LT
Operator:
Registration:
HK-5121
Flight Phase:
Survivors:
No
Site:
Schedule:
Medellín – Pizarro
MSN:
31-7652004
YOM:
1976
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The twin engine airplane was chartered by the Grupo San Germán Express to carry a team of six people from Medellín to Pizarro, Chocó. Shortly after takeoff from runway 02 at Medellín-Enrique Olaya Herrera Airport, while in initial climb, the crew encountered engine problems. The airplane went out of control and crashed onto a house located in the district of Belén Rosales, less than 500 metres from the runway end, bursting into flames. The house and the aircraft were destroyed and all 8 occupants were killed.
Crew:
Julián Aladino, pilot,
Sergio Guevara Delgado, copilot.
Passengers:
Jorge Cantillo Martínez,
Dubán Ovalle Quintero,
Anthony Mosquera Blanquiceth,
Pedro Pablo Serna,
Melissa Pérez Cuadros,
Nicolás Jiménez.

Crash of a Piper PA-31-350 Navajo Chieftain in Cobán

Date & Time: Apr 3, 2022
Operator:
Registration:
PT-ECU
Flight Type:
Survivors:
Yes
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances in bushes near Cobán, Guatemala, while engaged in an illegal flight. The aircraft was damaged beyond repair and no one was found on the scene. The registration seems to be false.

Crash of a Piper PA-31-350 Navajo Chiefain in Medford: 1 killed

Date & Time: Dec 5, 2021 at 1652 LT
Registration:
N64BR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Medford - Fallon
MSN:
31-7752124
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2167
Captain / Total hours on type:
1520.00
Aircraft flight hours:
8809
Circumstances:
The airplane was departing into instrument meteorological conditions using a standard instrument departure. The takeoff instructions consisted of making a climbing right turn direct to a nondirectional beacon. After departing, the pilot made a radio communication to an air traffic controller asking if he will tell him when to turn. The controller replied that he would not be calling his turn and that the pilot should fly the departure as published making a climbing right turn to overfly the approach end of the runway. The pilot acknowledged the communication, which was his last transmission. The airplane made a 360° turn and descended below the cloud layer. The airplane then climbed back into the cloud layer and made an inverted loop, descending into the ground in a near-vertical attitude. A postaccident examination of the airplane revealed no evidence of preimpact mechanical malfunctions or failures. Recorded audio of the airplane before the accident was consistent with the engines operating. The signatures on both propellers were consistent with one another and consistent with the engines operating at a similar rpm. The pilot was qualified and recently underwent recurrent training. The reasons the pilot became spatially disoriented could not definitely determined. The pilot left the anti-collision lights on while in the clouds, which may have resulted in him having flicker vertigo.
Probable cause:
The pilot’s failure to maintain aircraft control during the initial climb into clouds due to spatial disorientation, which resulted in an uncontrolled descent and collision with terrain.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain off South Bimini: 1 killed

Date & Time: Apr 16, 2021 at 2142 LT
Operator:
Registration:
N827RD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
South Bimini – Miami-Opa Locka
MSN:
31-7652094
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2085
Aircraft flight hours:
7102
Circumstances:
The airplane crashed moments after takeoff from the South Bimini Int’l Airport (MYBS), Bimini, Bahamas. The private flight departed MYBS with intended final destination of Opa Locka Airport (KOPF), Opa Locka, Florida, USA. The pilot sustained serious injuries and after being seen by medical personnel in South Bimini, was flown to Nassau, Bahamas for further medical attention. The passenger who occupied the right seat of the aircraft, succumbed to injuries he sustained as a result of the initial impact and subsequent crash sequence and subsequent submersion in the waters at the end of the runway environment. The pilot was a US certified commercial pilot with ratings for airplane land, single and multi-engine as well as an instrument airplane rating. The pilot’s medical certificate was valid at the time of the accident. The passenger (pilot’s son) also held a valid US certified private pilot – single engine land – airplane certificate. It is unknown what role (if any) the passenger (son) played during the takeoff to crash sequence. The weather conditions at the time of the accident was night (instrument meteorological conditions). A weak high pressure ridging was forecasted to continue to dominate the weather over the Bahamas throughout the night. However, no significant weather was anticipated.
Probable cause:
The AAIA has determined the probable cause of this accident to be loss of control inflight (LOC-I), resulting in uncontrolled flight into terrain (ocean). The cause of this loss of control could not be determined.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Salitre: 6 killed

Date & Time: Apr 7, 2021 at 1200 LT
Operator:
Registration:
HC-CVC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Nueva Loja – Guayaquil
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The twin engine airplane (a PA-31 Panther II variant) departed Nueva Loja-Lago Agrio Airport at 1023LT on an ambulance flight to Guayaquil, carrying one patient, one nurse, two doctors and two pilots. The descent to Guayaquil-José Joaquín de Olmedo Airport was started when the aircraft crashed in unknown circumstances in the Río Salitre, near Salitre, about 35 km north of Guayaquil Airport. The aircraft was destroyed and all six occupants were killed.

Crash of a Piper PA-31-350 Navajo Chieftain in Sergio Butrón Casas

Date & Time: Mar 3, 2021 at 1447 LT
Operator:
Registration:
N640WA
Flight Phase:
Survivors:
Yes
Schedule:
Morelia - Chetumal
MSN:
31-8252065
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot was approaching Chetumal Airport when he reported engine problems. He elected to make an amergency landing when the aircraft crash landed in an open field located in Sergio Butrón Casas, about 25 km west of Chetumal Airport. Both occupants were slightly injured and the aircraft was damaged beyond repair.

Crash of a Piper PA-31-350 Navajo Chieftain near Cooper Landing: 3 killed

Date & Time: Nov 29, 2019 at 1911 LT
Operator:
Registration:
N4087G
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Anchorage – Seward
MSN:
31-8152127
YOM:
1981
Flight number:
SVX36
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
35000
Captain / Total hours on type:
1200.00
Aircraft flight hours:
5502
Circumstances:
On November 29, 2019, about 1911 Alaska standard time, a Piper PA-31-350 airplane, N4087G, was destroyed by impact and postcrash fire when it collided with mountainous terrain about 15 miles west of Cooper Landing, Alaska. The three occupants; the airline transport pilot, a flight nurse, and the flight paramedic were fatally injured. The airplane was operated by Fly 4 You Inc., doing business as Security Aviation, as a Title 14 Code of Federal Regulations Part 135 visual flight rules air ambulance flight. Dark night visual meteorological conditions existed at the departure and destination locations and company flight following procedures were in effect. The flight departed Ted Stevens International Airport (PANC), Anchorage, Alaska, about 1848, destined for Seward Airport (PAWD), Seward, Alaska. Dispatch records indicated that, on November 29, Providence Seward Medical Center emergency clinic personnel contacted multiple air ambulance companies with a "weather check" for possible air ambulance transportation of a patient from Seward to Anchorage. The first company contacted was Guardian Flight, who declined the flight at 1624 due to limited daylight hours. The second company, LifeMed Alaska, declined the flight at 1637 due to weather. The third and final company contacted for the flight was Medevac Alaska. Their dispatch officer was not notified of the previous declined flight requests and forwarded the request to Security Aviation, who is their sole air charter provider. At 1731 Security Aviation accepted the flight, and Medevac Alaska flight SVX36 was staffed with a nurse and paramedic. A preliminary review of archived Federal Aviation Administration (FAA) radar and automatic dependent surveillance (ADS-B) data revealed that the accident airplane departed PANC and flew south about 3,000 ft mean sea level (msl) toward the Sterling Highway. The airplane was then observed descending to 2,200 ft msl while flying a right racetrack pattern before flying into the valley toward Cooper Landing. The last data point indicated that at 1911:14 the airplane was over the west end of Jean Lake at 2,100 ft msl, on a 127° course, and 122 kts groundspeed. Ground witnesses who were in vehicles on the Sterling Highway near milepost 63, reported that they saw the lights of the airplane flying over the highway that night. One witness stated that he saw the airplane west of the mountains turn in a circle as it descended and then entered the valley. He observed the wings rocking back and forth and while he was looking elsewhere, he heard an explosion and observed a large fire on the mountainside. Another witness reported seeing the airplane flying low and explode when it impacted the mountain. Witnesses to the fire called 911 and observed the wreckage high on the mountainside burning for a long time after impact. The airplane was reported overdue by the chief pilot for Security Aviation and the FAA issued an alert notice (ALNOT) at 2031. The Alaska Rescue Coordination Center dispatched an MH-60 helicopter to the last known position and located the burning wreckage that was inaccessible due to high winds in the area. On December 1, 2019, the Alaska State Troopers coordinated a mountain recovery mission with Alaska Mountain Rescue Group. The wreckage was observed on the mountain at an elevation of about 1,425 ft msl in an area of steep, heavily tree-covered terrain near the southeast end of Jean Lake in the Kenai National Wildlife Refuge. The airplane was highly fragmented and burned, however all major airplane components were accounted for. Multiple large trees around the wreckage were fractured and indicated an easterly heading prior to the initial impact.