Country
code
Krasnodar Krai
Crash of a PZL-Mielec AN-2R in Goryachy Klyuch
Date & Time:
May 6, 2010 at 1026 LT
Registration:
RA-40373
Survivors:
Yes
Schedule:
Goryachy Klyuch - Goryachy Klyuch
MSN:
1G222-52
YOM:
1986
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
4120
Aircraft flight cycles:
18409
Circumstances:
Shortly after take off from an open field located in Goryachy Klyuch, Krasnodar krai, while at a height of about 15 metres, the single engine aircraft stalled and crashed on a river shore. Both pilots were injured and the aircraft was damaged beyond repair. The crew was supposed to treat a wooded area with chemical products and the aircraft was carrying about 700 liters of this product at the time of the accident.
Probable cause:
The accident of airplane AN-2 RA-40373 was the result of the nose striking the ground during the execution of a forced landing due to shutdown of the ASz-62IR engine while in the process of taking off, most likely due to ingress of water into the carburetor from the fuel system of the aircraft, which led to the shutdown of the engine.
The cause of the accident was a combination of the following factors:
- Failure to comply with guidelines in part: checking facility for storing and dispensing aviation fuels and lubricants, monitoring and verification of the fuel sludge discharge after refueling for the lack of water and solids;
- Execution of a forced landing straight ahead outside the landing area on difficult terrain, covered with forests, a rugged ravine and a creek.
The cause of the accident was a combination of the following factors:
- Failure to comply with guidelines in part: checking facility for storing and dispensing aviation fuels and lubricants, monitoring and verification of the fuel sludge discharge after refueling for the lack of water and solids;
- Execution of a forced landing straight ahead outside the landing area on difficult terrain, covered with forests, a rugged ravine and a creek.
Final Report:
Crash of a PZL-Mielec AN-2R near Primorsko-Akhtarsk
Date & Time:
Jun 13, 2009 at 1130 LT
Operator:
Registration:
RF-00428
Survivors:
Yes
MSN:
1G230-11
YOM:
1988
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot was completing a crop-spraying mission when the engine failed. He attempted an emergency landing when the aircraft collided with power cables and crashed in a field located about 20 km southeast of Primorsko-Akhtarsk, bursting into flames. The aircraft was destroyed by a post crash fire and the pilot was injured.
Probable cause:
Engine failure for unknown reasons.
Crash of a PZL-Mielec AN-2 in Dmitrievskaya
Date & Time:
Jun 28, 2008 at 1930 LT
Registration:
RF-00403
Survivors:
Yes
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot, sole on board, was performing a local test flight following an engine overhaul. En route, the engine lost power. The pilot attempted an emergency landing when the aircraft crashed in an open field located 6 km northeast of Dmitrievskaya, bursting into flames. The aircraft was destroyed and the pilot was seriously injured.
Probable cause:
Engine failure for unknown reasons.
Crash of an Airbus A320-211 off Sochi: 113 killed
Date & Time:
May 3, 2006 at 0213 LT
Operator:
Registration:
EK-32009
Survivors:
No
Schedule:
Yerevan - Sochi
MSN:
547
YOM:
1995
Flight number:
RNV967
Crew on board:
8
Crew fatalities:
Pax on board:
105
Pax fatalities:
Other fatalities:
Total fatalities:
113
Captain / Total hours on type:
1436.00
Copilot / Total hours on type:
1022
Aircraft flight hours:
28234
Aircraft flight cycles:
14376
Circumstances:
On 2 May 2006 the Armavia A320, registered EK-32009, was undertaking passenger flight RNV 967 from Zvartnots (Yerevan, Armenia) to Adler (Sochi, Russia). Preliminary preparation of the crew was conducted on 23-24 May 2006 under the guidance of the airline’s Flight Director, in accordance with the requirements of ROLRGA RA-2000, Section 7.2.1. Pre-flight briefing of the crew was conducted on the day of departure, under the guidance of the Captain, in accordance with the requirements of ROLRGA RA-2000, Section 8.2.1 On 2 May 2006 at 19.30 the crew passed the pre-flight medical examination. The crew’s pre-flight rest period exceeded 24 hours. In accordance with ROLRGA RA-2000 and Work-Rest Norms for civil aircraft crews from the Republic of Armenia, each crew member is individually responsible for adherence to the pre-flight rest regime. It should be noted that it was difficult for the crew to take adequate rest during the day before the night flight, due to impairment of bio-rhythms. That is most likely why, in their cockpit conversations the crew members mentioned that they had not got enough sleep. In order to make their decision for departure, the crew obtained the observed weather data and the weather forecast for the takeoff, landing and alternate aerodromes that met the requirements for IFR flights. According to the documents submitted, the airplane takeoff weight and the centre of gravity were 62,712 kg and 29.9% mean aerodynamic chord, i.e. within the A320 FCOM limitations. There were 113 occupants on board: 105 passengers (including 5 children and 1 baby), 2 pilots, 5 flight attendants and 1 engineer. The airplane took off from Zvartnots airport at 20:47. Takeoff, climb and cruise were uneventful. The first communication between the Sochi approach controller and the crew took place at 21:10:20. At that moment the airplane was beyond the coverage area of Sochi aerodrome radar. Up until 21:17 the approach controller and the crew discussed the observed and forecast weather, and as a result the crew decided to return to Yerevan. At 21:26:37, after the decision had already been made, the crew asked the controller about the latest observed weather. At 21:30:49 the controller informed the crew that visibility was 3,600 m and the cloud ceiling 170 m. At 21.31.14 the crew decided to continue the flight to Sochi airport. The next communication with the approach controller was at 22:00:45. At that moment the airplane was descending to an altitude of 3,600 m heading to GUKIN point and was being tracked by the Sochi radar. The approach controller cleared the airplane for descent to 1,800 m and reported the observed weather at Sochi, as at 22:00, for runway 06, which was above the aerodrome minimum. Then the crew was handed over to the holding and tower controllers, and was cleared for descent to 600 m, as per aerodrome pressure QNH 1016 hPa, before entering the turn to final. While performing the turn to final, the runway extended centreline was overshot. Having eliminated the deviation, the airplane started descending along the glide slope, following the approach pattern. At 22:10:45 the crew reported extension of the landing gear and their readiness for landing. In response they were advised of the distance of 10 km and weather 4000 x 190, and were cleared for landing. However, about 30 seconds later, the controller advised the crew of the observed cloud ceiling at 100 m and instructed them to stop their descent and carry out a right turn and climb up to 600 m and also to get in touch with the holding controller. The last communication with the crew was at 22:12:35. After that the crew did not respond to any of the controller’s calls. At 22:13:03 the airplane struck the water, was destroyed and sank.
Probable cause:
The fatal crash of the Armavia A320 EK-32009 was a CFIT accident that happened due to collision with the water while carrying-out a climbing manoeuvre after an aborted approach to Sochi airport at night with weather conditions below the established minima for runway 06. While performing the climb with the autopilot disengaged, the Captain, being in a psychoemotional stress condition, made nose down control inputs due to the loss of pitch and roll awareness. This started the abnormal situation. Subsequently the Captain's inputs in the pitch channel were insufficient to prevent development of the abnormal situation into the catastrophic one. Along with the inadequate control inputs of the Captain, the contributing factors to development of the abnormal situation into the catastrophic one were also the lack of necessary monitoring of the aircraft descent parameters (pitch attitude, altitude, vertical speed) by the co-pilot and the absence of proper reaction by the crew to the EGPWS warning.
Final Report:
Crash of a PZL-Mielec AN-2R in Sladky Liman: 2 killed
Date & Time:
Aug 8, 2002 at 1920 LT
Registration:
RA-33322
Survivors:
No
MSN:
1G225-41
YOM:
1987
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
In the evening, a pilot and a technician took off for a local flight. After liftoff, at a height of about 10 metres, the aircraft rolled to the left and impacted the concrete support of a power line then crashed 38 metres further, bursting into flames. Both occupants were killed.
Probable cause:
It was determined that both occupants were intoxicated at the time of the accident. They took off while the ailerons were still locked. Poor flight preparation.
Crash of a PZL-Mielec AN-2R in Nekrasovskaya
Date & Time:
Apr 25, 2001 at 1730 LT
Registration:
RA-17832
Survivors:
Yes
Schedule:
Nekrasovskaya - Nekrasovskaya
MSN:
1G204-33
YOM:
1983
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was dispatched at Nekrasovskaya to perform a crop spraying mission for the farm 'Rossia'. While flying at an insufficient height of 5 metres, the copilot saw power cables and elected to gain height to avoid the collision. But the captain took over control and plunged the aircraft to pass below the line. The power cables struck the tail that was partially torn off. The aircraft nosed down and crashed in an open field, bursting into flames. Both pilots were seriously injured and the aircraft was destroyed by fire.
Probable cause:
The accident was the consequence of the combination of the following factors:
- Poor flight preparation on part of the crew who failed to locate various obstacles situated in and around the spraying area,
- The captain took the decision to complete the mission at an insufficient height of five metres while the minimum height was fixed at 20 metres,
- Poor crew coordination.
- Poor flight preparation on part of the crew who failed to locate various obstacles situated in and around the spraying area,
- The captain took the decision to complete the mission at an insufficient height of five metres while the minimum height was fixed at 20 metres,
- Poor crew coordination.
Crash of an Antonov AN-2 in Novoshcherbinovskaya
Date & Time:
Jun 5, 1997
Registration:
RA-02555
Survivors:
Yes
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a crop spraying mission on behalf of the the collective farm 'Dimitrova' in Novoshcherbinovskaya. After takeoff, while climbing to a height of 10 metres, the engine lost power. The captain attempted to make an emergency landing when the aircraft struck the ground, nosed over and came to rest upside down, bursting into flames. Both occupants were slightly injured and the aircraft was destroyed.
Probable cause:
Loss of engine power after takeoff for unknown reasons.
Crash of an Antonov AN-24RV in Krasnodar
Date & Time:
Dec 21, 1995
Operator:
Registration:
RA-46473
Survivors:
Yes
Schedule:
Trabzon - Krasnodar
MSN:
27308001
YOM:
1972
Crew on board:
5
Crew fatalities:
Pax on board:
39
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Trabzon, the crew started the descent to Krasnodar Airport by night. Upon landing, the aircraft bounced five times and a positive acceleration of 3,3 g was recorded. After the fifth bounce, the nose gear collapsed and the aircraft slid for few dozen metres before coming to rest. All 44 occupants escaped uninjured while the aircraft was damaged beyond repair. It was reported that the crew failed to prepare the flight according to published procedure and at the time of the accident, the CofG was too far aft, causing the aircraft to be unstable.
