Crash of a Tupolev TU-134B-3 in Phnom Penh: 65 killed

Date & Time: Sep 3, 1997 at 1400 LT
Type of aircraft:
Operator:
Registration:
VN-A120
Survivors:
Yes
Schedule:
Hô Chi Minh – Phnom Penh
MSN:
66360
YOM:
1984
Flight number:
VN815
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
60
Pax fatalities:
Other fatalities:
Total fatalities:
65
Aircraft flight hours:
11723
Aircraft flight cycles:
8209
Circumstances:
On approach to Phnom Penh-Pochentong Airport, the crew encountered poor weather conditions and limited visibility due to heavy rain falls. Unable to establish a visual contact with the runway, the captain initiated a go-around procedure. Few minutes later, on a second attempt to land, the captain continued the approach below the glide and passed the MDA. The flight engineer, the copilot and ATC as well warned the captain that his altitude was insufficient but he failed to correct the situation when the aircraft struck palms, stalled and crashed in a rice paddy field located 300 metres short of runway. A boy aged one was injured while 65 other occupants were killed.

Crash of a Boeing 727-251A in San Cristóbal

Date & Time: Aug 22, 1997 at 1438 LT
Type of aircraft:
Operator:
Registration:
HC-BVU
Survivors:
Yes
Schedule:
Guayaquil – San Cristóbal
MSN:
21322
YOM:
1977
Flight number:
EH800
Country:
Crew on board:
9
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Guayaquil to San Cristóbal, the crew encountered technical problems with the antiskid system. It was decided to perform a low approach to runway 16 to land on the first metres of the runway. On short final, the aircraft was too low, struck approach lights and landed 36 metres short of runway 16 threshold. On impact, the undercarriage were torn off and the aircraft skidded for about 700 metres before coming to rest. All 56 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Boeing 727-230A in Thessaloniki

Date & Time: Aug 12, 1997 at 1741 LT
Type of aircraft:
Operator:
Registration:
SX-CBI
Survivors:
Yes
Schedule:
Athens - Thessaloniki - Frankfurt
MSN:
20791
YOM:
1974
Flight number:
OA171
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
26
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Thessaloniki Airport was completed in poor weather conditions. The aircraft landed too far down the runway and after touchdown, the crew realized he could not stop the aircraft within the remaining distance so he decided to veer off runway to the right. While contacting soft ground, the undercarriage were torn off and the aircraft came to rest. All 35 occupants escaped uninjured and the aircraft was damaged beyond repair. At the time of the accident, the wind was from 360° at 18 knots gusting to 28 knots with thunderstorm activity, rain falls and a visibility of 5 km.
Probable cause:
The following findings were reported:
- Poor weather conditions,
- The runway surface was wet and the braking action was considered as moderate to low,
- The flying crew consisted of two highly experienced captains,
- The crew was under stress during the final approach due to poor weather conditions,
- Wrong approach configuration as the aircraft was too high on the glide,
- The crew failed to follow the approach checklist,
- The aircraft landed too far down the runway, about a third past its threshold, reducing the landing distance available,
- Lack of crew coordination,
- The crew failed to initiate a go-around procedure.

Crash of a Dornier DO228-212 in Matsu Nangan: 16 killed

Date & Time: Aug 10, 1997 at 0833 LT
Type of aircraft:
Operator:
Registration:
B-12256
Survivors:
No
Schedule:
Taipei - Matsu Nangan
MSN:
8220
YOM:
1993
Flight number:
VY7601
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
16
Circumstances:
On final approach to Matsu Nangan Airport, the twin engine aircraft struck the top of the Jade Hill located about one km short of runway and disintegrated on impact. A female passenger was seriously injured while 15 other occupants were killed. The only survivor died from his injuries few hours later. At the time of the accident, the visibility was reduced to six km in rain. It was reported that the crew was initiating a go-around procedure when the aircraft struck the hill. Few hours after the accident, a man in charge to transmit weather conditions to the crew committed suicide at the airport.

Crash of a Boeing 747-3B5 in Agana: 228 killed

Date & Time: Aug 6, 1997 at 0142 LT
Type of aircraft:
Operator:
Registration:
HL7468
Survivors:
Yes
Schedule:
Seoul - Agana
MSN:
22487
YOM:
1984
Flight number:
KE801
Country:
Region:
Crew on board:
17
Crew fatalities:
Pax on board:
237
Pax fatalities:
Other fatalities:
Total fatalities:
228
Captain / Total flying hours:
8932
Captain / Total hours on type:
1718.00
Copilot / Total flying hours:
4066
Copilot / Total hours on type:
1560
Aircraft flight hours:
50105
Aircraft flight cycles:
8552
Circumstances:
Korean Air Flight 801 was a regular flight from Seoul to Guam. The Boeing 747-300 departed the gate about 21:27 and was airborne about 21:53. The captain was pilot-flying. Upon arrival to the Guam area, the first officer made initial contact with the Guam Combined Center/Radar Approach Control (CERAP) controller about 01:03, when the airplane was level at 41,000 feet and about 240 nm northwest of the NIMITZ VOR/DME. The CERAP controller told flight 801 to expect to land on runway 06L. About 01:10, the controller instructed flight 801 to "...descend at your discretion maintain two thousand six hundred." The first officer responded, "...descend two thousand six hundred pilot discretion." The captain then began briefing the first officer and the flight engineer about the approach and landing at Guam: "I will give you a short briefing...ILS is one one zero three...NIMITZ VOR is one one five three, the course zero six three, since the visibility is six, when we are in the visual approach, as I said before, set the VOR on number two and maintain the VOR for the TOD [top of descent], I will add three miles from the VOR, and start descent when we're about one hundred fifty five miles out. I will add some more speed above the target speed. Well, everything else is all right. In case of go-around, since it is VFR, while staying visual and turning to the right...request a radar vector...if not, we have to go to FLAKE...since the localizer glideslope is out, MDA is five hundred sixty feet and HAT [height above touchdown] is three hundred four feet...." About 01:13 the captain said, "we better start descent;" shortly thereafter, the first officer advised the controller that flight 801 was "leaving four one zero for two thousand six hundred." During the descent it appeared that the weather at Guam was worsening. At 01:24 requested a deviation 10 miles to the left to avoid severe weather. At 01:31 the first officer reported to the CERAP controller that the airplane was clear of cumulonimbus clouds and requested "radar vectors for runway six left." The controller instructed the flight crew to fly a heading of 120°. After this transmission, the flight crew performed the approach checklist and verified the radio frequency for the ILS to runway 06L. About 01:38 the CERAP controller instructed flight 801 to "...turn left heading zero nine zero join localizer;" the first officer acknowledged this transmission. At that time, flight 801 was descending through 2,800 feet msl with the flaps extended 10° and the landing gear up. One minute later the controller stated, "Korean Air eight zero one cleared for ILS runway six left approach...glideslope unusable." The first officer responded, "Korean eight zero one roger...cleared ILS runway six left;" his response did not acknowledge that the glideslope was unusable. The flight engineer asked, "is the glideslope working? glideslope? yeh?" One second later, the captain responded, "yes, yes, it's working." About 01:40, an unidentified voice in the cockpit stated, "check the glideslope if working?" This statement was followed 1 second later by an unidentified voice in the cockpit asking, "why is it working?" The first officer responded, "not useable." The altitude alert system chime sounded and the airplane began to descend from an altitude of 2,640 feet msl at a point approximately 9 nm from the runway 06L threshold. About 01:40:22, an unidentified voice in the cockpit said, "glideslope is incorrect." As the airplane was descending through 2,400 feet msl, the first officer stated, "approaching fourteen hundred." About 4 seconds later, when the airplane was about 8 nm from the runway 06L threshold, the captain stated, "since today's glideslope condition is not good, we need to maintain one thousand four hundred forty. please set it." An unidentified voice in the cockpit then responded, "yes." About 01:40:42, the CERAP controller instructed flight 801 to contact the Agana control tower. The first officer contacted the Agana tower: "Korean air eight zero one intercept the localizer six left." The airplane was descending below 2,000 feet msl at a point 6.8 nm from the runway threshold (3.5 nm from the VOR). About 01:41:01, the Agana tower controller cleared flight 801 to land. About 01:41:14, as the airplane was descending through 1,800 feet msl, the first officer acknowledged the landing clearance, and the captain requested 30° of flaps. The first officer called for the landing checklist and at 01:41:33, the captain said, "look carefully" and "set five hundred sixty feet" (the published MDA). The first officer replied "set," the captain called for the landing checklist, and the flight engineer began reading the landing checklist. About 01:41:42, as the airplane descended through 1,400 feet msl, the ground proximity warning system (GPWS) sounded with the radio altitude callout "one thousand [feet]." One second later, the captain stated, "no flags gear and flaps," to which the flight engineer responded, "no flags gear and flaps." About 01:41:46, the captain asked, "isn't glideslope working?" The captain then stated, "wiper on." About 01:41:53, the first officer again called for the landing checklist, and the flight engineer resumed reading the checklist items. About 01:41:59, when the airplane was descending through 1,100 feet msl at a point about 4.6 nm from the runway 06L threshold (approximately 1.3 nm from the VOR), the first officer stated "not in sight?" One second later, the GPWS radio altitude callout sounded: "five hundred [feet]." About 01:42:14, as the airplane was descending through 840 feet msl and the flight crew was performing the landing checklist, the GPWS issued a "minimums minimums" annunciation followed by a "sink rate" alert about 3 seconds later. The first officer responded, "sink rate okay". At that time the airplane was descending 1,400 feet per minute. About 01:42:19, as the airplane descended through 730 feet msl, the flight engineer stated, "two hundred [feet]," and the first officer said, "let's make a missed approach." About one second later, the flight engineer stated, "not in sight," and the first officer said, "not in sight, missed approach." About 01:42:22, as the airplane descended through approximately 680 feet msl, the nose began to pitch up and the flight engineer stated, "go around." When the captain stated "go around" power was added and airspeed began to increase. As the airplane descended through 670 feet msl, the autopilot disconnect warning sounded. The GPWS radio altitude callouts continued: "one hundred...fifty...forty...thirty...twenty [feet]." About 01:42:26, the airplane impacted hilly terrain at Nimitz Hill, Guam, about 660 feet msl and about 3.3 nm from the runway 06L -threshold. It struck trees and slid through dense vegetation before coming to rest. A post-impact fire broke out. It was established a.o. that the software fix for the Minimum Safe Altitude Warning (MSAW) system at Agana Center Radar Approach Control (CERAP) had rendered the program useless. A software patch had been installed since there had been complaints of the high rate of false MSAW alarms at Guam. This made KAL801's descent below MDA go undetected at the Agana CERAP.
Probable cause:
The captain's failure to adequately brief and execute the nonprecision approach and the first officer's and flight engineer's failure to effectively monitor and cross-check the captain's execution of the approach. Contributing to these failures were the captain's fatigue and Korean Air's inadequate flight crew training. Contributing to the accident was the Federal Aviation Administration's intentional inhibition of the minimum safe altitude warning system and the agency's failure to adequately to manage the system.
Final Report:

Crash of a Boeing 737-242C in Douala

Date & Time: Aug 3, 1997 at 1748 LT
Type of aircraft:
Operator:
Registration:
TU-TAV
Flight Phase:
Survivors:
Yes
Schedule:
Douala – Bangui – N’Djamena
MSN:
19848
YOM:
1969
Flight number:
RK816
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
106
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll on runway 23 at Douala Airport, at a speed of 110 knots, the crew noted a loud bang and decided to abort. The crew initiated an emergency braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its undercarriage and both engines before coming to rest 130 metres further, bursting into flames. All 114 occupants were evacuated, among them 20 were slightly injured. The aircraft was destroyed.
Probable cause:
Rejected takeoff after a tyre burst on the left main gear.

Crash of an ATR42-512 in Florence: 1 killed

Date & Time: Jul 30, 1997 at 1110 LT
Type of aircraft:
Operator:
Registration:
F-GPYE
Survivors:
Yes
Schedule:
Nice - Florence
MSN:
492
YOM:
1996
Flight number:
FU701
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
10000
Copilot / Total flying hours:
10000
Circumstances:
The twin engine aircraft departed Nice-Côte d'Azur Airport on a regular schedule service to Florence, carrying 14 passengers and three crew members. On approach to Florence-Peretola Airport runway 23, the aircraft' speed was too high and after touchdown, it bounced several times and landed firmly 350 metres from the runway end. Unable to stop within the remaining distance, it overran, went through fences and eventually collided with an embankment and came to rest on the emergency lane of the motorway Florence - Pisa. The aircraft broke in two and the cockpit was destroyed on impact. All 15 people seating in the main cabin (14 passengers and the stewardess) were evacuated with minor injuries while both pilots were seriously injured. Two days later, one of them died from his injuries.
Probable cause:
The following findings were identified:
- Weather conditions were considered as good with light wind,
- The pilot acting as captain was flying on this route for the first time and this was also his first landing at Peretola Airport,
- Florence-Peretola Airport runway 23 is 1,650 metres long but has a displaced threshold, so the landing distance available is 1,030 metres only,
- The copilot was the pilot-in-command at the time of the accident. He was also a captain and could operate as an instructor,
- The approach configuration was incorrect since the aircraft's touchdown speed was 30 knots above the speed prescribed in the flight manuals,
- Failure of the crew to initiate a go-around procedure while the landing manoeuvre was obviously missed.

Crash of a BAc 111-203AE in Calabar: 1 killed

Date & Time: Jul 29, 1997
Type of aircraft:
Operator:
Registration:
5N-BAA
Survivors:
Yes
Schedule:
Lagos - Calabar
MSN:
041
YOM:
1965
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The approach to Calabar Airport runway 03 was completed in poor weather conditions with heavy rain falls, turbulences, clouds down to 240 metres and a visibility limited to 2,800 metres. On final, the aircraft was unstable and not properly aligned with the runway centerline. Upon touchdown, the left main gear landed on the grassy area to the left of the runway. The captain attempted to correct when the aircraft veered to the right back onto the runway and overran. It struck a ditch and came to rest 1,500 metres further, bursting into flames. A crew member was killed and 10 other occupants were injured.
Probable cause:
The following findings were reported:
- Poor weather conditions,
- Limited visibility and low ceiling,
- The aircraft was unstable on final approach and misaligned on runway 03,
- The aircraft landed at an excessive speed,
- The crew failed to initiate a go-around procedure,
- Poor planned approach.

Crash of a Cessna 207A Skywagon in Belize City: 1 killed

Date & Time: Jul 23, 1997 at 0724 LT
Operator:
Registration:
V3-HFD
Survivors:
No
Site:
Schedule:
San Pedro – Belize City-International – Belize City-Municipal
MSN:
207-0676
YOM:
1981
Flight number:
9N010
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1789
Captain / Total hours on type:
672.00
Aircraft flight hours:
11656
Circumstances:
The single engine aircraft landed at the Philip S. W. Goldson International Airport from San Pedro Airport, Ambergris Caye, with two passengers. The pilot remained in the aircraft on the apron while the two passengers disembarked. After receiving clearance from the Air Traffic Control Tower, V3-HFD, with no passengers, took off at 0720LT for the Belize City Municipal Airport. At 0722LT, the pilot reported by the Haulover Bridge and was instructed by ATC to change to frequency 122.8 MHz, which is the common broadcast frequency where pilots transmit their positions and intentions to each other. No further radio transmissions or distress calls were made to ATC after the pilot reported to Haulover Bridge. While approaching Belize City Municipal Airport at a very low altitude, the aircraft struck power cables and crashed onto a house located in the district Belama Phase 2, bursting into flames. The wreckage was found about 3 km southwest of runway 12 threshold. The pilot was killed and one people on the ground was injured. The aircraft was destroyed by impact forces and a post crash fire.
Probable cause:
There is no evidence which permits the investigation to determine with certainty the actual cause of the accident. It is considered a reasonable deduction that the probable cause of the accident was that the aircraft became uncontrollable after hitting high voltage transmission lines due to the aircraft being flown at a low altitude.
Final Report:

Crash of a Fokker F27 Friendship in Bandung: 28 killed

Date & Time: Jul 17, 1997 at 1155 LT
Type of aircraft:
Operator:
Registration:
PK-YPM
Survivors:
Yes
Site:
Schedule:
Bandung - Jakarta
MSN:
10415
YOM:
1969
Flight number:
TGN304
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
28
Circumstances:
The aircraft departed Bandung-Husein Sastranegara Airport on a regular schedule flight to Jakarta, carrying 45 passengers and 5 crew members. Shortly after takeoff, the captain informed ATC that the left engine lost power and elected to diver to the Bandung-Sulaiman AFB for an emergency landing. On final approach to runway 13, the crew was unable to maintain a safe altitude when the aircraft struck roofs and crashed. Twenty occupants were rescued while 28 others were killed, including all five crew members. All occupants were Indonesian citizens except for one passenger from Singapore.
Probable cause:
Failure of the left engine for unknown reasons.