Crash of a Let L-410UVP-E in San Cristóbal: 4 killed

Date & Time: Jul 13, 2003 at 1415 LT
Type of aircraft:
Registration:
YV-1060CP
Survivors:
Yes
Site:
Schedule:
La Carlota - San Cristóbal
MSN:
90 25 05
YOM:
1990
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
While descending to San Cristóbal Airport, the crew encountered marginal weather conditions and limited visibility due to low clouds. On approach, the twin engine aircraft struck the slope of Mt La Gama located in the Chorro del Indio National Park. Six people were seriously injured while four passengers were killed. The aircraft was destroyed by impact forces.
Probable cause:
Controlled flight into terrain after the crew initiated the descent prematurely in poor visibility.

Crash of a Mitsubishi MU-2B-35 Marquise in Belém: 4 killed

Date & Time: Jul 1, 2003 at 1957 LT
Type of aircraft:
Operator:
Registration:
PT-LFX
Survivors:
No
Schedule:
São Luis – Belém
MSN:
650
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
11236
Captain / Total hours on type:
4886.00
Copilot / Total flying hours:
1015
Copilot / Total hours on type:
359
Circumstances:
The twin engine aircraft was completing a taxi flight from São Luis to Belém, carrying two passengers, two pilots and a load of briefcases with bank documents. On approach to Belém-Val de Cans Airport by night, the crew encountered poor weather conditions with limited visibility, CB's, rain falls and severe turbulences. On final approach, the aircraft went out of control and crashed on the Ilha das Onças Island, about 5,5 km west of runway 06 threshold. The aircraft was destroyed and all four occupants were killed.
Probable cause:
It was determined that both engines were running normally at impact and no technical anomalies were found on the aircraft and its equipments. Both pilots were properly licenced and experienced on this type of aircraft. At the time of the accident, weather conditions were poor with CB's, rains falls, severe turbulences, strong winds and probable windshear that may have been a contributing factor.
Final Report:

Crash of a Cessna 402B in Little Whale Cay

Date & Time: Jun 17, 2003 at 1330 LT
Type of aircraft:
Registration:
N3748C
Survivors:
Yes
Schedule:
Chub Cay - Little Whale Cay
MSN:
402B-0606
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On June 17, 2003, about 1330 eastern daylight time, a Cessna 402B, N3748C, registered to Hamilton Development Company Ltd., operated by Execstar Aviation, Inc., collided with a seawall during the landing roll at a private airstrip located on Little Whale Cay, Bahamas. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 135 non-scheduled, international, passenger/cargo flight. The airplane was substantially damaged and the commercial-rated pilot and two passengers were not injured. The flight originated about 10 minutes earlier from Chub Cay, Bahamas. The pilot stated that after takeoff the flight proceeded to the destination airport where he overflew the runway and set up for landing to the southeast on the 2,000 foot-long runway. While on final approach with the flaps fully extended, he maintained 95 knots which was just below blue line, then slowed to 88 knots when the runway was assured. He landed within the first 1/3 on the wet runway and reported inadequate braking and the airplane was possibly hydroplaning. Recognizing that he was unable to clear an approximately 4-foot-tall seawall near the end of the runway, he applied aft elevator control input. He further stated he believes the main landing gear contacted the seawall causing them to structurally separate. The airplane descended and impacted the water where he and the passengers exited the airplane using the emergency window and walked to the beach.

Crash of an Embraer EMB-820C Navajo in Belo Horizonte: 4 killed

Date & Time: Jun 11, 2003 at 1600 LT
Registration:
PT-EHH
Survivors:
No
Schedule:
Belo Horizonte – Juiz de Fora
MSN:
820-044
YOM:
1977
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
180
Copilot / Total flying hours:
150
Circumstances:
The twin engine aircraft departed Belo Horizonte-Pampulha Airport at 1522LT on a taxi flight to Juiz de Fora, carrying two pilots, two passengers and a load of valuables. While cruising about 35 nm south of Belo Horizonte, the crew encountered technical problems with the engines and elected to return for an emergency landing. On approach to runway 13, the aircraft was too high and the crew was cleared to make a 360 turn to reduce his altitude. Doing so and after he completed 270° of this turn, the aircraft entered an uncontrolled descent and crashed 2 km short of runway, bursting into flames. The aircraft was totally destroyed by impact forces and a post crash fire and all four occupants were killed.
Probable cause:
The right engine suffered a oil leak in flight following the failure of a hose due to poor maintenance. The following contributing factors were identified:
- Both pilots did not have sufficient experience nor training on this type of aircraft,
- The copilot was flying for this operator for the first time,
- The operator was unable to provide any maintenance documentation nor crew training documentation to investigators,
- Both engines were running at impact but with limited power,
- The right propeller was feathered at impact.
Final Report:

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.