Crash of a Beechcraft F90-1 King Air in Navegantes: 4 killed

Date & Time: Aug 18, 1992 at 1020 LT
Type of aircraft:
Registration:
PT-OLP
Survivors:
No
Schedule:
Itumbiara – Ituverava – Blumenau
MSN:
LA-220
YOM:
1984
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
8609
Copilot / Total flying hours:
6330
Circumstances:
While descending to Blumenau Airport, the crew encountered poor weather conditions and decided to divert to Navegantes-Itajaí Airport. On approach to runway 25, at low height, the captain initiated a left turn when the twin engine aircraft struck the top of a hill and crashed, bursting into flames. All four occupants were killed.
Probable cause:
On final approach in limited visibility due to poor weather conditions, the pilot-in-command lost control of the airplane after suffering a spatial disorientation.
Final Report:

Crash of a Piper PA-31-310 Navajo B in Karlstad: 5 killed

Date & Time: Aug 16, 1992 at 1142 LT
Type of aircraft:
Operator:
Registration:
OY-BZD
Survivors:
Yes
Schedule:
Roskilde - Karlstad
MSN:
31-7401266
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
550
Captain / Total hours on type:
20.00
Aircraft flight hours:
4725
Circumstances:
On approach to Karlstad Airport, the pilot informed ATC he was low on fuel. Shortly later, he declared an emergency when the both engines stopped. The aircraft lost height and eventually crashed in the Vänern Lake located 12,5 km from Karlstad Airport. Four passengers and the pilot were killed while three other passengers were rescued.
Probable cause:
The accident was caused by a double engine failure due to fuel exhaustion. This was due to the failure of the pilot to refuel the aircraft before the flight or to make a fuel stop en route. The following contributing factors were reported:
- Both engines stopped due to fuel exhaustion before the aircraft reached the destination,
- The flight was initiated with a too little amount of fuel on board,
- The pilot deviated from the current Danish regulations with regard to the prescribed minimum amount of fuel.
Final Report:

Crash of a Beechcraft C90 King Air off Pontiac

Date & Time: Aug 6, 1992 at 1410 LT
Type of aircraft:
Operator:
Registration:
N90RG
Survivors:
Yes
Schedule:
Holland - Pontiac
MSN:
LJ-546
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2114
Captain / Total hours on type:
261.00
Aircraft flight hours:
8487
Circumstances:
Pilot was on final approach when he stated he got a fuel crossfeed 'warning' light. He then proceeded to try to troubleshoot the fuel system by cycling the right boost pump switch, and 'reset and arm' the auto crossfeed. He stated the crossfeed light came on again followed by the right fuel pressure light, and he experienced a power loss on the right side. When he feathered the right engine, the left engine also experienced a loss of power. The pilot cleaned up the airplane and ditched in the lake short of the airport. The investigation revealed the left wing fuel tanks were empty, and the left nacelle tank was collapsed. The right wing fuel tanks were empty, and the right nacelle tank contained 19 gallons of fuel. The fuel supply, transfer, and crossfeed systems were functionally checked, and were operable. All cockpit fuel system lights indicated normal system operation.
Probable cause:
The pilot's not understanding the fuel system, and his subsequent inadvertent discontinuance of fuel to both engines.
Final Report:

Crash of an Airbus A310-304 near Kathmandu: 113 killed

Date & Time: Jul 31, 1992 at 1245 LT
Type of aircraft:
Operator:
Registration:
HS-TID
Survivors:
No
Site:
Schedule:
Bangkok - Kathmandu
MSN:
438
YOM:
1987
Flight number:
TG311
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
99
Pax fatalities:
Other fatalities:
Total fatalities:
113
Circumstances:
Thai Airways Flight 311 was conducting the Sierra (VOR/DME) approach to runway 02 at Tribhuvan International Airport, in instrument weather conditions. A flap fault occurred while the flight was on the approach; this caused the crew to ask for clearance back to Calcutta, a decision that was in keeping with both Company and performance requirements, which necessitate the use of full flaps for the steep final approach. Shortly (21 seconds) after making this request, at a distance of approximately 12 nm from the Kathmandu VOR, the flap fault was rectified by retracting and then reselecting the flaps. The crew determined that it was not possible to continue the straight-in approach, due to the steep descent angles required and the position of the aircraft. The crew stated to the control tower that they wished to start their approach again and requested a left turn back to the Romeo fix, which is 41 nm south south-west (202 radial) of the Kathmandu VOR. The Controller, in the non-radar environment, responded by clearing the flight to make the Sierra approach, which starts at the 202 radial and 16 nautical miles from the VOR. The crew response to the clearance was to report that, at the moment, they couldn't land and to ask again for left turn back to Romeo to start their approach again. After further dialogue with the controller, which included requests for a left turn, the crew unilaterally initiated a right turn from the aircraft's 025° heading and commenced a climb from an altitude of 10,500 feet to FL180, when the flight was about 7 nm south of the Kathmandu VOR. The crew reported to the tower controller that the flight was climbing and the controller replied by instructing the crew to report at 16 nm for the Sierra approach. During the turn, there was more discussion between the tower controller and the flight, where it was established that the aircraft was to maintain an altitude of FL115 and was to 'proceed to Romeo' and contact the Area Control Center (ACC) controller. The flight, commencing a descent while in the turn, completed a 360° turn, momentarily rolling out on headings of 045° and 340°, and again proceeded toward the north on a heading of 025° magnetic. When the flight was about 5 nm south-west of the Kathmandu VOR, the crew contacted the ACC and stated that the aircraft was 'heading 025' and they wished to proceed to Romeo to start their approach again; adding they had 'technical problems concerned with the flight.' It was again established that the flight was to proceed to Romeo and the crew agreed to 'report over Romeo.' It was determined from the cockpit voice recorder that the crew was in the process of inserting 'Romeo' and other related navigational information in the Flight Management System, but were experiencing difficulties. The flight continued towards the north on a heading of 025° and then, at about 16 nm north, the heading was altered to the left to 005°. Slightly over one minute later, the Ground Proximity Warning System (GPWS) sounded the warning 'terrain, terrain' followed by 'whoop whoop pull-up'; the aural warning continued until impact approximately 16 seconds later. Engine thrust was increasing and 'Level Change' had been announced on the cockpit, just before the impact occurred at the 11,500-foot level of a 16,000-foot peak; the accident site was located on the 015 radial (north-north east) at 23.3 nm from the Kathmandu VOR. The aircraft was destroyed and all 113 occupants were killed.
Probable cause:
TG311 flight crew's management of the aircraft flight path wherein the flight proceeded in a northerly direction which was opposite to the cleared point Romeo to the South; ineffective radio communication between the area control centre and the TG311 flight crew which allowed the flight to continue in the wrong direction, in that the TG311 crew never provided the aircraft's VOR radial when stating DME and the controller never solicited this information and thus the aircraft's position was not transmitted at any time; and ineffective cockpit crew coordination by the TG311 crew in conducting flight navigation duties. Contributing factors were: the misleading depiction of Romeo on the operator's approach chart used by the flight crew; a flap fault, although corrected, required that the initial approach be discontinued; and radio communication difficulties between the TG311 crew and the air traffic controllers that stemmed from language difficulties and ineffective discussion of apparent unresolved problems.

Crash of a Cessna 207 Skywagon in Yakutat: 1 killed

Date & Time: Jul 29, 1992 at 0900 LT
Operator:
Registration:
N7ME
Flight Type:
Survivors:
No
Schedule:
Dry Bay - Yakutat
MSN:
207-0263
YOM:
1974
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
9500
Captain / Total hours on type:
2000.00
Aircraft flight hours:
3292
Circumstances:
The crash occurred at the 1,100 foot level of a mountainside while the airplane was flying a course roughly parallel to the mountain range. Marginal weather conditions were reported for the area. The pilot's 22-year-old son stated that in those type weather conditions his father would routinely climb up into the soup. Set a loran course for home, and sit back and relax. When close to home he would descend to vfr conditions over the flat coastal area and land. The pilot, sole on board, was killed.
Probable cause:
The pilot elected to fly an improper altitude. Contributing factors were the pilots attempt to fly VFR into IMC conditions, and the obscured weather.
Final Report:

Crash of a Vickers 798D Viscount near Mexico City: 4 killed

Date & Time: Jul 27, 1992 at 1612 LT
Type of aircraft:
Operator:
Registration:
XA-SCM
Flight Type:
Survivors:
No
Site:
Schedule:
Puebla - Mexico City
MSN:
392
YOM:
1958
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1839
Captain / Total hours on type:
63.00
Copilot / Total flying hours:
2639
Aircraft flight hours:
17213
Circumstances:
While approaching Mexico City-Benito Juarez Airport, the crew was cleared to descent from FL150 to FL120. In poor weather conditions, the crew continued the descent below FL120 when, at an altitude of 10,130 feet, the aircraft struck the slope of Mt Xocotlihuipa located 30 km east of the airport. The aircraft was destroyed and all four occupants were killed.
Probable cause:
Controlled flight into terrain after the crew failed to maintain FL120 as instructed by ATC while completing an IFR approach. It was reported that the copilot was not certified to act as a pilot on this type of aircraft. Also, the experience of the captain was limited.
Final Report:

Crash of a Lockheed C-130H Hercules near Juba

Date & Time: Jul 26, 1992 at 2030 LT
Type of aircraft:
Operator:
Flight Type:
Survivors:
No
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Juba Airport, the crew followed a holding pattern for about 15-20 minutes for unknown reasons. Then the aircraft crashed in unknown circumstances few km from the airport. Occupant's fate remains unknown.

Crash of an Antonov AN-12BK near Skopje: 8 killed

Date & Time: Jul 24, 1992 at 2023 LT
Type of aircraft:
Operator:
Registration:
CCCP-11342
Flight Type:
Survivors:
No
Site:
Schedule:
Simferopol - Skopje
MSN:
00 347 607
YOM:
1970
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
8
Aircraft flight hours:
4537
Aircraft flight cycles:
4868
Circumstances:
The aircraft departed Simferopol on a positioning flight to Skopje, carrying two passengers and six crew members. In Skopje, a load of automobile spare parts should be loaded and the aircraft was then scheduled to continue to Ukraine. A second AN-12 from the same operator approached Skopje few minutes prior to the accident and its crew decided to divert to Sofia Airport due to poor weather conditions (thunderstorm activity and heavy rain falls) at destination. On approach to Skopje, the crew modified his route to avoid the thunderstorm and followed a wrong heading of 230° instead of the planned 163°. Few minutes later, the crew was cleared for an approach to runway 34 and followed heading 140°. At an altitude of 5,200 feet on approach, the aircraft struck the slope of Mt Lisec (1,934 metres high) located 26 km south of runway 34 threshold. The wreckage was found at an altitude of 1,600 metres and all 8 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew decided to continue the approach in poor weather conditions without visual contact with the ground and unaware of his exact position. The following contributing factors were reported:
- Weather conditions were extremely difficult and unfavorable with the presence of thunderstorm activity and heavy rain falls,
- No call-out during the approach,
- Information regarding weather deterioration were not efficiently transmitted to the crew,
- Poor ATC assistance,
- The crew was unable to effectively use its Distance Measuring equipment either because of its failure or because of a momentary shutdown of the ground equipment, maybe after being switched to an emergency power unit,
- The crew's decision to continue the approach and his failure to initiate a go-around procedure.

Crash of a Vickers 816 Viscount in Ambon: 70 killed

Date & Time: Jul 24, 1992 at 1630 LT
Type of aircraft:
Operator:
Registration:
PK-RVU
Survivors:
No
Site:
Schedule:
Jakarta - Surabaya - Ujung Pandang - Ambon
MSN:
434
YOM:
1959
Flight number:
RI660
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
63
Pax fatalities:
Other fatalities:
Total fatalities:
70
Circumstances:
On approach to Ambon-Pattimura Airport, the crew encountered bad weather conditions with heavy rain falls. At an altitude of 2,300 feet, the four engine aircraft struck the slope of Mt Lalaboy located 14 km southwest of runway 04 threshold. The aircraft disintegrated on impact and all 70 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew was approaching the airport at an insufficient altitude, maybe following instrument misreading or malfunction.

Crash of a Canadair CL-215-1A10 off Isthmia

Date & Time: Jul 15, 1992
Type of aircraft:
Operator:
Registration:
1075
Flight Type:
Survivors:
Yes
MSN:
1075
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a scooping mission when the aircraft crashed in unknown circumstances off Isthmia, in the Saronic Gulf, near the Corinth Canal. Both pilots were rescued.