Crash of a Piper PA-31-350 Navajo Chieftain in Bogotá: 8 killed

Date & Time: Sep 1, 2005 at 1045 LT
Operator:
Registration:
HK-3069P
Flight Phase:
Survivors:
No
Schedule:
Bogotá - Puerto Berrío
MSN:
31-8352036
YOM:
1983
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
753
Captain / Total hours on type:
83.00
Copilot / Total flying hours:
105
Aircraft flight hours:
2090
Circumstances:
Shortly after takeoff from Bogotá-Guaymaral Airport runway 10, while in initial climb, the crew initiated a left turn in accordance with procedures. The copilot contacted ATC and declared an emergency following technical problems. The crew was immediately cleared to land at his discretion when the aircraft entered an uncontrolled descent and crashed in a prairie located 600 metres from the runway 28 threshold. The aircraft was totally destroyed and all eight occupants were killed.
Probable cause:
A possible fuel contamination affected the power on one engine or both. The aircraft was overloaded at takeoff, which, compounded by the considerable loss of power to the engines due to the altitude of the aerodrome, did not allow the pilot to maneuver the aircraft to return to the runway. In addition, the center of gravity, despite being within the permissible limits, was too far behind for an operation in adverse weather conditions.
Final Report:

Crash of a Britten-Norman BN-2B-27 Islander in Durban

Date & Time: Aug 21, 2005 at 1300 LT
Type of aircraft:
Operator:
Registration:
ZS-PCJ
Survivors:
Yes
Site:
Schedule:
Manzengwenya – Durban
MSN:
869
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
950
Captain / Total hours on type:
6.00
Aircraft flight hours:
7670
Circumstances:
The pilot accompanied by five passengers took off from Manzengwenya Aerodrome on a chartered flight to Virginia Aerodrome, (FAVG). The pilot reported that although it was drizzling, visibility was good. He reported his position to the FAVG Air Traffic Controller and requested joining instructions to FAVG. The ATC cleared the pilot to land on Runway 05. When he was on short finals, the tower noticed that the aircraft was drifting away from the runway centerline and called the pilot. The pilot stated that he is experiencing an engine problems and he is initiating a go around. The aircraft turned out to the left and away from the runway centerline, and the pilot allowed the aircraft to continue flying over the nearby “M4” highway and then towards a residential area. The aircraft then impacted the roof of a private residential property, (house) with its left wing first and the nose section. It came to rest in a tail high and inverted position. Although the wreckage was still fairly intact, both the aircraft and the residential property were extensively damaged. The aircraft’s left wing failed outboard of the engine on impact. The nose of the aircraft as well as the cabin instrumentation area was crushed towards the front seated passengers. Both main wing spars, the nose wheel, the engine mounts, the propellers, and the fuselage were also damaged. The aircraft had a valid Certificate of Airworthiness which was issued on 17 September 2004 with an expiry date of 16 September 2005. The last Mandatory Periodic Inspection was certified on 03 September 2004 at 7594.2 airframe hours and he aircraft had accumulated a further 75.8 hours since the last MPI was certified. The aircraft was recovered to an Approved AMO for further investigation. Both flight and engine controls were found satisfactory. Ground run test were conducted with both engines still installed to the aircraft, and both engines performed satisfactorily during these performance tests. The Aircraft Maintenance Organisation was audited in the last two years and the last audit was on 01 July 2005.
Probable cause:
The pilot employed a incorrect go-around technique and took inappropriate actions during the emergency situation, which aggravated the situation.
Contributory Factors:
- Prevalent carburettor icing probability conditions for any power setting.
- Lack of experience of the pilot on the aircraft type.
Final Report:

Crash of a McDonnell Douglas MD-82 in Machiques: 160 killed

Date & Time: Aug 16, 2005 at 0300 LT
Type of aircraft:
Operator:
Registration:
HK-4374X
Flight Phase:
Survivors:
No
Schedule:
Panama City - Fort-de-France
MSN:
49484
YOM:
1986
Flight number:
YH708
Location:
Country:
Crew on board:
8
Crew fatalities:
Pax on board:
152
Pax fatalities:
Other fatalities:
Total fatalities:
160
Captain / Total flying hours:
5942
Captain / Total hours on type:
1128.00
Copilot / Total flying hours:
1341
Copilot / Total hours on type:
862
Aircraft flight hours:
49494
Aircraft flight cycles:
24312
Circumstances:
The MD-82 arrived at Panama City-Tocumen after a flight from Medellín-José María Córdova Airport (MDE). The plane was then prepared to carry out a flight to the Caribbean island of Martinique. Flight WCW 708 departed Panama City at about 06:00 UTC and climbed to its cruising altitude of FL310. This altitude was reached at about 06:25 UTC. Sixteen minutes later the airplane began a normal climb to FL330. At 06:49 the speed began to steadily decrease from Mach 0.76. The horizontal stabilizer moved from about 2 units nose up to about 4 units nose up during this deceleration. At 06:51 UTC the crew reported at FL330 over the SIDOS waypoint, over the Colombian/Venezuelan border, and requested a direct course to the ONGAL waypoint. The controller instructed the crew to continue on the present heading and to await further clearance direct to ONGAL. The flight crew meanwhile discussed weather concerns that included possible icing conditions and the possible need to turn on engine and airfoil anti-ice. At 06:57 UTC the flight crew requested permission to descend to FL310, which was approved. The autopilot was disconnected and the airplane started to descend. As the airplane descended past about FL315, the airspeed continued to decrease and the engine EPR decreased to about flight idle. Two minutes later a further descent to FL290 was requested, but the controller at Maiquetía did not understand that this was a request from flight 708 and asked who was calling. Flight 708 responded and immediately requested descent to FL240. The controller inquired about the state of the aircraft, to which they responded that both engines had flamed out. The controller then cleared the flight to descent at pilot's discretion. In the meantime, the altitude alert warning had activated, followed by the stick shaker and the aural stall warning alert. The airspeed had reached a minimum of about 150 indicated air speed (IAS) knots at about FL250. The crew reported descending through FL140 and reported that they were not able to control the airplane. The aircraft descended at 7,000 ft/min, and finally crashed in a swampy area. The aircraft disintegrated on impact and all 160 occupants were killed. Debris were found on an area of 205 metres long and 110 metres wide. The entire descent from FL330 had taken approximately 3 minutes and 30 seconds.
Probable cause:
Given the aerodynamic and performance conditions, the aircraft was taken to a critical state, which led to a loss of lift. Consequently, the cockpit resource management (CRM) and decision-making during the development of emergency were misguided. This was caused by the following:
a) Awareness of environment (or situational awareness) insufficient or improper that allowed the cockpit crew, not being full and timely aware of what was happening regarding the performance and behavior of the aircraft.
b) Lack of effective communication between the cockpit crew that limited, within the decision making process, the possibility to timely choose appropriate alternatives and options and to set respective priorities in the actions taken at the time when it was established that there was a critical or emergency situation (stall condition at high altitude).
It is found that the cause of the accident is determined by the absence of appropriate action to correct the stall of the aircraft, and also in the emergency up to the impact with the ground, at an inappropriate hierarchy of priorities in implementing the procedures. Subsequently, the operations were conducted outside of the limits and parameters set by the manufacturer's manual performance, together with an inadequate flight planning by failing to consider meteorological aspects, in addition a misinterpretation and late of the energy state of the aircraft by the flight crew. Therefore, the evidence shows the classification of "Human Factor" as a cause of this accident.
Final Report:

Crash of a Dornier DO.28D-2 Skyservant off Puerto Ayacucho: 1 killed

Date & Time: Aug 14, 2005 at 1230 LT
Type of aircraft:
Registration:
YV-740C
Flight Phase:
Survivors:
Yes
MSN:
4113
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Puerto Ayacucho Airport, while climbing, one of the engine failed. The aircraft stalled and crashed in the Orinoco River, coming to rest upside down. A passenger was killed while 12 other occupants were injured.
Probable cause:
Engine failure for unknown reasons.

Crash of a Piper PA-31-350 Navajo Chieftain in Fort Lauderdale

Date & Time: Aug 13, 2005 at 1557 LT
Operator:
Registration:
N318JL
Survivors:
Yes
Schedule:
North Eleuthera - Fort Lauderdale
MSN:
31-8152033
YOM:
1981
Flight number:
TTL217
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14500
Captain / Total hours on type:
6550.00
Circumstances:
The pilot provided an emergency briefing to the passengers before departure. The outboard fuel tanks were empty and the inboard fuel tanks were filled before departure. After takeoff, the flight climbed to 8,500 feet msl and proceeded towards the destination airport. During cruise flight while flying at 1,000 feet msl approximately 10 miles from the destination airport , the left engine started losing power, but the airplane did not yaw; the left cowl flap was closed at the time. The pilot reported the left fuel flow light was on, but the fuel pressure was in the green arc (indicating approximately 38 to 42 psi). He switched each fuel selector to its respective outboard fuel tank though the outboard tanks were empty, turned on both emergency fuel pumps, and also attempted cross feeding fuel to the left engine in an effort to restore engine power but was unsuccessful. The left engine manifold pressure decreased to 18 inHg, and he was maintaining "blue line" airspeed plus a few knots with the right engine at full power. He slowed the airplane to less than blue line airspeed in an attempt to "gain altitude", and approximately 2 to 3 minutes after first noticing the loss of engine power from the left engine with the manifold pressure indication of 15 inHg, and after seeing boats nearby, he moved the left propeller control to the feather position but later reported the propeller did not feather. The left engine rpm was in the upper green arc through the whole event, and he did not see any oil coming out of the left engine cowling. The flight was unable to maintain altitude, and he advised the passengers to don but not inflate their life vests. He maneuvered the airplane into the wind near boats, and ditched with the flaps and landing gear retracted. All occupants exited the airplane and were rescued by one of the nearby boats. Each inboard fuel tank is equipped with a "surge tank" and a flapper valve, and also a sensing probe installed at the outlet of the tank. The airplane POH/AFM indicates that if the fuel flow light illuminates, and there is fuel in the corresponding tank, a malfunction of the flapper valve has occurred. The airplane was not recovered; therefore no determination could be made as to the reason for the reported loss of engine power from the left engine, nor the reason for the failure of the left propeller to feather.
Probable cause:
The reported loss of engine power from the left engine, and the failure of the left propeller to feather for undetermined reasons, resulting in the inability to maintain altitude, and subsequent ditching.
Final Report:

Crash of an ATR72-202 off Palermo: 16 killed

Date & Time: Aug 6, 2005 at 1539 LT
Type of aircraft:
Operator:
Registration:
TS-LBB
Flight Phase:
Survivors:
Yes
Schedule:
Bari – Djerba
MSN:
258
YOM:
1992
Flight number:
TUI1153
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
35
Pax fatalities:
Other fatalities:
Total fatalities:
16
Captain / Total flying hours:
7182
Captain / Total hours on type:
5582.00
Copilot / Total flying hours:
2431
Copilot / Total hours on type:
2130
Aircraft flight hours:
29893
Aircraft flight cycles:
35259
Circumstances:
The aircraft departed Bari at 1432LT on flight TUI1153 to Djerba with 39 people on board, 4 crew members, 35 passengers among which one airline engineer. While cruising, approximately 50 minutes after takeoff, at flight level 230, the right engine shut down and after approximately 100 seconds, also the left engine shut down. The flight crew decided to divert to the airport at Palermo, Punta Raisi, to make a precautionary landing. The crew referred to having tried to restart both engines, but without success. After gliding approximately 16 minutes, the aircraft ditched approximately 23 nautical miles northeast from Palermo's airport, Punta Raisi, within Italian territorial waters. On impact with the surface of the sea, the aircraft broke into three pieces; 14 passengers, the airliner engineer and a member of the crew (senior flight attendant) reported fatal injuries. The other occupants suffered serious to minor injuries.
Probable cause:
The accident under examination, as most aviation accidents, has been determined by a series of events linked one another, which caused the final ditching. The ditching was primarily due to the both engines flame out because of fuel exhaustion. The incorrect replacement of the fuel quantity indicator (FQI) was one of the contributing factors which led irremediably to the accident. The accident’s cause is therefore traceable firstly to the incorrect procedure used for replacing the FQI, by means of the operator’s maintenance personnel. This shall be considered the disruptive element, which caused the final ditching of the aircraft due to the lack of fuel that caused the shutdown of both engines. As said before the accident was determined by a series of events (contributing factors) linked one another. Hereafter are listed some considered of major importance.
- Errors committed by ground mechanics when searching for and correctly identifying the fuel indicator.
- Errors committed by the flight crew: non-respect of various operational procedures.
- Inadequate checks by the competent office of the operator that flight crew were respecting operational procedures.
- Inaccuracy of the information entered in the aircraft management and spares information system and the absence of an effective control of the system itself.
- Inadequate training for aircraft management and spares information system use and absence of a responsible person appointed for managing the system itself.
- Maintenance and organization standards of the operator unsatisfactory for an adequate aircraft management.
- Lack of an adequate quality assurance system;
- Inadequate surveillance of the operator by the competent Tunisian authority.
- Installation characteristics of fuel quantity indicators (FQI) for ATR 42 and ATR 72 which made it possible to install an ATR 42 type FQI in an ATR 72, and vice versa.
The analysis of various factors that contributed to the event has been carried out according to the so called Reason’s "Organizational accident" model. Active failures, which had triggered the accident, are those committed both by ground mechanics/technicians the day before the event while searching for and replacing the fuel quantity indicator, and by the crew who did not verify and fully and accurately complete the aircraft’s documentation, through which it would have been possible to perceive an anomalous situation regarding the quantity of fuel onboard. Latent failures, however, remained concealed, latent in the operator’s organizational system until, some active errors (by mechanics and pilots) were made, overcoming the system’s defence barriers, causing the accident. Analysing latent and active failures (errors) traceable to various parties, involved in the event in several respects, it clearly emerges that they were operating in a potentially deceptive organizational system. When latent failures remain within a system without being identified and eliminated, the possibility of mutual interaction increases, making the system susceptible for active failures, or not allowing the system to prevent them, in case of errors. Active failures were inserted in a context characterised by organizational and maintenance deficiencies. The error that led to the accident was committed by mechanics who searched for and replaced the FQI, but this error occurred in an organizational setting in which, if everybody were operating correctly, probably the accident would not have occurred. Inaccuracy of information entered in the aircraft management and spares information system, particularly regarding the interchangeability of items and the absence of an effective control of the system itself, has been considered in fact one of the latent failures that contributed to the event. The maintenance and organization standards of the operator, at the time of event, were not considered satisfactory for an adequate management of the aircraft. The flight crew and maintenance mechanics/technicians involved in the event, when they made incorrect choices and took actions not complying with standard procedures, did not receive sufficiently effective aid from the system in order to avoid the error.
Final Report:

Crash of a Pilatus PC-6/B2-H4 Turbo Porter off Brasilito: 6 killed

Date & Time: Jul 16, 2005 at 0945 LT
Operator:
Registration:
N908PL
Flight Phase:
Survivors:
No
Schedule:
Tamarindo - Tamarindo
MSN:
908
YOM:
1994
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The single engine aircraft departed Tamarindo on a sightseeing flight with five passengers and one pilot on board. While flying at low height, the aircraft went out of control and crashed in the sea some 1,300 metres offshore. The aircraft sank by a depth of 50 metres and all six occupants were killed.

Crash of a Piper PA-31-350 Navajo Chieftain in Mount Hotham: 3 killed

Date & Time: Jul 8, 2005 at 1725 LT
Operator:
Registration:
VH-OAO
Survivors:
No
Schedule:
Melbourne - Mount Hotham
MSN:
31-8252021
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
4770
Captain / Total hours on type:
1269.00
Aircraft flight hours:
9137
Circumstances:
On 8 July 2005, the pilot of a Piper PA-31-350 Navajo Chieftain, registered VH-OAO, submitted a visual flight rules (VFR) flight plan for a charter flight from Essendon Airport to Mount Hotham, Victoria. On board the aircraft were the pilot and two passengers. At the time, the weather conditions in the area of Mount Hotham were extreme. While taxiing at Essendon, the pilot requested and was granted an amended airways clearance to Wangaratta, due to the adverse weather conditions at Mount Hotham. The aircraft departed Essendon at 1629 Eastern Standard Time. At 1647 the pilot changed his destination to Mount Hotham. At 1648, the pilot contacted Flightwatch and requested that the operator telephone the Mount Hotham Airport and advise an anticipated arrival time of approximately 1719. The airport manager, who was also an accredited meteorological observer, told the Flightwatch operator that in the existing weather conditions the aircraft would be unable to land. At 1714, the pilot reported to air traffic control that the aircraft was overhead Mount Hotham and requested a change of flight category from VFR to instrument flight rules (IFR) in order to conduct a Runway 29 Area Navigation, Global Navigation Satellite System (RWY 29 RNAV GNSS) approach via the initial approach fix HOTEA. At 1725 the pilot broadcast on the Mount Hotham Mandatory Broadcast Zone frequency that the aircraft was on final approach for RWY 29 and requested that the runway lights be switched on. No further transmissions were received from the aircraft. The wreckage of the aircraft was located by helicopter at 1030 on 11 July. The aircraft had flown into trees in a level attitude, slightly banked to the right. Initial impact with the ridge was at about 200 ft below the elevation of the Mount Hotham aerodrome. The aircraft had broken into several large sections and an intense fire had consumed most of the cabin. The occupants were fatally injured.
Probable cause:
Findings:
• There were no indications prior to, or during the flight, of problems with any aircraft systems that may have contributed to the circumstances of the occurrence.
• The pilot continued flight into forecast and known icing conditions in an aircraft not approved for flight in icing conditions.
• The global navigation satellite constellation was operating normally.
• The pilot did not comply with the requirements of the published instrument approach procedure.
• The pilot was known, by his Chief Pilot and others, to adopt non-standard approach procedures to establish his aircraft clear of cloud when adverse weather conditions existed at Mount Hotham.
• The pilot may have been experiencing self-imposed and external pressures to attempt a landing at Mount Hotham.
• Terrain features would have been difficult to identify due to a heavy layer of snow, poor visibility, low cloud, continuing heavy snowfall, drizzle, sleet and approaching end of daylight.
• The pilot’s attitude, operational and compliance practices had been of concern to some Airservices’ staff.
• The operator’s operational and compliance history was recorded by CASA as being of concern, and as a result CASA staff continued to monitor the operator. However, formal surveillance of the operator in the preceding two years had not identified any significant operational issues.
Significant factors:
• The weather conditions at the time of the occurrence were extreme.
• The extreme weather conditions were conducive to visual illusions associated with a flat light phenomenon.
• The pilot did not comply with the requirements of flight under either the instrument flight rules (IFR) or the visual flight rules (VFR).
• The pilot did not comply with the requirements of the published instrument approach procedure and flew the aircraft at an altitude that did not ensure terrain clearance.
• The aircraft accident was consistent with controlled flight into terrain.
Final Report:

Crash of a Cessna 208 Caravan I in Matemo Island

Date & Time: Jun 28, 2005 at 1745 LT
Type of aircraft:
Operator:
Registration:
N9324F
Survivors:
Yes
Schedule:
Pemba - Matemo Island
MSN:
208-0013
YOM:
1985
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Matemo Island Airport, the single engine aircraft impacted the ground short of runway threshold. The aircraft lost its undercarriage then came to rest upside down, bursting into flames. All 11 occupants escaped with minor injuries while the aircraft was destroyed by fire.

Crash of a Havilland DHC-3 Turbo Otter in Yellowknife

Date & Time: Jun 24, 2005 at 1912 LT
Type of aircraft:
Operator:
Registration:
C-FXUY
Flight Phase:
Survivors:
Yes
Schedule:
Yellowknife - Blachford Lake
MSN:
142
YOM:
1956
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The Air Tindi Ltd. de Havilland DHC-3T (Turbo) Otter (registration C-FXUY, serial number 142) water taxied from the Air Tindi dock at Yellowknife, Northwest Territories, for a charter flight to Blachford Lake. The aircraft was loaded with two crew members, seven passengers, and 840 pounds of cargo. Before the flight, the pilot conducted a preflight passenger briefing, which included information about the location of life preservers and emergency exits. During the take-off run, at about 1912 mountain daylight time, the aircraft performed normally. It became airborne at about 55 mph, which is lower than the normal take-off speed of 60 mph. The pilot applied forward control column to counter the pitch-up tendency, but there was no response. He then trimmed the nose forward, but the aircraft continued to pitch up until it stalled at about 50 feet above the water and the left wing dropped. The aircraft struck the water in the East Bay in a nose-down, 45/ left bank attitude. On impact, the left wing and left float detached from the aircraft, and the aircraft came to rest on its left side. The crew was able to evacuate the passengers before the aircraft submerged, and local boaters assisted in the rescue. There were no serious injuries to the crew or passengers. The aircraft suffered substantial damage.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft was loaded in such a manner that the C of G was beyond the rearward limit. This resulted in the aircraft’s aerodynamic pitch control limitation being exceeded.
2. A weight and balance report was not completed by the pilot prior to departure and, as a consequence, he was unaware of the severity of the aft C of G position.
Finding as to Risk:
1. The weight of the passengers was underestimated due to the use of standard weights. This increased the potential of inadvertently loading the aircraft in excess of its maximum certified take-off weight.
Final Report: