Crash of an Antonov AN-32A in Baykit

Date & Time: Nov 22, 1996 at 1306 LT
Type of aircraft:
Registration:
RA-48104
Survivors:
Yes
Schedule:
Tura – Vanavara – Baykit – Yeniseysk
MSN:
16 02
YOM:
1988
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was damaged beyond repair when it veered off runway and the crew tried to get back on the runway without help. The aircraft went out of control, crossed the runway and hit the mast of a powerline and a parapet with more than 3.5 g, suffering structural damage. All 5 crew members and 22 passengers (19 of them illegal ones) escaped unhurt.

Crash of a Beechcraft 1900C-1 in Quincy: 12 killed

Date & Time: Nov 19, 1996 at 1701 LT
Type of aircraft:
Operator:
Registration:
N87GL
Survivors:
No
Schedule:
Chicago – Burlington – Quincy
MSN:
UC-087
YOM:
1989
Flight number:
UA5925
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
4000
Captain / Total hours on type:
700.00
Copilot / Total flying hours:
1950
Copilot / Total hours on type:
800
Aircraft flight hours:
18446
Aircraft flight cycles:
26797
Circumstances:
The Beechcraft 1900C, N87GL, was in its landing roll on runway 13, and the Beechcraft A90, N1127D, was in its takeoff roll on runway 04. The collision occurred at the intersection of the two runways. The flight crew of the Beechcraft 1900C had made appropriate efforts to coordinate the approach and landing through radio communications and visual monitoring; however they mistook a Cherokee pilot's transmission (that he was holding for departure on runway 04) as a response from the Beechcraft A90 to their request for the Beechcraft A90's intentions, and therefore mistakenly believed that the Beechcraft A90 was not planning to take off until after the Beechcraft 1900C had cleared the runway. The failure of the Beechcraft A90 pilot to announce over the common traffic advisory frequency his intention to take off created a potential for collision between the two airplanes.
Probable cause:
The failure of the pilots in the King Air A90 to effectively monitor the common traffic advisory frequency or to properly scan for traffic, resulting in their commencing a takeoff roll when the Beechcraft 1900C (United Express flight 5925) was landing on an intersecting runway. Contributing to the cause of the accident was the Cherokee pilot's interrupted radio transmission, which led to the Beechcraft 1900C pilot's misunderstanding of the transmission as an indication from the King Air that it would not take off until after flight 5925 had cleared the runway. Contributing to the severity of the accident and the loss of life were the lack of adequate aircraft rescue and firefighting services and the failure of the air stair door on the Beechcraft 1900C to be opened.
Final Report:

Crash of a Lockheed PV-1 Ventura in Richmond

Date & Time: Nov 18, 1996 at 1335 LT
Type of aircraft:
Operator:
Registration:
VH-SFF
Flight Type:
Survivors:
Yes
Schedule:
Richmond - Richmond
MSN:
5378
YOM:
1943
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11444
Captain / Total hours on type:
25.00
Circumstances:
The aircraft was approaching to land after completing a handling display during an Open Day at RAAF Richmond. At an altitude of about 800 feet, on the base leg for runway 28, both engines stopped simultaneously and without warning. As there was insufficient altitude to reach the field for a power off landing, the flaps and landing gear were retracted and a successful forced landing carried out into a cleared field short of the airfield. The crew evacuated the aircraft without injury.
Probable cause:
A subsequent investigation failed to positively determine the cause of the simultaneous stoppage of both engines. A large quantity of fuel remained in the tanks and no defects were found with either of the engine fuel systems. The engine ignition systems were tested and functioned normally after the accident. The design of this aircraft, as with other ex-military multi-reciprocating engine types, includes a master ignition switch. The switch is guarded, and when turned off results in the termination of ignition to all engines simultaneously. The switch was removed from the aircraft after the accident and subjected to extensive testing, including vibration tests, but could not be faulted. It was noted however that ignition isolation resulted with only a small movement of the switch from the ON position. The most likely reason for the sudden stoppage of both engines was movement of the master ignition switch from the ON position, possibly as the result of vibration or by a crew member inadvertently bumping the switch prior to landing.
Final Report:

Crash of a Grumman S-2E Tracker in Bahía Blanca

Date & Time: Nov 12, 1996
Type of aircraft:
Operator:
Registration:
0703/2-AS-24
Flight Type:
Survivors:
Yes
Schedule:
Bahía Blanca - Bahía Blanca
MSN:
325
YOM:
1957
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training flight at Bahía Blanca-Comandante Espora Airbase. For unknown reasons, the aircraft landed on its belly and came to rest. Both pilots escaped uninjured.

Crash of a Cessna 340A in Pawtucket

Date & Time: Nov 7, 1996 at 0900 LT
Type of aircraft:
Operator:
Registration:
N36JM
Flight Type:
Survivors:
Yes
Schedule:
Nantucket – Pawtucket
MSN:
340A-0749
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3213
Captain / Total hours on type:
153.00
Aircraft flight hours:
2058
Circumstances:
The pilot was conducting the localizer approach to runway 15 when the aircraft overran the runway and struck an obstacle. According to the pilot, a loss of power occurred in both engines as he attempted to do a missed approach, and the airspeed subsequently decreased from 105 to 80 knots. The pilot reported that he pushed the nose over to avoid a stall, broke out of the clouds over the mid-point of the runway, landed long and continued off the end of the runway into terrain and a tower structure. A witness reported the 'aircraft broke out of the clouds just above the trees north of runway 5 and west of runway 15. Reportedly, the aircraft as being banked from a right to left to get aligned with runway 5, flaps appeared to be up, and the gear was down. The witness said the engines sounded to be at idle and at high rpm, and the aircraft appeared to be 50 feet above the ground at midfield when it went out of sight behind hangar.' The weather observed at the time of the accident was in part: ceiling 100 feet overcast, visibility 0.5 mile with fog and rain. The published landing minimums for the approach was ceiling 400 feet and visibility 0.75 mile. Recorded radar data of the flight indicated a descent below the minimum descent altitude at a constant airspeed. Both engines started immediately and ran during a postaccident check of the aircraft.
Probable cause:
Failure of the pilot to comply with the published instrument approach procedure, by continuing the ILS approach below the decision height, rather than performing a missed approach; and his failure to attain a proper touchdown point for the continued landing. Factors relating to the accident were: weather below approach minimums, wet runway, and hydroplaning conditions.
Final Report:

Crash of an Antonov AN-24RV in Ust-Nera

Date & Time: Nov 6, 1996
Type of aircraft:
Operator:
Registration:
RA-47356
Survivors:
Yes
Schedule:
Yakutsk - Khandyga - Ust-Nera
MSN:
67310605
YOM:
1976
Flight number:
SKH017
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
24
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Ust-Nera Airport, following an uneventful flight from Khandyga, the crew mistook the new runway 85 (still under construction) for the operational runway 75 in poor visibility. When ATC realized this, they twice ordered the crew to go around but the crew failed to comply and touched down on runway 85. During the landing run, at a speed of 158 km/h, the captain attempted to go around but the check pilot aborted this attempt some seconds later. The confused flight engineer retracted the landing gear and the aircraft came to rest on its belly, suffering substantial damage. All 5 crew and 24 passengers escaped unhurt.
Probable cause:
The following findings were reported:
- Poor approach and landing planning,
- The crew descended below MDA without visual contact with the runway,
- The crew failed to comply with ATC instructions,
- Poor crew coordination,
- The flight engineer mistakenly raised the landing gear while the aircraft was still on ground.

Crash of a Swearingen SA226TC Metro II in Gods River

Date & Time: Nov 1, 1996 at 1423 LT
Type of aircraft:
Operator:
Registration:
C-FHOZ
Survivors:
Yes
Schedule:
Winnipeg – Gods Lake Narrows – Gods River – Winnipeg
MSN:
TC-283
YOM:
1979
Flight number:
PAG207
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Gods River Airport runway 27, the right main gear struck a snow berm located 105 metres short of runway threshold. The crew continued the approach and the aircraft landed 99 metres past the runway threshold. On touchdown, the right main gear collapsed. The aircraft slid fore few dozen metres then veered off runway to the right and came to rest. All seven occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of an Embraer EMB-110P1 Bandeirante in Flores: 14 killed

Date & Time: Nov 1, 1996 at 0810 LT
Registration:
TG-TPA
Survivors:
No
Schedule:
Guatemala - Flores
MSN:
110-313
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
14
Circumstances:
The approach to Flores-Santa Elena was completed in poor weather conditions. While descending at an altitude of 900 feet, the aircraft struck the slope of a mountain located 8 km from the runway threshold. All 14 occupants were killed, 13 citizen from Guatemala and one Mexican.

Crash of an Antonov AN-12 in Nizhnevartovsk

Date & Time: Nov 1, 1996
Type of aircraft:
Registration:
RA-11851
Flight Type:
Survivors:
Yes
MSN:
4 020 03
YOM:
1964
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach, the aircraft lost height and struck the ground short of runway threshold. The undercarriage were torn off and the aircraft bounced before coming to rest few dozen metres further. All 15 occupants escaped uninjured while the aircraft was damaged beyond repair. At the time of the accident, the total weight of the aircraft was nine tons above the maximum landing weight.

Crash of a Yakovlev Yak-40 in Khanty-Mansiysk: 5 killed

Date & Time: Oct 26, 1996 at 2044 LT
Type of aircraft:
Operator:
Registration:
RA-88257
Survivors:
Yes
Schedule:
Tyumen - Khanty-Mansiysk
MSN:
9 71 12 52
YOM:
1977
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
5
Aircraft flight hours:
21765
Aircraft flight cycles:
16947
Circumstances:
Following an uneventful flight from Tyumen, the aircraft was approaching Khanty-Mansiysk Airport by night and poor weather conditions due to snow falls and a visibility limited to 5,300 metres with a cloud base at 400 metres. On final approach, the aircraft descended below the MDA when it landed at a speed of 190 km/h on an helipad located 159 metres to the left of the runway and 950 metres from its threshold. The aircraft collided with three parked helicopters and crashed. Both pilots, a third crew member and two passengers were killed. The aircraft as well as three helicopter registered RA-22313, RA-25144 and RA-25939 were destroyed.
Probable cause:
The following findings were reported:
- The crew did not have sufficient information about the deterioration of the weather conditions at destination,
- The crew decided to continue the approach in a visibility that was below minimums,
- The power of the ground light system located at the helipad was higher than the runway light system, in conditions of limited visibility, which caused a wrong perception of the crew.