Crash of an Avro RJ100 in Samsun

Date & Time: Jan 11, 1998 at 1458 LT
Type of aircraft:
Operator:
Registration:
TC-THF
Survivors:
Yes
Schedule:
Istanbul - Samsun
MSN:
E3240
YOM:
1994
Flight number:
TK074
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
68
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to runway 21, the crew encountered poor weather conditions and limited visibility. unable to establish a visual contact with the runway, the captain decided to initiate a go-around procedure. While on a second approach to runway 03 which is 1,620 metres long, the aircraft was too high on the glide and landed about half way down the runway. Unable to stop within the remaining distance, it overran, lost its undercarriage and collided with an earth mound located 67 metres past the runway end. All 74 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the crew continued the approach above the glide with an excessive speed, causing the aircraft to land too far down the runway (about half way down), reducing the landing distance available. At the time of the accident, the runway was wet and the braking action was reduced. The crew failed to initiate a go-around procedure.

Crash of a De Havilland DHC-6 Twin Otter 310 in Limbang

Date & Time: Jan 8, 1998 at 1744 LT
Operator:
Registration:
9M-MDJ
Survivors:
Yes
Schedule:
Miri - Limbang
MSN:
791
YOM:
1982
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft landed a little too far down the runway and bounced twice. Out of control, it skidded and overran the runway before coming to rest in a ditch. All eight occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Fokker 100 in Isfahan

Date & Time: Jan 5, 1998 at 2042 LT
Type of aircraft:
Operator:
Registration:
EP-IDC
Survivors:
Yes
Schedule:
Orūmīyeh - Tehran
MSN:
11267
YOM:
1990
Flight number:
IR378
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
104
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While descending to Tehran-Mehrabad Airport, the crew was informed about the poor weather conditions at destination with snow falls, low visibility and a 20 knots tailwind. The crew decided to divert to Isfahan-Shahid Beheshti Airport. On approach, the crew encountered limited visibility due to foggy conditions. The aircraft struck the ground, lost its undercarriage and slid for almost one km before coming to rest in a desert area located 8 km short of runway 26. All 113 occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Britten-Norman BN-2A-6 Islander in Rio Sidra: 10 killed

Date & Time: Dec 31, 1997 at 0745 LT
Type of aircraft:
Operator:
Registration:
HP-986PS
Survivors:
No
Schedule:
Panama City – Rio Sidra
MSN:
178
YOM:
1970
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
The twin engine aircraft departed Panama City-Marcos A. Gelabert Airport at 0643LT on a flight to Rio Sidra, carrying nine passengers and one pilot. On approach to Rio Sidra, the pilot encountered poor visibility due to foggy conditions. On final, the aircraft struck the ground 6,5 km short of runway and crashed 62 minutes after its departure. The aircraft was totally destroyed and all 10 occupants were killed, among them four US citizens.

Crash of a Swearingen SA227AC Metro III in Trinidad

Date & Time: Dec 31, 1997
Type of aircraft:
Operator:
Registration:
CP-2321
Flight Phase:
Survivors:
Yes
Schedule:
Trinidad - La Paz
MSN:
AC-643
YOM:
1986
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the crew lost control of the airplane that veered off runway, lost its undercarriage and came to rest. All 20 occupants escaped uninjured while the aircraft was written off.

Crash of a Fokker F28 Fellowship 4000 in Sylhet

Date & Time: Dec 22, 1997 at 2236 LT
Type of aircraft:
Operator:
Registration:
S2-ACJ
Survivors:
Yes
Schedule:
Dhaka - Sylhet
MSN:
11180
YOM:
1981
Flight number:
BG609
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
85
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Sylhet Airport, the crew encountered foggy conditions. Due to poor visibility, the crew was unable to establish a visual contact with the approach and runway lights so the decision was taken to initiate a go-around procedure. Few minutes later, a second attempt to land was abandoned for the same reason. The captain insisted and elected to make another approach. On final, the aircraft descended below the MDA and struck the ground 3 km short of runway threshold. On impact, the undercarriage were torn off and the aircraft came to rest in a waterlogged area, broken in two. All 89 occupants were rescued, among them 50 were slightly injured.
Probable cause:
Controlled flight into terrain after the crew continued the descent below MDA without visual contact with the ground until the aircraft impacted terrain.

Crash of a Boeing 737-36N near Palembang: 104 killed

Date & Time: Dec 19, 1997 at 1613 LT
Type of aircraft:
Operator:
Registration:
9V-TRF
Flight Phase:
Survivors:
No
Schedule:
Jakarta - Singapore
MSN:
28556
YOM:
1997
Flight number:
MI185
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
97
Pax fatalities:
Other fatalities:
Total fatalities:
104
Captain / Total flying hours:
7173
Captain / Total hours on type:
3614.00
Copilot / Total flying hours:
2501
Copilot / Total hours on type:
2311
Aircraft flight hours:
2238
Aircraft flight cycles:
1306
Circumstances:
On 19 December 1997, a SilkAir Boeing B737-300 aircraft, registration 9V-TRF, was on a scheduled commercial international passenger flight under Instrument Flight Rules (IFR), routing Singapore – Jakarta – Singapore. The flight from Singapore to Jakarta operated normally. After completing a normal turnaround in Jakarta the aircraft departed Soekarno-Hatta International Airport for the return leg. At 08:37:13 (15:37:13 local time) the flight (MI185) took off from Runway 25R with the Captain as the handling pilot. The flight received clearance to climb to 35,000 feet (Flight Level 350) and to head directly to Palembang. At 08:47:23 the aircraft passed FL245. Ten seconds later, the crew requested permission to proceed directly to PARDI2. The air traffic controller instructed MI 185 to standby, to continue flying directly to Palembang and to report when reaching FL350. At 08:53:17, MI185 reported reaching FL350. Subsequently, the controller cleared MI185 to proceed directly to PARDI and to report when abeam Palembang. At 09:05:15.6, the cockpit voice recorder (CVR) ceased recording. According to the Jakarta ATC transcript, at 09:10:18 the controller informed MI 185 that it was abeam Palembang. The controller instructed the aircraft to maintain FL350 and to contact Singapore Control when at PARDI. The crew acknowledged this call at 09:10:26. There were no further voice transmissions from MI 185. The last readable data from the flight data recorder (FDR) was at 09:11:27.4. Jakarta ATC radar recording showed that MI185 was still at FL350 at 09:12:09. The next radar return, eight seconds later, indicated that MI185 was 400 feet below FL350 and a rapid descent followed. The last recorded radar data at 09:12:41 showed the aircraft at FL195. The empennage of the aircraft subsequently broke up in flight and the aircraft crashed into the Musi river delta, about 50 km (30 nm) north-northeast of Palembang at about 09:13. The accident occurred in daylight and in good weather conditions. All 104 occupants were killed. The accident was not survivable.
Probable cause:
- The NTSC investigation into the MI 185 accident was a very extensive, exhaustive and complex investigation to find out what happened, how it happened, and why it happened. It was an extremely difficult investigation due to the degree of destruction of the aircraft resulting in highly fragmented wreckage, the difficulties presented by the accident site and the lack of information from the flight recorders during the final moments of the accident sequence.
- The NTSC accident investigation team members and participating organizations have done the investigation in a thorough manner and to the best of their conscience, knowledge and professional expertise, taking into consideration all available data and information recovered and gathered during the investigation.
- Given the limited data and information from the wreckage and flight recorders, the NTSC is unable to find the reasons for the departure of the aircraft from its cruising level of FL350 and the reasons for the stoppage of the flight recorders.
- The NTSC has to conclude that the technical investigation has yielded no evidence to explain the cause of the accident.
Final Report:

Crash of a Yakovlev Yak-42 near Katerini: 70 killed

Date & Time: Dec 17, 1997 at 2112 LT
Type of aircraft:
Operator:
Registration:
UR-42334
Flight Phase:
Survivors:
No
Site:
Schedule:
Lvov - Odessa - Thessaloniki
MSN:
26 06 164
YOM:
1986
Flight number:
AEW241
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
62
Pax fatalities:
Other fatalities:
Total fatalities:
70
Captain / Total flying hours:
9850
Captain / Total hours on type:
2300.00
Copilot / Total flying hours:
16210
Copilot / Total hours on type:
5350
Aircraft flight hours:
12008
Aircraft flight cycles:
6836
Circumstances:
AeroSvit Airlines Flight 241 was a scheduled service from Kiev, Ukraine to Thessaloniki, Greece with an en route stop at Odessa, Ukraine. The first leg of the flight was operated by a Boeing 737. Because of engine problems, an aircraft change had to be made at Odessa. The last leg of the flight was carried out using a Yakovlev 42 (UR-42334), which was being chartered from Lvovskie Avialinii. The flight crew had no previous experience in flying to Thessaloniki. The flight was dispatched from Odessa with the No 1 VHF/NAV receiver inoperative, which was contrary to the minimum equipment list (MEL), and took off at 17:23 hours UTC. The weather conditions at Thessaloniki Airport were above required approach and landing minima, however, darkness and an overcast cloud layer obscured awareness of mountainous terrain in the area. The flight was instructed by the approach controller to conduct the LAMBI1F standard arrival procedure and was cleared to execute a VOR-DME-ILS approach to runway 16. The aircraft did not follow the "19 DME arc" as required by the approach procedure, but proceeded directly to the THS NDB. It overshot the localizer course at least twice and the flight crew were unable to establish a stabilized approach. According to the CVR cockpit conversations, the flight crew was confused and uncertain with respect to the navigation aids and the information that was presented. During the approach there were no standard callouts made by the flight crew related to the glide slope, outer marker or minima. At 18:54 UTC the Thessaloniki Tower controller reported that they had passed the airport. The flight crew was unaware that they overflew the runway until they were informed by the controller. The flight crew then initiated a go-around but did not follow the published missed approach procedure, nor did they follow the instructions given by the ATC. Although instructed by ATC to proceed to, and enter the south holding pattern, the flight continued on a flight path to the west. The flight crew remained confused, disorganized, and disoriented during the missed approach and the subsequent clearances issued by ATC. They had lost situational and terrain awareness, and they were uncertain with respect to the radio navigation aids and the information that was presented. They also requested "route vectors" and "heading" twice although Thessaloniki Airport was a non-radar facility. The flight crew occasionally was confused in reading and reporting the correct distances on their DME equipment (miles to kilometers and vice versa) as their instruments displayed distances in kilometers. The flight crew in their effort to solve the navigational problem, often switched their focus from VOR/DME information to ADF, and vice versa. This, in conjunction with the VHF/NAV receiver malfunction, contributed greatly to the confusion in the cockpit and to the loss of orientation. At 19:12 UTC the GPWS sounded for 4 seconds. At the same time the approach controller radioed: "AEW number one, continue VOR-DME/ILS approach minima, continue and report approaching the outer marker". The crew replied: "Outer marker will be report`. After a while the approach controller asked: "AEW-241, do you have the field in sight?". At that time the GPWS sounded again. Shortly afterwards the aircraft impacted the side of Mount Pente Pigadia at 3300 feet. The wreckage was found at 10:30 hours, December 20. At the same date a Greek Air Force Lockheed Hercules, which was being used in the search, crashed, killing all 5 on board. On October 6, 2000 a trial began with two air traffic controllers being accused of many counts of manslaughter and of violating the transportation regulations. They were sentenced to five years imprisonment. In December 2002 a Thessaloniki appeals court reduced the sentences of two air traffic controllers to four years and four months each.
Probable cause:
Causes:
1. The failure of the flight crew to adequately plan and execute the approach and missed approach procedure for runway 16 at Makedonia airport.
2. The failure of the flight crew to properly utilize the Makedonia airport radio navigational aids and aircraft radio equipment / instruments and to interpret the information that was presented.
3. The failure of the flight crew to declare an emergency when they lost their orientation following the missed approach, despite numerous cues alerting them for the aforementioned situation.
4. The captain's failure to achieve maximum performance climb in response to the GPWS alarm signal, 30" prior to impact.
5. The lack of command presence, cockpit discipline and resource management which resulted in a disorganized, confused and ultimately dysfunctional flight crew.
6. The company's inadequate oversight, over their flight operations, that allowed for and resulted in scheduling one inadequately prepared and marginally qualified flight crew and an aircraft which did not comply with national and international airworthiness regulations (it had not been issued the Type Certificate with the corresponding Amendment for the international flights), to execute a regular passenger flight with No 1 VHF/NAV receiver inoperative.
Contributing Factors:
1. The inadequate training provided to the flight crew for cockpit resource management and international flight operations.
2. The dispatch of the aircraft with No 1 VHF/NAV receiver, inoperative, despite the restrictions provided in M.E.L. (Appendix 28, pages 14, 16).
3. The assignment of a marginally qualified instructor pilot to this specific flight who disrupted and substantially reduced the coordination and effectiveness of the flight crew.
4. The inaccurate display of the symbol (R) on the Jeppesen Sanderson Inc. chart 11-1, for runway 16, from which the flight crew, most probably, have formed the wrong impression that radar service was available in Makedonia airport.
5. The insufficient evaluation by the Approach Control, under the aforementioned circumstances, of the difficulties encountered by the flight crew in following procedures and clearances, which prevented the Controllers to offer any available assistance, by their own initiative, in order to prevent, probably, the accident.
Final Report:

Crash of a Canadair RegionalJet CRJ100 in Fredericton

Date & Time: Dec 16, 1997 at 2348 LT
Operator:
Registration:
C-FSKI
Survivors:
Yes
Schedule:
Toronto - Fredericton
MSN:
7068
YOM:
1995
Flight number:
AC646
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
39
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11020
Captain / Total hours on type:
1770.00
Copilot / Total flying hours:
3225
Copilot / Total hours on type:
60
Aircraft flight hours:
6061
Aircraft flight cycles:
5184
Circumstances:
Air Canada Flight 646, C-FSKI, departed Toronto-Lester B. Pearson International Airport, Ontario, at 2124 eastern standard time on a scheduled flight to Fredericton, New Brunswick. On arrival, the reported ceiling was 100 feet obscured, the visibility one-eighth of a mile in fog, and the runway visual range 1200 feet. The crew conducted a Category I instrument landing system approach to runway 15 and elected to land. On reaching about 35 feet, the captain assessed that the aircraft was not in a position to land safely and ordered the first officer, who was flying the aircraft, to go around. As the aircraft reached its go-around pitch attitude of about 10 degrees, the aircraft stalled aerodynamically, struck the runway, veered to the right and then travelled—at full power and uncontrolled—about 2100 feet from the first impact point, struck a large tree and came to rest. An evacuation was conducted; however, seven passengers were trapped in the aircraft until rescued. Of the 39 passengers and 3 crew members, 9 were seriously injured and the rest received minor or no injuries. The accident occurred at 2348 Atlantic standard time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Although for the time of the approach the weather reported for Fredericton—ceiling 100 feet and visibility c mile—was below the 200-foot decision height and the charted ½ -mile (RVR 2600) visibility for the landing, the approach was permitted because the reported RVR of 1200 feet was at the minimum RVR specified in CAR 602.129.
2. Based on the weather and visibility, runway length, approach and runway lighting, runway condition, and the first officer’s flying experience, allowing the first officer to fly the approach is questionable.
3. The first officer allowed the aircraft to deviate from the flight path to the extent that a go-around was required, which is an indication of his ability to transition to landing in the existing environmental conditions.
4. Disengagement of the autopilot at 165 feet rather than at the 80-foot minimum autopilot altitude resulted in an increased workload for the PF, allowed deviations
from the glide path, and deprived the pilots of better visual cues for landing.
5. In the occurrence environmental conditions, the lack of runway centre line and touchdown-zone lighting probably contributed to the first officer not being able to see the runway environment clearly enough to enable him to maintain the aircraft on the visual glide path and runway centre line.
6. The first officer’s inexperience and lack of training in flying the CL-65 in low-visibility conditions contributed to his inability to successfully complete the landing.
7. The situation of a captain being the PNF when ordering a go-around probably played a part in the uncertainty regarding the thrust lever advance and the raising of the flaps because there was no documented procedure covering their duties.
8. The go-around was attempted from a low-energy situation outside of the flight boundaries certified for the published go-around procedures; the aircraft’s low energy was primarily the result of the power being at idle.
9. The sequential nature of steps within the go-around procedures, in particular, in directing the pitch adjustment prior to noting the airspeed, the compelling nature of the command bars, and the high level of concentration required when initiating the go-around contributed to the first officer’s inadequate monitoring of the airspeed during the go-around attempt.
10. Following the command bars in go-around mode does not ensure that a safe flying speed is maintained, because the positioning of the command bars does not take into consideration the airspeed, flap configuration, and the rate of change of the angle of attack, considerations required to compute stall margin.
11. The conditions under which the go-arounds are demonstrated for aircraft certification do not form part of the documentation that leads to aircraft limitations or boundaries for the go-around procedure; this contributed to these factors not being taken into account when the go-around procedures were incorporated in aircraft and training manuals.
12. The published go-around procedure does not adequately reflect that once power is reduced to idle for landing, a go-around will probably not be completed without the aircraft contacting the runway (primarily because of the time required for the engines to spool up to go-around thrust).
13. The Air Canada stall recovery training, as approved by Transport Canada, did not prepare the crew for the conditions in which the occurrence aircraft stick shaker activated and the aircraft stalled.
14. The limitations of the ice-detection and annunciation systems and the procedures on the use of wing anti-ice did not ensure that the wing would remain ice-free during flight.
15. Ice accretion studies indicate that the aircraft was in an icing environment for at least 60 seconds prior to the stall, and that during this period a thin layer of mixed ice with some degree of roughness probably accumulated on the leading edges of the wings. Any ice on the wings would have reduced the safety margins of the stall protection system.
16. The implications of ice build-up below the threshold of detection, and the inhibiting of the ice advisory below 400 feet, were not adequately considered when the stall margin was being determined during the 1996 certification of the ice-detection system and associated procedures.
17. The stall protection system operated as designed: that it did not prevent the stall is related to the degraded performance of the wings.
18. The Category I approach was without the extra aids and defences required for Category II approaches.
19. Canadian regulations with respect to Category I approaches are more liberal than those of most countries and are not consistent with the ICAO International Standards and Recommended Practices (Annex 14), which defines visibility limits; in Canada, the visibility values, other than RVR, are advisory only.
20. Even though a Category I approach may be conducted in weather conditions reported to be lower than the landing minima specified for the approach, there is no special training required for any flight crew member, and there is no requirement that flight crew be tested on their ability to fly in such conditions.
21. Air Canada’s procedures required that the captain fly the aircraft when conducting a Category II approach, in all weather conditions; however, the decision as to who will fly low-visibility Category I approaches was left to the captain, who may not be in a position to adequately assess the first officer’s ability to conduct the approach.
22. The aircraft stalled at an angle of attack approximately 4.5 degrees lower, and at a CLmax 0.26 lower, than would be expected for the natural stall.
23. On final approach below 1000 feet agl, the wing performance on the accident flight was degraded over the wing performance at the same phase on the previous flight.
24. The engineering simulator comparison indicated two step reductions in aircraft performance, at 400 feet and 150 feet agl, as a result of local flow separation in the vicinity of wing station (WS) 247 and WS 253.
25. Pitting on the leading edges of the wings had a negligible effect on the performance of the aircraft.
26. The sealant on the leading edges of both wings was missing in some places and protruding from the surface 2 to 3 mm in others. Test flights indicate that the effect of the protruding chordwise sealant on the aircraft performance could have accounted for a reduction of 1.7 to 2.0 degrees in maximum fuselage angle of attack and of 0.03 to 0.05 in CLmax.
27. The maximum reduction in angle of attack resulting from ground effect is considered to be in the order of 0.75±0.5 degree: the aircraft angle of attack was influenced by ground effect during the go-around manoeuvre.
28. The performance loss caused by the protruding sealant and by ground effect was not great enough to account for the performance loss experienced; there is no apparent phenomenon other than ice accretion that could account for the remainder of the performance loss.
29. Neither Bombardier Inc., nor Transport Canada, nor Air Canada ensured that the regulations, manuals, and training programs prepared flight crews to successfully and consistently transition to visual flight for a landing or to go-around in the conditions that existed during this flight, especially considering the energy state of the aircraft when the go-around was commenced.
Other Findings:
1. Both the captain and the first officer were licensed and qualified for the duties performed during the flight in accordance with regulations and Air Canada training
and standards, except for minor training deficiencies with regard to emergency equipment.
2. The occurrence flight attendant was trained and qualified for the flight in accordance with existing requirements.
3. The aircraft was within its weight and centre-of-gravity limits for the entire flight.
4. Records indicate that the aircraft was certified, equipped, and maintained in accordance with existing regulations and approved procedures.
5. There was no indication found of a failure or malfunction of any aircraft component prior to or during the flight.
6. When the stick shaker activated, it is unlikely that the crew could have landed the aircraft safely or completed a go-around without ground contact.
7. When power was selected for the go-around, the engines accelerated at a rate that would have been expected had the thrust levers been slammed to the go-around power setting.
8. The aircraft was not equipped with an emergency locator transmitter, nor was one required by regulation.
9. The lack of an emergency locator transmitter probably delayed locating the aircraft and its occupants.
10. Passengers and crew had no effective means of signaling emergency rescue services personnel.
11. The flight crew did not receive practical training on the operation of any emergency exits during their initial training program, even though this was required by
regulation.
12. Air Canada’s initial training program for flight crew did not include practical training in the operation of over-wing exits or the flight deck escape hatch.
13. Air Canada’s annual emergency procedures training for flight crew regarding the operation and use of emergency exits did not include practical training every third year, as required. Annual emergency exit training was done by demonstration only.
14. The flight crew were unaware that a pry bar was standard emergency equipment on the aircraft.
15. The four emergency flashlights carried on board were located in the same general area of the aircraft, increasing the possibility that all could be rendered inaccessible or unserviceable in an accident. (See section 4.1.6)
16. That there was a Flight Service Station specialist, as opposed to a tower controller, at the Fredericton airport at the time of the arrival of ACA 646 was not material to this occurrence.
Final Report:

Crash of a Tupolev TU-154B-1 in Sharjah: 85 killed

Date & Time: Dec 15, 1997 at 1835 LT
Type of aircraft:
Operator:
Registration:
EY-85281
Survivors:
Yes
Schedule:
Dushanbe - Sharjah
MSN:
78A281
YOM:
1978
Flight number:
TZK3183
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
79
Pax fatalities:
Other fatalities:
Total fatalities:
85
Circumstances:
Following an uneventful flight, the aircraft entered the UAE airspace and was cleared by Dubai ATC to successively descend to FL170, 100, 060 and 025 via heading 190. Passing 3,460 feet on descent, the crew was cleared to continue to 1,500 feet when, at an altitude of 1,800 feet, the aircraft entered an area of turbulences. The level of 1,500 feet was reached 15 km from the runway 30 threshold. For unknown reasons, the crew failed to report he was passing 1,500 feet and was then instructed to continue via heading 270 for the final approach to runway 30. In a relative limited visibility, the crew initiated a right turn at a speed of 400 km/h then lowered the landing gear. At an altitude of 820 feet, an alarm sounded in the cockpit, informing the crew about an excessive angle of attack. The captain corrected the pitch from 20° to 14° when few seconds later, at an altitude of 690 feet, the aircraft entered a second area of turbulences. The captain realized his altitude was insufficient and requested an increase of engine power when the aircraft struck the ground and crashed 13 km short of runway, bursting into flames. The copilot was the only survivor while 85 other occupants were killed. The aircraft disintegrated on impact.
Probable cause:
The accident was the consequence of a controlled flight into terrain.
The following findings were identified:
- The crew failed to follow the approach published procedures,
- The crew continued the approach below the MDA until the aircraft collided with terrain,
- The crew failed to proceed to the usual approach briefing and checks,
- Lack of visibility due to the night,
- Crew fatigue,
- Lack of crew mutual crosscheck during descent,
- Lack of crew coordination,
- Turbulences in the approach path,
- Non compliance to published procedures.