Crash of a Let L-410UVP-E20 in Recife: 16 killed

Date & Time: Jul 13, 2011 at 0654 LT
Type of aircraft:
Operator:
Registration:
PR-NOB
Flight Phase:
Survivors:
No
Schedule:
Recife - Natal - Mossoró
MSN:
92 27 22
YOM:
1992
Flight number:
NRA4896
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
16
Captain / Total flying hours:
15457
Captain / Total hours on type:
957.00
Copilot / Total flying hours:
2404
Copilot / Total hours on type:
404
Aircraft flight hours:
2126
Aircraft flight cycles:
3033
Circumstances:
At 0650 local time, the aircraft departed from Recife-Guararapes Airport runway 18, destined for Natal, carrying 14passengers and two crewmembers on a regular public transportation flight. During the takeoff, after the aircraft passed over the departure end of the runway, the copilot informed that they would return for landing, preferably on runway 36, and requested a clear runway. The aircraft made a deviation to the left, out of the trajectory, passed over the coastline, and, then, at an altitude of approximately 400ft, started a turn to the right over the sea. After about 90º of turn, upon getting close to the coast line, the aircraft reverted the turn to the left, going farther away from the coast line. After a turn of approximately 270º, it leveled the wings and headed for the airport area. The copilot informed, while the aircraft was still over the sea, that they would make an emergency landing on the beach. Witnesses reported that, as the aircraft was crossing over the coast line, the left propeller seemed to be feathered and turning loosely. At 0654 local time, the aircraft crashed into the ground in an area without buildings, between Boa Viagem Avenue and Visconde de Jequitinhonha Avenue, at a distance of 1,740 meters from the runway 36 threshold. A raging post-impact fire occurred and all 16 occupants were killed.
Probable cause:
Human Factors
Medical Aspect
- Anxiety
The perception of danger especially by the first officer affected the communication between the pilots and may have inhibited a more assertive attitude, which could have led to an emergency landing on the beach, minimizing the consequences of the accident.
Psychological Aspect
- Attitude
Operational decisions during the emergency may have resulted from the high confidence level, that the captain had acquired in years of flying and experience in aviation, as well as the captain's resistance to accept opinions different to his own.
- Emotional state
According to CVR recordings there was a high level of anxiety and tension even before the abnormal situation. These components may have influenced the judgment of conditions affecting the operation of the aircraft.
- Decision making
The persistence to land on runway 36 during the emergency, even though the first officer recognized the conditions no longer permitted to reach the airport, reflects misjudgment of operational information present at the time.
- Signs of stress
The unexpected emergency at takeoff and the lack of preparation for dealing with it may have invoked a level of stress with the crew, that negatively affected the operational response.
Psychosocial Information
- Interpersonal relations
The historical differences between the two pilots possibly hindered the exchange of information and created a barrier to deal with the adverse situation.
- Dynamic team
The present diverging intentions of how to proceed clearly show cooperation and management issues in the cockpit. This prevented the choice of best alternative to achieve a safe emergency landing when there were no options left to reach the airport.
- Company Culture
The company was informally divided into two groups, whose interaction was impaired. It is possible that this problem of interaction continued into the cockpit management during the in flight emergency, with one pilot belonging to one and the other to the other group.
Organizational Information
- Education and Training
Deficiencies of training provided by the operator affected the performance of the crew, who had not been sufficiently prepared for the safe conduct of flight in case of emergency.
- Organizational culture
The actions taken by the company indicate informality, which resulted in incomplete operational training and attitudes that endangered the safety.
Operational Aspects
According to data from the flight recorder the rudder pedal inputs were inadequate to provide sufficient rudder deflection in order to compensate for asymmetric engine power.
The values of side slip reached as result of inadequate rudder pedal inputs penalized the performance of the aircraft preventing further climb or even maintaining altitude.
In the final phase of the flight, despite the airspeed decaying below Vmca, despite continuous stall warnings and despite calls by the first officer to not hold the nose up in order to not stall the captain continued pitch up control inputs until the aircraft reached 18 degrees nose up attitude and entered stall.
- Crew Coordination
The delay in retracting the landing gear after the first instruction by the captain, the instruction of the captain to feather the propeller when the propeller had already been feathered as well as the first officer's request the captain should initiate the turn back when the aircraft was already turning are indicative that the crew tasks and actions were not coordinated.
Emergency procedures provided in checklists were not executed and there was no consensus in the final moments of the flight, whether the best choice (least critical option) was to return to the runway or land on the beach.
- Oblivion
It is possible in response to the emergency and influenced by anxiety, that the crew may have forgotten to continue into the 3rd segment of the procedure provided for engine failure on takeoff at or above V1 while trying to return to the airfield shortly after completion of the 2nd segment while at 400ft.
- Pilot training
The lack of training of engine failures on takeoff at or above V1, similar as is recommended in the training program, led to an inadequate pilot response to the emergency. The pilots did not follow the recommended flight profile and did execute the checklist items to be carried out above 400 feet.
- Pilot decisions
The pilots assessed that the priority was to return to land in opposite direction of departure and began the turn back at 400 feet, which added to the difficulty of flying the aircraft. At 400 feet the aircraft maintained straight flight and a positive rate of climb requiring minor flight control inputs only, which would have favored the completion of the emergency check list items in accordance with recommendations by the training program.
After starting the turn the crew would needed to adjust all flight controls to maintain intended flight trajectory in addition to working the checklists, the turn thus increased workload. It is noteworthy that the remaining engine developed sufficient power to sustain flight.
- Supervision by Management
The supervision by management did not identify that the training program provided to pilots failed to address engine failure above V1 while still on the ground and airborne.
It was not identified that the software adopted by the company to dispatch aircraft used the maximum structural weight (6,600 kg) as maximum takeoff weight for departures from Recife.
On the day of the accident the aircraft was limited in takeoff weight due to ambient temperature. Due to the software error the aircraft took off with more than the maximum allowable takeoff weight degrading climb performance.
Mechanical Aspects
- Aircraft
Following the hypothesis that the fatigue process had already started when the turbine blade was still attached to the Russia made engine, the method used by the engine manufacturer for assessment to continue use of turbine blades was not able to ensure sufficient quality of the blade, that had been mounted into position 27 of the left hand engine's Gas Generator Turbine's disk.
- Aircraft Documentation
The documentation of the aircraft by the aircraft manufacturer translated into the English language did not support proper operation by having confusing texts with different content for the same items in separate documents as well as translation errors. This makes the documentation difficult to understand, which may have contributed to the failure to properly implement the engine failure checklists on takeoff after V1.
An especially concerning item is the "shutdown ABC (Auto Bank Control)", to be held at 200 feet height, the difference between handling instructed by the checklist and provided by the flight crew manual may have contributed to the non-performance by the pilots, aggravating performance of the aircraft.
Final Report:

Crash of an Antonov AN-24RV in Strezhevoy: 7 killed

Date & Time: Jul 11, 2011 at 1156 LT
Type of aircraft:
Operator:
Registration:
RA-47302
Survivors:
Yes
Schedule:
Tomsk - Surgut
MSN:
5 73 103 02
YOM:
1975
Flight number:
IK9007
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
4570
Captain / Total hours on type:
4064.00
Copilot / Total flying hours:
9476
Copilot / Total hours on type:
5100
Aircraft flight hours:
48489
Aircraft flight cycles:
32783
Circumstances:
The twin engine aircraft departed Tomsk Airport at 1010LT on a flight (callsign IK9007/SP5007) to Surgut, carrying 33 passengers and a crew of four. About an hour and 26 minutes into the flight, the left engine's 'chips in oil' warning light came on. About eight minutes later, a burning smell was noticed in the cockpit and the captain decided to divert to Nizhnevartovsk Airport. During the descent, the left engine caught fire. Its propeller was feathered and the crew decided to divert to Strezhevoy Airport. But as the fire could not be extinguished, the captain eventually attempted an emergency landing in the Ob River. Upon landing, the aircraft broke in two and came to rest in shallow water. Seven passengers were killed while all other occupants were rescued.
Probable cause:
The Interstate Aviation Committee (MAK) released their final report in Russian concluding the probable causes of the accident were:
The catastrophe of the AN-24 RA-47302 occurred when ditching became necessary due to a fire in the left hand engine's nacelle. The destruction of the aircraft and loss of life was caused by collision with underwater obstacles that the crew could not anticipate or avoid. The fire in the left hand engine nacelle was caused by the fracture of a centrifugal breather releasing an air-fuel emulsion into the engine compartment as well as a delayed reaction to shut the engine down by the crew following an magnetic chip detector indication together with indications of oil pressure fluctuations, a burning smell and a low oil pressure indication. A delay in indicating engine vibrations to the crew as result of degradation of the engine vibration sensoring equipment, most likely caused by changes of the rotor speed of the engine as result of the aft bearing failure of the compressor rotor and/or misalignment of the sensor, which probably influenced the decision of the crew to shut the engine down with a delay. Cause of the fracture of the centrifugal breather was the destruction of the impeller due to prolonged exposure to hot air-fuel emulsion due to the failure of the aft compressor rotor support bearing. It was not possible to determine the cause of the destruction of the aft compressor rotor support bearing due to significant secondary damage. Most likely the destruction was caused by misalignment such as:
- Incorrect assembly of support parts mating with the compressor rotor during on-condition engine repairs,
- Or deviations from required geometry of support parts mating with the compressor rotor.
Contributing factors were:
- Psychological unpreparedness of the captain to shut the engine down due to lack of experience with the aircraft on one engine inoperative
- Late detection of the fire and as a consequence late attempts to extinguish the fire, it was however not possible to establish why the fire was detected late due to lack of objective information about the performance of the fire alarm systems.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain near Zaraza

Date & Time: Jun 16, 2011 at 0950 LT
Operator:
Registration:
YV1394
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Maracay - Puerto Ordaz
MSN:
31-7405135
YOM:
1974
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Maracay on a cargo flight to Puerto Ordaz, carrying one pilot, one passenger and some bank documents. While in cruising altitude, the pilot informed ATC about smoke in the cockpit and elected to divert to the nearest airport. Eventually, he attempted an emergency landing in an open field located some 20 km east from Zaraza. After touchdown, the aircraft rolled for few dozen metres before coming to rest, bursting into flames. While both occupants escaped uninjured, the aircraft was totally destroyed by fire.
Probable cause:
During a flight of transport of values, in the phase of cruise, a smoke emergency appeared in the cockpit, that when not being able to be controlled, derived in a landing of emergency by precaution in a nonprepared field, which resulted without apparent damages to the aircraft, triggering later a fire and the almost total destruction of the same, due, very probably, to an electrical failure that originated the fire.

Crash of an Antonov AN-26 off Libreville

Date & Time: Jun 6, 2011 at 1025 LT
Type of aircraft:
Operator:
Registration:
TR-LII
Flight Type:
Survivors:
Yes
Schedule:
Port Gentil - Libreville
MSN:
75 04
YOM:
1978
Flight number:
SLN122A
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Port Gentil on a cargo flight to Libreville on behalf of DHL Airways. On approach to Libreville-Léon Mba Airport, the captain informed ATC about hydraulic problems and initiated a go-around procedure. Shortly later, the aircraft stalled and crashed in the sea some 2,3 km southeast of the airport. All four occupants were rescued while the aircraft was damaged beyond repair. Due to the failure of the hydraulic system, the crew was unable to lower the gear.

Crash of a North American B-25J-35-NC Mitchell in Melun

Date & Time: May 31, 2011 at 1730 LT
Registration:
F-AZZU
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Melun - Melun
MSN:
108-47562
YOM:
1944
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crew was performing a local flight at Melun-Villaroche Airport. Few minutes after takeoff, while flying at low height, the engine caught fire. The pilot elected to return to the airport but was eventually forced to attempt an emergency landing. The aircraft collided with power cables then crashed on its belly in a field, coming to rest in flames. Both occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The right engine caught fire in flight for unknown reasons.

Crash of a Boeing 707-321B at Point Mugu NAS

Date & Time: May 18, 2011 at 1727 LT
Type of aircraft:
Operator:
Registration:
N707AR
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Point Mugu NAS - Point Mugu NAS
MSN:
20029/790
YOM:
1969
Flight number:
OME70
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5117
Captain / Total hours on type:
2730.00
Copilot / Total flying hours:
4052
Copilot / Total hours on type:
2900
Aircraft flight hours:
47856
Aircraft flight cycles:
15186
Circumstances:
On May 18, 2011, about 1727 Pacific daylight time, a modified Boeing 707, registration N707AR, operating as Omega Aerial Refueling Services (Omega) flight 70 crashed on takeoff from runway 21 at Point Mugu Naval Air Station, California (KNTD). The airplane collided with a marsh area to the left side beyond the departure end of the runway and was substantially damaged by postimpact fire. The three flight crewmembers sustained minor injuries. The flight was conducted under the provisions of a contract between Omega and the US Naval Air Systems Command (NAVAIR) to provide aerial refueling of Navy F/A-18s in offshore warning area airspace. According to the Federal Aviation Administration (FAA), Omega, and the US Navy, the airplane was operating as a nonmilitary public aircraft under the provisions of 49 United States Code Sections 40102 and 40125. The accident flight crew consisted of a captain, first officer, and flight engineer who had flown with each other many times previously. The crewmembers reported conducting a normal preflight inspection. As the airplane taxied toward the runway, the reported wind was from 280º magnetic at 24 knots, gusting to 34 knots; the flight crew reported that the windsock showed very little change in the wind direction and a slight amount of gust. The crew had calculated a takeoff decision speed (V1) of 141 knots and a rotation speed (Vr) of 147 knots. The crew elected to add 5 knots to the rotation speed to compensate for the wind gusts and briefed a maximum power takeoff. The first officer, who was the pilot monitoring, stated that he advised the captain, who was the pilot flying, about advancing the power relatively smoothly to avoid a compressor stall with the crosswind, and the captain agreed. About 1723, air traffic control cleared the flight for takeoff from runway 21 and instructed the crew to turn left to a heading of 160º after departure. The captain applied takeoff thrust, and the first officer told investigators that, as the pilot in the right seat, he applied forward pressure on the yoke and right aileron input to compensate for the right crosswind. According to the crew, the takeoff roll was normal. At rotation speed, the captain rotated the airplane to an initial target pitch attitude of 11º airplane nose up. Shortly after liftoff, when the airplane was about 20 feet above the runway and about 7,000 feet down the runway, all three crewmembers heard a loud noise and observed the thrust lever for the No. 2 (left inboard) engine rapidly retard to the aft limit of the throttle quadrant. The captain stated that he applied full right rudder and near full right aileron to maintain directional control and level the wings, but the airplane continued to drift to the left. The captain reported that he perceived the airplane would not continue to climb and decided to “put it back on the ground.” Witnesses and a cell phone video from another Omega 707 crewmember observing the takeoff indicated that the No. 2 (left inboard) engine separated and traveled up above the left wing as the airplane was passing abeam taxiway A2. The inlet cowling for the No. 1 (left outboard) engine separated immediately thereafter, consistent with being struck by the No. 2 engine nacelle. The airplane began to descend with the remaining three engine power levers at maximum power, and the left wing dipped slightly (Pratt & Whitney indicated that loss of the inlet cowling on the No. 1 engine would increase drag, effectively resulting in less than zero thrust output). The captain said he lowered the nose and leveled the wings just as the airplane touched down on the runway between taxiway A2 and A1. The airplane made multiple contacts with the runway before drifting left and departing the runway surface before the airplane reached taxiway A1. The airplane crossed taxiway A and came to rest in the marsh area. According to the flight crewmembers, they observed flames in the cabin area and did not have time to perform an engine shutdown or evacuation checklist. The crew reported difficulty exiting the cockpit due to mud and debris blocking the cockpit door. All three crewmembers successfully evacuated through the left forward entrance via the escape slide.
Probable cause:
The NTSB determines that the probable cause of this accident was the failure of a midspar fitting, which was susceptible to fatigue cracking and should have been replaced with a newer, more fatigue-resistant version of the fitting as required by an airworthiness directive. Also causal was an erroneous maintenance entry made by a previous aircraft owner, which incorrectly reflected that the newer fitting had been installed.
Final Report:

Crash of a Beechcraft E90 King Air in Bournemouth

Date & Time: May 18, 2011 at 1131 LT
Type of aircraft:
Registration:
N46BM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bournemouth - Manchester
MSN:
LW-198
YOM:
1976
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
800
Captain / Total hours on type:
660.00
Circumstances:
The pilot had planned to fly from Bournemouth Airport to Manchester Airport operating the flight as a single pilot, with a passenger seated in the co-pilot’s seat. He arrived at the airport approximately one hour before the planned departure time of 1130 hrs, completed his pre‑flight activities and went to the aircraft at approximately 1110 hrs. The 1120 hrs ATIS gave the weather at the airport as: surface wind from 230° at 10 kt, visibility 10 km or greater, few clouds at 1,000 ft, broken cloud at 1,200 ft and at 2,000 ft, temperature 16°C, dew point 12°C and QNH 1015 hPa. After starting the engines, the pilot was cleared to taxi to holding point ‘N’ for a departure from Runway 26 and he was given clearance to take off at 1127 hrs. At 1129:45 hrs, approximately 55 seconds after the aircraft became airborne, the aerodrome controller transmitted “four six bravo mike do you have a problem?” because he believed the aircraft was not climbing normally. The pilot replied “november four six bravo going around” and, shortly afterwards, “four six bravo requesting immediate return”. The controller cleared the pilot to use either runway to land back at the airport but received no reply. The pilot carried out a forced landing into a field 1.7 nm west of the Runway 08 threshold at Bournemouth Airport and neither he nor his passenger was hurt.
Probable cause:
The pilot experienced symptoms of symmetrical power loss sufficient to prevent the aircraft from sustaining level flight and made a forced landing into a field. The deficiency in the aircraft’s takeoff performance suggested that its powerplants were not producing sufficient thrust. As fuel contamination was discounted and no fault was found in either engine, it was concluded that, in all probability, the poor performance was not caused by a failure in either powerplant. Maximum rpm was not selected for departure but it was unlikely that this explained the aircraft’s poor performance on the runway or in the air. The pilot insisted that he had set torque to the takeoff limit. There was insufficient evidence to enable the cause of the apparent power loss to be determined.
Final Report:

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

Date & Time: May 17, 2011 at 1915 LT
Type of aircraft:
Operator:
Registration:
RA-68122
Flight Phase:
Survivors:
Yes
MSN:
1G195-27
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Circumstances:
The pilot, sole on board, was performing a crop spraying flight when the engine lost power. He elected to make an emergency landing in a field 2 kilometers from Sofyevka, in the Stavropol krai. Upon touchdown, the aircraft rolled over and came to rest upside down, bursting into flames. The pilot escaped uninjured while the aircraft was partially destroyed by fire. The wreck was evacuated and disposed away before the arrival of the accident investigation commission. Therefore, it was not possible to the MAK to determine the cause of the engine failure. As the pilot did not have any valid licence for this kind of aircraft, this PZL-Mielec AN-2R built on 11FEB1982 did not have a valid Certificate of Airworthiness. It had a double registration: FLA-34906 and RA-68122 which was the official one present in the Russian Civil Aviation registry.
Probable cause:
Engine failure in flight for undetermined reasons.
Final Report:

Crash of a BAe 125-700A off Loreto

Date & Time: May 5, 2011 at 1155 LT
Type of aircraft:
Operator:
Registration:
N829SE
Flight Type:
Survivors:
Yes
MSN:
257095
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Loreto Airport, the crew encountered technical problems and elected to return. On final approach over the Gulf of California, in a gear up configuration, the aircraft struck the water surface and came to rest into the sea close to the shore, few dozen metres short of runway 34 threshold. Both pilots escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Grumman S-2T Tracker in Bahía Blanca

Date & Time: Apr 20, 2011
Type of aircraft:
Operator:
Registration:
0701/2-AS-22
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bahía Blanca - Bahía Blanca
MSN:
298
YOM:
1957
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a training flight on this Tracker delivered to the Armada Argentina in 1978. While flying in the vicinity of the Bahía Blanca-Comandante Espora Airport, the crew encountered unknown technical problems and was forced to attempt an emergency landing in an open field. While both pilots escaped with minor injuries, the aircraft was damaged beyond repair.