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

Date & Time: Jun 6, 2003 at 1907 LT
Registration:
ZK-NCA
Survivors:
Yes
Schedule:
Palmerston North – Christchurch
MSN:
31-7405203
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
4325
Captain / Total hours on type:
820.00
Aircraft flight hours:
13175
Circumstances:
The aircraft was on an air transport charter flight from Palmerston North to Christchurch with one pilot and 9 passengers. At 1907 it was on an instrument approach to Christchurch Aerodrome at
night in instrument meteorological conditions when it descended below minimum altitude, in a position where reduced visibility prevented runway or approach lights from being seen, to collide with trees and terrain 1.2 nm short of the runway. The pilot and 7 passengers were killed, and 2 passengers received serious injury. The aircraft was destroyed. The accident probably resulted from the pilot becoming distracted from monitoring his altitude at a critical stage of the approach. The possibility of pilot incapacitation is considered unlikely, but cannot be ruled out.
Probable cause:
Findings:
- The pilot was appropriately licensed and rated for the flight.
- The pilotís previously unknown heart disease probably would not have made him unfit to hold his class 1 medical certificate.
- The pilotís ability to control the aircraft was probably not affected by the onset of any incapacitation associated with his heart condition.
- Although the pilot was experienced on the PA 31 type on VFR operations, his experience of IFR operations was limited.
- The pilot had completed a recent IFR competency assessment, which met regulatory requirements for recent instrument flight time.
- The aircraft had a valid Certificate of Airworthiness, and the scheduled maintenance which had been recorded met its airworthiness requirements.
- The return of the cabin heater to service by the operator, after the maintenance engineer had disabled it pending a required test, was not appropriate but was not a factor in the accident.
- The cabin heater was a practical necessity for IFR operations in winter, and the required test should have been given priority to enable its safe use.
- The 3 unserviceable avionics instruments in the aircraft did not comply with Rule part 135, and indicated a less than optimum status of avionics maintenance. However there was sufficient
serviceable equipment for the IFR flight.
- The use of cellphones and computers permitted by the pilot on the flight had the potential to cause electronic interference to the aircraftís avionics, and was unsafe.
- The pilotís own cellphone was operating during the last 3 minutes of the flight, and could have interfered with his glide slope indication on the ILS approach.
- The aircraftís continued descent below the minimum altitude could not have resulted from electronic interference of any kind.
- The pilotís altimeter was correctly set and displayed correct altitude information throughout the approach.
- There was no aircraft defect to cause its continued descent to the ground.
- The aircraftís descent which began before reaching the glide slope, and continued below the glide slope, resulted either from a faulty glide slope indication or from the pilot flying a localiser approach instead of an ILS approach.
- When the aircraft descended below the minimum altitude for either approach it was too far away for the pilot to be able to see the runway and approach lights ahead in the reduced visibility at the time.
- The pilot allowed the aircraft to continue descending when he should have either commenced a missed approach or stopped the aircraftís descent.
- The pilotís actions or technique in flying a high-speed unstabilised instrument approach; reverting to hand-flying the aircraft at a late stage; not using the autopilot to fly a coupled approach and, if intentional, his cellphone call, would have caused him a high workload and possibly overload and distraction.
- The pilotís failure to stop the descent probably arose from distraction or overload, which led to his not monitoring the altimeter as the aircraft approached minimum altitude.
- The possibility that the pilot suffered some late incapacity which reduced his ability to fly the aircraft is unlikely, but cannot be ruled out.
- If TAWS equipment had been installed in this aircraft, it would have given warning in time for the pilot to avert the collision with terrain.
- While some miscommunication of geographical coordinates caused an erroneous expansion of the search area, the search for the aircraft was probably completed as expeditiously as possible in difficult circumstances.
Final Report:

Crash of a Yakovlev Yak-42D near Trabzon: 75 killed

Date & Time: May 26, 2003 at 0445 LT
Type of aircraft:
Operator:
Registration:
UR-42352
Survivors:
No
Site:
Schedule:
Bishkek - Trabzon - Zaragoza
MSN:
18 11 395
YOM:
1988
Flight number:
UKM4230
Country:
Region:
Crew on board:
13
Crew fatalities:
Pax on board:
62
Pax fatalities:
Other fatalities:
Total fatalities:
75
Aircraft flight hours:
18739
Aircraft flight cycles:
9700
Circumstances:
Chartered by the Spanish Government, the aircraft was completing a charter flight from Bishkek to Zaragoza with an intermediate stop in Trabzon, carrying 62 Spanish peacekeepers and 13 crew members. The 62 passengers were respectively 41 members of the Land Forces and 21 members of the Air Force who were returning to Spain following a peacekeeping mission in Afghanistan. While descending to Trabzon Airport by night, the crew encountered poor visibility due to foggy conditions. Unable to establish a visual contact with the approach lights and the runway 29, the crew initiated a go-around procedure. Few minutes later, while completing a second approach, the crew failed to realize he was not following the correct pattern for an approach to runway 29 when the aircraft impacted a mountain at an altitude of 4,600 feet. The aircraft disintegrated on impact and all 75 occupants were killed. The wreckage was found 3,5 km east of the village of Maçka, about 23 km southwest of the airport.
Probable cause:
The accident was the consequence of a controlled flight into terrain due to the combination of the following factors:
- Loss of situational awareness on part of the flying crew,
- The crew failed to comply with the Standard Operational Procedures published by the operator,
- The crew failed to follow the published approach charts,
- Implementation of a non-precision approach,
- Incorrect use of the automated flight systems,
- Inadequate training (LOFT),
- The crew descended below the MDA in limited visibility.

Crash of a Beechcraft 1900C-1 in Kinshasa

Date & Time: Apr 29, 2003 at 1930 LT
Type of aircraft:
Operator:
Registration:
TR-LFQ
Survivors:
Yes
Schedule:
Brazzaville - Kinshasa
MSN:
UC-80
YOM:
1989
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Brazzaville on a charter flight to Kinshasa, carrying 13 passengers (all Air France crew members) and two pilots. On approach to Kinshasa, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and strong crosswinds. After touchdown, the aircraft became unstable, deviated to the left and veered off runway. While contacting soft ground, the aircraft lost its undercarriage and slid for few dozen metres before coming to rest beside the runway. All 15 occupants escaped uninjured but the aircraft was damaged beyond repair.
Probable cause:
It is believed that the aircraft became unstable at touchdown due to strong crosswinds. A inappropriate reaction on part of the pilot-in-command, an overcorrection or a wrong configuration may have been a contributing factor.

Crash of a Vickers 836 Viscount in Democratic Republic of Congo

Date & Time: Apr 27, 2003
Type of aircraft:
Operator:
Registration:
9Q-CGL
Flight Phase:
Survivors:
Yes
MSN:
435
YOM:
1960
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The exact circumstances of this accident remains unknown. While landing on a 900 meters long gravel runway somewhere in DRC, one of the four engine was damaged. The crew later decided to takeoff on a three-engine configuration but a second engine failed during takeoff. The aircraft stalled and crashed near the runway end. There were no casualties.
Probable cause:

Crash of a Cessna 411 in Colchani: 1 killed

Date & Time: Feb 28, 2003 at 1115 LT
Type of aircraft:
Registration:
CP-1885
Flight Phase:
Survivors:
Yes
Schedule:
Uyuni - Oruro
MSN:
411-0191
YOM:
1966
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
After takeoff from Uyuni-La Joya Andina Airport, while climbing, the crew encountered engine problems. They attempted an emergency landing when the aircraft crashed near Colchani, about 16 km north of the airport. A pilot was killed while four other occupants were injured. The aircraft was destroyed.
Probable cause:
Failure of the right engine during initial climb for unknown reasons.

Crash of a Cessna 402B off Karachi: 8 killed

Date & Time: Feb 24, 2003
Type of aircraft:
Operator:
Registration:
AP-BFG
Flight Phase:
Survivors:
No
Schedule:
Karachi - Kabul
MSN:
402B-1304
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Aircraft flight hours:
6793
Circumstances:
The aircraft was chartered by the Afghan Government to carry a delegation from Karachi to Kabul. After takeoff from Karachi-Quaid-e-Azam Airport, the twin engine aircraft continued to climb to an altitude of 9,000 feet when it entered an uncontrolled descent. At an altitude of 2,500 feet, the aircraft disappeared from radar screens then crashed in the Arabian Sea few km offshore. The stabilizers and the tail were found few hundred metres from the main wreckage. All eight occupants were killed, among them Juma Mohammad Mohammadi, Afghan Minister of Industry and four members of his cabinet as well as one Chinese businessman.
Probable cause:
The Pakistan board of investigations determined that the probable cause of this accident was a structural failure due to overload. The aircraft weight was 7,183 lbs at the time of the accident as the maximum load as mentioned in the operational manual is 6,300 lbs, which means 883 pounds above max gross weight. It is believed that during climbout, the tail and stabilizers detached due to overload conditions.

Crash of a Cessna 402C in Sacramento

Date & Time: Jan 23, 2003 at 2030 LT
Type of aircraft:
Operator:
Registration:
N6814A
Survivors:
Yes
Schedule:
Ukiah – Sacramento
MSN:
402C-0645
YOM:
1982
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3400
Captain / Total hours on type:
350.00
Aircraft flight hours:
13817
Circumstances:
The airplane collided with obstructions following a loss of power in one engine during a missed approach. Following the collision sequence the airplane came to rest upright about 500 feet from the approach end of the runway and was destroyed in a post-impact ground fire. The pilot told a responding sheriff's deputy and a Federal Aviation Administration (FAA) inspector that he made the ILS approach to land and initiated a missed approach. When he added power, the left engine sputtered and the airplane veered to the left. He activated the fuel boost pump, but the airplane contacted obstructions and crashed. The responding sheriff's deputy also observed the accident. He heard an engine of an airplane making unusual sounds. The engine "seemed to get quiet and then revved higher as if to climb." He looked in the direction of the sound and saw a series of blue flashes and then an orange fireball. The deputy reported that there was a dense fog in the area at the time. At the time of the accident, the airport's weather conditions were reported as 100 feet overcast and 1/4-mile visibility in fog. The landing minimums for the ILS approach are 200 feet and 1/2-mile. According to the operator's records, when the airplane departed from Ukiah, its gross takeoff weight was about 5,909 pounds. The pilot operating handbook (POH) for the airplane lists the following items in the single engine go around checklist: 1) Throttle full forward; 2) wing flaps up; 3) when positive climb rate achieved, gear up; 4) ensure the inoperative engine is feathered. For a gross weight of 5,900 pounds, and the existing atmospheric conditions, the single engine climb performance chart shows an expected positive rate of climb of 500 feet per minute if the airplane was configured correctly. The chart also lists the following subtractions from that performance for the listed condition: 1) -400 fpm for wind milling inoperative engine; 2) -350 feet for landing gear down; 3) -200 fpm for flaps extended to 15 degrees. Examination of the wreckage disclosed that neither engine's propeller was feathered, the landing gear was down and the flaps were extended to 10 degrees. Without the airplane configured correctly for the single engine missed approach, the net climb performance would be a negative 400 feet per minute. There were no discrepancies noted with the airframe examination. The engine examination revealed no mechanical anomalies with either engine that would have precluded normal operation. 14 CFR 135.224 states that a pilot cannot initiate an approach if the weather conditions are below landing minimums if the approach is started outside of the final approach fix. The pilot can continue the landing if they are already established on the approach and the airport goes below landing minimums. According to the operator's FAA approved operating specifications, the operator had not been approved for lower than standard landing minimums.
Probable cause:
Loss of engine power in the left engine for undetermined reasons. Also causal was the pilot's failure to correctly configure the airplane for a single engine missed approach, which resulted in a negative climb performance. A factor was the pilot's decision to initiate the approach when the weather conditions were below the published approach minimums.
Final Report:

Crash of a Cessna 207A Skywagon in Put-in-Bay

Date & Time: Jan 20, 2003 at 0945 LT
Operator:
Registration:
N9945M
Flight Phase:
Survivors:
Yes
Schedule:
Put-in-Bay – Port Clinton
MSN:
207-0153
YOM:
1970
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4500
Captain / Total hours on type:
405.00
Aircraft flight hours:
6283
Circumstances:
Shortly after takeoff, about 300 feet agl, the engine lost all power. The pilot activated the electric fuel pump, and moved the fuel selector several times. However, the engine did not regain power, and the pilot performed a forced landing into trees. After the accident, the pilot stated to a police officer that he might have departed with the fuel selector positioned to an empty tank. The pilot subsequently stated that both fuel gauges indicated "1/4" full, and he could not remember which tank was selected during the takeoff. Additionally, a passenger stated that he did not smell or observe fuel when he exited the airplane. The passenger added that in the past, the pilot had exhausted one fuel tank, then switched to the other tank and the engine re-started. Examination of the wreckage by an FAA inspector revealed that fuel selector was positioned to the right tank. The right fuel tank contained some fuel, and left fuel tank had ruptured. Following the accident, a successful engine test-run was performed.
Probable cause:
The pilot's inadequate fuel management, which resulted in fuel starvation and a total loss of engine power during the initial climb.
Final Report:

Crash of a BAe 3101 Jetstream 31 in Yacuiba

Date & Time: Jan 17, 2003 at 0900 LT
Type of aircraft:
Operator:
Registration:
CP-2404
Survivors:
Yes
Schedule:
Yacuiba - Santa Cruz
MSN:
680
YOM:
1985
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8194
Copilot / Total flying hours:
832
Circumstances:
During the takeoff roll at Yacuiba Airport, at V2 speed, the right engine lost power. The captain decided to continue the takeoff procedure. During initial climb, decision was taken to return for an emergency landing and the crew shut down the right engine and feathered its propeller. After touchdown on runway 20, the aircraft was unable to stop within the remaining distance, overran, lost its nose gear and collided with bushes and small trees, coming to rest about 50 metres past the runway end. All 21 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The accident was the consequence of the combination of the following factors:
- Excessive speed upon landing,
- Delayed application of the brake systems,
- The runway length available was limited according to the conditions in force,
- The total weight of the aircraft upon landing,
- The aircraft configuration,
- The direction and intensity of the wind,
- An inadequate crew training.
Additionally, the exact cause of the loss of power on the right engine was not clearly determined at the time the final report was published.
Final Report:

Crash of a Raytheon 390 Premier I in Santo Domingo

Date & Time: Jan 8, 2003 at 1824 LT
Type of aircraft:
Registration:
N390RB
Survivors:
Yes
Schedule:
Santo Domingo - Santo Domingo
MSN:
RB-26
YOM:
2002
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft overran the runway and came to rest in a parking lot, while landing at Herrera International Airport, Santo Domingo, Dominican Republic, while on a 14 CFR Part 91 positioning flight. Visual meteorological conditions prevailed at the time and a visual flight rules flight plan was filed. The airplane received substantial damage and the airline transport-rated pilot, copilot, and two passengers received minor injuries. The flight originated from Las Americas International Airport, Santo Domingo, Dominican Republic, the same day, about 1810. The pilot stated they made a normal approach and landing on runway 19 at Herrera International Airport. Once on the ground they activated lift dump spoilers, but the system failed. They were unable to stop the airplane on the remaining runway. The airplane came to a stop, inverted beyond a street that is at the end of the runway.