Crash of a Douglas DC-3C in Masai Mara

Date & Time: Feb 15, 1992
Type of aircraft:
Operator:
Registration:
5Y-BBN
Survivors:
Yes
MSN:
16097/32845
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Suffered an accident upon landing on an airport somewhere in the Masai Mara National Reserve. There were no casualties while the aircraft was damaged beyond repair.

Crash of an Antonov AN-24B in Guryev

Date & Time: Feb 9, 1992
Type of aircraft:
Operator:
Registration:
CCCP-46816
Survivors:
Yes
MSN:
67302508
YOM:
1976
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
46
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from Guryev Airport, while climbing to an altitude of 900 metres, the right engine lost power and flamed out. The crew shut down the engine and feathered the propeller before completing a circuit to return to the airport. On final, the crew encountered icing conditions and as the aircraft was not properly aligned, the captain decided to initiate a go-around when the aircraft lost height and crashed in a field with its undercarriage partially retracted. The aircraft slid for 418 metres before coming to rest 6 km from the airport. All 51 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right engine during initial climb for unknown reasons. Icing conditions were considered as contributing factor.

Crash of a Boeing 707-351B in Karachi

Date & Time: Feb 7, 1992
Type of aircraft:
Operator:
Registration:
AP-AZW
Survivors:
Yes
MSN:
19636/731
YOM:
1968
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine aircraft suffered a runway excursion after landing at Karachi-Quaid-e-Azam Airport. There were no casualties while the aircraft was damaged beyond repair.

Crash of an Embraer EMB-110C Bandeirante in Caetité: 12 killed

Date & Time: Feb 3, 1992 at 1120 LT
Operator:
Registration:
PT-TBB
Flight Phase:
Survivors:
No
Site:
Schedule:
Salvador - Guanambi
MSN:
110-005
YOM:
1973
Flight number:
NES092
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
4068
Captain / Total hours on type:
2368.00
Copilot / Total flying hours:
1321
Copilot / Total hours on type:
671
Circumstances:
While descending to Guanambi Airport, the crew encountered poor weather conditions and limited visibility. At an altitude of 3,400 feet, the twin engine aircraft struck the slope of Mt Taquari located near Caetité, about 35 km northeast of Guanambi. The aircraft was destroyed and all 12 occupants were killed.
Probable cause:
Wrong approach configuration on part of the crew who continued the descent below MDA of 5,000 feet in limited visibility. The following contributing factors were reported:
- Poor judgment on part of the crew,
- Lack of crew coordination,
- Poor approach planning,
- The crew failed to follow the published approach procedures,
- Lack of visibility due to low clouds (Mt Taquari was shrouded in clouds),
- The crew did not establish any visual contact with the runway,
- Deficiencies in crew management, recruiting, selection and training supervision.
Final Report:

Crash of a Cessna 208B Grand Caravan near Turbo

Date & Time: Jan 31, 1992
Type of aircraft:
Registration:
HP-1191XI
Survivors:
Yes
Schedule:
Panama City - El Porvenir
MSN:
208B-0274
YOM:
1991
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Panama City to El Porvenir Island, four hijackers forced to crew to change his itinerary and to fly to Turbo, Colombia. The aircraft force landed in a remote airstrip where all four hijackers disembarked and disappeared. All other occupants were injured and the aircraft did not return into service.
Probable cause:
Hijacked.

Crash of a Tupolev TU-134A in Batumi

Date & Time: Jan 24, 1992
Type of aircraft:
Operator:
Registration:
CCCP-65053
Survivors:
Yes
MSN:
49838
YOM:
1977
Location:
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Batumi Airport, the aircraft encountered difficulties to stop within the remaining distance. It overran and lost its nose gear before coming to rest. There were no casualties while the aircraft was damaged beyond repair. It was reported that the runway had not been thoroughly cleared from snow.

Crash of a Cessna 402C in Clewiston: 2 killed

Date & Time: Jan 23, 1992 at 2022 LT
Type of aircraft:
Operator:
Registration:
N2714A
Flight Phase:
Survivors:
No
Schedule:
Fort Lauderdale - Sarasota
MSN:
402C-0209
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5500
Captain / Total hours on type:
2250.00
Aircraft flight hours:
13708
Circumstances:
The scheduled passenger flight departed without a flight plan and was last heard from while descending in attempt to remain in VFR conditions. Witnesses on the ground stated that there was extremely heavy rain and thunderstorms at the time of the accident. The wreckage was located the next day and evidence indicated that the airplane hit the ground in a 50° nose down attitude at a high rate of speed. Both occupants were killed.
Probable cause:
Pilot-in-command's improper inflight decision to attempt to descend and remain in VFR conditions in an area of thunderstorms and heavy rain. Contributing to the accident was the pilot-in-command's loss of control in flight.
Final Report:

Crash of an Airbus A320-111 on Mt Sainte-Odile: 87 killed

Date & Time: Jan 20, 1992 at 1920 LT
Type of aircraft:
Operator:
Registration:
F-GGED
Survivors:
Yes
Site:
Schedule:
Lyon - Strasbourg
MSN:
15
YOM:
1988
Flight number:
IT148
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
90
Pax fatalities:
Other fatalities:
Total fatalities:
87
Captain / Total flying hours:
8806
Captain / Total hours on type:
162.00
Copilot / Total flying hours:
3615
Copilot / Total hours on type:
61
Aircraft flight hours:
6316
Aircraft flight cycles:
7194
Circumstances:
On 20 January 1992, an Airbus A320 registered F-GGED and operated by the company Air Inter, made the scheduled connection by night between Lyon-Satolas and Strasbourg-Entzheim using the call sign ITF 148 DA. The aircraft took off from Lyon at approx. 17.20 hours with 90 passengers, 2 flight crew members and 4 cabin crew members on board. No problems were reported by the crew during the course of the flight. The runway in operation at Strasbourg-Entzheim was 05. After listening to the ATIS announcements, the crew planned to carry out an ILS approach procedure for runway 23, followed by visual manoeuvres for a landing on runway 05. Before transferring the aircraft to Strasbourg Approach Control, the Centre Régional de la Navigation Aérienne (CRNA) Est (Eastern Regional Air Navigation Centre) in Reims cleared it to descend to Flight Level 70 near the ANDLO way point. At 18.09 hours contact was established with Strasbourg Approach Control. While the aircraft was crossing Flight Level 150 in descent its distance to STR VOR was around 22 nautical miles. Strasbourg Control cleared it to continue its descent to an altitude of 5,000 feet QNH, then, after announcing that it had passed ANDLO, cleared it to a VOR-DME approach to runway 05. However, the altitude and speed of the aircraft were such that the direct approach procedure could no longer be carried out and the crew informed Control of their intention to carry out an ILS Rwy 23 approach procedure followed by visual manoeuvres for runway 05. Control warned them that this choice would mean a delay, as three aircraft were in the process of taking off from runway 05, using an IFR flight plan. The crew then modified their strategy and advised Control that they would carry out a complete VOR-DME procedure for runway 05. Control then suggested radar guidance to bring them back to ANDLO, thus curtailing the approach procedure. The aircraft was a few seconds away from STR VOR. The crew accepted and carried out the manoeuvres prescribed by the controller: left turn towards heading 230 for an outbound track parallel to the approach axis, then a reciprocal turn towards the ANDLO point. At 18.19 hours the Controller informed the crew that the aircraft was abeam the ANDLO way point and cleared them to final approach. The aircraft then commenced its descent, approximately at the distance allowed for the approach procedure, i.e. 11 nautical miles from STR VOR. Thirty seconds later the Controller requested the crew to call back passing STR. The crew acknowledged. This was the last contact with the aircraft. The wreckage was discovered at 22.35 hours, on a slope of Mont "La Bloss" at a topographical level close to 800 metres (2,620 feet), at a distance approximately 0.8 nautical miles (1,500 m) to the left of the approach path and 10.5 nautical miles (19.5 km) from the runway threshold. Five crew members and 82 passengers were killed while 9 other occupants, including one crew members, were rescued.
Probable cause:
After analysing the accident mechanisms, the commission reach the following conclusions:
1 - The crew was late in modifying its approach strategy due to ambiguities in communication with air traffic control. They then let the controller guide them and relaxed their attention, particularly concerning their aircraft position awareness, and did not sufficiently anticipated preparing the aircraft configuration for landing.
2 - In this situation, and because the controller's radar guidance did not place the aircraft in a position which allowed the pilot flying to align it before ANDLO, the crew was faced with a sudden workload peak in making necessary lateral corrections, preparing the aircraft configuration and initiating the descent.
3 - The key event in the accident sequence was the start of aircraft descent at the distance required by the procedure but at an abnormally high vertical speed (3300 feet/min) instead of approx. 800 feet/min, and the crew failure to correct this abnormally high rate of descent.
4 - The investigation did not determined, with certainty, the reason for this excessively high rate of descent . Of all the possible explanations it examined, the commission selected the following as seen most worthy of wider investigation and further preventative actions:
4.1 - The rather probably assumptions of confusions in vertical modes (due either to the crew forgetting to change the trajectory reference or to incorrect execution of the change action) or of incorrect selection of the required value (for example, numerical value stipulated during briefing selected unintentionally).
4.2 - The highly unlikely possibility of a FCU failure (failure of the mode selection button or corruption of the target value the pilot selected on the FCU ahead of its use by the autopilot computer).
5 - Regardless of which of these possibilities short-listed by the commission is considered, the accident was made possible by the crew's lack of noticing that the resulting vertical trajectory was incorrect, this being indicated, in particular, by a vertical speed approximately four times higher than the correct value, an abnormal nose-down attitude and an increase in speed along the trajectory.
6 - The commission attributes this lack of perception by the crew to the following factors, mentioned in an order which in no way indicates priority:
6.1 - Below-average crew performance characterised by a significant lack of cross-checks and checks on the outputs of actions delegated to automated systems. This lack is particularly obvious by the failure to make a number of the announcements required by the operating manual and a lack of the height/range check called for as part of a VOR DME approach.
6.2 - An ambiance in which there was only minimum communication between crew members;
6.3 - The ergonomics of the vertical trajectory monitoring parameters display, adequate for normal situations but providing insufficient warning to a crew trapped in an erroneous mental representation;
6.4 - A late change to the approach strategy caused by ambiguity in crew-ATC communication;
6.5 - A relaxation of the crew's attention during radar guidance followed by an instantaneous peak workload which led them to concentrate on the horizontal position and the preparation of the aircraft configuration, delegating the vertical control entirely to the aircraft automatic systems;
6.6 - During the approach alignment phase, the focusing of both crew members attention on the horizontal navigation and their lack of monitoring of the autopilot controlled vertical trajectory;
6.7 - The absence of a GPWS and an appropriate doctrine for its use, which deprived the crew of a last chance of being warned of the gravity of the situation.
7 - Moreover, notwithstanding the possibility of a FCU failure, the commission considers that the ergonomic design of the autopilot vertical modes controls could have contributed to the creation of the accident situation . It believes the design tends to increase the probability of certain errors in use, particularly during a heavy workload.
Final Report:

Crash of a Douglas DC-9-31 in Elmira

Date & Time: Jan 18, 1992 at 1028 LT
Type of aircraft:
Operator:
Registration:
N964VJ
Survivors:
Yes
Schedule:
Ithaca - Elmira
MSN:
47373
YOM:
1969
Flight number:
US305
Crew on board:
5
Crew fatalities:
Pax on board:
36
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
19000
Captain / Total hours on type:
9500.00
Aircraft flight hours:
59251
Circumstances:
At the time of the accident, gusty winds were forecast for the surface to higher altitudes. The copilot was flying and configured the airplane about four miles out for landing on runway 24. The flightcrew received progressive wind information during the approach; the last report was wind at 310° and 25 knots. The approach speed was v ref + 10. According to the flightcrew, during the landing flare a wind gust occurred, and the airplane lifted in a nose down attitude. The gust stopped and then the airplane descended to the runway and landed hard. The examination of the airplane revealed the fuselage cracked near where the wings were attached and the aft fuselage was bent down about 7°. Two passengers were seriously injured.
Probable cause:
The aircraft encountered a sudden wind gust during landing flare, which resulted in a hard landing.
Final Report:

Crash of a Beechcraft 1900C in Saranac Lake: 2 killed

Date & Time: Jan 3, 1992 at 0546 LT
Type of aircraft:
Operator:
Registration:
N55000
Survivors:
Yes
Schedule:
Plattsburgh – Saranac Lake – Albany
MSN:
UC-135
YOM:
1990
Flight number:
US4821
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7700
Captain / Total hours on type:
3700.00
Aircraft flight hours:
1675
Circumstances:
On IFR arrival, flight 4821 was cleared to intersection 17 northeast of airport at 6,000 feet, then for ILS runway 23 approach. Radar service was terminated 6.5 east of intersection. Radar data showed that flight crossed and then bracketed localizer. Flight intercepted glide slope from below about 7 miles outside of outer marker and thence deviated above glide slope. About 2 miles outside of marker, flight was at a full fly down deflection when it entered a descent varying from 1,200 to 2,000 fpm. Aircraft struck wooded mountain top 2.0 miles inside of outer marker (3.9 miles from runway) at elevation of 2,280 feet. Minimum altitude at marker was 3,600 feet. Glide slope elevation at point of impact was approximately 2,900 feet. Evidence was found of inadequate electrical ground path between radome and fuselage which, when combined with existing weather conditions, may have produced electrostatic discharge (precipitation static). Although post-accident tests were not conclusive, the safety board believes that the glide slope indications might have been unreliable due to precipitation static interference. Two occupants survived while two others (one pilot and one passenger) were killed.
Probable cause:
Failure of the captain to establish a stabilized approach, his inadequate cross-check of instruments, his descent below specified minimum altitude at the final approach fix, and failure of the copilot to monitor the approach. Factors related to the accident were: weather conditions and possible precipitation static interference, caused by inadequate grounding between the radome and fuselage that could have resulted in unreliable glide slope indications.
Final Report: