Crash of a PZL-Mielec AN-2T in Santa Isabel

Date & Time: Oct 24, 2010 at 1145 LT
Type of aircraft:
Operator:
Registration:
CX-CAP
Survivors:
Yes
Schedule:
Santa Isabel - Santa Isabel
MSN:
1G142-31
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1200
Captain / Total hours on type:
100.00
Aircraft flight hours:
4339
Circumstances:
The single engine aircraft was engaged in a local skydiving mission in Santa Isabel, carrying nine skydivers and one pilot. Shortly after takeoff, while climbing to a height of about 150 metres, the engine lost power. The pilot decided to return immediately. Upon landing, the aircraft collided with bushes and came to rest, bursting into flames. All 10 occupants escaped unhurt while the aircraft was totally destroyed by fire.
Probable cause:
The exact cause of the accident could not be determined.
Final Report:

Crash of a Harbin Yunsunji Y-12-II in Mukinge

Date & Time: Oct 16, 2010
Type of aircraft:
Operator:
Registration:
AF-215
Flight Type:
Survivors:
Yes
Schedule:
Lusaka – Mukinge
MSN:
0088
YOM:
1994
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Lusaka on a flight to Mukinge, carrying staff and various goods on behalf of the Zambian Presidency. After touchdown, the aircraft veered off runway and came to rest against trees. All occupants escaped uninjured while the aircraft was damaged beyond repair. The crew was flying to Mukinge, preparing the next official visit of the President of the Republic of Zambia Rupiah Banda.

Crash of an Airbus A319-132 in Palermo

Date & Time: Sep 24, 2010 at 2007 LT
Type of aircraft:
Operator:
Registration:
EI-EDM
Survivors:
Yes
Schedule:
Rome - Palermo
MSN:
2424
YOM:
2005
Flight number:
JET243
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
124
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13860
Captain / Total hours on type:
2918.00
Copilot / Total flying hours:
1182
Copilot / Total hours on type:
937
Aircraft flight hours:
15763
Aircraft flight cycles:
8936
Circumstances:
Following an uneventful flight from Rome-Fiumicino Airport, the crew started a night approach to Palermo-Punta Raisi Airport in poor weather conditions with heavy rain falls, thunderstorm activity and reduced visibility. During the descent, weather information was transmitted to the crew, indicating a visibility of 4 km with few CB's at 1,800 feet and a windshear warning for runway 20. On final approach, at an altitude of 810 feet (100 feet above MDA), following the 'minimum' call, the captain instructed the copilot to continue the approach despite the copilot did not establish a visual contact with the runway. At an altitude of 240 feet, the copilot reported the runway in sight but informed the captain that all four PAPI's lights were red. The captain took over control and continued the approach after the airplane deviated from the descent profile. With an excessive rate of descent of 1,360 feet per minute, the aircraft impacted ground 367 metres short of runway 07 threshold and collided with the runway 25 localizer antenna. Upon impact, both main landing gear were partially torn off. The aircraft slid for about 850 metres before coming to rest on the left of the runway. All 129 occupants were rescued, among them 35 were injured. The aircraft was damaged beyond repair.
Probable cause:
The event is classified as short landing accident and the cause is mainly due to human factors. The fact that the aircraft contacted the ground took place about 367 meters short of the runway threshold was due to the crew's decision to continue the instrument approach without a declared shared acquisition of the necessary visual references for the completion of the non-precision procedure and of the landing maneuver. The investigation revealed no elements to consider that the incident occurred due to technical factors inherent in the aircraft.
The following contributing factors were identified:
- The poor attitude of those present in the cockpit to use of basics of CRM, particularly with regard to interpersonal and cognitive abilities of each and, overwhelmingly, the commander.
- Deliberate failure to comply with SOP in place which provided, reaching the MDA, to apply the missed approach procedure where adequate visual reference of the runway in use had not been in sight of both pilots.
- Failure to apply, by those present in the cockpit, the operators rules, concerning in particular: the concept of "sterile cockpit"; to do the descent briefing; to make callouts on final approach.
- The routine with the crew, carrying out approaches to Palermo-Punta Raisi Airport, from which the complacency to favor the personalization of the standards set by operator, and by law. The complacency is one of the most insidious aspects in the context of the human factor, as it creeps in individual self-satisfaction of a condition, which generates a lowering of situational awareness, however bringing them to believe they had found the best formula to operate.
- The existence of adverse weather conditions, characterized by the presence of an extreme rainfall, which significantly reduced the overall visibility.
- The "black hole approach" phenomenon, due to adverse weather conditions together with an approach carried out at night, the sea, to a coast characterized by few dimly lit urban settlements.
This created the illusion in the PF of "feeling high" compared to what he saw and believed to be the threshold, with the result to get him to abandon the ideal descent profile, hitherto maintained, to make a correction and the subsequent short landing.
- The decrease of performance of the light beam produced by SLTH in extreme rain conditions; The only bright horizontal reference for the crew consisted of the crossbar of the SALS, probably mistaken for the threshold lights.
Final Report:

Crash of a Rockwell Aero Commander 500 in Santo Domingo

Date & Time: Sep 23, 2010 at 1245 LT
Registration:
N100PV
Flight Type:
Survivors:
Yes
Schedule:
San Juan - Santo Domingo
MSN:
500-784
YOM:
1959
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2500
Captain / Total hours on type:
100.00
Aircraft flight hours:
7810
Circumstances:
The twin engine aircraft departed San Juan-Isla Grande Airport on a private flight to Santo Domingo with two passengers and two pilots on board. On final approach to Santo Domingo-Las Américas-Dr. José Francisco Peña Gómez Airport, at an altitude of 2,000 feet and at a distance of 8 km from the airport, both engines failed simultaneously. As the crew realized he was unable to reach the airport, he attempted an emergency landing when the aircraft crashed in a dense wooded area located about one km southeast of runway 35 threshold. All four occupants escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
Double engine failure on final approach due to fuel exhaustion. It was determined that prior to takeoff from San Juan Airport, the fuel quantity in the tanks was sufficient for the flight to Santo Domingo. But the fuel cap was missing prior to takeoff and the crew applied some 'duct tape' in an attempt to replace the fuel cap. Despite the aircraft was unworthy, the crew decided to takeoff in such conditions. Because the fuel cap was missing, some fuel leaked in flight, causing both engines to stop on final approach to Santo Domingo Airport.
Final Report:

Crash of a Beechcraft B100 King Air in Montmagny

Date & Time: Sep 22, 2010 at 1700 LT
Type of aircraft:
Operator:
Registration:
C-FSIK
Flight Phase:
Survivors:
Yes
Schedule:
Montmagny - Montreal
MSN:
BE-39
YOM:
1978
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4500
Captain / Total hours on type:
2500.00
Copilot / Total flying hours:
7800
Copilot / Total hours on type:
675
Circumstances:
The aircraft was operating as flight MAX100 on an instrument flight rules flight from Montmagny to Montreal/St-Hubert, Quebec, with 2 pilots and 4 passengers on board. At approximately 1700 Eastern Daylight Time, the aircraft moved into position on the threshold of 3010-foot-long runway 26 and initiated the take-off. On the rotation, at approximately 100 knots, the flight crew saw numerous birds in the last quarter of the runway. While getting airborne, the aircraft struck the birds and the left engine lost power, causing the aircraft to yaw and roll to the left. The aircraft lost altitude and touched the runway to the left of the centre line and less than 100 feet from the runway end. The take-off was aborted and the aircraft overran the runway, coming to rest in a field 885 feet from the runway end. All occupants evacuated the aircraft via the main door. There were no injuries. The aircraft was substantially damaged.
Probable cause:
Findings As To Causes and Contributing Factors:
The bird strike occurred on take-off at an altitude of less than 50 feet. Gulls were ingested in the left engine, which then lost power.
After the loss of engine power, the flight crew had difficulty controlling the aircraft. The aircraft touched the ground, forcing the pilot flying to abort the take-off when the runway remaining was insufficient to stop the aircraft, resulting in the runway overrun.
Findings As To Risks:
Although a cannon was in place, it was not working on the day of the accident, which increased the risk of a bird strike.
The presence of a goose and duck farm outside the airport perimeter but near a runway increases the risk of attracting gulls.
Operators subject to Canadian Aviation Regulations Subpart 703 are not prohibited from having an aircraft take off from a runway that is shorter than the accelerate-stop distance of that aircraft as determined from the performance diagrams. Consequently, travellers carried by these operators are exposed to the risks associated with a runway overrun when a take-off is aborted.
The absence of a CVR makes it harder to ascertain material facts. Consequently, investigations can take more time, resulting in delays which compromise public safety.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in South Bimini

Date & Time: Sep 19, 2010 at 1440 LT
Operator:
Registration:
N84859
Survivors:
Yes
Schedule:
South Bimini - Fort Lauderdale
MSN:
31-7305043
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On September 19, 2010, at 1440 eastern daylight time, a Piper PA31-350, N84859, registered to Spirit Air Inc, and operated by Pioneer Air Service was on initial climb out when the lower half of the main cabin door came open. The pilot reversed his course and returned to the departure airport, landing on runway 27. The right main landing gear tire blew out on the landing roll. The airplane went off the right side of the runway, struck a tree, caught fire and came to a complete stop. Visual meteorological conditions prevailed and an instrument flight plan was filed. The commercial pilot and five passengers were not injured and the airplane received substantial damage. The flight originated from Bimini Airport, South Bimini Island, Bahamas, at 1435, and was operated in accordance with 14 Code of Federal Regulations Part 135.

Crash of an ATR42-320 in Puerto Ordaz: 17 killed

Date & Time: Sep 13, 2010 at 1023 LT
Type of aircraft:
Operator:
Registration:
YV1010
Survivors:
Yes
Schedule:
Porlamar - Puerto Ordaz
MSN:
371
YOM:
1994
Flight number:
VCV2350
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
17
Captain / Total hours on type:
1574.00
Copilot / Total flying hours:
1083
Copilot / Total hours on type:
483
Aircraft flight hours:
27085
Aircraft flight cycles:
29603
Circumstances:
Following two uneventful flights to Santiago Mariño and Maturín, the aircraft departed Porlamar on a flight to Puerto Ordaz with 47 passengers and a crew of four on board. While descending to Puerto Ordaz, at an altitude of 13,500 feet and at a distance of 79 km from the destination, the crew reported control difficulties. After being prioritized, the crew was instructed for an approach and landing on runway 07. At 1021LT, the crew reported his position at 3,000 feet and 28 km from the destination Airport. Two minutes later, the message 'mayday mayday mayday' was heard on the frequency. The aircraft went out of control and crashed in an industrial area located about 9 km short of runway, bursting into flames. Three crew members and 14 passengers were killed while 34 other occupants were injured, 10 seriously.
Probable cause:
The most probable cause for the occurrence of the accident was the malfunction of the centralized crew warning system (CCAS/CAC) with erroneous activation of the flight loss of lift warning system.
The following contributing factors were identified:
- Poor crew resources management,
- Loss of situational awareness,
- Inadequate coordination during the decision-making process to deal with abnormal situations in flight,
- Ignorance of the loss of lift warning system.
- Inadequate handling of flight controls.
Final Report:

Crash of a Fletcher FU-24-954 in Fox Glacier: 9 killed

Date & Time: Sep 4, 2010 at 1327 LT
Type of aircraft:
Registration:
ZK-EUF
Flight Phase:
Survivors:
No
Schedule:
Fox Glacier - Fox Glacier
MSN:
281
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
9
Captain / Total flying hours:
4554
Captain / Total hours on type:
41.00
Circumstances:
Shortly after take off from Fox Glacier aerodrome, while climbing, aircraft stalled and crashed in flames in a paddock near the airfield. All nine occupants, the pilot and 8 skydivers, were killed. The new owner and operator of the aeroplane had not completed any weight and balance calculations on the aeroplane before it entered service, nor at any time before the accident. As a result the aeroplane was being flown outside its loading limits every time it carried a full load of 8 parachutists. On the accident flight the centre of gravity of the aeroplane was well rear of its aft limit and it became airborne at too low a speed to be controllable. The pilot was unable to regain control and the aeroplane continued to pitch up, then rolled left before striking the ground nearly vertically.
Probable cause:
Findings:
- There were no technical defects identified that may have contributed to the accident and the aeroplane was considered controllable during the take-off roll, with the engine able to deliver power during the short flight.
- The aeroplane’s centre of gravity was at least 0.122m rear of the maximum permissible limit, which created a tendency for the nose to pitch up. The most likely reason for the crash was the aeroplane being excessively out of balance. In addition, the aeroplane probably became airborne early and at too low an airspeed to prevent uncontrollable nose-up pitch.
- The aeroplane reached a pitch angle that would have made it highly improbable for the unrestrained parachutists to prevent themselves sliding back towards the tail. Any shift in weight rearward would have made the aeroplane more unstable.
- The engineering company that modified ZK-EUF for parachuting operations did not follow proper processes required by civil aviation rules and guidance. Two of the modifications had been approved for a different aircraft type, one modification belonged to another design holder and a fourth was not referred to in the aircraft maintenance logbook.
- The flight manual for ZK-EUF had not been updated to reflect the new role of the aeroplane and was limited in its usefulness to the aeroplane owner for calculating weight and balance.
- Regardless of the procedural issues with the project to modify ZK-EUF, the engineering work conducted on ZK-EUF to convert it from agricultural to parachuting operations in the standard category was by all accounts appropriately carried out.
- The weight and balance of the aeroplane, with its centre of gravity at least 0.122m outside the maximum aft limit, would have caused serious handling issues for the pilot and was the most significant factor contributing to the accident.
- ZK-EUF was 17 kg over its maximum permissible weight on the accident flight, but was still 242 kg lighter than the maximum all-up weight for which the aeroplane was certified in its previous agricultural role. Had the aeroplane not been out of balance it is considered the excess weight in itself would have been unlikely to cause the accident. Nevertheless, the pilots should have made a full weight and balance calculation before each flight.
- The aeroplane owner and their pilots did not comply with civil aviation rules and did not follow good, sound aviation practice by failing to conduct weight and balance calculations on the aeroplane. This resulted in the aeroplane being routinely flown overweight and outside the aft centre of gravity allowable limit whenever it carried 8 parachutists.
- The empty weight and balance for ZK-EUF was properly recorded in the flight manual, but the stability information in that manual had not been appropriately amended to reflect its new role of a parachute aeroplane. Nevertheless, it was still possible for the aeroplane operator to initially have calculated the weight and balance of the aeroplane for the predicted operational loads before entering the aeroplane into service.
- The aeroplane owner did not comply with civil aviation rules and did not follow good, sound aviation practice when they: used the incorrect amount of fuel reserves; removed the flight manual from the aeroplane; and did not formulate their own standard operating procedures before using the aeroplane for commercial parachuting operations.
- The Director of Civil Aviation delegated the task of assessing and overseeing major modifications to Rule Part 146 design organisations and individual holders of “inspection authorisations”. The delegations did not absolve the Director of his responsibility to monitor compliance with civil aviation rules and guidance.
Page 38 | Report 10-009
- The delegations increased the risk that unless properly managed the CAA could lose control of 2 safety-critical functions: design and inspection. The Director had not appropriately managed that risk with the current oversight programme.
- The CAA had adhered strictly to its normal practice and was acting in accordance with civil aviation rules when approving the change in airworthiness category from special to standard. However, knowing the scope, size and complexity of the modifications required to change ZK-EUF from an agricultural to a parachuting aeroplane, it should have had greater participation in the process to help ensure there were no safety implications.
- There was a flaw in the regulatory system that allowed an engineering company undertaking major modification work on an aircraft to have little or no CAA involvement by using an internal or contracted design delegation holder and a person with the inspection authorisation to oversee and sign off the work.
- The level of parachuting activity in New Zealand warranted a stronger level of regulatory oversight than had been applied in recent years.
- The CAA’s oversight and surveillance of commercial parachuting were not adequate to ensure that operators were functioning in a safe manner.
- The CAA had mechanisms through the Director’s powers under the Civil Aviation Act and his designated powers under the HSE Act to effectively regulate the parachuting industry pending the introduction of Rule Part 115.
- An alcohol and drug testing regime needs to be initiated for persons performing activities critical to flight safety, to detect and deter the use of performance-impairing substances.
- In this case the impact was not survivable and the passengers wearing safety restraints would not have prevented their deaths, but in other circumstances the wearing of safety restraints might reduce injuries and save lives.
- Safety harnesses or restraints would help to prevent passengers sliding rearward and altering the centre of gravity of the aircraft. It could not be established if this was a factor in this accident.
Final Report:

