Crash of a PZL-Mielec AN-2T in Volosovo

Date & Time: Mar 7, 2009
Type of aircraft:
Operator:
Registration:
RF-01206
Flight Phase:
Survivors:
Yes
Schedule:
Volosovo - Volosovo
MSN:
1G98-22
YOM:
1968
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
45 seconds after takeoff, while climbing, the aircraft stalled and crashed in a snow covered field. The pilot and all 10 skydivers escaped uninjured while the aircraft was damaged beyond repair.

Crash of a GAF Nomad N.22B at Lop Buri AFB: 1 killed

Date & Time: Mar 6, 2009 at 1000 LT
Type of aircraft:
Operator:
Registration:
L9-5/25
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lop Buri – Phitsanulok
MSN:
137
YOM:
1982
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Lop Buri AFB, the left engine failed. The aircraft rolled to the left, causing the left wing to struck the runway surface. The aircraft went out of control and crashed few dozen metres further. Four crew members were seriously injured while the fifth occupant was killed.
Probable cause:
Failure of the left engine just after liftoff for unknown reasons.

Crash of a PZL-Mielec AN-2SX in Bishkek

Date & Time: Feb 22, 2009 at 1249 LT
Type of aircraft:
Operator:
Registration:
EX-68039
Flight Phase:
Survivors:
Yes
Schedule:
Bishkek - Bukhara
MSN:
1G193-11
YOM:
1981
Flight number:
GRA4571
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8215
Captain / Total hours on type:
7362.00
Copilot / Total flying hours:
7613
Copilot / Total hours on type:
4985
Aircraft flight hours:
6132
Circumstances:
The single engine aircraft departed from a small airstrip in Bishkek on a charter service (flight GRA4571) to Bukhara with two passengers and two pilots on board. About a minute after takeoff, while in initial climb, the engine lost power. The crew informed ATC about the situation and was cleared for an immediate return. Shortly later, the engine failed and the crew attempted an emergency landing in an open field located near the aerodrome. Upon landing, the aircraft collided with a small drainage ditch, lost its left main gear and both left wings before coming to rest. All four occupants escaped with minor injuries and the aircraft was damaged beyond repair.
Probable cause:
The reason for the loss of engine power in flight, most likely, was a reduction in the filing of the gasoline due to clogging of fuel filters. The appearance, structure and nature of the impurities found in the fuel on the aircraft were not characteristic of impurities accumulated in the fuel supply system in normal operating conditions. The source of the impurities in aircraft fuel system could not be found.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Kenai

Date & Time: Feb 20, 2009 at 1515 LT
Type of aircraft:
Operator:
Registration:
N5342G
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Kenai - Kenai
MSN:
854
YOM:
1956
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14300
Captain / Total hours on type:
9000.00
Copilot / Total flying hours:
799
Copilot / Total hours on type:
30
Aircraft flight hours:
9483
Circumstances:
The certificated flight instructor was familiarizing the second pilot with ski operations in a ski-equipped airplane during an instructional flight. The flight instructor reported that he took the flight controls from the second pilot to demonstrate a touch-and-go landing on a frozen, snow-covered lake. After landing to the east, the instructor said that he kept the tail of the airplane up and the airspeed just below flying speed in order to make ski tracks on the lake to check the snow conditions. About midway along the lake the instructor added full engine power and the airplane became airborne but failed to climb sufficiently to avoid colliding with an area of rising, tree-covered terrain at the departure end of the lake. The airplane sustained substantial damage to the wings, fuselage, and empennage. Postaccident examination revealed no preaccident mechanical anomalies. The instructor noted that after the accident he noticed occasional strong gusts of wind from the west.
Probable cause:
The flight instructor’s decision to attempt a touch-and-go landing toward rising terrain and with a tailwind, resulting in an in-flight collision with terrain during takeoff.
Final Report:

Crash of an Antonov AN-12B in Luxor: 5 killed

Date & Time: Feb 20, 2009 at 0418 LT
Type of aircraft:
Operator:
Registration:
S9-SVN
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kisangani – Entebbe – Luxor – Mykolaiv
MSN:
6 3 443 10
YOM:
1966
Flight number:
LFT1015
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
20000
Copilot / Total flying hours:
6397
Aircraft flight hours:
11692
Aircraft flight cycles:
6451
Circumstances:
The four engine aircraft was transferred from Kisangani to Mykolaiv, Ukraine, for maintenance purposes. Two enroute stops were scheduled in Entebbe and Luxor. Ar 0417LT, the crew was cleared for takeoff. The aircraft started rolling on runway 02 for takeoff but it kept rolling on it till it reached its end. The aircraft continued rolling in the sand drifting from the runway centerline to the right, crossing a service road and eventually crashing into a military zone located 500 metres from the runway end. The aircraft crashed into one of the buildings inside the military unit causing complete destruction of the building. The right wing also crashed into another building putting the aircraft on fire and forcing the aircraft to turn right. The aircraft kept moving forward the military unit fence (next to Tiba-Luxor road) and stopped there, crashing in its way into oil barrel. The accident resulted in the total destruction and fire of the aircraft and the fatality of its crew but no further injuries.
Probable cause:
The following factors were identified:
- Lack of available thrust which corresponded to the power of only two engines running during take off run,
- Lack of authorized maintenance of the aircraft,
- The uncoordinated crew actions in the critical situation (both pilots had previously flown as captains). The lack of coordination is confirmed by the braking trails left by the main landing gear at the end of RWY -02, based on FCOM instructions, and in case of rejected takeoff attempt, the crew had to set the throttles to idle, lower the nose gear to reach the runway and then use the propellers for braking (releasing them from the stops). Also, to reduce the roll and to maintain the direction they were to use the nose wheel steering and wheel brakes as well as emergency braking if needed. Actually the crew did neither of the above procedures, except using the main wheel brakes.
Final Report:

Crash of an Antonov AN-2 in Pskov

Date & Time: Feb 11, 2009 at 1030 LT
Type of aircraft:
Operator:
Registration:
10 yellow
Flight Phase:
Survivors:
Yes
Schedule:
Pskov - Pskov
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after take off from Pskov Airport, while climbing to a height of about 50-70 metres, the crew encountered engine problems and elected to make an emergency landing. The aircraft lost height and crashed in a snow covered field located near the airport and came to rest. All 13 occupants escaped uninjured while the aircraft was damaged beyond repair. All passengers were skydivers (paratroopers) from the Marine Corps.
Probable cause:
Engine failure for unknown reasons.

Crash of a Cessna 650 Citation III in Trigoria: 2 killed

Date & Time: Feb 7, 2009 at 0602 LT
Type of aircraft:
Operator:
Registration:
I-FEEV
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rome - Bologna
MSN:
650-0105
YOM:
1986
Flight number:
AOE301
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6077
Captain / Total hours on type:
877.00
Copilot / Total flying hours:
3000
Copilot / Total hours on type:
58
Aircraft flight hours:
6977
Circumstances:
The crew was engaged in a positioning flight from Rome to Bologna to pick up a medical team for an ambulance mission. At 0554LT, the crew was cleared for takeoff. The aircraft departed Rome-Ciampino Airport runway 15 at 0600LT. During initial climb, after being cleared to Bolsena at FL240, the aircraft entered an uncontrolled descent and crashed near a cattle barn. The aircraft disintegrated on impact and both pilots were killed. At the time of the accident, weather conditions were as follow: wind from 140 at 18 knots, light rain, few at 1,800 feet, broken 3,000 feet and scattered at 7,000 feet with an OAT of 13° C.
Probable cause:
The cause of the accident was due to an impact with the ground resulting from the loss of control of the aircraft by the captain, who was also the PF. It appears very likely that during the initial phase inadequate attention was replaced by a phase of spatial disorientation, resulting in a loss of situational awareness, which prompted an inadequate intervention on the flight controls by the PF, resulting in total loss of control of the aircraft (having accentuated the tilt to the left wing, instead of leveling the aircraft). It is reasonable to assume that the PF, based on the conviction of being in a right turn for Bolsena in IMC night conditions, misinterpreted the unusual turn, using the controls in order to accentuate the bank angle to the left, drastically reducing the vertical component of lift. This turn has consequently caused the aircraft to assume an attitude of increasing bank, a condition that has been aggravated by the continued application on the controls of a positive load factor in order to stop the sudden loss of altitude, without first leveling the wings. Or the aircraft is stabilized in a pronounced downward spiral to the left. The first officer (PNF), engaged in the management of navigation equipment, has created the unusual turn of the aircraft in conjunction with the commander (PF). Nevertheless, the considerable gradient of experience on the airplane and hierarchy within the organization between the captain and the first officer has probably prevented him to intervene in a more directive or authoritative way in the recovery phase of the situation. Also contributing to the outcome of the event was the lack of detail in the definition of the duties of the crew procedures and inadequate adherence to the basic principles of CRM/MCC, with reference to the monitoring and statement of the navigation modes active, navigation procedures and in particular to the lack of requests for inclusion of turns and routes, the deficiency in the performance of controls and optimization of automation that can lighten the workload in a time unfavorable from the point of view of the circadian rhythm and IMC night. In this respect, it seems fitting to remember the problem of spatial disorientation, although known and studied for decades, is still relevant, and that the only way to counter it is the application of proper use of instruments in compliance with the basic principles of CRM/MCC, which should be part of the normal operating procedures of an operator. This is especially true when working outside of normal circadian rhythms, when it is most easily seen a slowing of cognitive processes.
Final Report:

Crash of a Piper PA-31 Navajo Chieftain in Darwin

Date & Time: Feb 6, 2009 at 0840 LT
Operator:
Registration:
VH-TFX
Flight Phase:
Survivors:
Yes
Schedule:
Darwin – Maningrida
MSN:
31-8152143
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Darwin Airport, while in initial climb, one of the engine failed. The pilot declared an emergency and elected to return but eventually attempted to ditch the aircraft that came to rest in shallow water about 200 metres offshore. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a De Havilland DHC-6 Twin Otter 100 in La Ronge

Date & Time: Feb 4, 2009 at 0915 LT
Operator:
Registration:
C-FCCE
Flight Phase:
Survivors:
Yes
Schedule:
La Ronge – Deschambeault Lake
MSN:
8
YOM:
1966
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14000
Captain / Total hours on type:
11000.00
Copilot / Total flying hours:
625
Copilot / Total hours on type:
425
Circumstances:
The aircraft was taking off from a ski strip east of and parallel to Runway 36 at La Ronge. After the nose ski cleared the snow, the left wing rose and the aircraft veered to the right and the captain, who was the pilot flying, continued the take-off. The right ski, however, was still in contact with the snow. The aircraft became airborne briefly as it cleared a deep gully to the right of the runway. The aircraft remained in a steep right bank and the right wing contacted the snow-covered ground. The aircraft flew through a chain link fence and crashed into trees surrounding the airport. The five passengers and two crewmembers evacuated the aircraft with minor injuries. There was a small fire near the right engine exhaust that was immediately extinguished by the crew.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Contamination on the wings of the aircraft was not fully removed before take-off. It is likely that asymmetric contamination of the wings created a lift differential and a loss of lateral control.
2. Although the operator was not authorized for short take-off and landing (STOL) take-off on this aircraft, the crew conducted a STOL take-off, which reduced the aircraft’s safety margin relative to its stalling speed and minimum control speed.
3. As a result of the loss of lateral control, the slow STOL take-off speed, and the manipulation of the flaps, the aircraft did not remain airborne and veered right, colliding with obstacles beside the ski strip.
Findings as to Risk:
1. The out of phase task requirements regarding the engine vibration isolator assembly, as listed in the operator’s maintenance schedule approval, results in a less than thorough inspection requirement, increasing the likelihood of fatigue cracks remaining undetected.
2. The right engine inboard and top engine mounts had pre-existing fatigue cracks, increasing the risk of catastrophic failure.
Other Findings:
1. The cockpit voice recorder (CVR) contained audio of a previous flight and was not in operation during the occurrence flight. Minimum equipment list (MEL) procedures for logbook entries and placarding were not followed.
2. The Transwest Air Limited safety management system (SMS) did not identify deviations from standard operating procedures.
Final Report:

Crash of an AMI Turbo DC-3-65TP in Mojave

Date & Time: Feb 4, 2009 at 0852 LT
Type of aircraft:
Operator:
Registration:
N834TP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mojave - Mojave
MSN:
12590
YOM:
1947
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18000
Captain / Total hours on type:
1326.00
Aircraft flight hours:
17277
Circumstances:
During the takeoff roll, the airplane began to drift to the right. Despite the certified flight instructor's and student's attempts, they were unable to stop the yaw and drift. As the airplane was about to depart the runway, the pilots did not reduce the throttles or apply brakes as they felt that it would be safer to attempt to get airborne. After departing the runway surface, the airplane collided with a series of berms, which sheared off the left landing gear and left engine. The right landing gear collapsed, and the airplane came to rest in a nose down attitude. Post accident e examination revealed that the student pilot had inadvertently set the rudder trim to the full right position when he adjusted the rudder pedals during the prestart checks. The rudder trim was in the full right position for the takeoff, and found in the same position upon post accident inspection.
Probable cause:
The student pilot failed to follow the checklist and set the takeoff trim properly prior to takeoff resulting in a loss of directional control. Contributing to the accident were the certified flight instructor's inadequate supervision and delayed remedial action.
Final Report: