Crash of a PZL-Mielec AN-2R in Pyatykhatki

Date & Time: Jul 21, 2013 at 0635 LT
Type of aircraft:
Operator:
Registration:
UR-ART
Flight Phase:
Survivors:
Yes
MSN:
1G234-55
YOM:
1989
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 crop spraying flight in the Krasnoperekopsk District of the autonomous Republic of Crimea. While flying at a height of about 35-40 metres, the engine failed. The crew attempted an emergency landing in a rice paddy field near Pyatykhatki but the wheels got stuck in the soft ground and the aircraft nosed over, coming to rest upside down. While both occupants escaped uninjured, the aircraft was damaged beyond repair.
Probable cause:
A loss of engine power caused by the failure of the valve on cylinder n°9 that remained in open position due to an excessive deposit of calamine (soot).

Crash of a Britten-Norman BN-2A-21 Islander on Perico Island

Date & Time: Jul 19, 2013 at 1234 LT
Type of aircraft:
Operator:
Registration:
HP-1338MF
Survivors:
Yes
Schedule:
Isla del Rey - Panama City
MSN:
818
YOM:
1977
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Few minutes after he departed Isla del Rey Airport, while overflying the bay of Panama City, the pilot informed ATC about engine problems. Unable to reach Panama City-Marcos A. Gelabert Airport, the pilot reduced his altitude and elected to make an emergency landing on the Perico Island, some 10 km south of Panama City Airport. After touchdown, the aircraft rolled for few dozen metres before coming to rest against a container. All eight occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Partenavia P.68 Observer in the Dzalanyama Forest Reserve

Date & Time: Jul 16, 2013 at 0900 LT
Type of aircraft:
Operator:
Registration:
ZS-LSX
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tete – Lilongwe – Dar es-Salaam
MSN:
323-16-OB
YOM:
1984
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed South Africa on a flight to Tanzania with intermediate stops in Tete and Lilongwe, carrying one passenger and one pilot. The aircraft was en route to Dar es-Salaam to perform a Lidar (Laser Imaging Detection And Ranging) mission. En route, the pilot encountered engine problems and elected to make an emergency landing. Upon landing in an open field, the aircraft lost its tail and crashed landed about 45 km southwest of Lilongwe. Both occupants were rescued and the aircraft was destroyed.

Crash of a PZL-Mielec AN-2R in Terenozek: 1 killed

Date & Time: Jun 28, 2013 at 1940 LT
Type of aircraft:
Registration:
UP-A0190
Flight Phase:
Survivors:
Yes
MSN:
1G220-21
YOM:
1986
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was engaged in a crop spraying flight in Terenozek. While flying at low height, the pilot-in-command initiated a left turn when the aircraft crashed in a field, bursting into flames. The copilot was seriously injured and the captain was killed.
Probable cause:
The accident was caused by the combination of the following factors:
- Violation by the crew of the airplane flight control of the An-2,
- Loss of speed while making a turn,
- Unsatisfactory knowledge of the work area by the crew.

Crash of a PZL-Mielec AN-2 near Nekrasovka

Date & Time: Jun 28, 2013 at 1100 LT
Type of aircraft:
Operator:
Registration:
RF-00408
Flight Phase:
Survivors:
Yes
Schedule:
Khabarovsk - Samarga
MSN:
1G98-04
YOM:
1968
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft departed Khabarovsk on a charter flight to Samarga, carrying two pilots and seven fishermen flying to a fish camp. En route, the crew encountered engine problems and elected to return to Khabarovsk. Unable to maintain a safe altitude, the crew attempted to carry out an emergency landing when the airplane impacted trees and crashed in a wooded area, coming to rest in a small river. All nine occupants were injured, five of them seriously. The aircraft was damaged beyond repair.

Crash of a Rockwell 690B Turbo Commander in McClellanville: 2 killed

Date & Time: Jun 20, 2013 at 1648 LT
Operator:
Registration:
N727JA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Charleston - Charleston
MSN:
11399
YOM:
1977
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1540
Copilot / Total flying hours:
22300
Aircraft flight hours:
12193
Circumstances:
The purpose of the flight was for the pilot to accomplish a flight review with a flight instructor. According to air traffic control records, after takeoff, the pilot handling radio communications requested maneuvering airspace for airwork in an altitude block of 13,000 to 15,000 feet mean sea level (msl). About 8 minutes later, the air traffic controller asked the pilot to state his heading, but he did not respond. A review of recorded radar data revealed that, about 14,000 msl and 3 miles southeast of the accident site, the airplane made two constant-altitude 360-degree turns and then proceeded on a north-northeasterly heading for about 2.5 miles. The airplane then abruptly turned right and lost altitude, which is consistent with a loss of airplane control. The airplane continued to rapidly descend until it impacted trees and terrain on a southerly heading. No discernible distress calls were noted. The wreckage was found generally fragmented, and all of the airplane’s structural components and flight control surfaces were accounted for within the wreckage debris path. Subsequent examination of the engines revealed evidence of rotation and operation at impact and no mechanical malfunctions or failures that would have precluded normal operation.
Probable cause:
The pilot’s loss of airplane control during high-altitude maneuvering and his subsequent failure to recover airplane control. Contributing to the accident was the flight instructor’s
inadequate supervision of the pilot and his failure to perform remedial action.
Final Report:

Crash of a Cessna 340A near Boynton Beach: 1 killed

Date & Time: Jun 8, 2013 at 1002 LT
Type of aircraft:
Registration:
N217JP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fort Lauderdale – Leesburg
MSN:
340A-0435
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
16561
Captain / Total hours on type:
56.00
Aircraft flight hours:
4209
Circumstances:
Four minutes after taking off on an instrument flight rules flight, during an assigned climb to 4,000 feet, the pilot advised the departure air traffic controller that the airplane was having "instrument problems" and that he wanted to "stay VFR" (visual flight rules), which the controller acknowledged. As directed, the pilot subsequently contacted the next sector departure controller, who instructed him to climb to 8,000 feet. The pilot stated that he would climb the airplane after clearing a cloud and reiterated that the airplane was having "instrument problems." The controller told the pilot to advise when he could climb the airplane. About 30 seconds later, the pilot told the controller that he was climbing the airplane to 8,000 feet, and, shortly thereafter, the controller cleared the airplane to 11,000 feet, which the pilot acknowledged. Per instruction, the pilot later contacted a center controller, who advised him of moderate-to-heavy precipitation along his (northbound) route for the next 10 miles and told him that he could deviate either left or right and, when able, proceed direct to an intersection near his destination. The pilot acknowledged the direct-to-intersection instruction, and the controller told the pilot to climb the airplane to 13,000 feet, which the pilot acknowledged. The pilot did not advise the center controller about the instrument problems. The airplane subsequently began turning east, eventually completing about an 80-degree turn toward heavier precipitation, and the controller told the pilot to climb to 15,000 feet, but the pilot did not respond. After two more queries, the pilot stated that he was trying to maintain "VFR" and that "I have an instrument failure here." The controller then stated that he was showing the airplane turning east, which "looks like a very bad idea." He subsequently advised the pilot to turn to the west but received no further transmissions from the airplane. Radar indicated that, while the airplane was turning east, it climbed to 9,500 feet but that, during the next 24 seconds, it descended to 7,500 feet and, within the following 5 seconds, it descended to just above ground level (the ground-based radar altitude readout was 0 feet). The pilot recovered the airplane and climbed it northeast-bound to 1,500 feet during the next 20 seconds. It then likely stalled and descended northwest-bound into shallow waters of a wildlife refuge. Weather radar returns indicated that the airplane's first descent occurred in an area of moderate-to-heavy rain but that the second descent occurred in light rain. The ceiling at the nearest recording airport, located about 20 nautical miles from the accident site, was 1,500 feet, indicating that the pilot likely climbed the airplane back into instrument meteorological conditions (IMC)before finally losing control. The investigation could not determine the extent to which the pilot had planned the flight. Although a flight plan was on file, the pilot did not receive a formal weather briefing but could have self-briefed via alternative means. The investigation also could not determine when the pilot first lost situational awareness, although the excessive turn to the east toward heavier precipitation raises the possibility that the turn likely wasn't intentional and that the pilot had already lost situational awareness. Earlier in the flight, when the pilot reported an instrument problem, the two departure controllers coordinated between their sectors in accordance with air traffic control procedures, allowing him to remain low and out of IMC. Although the second controller told the pilot to advise when he was able to climb, the pilot commenced a climb without further comment. The controller was likely under the impression that the instrument problem had been corrected; therefore, he communicated no information about a potential instrument problem to the center controller. The center controller then complied with the level of service required by advising the pilot of the weather conditions ahead and by approving deviations. The extent and nature of the deviation was up to the pilot with controller assistance upon pilot request. The pilot did not request further weather information or assistance with deviations and only told the center controller that the airplane was having an instrument problem after the controller pointed out that the airplane was heading into worsening weather. Due to impact forces, only minimal autopsy results could be determined. Federal Aviation Administration medical records indicated that the 16,560-hour former military pilot did not have any significant health issues, and the pilot's wife was unaware of any preexisting significant medical conditions. The wreckage was extremely fractured, which precluded thorough examination. However, evidence indicated that all flight control surfaces were accounted for at the accident scene and that the engines were under power at the time of impact. The airplane was equipped with redundant pilot and copilot flight instruments, redundant instrument air sources, onboard weather radar, and a storm scope. The pilot did not advise any of the air traffic controllers about the extent or type of instrument problem, and the investigation could not determine which instrument(s) might have failed or how redundant systems could have been failed at the same time. Although the pilot stated on several occasions that the airplane was having instrument problems, he opted to continue flight into IMC. By doing so, he eventually lost situational awareness and then control of airplane but regained both when he acquired visual ground contact. Then, for unknown reasons, he climbed the airplane back into IMC where he again lost situational awareness and airplane control but was then unable to regain them before the airplane impacted the water.
Probable cause:
The pilot's loss of situational awareness, which resulted in an inadvertent aerodynamic stall/spin after he climbed the airplane back into instrument meteorological conditions (IMC). Contributing to the accident was the pilot's improper decision to continue flight into IMC with malfunctioning flight instrument(s).
Final Report:

Crash of a PZL-Mielec AN-2SX in Jyl-Kol: 3 killed

Date & Time: May 24, 2013 at 1002 LT
Type of aircraft:
Operator:
Registration:
EX-02015
Flight Phase:
Survivors:
No
Schedule:
Tash Kumyr - Tash Kumyr
MSN:
1G153-56
YOM:
1974
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
9818
Captain / Total hours on type:
6518.00
Copilot / Total flying hours:
4334
Copilot / Total hours on type:
2401
Aircraft flight hours:
10995
Aircraft flight cycles:
34201
Circumstances:
The crew was engaged in a fumigation mission against locusts over plantation located near Jyl-Kol, in the Jalal-Abad Province. While flying at a height of about 15 metres, the aircraft hit power cables and crashed, bursting into flames. All three occupants were killed and aircraft was destroyed by post crash fire.
Probable cause:
In violation of Section 5.1.15 of the Guidelines for Aviation Chemical Works (ACW), the Aircrew Commander (AC) decided to combine the production flight with followed inspection of the new site, taking a representative of the Customer on board. In violation of Section 5, PPLS, the passenger was seating in the co-pilot seat and this is prohibited. Before making a decision to operate a flight, the Aircrew Commander received an indicative weather forecast from the hydro meteorology experts of Osh International Airport. The revised weather forecast was not drawn up and the crew did not receive it because the flight control officer did not send an actual weather data provided by the crew after take-off, in accordance with the requirements of paragraph 8.7.7, APKR-3 . The technology of air traffic controllers’ work at Osh International Airport does not include responsibility for the transfer of information about the actual weather obtained from the crews to base aerodrome meteorological office responsible for forecasting weather and it does not specifically define the actions of air traffic services in obtaining information about an aviation accident. No changes were made in the temperature regime when performing aviation chemical works in accordance with the Guidelines for the Implementation of ACW technology in Agriculture and Forestry” designed by the Civil Aviation Ministry, USSR, and issued on December 30, 1980, Number 668/Y (these instructions were entered into operation by the order of the Director of the Civil Aviation Department under the Kyrgyz Ministry of Transport and Communications on March 20, 2009, number 188/p in the “List of Legislative Acts Regulating the Civil Aviation Activities of the Kyrgyz Republic”). Portable emergency radio beacon, PARM -406, did not function at the time of the accident. The Statute of Aeronautical Search and Rescue Service of the Kyrgyz Republic has no changes related to its reorganization in 2007.
Final Report:

Crash of a PZL-Mielec AN-2R near Chernolesskoye: 1 killed

Date & Time: May 15, 2013 at 1034 LT
Type of aircraft:
Registration:
RA-31403
Flight Phase:
Survivors:
No
Schedule:
Chernolesskoye - Chernolesskoye
MSN:
1G197-26
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5437
Captain / Total hours on type:
2527.00
Aircraft flight hours:
8523
Aircraft flight cycles:
34391
Circumstances:
The pilot, sole on board, was performing a crop spraying flight on behalf of the 'Svoboda' Agricultural Cooperation in the region of Chernolesskoye. While flying at a height of about 9 metres, trying to get altitude, the single engine aircraft successively collided with power cables and a concrete pylon, continued for about 99 metres then crashed in an open field, bursting into flames. The aircraft was destroyed by impact forces and a post impact fire and the pilot was killed.
Probable cause:
The accident occurred during crop-dusting flight due to late aircraft entry into climb for flying over PTL resulted in aircraft collision with power transmission line tower on a field under cultivation, followed by ground impact and fire. Probably late aircraft entry into climb was caused by PIC performance impairment (final crop dusting in final flight was performed after which PIC had to rest during 1,5 hours and short recreation cycle was disordered during flight operation), and also low-observability of PTL wires without day marking.
Final Report:

Crash of a Fletcher FU-24-950 in North Rawajitu: 1 killed

Date & Time: May 11, 2013 at 1125 LT
Type of aircraft:
Operator:
Registration:
PK-PNC
Flight Phase:
Survivors:
No
Schedule:
North Rawajitu - North Rawajitu
MSN:
243
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Pilot was engaged in a spraying mission over an oil palm plantation in the region of North Rawajitu, Lampung Province. Less than three minutes after takeoff, the single engine aircraft stalled and crashed in a wooded area, bursting into flames. The aircraft was destroyed by impact forces and a post impact fire and the pilot, sole on board, was killed.