Crash of a Cessna 207A Skywagon in Tuluksak

Date & Time: Sep 3, 2010 at 1830 LT
Operator:
Registration:
N9942M
Flight Phase:
Survivors:
Yes
Schedule:
Tuluksak - Bethel
MSN:
207-0756
YOM:
1983
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4545
Captain / Total hours on type:
245.00
Aircraft flight hours:
29550
Circumstances:
Shortly after take off from runway 20, aircraft hit tree tops, stalled and crashed in a wooded area near the airport. Both passenger were slightly injured while the pilot was seriously injured. Aircraft was damaged beyond repair. The director of operations for the operator stated that soft field conditions and standing water on the runway slowed the airplane during the takeoff roll. The airplane did not lift off in time to clear trees at the end of the runway and sustained substantial damage to both wings and the fuselage when it collided with the trees. The pilot reported that he used partial power at the beginning of the takeoff roll to avoid hitting standing water on the runway with full power. After passing most of the water, he applied full power, but the airplane did not accelerate like he thought it would. He recalled the airplane being in a nose-high attitude and the main wheels bouncing several times before the airplane impacted the trees at the end of the runway.
Probable cause:
The pilot's delayed application of full power during a soft/wet field takeoff, resulting in a collision with trees during takeoff.
Final Report:

Crash of a Cessna 550 Citation II in Bwagaoia: 4 killed

Date & Time: Aug 31, 2010 at 1615 LT
Type of aircraft:
Registration:
P2-TAA
Survivors:
Yes
Schedule:
Port Moresby – Bwagaoia
MSN:
550-0145
YOM:
1980
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
14591
Copilot / Total flying hours:
872
Aircraft flight hours:
14268
Circumstances:
The aircraft was conducting a charter flight from Jackson’s International Airport, Port Moresby, National Capital District, Papua New Guinea (PNG), to Bwagaoia Aerodrome, Misima Island, Milne Bay Province, PNG (Misima). There were two pilots and three passengers on board for the flight. The approach and landing was undertaken during a heavy rain storm over Bwagaoia Aerodrome at the time, which resulted in standing water on the runway. This water, combined with the aircraft’s speed caused the aircraft to aquaplane. There was also a tailwind, which contributed the aircraft to landing further along the runway than normal. The pilot in command (PIC) initiated a baulked landing procedure. The aircraft was not able to gain flying speed by the end of the runway and did not climb. The aircraft descended into terrain 100 m beyond the end of the runway. The aircraft impacted terrain at the end of runway 26 at 1615:30 PNG local time and the aircraft was destroyed by a post-impact, fuel-fed fire. The copilot was the only survivor. Other persons who came to assist were unable to rescue the remaining occupants because of fire and explosions in the aircraft. The on-site evidence and reports from the surviving copilot indicated that the aircraft was serviceable and producing significant power at the time of impact. Further investigation found that the same aircraft and PIC were involved in a previous landing overrun at Misima Island in February 2009.
Probable cause:
Contributing safety factors:
• The operator’s processes for determining the aircraft’s required landing distance did not appropriately consider all of the relevant performance factors.
• The operator’s processes for learning and implementing change from the previous runway overrun incident were ineffective.
• The flight crew did not use effective crew resource management techniques to manage the approach and landing.
• The crew landed long on a runway that was too short, affected by a tailwind, had a degraded surface and was water contaminated.
• The crew did not carry out a go-around during the approach when the visibility was less than the minimum requirements for a visual approach.
• The baulked landing that was initiated too late to assure a safe takeoff.
Other safety factors:
• The aircraft aquaplaned during the landing roll, limiting its deceleration.
• The runway surface was described as gravel, but had degraded over time.
• The weather station anemometer was giving an incorrect wind indication.
Final Report: