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 Tupolev TU-204-100 in Moscow

Date & Time: Mar 22, 2010 at 0235 LT
Type of aircraft:
Operator:
Registration:
RA-64011
Flight Type:
Survivors:
Yes
Schedule:
Hurghada - Moscow
MSN:
14507413640
YOM:
1993
Flight number:
TUP1906
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5388
Captain / Total hours on type:
1868.00
Copilot / Total flying hours:
1973
Copilot / Total hours on type:
979
Aircraft flight hours:
18335
Aircraft flight cycles:
4795
Circumstances:
The aircraft was returning to Moscow on a ferry flight after passengers have been dropped off in Hurghada. On approach to Moscow-Domodedovo Airport, the visibility was low due to foggy conditions. Horizontal visibility on runway 14L threshold was 1,300 meters and vertical visibility was 200 feet. In flight, the flight computer failed and the crew continued the approach below minimums. Despite he was not able to establish a visual contact with the runway, the captain continued the approach and failed to initiate a go-around procedure. The aircraft descended below the glide, impacted trees and crashed in a dense wooded area located 1,450 metres short of runway. All eight occupants were injured, three seriously. The aircraft was destroyed.
Probable cause:
The crew performed an approach in below-minima weather conditions for an airplane with a defective flight computer. The crew failed to initiate a go-around procedure while unable to establish a visual contact with the runway.
Contributing factors were:
- Insufficient training of the crew to perform approaches at or near weather minimums,
- Lack of control over the activities of the crew, which led to poor resource management (CRM) of the captain,
- Failure of the flight control computer system, which led to an increase in the allowed weather minima of the aircraft,
- Failure of captain to divert to another airport,
- Failure of captain to decide about a missed approach when there was visual contact with the approach lights,
- Failure of the co-pilot to call for a missed approach,
- Unsatisfactory interaction in the crew, resulting in a descent below safe altitude.
Final Report:

Crash of a Learjet 35A in Jeffersonville

Date & Time: Mar 21, 2010
Type of aircraft:
Registration:
N376HA
Flight Type:
Survivors:
Yes
Schedule:
Lexington – Jeffersonville
MSN:
35-477
YOM:
1982
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft landed hard at Jeffersonville-Clark County Airport. There were no injuries among the people on board and the aircraft was damaged beyond repair due to severe damages to the left wing and the tail section.
Probable cause:
No investigation conducted by the NTSB.

Crash of an Antonov AN-26B in Tallinn

Date & Time: Mar 18, 2010 at 1018 LT
Type of aircraft:
Operator:
Registration:
SP-FDO
Flight Type:
Survivors:
Yes
Schedule:
Helsinki – Tallinn
MSN:
105 03
YOM:
1980
Flight number:
EXN3589
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4695
Captain / Total hours on type:
2295.00
Copilot / Total flying hours:
990
Copilot / Total hours on type:
495
Aircraft flight hours:
25941
Circumstances:
Exin Co was operating An-26B for regular cargo flight between Tallinn and Helsinki. The crew performed last maintenance check in Tallinn on previous day and made uneventful flight to Helsinki on 17th March afternoon. Next morning the aircraft took off from Helsinki for regular flight EXN3589 to Tallinn at 09:46 local time. The takeoff weight was 23,954 kg, 46 kg below the MTOW. Four crewmembers, company mechanic and one cargo attendant were on board. During takeoff crew used RU 19-300 APU for additional thrust as prescribed in AFM. The RU 19-300 was shot down after takeoff. The flight was uneventful until 08:14:50, 9.5 nm from the runway 26. When power levers were retarded to flight idle crew noticed engine vibration and smelled a smoke in the cockpit. The engine chip detector indicator in the cockpit was lit. After short discussion about which engine should be shot down the flight engineer shot down the left engine and the captain tried to start the RU19A-300 (APU) to gain more thrust. During the approach the air traffic controller noticed the aircraft deviation from the approach path to the left and notified the crew. According to the FDR and CVR data the crew was unable to maintain a proper approach path both in lateral and vertical dimensions. The attempts to start RU19A-300 engine failed. Visual contact with the RWY was established 0.5 nm from the threshold. The aircraft crossed the airport boundary being not configured for landing and with IAS 295-300 km/h. The flaps were extended for 10˚ over the threshold; the landing gear was lowered after passing the RWY threshold and retracted again. The aircraft made a high speed low path over the runway on ca 10-15 feet altitude with the landing gear traveling down and up again. Flaps were extended over runway, and then retracted again seconds before impact. At the end of the RWY the full power on right engine was selected, aircraft climbed 15-20 feet and started turning left. Crew started retracting flaps and lowered landing gear. Aircraft crossed the highway at the end of the RWY on altitude ca 30 feet, then descended again, collided with the treetops at the lake shore and made crash-landing on the snow and ice-covered lake waterline. Due to the thick ice the aircraft remained on the ice and glided 151 m on the ice with heading 238˚ before coming to full stop. After the impact the flight engineer shoot down the RH engine and power and released all engine fire extinguishers. All persons onboard escaped immediately through the main door. No emergency was declares and despite suggestions from FO go-around was not commanded.
Probable cause:
Causes of the accident:
1. The failure of the left engine lubrication oil system, leading to the failure of the rear compressor bearing and inflight engine failure.
2. The failure of the crew to maintain the approach path and adhere to single engine landing procedures.
Factors contributing to the accident:
1. Improper and insufficient crew training, inter alia complete absence of simulator training.
2. The lack of effective coordination between crewmembers.
3. The failure of the crew to start RU19A-300 (APU).
4. Adverse weather conditions.
5. Inadequate company supervision by Polish CAA, consisting in not noticing the lack.
of flight crew training and companies generally pour safety culture.
6. Inadequate company maintenance practices, leaving preexisting breather duct failure unnoticed.
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 an Aeritalia G.222 in Port Harcourt

Date & Time: Mar 12, 2010
Type of aircraft:
Operator:
Registration:
NAF950
Flight Type:
Survivors:
Yes
Schedule:
Abuja - Port Harcourt
MSN:
4070
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Port Harcourt Airport, the aircraft skidded then veered off runway and came to rest. All 52 occupants were rescued, among them 10 were slightly injured. The aircraft was damaged beyond repair. All passengers were members of the intervention group taking part to a disaster response operation.

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 Fokker F27 Friendship 300M in Bosaso

Date & Time: Mar 4, 2010
Type of aircraft:
Operator:
Registration:
5Y-BRN
Flight Type:
Survivors:
Yes
MSN:
10155
YOM:
1960
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Bosaso Airport, the crew encountered poor weather conditions when the aircraft crashed short of runway. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair.