Crash of a Cessna 208 Caravan I in El Rosal: 8 killed

Date & Time: Apr 29, 1994 at 1427 LT
Type of aircraft:
Registration:
HK-3479
Survivors:
Yes
Site:
Schedule:
Furatena – Quipama – Boyaca – Bogotá
MSN:
208-0143
YOM:
1989
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
While descending to Bogotá-El Dorado Airport, the single engine aircraft struck the slope of a mountain located near El Rosal, about 19 km northwest of the airport. A passenger was seriously injured while eight other occupants were killed. For unknown reasons, the pilot was completing the approach at an unsafe altitude.

Crash of an Airbus A300-622R in Nagoya: 264 killed

Date & Time: Apr 26, 1994 at 2015 LT
Type of aircraft:
Operator:
Registration:
B-1816
Survivors:
Yes
Schedule:
Taipei - Nagoya
MSN:
580
YOM:
1990
Flight number:
CI140
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
256
Pax fatalities:
Other fatalities:
Total fatalities:
264
Captain / Total flying hours:
8340
Captain / Total hours on type:
1350.00
Copilot / Total flying hours:
1624
Copilot / Total hours on type:
1033
Aircraft flight hours:
8550
Aircraft flight cycles:
3910
Circumstances:
China Airlines' Flight 140 (from Taipei International Airport to Nagoya Airport), B-1816, took off from Taipei International Airport at 0853 UTC (1753 JST) on April 26, 1994 (hereinafter all times shown are Coordinated Universal Time, unless otherwise specified), canying a total of 271 persons consisting of 2 flight crew members, 13 cabin crew members and 256 passengers (including 2 infants). The flight plan of the aircraft, which had been filed to the Taiwanese civil aviation authorities, Zhongzheng International Airport Office, was as follows:
Flight rule: IFR, Aerodrome of departure: Taipei International Airport, Destination Aerodrome: Nagoya Airport, Cruising speed: 465 knots, Level: FL330, Route: A1 SUCJAKAL-KE-SIV-XMC, total estimated enroute time: 2 hours and 18 minutes, Alternate Aerodrome: Tokyo International Airport.
DFDR shows that the aircraft reached FL330 about 0914 and continued its course toward Nagoya Airport in accordance with its flight plan.
DFDR and CVR show that its flight history during approximately 30 minutes prior to the accident progressed as follows:
The aircraft which was controlled by the FIO, while cruising at FL330 was cleared at 1047:35 to descend to FL210 by the Tokyo Area Control Center and commenced descent. For about 25 minutes from a few minutes before the aircraft began its descent, the CAP briefed the F/O on approach and landing.
At 1058:18, communication was established with Nagoya Approach Control. The aircraft began to descend and decreased its speed gradually, in accordance with the clearances given by Approach Control.
At 1104:03, the aircraft was instructed by Nagoya Approach control to make a left turn to a heading of 010". Later, at 1107:14, the aircraft was cleared for ILS approach to Runway 34 and was instructed to contact Nagoya Tower. After the aircraft took off from Taipei International Airport, from 0854 when the aircraft had passed 1,000 feet pressure altitude, AP No.2 was engaged during climb, cruise and descent.
At 1107:22, when the aircraft was in the initial phase of approach to Nagoya airport, AP No. 1 was also engaged. Later, at 1111:36, both AP No. 1 and 2 were disengaged by the FIO. The aircraft passed the outer marker at 1112:19, and at 1113:39, received landing clearance from Nagoya Tower. At this time, the aircraft was reported of winds 290 degrees at 6 knots. Under manual control, the aircraft continued normal LS approach.
At 1114:05, however, while crossing approximately 1,070 feet pressure altitude, the F/O inadvertently triggered the GO lever. As a result the aircraft shifted into GO AROUND mode leading to an increase in thrust. The CAP cautioned the FIO that he had triggered the GO lever and instructed him, saying "disengage it". The aircraft leveled off for about 15 seconds at approximately 1,040 feet pressure altitude (at a point some 5.5 km from the Runway). The CAP instructed the F/O to correct the descent path which had become too high. The F/O acknowledged this. Following the instruction, the F/O applied nose down elevator input to adjust its descent path, and consequently the aircraft gradually regained its normal glide path. During this period, the CAP cautioned to the FIO twice that the aircraft was in GO AROUND Mode.
At 1114: 18, both AP No.2 and No. 1 were engaged almost simultaneously when the aircraft was flying at approximately 1,040 feet pressure altitude, a point 1.2 dots above the glide slope. Both APs were used for the next 30 seconds. There is no definite record in the CVR of either the crew expressing their intention or calling out to use the AP. For approximately 18 seconds after the AP was engaged, the THS gradually moved from -5.3" to -12.3", which is close to the maximum nose-up limit. The THS remained at -12.3" until 1115: 1 1. During this period, the elevator was continually moved in the nose-down direction. In this condition, the aircraft continued its approach, and at 1115:02, when it was passing about 510 feet pressure altitude (at a point approximately 1.8 km from the runway), the CAP, who had been informed by the FIO that the THR had been latched, told the FIO that he would take over the controls. Around this time, the THR levers had moved forward greatly, increasing EPR from about 1.0 to more than 1.5. Immediately afterwards, however, the THR levers were retarded, decreasing EPR to 1.3. In addition, the elevator was moved close to its nose-down limit when the CAP took the controls.
At 1115:11, immediately after the CAP called out "Go lever", the THR levers were moved forward greatly once again, increasing EPR to more than 1.6. The aircraft therefore began to climb steeply. The F/O reported to Nagoya Tower that the aircraft would go around, and Nagoya Tower acknowledged this. The aircraft started climbing steeply, AOA increased sharply and CAS decreased rapidly. During this period, the TI-IS decreased from -12.3" to -7.4", and SLATS/FLAPS were retracted from 30/40 to 15/15 after the F/O reported "Go Around to Nagoya Tower.
At 1115:17, the GPWS activated Mode 5 warning "Glide Slope" once, and at 1115:25, the stall warning sounded for approximately 2 seconds.
At 1115:31, after reaching about 1,730 feet pressure altitude (about 1,790 feet radio altitude), the aircraft lowered its nose and began to dive.
At 1115:37, the GPWS activated Mode 2 warning "Terrain, Terrain" once, and the stall warning sounded from 1115:40 to the time of crash.
At about 1115:45, the aircraft crashed into the landing zone close to the El taxiway. The accident occurred within the landing zone approximately 110 meters east-northeast of the center of the Runway 34 end at Nagoya Airport. It occurred at about 1115:45. Seven passengers were seriously injured and all 264 other occupants were killed.
Probable cause:
While the aircraft was making an ILS approach to Runway 34 of Nagoya Airport, under manual control by the F/O, the F/O inadvertently activated the GO lever, which changed the FD (Flight Director) to GO AROUND mode and caused a thrust increase. This made the aircraft deviate above its normal glide path. The APs were subsequently engaged, with GO AROUND mode still engaged. Under these conditions the FIO continued pushing the control wheel in accordance with the CAP'S instructions. As a result of this, the THS (Horizontal Stabilizer) moved to its full nose-up position and caused an abnormal out-of-trim situation. The crew continued approach, unaware of the abnormal situation. The AOA increased. The Alpha Floor function was activated and the pitch angle increased. It is considered that, at this time, the CAP (who had now taken the controls), judged that landing would be difficult and opted for go-around. The aircraft began to climb steeply with a high pitch angle attitude. The CAP and the FIO did not carry out an effective recovery operation, and the aircraft stalled and crashed.
The AAIC determined that the following factors, as a chain or a combination thereof, caused the accident:
1. The F/O inadvertently triggered the Go lever. It is considered that the design of the GO lever contributed to it: normal operation of the thrust lever allows the possibility of an inadvertent triggering of the GO lever.
2. The crew engaged the APs while GO AROUND mode was still engaged, and continued approach.
3. The F/O continued pushing the control wheel in accordance with the CAP'S instructions, despite its strong resistive force, in order to continue the approach.
4. The movement of the THS conflicted with that of the elevators, causing an abnormal out-of-trim situation.
5. There was no warning and recognition function to alert the crew directly and actively to the onset of the abnormal out-of-trim condition.
6. The CAP and FIO did not sufficiently understand the FD mode change and the AP override function. It is considered that unclear descriptions of the AFS (Automatic Flight System) in the FCOM (Flight Crew Operating Manual) prepared by the aircraft manufacturer contributed to this.
7. The CAP'S judgment of the flight situation while continuing approach was inadequate, control take-over was delayed, and appropriate actions were not taken.
8. The Alpha-Floor function was activated; this was incompatible with the abnormal out-of-trim situation, and generated a large pitch-up moment. This narrowed the range of selection for recovery operations and reduced the time allowance for such operations.
9. The CAP'S and F/O's awareness of the flight conditions, after the PIC took over the controls and during their recovery operation, was inadequate respectively.
10. Crew coordination between the CAP and the FiO was inadequate.
11. The modification prescribed in Service Bulletin SB A300-22-6021 had not been incorporated into the aircraft.
12. The aircraft manufacturer did not categorise the SB A300-22-602 1 as "Mandatory", which would have given it the highest priority. The airworthiness authority of the nation of design and manufacture did not issue promptly an airworthiness directive pertaining to implementation of the above SB.
Final Report:

Crash of a Britten-Norman BN-2A-21 Islander on Mt Saran: 11 killed

Date & Time: Apr 25, 1994
Type of aircraft:
Operator:
Registration:
PK-ZAA
Flight Phase:
Survivors:
No
Site:
Schedule:
Pontianak - Nanga Pinoh
MSN:
730
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
En route from Pontianak to Nanga Pinoh, the pilot encountered poor weather conditions. While descending in IMC conditions, the twin engine aircraft struck the slope of Mt Saran located 48 km west of Nanga Pinoh. All 11 occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a De Havilland DHC-6 Twin Otter 300 in Ambato: 17 killed

Date & Time: Apr 6, 1994
Operator:
Registration:
FAE450
Flight Phase:
Survivors:
No
Site:
Schedule:
Taura - Latacunga
MSN:
436
YOM:
1974
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
En route from Taura to Latacunga, the crew was cleared to climb to FL155 when, at an altitude of 13,400 feet, the twin engine aircraft stuck the slope of Mt Lozan shrouded in clouds. All 17 occupants were killed. The wreckage was found 100 metres below the summit.
Probable cause:
Controlled flight into terrain.

Crash of a Saab 340B in Amsterdam: 3 killed

Date & Time: Apr 4, 1994 at 1446 LT
Type of aircraft:
Operator:
Registration:
PH-KSH
Survivors:
Yes
Schedule:
Amsterdam - Cardiff
MSN:
195
YOM:
1990
Flight number:
KL433
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
2605
Captain / Total hours on type:
1214.00
Copilot / Total flying hours:
1718
Copilot / Total hours on type:
1334
Aircraft flight hours:
6558
Circumstances:
After take off from runway 24, the aircraft followed a VALKO departure as cleared by Air Traffic Control (ATC) . During climb, passing flight level 165 (FL165), the Master Warning was triggered by the right engine oil pressure Central Warning Panel (CWP) light. The Captain slowly retarded the right hand power lever to flight idle and called for the emergency checklist. After completion of the emergency checklist procedure, the right hand engine oil pressure CWP light was still on and the Captain decided to return to Amsterdam . The right hand engine remained in flight idle during the remainder of the flight. While returning to Amsterdam, the flight was radar vectored by ATC for an Instrument Landing System (ILS) approach on runway 06 . After passing approximately 200 feet height, the aircraft became displaced to the right of the runway and a go around was initiated. During the go around, control of the aircraft was lost and, at 12 :46 UTC, the aircraft hit the ground, in a slight nose low attitude with approximately 80° bank to the right, approximately 560 meters right from the runway 06 centerline, just outside the airport. Two passengers and the Captain died in the accident; eight passengers and the First Officer (FO) were seriously injured.
Probable cause:
Inadequate use of the flight controls during an asymmetric go around resulting in loss of control.
The following contributing factors were reported:
- Insufficient understanding of the flight crew of the SAAB 340B engine oil system,
- Lack of awareness of the consequences of an aircraft configuration with one engine in flight idle,
- Poor Crew Resource Management.
Final Report:

Crash of an Airbus A310-308 near Mezhdurechensk: 75 killed

Date & Time: Mar 23, 1994 at 0057 LT
Type of aircraft:
Operator:
Registration:
F-OGQS
Flight Phase:
Survivors:
No
Schedule:
Moscow - Hong Kong
MSN:
596
YOM:
1991
Flight number:
SU593
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
63
Pax fatalities:
Other fatalities:
Total fatalities:
75
Captain / Total flying hours:
9675
Captain / Total hours on type:
38.00
Copilot / Total flying hours:
5855
Copilot / Total hours on type:
440
Aircraft flight hours:
5375
Aircraft flight cycles:
846
Circumstances:
While cruising by night at the assigned altitude of 10,100 metres, approaching the Novokuznetsk reporting point, the captain's daughter entered the cockpit. She was allowed to sit the left-hand seat while the captain demonstrated some autopilot features, using HDG/S and NAV submodes to alter the heading. The captain's son then took the left front seat. The captain intended to demonstrate the same manoeuvre when his son asked if he could turn the control wheel. He then turned the wheel slightly (applying a force of between 8-10 kg) and held it in that position for a few seconds before returning the wheel to the neutral position. The captain then demonstrated the same features as he did to his daughter and ended by using the NAV submode to bring the aircraft back on course. As the autopilot attempted to level the aircraft at its programmed heading, it came in conflict with the inputs from the control wheel which was blocked in a neutral position. Forces on the control wheel increased to 12-13 kg until the torque limiter activated by disconnecting the autopilot servo from the aileron control linkage. The autopilot remained engaged however. The aircraft then started to bank to the right at 2,5° per second, reaching 45° when the autopilot wasn't able to maintain altitude. The A310 started buffeting, which caught the attention of the captain who told the copilot to take control while he was trying to regain his seat. The seat of the copilot was fully aft, so it took him an additional 2-3 seconds to get to the control wheel. The bank continued to 90°, the aircraft pitched up steeply with +4,8g accelerations, stalled and entered a spin. Two minutes and six seconds later the aircraft struck the ground. The aircraft disintegrated on impact and all 75 occupants were killed, among them 25 foreigners.
Probable cause:
The accident was caused by a stall, spin and impact with the ground resulting from a combination of the following factors:
1. The decision by the PIC to allow an unqualified and unauthorized outsider (his son) to occupy his duty station and intervene in the flying of the aeroplane.
2. The execution of demonstration manoeuvres that were not anticipated in the flight plan or flight situation, with the PIC operating the autopilot while not at his duty station.
3. Application by the outsider and the co-pilot of control forces that interfered with the functioning of the roll channel of the autopilot (and are not recommended in the A310 flight manual), thus overriding the autopilot and disconnecting it from the aileron control linkage.
4. The copilot and PIC failed to detect the fact that the autopilot had become disconnected from the aileron control linkage, probably because:
- The A310 instrumentation has no declutch warning. The provision of signals in accordance with the requirements of Airworthiness Standard NLGS-3, para. 8.2.7.3., and international recommended practices, could have enabled the crew to detect the disengaged autopilot in a timely manner.
- The copilot and PIC may have been unaware of the peculiarities of the declutching function and the actions to be taken in such a situation because of a lack of appropriate information in the flight manual and crew training programme;
- It was difficult for the co-pilot to detect the disengagement of the autopilot by feel, either because of the small forces on his control column or because he took changing forces to be the result of Eldar's actions;
- The PIC was away from his position and distracted by the conversation with his daughter.
5. A slight, unintentional further turn of the control wheel(s) following disengagement of the autopilot caused a right roll to develop.
6. The PIC and copilot failed to detect the excessive right bank angle, which exceeded operating limits, and were late in re-entering the aircraft control loop because their attention was focussed on determining why the aircraft had banked to the right, a manoeuvre they interpreted as entry into a holding area with either no course line or with a new (false) course line generated on the navigational display.
A strong signal indicating that the aeroplane had exceeded the allowable operating bank angle, taking account of the delay in recognizing and assessing the situation and making a decision, could in this situation have attracted the crew's attention and enabled them to detect the bank at an earlier stage.
7. The aeroplane was subjected to buffeting and high angles of attack because the autopilot continued to perform its height-keeping function even after the actuator declutched and as the right roll developed, until the pilot disconnected it by overriding its longitudinal channel.
8. Inappropriate and ineffective action on the part of the copilot, who failed to disconnect the autopilot and to push the control column forward when the buffeting occurred and the aeroplane entered an unusual attitude (high angles of attack and pitch). These actions, which caused the aeroplane to stall and spin, could have resulted from:
- the presence of an outsider in the left-hand pilot's seat and the resulting delay before the PIC re-entered the aeroplane control loop;
- the less-than-optimum working posture of the copilot, whose seat was pushed back to its rearmost position;
- the occurrence, 2 seconds following the onset of buffeting, of an unintentional pitching up of the aeroplane, which sharply increased the angle of attack and reduced lateral controllability;
- unpreparedness of the crew to act in this situation because of lack of appropriate drills in the training programme;
- temporary loss of spatial orientation in night conditions.
Final Report:

Crash of a Britten-Norman BN-2A-21 Islander in Weipa: 6 killed

Date & Time: Mar 21, 1994 at 1754 LT
Type of aircraft:
Registration:
VH-JUU
Flight Phase:
Survivors:
No
Schedule:
Weipa - Aurukun
MSN:
632
YOM:
1971
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
321
Captain / Total hours on type:
6.00
Circumstances:
On the day before the accident, the aircraft flew from Aurukun to Weipa with the chief pilot occupying the left pilot seat and the pilot involved in the accident occupying the right pilot seat. At Weipa the chief pilot left the aircraft, instructing the other pilot to fly some practice circuits before returning the aircraft to Aurukun. Before commencing the circuits and the return flight to Aurukun, the aircraft's two main tanks each contained 100 L of fuel and the two wing tip tanks each contained about 90 L of fuel. On the day of the accident the pilot added 200 L of fuel at Aurukun to the aircraft's tanks and then flew the aircraft and the passengers to Weipa. About 50 minutes before sunset, the aircraft taxied for departure from runway 30 for the 25-minute return flight to Aurukun. When the aircraft was about 300 ft above ground level after takeoff, a witness reported that all engine sounds stopped and that the aircraft attitude changed from a nose-high climb to a more level attitude. A short time later, the noise of engine power surging was heard. The aircraft rolled left and entered a spiral descent. It struck level ground some 350 m beyond the departure end of runway 30 and 175 m to the left of the extended centreline. All six occupants were killed.
Probable cause:
Significant factors:
- The pilot mismanaged the aircraft fuel system.
- Both engines suffered a total power loss due to fuel starvation.
- The right engine regained power probably as a result of a change in aircraft attitude.
- The pilot lost control of the aircraft.
- Recovery was not possible in the height available.
Final Report:

Crash of a Douglas DC-9-32 in Vigo

Date & Time: Mar 21, 1994 at 0917 LT
Type of aircraft:
Operator:
Registration:
EC-CLE
Survivors:
Yes
Schedule:
Madrid - Vigo
MSN:
47678
YOM:
1975
Flight number:
AO260
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
110
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
38224
Aircraft flight cycles:
41155
Circumstances:
On final approach to Vigo Airport runway 20, the crew encountered foggy conditions with a visibility limited to 1,500 metres. The aircraft descended below the glide and the left main gear struck an element of the approach light system located 100 metres short of runway threshold. The aircraft then landed 50 metres short of runway, causing both main landing gear to collapse. The aircraft slid on its belly for about 580 metres before coming to rest, bursting into flames. All 116 occupants were rescued, among them 21 were injured. The aircraft was destroyed.
Probable cause:
Wrong approach configuration on part of the flying crew who led the aircraft descending below the glide in limited visibility conditions. The crew's attention was focused on the visual contact with the runway and the pilots ignored the alarms that was sounding in the cockpit.

Crash of a Casa 212 Aviocar 200 near La Macarena

Date & Time: Mar 19, 1994
Type of aircraft:
Operator:
Registration:
FAC-1154
Flight Phase:
Survivors:
Yes
Schedule:
Villavicencio – La Macarena
MSN:
317
YOM:
1983
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Villavicencio-La Vanguardia Airport, the crew started the descent to La Macarena when one of the engine failed. The crew declared an emergency then reduced his altitude and attempted a forced landing. The aircraft struck various obstacles and eventually came to rest in a ditch. All 29 occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
Engine failure for unknown reasons.

Crash of an Ilyushin II-86 in New Delhi: 4 killed

Date & Time: Mar 8, 1994 at 1200 LT
Type of aircraft:
Operator:
Registration:
RA-86119
Flight Phase:
Survivors:
Yes
Schedule:
New Delhi - Tashkent - Moscow
MSN:
51483209087
YOM:
1985
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
An Air Sahara (Sahara Airlines) boeing 737-2R4C registered VT-SIA was engaged in a local training flight at New Delhi-Indira Gandhi Airport, carrying one instructor and three trainee pilots. Five circuits and landings were completed uneventfully and during the sixth touch-and-go exercice, after take off from runway 28, the aircraft took a left turn and crashed on the international apron. The aircraft collided with an Aeroflot Ilyushin II-86 registered RA-86119 that was parked on the apron, bay n°45. Both aircraft were destroyed by fire. All four crew members on board the Boeing 737 were killed as well as four people on board the II-86 and one on the ground.
Probable cause:
Loss of control after rotation due to application of wrong rudder by trainee pilot during engine failure exercice. The instructor did not guard/block the rudder control and give clear commands as instructor so as to obviate the application of wrong rudder control by the trainee pilot.