Crash of a Piper PA-31T Cheyenne II in Friedrichshafen: 6 killed

Date & Time: Feb 8, 1992 at 1455 LT
Type of aircraft:
Registration:
OE-FGK
Survivors:
No
Schedule:
Salzburg - Altenrhein
MSN:
31-8020052
YOM:
1980
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The twin engine aircraft departed Salzburg on a charter flight to Altenrhein, St Gallen, carrying five passengers and one pilot. On approach to Altenrhein Airport, the pilot encountered poor weather conditions. Unable to locate the runway due to low visibility, he abandoned the approach, initiated a go-around procedure and was cleared to divert to Friedrichshafen-Bodensee Airport that he reached few minutes later. On final approach, the aircraft stalled and crashed in a field located short of runway threshold. The aircraft was destroyed upon impact and all six occupants were killed. At the time of the accident, weather conditions were poor.
Probable cause:
The aircraft stalled while the pilot was attempting a go-around procedure. The distance between the aircraft and the ground was insufficient to expect recovery. Poor weather conditions and limited visibility were considered as contributing factors.

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 a Lockheed C-130B Hercules in Evansville: 17 killed

Date & Time: Feb 6, 1992 at 1000 LT
Type of aircraft:
Operator:
Registration:
58-0732
Flight Type:
Survivors:
No
Site:
Schedule:
Evansville - Evansville
MSN:
3527
YOM:
1959
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
The crew was completing a local training flight at Evansville-William H. Dress Airport on behalf of the Kentucky National Guard, consisting of touch-and-go maneuvers. On approach to runway 22, the crew was instructed by ATC to initiate a go-around for unknown reasons. The crew increased engine power and climbed to a height of 1,500 feet when the aircraft entered a nose down attitude, plunged and crashed onto an hotel located 4,800 feet short of runway 22 threshold. The aircraft, the hotel and a restaurant were destroyed. All five crew members as well as 11 people on the hotel/restaurant were killed. A police officer who was seriously injured in the accident died from his injuries 10 days later.
Probable cause:
It is believed that the loss of control was the consequence of negligences on part of the crew who maintained an insufficient speed while initiating a go-around procedure, causing the aircraft to suffer an aerodynamic stall.

Crash of a Beechcraft E18S in Island Lake

Date & Time: Feb 6, 1992
Type of aircraft:
Operator:
Registration:
C-FRGT
Flight Type:
Survivors:
Yes
Schedule:
Little Grand Rapids – Island Lake
MSN:
BA-154
YOM:
1956
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Island Lake Airport (Stevenson Island), the twin engine aircraft struck the surface of a frozen lake and crashed near Garden Hill. The pilot was slightly injured and the aircraft was damaged beyond repair.

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 Cessna 421C Golden Eagle III in Munich: 5 killed

Date & Time: Jan 25, 1992
Operator:
Registration:
D-IBHH
Survivors:
No
Schedule:
Zurich - Augsburg
MSN:
421C-0162
YOM:
1976
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
On approach to Augsburg-Mühlhausen Airport, the pilot encountered foggy conditions with a visibility down to 500 meters. Unable to establish a visual contact with the runway, he initiated a go-around procedure and diverted to Munich-Riem Airport. On approach to Munich, weather conditions were poor. On short final, he realize the aircraft was not properly aligned and decided to attempt a go-around maneuver when the aircraft struck the ground and crashed to the left of the runway. The aircraft was destroyed upon impact and all five occupants were killed. At the time of the accident, visibility and RVR were below minimums.

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 Grumman HU-16B Albatross at Elefsis AFB: 3 killed

Date & Time: Jan 23, 1992
Operator:
Registration:
51-7202
Flight Type:
Survivors:
No
Schedule:
Elefsis - Elefsis
MSN:
G-270
YOM:
1953
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The crew was completing a post maintenance test flight at Elefsis AFB. On approach, the seaplane crashed in unknown circumstances, killing all three occupants.

Crash of a Douglas VC-47A in Bangkok

Date & Time: Jan 21, 1992
Operator:
Registration:
L2-41/18
Flight Type:
Survivors:
Yes
MSN:
15026/26471
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Bangkok-Don Mueang Airport, the aircraft went out of control, veered off runway to the left, struck a fence and crossed a drainage ditch before coming to rest. There were no casualties.

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: