Crash of a Piper PA-31-350 Navajo Chieftain in Rainbow Lake

Date & Time: Jan 15, 1998 at 1935 LT
Registration:
C-FZBW
Flight Phase:
Survivors:
Yes
Schedule:
Rainbow Lake – High Level – Edmonton – Calgary
MSN:
31-8152096
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3700
Captain / Total hours on type:
93.00
Copilot / Total flying hours:
632
Copilot / Total hours on type:
277
Circumstances:
The Airco Aircraft Charters Piper PA-31-350 Chieftain, serial number 31-8152096, had been chartered by Northern Sky Aviation to complete a daily passenger flight from the Edmonton City Centre Airport to High Level, Rainbow Lake, Edmonton, and Calgary, Alberta. The flight from Edmonton to High Level and Rainbow Lake was uneventful. Following a routine landing and turn around, the aircraft departed Rainbow Lake in darkness, at 1935 mountain standard time (MST), on an instrument flight rules (IFR) flight to Edmonton. Shortly after take-off from runway 27, the aircraft collided with trees and terrain approximately 3 000 feet west of the departure end of the runway. The nine occupants sustained minor injuries and the aircraft was substantially damaged. Immediately following the evacuation of the aircraft, a Rainbow Lake passenger initiated the local emergency response by cell phone. Volunteer ground rescue personnel organized a snowmobile search, and a helicopter was dispatched from the airport to conduct an aerial search. The ground search was hampered by darkness, dense forest, cold temperatures, and deep snow. The helicopter pilot located the aircraft wreckage on his first pass over the departure corridor and, following his immediate return to the airport, he lead the ground rescuers to the accident site. Rescuers reached the accident site approximately one and one-half hours after the occurrence and assisted all of the survivors to the Rainbow Lake nursing station.
Probable cause:
The aircraft was inadvertently flown into trees and the ground, in controlled flight and dark ambient conditions, during a night departure because a positive rate of climb was not maintained after take off. Factors contributing to the accident were the pilot’s concentrating on blue line speed rather than maintaining a positive rate of climb, the dark ambient conditions, a departure profile into rising terrain, an overweight aircraft, and crew resource mismanagement.
Final Report:

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

Date & Time: Jan 9, 1998 at 1935 LT
Operator:
Registration:
N4111M
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manila - Saipan
MSN:
31-8352001
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On January 9, 1998, at 1935 hours Philippines local time, a Piper PA-31, N4111M, reportedly experienced a loss of engine power and crashed at the Ninoy Aquino International Airport, Manila, Philippines. The aircraft was substantially damage the airline transport rated pilot and copilot were not injured. Visual meteorological conditions existed for the night ferry flight to Saipan in the Marianas, and an instrument flight rules (IFR) flight plan had been filed. The pilot stated that after completing a preflight they had been cleared to taxi to the active runway. The pilot requested a full length takeoff from runway 06. Approximately 75 feet after lifting off from the ground, the pilot requested that the copilot retract the landing gear. The pilot reported that shortly after the landing gear was raised the aircraft yawed sharply to the right. He lowered the nose to regain some of the airspeed that was lost due to the right yaw. He stated that they were losing airspeed and altitude quickly, and asked the copilot to extend the landing gear. The pilot reported that on landing he had the power on until they contacted the runway. The aircraft slid to the left and came to rest after striking a concrete ditch. A test flight of the accident aircraft had been conducted 2 days and on the day before the accident. The purpose of the test flights were to check the propellers that had been overhauled, and to obtain a ferry permit from the Federal Aviation Administration's Designated Airworthiness Representative (DAR). The DAR found the aircraft to be within required specifications. He made the appropriate entry into the aircraft's logbook and issued the ferry authorization.

Crash of a Piper PA-31-350 Navajo Chieftain on Mt Kilimandjaro: 1 killed

Date & Time: Nov 1, 1997 at 1020 LT
Operator:
Registration:
5H-AZM
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Nairobi - Zanzibar
MSN:
31-8052207
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
10000
Circumstances:
On 1 November 1997 at 09:46 hours 5H-AZM took off from Nairobi Wilson airport, for a visual flight rules flight to Zanzibar International Airport, Tanzania. It was carrying one pilot and some cargo. There were no passengers. The flight plan indicated that the aircraft had 0330 hours of fuel on departure. The pilot planned' to fly a direct route to Zanzibar with Dar-es-salaam International airport as his alternate aerodrome. After take off from Nairobi Wilson, the flight transited the southern axis lane of the Nairobi control Zone to the zone boundary. The pilot checked the Nairobi zone boundary with Nairobi Wilson Tower and was instructed by air traffic control to contact the Nairobi Control Centre. No contact was reported established by Nairobi Control with 5H-AZM. 5H-AZM contacted the Kilimanjaro Control Tower at 10:20 hours and passed his own ward estimates as Flight Information Region 10:25 hours and arrival at Zanzibar at 11:40 hours. 5H-AZM was advised that there was no reported traffic for the flight in the Kilimanjaro Terminal Control area at 'the VFR flight level 115, and at the same time instructed the aircraft to contact Dar-es-salaam Control on 119.6 MHz when in range. No further transmission was received from the aircraft. It also failed to arrive in Zanzibar. Unfruitful formal searches (involving communications, aerial and ground searches) were mounted on 3 November 1997 along the probable route area in Kenya and Tanzania. The formal search was terminated on 4 December 1997 and there after the missing aircraft incident was considered to be an 'accident. Wreckage was eventually located in the Kibo Crater near the summit of Mount Kilimanjaro in Tanzania on 28 August 2003, almost six years later. The wreckage of the Piper PA 31-350 was found at 15,400 feet on the Kibo wing. It was also 30 nautical miles west of its projected track. The aircraft had earlier been cleared to climb from 9,500 feet to 11,500 feet under visual flight rules.
Probable cause:
Controlled flight into terrain for unknown reasons.

Crash of a Piper PA-31-350 Navajo Chieftain off Hilo

Date & Time: Apr 10, 1997 at 0706 LT
Registration:
N27659
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hilo - Hayward
MSN:
31-7852090
YOM:
1978
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5700
Captain / Total hours on type:
15.00
Aircraft flight hours:
5074
Circumstances:
The aircraft was being operated on a trans-Pacific ferry flight. A special flight permit authorized a gross weight increase and ferry fuel tanks had been installed along with long range communication and navigation radios. The pilot reported that when 85 miles from the departure airport, the right engine failed and he was unable to restart it. Power from the remaining engine was insufficient to maintain level flight at the overweight condition and the pilot permitted the aircraft to drift down until it was necessary to ditch in the ocean 28 miles offshore. The pilot had departed and returned to Hawaii twice previously. The first time he returned due to an oil leak on the left engine, and the second time because of a loose window. A mechanic who repaired the window reported that the left engine appeared to still be leaking oil. Both pilots told the FAA inspector that the oil leak had been repaired.
Probable cause:
The loss of engine power in one engine for undetermined reasons. A factor in the accident was the aircraft's diminished single engine performance during the early portion of the overweight ferry flight.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Charlo: 8 killed

Date & Time: Oct 20, 1996 at 1213 LT
Operator:
Registration:
N744W
Survivors:
No
Schedule:
Port-Menier - Gaspé - Bangor
MSN:
31-7952246
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
3600
Captain / Total hours on type:
1000.00
Aircraft flight hours:
6041
Circumstances:
The aircraft, a Piper PA-31-350 Navajo Chieftain (hereafter referred to as a Chieftain), took off at 1113 Atlantic daylight saving time on a charter flight from Port-Menier, Quebec, to Bangor, Maine, with one pilot and seven passengers on board. As the aircraft was approaching Charlo, New Brunswick, the pilot reported to Moncton Air Traffic Control Centre that his aircraft had a rough-running engine, and that he would be making an emergency landing at Charlo airport. While the pilot was apparently manoeuvring to land the aircraft, it crashed three miles west of the runway, in the community of Eel River Crossing. All eight occupants of the aircraft received fatal injuries.
Probable cause:
There was a loss of power from the right engine, and the pilot did not conserve altitude or configure the aircraft for maximum performance following the loss of power. Control of the aircraft was lost, probably as the pilot was attempting to intercept the ILS for runway 13 during a low-level turn. Contributing factors were the overweight condition of the aircraft and the lack of in-flight emergency procedures training received by the pilot.
Final Report:

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

Date & Time: Feb 27, 1996
Operator:
Registration:
ZS-MZH
Flight Phase:
Flight Type:
Site:
MSN:
31-7405232
YOM:
1974
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances in a mountainous area near Sabie. Occupant's fate unknown.

Crash of a Piper PA-31-350 Navajo Chieftain in King Island-Currie: 1 killed

Date & Time: Feb 8, 1996 at 0507 LT
Operator:
Registration:
VH-KIJ
Flight Type:
Survivors:
No
Schedule:
Melbourne - King Island
MSN:
31-7405222
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5519
Captain / Total hours on type:
106.00
Circumstances:
A witness heard the aircraft pass King Island aerodrome at 0455 EST at the same time as he noticed the pilot-activated 10/28 runway lights illuminate. The pilot reported to Melbourne Control that he would be completing a runway 10, non-directional beacon (NDB) approach. A short time later he broadcast that the aircraft was at the minimum descent altitude, which is 640 feet above mean sea level (AMSL) for a runway 10 NDB approach. He also broadcast that there was a complete cloud cover. The aircraft did not enter a missed approach procedure but was heard to fly towards the south-east from overhead the NDB, which is located 1.3 km south-south-west of the centre of runway 10/28. A second witness, located near the NDB site, reported observing the aircraft's lights to the south-east. At 0507 a farmer heard the aircraft pass low over his house shortly before it crashed into trees, 3.5 km south-east of the aerodrome. The first responders arrived at the accident site at about 0530. The pilot had not survived.
Probable cause:
The pilot continued a visual approach in conditions which prevented him from maintaining adequate visual clearance from the ground or obstacles and which made visual judgement of the approach difficult. Also, the pilot probably did not recognise that the conditions were not suitable for a visual approach.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Johannesburg: 2 killed

Date & Time: Jan 26, 1996
Operator:
Registration:
ZS-KBY
Flight Phase:
Flight Type:
Survivors:
No
MSN:
31-7852067
YOM:
1978
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Johannesburg-Oliver Reginald Tambo Airport, while climbing, the twin engine aircraft went out of control and crashed near Boksburg, about 5 km south of the airport. Both occupants were killed.

Crash of a Piper PA-31-350 Navajo Chieftain in Moroubas: 10 killed

Date & Time: Jan 12, 1996 at 1006 LT
Operator:
Registration:
TL-ASB
Flight Phase:
Survivors:
No
Schedule:
Bangui - Koumbala
MSN:
31-7852054
YOM:
1978
Location:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
En route from Bangui to Koumbala, province of Bamingui-Bangoran, while cruising at an altitude of 7,000 feet, the pilot encountered technical problems with the right engine that was shut down and its propeller feathered. The pilot declared an emergency and elected to divert to Bambari Airport. Thirteen minutes later, the aircraft went out of control and crashed in an isolated area located about 60 km northwest of Bambari Airport. The aircraft was destroyed by impact forces and a post crash fire and all 10 occupants were killed.
Probable cause:
Failure of the right engine in flight for unknown reasons.

Crash of a Piper PA-31-350 Navajo Chieftain in San Jose: 2 killed

Date & Time: Dec 23, 1995 at 0019 LT
Operator:
Registration:
N27954
Flight Type:
Survivors:
No
Site:
Schedule:
Oakland - San Jose
MSN:
31-7952062
YOM:
1979
Flight number:
AMF041
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4659
Captain / Total hours on type:
914.00
Aircraft flight hours:
9840
Aircraft flight cycles:
10966
Circumstances:
The aircraft impacted mountainous terrain in controlled flight during hours of darkness and marginal VFR conditions. The flight was being vectored for an instrument approach during the pilot's 14 CFR Part 135 instrument competency check flight. The flight was instructed by approach control to maintain VFR conditions, and was assigned a heading and altitude to fly which caused the aircraft to fly into another airspace sector below the minimum vectoring altitude (MVA). FAA Order 7110.65, Section 5-6-1, requires that if a VFR aircraft is assigned both a heading and altitude simultaneously, the altitude must be at or above the MVA. The controller did not issue a safety alert, and in an interview, said he was not concerned when the flight approached an area of higher minimum vectoring altitudes (MVA's) because the flight was VFR and 'pilots fly VFR below the MVA every day.' At the time of the accident, the controller was working six arrival sectors and experienced a surge of arriving aircraft. The approach control facility supervisor was monitoring the controller and did not detect and correct the vector below the MVA.
Probable cause:
The failure of the air traffic controller to comply with instructions contained in the Air Traffic Control Handbook, FAA Order 7110.65, which resulted in the flight being vectored at an altitude below the minimum vectoring altitude (MVA) and failure to issue a safety advisory. In addition, the controller's supervisor monitoring the controller's actions failed to detect and correct the vector below the MVA. A factor in the accident was the flightcrew's failure to maintain situational awareness of nearby terrain and failure to challenge the controller's instructions.
Final Report: