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 PZL-Mielec AN-2P in Lovozero

Date & Time: Jun 4, 2002 at 1340 LT
Type of aircraft:
Operator:
Registration:
RA-07748
Flight Phase:
Survivors:
Yes
Schedule:
Lovozero – Murmansk
MSN:
1G159-23
YOM:
1974
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Just after liftoff from Lovozero Airstrip, while climbing to a height of 15-20 metres, the engine lost power and white smoke escaped from the bottom of the engine. The aircraft lost height, struck an 8 metres tall tree located 191 metres past the runway end then crashed in a wooded area 58 metres further. All 12 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Engine failure due to poor maintenance. Deficiencies were reported during investigations regarding the operator's maintenance procedures. The documentation related to aircraft maintenance was incomplete. Also, several mechanics and engineers working on the AN-2 fleet were not qualified and authorised to do so.

Crash of a Boeing 747-209B off Magong: 225 killed

Date & Time: May 25, 2002 at 1529 LT
Type of aircraft:
Operator:
Registration:
B-18255
Flight Phase:
Survivors:
No
Schedule:
Taipei - Hong Kong
MSN:
21843
YOM:
1979
Flight number:
CI1611
Country:
Region:
Crew on board:
19
Crew fatalities:
Pax on board:
206
Pax fatalities:
Other fatalities:
Total fatalities:
225
Captain / Total flying hours:
10148
Captain / Total hours on type:
4732.00
Copilot / Total flying hours:
10173
Copilot / Total hours on type:
5831
Aircraft flight hours:
64810
Aircraft flight cycles:
21398
Circumstances:
On May 25, 2002, China Airlines (CAL) CI611, a Boeing 747-200, Republic of China (ROC) registration B-18255, was a regularly scheduled flight from Chiang Kai Shek International Airport (CKS), Taoyuan, Taiwan, ROC to Chek Lap Kok International Airport, Hong Kong. Flight CI611 was operating in accordance with ROC Civil Aviation Administration (CAA) regulations. The captain (Crew Member-1, CM-1) reported for duty at 1305 , at the CAL CKS Airport Dispatch Office and was briefed by the duty dispatcher for about 20 minutes, including Notices to Airmen (NOTAM) regarding the TPE Flight Information Region (FIR). The first officer (Crew Member-2, CM-2) and flight engineer (Crew Member-3, CM-3) reported for duty at CAL Reporting Center, Taipei, and arrived at CKS Airport about 1330. The aircraft was prepared for departure with two pilots, one flight engineer, 16 cabin crew members, and 206 passengers aboard. The crew of CI611 requested taxi clearance at 1457:06. At 1507:10, the flight was cleared for takeoff on Runway 06 at CKS. The takeoff and initial climb were normal. The flight contacted Taipei Approach at 1508:53, and at 1510:34, Taipei Approach instructed CI611 to fly direct to CHALI. At 1512:12, CM-3 contacted China Airlines Operations with the time off-blocks, time airborne, and estimated time of arrival at Chek Lap Kok airport. At 1516:24, the Taipei Area Control Center controller instructed CI611 to continue its climb to flight level 350, and to maintain that altitude while flying from CHALI direct to KADLO4. The acknowledgment of this transmission, at 1516:31, was the last radio transmission received from the aircraft. Radar contact with CI611 was lost by Taipei Area Control at 1528:03. An immediate search and rescue operation was initiated. At 1800, floating wreckage was sighted on the sea in the area 23 nautical miles northeast of Makung, Penghu Islands. The aircraft was totally destroyed and all 225 occupants were killed.
Probable cause:
Findings related to probable causes:
1. Based on the recordings of CVR and FDR, radar data, the dado panel open-close positions, the wreckage distribution, and the wreckage examinations, the in-flight breakup of CI611, as it approached its cruising altitude, was highly likely due to the structural failure in the aft lower lobe section of the fuselage.
2. In February 7 1980, the accident aircraft suffered a tail strike occurrence in Hong Kong. The aircraft was ferried back to Taiwan on the same day un-pressurized and a temporary repair was conducted the day after. A permanent repair was conducted on May 23 through 26, 1980.
3. The permanent repair of the tail strike was not accomplished in accordance with the Boeing SRM, in that the area of damaged skin in Section 46 was not removed (trimmed) and the repair doubler did not extend sufficiently beyond the entire damaged area to restore the structural strength.
4. Evidence of fatigue damage was found in the lower aft fuselage centered about STA 2100, between stringers S-48L and S-49L, under the repair doubler near its edge and outside the outer row of securing rivets. Multiple Site Damage (MSD), including a 15.1-inch through thickness main fatigue crack and some small fatigue cracks were confirmed. The 15.1-inch crack and most of the MSD cracks initiated from the scratching damage associated with the 1980 tail strike incident.
5. Residual strength analysis indicated that the main fatigue crack in combination with the Multiple Site Damage (MSD) were of sufficient magnitude and distribution to facilitate the local linking of the fatigue cracks so as to produce a continuous crack within a two-bay region (40 inches). Analysis further indicated that during the application of normal operational loads the residual strength of the fuselage would be compromised with a continuous crack of 58 inches or longer length. Although the ASC could not determine the length of cracking prior to the accident flight, the ASC believes that the extent of hoop-wise fretting marks found on the doubler, and the regularly spaced marks and deformed cladding found on the fracture surface suggest that a continuous crack of at least 71 inches in length, a crack length considered long enough to cause structural separation of the fuselage, was present before the in-flight breakup of the aircraft.
6. Maintenance inspection of B-18255 did not detect the ineffective 1980 structural repair and the fatigue cracks that were developing under the repair doubler. However, the time that the fatigue cracks propagated through the skin thickness could not be determined.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 near Nabire: 6 killed

Date & Time: May 25, 2002 at 0700 LT
Operator:
Registration:
PK-YPZ
Flight Phase:
Survivors:
No
Site:
Schedule:
Nabire – Enarotali
MSN:
458
YOM:
1975
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
While cruising in poor weather conditions at an altitude of 7,800 feet, the twin engine aircraft struck the slope of a mountain located about 50 km from Nabire. The aircraft was destroyed and all six occupants were killed. At the time of the accident, the visibility was poor due to heavy rain falls and the mountain struck by the aircraft was shrouded in mist.
Probable cause:
Controlled flight into terrain.

Crash of a McDonnell Douglas MD-82 off Dalian: 112 killed

Date & Time: May 7, 2002 at 2132 LT
Type of aircraft:
Operator:
Registration:
B-2138
Survivors:
No
Schedule:
Beijing - Dalian
MSN:
49522
YOM:
1990
Flight number:
CJ6136
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
103
Pax fatalities:
Other fatalities:
Total fatalities:
112
Aircraft flight hours:
26000
Aircraft flight cycles:
16000
Circumstances:
Following an uneventful flight from Beijing, the crew started the descent to Dalian Airport. While flying over the east side of the Korean Gulf, the crew contacted ATC and declared an emergency, reporting fire on board and smoke spreading in the cabin. Shortly later, the aircraft entered an uncontrolled descent and crashed in the sea about 20 km from the airport. The aircraft disintegrated on impact and all 112 occupants were killed. The CVR was found on May 13 and FDR on May 18.
Probable cause:
It was determined that the in-flight fire was the consequence of an act of sabotage. A passenger contracted seven life insurances from different companies for a total amount of 170,000 US$ and was able to board at Beijing-Capital Airport with a bottle filled with gasoline that he ignited during flight.

Crash of a Boeing 737-566 in Tunis: 14 killed

Date & Time: May 7, 2002 at 1518 LT
Type of aircraft:
Operator:
Registration:
SU-GBI
Survivors:
Yes
Schedule:
Cairo - Tunis
MSN:
25307
YOM:
1991
Flight number:
MS843
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
4509
Captain / Total hours on type:
1549.00
Copilot / Total flying hours:
880
Copilot / Total hours on type:
639
Aircraft flight hours:
26082
Aircraft flight cycles:
15686
Circumstances:
The aircraft departed Cairo-Intl Airport at 1140LT on a regular schedule flight to Tunis-Carthage Airport with 56 passengers and six crew members on board. It entered the Tunis FIR at 1450LT, under control of the Tunis Regional CCR. After being transferred to the approach control at 1500LT, the crew was cleared for a VOR/DME approach to runway 11. On approach at 3,000 feet, the crew was informed he was number one for landing. The crew informed ATC that he departed 3,000 feet for 2,100 feet at 12 NM and wa later cleared to land. Wind was from 130 at 30 knots. At 1516LT, on final, the crew was transferred from the approach control to the tower and received a second clearance to land. In limited visibility, the aircraft struck a fence located on the top of a mountain and crashed in hilly terrain 6,6 km from the runway 11 threshold. Three crew members and 11 passengers were killed while 48 other people were injured. On board were 33 Egyptians including the six crew members, 16 Tunisians, three Algerians, three Jordans, two Chinese, two British, one Libyan, one Saudi and one Palestinian.
Probable cause:
The accident was due to the crew's failure to perform and control the final approach. This was materialized by the failure to respect the approach fix associated with the decision to start the final approach prematurely.
The following contributing factors were identified:
- The poor weather conditions that prevailed at the time of the accident, particularly the limited visibility,
- The shortcomings noted in the training of both pilots, particularly those relating to conventional VOR/DME approaches,
- The relative weakness of the flight experience of both crew members on the type of aircraft operated.
Final Report:

Crash of a BAc 111-525FT in Kano: 149 killed

Date & Time: May 4, 2002 at 1335 LT
Type of aircraft:
Operator:
Registration:
5N-ESF
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Jos - Kano - Lagos
MSN:
266
YOM:
1980
Flight number:
EXW4226
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
71
Pax fatalities:
Other fatalities:
Total fatalities:
85
Circumstances:
The aircraft was completing a regular schedule flight from Jos to Lagos with an intermediate stop in Kano. Weather conditions were good but the OAT at the time of the accident was +42° C. Due to construction works (retreatment of the asphalt surface), the longest runway 24/06 was closed to traffic so the crew was departing from runway 23 at Kano-Mallam Aminu Kano Airport which is 2,600 metres long. Due to high temperature and reduced performances, the aircraft used the entire runway length, overran and rolled on a grassy area for few dozen metres before lifting off. During initial climb, the aircraft encountered difficulties to gain sufficient height and to follow a positive rate of climb when it collided with obstacles and crashed in the district of Gwammaja located about 2 km past the end of runway 23. The aircraft was totally destroyed by impact forces and a post crash fire as well a several buildings, among them a school and a mosque. Among the 77 people on board the aircraft, six survived (five passengers and one stewardess). All 71 other occupants were killed as well as 78 people on the ground. More than 70 other people on the ground were injured, some seriously. It was later reported that the aircraft was out of service for 52 days due to engine problems. Nevertheless, both engines were changed few days prior to the accident and accumulated 10 hours of flight since.

Crash of a Boeing 767-2J6ER in Busan: 129 killed

Date & Time: Apr 15, 2002 at 1121 LT
Type of aircraft:
Operator:
Registration:
B-2552
Survivors:
Yes
Schedule:
Beijing - Busan
MSN:
23308
YOM:
1985
Flight number:
CA129
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
155
Pax fatalities:
Other fatalities:
Total fatalities:
129
Captain / Total flying hours:
6497
Captain / Total hours on type:
6287.00
Copilot / Total flying hours:
5295
Copilot / Total hours on type:
1215
Aircraft flight hours:
39541
Aircraft flight cycles:
14308
Circumstances:
On April 15, 2002, about 11:21:17, Air China flight 129, a Boeing 767-200ER, operated by Air China International (Air China hereinafter), en route from Beijing, China to Busan, Korea, crashed during a circling approach, on Mt. Dotdae located 4.6 km north of runway 18R threshold at Busan/Gimhae International Airport (Gimhae airport hereinafter), at an elevation of 204 meters. The flight was a regularly scheduled international passenger service flight operating under instrument flight rules (IFR) within Korean airspace, according to the provisions of the Korean Aviation Act and Convention on International Civil Aviation. One captain, one first officer and one second officer, eight flight attendants, and 155 passengers were on board at the time of the accident. The aircraft was completely destroyed by impact forces and a post crash fire. Of the 166 persons on board, 37 persons including the captain and two flight attendants survived, while the remaining 129 occupants including two copilots were killed.
Probable cause:
3.1 Findings Related to Probable Causes:
1. The flight crew of flight 129 performed the circling approach, not being aware of the weather minima of widebody aircraft (B767-200) for landing, and in the approach briefing, did not include the missed approach, etc., among the items specified in Air China’s operations and training manuals.
2. The flight crew exercised poor crew resource management and lost situational awareness during the circling approach to runway 18R, which led them to fly outside of the circling approach area, delaying the base turn, contrary to the captain’s intention to make a timely base turn.
3. The flight crew did not execute a missed approach when they lost sight of the runway during the circling approach to runway 18R, which led them to strike high terrain (mountain) near the airport.
4. When the first officer advised the captain to execute a missed approach about 5 seconds before impact, the captain did not react, nor did the first officer initiate the missed approach himself.
Final Report:

Crash of a Harbin Yunsunji Y-12 II in Sam Neua

Date & Time: Feb 14, 2002 at 1200 LT
Type of aircraft:
Operator:
Registration:
RDPL-34118
Flight Phase:
Survivors:
Yes
Schedule:
Sam Neua - Vientiane
MSN:
0043
YOM:
1991
Flight number:
QV702
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Just after liftoff, while climbing to a height of about two metres, the twin engine aircraft encountered downdraft. It struck the runway surface, went out of control and veered off runway. It then collided with a fence and came to rest on a road located 17 metres below. All 15 occupants evacuated safely while the aircraft was damaged beyond repair. At the time of the accident, the wind was blowing at 8 knots but apparently changed rapidly and became stronger shortly after rotation.

Crash of a Tupolev TU-154M near Khorramabad: 119 killed

Date & Time: Feb 12, 2002 at 0755 LT
Type of aircraft:
Operator:
Registration:
EP-MBS
Survivors:
No
Site:
Schedule:
Tehran - Khorramabad
MSN:
91A871
YOM:
1991
Flight number:
IRB956
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
107
Pax fatalities:
Other fatalities:
Total fatalities:
119
Aircraft flight hours:
12701
Aircraft flight cycles:
5516
Circumstances:
Following an uneventful flight from Tehran, the crew started the descent to Khorramabad Airport runway 11 in bad weather conditions. In poor visibility, the crew failed to realize he was off course when the aircraft struck the slope of a mountain located few km northeast from the city of Sarab-e Dowreh, about 25 km northwest from the runway 11 threshold. The wreckage was found few hours later on a snow covered rock wall. The aircraft disintegrated on impact and all 119 occupants were killed, among them four Spanish citizens.
Probable cause:
Controlled flight into terrain after the crew failed to follow the approach procedures and the company SOP's. This caused the aircraft to deviate from the approach path by 3 nm to the north when it struck the mountain that was shrouded in clouds. The lack of visibility due to poor weather conditions was a contributing factor.