Crash of a Casa 212 Aviocar 300DF off Robinson Crusoe Island: 21 killed

Date & Time: Sep 2, 2011 at 1748 LT
Type of aircraft:
Operator:
Registration:
966
Flight Type:
Survivors:
No
Schedule:
Santiago - Robinson Crusoe Island
MSN:
443
YOM:
1994
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
21
Circumstances:
The twin engine aircraft departed Santiago de Chile-Comodoro Arturo Merino Benítez (Pudahuel) Airport on a special flight to Robinson Crusoe Island, carrying 17 passengers and a crew of four. The flight was organized by NGO's in cooperation with the Chilean National Television to see the progress of the reconstruction on the island of Robinson Crusoe following the 2010 earthquake. Among the occupants were members of the National Television and also from the Council of Culture. The famous Chilean television icon Felipe Camiroaga Fernández was among the passengers. Following an almost 3-hour flight, the crew completed a low pass over the runway 14 then started the approach to runway 32 from the sea. At an altitude of about 650 feet, the aircraft entered an uncontrolled descent, rolled to the left to an angle of 90° and impacted the sea. Debris were found floating on water and the main wreckage was later found about one km southeast from the airport. All 21 occupants were killed.

Personnel from the Chilean Air Force:
Lt Carolina Fernández Quinteros,
Lt Juan Pablo Mallea Lagos,
1st Sgt Eduardo Jones San Martín,
1st Cpl Eduardo Estrada Muñoz,
2nd Cpl Flavio Oliva Pino,
2nd Cpl Erwin Núñez Rebolledo,
Cdt Rodrigo Fernández Apablaza,
José Cifuentes Juica.

Council of Culture:
Galia Diaz Riffo,
Romina Irarrázabal Faggiani.

Chilean National Television:
Felipe Camiroaga Fernández,
Roberto Bruce Pruzzo,
Sylvia Slier Munoz,
Caroline Gatica Aburto,
Rodrigo Cabezón de Amesti.

Members of the 'Desafío Levantemos Chile' NGO:
Felipe Cubillos Sigall,
Sebastián Correa Murillo,
Catalina Vela Montero,
Joel Lizama Nahuelhual,
Jorge Palma Calvo,
Joaquín Arnolds Reyes.
Probable cause:
The accident was caused by the loss of control of the airplane while performing the tailwind leg through the channel between the islands of Robinson Crusoe and Santa Clara to an estimated height of 650 feet or less, during the circuit approach to Runway 32 in a very low trajectory (with little height difference above the runway), where very adverse airflow conditions were found, including wind shear, which exposed the crew to extreme flight conditions.
Adverse airflow conditions were the results of a combination of different factors, including:
- Very unstable atmosphere, with strong turbulence and possibly eventually powerful down gusts arising from the presence of open cells after a front passed,
- The presence of the two counter-rotating vortexes in the Santa Clara Island downwind wake,
- The presence of strong and gusty crosswinds that were very variable in strength and direction in a very short time.

Crash of a Britten Norman BN-2A-7 Islander in Port Kaituma

Date & Time: Aug 20, 2011 at 1200 LT
Type of aircraft:
Operator:
Registration:
8R-GHD
Survivors:
Yes
MSN:
622
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight, the pilot started the descent to Port Kaituma in poor weather conditions (heavy rain falls). After touchdown on a wet runway, the twin engine aircraft skidded, veered off runway, hit a pole with its left wing and lost its nose gear before coming to rest. While all four occupants escaped with minor injuries, the aircraft was damaged beyond repair.

Crash of a Cessna C-98A Grand Caravan near Bom Jardim da Serra: 8 killed

Date & Time: Aug 2, 2011 at 1327 LT
Type of aircraft:
Operator:
Registration:
2735
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Porto Alegre - Rio de Janeiro
MSN:
208B-2130
YOM:
2009
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Circumstances:
The single engine aircraft departed Canoas AFB in Porto Alegre at 1145LT on a flight to Rio de Janeiro-Galeão Airport, carrying six officers and two pilots on behalf of the 5th Air Transport Squadron. While cruising over the State of Santa Catarina, the crew encountered limited visibility due to poor weather conditions when the aircraft impacted a mountain near Bom Jardim da Serra. The aircraft disintegrated on impact and all 8 occupants were killed.

Crash of a Boeing 737-8BK in Georgetown

Date & Time: Jul 30, 2011 at 0132 LT
Type of aircraft:
Operator:
Registration:
9Y-PBM
Survivors:
Yes
Schedule:
New York - Port of Spain - Georgetown
MSN:
29635/2326
YOM:
2007
Flight number:
BW523
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
157
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9600
Captain / Total hours on type:
5000.00
Copilot / Total flying hours:
1400
Copilot / Total hours on type:
350
Aircraft flight hours:
14861
Circumstances:
The flight originated in New York as BW 523, and made a passenger and fuel stop in Port-of-Spain, Trinidad where there was also a change of crew comprising two pilots and four flight attendants before proceeding to Georgetown, Guyana. The flight departed Piarco at 04:36UTC. The aircraft proceeded to Georgetown from Port of Spain at Flight Level (FL) 330, was given descent clearance and was cleared for an RNAV (GPS) approach to RWY 06, landing at 05:32 UTC. There were no reported anomalies in the en-route profile, although during the transition from cruise to approach to RWY 06 the aircraft deviated to avoid some thunderstorm cells north and east of the Airport. The reported visibility was 9,000m. Light rain was encountered during the approach. The pilot reported that after visual contact was made and after crossing the Final Approach Fix (FAF), he disengaged the auto pilot and configured the aircraft for landing. The Flight Data Recorder (FDR) indicated that the flight was normal until the aircraft was approaching the runway. Even before the aircraft was over the threshold, the captain commented that he was not landing here. As the flight continued over the runway, comments on the Cockpit Voice Recorder (CVR), revealed that the captain indicated to the First Officer (FO) that the aircraft was not touching down. A go-around call was made by the Captain and acknowledged by the First Officer, however three seconds elapsed and the aircraft subsequently touched down approximately 4700ft from the threshold of RWY06, leaving just over 2700 feet of runway surface remaining. Upon touchdown, brake pressure was gradually increased and maximum brake pressure of 3000psi was not achieved until the aircraft was 250ft from the end of the runway or 450ft from the end of the paved area. The ground spoilers were extended on touchdown. The thrust reversers were partially deployed after touchdown. The aircraft did not stop and overran the runway. It then assumed a downward trajectory followed by a loud impact.
Probable cause:
The probable cause of the accident was that the aircraft touched down approximately 4,700 feet beyond the runway threshold, some 2,700 feet from the end of the runway, as a result of the Captain maintaining excess power during the flare, and upon touching down, failure to utilize the aircraft’s full deceleration capability, resulted in the aircraft overrunning the remaining runway and fracturing the fuselage.
Contributory Factors:
The Flight Crew’s indecision as to the execution of a go-around, failure to execute a go-around after the aircraft floated some distance down the runway and their diminished situational awareness contributed to the accident.
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 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 a Cessna 208B Grand Caravan in Barra do Vento

Date & Time: May 23, 2011 at 0750 LT
Type of aircraft:
Registration:
PT-OSG
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Barra do Vento – Boa Vista
MSN:
208B-0300
YOM:
1992
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6200
Captain / Total hours on type:
4800.00
Circumstances:
The pilot, sole on board, departed Barra do Vento Airport on a ferry flight to Boa Vista-Atlas Brasil-Cantanhede Airport, Roraima. Shortly after rotation, he noticed abnormal vibrations. At the same time, the 'door warning' light came ON on the instrument panel. He decided to land back but lost control of the airplane that veered off runway to the right and collided with an earth mound, bursting into flames. The aircraft was totally destroyed by a post crash fire and the pilot was seriously injured.
Probable cause:
It is possible that the pilot applied the flight controls inappropriately when the aircraft returned to the runway, making it impossible to maintain direction. After the 'door warning' light activated, the pilot made the decision to land when, according to the manufacturer, the situation did not require such immediate action but a continuation of the climb. It is possible that the pilot's training was not adequate or sufficient, because after the 'door warning' light came ON and the abnormal vibrations, the pilot carried out a procedure different from the one recommended by the manufacturer, and placed the plane in an irreversible condition.
Final Report:

Crash of a Saab 340A near Prahuaniyeu: 22 killed

Date & Time: May 18, 2011 at 2050 LT
Type of aircraft:
Operator:
Registration:
LV-CEJ
Flight Phase:
Survivors:
No
Schedule:
Rosario – Córdoba – Mendoza – Neuquén – Comodoro Rivadavia
MSN:
25
YOM:
1985
Flight number:
OSL5428
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
22
Captain / Total flying hours:
6133
Captain / Total hours on type:
2187.00
Copilot / Total flying hours:
1342
Copilot / Total hours on type:
288
Aircraft flight hours:
41422
Aircraft flight cycles:
44477
Circumstances:
On 18 May 2011, the pilot in command (PIC) and the crew - composed of the copilot (COP) and cabin crew members (CCM) - initiated the flight OSL5428 from Rosario International Airport (ROS) in the province of Santa Fe at 20:35, the final destination being the Comodoro Rivadavia International Airport (CRD), in the province of Chubut. The flight had scheduled intermediate stopovers at Córdoba International Airport (COR), Mendoza (MDZ), and Neuquén (NQN), according to the company's plans. The company designated aircraft Saab 340A, with registration number LV-CEJ, for the flight. After having made the intermediate stopovers in Córdoba (COR) and Mendoza (MDZ), the pilot landed the aircraft at the airport in Neuquén at 22:20. After refuelling and carrying out the planned dispatch, the crew and 19 passengers (18 adults and one minor) on board, prepared to make the last leg of the flight OSL5428, from Neuquén Airport (NQN) to the final destination: Comodoro Rivadavia International Airport (CRD). The flight took off at 23:05. After the take-off, the aircraft started to climb AWY T 105, to reach FL190, in accordance with the flight plan. After flying for 24 minutes, the pilot levelled the aircraft at 17,800 feet, and remained at this level for approximately 9 minutes. Due to the fact that the meteorological conditions at this level caused icing, the technical crew descended to FL (flight level) 140. Shifting to FL140 took five minutes. During this stage of the flight the icing conditions steadily worsened. By the time the aircraft had reached FL140, the icing conditions were severe. The aircraft flew for approximately two minutes with a straight and level flight attitude, increasing the accumulation of ice. Then the aircraft completely lost lift, which resulted in a loss of control, and the subsequent entry into abnormal flight attitude. The aircraft plunged towards the earth and impacted the ground, which resulted in a fire. Everyone on board perished and the aircraft was destroyed. The accident happened at night under IMC conditions.
Probable cause:
During a commercial, domestic passenger flight, while cruising, the crew lost control of the aircraft, which uncontrollably impacted the ground due to severe ice formation caused by the following factors:
- Entering an area with icing conditions without adequately monitoring the warning signals from the external environment (temperature, cloudiness, precipitation and ice accumulation) or the internal (speed, angle of attack), which allowed for prolonged operations in icing conditions to take place.
- Receiving a forecast for slight icing - given that the aircraft encountered sever icing conditions - which led to a lack of understanding regarding the specific meteorological danger.
- Inadequately evaluating the risks, which led to mitigating measures such as adequate briefing (distribution of tasks in the cockpit, review of the de-icing systems, limitations, use of power, use of autopilot, diversion strategy etc.) not being adopted.
- Levels of stress increasing, due to operations not having the expected effects, which led the crew to lose focus on other issues.
- Icing conditions that surpassed the aircraft's ice protection systems, which were certified for the aircraft (FAR 25 Appendix C).
- Inadequate use of speed, by maintaining the speed close to stall speed during flight in icing conditions.
- Inadequate use of the autopilot, by not selecting the IAS mode when flying in icing conditions.
- Partially carrying out the procedures established in the Flight Manual and the Operations Manual, when entering into areas with severe icing conditions.
- Realizing late that the aircraft had started to stall, because the buffeting that foretells a stall was confused with the vibrations that signify ice contamination on the propellers.
- Activation of the Stick Shaker and Stall Warning at a lower speed than expected in icing conditions.
- Using a stall recovery technique which prioritized the reduction of the angle of attack at the expense of altitude loss, and which was inappropriate for the flight conditions.
- The aileron flight controls reacting in an unusual manner when the aircraft lost control, probably due to the accumulation of ice in the surfaces of these, which made it impossible for the aircraft to recover. The increasingly stressful situation of the crew, which affected its operational decision-making.
Final Report:

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.

Crash of a Piper PA-31T Cheyenne II in Valparaiso

Date & Time: Apr 15, 2011 at 1200 LT
Type of aircraft:
Registration:
CC-CZC
Flight Type:
Survivors:
Yes
Schedule:
Robinson Crusoe Island - Valparaiso
MSN:
31-7920072
YOM:
1979
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7396
Captain / Total hours on type:
1092.00
Aircraft flight hours:
7168
Circumstances:
The twin engine aircraft departed Robinson Crusoe Island on a cargo flight to Valparaiso, carrying one passenger, one pilot and a load consisting of 1,000 lbs of lobsters. Upon landing at Valparaiso Airport in good weather conditions, the airplane went out of control, veered off runway, crossed a road and came to rest in a wooded area located along the highway. The aircraft was damaged beyond repair and both occupants escaped with minor injuries.
Probable cause:
The most likely cause of the accident would have been the loss of control of the aircraft when performing the flare, caused by a loss of lift (stall), because the CofG was beyond the rear limit.
The following contributing factors were identified:
- The aircraft was unstable on its longitudinal axis because the CofG was too far aft,
- The cargo was not properly secured in the cabin.
Final Report: