Crash of a Piper PA-61 Aerostar (Ted Smith 601P) in Tijuana: 3 killed

Date & Time: Oct 31, 2011 at 1110 LT
Registration:
N76VK
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Tijuana – Loreto
MSN:
61-0305-079
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Shortly after takeoff from runway 09 at Tijuana-General Abelardo L. Rodríguez Airport, while in initial climb, the twin engine aircraft entered an uncontrolled descent and crashed onto a garage, bursting into flames. Both occupants as well as one people in his car were killed.

Crash of a Cessna 208B Grand Caravan in Xakanaka: 8 killed

Date & Time: Oct 14, 2011 at 1355 LT
Type of aircraft:
Operator:
Registration:
A2-AKD
Flight Phase:
Survivors:
Yes
Schedule:
Xakanaka - Pom Pom
MSN:
208B-0582
YOM:
1996
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
Shortly after takeoff from Xakanaka Airstrip on a taxi flight to the Pom Pom Camp located in the Okavango Delta, the single aircraft lost height and crashed, bursting into flames. The pilot and seven passengers were killed while four others were injured. The pilot was a British citizen as the seven passengers killed were respectively four Swedish, on British and two French. The aircraft was totally destroyed by a post crash fire. For unknown reasons, the aircraft caught fire shortly after takeoff.

Crash of an Embraer EMB-120ER Brasília in Huambo: 17 killed

Date & Time: Sep 14, 2011 at 1130 LT
Type of aircraft:
Operator:
Registration:
T-500
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Huambo - Luanda
MSN:
120-359
YOM:
2002
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
17
Circumstances:
Shortly after take off from Huambo-Albano Machado Airport, the twine engine aircraft stalled and crashed near the runway end, bursting into flames. All four crew and two passengers survived while 17 passengers were killed. There were 11 officers, three generals and six civilians on board. This Embraer Brasilia was the most recent built in service.

Crash of a Piper PA-60 Aerostar (Ted Smith 602P) in Hildesheim: 1 killed

Date & Time: Sep 13, 2011 at 1940 LT
Operator:
Registration:
D-IIWA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Hildesheim – Augsburg
MSN:
62-0903-8165032
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3450
Aircraft flight hours:
2114
Aircraft flight cycles:
1209
Circumstances:
During the takeoff roll from runway 25 at Hildesheim Airport, the twin engine aircraft accelerated slowly and lifted off from the mid-runway only. After takeoff, the climb gradient was low then the airplane lost height and descended until it impacted a wall and crashed in an industrial area located about 900 metres from the runway end, bursting into flames. The aircraft was totally destroyed and the pilot, sole on board, was killed.
Probable cause:
The accident was due to the fact that the aircraft did not gain altitude after takeoff, went into an uncontrolled flight condition and crashed. There was a high probability that a disturbance of the pilot's consciousness and a considerable reduced capacity of action from the pilot contributed to the accident.
Final Report:

Crash of a Piper PA-31P-425 Pressurized Navajo in Monterrey: 2 killed

Date & Time: Sep 12, 2011 at 1345 LT
Type of aircraft:
Operator:
Registration:
N69DJ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Monterrey - Monterrey
MSN:
31-7300155
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The twin engine aircraft was engaged in a local post maintenance test flight at Monterrey-Del Norte Airport. Shortly after takeoff, the airplane encountered difficulties to gain height when it stalled and crashed in a field located 500 metres past the runway end, bursting into flames. The aircraft was destroyed by fire and both occupants were killed.

Crash of a Yakovlev Yak-42D in Yaroslavl: 44 killed

Date & Time: Sep 7, 2011 at 1600 LT
Type of aircraft:
Operator:
Registration:
RA-42434
Flight Phase:
Survivors:
Yes
Schedule:
Yaroslavl - Minsk
MSN:
4520424305017
YOM:
1993
Flight number:
AEK9633
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
44
Captain / Total flying hours:
6954
Captain / Total hours on type:
1525.00
Copilot / Total flying hours:
13492
Copilot / Total hours on type:
613
Aircraft flight hours:
6490
Aircraft flight cycles:
3112
Circumstances:
The aircraft was chartered by the Lokomotiv Yaroslavl ice hockey team to carry his staff to Minsk to take part to the first game of the Russian 2011-2012 championship. During the takeoff roll from runway 23 at Yaroslavl-Tunoshna Airport, the crew selected flaps down at 20° and the stabilizer in a nose-up position of 8,7°. The aircraft slowly accelerated to 165 km/h due to a residual pressure on the brake pedal. At a speed of 185 km/h and at a distance of 1,350 metres from the runway end, the nose gear lifted off. But the aircraft continued, passed the runway end and rolled for about 400 metres before it took off. Then it collided with various approach lights and the localizer antenna, lost height and eventually crashed on the shore of the Volga River, bursting into flames, 2 minutes after the takeoff roll was initiated. A passenger and the flight engineer were seriously injured while 43 other occupants were killed. Almost a week later, the passenger died from his injuries. Among the passengers were 26 players from the Lokomotiv Yaroslavl ice hockey team, Russian citizens and also Canadian, Czech, Ukrainian, German and Slovak. The Canadian coach Brad McCrimmon, his both assistants, the cameraman, three masseurs, one admin and two doctors were among the victims.
Probable cause:
Erroneous actions on part of the crew, especially by applying brake pedal pressure just before rotation as result of a wrong foot position on the pedal during the takeoff run. This led to braking forces on the main gear requiring additional time for acceleration, a nose down moment preventing the crew to establish a proper rotation and preventing the aircraft to reach a proper pitch angle for becoming airborne, overrun of the runway at high speed with the elevator fully deflected for nose up rotation (producing more than double the elevator forces required to achieve normal takeoff rotation). The aircraft finally achieved a high rate of nose up rotation, became airborne 450 meters past the runway end and rotated up to a supercritical angle of attack still at a large rate of pitch up causing the aircraft to stall at low altitude, to impact obstacles and ground, break up and catch fire killing all but one occupants.
Contributing factors were:
- serious shortcomings in the re-training of the crew members with regards to the Yak-42, which did not take place in full, was spread out over a long period of time and took place while the crew remained in full operation on another aircraft type (Yak-40), which led to a negative transfer of skills, especially a wrong position of the foot on the brake pedal on the Yak-42,
- Lack of supervision of the re-training,
- errors and missed procedures by the crew in preparation and execution of the takeoff,
- inconsistent, uncoordinated actions by the crew in the final stages of the takeoff.
Final Report:

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

Date & Time: Aug 28, 2011 at 0854 LT
Type of aircraft:
Operator:
Registration:
RA-01105
Flight Phase:
Survivors:
Yes
Schedule:
Baranikovskiy - Baranikovskiy
MSN:
1G239-50
YOM:
1991
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
1208
Aircraft flight cycles:
4247
Circumstances:
The single engine aircraft was dispatched in Baranikovskiy to perform a crop spraying mission on rice paddy field. Before flight, the tank was refueled with 250 litres of E95 fuel. The technician told the pilot the fuel was abnormally yellow but the pilot decided to proceed with the flight. Prior to take off, he asked the copilot to stay on ground and replaced him by the owner of the zone to be treated which is against the published procedures. During the takeoff roll, the aircraft did not accelerate as expected but the pilot continued. After liftoff, at a height of about 30 metres, the pilot initiated a 90° left turn when the engine lost power. He started to drop the load of chemicals then attempted an emergency landing when the aircraft impacted ground. It continued for about 134 metres then struck an irrigation drain, nosed over and came to rest, bursting into flames. The pilot was killed and the passenger was seriously injured.
Probable cause:
The accident was caused by a loss of engine power because the aircraft has been refueled with fuel dedicated to automobile.
The following contributing factors were identified:
- The pilot's lack of knowledge about the flight area and the layout of cultivated fields,
- The pilot failed to brake properly during the emergency landing,
- The absence of a copilot on board,
- The Operator certificat was revoked 3 days prior to the accident.

Crash of a Piper PA-46-350P Malibu Mirage in Rantoul: 3 killed

Date & Time: Jul 24, 2011 at 0920 LT
Operator:
Registration:
N46TW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rantoul – Sarasota
MSN:
46-22071
YOM:
1989
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1850
Aircraft flight hours:
2560
Circumstances:
On July 24, 2011, about 0920 central daylight time, a Piper PA-46-350P, N46TW, owned and operated by a private pilot, sustained substantial damage when it impacted powerlines and terrain during takeoff from runway 27 at the Rantoul National Aviation Center Airport-Frank Elliott Field (TIP), near Rantoul, Illinois. A post impact ground fire occurred. The personal flight was operating under 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident. An instrument flight rules (IFR) flight plan was on file. The pilot and two passengers sustained fatal injuries. The flight was originating from TIP at the time of the accident and was destined for Sarasota/Bradenton International Airport (SRQ), near Sarasota, Florida. A witness, who worked at the fixed base operator, stated that the pilot performed the preflight inspection of the airplane in a hangar. An estimated 80 pounds. of luggage was loaded behind the airplane's rear seat. The witness said that the pilot's wife told the pilot that she had to use the restroom. The pilot reportedly replied to her to "hurry because a storm front was coming." The witness said that the engine start was normal and that both passengers were sitting in the rear forward-facing seats when the airplane taxied out. A witness at the airport, who was a commercial pilot, reported that he observed the airplane takeoff from runway 27 and then it started to turn to the south. He indicated that the landing gear was up when the airplane was about 500 feet above the ground. The witness stated that a weather front was arriving at the airport and that the strong winds from the northwest appeared to "push the tail of the plane up and the nose down." The airplane descended and impacted powerlines and terrain where the airplane subsequently caught on fire. The witness indicated that the airplane's engine was producing power until impact.
Probable cause:
The pilot did not maintain airplane control during takeoff with approaching thunderstorms. Contributing to the accident was the pilot's decision to depart into adverse weather conditions.
Final Report:

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 a Cessna 208B Grand Caravan in Pukatawagan: 1 killed

Date & Time: Jul 4, 2011 at 1610 LT
Type of aircraft:
Operator:
Registration:
C-FMCB
Flight Phase:
Survivors:
Yes
Schedule:
Pukatawagan - The Pas
MSN:
208B-1114
YOM:
2005
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1900
Captain / Total hours on type:
400.00
Circumstances:
The Beaver Air Services Limited Partnership Cessna 208B (registration C-FMCB serial number 208B1114), operated by its general partner Missinippi Management Ltd (Missinippi Airways), was departing Pukatawagan, Manitoba, for The Pas/Grace Lake Airport, Manitoba. At approximately 1610 Central Daylight Time, the pilot began the takeoff roll from Runway 33. The aircraft did not become fully airborne, and the pilot rejected the takeoff. The pilot applied reverse propeller thrust and braking, but the aircraft departed the end of the runway and continued down an embankment into a ravine. A post-crash fire ensued. One of the passengers was fatally injured; the pilot and the 7 other passengers egressed from the aircraft with minor injuries. The aircraft was destroyed. The emergency locator transmitter did not activate.
Probable cause:
Findings as to Causes and Contributing Factors:
Runway conditions, the pilot's takeoff technique, and possible shifting wind conditions combined to reduce the rate of the aircraft's acceleration during the takeoff roll and prevented it from attaining takeoff airspeed. The pilot rejected the takeoff past the point from which a successful rejected takeoff could be completed within the available stopping distance. The steep drop-off and sharp slope reversal at the end of Runway 33 contributed to the occupant injuries and fuel system damage that in turn caused the fire. This complicated passenger evacuation and prevented the rescue of the injured passenger. The deceased passenger was not wearing the available shoulder harness. This contributed to the serious injuries received as a result of the impact when the aircraft reached the bottom of the ravine and ultimately to his death in the post-impact fire.
Findings as to Risk:
If pilots are not aware of the increased aerodynamic drag during takeoff while using soft-field takeoff techniques they may experience an unexpected reduction in takeoff performance. Incomplete passenger briefings or inattentive passengers increase the risk that they will be unable to carry out critical egress procedures during an aircraft evacuation. When data recordings are not available to an investigation, this may preclude the identification and communication of safety deficiencies to advance transportation safety. Although the runway at Pukatawagan and many other aerodromes are compliant with Aerodrome Standards and Recommended Practices (TP 312E), the topography of the terrain beyond the runway ends may increase the likelihood of damage to aircraft and injuries to crew and passengers in the event of an aircraft overrunning or landing short. TC's responses to TSB recommendations for action to reduce the risk of post-impact fires have been rated as Unsatisfactory. As a result, there is a continuing risk of post-impact fires in impact-survivable accidents involving these aircraft. The lack of accelerate stop distance information for aircraft impedes the crew's ability to plan the takeoff-reject point accurately.
Other finding:
Several anomalies were found in the engine's power control hardware. There was no indication that these anomalies contributed to the occurrence.
Final Report: