Crash of a PZL-Mielec AN-2R in Goryachy Klyuch

Date & Time: May 6, 2010 at 1026 LT
Type of aircraft:
Operator:
Registration:
RA-40373
Flight Phase:
Survivors:
Yes
Schedule:
Goryachy Klyuch - Goryachy Klyuch
MSN:
1G222-52
YOM:
1986
Country:
Region:
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.
Final Report:

Crash of an Antonov AN-2 in Marianivka

Date & Time: May 4, 2010 at 0817 LT
Type of aircraft:
Operator:
Flight Phase:
Survivors:
Yes
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after take off from a field located 3 km from Marianivka, west from Odessa, while climbing to a height of about 150 metres, the engine failed. The crew attempted an emergency landing when the aircraft stalled and crashed, bursting into flames. Both occupants were injured and the aircraft was destroyed by a post crash fire.
Probable cause:
Engine failure during initial climb for unknown reasons.

Crash of a Fletcher FU24-950 Fletcher in Waipukurau

Date & Time: Apr 20, 2010 at 1420 LT
Type of aircraft:
Operator:
Registration:
ZK-EGT
Flight Phase:
Survivors:
Yes
Schedule:
Waipukurau - Waipukurau
MSN:
242
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot was engaged in a crop spraying mission on a plantation close to a farm located in Waipukurau. The accident occurred on takeoff in unknown circumstances. While the pilot was seriously injured, the aircraft was damaged beyond repair.

Crash of an Antonov AN-74 in Ivanovo

Date & Time: Mar 30, 2010 at 1400 LT
Type of aircraft:
Operator:
Registration:
RA-74017
Flight Phase:
Survivors:
Yes
Schedule:
Ivanovo - Moscow
MSN:
471 95 015
YOM:
2004
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Just after liftoff, at a height of about 3 meters, left engine thrust reverser deployed. The takeoff procedure was aborted but the aircraft veered off runway and came to rest in a field with the cockpit partially separated. All five occupants were injured, both pilots seriously. The aircraft was damaged beyond repair. Configured in a VIP version, it was used by the FSB's Director Nikolai Patrushev and flying back to Moscow at the time of the accident.
Probable cause:
The thrust reverser deployed accidentally on the left engine after rotation due to inappropriate maintenance.

Crash of a Piper PA-46-310P Malibu in Roanoke: 1 killed

Date & Time: Mar 30, 2010 at 1310 LT
Registration:
N6913Z
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Roanoke – Charlottesville
MSN:
46-8508073
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3000
Aircraft flight hours:
956
Circumstances:
About one minute after takeoff, the pilot reported to the air traffic controller that the airplane's control wheels were locked. The controller subsequently cleared the pilot to land on any runway. No further transmissions were received from the pilot and the airplane continued straight ahead. Witnesses observed the airplane in a slow, level descent, until it impacted wires and then the ground. During a postaccident examination of the airplane, flight control continuity was confirmed to all the flight controls. Due to the impact and post-crash fire damage, a cause for the flight control anomaly, as reported by the pilot, could not be determined; however, several unsecured cannon plugs and numerous unsecured heat damaged wire bundles were found lying across the control columns forward of the firewall. Examination of the airplane logbooks revealed the most recent maintenance to the flight controls was performed about four months prior to the accident. The airplane had flown 91 hours since then.
Probable cause:
A malfunction of the flight controls for undetermined reasons.
Final Report:

Crash of an Embraer EMB-120ER Brasília in Darwin: 2 killed

Date & Time: Mar 22, 2010 at 1009 LT
Type of aircraft:
Operator:
Registration:
VH-ANB
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Darwin - Darwin
MSN:
120-116
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
8217
Captain / Total hours on type:
3749.00
Copilot / Total flying hours:
5664
Copilot / Total hours on type:
3085
Aircraft flight hours:
32799
Aircraft flight cycles:
33700
Circumstances:
Aircraft crashed moments after takeoff from runway 29 at Darwin Airport, Northern Territory, fatally injuring both pilots. The flight was for the purpose of revalidating the command instrument rating of the pilot under check and was under the command of a training and checking captain, who occupied the copilot’s seat. The takeoff included a simulated engine failure. Data from the aircraft’s flight recorders was used to establish the circumstances leading to the accident and showed that the pilot in command (PIC) retarded the left power lever to flight idle to simulate an engine failure. That introduced a simulated failure of the left engine and propeller autofeathering system. The increased drag from the ‘windmilling’ propeller increased the control forces required to maintain the aircraft’s flightpath. The pilot under check allowed the speed to decrease and the aircraft to bank toward the inoperative engine. Additionally, he increased power on the right engine, and engaged the yaw damper in an attempt to stabilize the aircraft’s flight. Those actions increased his workload and made control of the aircraft more difficult. The PIC did not restore power to the left engine to discontinue the manoeuvre. The few seconds available before the aircraft became uncontrollable were insufficient to allow ‘trouble shooting’ and deliberation before resolving the situation.
Probable cause:
• The pilot in command initiated a simulated left engine failure just after becoming airborne and at a speed that did not allow adequate margin for error.
• The pilot in command simulated a failure of the left engine by selecting flight idle instead of zero thrust, thereby simulating a simultaneous failure of the left engine and its propeller autofeather system, instead of a failure of the engine alone.
• The pilot under check operated the aircraft at a speed and attitude (bank angle) that when uncorrected, resulted in a loss of control.
• The pilot under check increased his workload by increasing torque on the right engine and selecting the yaw damper.
• The pilot in command probably became preoccupied and did not abandon the simulated engine failure after the heading and speed tolerance for the manoeuvre were exceeded and before control of the aircraft was lost.
Final Report:

Crash of a Britten-Norman BN-2A-21 Islander in Kodiak

Date & Time: Mar 15, 2010 at 1243 LT
Type of aircraft:
Operator:
Registration:
N663SA
Flight Phase:
Survivors:
Yes
Schedule:
Kodiak - Old Harbor
MSN:
4
YOM:
1967
Flight number:
8D501
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7370
Captain / Total hours on type:
106.00
Aircraft flight hours:
11348
Circumstances:
The airline transport pilot was taking off on a passenger flight under Title 14, CFR Part 135, when the accident occurred. He reported that during takeoff the wind was reported from 290-300 degrees, at 15 knots, gusting to 27 knots. He chose to make an intersection takeoff on runway 25 at its intersection with runway 29, rather than use the full length of runway 29. He said his airspeed did not develop as quickly as he had anticipated, and that with his airspeed lagging and poor climb performance, he realized the airplane was not going to clear the ridge at the end of the runway. He said he initiated a right descending turn to maintain his airspeed, but impacted trees alongside the runway. He reported that the airplane sustained substantial damage to the wings and fuselage when it impacted trees. He said there were no mechanical problems with the airplane prior to the accident.
Probable cause:
The pilot's failure to maintain clearance from rising terrain during takeoff resulting in collision with trees.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Tegucigalpa: 3 killed

Date & Time: Mar 10, 2010 at 1405 LT
Operator:
Registration:
TG-JYM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tegucigalpa – La Mesa
MSN:
421B-0403
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Three minutes after takeoff from Tegucigalpa-Toncontin Airport, while in initial climb, the twin engine aircraft went out of control and crashed few km from the airport, bursting into flames. The aircraft was totally destroyed and all three occupants were killed.

Crash of a Learjet 35A in Manaus

Date & Time: Mar 7, 2010 at 1535 LT
Type of aircraft:
Operator:
Registration:
PT-LJK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Palm Beach – Aguadilla – Manaus – Rio de Janeiro
MSN:
35-372
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6240
Captain / Total hours on type:
754.00
Copilot / Total flying hours:
1095
Copilot / Total hours on type:
410
Circumstances:
The aircraft was completing an ambulance flight from Palm Beach to Rio de Janeiro with intermediate stops in Aguadilla and Manaus, carrying one patient, a medical team and two pilots. During the takeoff roll from 10 at Manaus-Eduardo Gomes Airport, just before V1 speed, the crew heard a loud noise coming from the right side of the airplane. In the mean time, the aircraft started to deviate to the right. The captain decided to abandon the takeoff procedure and initiated a braking maneuver. Unable to stop within the remaining distance, the aircraft overran and came to rest 400 metres past the runway end. All six occupants escaped uninjured while the aircraft was damage beyond repair.
Probable cause:
The following findings were identified:
- The external tyre on the right main gear deflated during the takeoff roll,
- The crew retarded the power levers and deployed the spoilers,
- The crew did not use the parachute, judging the relative low speed and thinking this was an optional equipment,
- Technical analysis on the right main gear revealed that the six bolts on the external wheel torque were approximately 90% lower than foreseen, which may contributed to the tyre deflection.
Final Report:

Crash of a Cessna T303 Crusader in Louisa: 1 killed

Date & Time: Mar 4, 2010 at 1245 LT
Type of aircraft:
Registration:
N9305T
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Manassas - Louisa - Danville
MSN:
303-00001
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2255
Aircraft flight hours:
1374
Circumstances:
During takeoff, one witness noted that at least one engine seemed to be running rough and not making power. Several other witnesses, located about 1/2 mile northwest of the airport, observed the accident airplane pass overhead in a right turn. They reported that the engine noise did not sound normal. Two of the witnesses noted grayish black smoke emanating from the airplane. The airplane then rolled left and descended nose down into the front yard of a residence. Review of maintenance records revealed the airplane underwent an annual inspection and extensive maintenance about 3 months prior to the accident. One of the maintenance issues was to troubleshoot the right engine that was reportedly running rough at cruise. During the maintenance, the right engine fuel pump, metering valve, and fuel manifold were removed and replaced with overhauled units. Additionally, the right engine fuel flow was reset contrary to procedures contained in an engine manufacturer service information directive; however, the fuel pump could not be tested due to thermal damage and the investigation could not determine if the fuel flow setting procedure contributed to the loss of power on the right engine. On-scene examination of the wreckage and teardown examination of both engines did not reveal any preimpact mechanical malfunctions. Teardown examination of the right propeller revealed that the blades were not at or near the feather position, which was contrary to the emergency procedure published by the manufacturer, to secure the engine and feather the propeller in the event of an engine power loss. The right propeller exhibited signatures consistent with low or no power at impact, while the left propeller exhibited signatures consistent of being operated with power at impact.
Probable cause:
The pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.
Final Report: