Crash of an Antonov AN-24RV in Yakutsk

Date & Time: Jul 13, 2002 at 1418 LT
Type of aircraft:
Operator:
Registration:
RA-46670
Flight Type:
Survivors:
Yes
Schedule:
Yakutsk - Yakutsk
MSN:
47309601
YOM:
1974
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Antonov departed Yakutsk on a crew training flight. Two approach and landings were carried out using flap settings of 38 and 15 degrees. During the third approach the captain called for lowering of the landing gear. The flight engineer moved the landing gear handle from neutral into the "retract" position. He did not check for three greens so failed to notice his mistake. Then the captain requested the flaps to be selected at 10 degrees. The Antonov turned to finals, but the crew did not carry out the final approach checks and continued after having obtained landing clearance. Fourteen seconds before touchdown an air traffic controller informed the crew that they should go around because the landing gear was not down. The captain did not hear this because at that moment height and speed were called out by the flight engineer. Five seconds later the controller repeated his warning. One of the crew members heard the call and noticed three reds on the instrument panel. He informed that captain about this, but it was already too late. The captain added takeoff power, but within three seconds the tail struck the runway. The airplane skidded about 1000 metres before coming to rest.
Probable cause:
The accident was caused by the combination of the following factors:
- The erroneous actions of the flight engineer when trying to lower the landing gear,
- Failure of the flight crew to conduct the necessary (final approach) checks,
- The failure by the crew to check and respond to landing gear warning indications,
- The execution of a flight with an incomplete composition of crew, causing additional workload on the flight engineer during the approach (height and speed call outs),
- Late commands to go around by the air traffic controller,
- On the Yak-40 the landing gear handle moves to the opposite direction for retraction and lowering compared to the Antonov 24 (the flight mechanic had more, and recent, flight experience on the Yakovlev 40 jet),
- The large workload and fatigue of the crew during the recent six days before the incident.

Crash of a Saab 2000 in Werneuchen

Date & Time: Jul 10, 2002 at 2042 LT
Type of aircraft:
Operator:
Registration:
HB-IZY
Survivors:
Yes
Schedule:
Basel - Hamburg
MSN:
2000-047
YOM:
1997
Flight number:
LX850
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2600
Captain / Total hours on type:
2350.00
Copilot / Total flying hours:
1940
Copilot / Total hours on type:
1732
Aircraft flight hours:
12303
Aircraft flight cycles:
12069
Circumstances:
The twin engine aircraft departed Basel-EuroAirport on a flight to Hamburg with 16 passengers and four crew members on board. While descending to Hamburg, weather conditions deteriorated rapidly and due to thunderstorm activity with heavy rain falls and strong winds, the crew was unable to land at Hamburg-Fuhlsbüttel Airport and decided to divert to Bremen. Unfortunately, weather conditions were so poor that the crew was unable to land in Bremen, Hanover and Berlin-Tegel Airport as well. Due to low fuel reserve, the crew informed ATC about his situation and was vectored to Werneuchen, a former Soviet military airfield some 60 km northeast of Berlin. Werneuchen's unlighted runway has a length of 2,400 metres but has no approach aids. ATC warned the crew about the presence of a one metre high earth embankment across the runway, some 900 metres past the runway threshold which was there to avoid illegal car races. The remaining runway was still used for general aviation. Due to limited visibility caused by poor weather conditions, the crew was unable to see and avoid the earth embankment. After landing, the aircraft impacted the earth embankment, causing the undercarriage to be torn off. The aircraft slid on its belly for few dozen metres before coming to rest in the middle of the runway. All 20 occupants evacuated the cabin, among them two were slightly injured. The aircraft was damaged beyond repair.
Probable cause:
The following findings were identified:
- Dimension and intensity of the storm front and dynamics of the weather conditions,
- Inadequate use of resources in decision-making during the flight (proactive),
- Loss of alternative landing facilities at increasing time pressure (reactive),
- Landing of the aircraft outside the operating area of an aerodrome,
- Collision with the embankment due to the non-detection of an obstacle.
Systemic causes:
- Inadequate information on weather conditions and development before and during the flight,
- Inadequate information on the Werneuchen Special Airfield due to an ambiguous map display as well as misleading or lack of communication,
- Inadequate labeling/marking of the operational and non-operational areas of the airport.
Final Report:

Crash of a Boeing 707-123B in Bangui: 28 killed

Date & Time: Jul 4, 2002 at 1115 LT
Type of aircraft:
Registration:
9XR-IS
Flight Type:
Survivors:
Yes
Site:
Schedule:
N'Djamena - Brazzaville
MSN:
19335
YOM:
1967
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
28
Circumstances:
The aircraft departed N'Djamena Airport on a cargo flight to Brazzaville, carrying 21 passengers, nine crew members and a load of onions and garlic. Few minutes after takeoff, the crew reported technical problems with the undercarriage and was cleared to divert to Bangui Airport. The crew completed a holding circuit over Bangui to consume fuel then later started the descent to the airport. On final approach to runway 35, all four engines stopped simultaneously due to fuel exhaustion. The aircraft stalled and crashed in a residential area located 4 km short of runway. A crew member and one passenger were injured while 28 other people were killed. There were no casualties on the ground.
Probable cause:
The crew reported that the undercarriage could not be raised. Loss of control on final approach after all four engines stopped due to a fuel exhaustion.

Crash of a Boeing 767-281 in Shimoji-shima

Date & Time: Jun 26, 2002 at 1254 LT
Type of aircraft:
Operator:
Registration:
JA8254
Flight Type:
Survivors:
Yes
Schedule:
Shimoji-shima - Shimoji-shima
MSN:
23433
YOM:
1987
Flight number:
NH8254
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10375
Captain / Total hours on type:
6654.00
Copilot / Total flying hours:
259
Copilot / Total hours on type:
5
Aircraft flight hours:
35347
Circumstances:
On June 26, 2002, a Boeing 767-200 of All Nippon Airways, registration JA8254, took off from Shimoji-Shima Airport at around 11:32 on a flight for takeoff and landing training. The flight plan of the aircraft submitted to the Shimoji-Shima Airport Office of the Japan Civil Aviation Bureau (CAB) was as follows: FLIGHT RULES: VFR, AERODROME of DEPARTURE: Shimoji-Shima Airport, TIME: 11:20, CRUISING SPEED: 250kt, LEVEL: VFR, ROUTE: Traffic Pattern, DESTINATION AERODROME: Shimoji-Shima Airport, FLIGHT PURPOSE: Training Flight, TOTAL EET: 1 hour 40 minutes, ENDURANCE: 6 hrs 32 minutes, PERSONS ON BOARD: 3. The three persons on board were in the cockpit at the time of the accident: A pilot undergoing training for promotion to First Officer (Trainee Pilot-A) occupying the left pilot’s seat, the Captain acting as instructor occupying the right pilot’s seat, and another pilot undergoing training for promotion to First Officer (Trainee Pilot-B) occupying the left observer’s seat. First, Trainee Pilot-B made seven landings on runway 17 from the left pilot’s seat, including two landings with one engine simulated inoperative, and a go-around with both engines operative. He then changed places with Trainee Pilot-A. At around that time, the wind direction changed from the south to the west, and the aerodrome control tower instructed a change to runway 35. Trainee Pilot-A then made two landings on runway 35 with both engines operative, and training then switched to landing with one engine simulated inoperative. The first landing was made with the left engine simulated inoperative. After that, during a landing with the right engine simulated inoperative, the touchdown was late and Trainee Pilot-A attempted to go-around with go-around thrust on the left engine only. A few seconds later the instructor increased power on the right engine to go-around thrust, but at that time even though the left engine thrust had started to increase the right engine was still at minimum idle thrust. As a result, a thrust imbalance occurred between the left and right engines while right rudder was
being applied, and the aircraft rolled and yawed to the right (East). Although Trainee Pilot-A and the instructor attempted to correct the attitude changes, the aircraft veered off the runway into a grass field on east side of the runway and came to a stop around 1,990m from the point it had first touched down. The accident occurred at runway 35 of Shimoji-Shima Airport at around 12:54.
Probable cause:
It is estimated that the accident was caused as follows:
The aircraft was being operated on a training flight at Shimoji-Shima Airport, and was making a one-engine-out touch-and-go landing with the right engine simulated inoperative. The touchdown was late and beyond the normal aim point, and on the direction of the instructor, the trainee pilot attempted to go around on only the left engine. However, the trainee mishandled the aircraft, and then, seeing the instructor advance the right engine’s thrust lever, he applied right rudder pedal mechanically. This coincided with an increase in the rotation speed of the left engine, and the aircraft’s attitude suddenly changed towards the right. Because the trainee pilot could not fully correct this and the instructor was late in taking over control, the aircraft veered off the east side of the runway into a grass area and was damaged. Moreover, it is estimated that the following causal factors contributed to the accident:
1) The instructor did not take over when he directed the trainee to go around, or at an earlier stage, because he thought to allow the trainee pilot to handle the aircraft as much as possible, and because he did not sufficiently recognize that a go-around with one-engine simulated inoperative is a difficult maneuver for an inexperienced pilot.
2) Regarding the instructor’s intent to allow the trainee pilot to handle the aircraft as much as possible, the company’s instructional guidelines contained statements meaning that a judgment to go around should be made by the trainee pilot, and that during simulated one-engine-out touch-and-go training landings, the go-around after landing should continue with one engine simulated inoperative.
3) Regarding the instructor’s insufficient recognition of the difficulty of a go-around with one engine simulated inoperative for an inexperienced pilot, the instructor had not been trained to deal with the situation encountered in the accident, and the company’s regulations and manuals did not describe considerations on the difficulty of executing a go-around with one-engine simulated inoperative for an inexperienced pilot or on the effects of the wind on such maneuvers.
4) Regarding the delay in the instructor taking over control of the aircraft, the instructor was not following with his hands on the control wheel and was not in a position to take over immediately if necessary, and when the instructor had changed from being a simulator instructor to a flight instructor, he had not received sufficient training on cautionary matters regarding training in actual aircraft.
Final Report:

