Crash of a BAc 111-208AL in Kaduna

Date & Time: Aug 29, 1992
Type of aircraft:
Operator:
Registration:
5N-HTA
Survivors:
Yes
MSN:
051
YOM:
1965
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
66
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Kaduna Airport, the crew encountered poor weather conditions with limited visibility due to heavy rain falls. On short final, the aircraft entered a rain squall and the pilots momentarily lost visual contact with the runway lights. The aircraft descended until it struck the runway surface and bounced. Out of control, it veered off runway to the right and came to rest. All 73 occupants were rescued (among them 13 were injured) while the aircraft was damaged beyond repair.
Probable cause:
The crew decided to continue the approach after he lost visual contact with the runway lights, and failed to initiate a go-around procedure. The lack of visibility due to heavy rain falls was considered as a contributing factor.

Crash of a Vickers 843 Viscount in Banjarmasin

Date & Time: Aug 28, 1992
Type of aircraft:
Operator:
Registration:
PK-IVX
Flight Phase:
Survivors:
Yes
MSN:
454
YOM:
1963
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
71
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from Banjarmasin-Syamsudin Noor Airport, while climbing, the crew declared an emergency after the engine n°2 caught fire. The crew shut down the engine, feathered its propeller and returned to the airport. A normal landing was completed and the crew stopped the aircraft on the main runway. All 77 occupants evacuated safely while the aircraft was destroyed by fire.
Probable cause:
Failure and fire on engine n°2 for unknown reasons.

Crash of a Tupolev TU-134A in Ivanovo: 84 killed

Date & Time: Aug 27, 1992 at 2244 LT
Type of aircraft:
Operator:
Registration:
CCCP-65058
Survivors:
No
Schedule:
Mineralnye Vody - Donetsk - Ivanovo
MSN:
49868
YOM:
1977
Flight number:
SU2808
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
77
Pax fatalities:
Other fatalities:
Total fatalities:
84
Aircraft flight hours:
26307
Aircraft flight cycles:
16388
Circumstances:
The aircraft departed Mineralnye Vody on a schedule service to Ivanovo with an intermediate stop in Donetsk. Following an uneventful flight, the crew initiated the descent to Ivanovo-Yuzhny Airport. The visibility was limited due to the night and poor weather conditions. On final approach, the aircraft was not properly aligned on the glide and the copilot and the navigator attempted to inform the captain about the deviation but without success. The captain continued the approach in a wrong configuration when, at a speed of 370 km/h and a rate of descent of 6 metres per second, the left wing struck a residential building. The aircraft entered a nose-down attitude and crashed 512 metres further, some 2,450 metres short of runway 29, bursting into flames. The aircraft was totally destroyed and all 84 occupants were killed.
Probable cause:
The accident was the consequence of a wrong approach configuration on part of the crew. The captain ignored several alerts from the copilot and the navigator and failed to initiate a go-around procedure despite the GPWS alarm sounded for about 10 seconds. The following contributing factors were reported:
- Loss of altitude control in adverse weather conditions following a premature descent,
- The crew failed to follow the published approach procedures, which resulted in the aircraft approaching the airport at an insufficient altitude and at an excessive speed,
- The 4th turn was completed too late at a distance less than calculated, which caused the aircraft to deviate from the approach path with a separation (deviation) of 1,900 metres to the right of the approach path at a distance of 8,600 metres from the runway threshold at an altitude of 500 metres,
- The captain decided to continue the approach while a landing was obviously impossible,
- A total interruption of interactions within the crew during the approach procedure, which brang the captain in a delicate situation without any assistance from the other members of the crew and causing a regular loss of the altitude control,
- The crew let the aircraft passing the admissible vertical speed during the final approach,
- Failure of the crew to initiate a go-around procedure while the Ground Proximity Warning System alarm sounded for about 10 seconds,
- Excessive corrective maneuvers on part of the captain which caused the aircraft to enter a roll angle greater than the permissible limits,
- The violation by the crew of the approach pattern was facilitated by the lack of assistance from ATC at Ivanovo Airport.

Crash of a De Havilland DHC-6 Twin Otter 300 near El Estrecho: 8 killed

Date & Time: Aug 27, 1992
Operator:
Registration:
OB-1153
Flight Phase:
Survivors:
Yes
Schedule:
Iquitos – El Estrecho
MSN:
316
YOM:
1971
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
En route from Iquitos to El Estrecho, the crew encountered engine problems and elected to make an emergency landing on the Río Algodón when the aircraft struck trees and crashed in a dense wooded area, about 22 km south of El Estrecho. Both pilots and six passengers were killed while 13 other occupants were injured.

Crash of a BAc 111-204AF in Sokoto

Date & Time: Aug 23, 1992
Type of aircraft:
Operator:
Registration:
5N-KBA
Survivors:
Yes
MSN:
179
YOM:
1968
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
53
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following a poor flight and approach planning, the crew landed at the old Sokoto Airport. After touchdown, the pilots realized their mistake and attempted to take off but eventually decided to initiate an emergency braking procedure due to the presence of high tension cables at the end of the runway. Unable to stop within the remaining distance, the aircraft overran, lost its undercarriage and slid for few dozen metres before coming to rest. All 57 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Poor flight and landing planning on part of the crew who completed the landing on the wrong airport. The following contributing factors were reported:
- Erroneous actions on part of the crew,
- Poor crew decisions,
- Poor crew coordination,
- Absence of crew cross checks,
- Lack of ATC assistance.

Crash of a Yakovlev Yak-42D in Nankin: 107 killed

Date & Time: Jul 31, 1992 at 1512 LT
Type of aircraft:
Operator:
Registration:
B-2755
Flight Phase:
Survivors:
Yes
Schedule:
Nankin - Xiamen
MSN:
21 16 644
YOM:
1992
Flight number:
GP7552
Location:
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
116
Pax fatalities:
Other fatalities:
Total fatalities:
107
Circumstances:
During the takeoff roll on runway 06, after passing decision speed, the crew started to rotate but the aircraft failed to respond. The crew aborted takeoff and initiated an emergency braking procedure. Unable to stop within the remaining distance, the aircraft overran and rolled for about 420 meters. At a speed of 210 km/h, it struck successively a 6,7 metres deep drainage ditch and a 2 metres high embankment before coming to rest, bursting into flames. 19 people including one crew member were injured while 107 other occupants were killed.
Probable cause:
It was determined that the crew did not prepare the flight according to published procedures and failed to follow the pre-takeoff checklist. As a result, the aircraft was unable to takeoff because the elevator trim was set in a landing configuration.

Crash of an Airbus A310-304 near Kathmandu: 113 killed

Date & Time: Jul 31, 1992 at 1245 LT
Type of aircraft:
Operator:
Registration:
HS-TID
Survivors:
No
Site:
Schedule:
Bangkok - Kathmandu
MSN:
438
YOM:
1987
Flight number:
TG311
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
99
Pax fatalities:
Other fatalities:
Total fatalities:
113
Circumstances:
Thai Airways Flight 311 was conducting the Sierra (VOR/DME) approach to runway 02 at Tribhuvan International Airport, in instrument weather conditions. A flap fault occurred while the flight was on the approach; this caused the crew to ask for clearance back to Calcutta, a decision that was in keeping with both Company and performance requirements, which necessitate the use of full flaps for the steep final approach. Shortly (21 seconds) after making this request, at a distance of approximately 12 nm from the Kathmandu VOR, the flap fault was rectified by retracting and then reselecting the flaps. The crew determined that it was not possible to continue the straight-in approach, due to the steep descent angles required and the position of the aircraft. The crew stated to the control tower that they wished to start their approach again and requested a left turn back to the Romeo fix, which is 41 nm south south-west (202 radial) of the Kathmandu VOR. The Controller, in the non-radar environment, responded by clearing the flight to make the Sierra approach, which starts at the 202 radial and 16 nautical miles from the VOR. The crew response to the clearance was to report that, at the moment, they couldn't land and to ask again for left turn back to Romeo to start their approach again. After further dialogue with the controller, which included requests for a left turn, the crew unilaterally initiated a right turn from the aircraft's 025° heading and commenced a climb from an altitude of 10,500 feet to FL180, when the flight was about 7 nm south of the Kathmandu VOR. The crew reported to the tower controller that the flight was climbing and the controller replied by instructing the crew to report at 16 nm for the Sierra approach. During the turn, there was more discussion between the tower controller and the flight, where it was established that the aircraft was to maintain an altitude of FL115 and was to 'proceed to Romeo' and contact the Area Control Center (ACC) controller. The flight, commencing a descent while in the turn, completed a 360° turn, momentarily rolling out on headings of 045° and 340°, and again proceeded toward the north on a heading of 025° magnetic. When the flight was about 5 nm south-west of the Kathmandu VOR, the crew contacted the ACC and stated that the aircraft was 'heading 025' and they wished to proceed to Romeo to start their approach again; adding they had 'technical problems concerned with the flight.' It was again established that the flight was to proceed to Romeo and the crew agreed to 'report over Romeo.' It was determined from the cockpit voice recorder that the crew was in the process of inserting 'Romeo' and other related navigational information in the Flight Management System, but were experiencing difficulties. The flight continued towards the north on a heading of 025° and then, at about 16 nm north, the heading was altered to the left to 005°. Slightly over one minute later, the Ground Proximity Warning System (GPWS) sounded the warning 'terrain, terrain' followed by 'whoop whoop pull-up'; the aural warning continued until impact approximately 16 seconds later. Engine thrust was increasing and 'Level Change' had been announced on the cockpit, just before the impact occurred at the 11,500-foot level of a 16,000-foot peak; the accident site was located on the 015 radial (north-north east) at 23.3 nm from the Kathmandu VOR. The aircraft was destroyed and all 113 occupants were killed.
Probable cause:
TG311 flight crew's management of the aircraft flight path wherein the flight proceeded in a northerly direction which was opposite to the cleared point Romeo to the South; ineffective radio communication between the area control centre and the TG311 flight crew which allowed the flight to continue in the wrong direction, in that the TG311 crew never provided the aircraft's VOR radial when stating DME and the controller never solicited this information and thus the aircraft's position was not transmitted at any time; and ineffective cockpit crew coordination by the TG311 crew in conducting flight navigation duties. Contributing factors were: the misleading depiction of Romeo on the operator's approach chart used by the flight crew; a flap fault, although corrected, required that the initial approach be discontinued; and radio communication difficulties between the TG311 crew and the air traffic controllers that stemmed from language difficulties and ineffective discussion of apparent unresolved problems.

Crash of a Lockheed L-1011-385-1 TriStar 1 in New York

Date & Time: Jul 30, 1992 at 1741 LT
Type of aircraft:
Operator:
Registration:
N11002
Flight Phase:
Survivors:
Yes
Schedule:
New York - San Francisco
MSN:
193B-1014
YOM:
1972
Flight number:
TW843
Crew on board:
12
Crew fatalities:
Pax on board:
280
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20149
Captain / Total hours on type:
2397.00
Copilot / Total flying hours:
15242
Copilot / Total hours on type:
2953
Aircraft flight hours:
49662
Aircraft flight cycles:
19659
Circumstances:
Immediately after liftoff the stick shaker activated, and the first officer, who was making the takeoff, said 'you got it.' The captain took control, closed the thrust levers, and landed. He applied full reverse thrust and maximum braking, and turned the airplane off the runway to avoid a barrier at the end. A system design deficiency permitted a malfunctioning aoa sensor to cause a false stall warning. The sensor had experienced 9 previous malfunctions, and was inspected and returned to service without a determination on the reason for the intermittent malfunction. The first officer had incorrectly perceived that the airplane was stalling and gave control to the captain without proper coordination of the transfer of control. All 292 occupants were rescued, among them 10 were injured, one seriously.
Probable cause:
Design deficiencies in the stall warning system that permitted a defect to go undetected, the failure of twa's maintenance program to correct a repetitive malfunction of the stall warning system, and inadequate crew coordination between the captain and first officer that resulted in their inappropriate response to a false stall warning.
Final Report:

Crash of a Vickers 816 Viscount in Ambon: 70 killed

Date & Time: Jul 24, 1992 at 1630 LT
Type of aircraft:
Operator:
Registration:
PK-RVU
Survivors:
No
Site:
Schedule:
Jakarta - Surabaya - Ujung Pandang - Ambon
MSN:
434
YOM:
1959
Flight number:
RI660
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
63
Pax fatalities:
Other fatalities:
Total fatalities:
70
Circumstances:
On approach to Ambon-Pattimura Airport, the crew encountered bad weather conditions with heavy rain falls. At an altitude of 2,300 feet, the four engine aircraft struck the slope of Mt Lalaboy located 14 km southwest of runway 04 threshold. The aircraft disintegrated on impact and all 70 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew was approaching the airport at an insufficient altitude, maybe following instrument misreading or malfunction.

Crash of a Beechcraft H18 in Cagayán de Oro

Date & Time: Jul 11, 1992
Type of aircraft:
Operator:
Registration:
RP-C1104
Flight Phase:
Survivors:
Yes
MSN:
BA-731
YOM:
1965
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff, while in initial climb, one of the engine failed. The aircraft lost height and crashed near the airport. All four occupants were injured.
Probable cause:
Engine failure after takeoff for unknown reasons.