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 Cessna 340 in Bangalore

Date & Time: Jul 16, 2005 at 1150 LT
Type of aircraft:
Operator:
Registration:
N888HB
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
340-0101
YOM:
1972
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Bangalore-Jakkur Airport runway 08, while in initial climb, the aircraft suffered an engine failure. It stalled and crashed in shallow water in Jakkur Lake, about one km northeast of the aerodrome. Both pilots were rescued and the aircraft was damaged beyond repair.
Probable cause:
Engine failure for unknown reasons.

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 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:

Crash of a SCAN-30 Super Widgeon off Manerba di Garda

Date & Time: Mar 29, 2005 at 1441 LT
Type of aircraft:
Operator:
Registration:
OE-FWS
Flight Type:
Survivors:
Yes
Schedule:
Salzburg - Lake Garda
MSN:
30
YOM:
1949
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23356
Captain / Total hours on type:
130.00
Aircraft flight hours:
3875
Circumstances:
The twin engine aircraft departed Salzburg Airport at 1242LT on a private flight to the Lake Garda (Lago di Garda). Upon landing off Manerba di Garda, the aircraft went out of control, plunged and sank. Both occupants evacuated safely while the aircraft sank by a depth of about 120 metres.
Probable cause:
It is believed that the loss of control upon landing was the consequence of the combination of a poor management of the factor P on part of the pilot-in-command, and microbursts. However, a technical problem was not ruled out.
Final Report:

Crash of an Ilyushin II-76TD off Mwanza: 8 killed

Date & Time: Mar 23, 2005 at 2305 LT
Type of aircraft:
Operator:
Registration:
ER-IBR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Mwanza – Khartoum – Benghazi – Osijek
MSN:
0043 4546 23
YOM:
1984
Flight number:
RIN982
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
11609
Captain / Total hours on type:
8939.00
Copilot / Total flying hours:
4769
Aircraft flight hours:
2615
Aircraft flight cycles:
1548
Circumstances:
On 23 March 2005 at 0533 hours an Ilyushin IL-76 cargo jet with the Republic of Moldova registration letters ER-IBR landed at Mwanza on a flight from Benghazi, Libya. It was carrying a crew of 8 including 2 ground engineers. All the 8 crew members were later involved in the accident. While at Mwanza, some 50,000 kg of fish was uplifted. At 1930 hours the commander filed a flight plan for Khartoum. The endurance was 0450 hours. The cargo manifest showed that ER-IBR was operating Air Trans Inc. Flight RIN 982 from Mwanza to Osijek, Croatia, with refueling stops at Khartoum and Benghazi. At 2000 hours the aircraft was given information relevant for take off as well as the departure clearance. ER-IBR subsequently advised that he was starting the take-off roll. This was the last communication received from the aircraft. The aircraft was observed to execute a normal take-off roll from runway 30. This runway ends 120m short of Lake Victoria. After observing that the aircraft was airborne, the controller who was handling the flight reported that he turned to complete the flight progress strip. Having done so, he lost visual contact with the aircraft that was supposed to be in a climb profile over the lake. Efforts to raise the aircraft on the radio failed. In about two minutes from the time that the aircraft was airborne, he saw a fire tender speeding along runway 30. It was then that he realized that the flight may have crashed. The Mwanza Airport Rescue and Fire Fighting Services were not equipped for operations in the lake. They were therefore unable to reach the aircraft, which was more than 1 km away from the shore. It was the fishermen at the lake shore near Mwanza airport who saw the aircraft going down in the lake. They proceeded to the crash site in fishing boats and brought back some documents (flight manuals and wiring diagrams) which they found floating near the wreckage.
Probable cause:
The accident was caused by aircraft colliding with the water surface shortly after take off. While the aircraft had gathered sufficient energy to sustain climb, the crew failed to monitor altitude and react correctly in the short time that the aircraft was airborne. This resulted in the aircraft going into descent till it reached an altitude where recovery was not possible. The possibility of crew fatigue as a contributory factor in this accident cannot be ruled out.
Final Report:

Crash of a Boeing 707-3K1C off Entebbe

Date & Time: Mar 19, 2005 at 1053 LT
Type of aircraft:
Registration:
9G-IRL
Flight Type:
Survivors:
Yes
Schedule:
Addis Ababa - Entebbe - Lomé
MSN:
20805
YOM:
1974
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was completing a cargo flight from Addis Ababa to Lomé, Togo, with an intermediate stop in Entebbe, Uganda, carrying five crew members and a load of 32,8 tons of various goods (T-shirts) on behalf of Ethiopian Airlines. On approach to runway 17 in a 8 km visibility, the captain decided to initiate a go-around procedure. Few minutes later, while on a second attempt to land on runway 35, the crew encountered local patches of fog when, on short final, the aircraft crashed in Lake Victoria. The tail was found about 200 metres offshore while the cockpit was found near the shore. All five occupants were injured.
Probable cause:
The crew continued the approach below MDA until the aircraft impacted water and crashed. The crew failed to follow the published procedures and to initiate a second go-around procedure.

Crash of a Britten-Norman BN-2B-26 Islander off Campbeltown: 2 killed

Date & Time: Mar 15, 2005 at 0018 LT
Type of aircraft:
Operator:
Registration:
G-BOMG
Flight Type:
Survivors:
No
Schedule:
Glasgow – Campbeltown
MSN:
2205
YOM:
1989
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3553
Captain / Total hours on type:
205.00
Aircraft flight hours:
6221
Aircraft flight cycles:
40018
Circumstances:
The Glasgow based Islander aircraft was engaged on an air ambulance task for the Scottish Ambulance Service when the accident occurred. The pilot allocated to the flight had not flown for 32 days; he was therefore required to complete a short flight at Glasgow to regain currency before landing to collect a paramedic for the flight to Campbeltown Airport on the Kintyre Peninsula. Poor weather at Campbeltown Airport necessitated an instrument approach. There was neither radar nor Air Traffic Control Service at the airport, so the pilot was receiving a Flight Information Service from a Flight Information Service Officer in accordance with authorised procedures. After arriving overhead Campbeltown Airport, the aircraft flew outbound on the approach procedure for Runway 11 and began a descent. The pilot next transmitted that he had completed the ‘base turn’, indicating that he was inbound to the airport and commencing an approach. Nothing more was seen or heard of the aircraft and further attempts at radio contact were unsuccessful. The emergency services were alerted and an extensive search operation was mounted in an area based on the pilot’s last transmission. The aircraft wreckage was subsequently located on the sea bed 7.7 nm west-north-west of the airport; there were no survivors.
Probable cause:
The investigation identified the following causal factors:
1. The pilot allowed the aircraft to descend below the minimum altitude for the aircraft’s position on the approach procedure, and this descent probably continued unchecked until the aircraft flew into the sea.
2. A combination of fatigue, workload and lack of recent flying practise probably contributed to the pilot’s reduced performance.
3. The pilot may have been subject to an undetermined influence such as disorientation, distraction or a subtle incapacitation, which affected his ability to safely control the aircraft’s flightpath.
Final Report:

Crash of a Cessna 208B Grand Caravan off Belize City

Date & Time: Mar 9, 2005 at 1720 LT
Type of aircraft:
Operator:
Registration:
V3-HFW
Flight Phase:
Survivors:
Yes
Schedule:
Belize City – San Pedro
MSN:
208B-0791
YOM:
1999
Flight number:
9N2110
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Belize City-Sir Barry Bowen Municipal Airport, while in initial climb, the single engine aircraft went out of control and crashed in the sea, coming to rest upside down in shallow water. All 14 occupants were rescued while the aircraft was damaged beyond repair.
Probable cause:
Loss of control during initial climb due to windshear after weather conditions suddenly changed as a thunderstorm was approaching the airport.