Crash of a Douglas DC-9-14 in Neiva

Date & Time: Jun 14, 2002 at 1815 LT
Type of aircraft:
Operator:
Registration:
HK-3859X
Survivors:
Yes
Schedule:
Bogotá – Florencia – Neiva
MSN:
45843
YOM:
1966
Flight number:
RS8883
Location:
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
65
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5590
Captain / Total hours on type:
442.00
Copilot / Total flying hours:
804
Copilot / Total hours on type:
461
Aircraft flight hours:
73906
Circumstances:
Following an uneventful flight from Florencia, the crew was cleared to descend to Neiva-Benito Salas Airport. On approach, the aircraft was unstable and after the GPWS alarm sounded, the captain increased power and gained altitude, causing the aircraft to climb over the glide. The approach was continued and the airplane passed over the threshold at a height of 140 feet and eventually landed 1,700 feet past the runway threshold at intersection Bravo (the runway is 5,249 feet long). After touchdown, the crew started the braking procedure but two tyres burst and the aircraft was unable to stop within the remaining distance. It overran and came to rest in a grassy area. All 71 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The energy accumulated in the set of tires deflated the tire n°2, reducing the braking effectiveness by 50% due to the loss of the antiskid of that set in the same proportion, and subsequently the loss of 100% of the effectiveness of braking when tires n°3 and 4 burst successively, causing the aircraft to exceed the remaining runway length leading to the accident situation.
The following contributing factors were identified:
- The increase in speed of the VRF by the crew that increased the landing length,
- An unstabilized approach completed by the the crew,
- The pressure exerted on the crew due to the public order situation in the city of Florence for the purpose of a possible overnight stay of the aircraft and consequently the crew.
Final Report:

Crash of a Cessna 421C Golden Eagle III off Westerland

Date & Time: Jun 12, 2002 at 1113 LT
Operator:
Registration:
D-IJJJ
Flight Type:
Survivors:
Yes
Schedule:
Hamburg - Westerland
MSN:
421C-1012
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
370
Captain / Total hours on type:
24.00
Aircraft flight hours:
2883
Circumstances:
The pilot, sole on board, was completing a flight from Hamburg to Westerland. At a distance of 30 km southeast from Westerland-Sylt Airport, at an altitude of 1,300 feet, the pilot was cleared for an approach to runway 24. Few seconds later, both engines lost power. The pilot declared an emergency and was cleared for a straight-in approach to runway 33. Due to the situation, the pilot attempted to ditch the aircraft two km offshore. Rescue teams arrived on site about 45 minutes later and the pilot was rescued while the aircraft sank. The pilot added 250 litres of fuel at Hamburg Airport and a total of about 400 litres were found in all tanks after the wreckage was recovered, dismissing the possibility of a fuel exhaustion. Traces of corrosion were found on several engine parts.

Crash of a Fokker F27 Friendship 600 in Khartoum

Date & Time: Jun 11, 2002 at 1830 LT
Type of aircraft:
Operator:
Registration:
ST-SSD
Flight Type:
Survivors:
Yes
Schedule:
Khartoum - Khartoum
MSN:
10563
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
19822
Aircraft flight cycles:
19349
Circumstances:
The crew was completing a local training flight at Khartoum-Haj Yusuf Airport. Following several touch-and-goes completed successfully on runway 18, the crew landed the airplane and elected to takeoff when the captain encountered difficulties to raise the flaps from 40° to 16,5°. In such conditions, he decided to reject the takeoff procedure and initiated an emergency braking manoeuvre. The aircraft skidded on runway, overran and lost its right main gear before coming to rest against the ILS antenna for runway 36. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Piper PA-31-350 Navajo Chieftain in Winnipeg: 1 killed

Date & Time: Jun 11, 2002 at 0920 LT
Operator:
Registration:
C-GPOW
Survivors:
Yes
Site:
Schedule:
Gunisao Lake - Winnipeg
MSN:
31-7305093
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3000
Circumstances:
The aircraft was on an instrument flight rules flight from Gunisao Lake, Manitoba, to Winnipeg. One pilot and six passengers were on board. At 0913 central daylight time, KEE208 began an instrument landing system approach to Runway 13 at Winnipeg International Airport. The captain flew the approach at a higher-than-normal approach airspeed and well above the glide path. When the aircraft broke out of the cloud layer, it was not in position to land safely on the remaining runway. The captain executed a missed approach at 0916 and, after switching to the approach frequency from tower frequency, requested an expedited return to the airport. The approach controller issued instructions for a turn back to the airport. Almost immediately, at 0918, the captain declared a 'Mayday' for an engine failure. Less than 20 seconds later the captain transmitted that the aircraft had experienced a double engine failure. The aircraft crashed at a major traffic intersection at 0920, striking traffic signals and several vehicles. All seven of the aircraft passengers and several of the vehicle occupants were seriously injured; one passenger subsequently died of his injuries. The aircraft experienced extensive structural damage, with the wings and engines tearing off along the wreckage trail. There was a small post-crash fire in the right wing and engine area.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot did not correctly calculate the amount of fuel required to accomplish the flight from Winnipeg to Gunisao Lake and return, and did not ensure that the aircraft carried sufficient fuel for the flight.
2. The ILS approach was flown above the glideslope and beyond the missed approach point, which reduced the possibility of a safe landing at Winnipeg, and increased the risk of collision with terrain.
3. During the missed approach, the aircraft's engines lost power as a result of fuel exhaustion, and the pilot conducted a forced landing at a major city intersection.
4. The pilot did not ensure that the aircraft was equipped with an autopilot as specified by CARs.
Findings as to Risk:
1. The company did not provide an adequate level of supervision and allowed the flight to depart without an autopilot.
2. The company operations manual did not reflect current company procedures.
3. The company did not provide an adequate level of supervision and allowed the flight to depart without adequate fuel reserves. The company did not have a safety system in place to prevent a fuel exhaustion situation developing.
Other Findings:
1. The pilot did not advise air traffic control of his critical situation in a timely fashion.
Final Report:

Crash of a Dornier DO228-201 in Jaipur

Date & Time: Jun 9, 2002
Type of aircraft:
Operator:
Registration:
VT-EJN
Flight Type:
Survivors:
Yes
Schedule:
Jaipur - Jaipur
MSN:
8060
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Jaipur-Sanganer Airport. After touchdown, the twin engine aircraft skidded on runway, veered off runway and came to rest. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of an Avro 748 in George: 3 killed

Date & Time: Jun 1, 2002 at 0715 LT
Type of aircraft:
Operator:
Registration:
ZS-OJU
Flight Type:
Survivors:
No
Site:
Schedule:
Bloemfontein - George
MSN:
1782
YOM:
1980
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
20963
Captain / Total hours on type:
1819.00
Copilot / Total flying hours:
1099
Copilot / Total hours on type:
518
Aircraft flight hours:
14226
Aircraft flight cycles:
19789
Circumstances:
The aircraft was on a scheduled freight flight from Bloemfontein to George. Poor weather conditions prevailed over the George area and the pilots had to execute an instrument guided approach for the landing. The ground based Instrument Landing System (ILS) on Runway 29 at George Aerodrome was intermittently unreliable during the approach. The pilots decided to execute a missed approach. During the missed approach the pilots did not comply with the published missed approach procedure and with a combination of strong winds and possible erroneous heading indications they lost situational awareness. They flew the aircraft into a valley and crashed into the side of the mountains North-East of the George Aerodrome. The passenger was Hansie Cronje, a former South African cricket captain who had missed a South African Airlines flight.
Probable cause:
The crew deviated from the prescribed missed approach procedure during an attempted Instrument Landing System landing on Runway 29 at George in Instrument Meteorological Conditions and lost situational awareness aggravated by the presence of strong upper SouthWesterly winds. They allowed the aircraft to drift off course resulting in a controlled impact with terrain 6.7 nm North-East of the aerodrome. Contributing factors to the probable cause were the weather conditions, the intermittent unreliability of the Instrument Landing System, the serviceability of the directional gyro and the uncleared defects.
Final Report: