Crash of a PZL-Mielec AN-28 in Benzdorp: 19 killed

Date & Time: Apr 3, 2008 at 1100 LT
Type of aircraft:
Operator:
Registration:
PZ-TSO
Survivors:
No
Site:
Schedule:
Paramaribo – Lawa
MSN:
1AJ007-17
YOM:
1990
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
While approaching Lawa-Antino airport, the crew was informed that another airplane was on the runway at that time. The crew initiated a go-around procedure when the aircraft hit a wooded hillside and crashed, bursting into flames. All 19 occupants were killed.

Crash of a Beechcraft 1900D in Bushi: 3 killed

Date & Time: Mar 15, 2008 at 0920 LT
Type of aircraft:
Operator:
Registration:
5N-JAH
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Lagos - Bebi
MSN:
UE-322
YOM:
1998
Flight number:
TWD8300
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
9730
Captain / Total hours on type:
852.00
Copilot / Total flying hours:
444
Copilot / Total hours on type:
204
Aircraft flight hours:
5578
Circumstances:
The aircraft, Beech 1900D with flight number TWD8300 on a positioning flight, filed an Instrument Flight Rule (IFR) with Air Traffic Services (ATS) at Murtala Muhammed Airport (MMA) Lagos for departure to Bebi airstrip, Obudu on a filed flight plan LAG – UA609 – POTGO – DCT – ENU – DCT - OBUDU. But the actual route flown was LAG – UA609 – POTGO – LIPAR – LUNDO – IKROP – BUDU. The aircraft departed MMA at 0736 hrs as per the flight plan, climbed to FL250, estimated MOPAD at 0755 hrs, BEN at 0814hrs, POTGO at 0837hrs, LIPAR at 0844hrs, LUNDO at 0902 hrs and OBUDU destination at 0917hrs. The aircraft was transferred to Port Harcourt at 0845 hrs thereafter the crew requested descent. It was cleared to FL110 but on passing through FL160 requested further descent and was then released to Enugu at 0856 hrs by Port Harcourt. Enugu cleared it to FL050. The aircraft deviated from the flight plan route, and flew on airway UA609 direct to IKROP from POTGO. The inputs into Global Positioning System (GPS) gave the crew different distances to Bebi. The crew agreed on a coordinate to input and thereafter were busy trying to locate the airstrip physically. During this process the Ground Proximity Warning System (GPWS), warning signals and sound of “Terrain, terrain…..pull up” was heard several times without any of the pilot following the command. The aircraft flew into terrain, crashed and was destroyed. At 0923hrs, the Radio Operator at Bebi called the aircraft to confirm its position, but received no reply. The FDR showed that the aircraft crashed at about 0920:15 hrs at an altitude of about 3,400ft at Bushi Village during the hours of daylight with three fatalities. The aircraft flew for 103.75 minutes before impact.At 0924 hrs, Bebi Radio Operator called Calabar, to confirm if in contact with 5N-JAH, Calabar replied negative contact. The burnt wreckage was found by hunters in a dense wooded area on 30 August 2008.
Probable cause:
The flight crew conducted an approach into a VFR airfield in an instrument meteorological condition and did not maintain terrain clearance and minimum safe altitude which led to Controlled Flight Into Terrain. The crew did not respond promptly to GPWS warning.
Contributory Factors:
- The flight crew was not familiar with the route in a situation of low clouds, poor visibility and mountainous terrain.
- The Area Controllers did not detect the estimate as passed by the pilot for positions not in the filed flight plan (LIPAR and LUNDO) and omitting ENUGU.
- The flight crew changed from IFR flight to VFR flight without proper procedure and ATC clearance.
- The crew did not use Jeppesen charts as approved in WINGS AVIATION Operational Specifications by NCAA.
- The Lagos Area Control Center (ACC) did not detect or question the disparity in waypoints and routing as read back by the crew, compared with the filed flight plan.
Final Report:

Crash of an ATR42-300 in Mérida: 46 killed

Date & Time: Feb 21, 2008 at 1700 LT
Type of aircraft:
Operator:
Registration:
YV1449
Flight Phase:
Survivors:
No
Site:
Schedule:
Mérida – Caracas
MSN:
28
YOM:
1986
Flight number:
BBR518
Location:
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
46
Circumstances:
After takeoff from Mérida-Alberto Carnevalli Airport runway 25, the aircraft climbed in clouds when it collided with a mountain located 10 km northwest of the airport. The aircraft disintegrated on impact and all 46 occupants were killed. The wreckage was found at an altitude of 4,100 metres.
Probable cause:
After departure from runway 25, the crew planned to use an unpublished procedure. Climbing through clouds a 180-degree turn was initiated. Using the unreliable magnetic compass, the flight made a 270 degree turn, heading towards rising terrain. The captain took over control from the copilot. When visual contact with terrain was regained, the crew noted they were heading for mountains. The captain tried to avoid rising terrain but the aircraft impacted the side of a mountain at 4,100 metres.

Crash of a Cessna 340A near Cabazon: 4 killed

Date & Time: Feb 2, 2008 at 1340 LT
Type of aircraft:
Registration:
N354TJ
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Palm Springs – Chino
MSN:
340A-0042
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
5972
Circumstances:
The airplane departed under daytime visual meteorological conditions on a cross-country flight from an airport on the east side of a mountain range to a destination on the west side of the mountains. The airplane, which had been receiving flight following, then collided with upsloping mountainous terrain in a mountain pass while in controlled flight after encountering instrument meteorological conditions. The controller terminated radar services due to anticipation of losing radar coverage within the mountainous pass area, and notified the pilot to contact the next sector once through the pass while staying northwest of an interstate highway due to opposing traffic on the south side of the highway. The pilot later contacted the controller asking if he still needed to remain on a northwesterly heading. The controller replied that he never assigned a northwesterly heading. No further radio communications were received from the accident airplane. Radar data revealed that while proceeding on a northeasterly course, the airplane climbed to an altitude of 6,400 feet mean sea level (msl). A few minutes later, the radar data showed the airplane turning to an easterly heading and initiating a climb to an altitude of 6,900 feet msl. The airplane then started descending in a right turn from 6,900 feet to 5,800 feet msl prior to it being lost from radar contact about 0.65 miles southeast of the accident site. A weather observation station located at the departure airport reported a scattered cloud layer at 10,000 feet above ground level (agl). A weather observation system located about 29 miles southwest of the accident site reported a broken cloud layer at 4,000 feet agl. A pilot, who was flying west bound at 8,500 feet through the same pass around the time of the accident, reported overcast cloud coverage in the area of the accident site that extended west of the mountains. The pilot stated that the ceiling was around 4,000 feet msl and the tops of the clouds were 7,000 feet msl or higher throughout the area. Postaccident examination of the airframe and both engines revealed no anomalies that would have precluded normal operation.
Probable cause:
The pilot's continued visual flight into instrument meteorological conditions and failure to maintain terrain clearance while en route. Contributing to the accident were clouds and mountainous terrain.
Final Report:

Crash of a Beechcraft B200 Super King Air near Huambo: 13 killed

Date & Time: Jan 19, 2008 at 0832 LT
Registration:
D2-FFK
Flight Phase:
Survivors:
No
Site:
Schedule:
Luanda – Huambo
MSN:
BB-1026
YOM:
1982
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
13
Circumstances:
The twin engine aircraft departed Luanda-4 de Fevereiro Airport shortly prior to 0700LT on an exec flight to Huambo, carrying 11 passengers and two pilots, among them two Portuguese citizens and the CEO of the operator. While descending to Huambo Airport in poor weather conditions (limited visibility due to rain and fog), the aircraft collided with Mt Mbave (2,021 metres high) located about 40 km north of Huambo Airport. All 13 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew descended too low during an approach in IMC conditions.

Crash of a PZL-Mielec AN-2R near Trbovlje: 1 killed

Date & Time: Jan 11, 2008
Type of aircraft:
Registration:
HA-MKK
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Šentvid pri Stični – Maribor
MSN:
1G178-53
YOM:
1978
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew departed Šentvid pri Stični on a flight to Maribor as the aircraft should be transferred to Hungary for maintenance purposes. While cruising in poor visibility due to fog, the aircraft struck the slope of a mountain located near Trbovlje. A pilot was seriously injured while the second one was killed. The aircraft was destroyed.
Probable cause:
Controlled flight into terrain.

Crash of a McDonnell Douglas MD-83 in Isparta: 57 killed

Date & Time: Nov 30, 2007 at 0136 LT
Type of aircraft:
Operator:
Registration:
TC-AKM
Survivors:
No
Site:
Schedule:
Istanbul - Isparta
MSN:
53185/2090
YOM:
1994
Flight number:
KK4203
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
57
Circumstances:
The aircraft departed Istanbul-Atatürk Airport at 0051LT on a schedule service to Isparta, carrying 50 passengers and 7 crew members. After being cleared to proceed to a VOR/DME approach to Isparta Airport runway 05, the crew was supposed to fly over IPT VOR then to follow a 223° heading. But the crew failed to input the arrival procedures in the FMS and started the approach by night over rising terrain. As the EGPWS failed to activate, the crew did not realize his altitude was insufficient when the aircraft collided with trees and crashed in a mountainous area located near Çukurören, about 12 km west of Isparta Airport. The aircraft was destroyed and all 57 occupants were killed.
Probable cause:
The following findings were identified:
- The crew failed to follow the published procedures,
- The crew failed to adhere to SOP's,
- The EGPWS system failed to activate and to warn the crew about the insufficient altitude,
- The EGPWS failed 86 times during the last 235 flights and was removed from another aircraft to be installed on TC-AKM 10 days prior to the accident,
- Lack of visibility due to the night,
- The CVR system was unserviceable,
- The DFDR system was partially unserviceable and recorded the last 15 minutes of flight only,
- Lack of crew training,
- The captain followed only 20 of the requested 32 hours training,
- The copilot followed a 32-hours training program in Sofia but this was not documented,
- A probable lack of situational awareness on part of the crew.

Crash of a Cessna 404 Titan near Nakatsugawa: 2 killed

Date & Time: Nov 15, 2007 at 1036 LT
Type of aircraft:
Operator:
Registration:
JA5257
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Nagoya - Nagoya
MSN:
404-0041
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
16512
Captain / Total hours on type:
837.00
Aircraft flight hours:
5671
Circumstances:
The twin engine aircraft departed Nagoya Airport at 0846LT on an aerial photography mission over the Mt Ena and Gifu district. Several circuits were completed over the area of Mt Ena at various altitudes and in good weather conditions. Approaching Mt Ena at an altitude of about 2,000 metres, weather conditions worsened as the mountain was shrouded in clouds. While flying under VFR mode, the aircraft entered clouds, collided with a tree and crashed in a wooded area. The copilot (a mechanic) was seriously injured while both other occupants were killed. The aircraft was destroyed.
Probable cause:
Controlled flight into terrain after the pilot decided to continue under VFR mode in IMC conditions.
Final Report:

Crash of a Fletcher FU-24-950EX in Opotiki: 1 killed

Date & Time: Nov 10, 2007 at 1320 LT
Type of aircraft:
Operator:
Registration:
ZK-EGV
Flight Phase:
Survivors:
No
Site:
MSN:
244
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5243
Captain / Total hours on type:
4889.00
Circumstances:
On the afternoon of Friday 9 November 2007, the pilot of ZK-EGV, a specialised agricultural aeroplane powered by a turbine engine, began a task to sow 80 tonnes of superphosphate over a farm situated in low hills 5 km south of Opotiki township and 4 km from the Opotiki aerodrome. The pilot was familiar with the farm’s airstrip where he loaded the product, and with the farm. After 6 or 7 loads, the wind was too strong for top-dressing, so the pilot and loader-driver flew back to their base at the Whakatane aerodrome, about 40 km away. At Whakatane, the aeroplane’s fuel tanks were filled. Later that day, the pilot replaced the display for the aeroplane’s precision sowing guidance system, which had a software fault. The next morning, 10 November 2007, the pilot bicycled about 6 km from his house to the Whakatane aerodrome. The loader-driver said that the pilot looked “pretty tired” from the effort when he arrived at the aerodrome at about 0545. After the aeroplane had been started using its internal batteries, the pilot and loader-driver flew to complete a task at a farm west of Whakatane. The pilot’s notebook recorded that he began the task at 0610 and took 45 loads to spread the remaining 68 tonnes of product, an average load of 1511 kilograms (kg). The loader-driver said that the pilot had determined about 2 months earlier that the scales on the loader used at that airstrip were “weighing light” by about 200 kg, so the loader-driver allowed for that difference. After that task, the pilot and loader-driver flew back to the farm south of Opotiki where they had been the previous afternoon. A different loader at that airstrip had accurate scales, and the loader-driver said that he loaded 1500 kg each time, as requested by the pilot. The fertiliser that remained in the farm airstrip storage bin after the accident was found to be dry and free flowing. The sowing task at this farm began at 1010 and the pilot stopped after every hour to uplift 180 litres (L) of fuel, which weighed 144 kg. During the last refuel stop, between 1226 and 1245, he had a snack and a drink. Sowing recommenced at 1245 with about 3 minutes between each load, the last load being put on at about 1316. The loader-driver said the wind at the airstrip was light and the pilot did not report any problem with the aeroplane. After the last refuel, the top-dressing had been mostly out of sight of the loader-driver. When the aeroplane did not return when expected for the next load, the loader driver tried 3 or 4 times to call the cellphone installed in the aeroplane. This was unsuccessful, so at 1338 he followed the operator’s emergency procedure and called 111 to report that the aeroplane was overdue. Telephone records showed that on 10 November 2007 the aeroplane cellphone had been connected for a total of more than 90 minutes on 14 voice calls, and had been used to send or receive 10 text messages. Correlation of the call times with the job details recorded by the pilot suggested he sent most of his messages while the aeroplane was on the ground. Nearly all of the calls and messages involved a female work colleague who was a friend. The pilot initiated most calls by sending a message, but each time that the signal was lost during a call, the friend would stop the call and immediately re-dial the aeroplane phone; so, in some cases, consecutive connections were parts of one long conversation. The longest session exceeded 35 minutes. The nature of the calls could not be determined, but the friend claimed the content of the last phone call was not acrimonious or likely to have agitated the pilot. The friend advised that the pilot had said he often made the phone calls to help himself stay alert. At 1153, in a phone call to his home, the pilot indicated that the job was going well and he might be home by about 1400. In one call to the friend, the pilot said that he was a bit tired and that he hoped the wind would increase enough that afternoon to force him to cancel the next job. At 1308:45, the friend called the aeroplane phone and talked with the pilot until the call was disconnected at 1320:14. The friend said that while the pilot had been talking, the volume of his voice decreased slightly then there was a “static” sound. Apart from the reduced volume, the pilot’s voice had sounded normal and he had not suggested anything untoward regarding the job or the aeroplane. The friend immediately called back, but got the answerphone message from the aeroplane phone. Two further attempts to contact the pilot were unsuccessful, but the friend did not consider that anything untoward might have happened. An orchardist who was working approximately 3 km from the farm being top-dressed had heard an aeroplane flying nearby for some hours before he heard a loud sound that led him to fear that there had been an accident. He noted that the time was 1320 and immediately began to search the surrounding area. After the loader-driver’s emergency call, the Police organised an aerial search, which found the wreckage of the aeroplane at 1435 on the edge of a grove of native trees, approximately 600 metres (m) northwest of the area being top-dressed. The pilot had been killed. His body was not removed until 26 hours after the accident, because of a Police concern not to disturb the wreckage until aviation accident investigators were present. The CAA began an investigation that day into the accident and the Commission sent an investigator to help determine whether there were any similarities with another Fletcher accident that the Commission was then investigating. On 19 November 2007, because of potential issues that concerned regulatory oversight, the Commission started its own inquiry.
Probable cause:
Findings are listed in order of development and not in order of priority.
- The reason for the aeroplane colliding with trees was not conclusively determined. However, the pilot was affected by a number of fatigue-inducing factors, none of which should have been significant on its own. The combination of these factors and the added distractions of a prolonged cell phone call and a minor equipment failure were considered likely to have diverted the pilot’s attention from his primary task of monitoring the aeroplane’s flight path.
- Although pilot incapacitation could not be ruled out entirely, it was considered that the pilot’s state of health had not directly contributed to the accident.
- The potential distraction of cellphones during critical phases of flight under VFR was not specifically addressed by CARs.
- Apart from the probable failure of the GPS sowing guidance equipment, no evidence was found to suggest that the aeroplane was unserviceable at the time of the accident, but its airworthiness certificate was invalid because there was no record that the mandatory post-flight checks of the vertical tail fin had been completed in the previous 3 days.
- The installation of a powerful turbine engine without an effective means of de-rating the power created the potential for excessive power demands and possible structural overload, but this was not considered to have contributed to the accident.
- The pilot was an experienced agricultural pilot in current practice. Although he had met the operator’s continued competency requirements, the operator’s method of conducting his last 2 competency checks was likely to have made them invalid in terms of the CAR requirements.
- Although the aeroplane was grossly overloaded and the hopper load exceeded the structural limit on the take-off prior to the accident, neither exceedance contributed to the accident, and the aeroplane was not overloaded at the time of the accident.
- The emergency locator transmitter did not radiate a useful signal because of damage to the antenna socket on the unit. The installation was also not in accordance with the manufacturer’s instructions or the recommended practice.
Final Report:

Crash of a Piper PA-46-310P Malibu near Invermere: 3 killed

Date & Time: Oct 26, 2007 at 1912 LT
Registration:
C-GTCS
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Salem – Calgary
MSN:
46-08065
YOM:
1987
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The privately operated Piper Malibu PA-46-310P was en route from Salem, Oregon, to Springbank, Alberta, on an instrument flight rules flight plan. During the descent through 17 000 feet at approximately 55 nautical miles (nm) southwest of Calgary, the pilot declared an emergency with the Edmonton Area Control Centre, indicating that the engine had failed. The pilot attempted an emergency landing at the Fairmont Hot Springs airport in British Columbia, but crashed at night at about 1912 mountain daylight time 11 nm east of Invermere, British Columbia, in wooded terrain. The pilot and two passengers were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. An unapproved part was installed in the alternator coupling. This resulted in debris from the coupling causing a partial blockage of oil flow to the number two connecting rod bearing. This low oil flow caused overheating and failure of the bearings, connecting rod cap bolts and nuts, and the subsequent engine failure.
2. The engine failure occurred after sunset and the low-lighting conditions in the valley would have made selecting a suitable landing area difficult.
3. The engine knocking was not reported to maintenance personnel which prevented an opportunity to discover the deteriorating engine condition.
Finding as to Risk:
1. All flights on the day of the accident were carried out without the oil filler cap in place. The absence of the oil filler cap could have resulted in the loss of engine oil.
Other Findings:
1. There were no current instrument flight rules charts or approach plates on board the aircraft for the intended flight.
2. The Teledyne Continental Motors Service Bulletin M84-5 addressed only the 520 series engines and did not include other gear-driven alternator equipped engines.
Final Report: