Crash of a Boeing 737-2D6C in Tlemcen

Date & Time: Aug 2, 1996
Type of aircraft:
Operator:
Registration:
7T-VED
Flight Phase:
Survivors:
Yes
Schedule:
Tlemcen - Algiers
MSN:
20650
YOM:
1972
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
100
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
43293
Circumstances:
During the takeoff roll, the captain noted a difference in the engine N1 readings. He decided to abandon the takeoff procedure and initiated an emergency braking manoeuvre. Unable to stop within the remaining distance, the aircraft overran, lost its nose gear and came to rest 40 metres further. All 106 occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Grumman G-159 Gulfstream I in Lubi

Date & Time: Aug 2, 1996
Type of aircraft:
Operator:
Registration:
N190LE
Flight Type:
Survivors:
Yes
MSN:
190
YOM:
1968
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing an humanitarian flight from Kenya. Upon landing on soft ground at Lubi Airstrip, the nose gear sank then collapsed. The aircraft slid on its nose for few dozen metres and both propellers struck the ground as well. The aircraft came to rest and was damaged beyond repair. Both pilots escaped uninjured. At the time of the accident, the aircraft was still registered HK-4022X while its official new registration was N190LE since last 9 of July.

Crash of a Cessna 340A in Richland: 2 killed

Date & Time: Jul 27, 1996 at 0855 LT
Type of aircraft:
Operator:
Registration:
N341TL
Flight Type:
Survivors:
No
Schedule:
Richland - Richland
MSN:
340A-1268
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4239
Captain / Total hours on type:
1240.00
Circumstances:
The pilot-under-instruction (PUI) who possessed an expired medical, and the pilot-in-command (PIC), an ATP pilot with 1240 hours in the Cessna 340, departed on the third training flight for the PUI in the aircraft. The second training flight, flown the previous Saturday, had included single-engine work. The aircraft was observed in the vicinity of the Richland airport by witnesses, several of whom reported the left propeller turning slowly. All witnesses reported seeing the aircraft descending rapidly to the ground in a nose down attitude and several witnesses described the descent as a spin. The aircraft impacted the ground in a near vertical, nose low attitude and was destroyed by fire. Postcrash examination of the aircraft revealed the left propeller in the feathered position and power signatures on the blades of the right propeller. Disassembly of both engines revealed no pre-impact mechanical malfunction. The gear and flaps were up and the rudder trim tab showed about 5 degrees of left tab trim. The information manual for the Cessna 340 indicates that the air minimum control speed (single engine), Vmca is 82 KIAS. The manual also indicates that a more suitable airspeed for one engine inoperative training events is 91 KIAS.
Probable cause:
The pilot-in-command's allowing the aircraft's airspeed to decrease below the single-engine minimum control speed (Vmc) resulting in a stall/spin condition. Factors contributing to the accident were the pilot-in-command's allowing the left engine to be shut down as well as his allowing the aircraft's airspeed to decelerate below the manufacturer's recommended intentional one-engine inoperative airspeed. A third factor was the aircraft's low altitude at the stall/spin entry which precluded a successful recovery.
Final Report:

Crash of a Dornier DO.128-6 Skyservant in Atar

Date & Time: Jul 27, 1996
Type of aircraft:
Operator:
Registration:
5Y-BLB
Flight Type:
Survivors:
Yes
Schedule:
Lokichogio - Atar
MSN:
6001
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft was engaged in an humanitarian flight from Lokichogio to Atar on behalf of UNICEF. On approach, the pilot decided to make a low pass to analyze the runway state and to locate potential animals. During the second approach, on short final, he spotted an animal on the runway and decided to land a little further down. After touchdown, the aircraft was unable to stop within the remaining distance, overran and came to rest in a ditch. All four occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Yakovlev Yak-40 in Monrovia

Date & Time: Jul 25, 1996 at 1037 LT
Type of aircraft:
Operator:
Registration:
RA-87573
Survivors:
Yes
Schedule:
Freetown - Monrovia
MSN:
9 22 05 22
YOM:
1972
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Freetown, the three engine aircraft encountered windshear on final approach to Monrovia, lost height and struck the ground 5 metres before the runway threshold (0.8-1 meter below the runway elevation). The left main gear was torn off and the aircraft slid/rolled for about 300 metres before coming to rest. All 11 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Loss of control on short final after the aircraft encountered windshear.

Crash of a Fokker F27 Friendship 600 in Mergui: 8 killed

Date & Time: Jul 24, 1996
Type of aircraft:
Operator:
Registration:
XY-AET
Survivors:
Yes
Schedule:
Yangon - Mergui
MSN:
10433
YOM:
1970
Flight number:
UB309
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
While descending to Mergui Airport, the crew encountered poor weather conditions with heavy rain falls. On short final, the aircraft lost height and struck the ground about 250 metres short of runway 18. On impact, the undercarriage were torn off and the aircraft slid for few dozen metres before coming to rest in a 1,2 metre deep excavation located short of runway threshold. Eight passengers were killed while 16 others were seriously injured.
Probable cause:
It was reported that the crew initiated the approach while maintaining a visual contact with the runway. At an altitude of 1,500 feet, visual contact with the runway was lost due to heavy rain falls and the aircraft lost height and struck the ground in a relative flat attitude. The horizontal visibility at the time of the accident was estimated to be 1,500 metres and it is possible that the aircraft encountered windshear.

Crash of an IAI-1124 Westwind in Rosh Pina

Date & Time: Jul 23, 1996
Type of aircraft:
Operator:
Registration:
4X-AIP
Survivors:
Yes
Schedule:
Eilat - Rosh Pina
MSN:
243
YOM:
1979
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 33 at Rosh Pina Airport, the captain thought the thrust reverser systems did not work properly so he instructed the copilot to activate them again. The aircraft failed to decelerate correctly so the captain decided to veer off runway when the aircraft struck a concrete block, lost its undercarriage and came to rest. All eight occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
Runway 33 at Rosh Pina Airport is 1,100 metres long with a displaced threshold, giving a landing distance available of 975 metres. It was determined that the crew never land in the past at this airport and due to a poor flight preparation and planning, failed to identify that the runway length was insufficient for such type of aircraft in such flight configuration. No malfunction was found on the thrust reversers.

Crash of a Douglas DC-6A in Russian Mission: 4 killed

Date & Time: Jul 20, 1996 at 1506 LT
Type of aircraft:
Operator:
Registration:
N313RS
Flight Type:
Survivors:
No
Schedule:
Emmonak – Aniak
MSN:
44663
YOM:
1955
Flight number:
HU033
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
14200
Captain / Total hours on type:
7200.00
Aircraft flight hours:
38248
Circumstances:
The cargo flight was en route, when a fire erupted in or near the #3 engine. During subsequent emergency procedures, the flight crew pulled the fire handle first. Later, they feathered the #3 engine. The fire did not extinguish. During an attempt to land at a rural, intermediate airstrip, while the airplane was in the traffic pattern, witnesses saw fire coming from the area of the #3 engine. They stated the right wing buckled upward, and the airplane crashed. Examination of the wreckage revealed a failure of the master rod in the front bank of cylinders of the #3 engine. Metallurgical tests revealed a crack in the top of the master rod head, which had resulted from corrosion pits. The side of the master rod head was measured and found to be out of round. The master rod shank also fractured due to fatigue. The operator's training procedures and the Douglas Aircraft emergency checklist procedures, required that the engine's propeller be feathered first, and then the fire extinguishing system to be activated. According to information derived from the airplane's cockpit voice recorder, the flight crew reversed that order. The effectiveness of the fire suppression system is diminished if the propeller is not feathered first.
Probable cause:
Fatigue failure of the master connecting rod, which originated from corrosion pitting, subsequently compromised the engine crankcase, and resulted in a fire; and failure of the flight crew to follow emergency procedures by pulling the fire handle before feathering the propeller, which diminished the effectiveness of the fire suppression system.
Final Report:

Crash of a Mitsubishi MU-2B-36 Marquise in Scottsdale

Date & Time: Jul 20, 1996 at 0857 LT
Type of aircraft:
Operator:
Registration:
N999FA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Scottsdale - Phoenix
MSN:
676
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4559
Captain / Total hours on type:
81.00
Aircraft flight hours:
8878
Circumstances:
The right engine lost power after an uncontained engine failure during the initial takeoff climb. The airplane would not climb and the pilot was forced to land. The pilot selected a street for a forced landing area. The pilot landed gear up while maneuvering to avoid hitting street light poles and automobiles. After touchdown, the airplane slid into a block wall. A fire erupted as a result of a post impact fuel leak in the left wing. The airplane's engines were examined at the manufacturer's facilities. The right engine exhibited evidence of an uncontained separation of the second stage turbine rotor disk. Examination of the disk fragments revealed a low cycle fatigue fracture mode. The fatigue initiated from multiple areas at and adjacent to the inside diameter bore surface near the aft side of the disk. According to the engine manufacturer, the multiple indication areas were associated with uninspectable size porosity and the primary carbides in the cast material. There were no material or casting defects detected on any of the fractures through the wheel.
Probable cause:
Aan uncontained failure of the second stage turbine wheel due to fatigue. Factors were: obstructions in the forced landing area and the inability of the airplane to climb after the turbine wheel failure.
Final Report:

Crash of a Bristol 170 Freighter Mk 31M in Enstone

Date & Time: Jul 18, 1996 at 1135 LT
Type of aircraft:
Registration:
C-FDFC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Enstone - Bristol
MSN:
13218
YOM:
1954
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11000
Captain / Total hours on type:
1300.00
Copilot / Total hours on type:
60
Circumstances:
The weather at the departure airfield consisted of a light and variable wind, good visibility and a temperature of 20ºC. At the start of the take-off run the aircraft, which was being flown by the copilot, who is also an experienced pilot with some 60 hours on type, began to swing to the right. Corrective action caused it to swing to the left but, after further correction,the aircraft continued accelerating and swing to the right. The Bristol Freighter is well known for its tendency to swing on takeoff. The commander joined the co-pilot on the controls and attempted to assist in correcting the right-hand swing. It became apparent to the pilots that they would be unable to prevent the aircraft running over the edge of the runway and, as there were people standing by the edge and a small control tower building behind them, they applied full up-elevator in an effort to avoid a collision. Because of the low airspeed at which this occurred, the aircraft stalled and the left wing tip hit the ground. This caused the aircraft to turn so that it was then travelling sideways which resulted in the landing gear collapsing as it touched the runway. The aircraft then slid off the runway onto the grass. There was no fire and the only injuries were sustained by three of the aircraft passengers.
Final Report: