Crash of a Convair CV-340-70 in Miami

Date & Time: Dec 4, 2004 at 0851 LT
Type of aircraft:
Operator:
Registration:
N41626
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Miami – Nassau
MSN:
274
YOM:
1955
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3100
Captain / Total hours on type:
2400.00
Copilot / Total flying hours:
9169
Copilot / Total hours on type:
964
Aircraft flight hours:
18465
Circumstances:
The pilot stated that when the airplane was 3 miles east of the shoreline, at 3,000 feet, he felt a short tremor in the left engine followed by loss of power from the left engine. The pilot elected to return to the departure airport while declaring an emergency to air traffic control. During the process of securing the left engine the pilot noticed the propeller did not feathered and the airplane was descending quickly. He maneuvered the airplane and ditched in a lake. On September 26, 2003 engine s/n: 34592 was removed from the accident airplane due to high oil consumption with 1,225 hours of time in service. It was reportedly preserved and stored at the operator's warehouse. The mechanic who reportedly preserved the engine stated he followed the steps in the manual that was provided by the operator. On October 27, 2004 the left engine, s/n: NK510332, which was producing metal for months, was removed and engine s/n: 34592 was taken out of preservation and installed in the left position on the accident airplane with a new overhauled propeller assembly. On November 06, 2004, the left engine's, s/n: 34592, propeller governor was replaced due to the left propeller slow to response to power setting. During the post accident engine examination, the engine's main oil screen was observed with deposits of metal flakes and fragments, the oil scavenge pump would not rotate and had deposits of metal fragments internally; the engine was seized and wound not rotate. Catastrophic damage was observed to the accessories drive gears, oil transfer tube, and protection covers in the front accessory area. It was observed during a visual inspection of the crankshaft and bearings, including the front journal and front crankpin had damaged and sections of their respective bearings missing. The master rod bearing had incurred a catastrophic failure. Several cylinders skirts were found with impact marks from piston rods. Before removing the propeller assembly from the engine, the propeller feather system was flush with fresh oil and pressured with a feathering pump; the propeller blades were observed moving toward the feather position. Examination of the propeller assembly revealed metal contamination throughout the system; the propeller's governor screen gasket was clogged with metal contamination. The maintenance manual provided by the operator used for the engine preservation details several tasks required to be accomplished to the engine for proper engine preservation (i.e. thrust bear, cylinder, and propeller shaft treatments), which the mechanic did not mention he performed. No documentation for inspection and condition status of the dehydrator plugs were available. Documentation for flushing of contamination from the metal producing engine, s/n NK510332, was not available nor knowledge by the operator if since a process was preformed to the left engine's oil tank and its system before installation of engine s/n: 34592. An FAA review of the cargo manifest discovered two different manifest weights. The cargo manifest obtained at the accident scene showed a total of 267 pieces of cargo annotated at a total weight of 10, 837 lbs. The sealed cargo manifest package showed a total of 267 pieces of cargo annotated at a total weight of 14,182 lbs. The maximum payload weight for the accident airplane is 13,586 lbs.
Probable cause:
The improper maintenance of the left engine by company maintenance personnel (failure to flush metal from the oil system and failure to properly preserve the engine for storage) resulting in a total failure of the master rod bearing and contamination of the engine oil system with metal, which prevented the left propeller from feathering. This resulted in the airplane being unable to maintain altitude following loss of engine power and subsequent ditching in a lake. A factor in this accident is the aircraft operator and flight crew exceeding the maximum allowable takeoff weight for the airplane.
Final Report:

Crash of a Boeing 747-200 in Sharjah

Date & Time: Nov 7, 2004 at 1635 LT
Type of aircraft:
Operator:
Registration:
TF-ARR
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hong Kong – Sharjah – Frankfurt
MSN:
23621
YOM:
1986
Flight number:
DLH8457
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
21430
Captain / Total hours on type:
430.00
Copilot / Total flying hours:
4230
Copilot / Total hours on type:
1547
Aircraft flight hours:
79733
Aircraft flight cycles:
13833
Circumstances:
The aircraft and crew were assigned to operate a cargo flight, DLH8457, from Sharjah, U.A.E. to Frankfurt, Germany. The crew did not notice anything unusual with the aircraft apart from a few known defects verbally reported by the crew that operated the previous sector from Bangkok. The aircraft was then prepared for the flight to Frankfurt and the crew completed pre-departure checks including an external inspection of the aircraft. After push back and engines start-up, at 1623:24 hr the crew was cleared by ATC to taxi the aircraft to runway 30. From the performance and speed reference cards the crew ascertained the decision speeds for a reduced engine thrust 10º flap takeoff as follows; V1 – 162 KIAS, Vr – 174 KIAS and V2 – 180 KIAS. The crew line-up the aircraft for a full length take-off and was cleared for take-off at 1631:42 hr. A surface wind check of 340º/08 kt was passed by the tower controller. The take-off roll commenced at 1633:32 hr. During the roll, the FO made the 80 KIAS call at 1633:57 hr followed by the V1 call 26 seconds later. At the same time of the V1 call, the tower controller transmitted to the crew “and Lufthansa there was a bang and you’ve got smoke coming on the right hand side”. The commander then aborted the take-off at 1634:26 hrs whilst maintaining the aircraft on the runway centreline. The speed of the aircraft when aborting actions were first initiated by the crew was 165 KIAS. The crew indicated that the power levers were brought to idle, full reverse thrust selected, speed brakes deployed and manual application of brakes were made. The aircraft acceleration however, continued to 171 KIAS before decelerating normally but was not able to come to a halt within the accelerate stop distance available. Just prior to reaching the end of the runway, the commander turned the aircraft to the left to avoid the elevated approach lights at the end of the runway and it came to a stop in an open sand area approximately 30 metres from the prepared surface of the runway in a nose low attitude. The commander then ordered an evacuation and the crew exited through the right upper deck door using ladders provided by personnel from the airport RFF services.
Probable cause:
The cause of this accident was the termination of the take-off at a speed above V1 with insufficient runway remaining to stop the aircraft safely as a result of the commander’s interpretation that there was smoke and ‘fire’.
Contributory Causes:
a) The failure of the No 9 wheel rim during the take-off roll which caused the bang and smoke.
b) The probable use of watermist as a medium to cool hot brakes which may have subject the wheel rims to fail under normal operating loads.
c) The continued usage of the inboard wheel half that should have been retired during year 2000.
Final Report:

Crash of a Boeing 707-330C in Manaus

Date & Time: Oct 23, 2004 at 0840 LT
Type of aircraft:
Operator:
Registration:
PP-BSE
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manaus – São Paulo
MSN:
19317
YOM:
1967
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9487
Captain / Total hours on type:
6600.00
Copilot / Total flying hours:
14180
Copilot / Total hours on type:
3180
Aircraft flight hours:
95933
Circumstances:
Ready for takeoff on runway 10 at Manaus-Eduardo Gomes Airport, the crew released brakes and increased engine power when a loud noise was heard coming from the right side of the aircraft. The captain decided to reject takeoff and applied brakes when the aircraft started to deviate to the right. It veered off runway and came to rest. All three crew members escaped uninjured while the aircraft was considered as damaged beyond repair after the right main gear punctured the wing.
Probable cause:
The right main gear collapsed during takeoff following a structural failure caused by the presence of fatigue cracks that were not detected by the maintenance crew because of poor maintenance. The aircraft already suffered an accident in Guarulhos Airport, causing damages to the right main gear.
Final Report:

Crash of a Cessna F406 Caravan II near Inverness: 1 killed

Date & Time: Oct 22, 2004 at 1133 LT
Type of aircraft:
Operator:
Registration:
G-TWIG
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Stornoway – Inverness
MSN:
406-0014
YOM:
1987
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2735
Captain / Total hours on type:
510.00
Circumstances:
The aircraft and its commander were concluding the fifth sector of the day when, shortly after starting a descent for Inverness, the aircraft’s rate of descent became unsteady and it started to turn left. The available evidence indicated that the aircraft struck the ground in a steep, left, spiral dive. The extreme fragmentation of the wreckage suggested a high impact speed, probably in the region of 350 kt. Major airframe and powerplant failures were discounted but otherwise, there was insufficient evidence to draw firm conclusions about the reasons for the sudden deviation from controlled flight and secondly, the absence of any evidence consistent with an attempt to recover from the dive. Two safety recommendations made recently to the EASA concerning flight recorders were re-iterated.
Probable cause:
During a gentle descent from FL95 to FL75 in instrument meteorological conditions G-TWIG rapidly entered a dramatic and sustained manoeuvre from what initially appeared to be controlled flight at normal descent speed. Despite a determined and thorough investigation, because there was insufficient evidence from which to draw a firm conclusion, the cause or causal factors for this rapid deviation from controlled flight could not be identified.
Final Report:

Crash of a Britten-Norman BN-2A-21 Islander near Coron: 2 killed

Date & Time: Oct 16, 2004 at 1530 LT
Type of aircraft:
Operator:
Registration:
RP-C1325
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Coron - Manila
MSN:
593
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The twin engine aircraft departed Coron-Francisco B. Reyes Airport on a cargo flight to Manila, carrying two pilots and a load consisting of 700 kilos of fish. While climbing in poor weather conditions, the aircraft struck the slope of Mt Tagbao located 9 km from the airport. The wreckage was found a day later and both pilots were killed.
Probable cause:
Controlled flight into terrain after the crew apparently suffered a spatial disorientation while climbing in limited visibility due to low ceiling and heavy rain falls.

Crash of a Douglas DC-3C in Medellín: 3 killed

Date & Time: Oct 15, 2004 at 0750 LT
Type of aircraft:
Operator:
Registration:
HK-1503
Flight Type:
Survivors:
No
Site:
Schedule:
Villavicencio - Medellín
MSN:
17064/34331
YOM:
1945
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
21490
Captain / Total hours on type:
370.00
Copilot / Total flying hours:
305
Copilot / Total hours on type:
91
Aircraft flight hours:
27592
Circumstances:
The aircraft departed Villavicencio on a cargo flight to Medellin-José María Córdova Airport with one passenger and two pilots on board. While descending to Medellín, the crew was informed about the poor weather conditions at destination (poor visibility due to fog) and decided to divert to Medellín-Enrique Olaya Herrera Airport. On final approach, the aircraft descended too low when it struck a mountain located 13 km short of runway. The aircraft was destroyed and all three occupants were killed.
Probable cause:
Controlled flight into terrain after the crew took the decision to continue the approach under VFR mode in IMC conditions until the aircraft impacted terrain. Poor CRM and lack of situational awareness were considered as contributing factors.
Final Report:

Crash of a Boeing 747-244BSF in Halifax: 7 killed

Date & Time: Oct 14, 2004 at 0356 LT
Type of aircraft:
Operator:
Registration:
9G-MKJ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Windsor Locks - Halifax - Zaragoza
MSN:
22170
YOM:
1980
Flight number:
MKA1602
Country:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
23200
Copilot / Total flying hours:
8537
Aircraft flight hours:
80619
Aircraft flight cycles:
16368
Circumstances:
MKA1602 landed on Runway 24 at Halifax International Airport at 0512 and taxied to the ramp. After shutdown, loading of the aircraft was started. During the loading, two MK Airlines Limited crew members were observed sleeping in the upper deck passenger seats. After the fuelling was complete, the ground engineer checked the aircraft fuelling panel and signed the fuel ticket. The aircraft had been uploaded with 72 062 kg of fuel, for a total fuel load of 89 400 kg. The ground engineer then went to the main cargo deck to assist with the loading. Once the loading was complete, the ramp supervisor for the ground handling agent went to the upper deck to retrieve the MKA1602 cargo and flight documentation. While the loadmaster was completing the documentation, the ramp supervisor visited the cockpit and noted that the first officer was not in his seat. Approximately 10 minutes later, the ramp supervisor, with the documentation, left the aircraft. At 0647, the crew began taxiing the aircraft to position on Runway 24, and at 0653, the aircraft began its take-off roll. See Section 1.11.4 of this report for a detailed sequence of events for the take-off. During rotation, the aircraftís lower aft fuselage briefly contacted the runway. A few seconds later, the aircraftís lower aft fuselage contacted the runway again but with more force. The aircraft remained in contact with the runway and the ground to a point 825 feet beyond the end of the runway, where it became airborne and flew a distance of 325 feet. The lower aft fuselage then struck an earthen berm supporting an instrument landing system (ILS) localizer antenna. The aircraft's tail separated on impact, and the rest of the aircraft continued in the air for another 1200 feet before it struck terrain and burst into flames. The final impact was at latitude 44°52'51" N and longitude 063°30'31" W, approximately 2500 feet past the departure end of Runway 24, at an elevation of 403 feet above sea level (asl). The aircraft was destroyed by impact forces and post-crash fire. All persons on board (seven crew members) were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The Bradley take-off weight was likely used to generate the Halifax take-off performance data, which resulted in incorrect V speeds and thrust setting being transcribed to the take-off data card.
2. The incorrect V speeds and thrust setting were too low to enable the aircraft to take off safely for the actual weight of the aircraft.
3. It is likely that the flight crew member who used the Boeing Laptop Tool (BLT) to generate take-off performance data did not recognize that the data were incorrect for the planned take-off weight in Halifax. It is most likely that the crew did not adhere to the operatorís procedures for an independent check of the take-off data card.
4. The pilots of MKA1602 did not carry out the gross error check in accordance with the company's standard operating procedures (SOPs), and the incorrect take-off performance data were not detected.
5. Crew fatigue likely increased the probability of error during calculation of the take-off performance data, and degraded the flight crewís ability to detect this error.
6. Crew fatigue, combined with the dark take-off environment, likely contributed to a loss of situational awareness during the take-off roll. Consequently, the crew did not recognize the inadequate take-off performance until the aircraft was beyond the point where the take-off could be safely conducted or safely abandoned.
7. The aircraftís lower aft fuselage struck a berm supporting a localizer antenna, resulting in the tail separating from the aircraft, rendering the aircraft uncontrollable.
8. The company did not have a formal training and testing program on the BLT, and it is likely that the user of the BLT in this occurrence was not fully conversant with the software.
Findings as to Risk:
1. Information concerning dangerous goods and the number of persons on board was not readily available, which could have jeopardized the safety of the rescue personnel and aircraft occupants.
2. Failure of one of the airport emergency power generators to provide backup power prevented the operation of some automatic functions at the fire hall after the crash alarm was activated, increasing the potential for a delayed response.
3. Grid map coordinates were not used to direct units responding to the crash and some responding units did not have copies of the grid map. The non-use of grid coordinates during an emergency could lead to confusion and increase response times.
4. Communication difficulties encountered by the emergency response agencies complicated coordination and could have hampered a rescue attempt or quick evacuation of an injured person.
5. A faulty aircraft cargo loading system prevented the proper positioning of a roll of steel, resulting in the weight limits of positions LR and MR being exceeded by 4678 kg (50 per cent).
6. The company increase of the maximum flight duty time for a heavy crew from 20 to 24 hours increased the potential for fatigue.
7. Regulatory oversight of MK Airlines Limited by the Ghana Civil Aviation Authority (GCAA) was not adequate to detect serious non-conformances to flight and duty times, nor ongoing non-adherence to company directions and procedures.
8. The delay in passing the new Civil Aviation Act, 2004 hindered the GCAAís ability to exercise effective oversight of MK Airlines Limited.
9. Company planning and execution of very long flight crew duty periods substantially increased the potential for fatigue.
10. The company expansion, flight crew turnover, and the MK Airlines Limited recruitment policy resulted in a shortage of flight crew; consequently, fewer crews were available to meet operational demands, increasing stress and the potential for fatigue.
11. There were no regulations or company rules governing maximum duty periods for loadmasters and ground engineers, resulting in increased potential for fatigue-induced errors.
12. The MK Airlines Limited flight operations quality and flight safety program was in the early stages of development at the time of the accident; consequently, it had limited effectiveness.
13. The berms located at either end of runways 06 and 24 were not evaluated as to whether they were a hazard to aircraft in the runway overrun/undershoot areas.
14. The operating empty weight of the aircraft did not include 1120 kg of personnel and equipment; consequently, it was possible that the maximum allowable aircraft weights could be exceeded unknowingly.
15. The ground handling agent at Halifax International Airport did not have the facilities to weigh built-up pallets that were provided by others. Incorrect load weights could result in adverse aircraft performance.
16. Some MK Airlines Limited flight crew members did not adhere to all company SOPs; company and regulatory oversight did not address this deficiency.
Other Findings:
1. An incorrect slope for Runway 24 was published in error and not detected; the effect of this discrepancy was not a significant factor in the operation of MKA1602 at Halifax.
2. The occurrence aircraft was within the weight and centre of gravity limits for the occurrence flight, although the allowable cargo weights on positions LR and MR were exceeded.
3. Based on engineering simulation, the accident aircraft performance was consistent with that expected for the configuration, weight and conditions for the attempted take-off at Halifax International Airport.
4. There have been several examples of incidents and accidents worldwide where non-adherence to procedures has led to incorrect take-off data being used, and the associated flight crews have not recognized the inadequate take-off performance. 5. No technical fault was found with the aircraft or engines that would have contributed to the accident.
Final Report:

Crash of an Antonov AN-12 near Kaduqli: 4 killed

Date & Time: Oct 5, 2004 at 1237 LT
Type of aircraft:
Operator:
Registration:
ST-SAF
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
El Obeid – Juba
MSN:
00 347 606
YOM:
1970
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
On a cargo flight from El Obeid to Juba, while cruising at an altitude of 17,000 feet, the crew declared an emergency following the failure of all four engine, and elected to divert to Heglig Airport. Shortly later, the aircraft crashed in a wooded area located about 50 km south of Kaduqli. All four occupants were killed.

Crash of a Britten-Norman BN-2A-27 near Vega Baja: 1 killed

Date & Time: Sep 29, 2004 at 1859 LT
Type of aircraft:
Operator:
Registration:
N902GD
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Mayaguez – San Juan
MSN:
905
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On September 29, 2004, about 1859, Atlantic standard time, the accident airplane, N902GD, operating as an "on demand" air taxi flight, transporting bank financial documents, departed
Mayaguez, Puerto Rico, and was later reported as not having arrived at its destination. Search and rescue assets later discovered airplane related debris, specific to the missing airplane, floating in the Atlantic Ocean, in the vicinity of geographic position 18 degrees 29 minutes north latitude, 066 degrees 27 minutes west longitude. The NTSB evaluated radar and weather data, and radar track data for the flight showed that after departure the accident airplane climbed to 1,700 feet, and then descended to 1,300 feet at 1840. From 1840 to 1850, the radar data indicated that the flight was proceeding east along the northern coast of Puerto Rico, at an altitude of 1,100 feet. About 1855, the data showed that the airplane climbed to 1,400 feet, and about 1856, it descended to about 1,000 feet. About 1858, the airplane descended to 800 feet, and then to 600 feet, before disappearing from radar at 18:59:18. Weather data showed that a weak upper air trough, a moist low level southeasterly flow and associated showers and thunderstorms had formed over Puerto Rico during the time of the accident flight. The weather data showed that at departure visual meteorological conditions existed, but doppler weather radar data showed that a 50 dBz (level 5) rain shower was positioned about 3 to 5 miles off the airplane's right wing from 1837 to 1838, and from 1855 to 1901 there was a level 4-5 (45-50 dBZ) rain shower along the accident airplane's track, and the radar track data along with the doppler weather radar data was consistent with the flight having penetrated the rain shower corresponding to the time radar contact with the flight was lost. The NTSB Weather Group Chairman's Report has been included as an attachment to the factual report.
Probable cause:
The pilot's improper inflight planning which resulted in an inflight encounter with weather (low ceilings and thunderstorms), his loss of aircraft control, and an inflight collision with the ocean during uncontrolled descent.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Gwinner

Date & Time: Sep 23, 2004 at 2345 LT
Type of aircraft:
Registration:
N7392B
Flight Type:
Survivors:
Yes
Schedule:
Fergus Falls – Gwinner
MSN:
208B-0045
YOM:
1987
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17420
Captain / Total hours on type:
50.00
Aircraft flight hours:
11945
Circumstances:
The airplane was substantially damaged when it impacted an open field about 1-1/2 miles south of the destination airport. The pilot had executed an instrument approach and was circling to land when the accident occurred. Night instrument meteorological conditions prevailed at the time. The area south and east of the airport was sparsely populated. The pilot reported that he obtained the Automated Weather Observing System (AWOS) broadcast for the destination via the aircraft radio while en route. He stated the reported visibility was above that required for the Non-Directional Beacon (NDB) approach, however, the ceiling was below the minimum descent altitude (MDA). He reported that he attempted to contact air traffic control (ATC) with the intention of diverting. He was not able to contact ATC and elected to continue to the destination. The pilot reported that he flew the entire NDB approach and stated: "When I arrived at the MDA, I saw the runway, directly below and a little to my left. My plan, at the time, was to circle left and land." He stated after that point he had no further recollection of the events surrounding the accident. The pilot reported that there were no failures or malfunctions associated with the aircraft. Two witnesses reported seeing lights from an airplane near the airport. One recalled that the weather was "foggy and a heavy mist." The other witness stated: "When I saw the plane it was very low but I thought it was going around for the landing because it looked like the plane had its right wing higher, and I could see part of the belly of the plane, which made it look like it was banking around." Flight control continuity was confirmed during a post-accident examination. The airport AWOS recorded an overcast sky at 400 feet above ground level (agl). The MDA for the instrument approach as 694 feet above field elevation.
Probable cause:
The pilot's failure to maintain altitude during the circling maneuver. Contributing factors were the pilot's improper decision to execute the approach when weather conditions were below minimums and the low light (dark night) conditions.
Final Report: