Crash of a Canadair RegionalJet CRJ-200LR in Baotou: 55 killed

Date & Time: Nov 21, 2004 at 0820 LT
Operator:
Registration:
B-3072
Flight Phase:
Survivors:
No
Schedule:
Baotou – Shanghai
MSN:
7697
YOM:
2002
Flight number:
CYH5210
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
55
Circumstances:
Shortly after takeoff from runway 13 at Baotou Airport, while in initial climb, the aircraft encountered difficulties to maintain a positive rate of climb. It stalled, collided with a small house and eventually crashed in the icy lake of the Nanhai Park. The wreckage was found about 2 km from the airport and all 53 occupants were killed as well as two people in the house.
Probable cause:
Loss of lift and subsequent stall after takeoff due to an excessive accumulation of ice and frost on wings, tail and fuselage. It was determined that the aircraft remained parked outside, on the ramp, all preceding night by negative temperature and that the crew failed to deice the airplane prior to takeoff.

Crash of an IAI Arava 201 in Swaziland

Date & Time: Nov 20, 2004 at 1800 LT
Type of aircraft:
Registration:
3D-DAC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
070
YOM:
1981
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew just completed a paratroopers mission when weather conditions deteriorated. The crew decided to divert to a remote airstrip located in the southeast part of the country. After weather conditions improved, the crew took off for a back trip to his base. During the takeoff roll, the aircraft failed to get airborne and crashed in a sugar cane field. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair.
Probable cause:
It was reported that the crew elected to takeoff with the control locks still engaged.

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 Beechcraft B60 Duke in Asheville: 4 killed

Date & Time: Oct 27, 2004 at 1050 LT
Type of aircraft:
Operator:
Registration:
N611JC
Flight Phase:
Survivors:
No
Site:
Schedule:
Asheville – Greensboro
MSN:
P-496
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
13400
Aircraft flight hours:
2144
Circumstances:
At about the 3,000-foot marker on the 8,000-foot long runway witnesses saw the airplane at about 100 to 150-feet above the ground with the landing gear retracted when they heard a loud "bang". They said the airplane made no attempt to land on the remaining 5,000 feet of runway after the noise. The airplane continued climbing and seemed to gain a little altitude before passing the end of the runway. At that point the airplane began a right descending turn and was in a 60 to 80 degree right bank, nose low attitude when they lost sight of it. The airplane collided with the ground about 8/10 of a mile from the departure end of runway 34 in a residential area. Examination of the critical left engine found no pre-impact mechanical malfunction. Examination of the right engine found galling on all of the connecting rods. Dirt and particular contaminants were found embedded on all of the bearings, and spalling was observed on all of the cam followers. The oil suction screen was found clean, The oil filter was found contaminated with ferrous and non-ferrous small particles. The number 3 cylinder connecting rod yoke was broken on one side of the rod cap and separated into two pieces. Heavy secondary damage was noted with no signs of heat distress. Examination of the engine logbooks revealed that both engine's had been overhauled in 1986. In 1992, the airplane was registered in the Dominican Republic and the last maintenance entry indicated that the left and right engines underwent an inspection 754.3 hours since major overhaul. There were no other maintenance entries in the logbooks until the airplane was sold and moved to the United States in 2002. All three blades of the right propeller were found in the low pitch position, confirming that the pilot did not feather the right propeller as outlined in the pilot's operating handbook, under emergency procedures following a loss of engine power during takeoff.
Probable cause:
The pilot's failure to follow emergency procedures and to maintain airspeed following a loss of engine power during takeoff, which resulted in an inadvertent stall/spin and subsequent uncontrolled impact with terrain. Contributing to the cause was inadequate maintenance which resulted in oil contamination.
Final Report:

Crash of a Learjet 35A in San Diego: 5 killed

Date & Time: Oct 24, 2004 at 0025 LT
Type of aircraft:
Operator:
Registration:
N30DK
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
San Diego – Albuquerque
MSN:
35-345
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
13000
Captain / Total hours on type:
600.00
Copilot / Total flying hours:
3000
Copilot / Total hours on type:
375
Aircraft flight hours:
10047
Circumstances:
On October 24, 2004, about 0025 Pacific daylight time, a Learjet 35A twin-turbofan airplane, N30DK, registered to and operated by Med Flight Air Ambulance, Inc. (MFAA), collided into mountainous terrain shortly after takeoff from Brown Field Municipal Airport (SDM), near San Diego, California. The captain, the copilot, and the three medical crewmembers received fatal injuries, and the airplane was destroyed. The repositioning flight was operated under the provisions of 14 Code of Federal Regulations (CFR) Part 91 with an instrument flight rules (IFR) flight plan filed. Night visual meteorological conditions prevailed. The flight, which was the fourth and final leg of a trip that originated the previous day, departed SDM at 0023.
Probable cause:
The failure of the flight crew to maintain terrain clearance during a VFR departure, which resulted in controlled flight into terrain, and the air traffic controller's issuance of a clearance that transferred the responsibility for terrain clearance from the flight crew to the controller, failure to provide terrain clearance instructions to the flight crew, and failure to advise the flight crew of the MSAW alerts. Contributing to the accident was the pilots' fatigue, which likely contributed to their degraded decision-making.
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 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 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 a Howard 250 in Midland

Date & Time: Oct 3, 2004 at 1620 LT
Type of aircraft:
Operator:
Registration:
N6371C
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Midland – Boulder
MSN:
2598
YOM:
1943
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18000
Captain / Total hours on type:
50.00
Copilot / Total flying hours:
2600
Copilot / Total hours on type:
20
Aircraft flight hours:
8999
Circumstances:
The 18,000- hour pilot was cleared for takeoff in the vintage twin-engine tail wheel equipped airplane on a 9,501- foot by 50- foot runway. The pilot was aware that there was a tailwind from approximately 160 degrees at 10 knots. Shortly after starting the takeoff roll, the airplane swerved to the right. The pilot was able to correct back to the centerline utilizing rudder control. The airplane then swerved to the left, and full right rudder was applied but the swerve could not be corrected. By the time the airplane reached the left edge of the runway, the airplane had not reached its calculated V2 speed of 110 knots. The airplane departed the left side of the runway, went airborne and shortly thereafter, the right wing dropped and contacted the ground. The airplane then spun 180 degrees, impacted the ground, slid backward, and came to rest upright. A post-crash fire consumed the aft fuselage and left wing.
Probable cause:
The pilot's failure to maintain directional control during takeoff. Contributing factors were the choice of runway used and the prevailing tailwind.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante in Douala

Date & Time: Oct 1, 2004
Operator:
Registration:
ZS-OWO
Flight Phase:
Survivors:
Yes
Schedule:
Douala - Yaoundé
MSN:
110-311
YOM:
1981
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the left engine failed. Control was lost and the aircraft veered off runway and came to rest. All four occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the left engine for unknown reasons.