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 Fokker F27 Friendship 600 near Bani Walid

Date & Time: Dec 23, 1997
Type of aircraft:
Operator:
Registration:
5A-DBO
Survivors:
Yes
Schedule:
Siirt - Tripoli
MSN:
10513
YOM:
1975
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Siirt on a cloud-seeding flight to Tripoli. It is believed that the crew encountered technical problems enroute and decided to attempt an emergency landing. The aircraft belly landed in a sandy area located 15 km south of Bani Walid and came to rest. All five occupants escaped uninjured while the aircraft was damaged beyond repair.

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 Beechcraft A100 King Air in Colorado Springs: 2 killed

Date & Time: Dec 21, 1997 at 0626 LT
Type of aircraft:
Operator:
Registration:
N100BE
Survivors:
Yes
Schedule:
Eden Prairie - Colorado Springs
MSN:
BB-221
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3400
Captain / Total hours on type:
65.00
Aircraft flight hours:
8651
Circumstances:
The pilot was cleared for an ILS DME approach to runway 17L. During the final stage of the approach, the aircraft entered fog and disappeared from view of the control tower personnel. Radar and radio communications were lost also. After searching for 31 minutes, the aircraft was found by airport operations personnel over half way down the runway and 600 feet east of the runway. There was no evidence the aircraft touched down on the runway. The aircraft was configured with the landing gear up and the flaps deployed. Missed approach procedures require the flaps and landing gear to be retracted after initiating the procedure. The decision
height for the approach is 6,384 feet msl (200 feet above ground level) and the required RVR for a 14 CFR Part 135 flight to commence and approach is 2400 (1/2 mile). When on the glide slope, the decision height is 0.4 miles from the runway touchdown zone. Examination of the airplane did not disclose evidence of mechanical malfunction.
Probable cause:
Failure of the pilot to follow IFR Procedures and maintain the minimum descent altitude (MDA). A related factor was fog.
Final Report:

Crash of a Beechcraft 65-80 Queen Air off Maiquetía: 9 killed

Date & Time: Dec 20, 1997 at 1805 LT
Type of aircraft:
Operator:
Registration:
YV-539C
Survivors:
Yes
Schedule:
Los Roques – Caracas
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
At 1759LT, while descending to Caracas-Maiquetía-Simón Bolívar Airport by night, the pilot informed ATC about an engine failure. Six minutes later, the aircraft crashed in the sea about 22 km north of the airport. A passenger was rescued at 2205LT. The following night, two dead bodies were found while seven other occupants were never found. The aircraft sank and was lost.
Crew:
Ricardo Batija. †
Passengers:
Francesco Porco,
Fernando Guasamucare, †
Ileana González, †
Víctor Ruiz, †
Yelitza Arenas, †
Juan Cabezas, †
Ledda Martínez, †
Edwin Núñez, †
Paola de Guasamucare. †
Probable cause:
Engine failure for unknown reasons.

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.

Crash of a Rockwell Grand Commander 690A in Yakima: 2 killed

Date & Time: Dec 12, 1997 at 2230 LT
Operator:
Registration:
N72VF
Flight Type:
Survivors:
No
Schedule:
Seattle - Yakima
MSN:
690-11242
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4800
Captain / Total hours on type:
80.00
Aircraft flight hours:
7001
Circumstances:
The flight was operating into the Yakima airport at night during the period the airport operates as non-towered. Some witnesses reported the aircraft initially appeared lower than normal and that it descended and impacted the ground at a steep angle, and some witnesses reported an abrupt entry into the descent. The aircraft crashed 2.2 nautical miles east of the runway threshold, slightly right of the localizer course The pilot was 'cleared for approach' by air traffic control (ATC) and he subsequently initiated an instrument landing system (ILS) approach to runway 27. The last radar position showed the aircraft approximately on the localizer, at glide slope intercept altitude, 9 nautical miles east of the airport. Three minutes after the last radar position, the pilot reported to ATC he had broken out and had the airport in sight, and canceled instrument flight rules (IFR). ATC then terminated service and approved a frequency change.. Ceiling was 1,500 feet overcast with 6 miles visibility in mist, with no significant icing forecast. No evidence of mechanical problems was found; however, much of the aircraft was consumed by an intense post-crash fire.
Probable cause:
A loss of aircraft control for undetermined reasons.
Final Report:

Crash of an Antonov AN-12BP in Naryan-Mar: 8 killed

Date & Time: Dec 11, 1997 at 1657 LT
Type of aircraft:
Operator:
Registration:
RA-12105
Flight Type:
Survivors:
Yes
MSN:
5 3 434 04
YOM:
1965
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
A Mil Mi-8 registered RA-24247 just landed at Naryan-Mar Airport after completing a local flight with eight passengers and three crew members on board. Its crew was instructed to vacate via taxiway 4. Following an uneventful flight, the crew of the Antonov AN-12 was cleared to land on the same runway two minutes later. After touchdown, the aircraft collided with the helicopter. Both aircrafts were destroyed and while all nine people on board the Antonov were injured, among the 11 people on board the helicopter, eight were killed and three were injured. At the time of the accident, the visibility was reduced to 500 metres.
Probable cause:
The airport of Naryan-Mar is controlled by both civil and military services. The helicopter has been cleared to land by civil ATC and less than two minutes later, the aircraft was cleared by military ATC to land on the same runway. A lack of coordination between both ATC services was identified as the separation between both landings was insufficient. Nevertheless, it was also reported that the crew of the Antonov failed to follow ATC message after the controller in the tower instructed the crew to initiate a go-around procedure. The crew misinterpreted this order thinking ATC was referring to the lack of visibility and not to the presence of another aircraft on the runway.

Crash of a Beechcraft A100 King Air in Charlotte: 1 killed

Date & Time: Dec 10, 1997 at 2321 LT
Type of aircraft:
Registration:
N30SA
Survivors:
Yes
Schedule:
Lewisberg - Concord
MSN:
BB-246
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
14320
Aircraft flight hours:
6575
Circumstances:
Following a missed approach at the destination, the pilot requested weather information for two nearby airports. One airport was 53 miles northeast with a cloud ceiling of 900 feet, and visibility 6 miles. The pilot opted for the accident airport, 21 miles southwest, with an indefinite ceiling of zero, and visibility 1/4 mile. After completing the second missed approach, the flight proceeded to the accident airport. Radar vectors were provided to the ILS runway 36L. On the final approach, the flight veered to the right of the localizer and descended abruptly. Last recorded altitude for the flight was below the decision height. Investigation revealed no anomalies with the airport navigational aids for the approach, and the airplane's navigation receivers were found to be operational. Postmortem examinations of the pilot did not reveal any pre-existing diseases, and toxicological examinations were negative for alcohol and other drugs.
Probable cause:
The pilot's continued approach below decision height without reference to the runway environment, and his failure to execute a missed approach.
Final Report: