Crash of a Lockheed C-130H Hercules in Sanaa

Date & Time: Nov 18, 2010
Type of aircraft:
Operator:
Registration:
7O-ADD
Flight Type:
Survivors:
Yes
MSN:
4827
YOM:
1979
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Sanaa Airport, the four engine aircraft veered off runway and came to rest, bursting into flames. All occupants escaped uninjured. The fire was quickly extinguished but the aircraft was damaged beyond repair.

Crash of a Learjet 25B in Portland

Date & Time: Nov 17, 2010 at 1553 LT
Type of aircraft:
Operator:
Registration:
N25PJ
Flight Type:
Survivors:
Yes
Schedule:
Boise - Portland
MSN:
25-111
YOM:
1973
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6000
Copilot / Total flying hours:
652
Copilot / Total hours on type:
10
Aircraft flight hours:
8453
Circumstances:
The airplane was flying a VOR/DME-C approach that was on an oblique course about 40 degrees to the runway 30 centerline; the wind conditions produced an 8-knot tailwind for landing on runway 30. Despite the tailwind, the captain elected to land on the 6,600-foot-long runway instead of circling to land with a headwind. Moderate to heavy rain had been falling for the past hour, and the runway was wet. The crew said that the airplane was flown at the prescribed airspeed (Vref) for its weight with the wing flaps fully extended on final approach, and that they touched down just beyond the touchdown zone. The captain said that he extended the wings' spoilers immediately after touchdown. He tested the brakes and noted normal brake pedal pressure. However, during rollout, he noted a lack of deceleration and applied more brake pressure, with no discernible deceleration. The airplane's optional thrust reversers had been previously rendered non-operational by company maintenance personnel and were therefore not functional. The captain stated that he thought about performing a go-around but believed that insufficient runway remained to ensure a safe takeoff. While trying to stop, he did not activate the emergency brakes (which would have bypassed the anti-skid system) because he thought that there was insufficient time, and he was preoccupied with maintaining control of the airplane. He asked the first officer to apply braking with him, and together the crew continued applying brake pedal pressure; however, when the airplane was about 2,000 feet from the runway's end, it was still traveling about 100 knots. As the airplane rolled off the departure end on runway 30, which was wet, both pilots estimated that the airplane was still travelling between 85 and 90 knots. The airplane traveled 618 feet through a rain-soaked grassy runway safety area before encountering a drainage swale that collapsed the nose gear. As the airplane was traversing the soft, wet field, its wheels partially sank into the ground. While decelerating, soil impacted the landing gear wheels and struts where wiring to the antiskid brake system was located. The crew said that there were no indications on any cockpit annunciator light of a system failure or malfunction; however, after the airplane came to a stop they observed that the annunciator light associated with the antiskid system for the No. 2 wheel was illuminated (indicating a system failure). The other three annunciator lights (one for each wheel) were not illuminated. During the approach, the first officer had completed the landing data card by using a company-developed quick reference card. The quick reference card’s chart, which contained some data consistent with the landing charts in the Airplane Flight Manual (AFM), did not have correction factors for tailwind conditions, whereas the charts in the AFM do contain corrective factors for tailwind conditions. The landing data prepared by the first officer indicated that 3,240 feet was required to stop the airplane on a dry runway in zero wind conditions, with a wet correction factor increasing stopping distance to 4,538 feet. The Vref speed was listed as 127 knots for their landing weight of 11,000 pounds, and the first officer’s verbal and written statements noted that they crossed the runway threshold at 125 knots. During the investigation, Bombardier Lear calculated the wet stopping distances with an 8-knot tailwind as 5,110 feet. The touchdown zone for runway 30 is 1,000 feet from the approach end. The crew’s estimate of their touchdown location on the runway is about 1,200 feet from the approach end, yielding a remaining runway of 5,400 feet. On-duty controllers in the tower watched the landing and said that the airplane touched down in front of the tower at a taxiway intersection that is 1,881 feet from the approach end, which would leave about 4,520 feet of runway to stop the airplane. The controllers observed water spraying off the airplane’s main landing gear just after touchdown. Post accident testing indicated that the brake system, including the brake wear, was within limits, with no anomalies found. No evidence of tire failure was noted. The antiskid system was removed from the airplane for functional tests. The control box and the left and right control valves tested within specifications. The four wheel speed sensors met the electrical resistance specification. For units 1, 2 and 3, the output voltages exceeded the minimum specified voltages for each of the listed frequencies. Unit 4 was frozen and could not be rotated and thus could not be tested. Sensors 1 and 2 exceeded the specified 15% maximum to minimum voltage variation limit. Sensor 3 was within the limit and 4 could not be tested. Based on all the evidence, it is likely that the airplane touched down on the water-contaminated runway beyond the touchdown zone, at a point with about 600 feet less remaining runway than the performance charts indicated that the airplane required for the wet conditions. Since a reverted rubber hydroplaning condition typically follows an encounter with dynamic hydroplaning, the reverted rubber signatures on the No. 2 tire indicate that the airplane encountered dynamic hydroplaning shortly after touchdown, and the left main gear wheel speed sensor anomalies allowed the left tires to progress to reverted rubber hydroplaning. This, along with postaccident testing, indicates that the anti-skid system was not performing optimally and, in concert with the hydroplaning conditions, significantly contributed to the lack of deceleration during the braking attempts.
Probable cause:
The failure of the flight crew to stop the airplane on the runway due to the flying pilot’s failure to attain the proper touchdown point. Contributing to the accident was an anti-skid system that was not performing optimally, which allowed the airplane to encounter reverted rubber hydroplaning, and the company-developed quick reference landing distance chart that did not provide correction factors related to tailwind conditions.
Final Report:

Crash of a Swearingen SA227AC Metro III in Andahuaylas

Date & Time: Nov 13, 2010 at 1602 LT
Type of aircraft:
Operator:
Registration:
N781C
Survivors:
Yes
Schedule:
Huaraz - Andahuaylas
MSN:
AC-535
YOM:
1982
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6301
Captain / Total hours on type:
2615.00
Copilot / Total flying hours:
3253
Copilot / Total hours on type:
737
Aircraft flight hours:
27889
Aircraft flight cycles:
37163
Circumstances:
Following an uneventful flight, the twine engine aircraft approached Andahuaylas Airport and landed normally on runway 03. After touchdown, while decelerating to a speed of about 40 knots, the aircraft started to deviate to the left. The crew counteracted but the aircraft continued to the left, veered off runway, rolled through a grassy and eventually came down a four meters high embankment before coming to rest. While all 19 occupants escaped uninjured, the aircraft was damaged beyond repair.
Probable cause:
It appears that the loss of directional control after touchdown was caused by the failure of the brake systems. The aircraft had already several technical problems with its brake systems previous to the flight, and maintenance was performed by technicians the day before the accident. For unknown reasons, the problem was resolved but no feedback or troubleshooting was performed on part of the technicians or the crew. The Captain was aware of the problem and took the decision to complete the flight despite the risk the problem may persist or happen again.
Final Report:

Crash of an Antonov AN-24B in Zalingei: 2 killed

Date & Time: Nov 11, 2010 at 1618 LT
Type of aircraft:
Operator:
Registration:
ST-ARQ
Survivors:
Yes
Schedule:
Khartoum - Nyala - Zalingei
MSN:
0 73 059 10
YOM:
1970
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
38
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4400
Captain / Total hours on type:
300.00
Copilot / Total flying hours:
900
Copilot / Total hours on type:
700
Circumstances:
The crew started the approach to Zaligei Airport runway 03 in good weather conditions. The aircraft landed hard 200 metres past the runway threshold, causing both propeller blades to struck the ground on a distance of 33 metres. The aircraft bounced and landed a second time 263 metres further then a third time after 15 metres. Upon impact, both engines were torn off and the aircraft rolled for about 400 metres before coming to rest, bursting into flames. Two passengers were killed while five others were injured. All 37 other occupants escaped unhurt. The aircraft was totally destroyed by a post crash fire.
Probable cause:
Sudan's Central Directorate of Air Accident Investigation concluded the probable causes as follow:
The accident cause is a complex set of reasons. The aircraft impacted the ground on three wheels at high forward speed shearing off both engines and propellers and damaging the left main landing gear which put the aircraft in an uncontrollable condition.
Contributory factors were:
- Absence of crew coordination,
- Absence of cabin procedure and check-lists for different phases of flight,
- Unsatisfactory Periodic and Annual job check being reflected on the inoperative Cockpit Voice and Flight Data Recorders,
- Bad planning of the flight and long period taken to clear the recorded defects before departure is considered to be a contributory factor to this accident.

Crash of a Swearingen SA227AC Metro III in Huánuco

Date & Time: Nov 5, 2010 at 1423 LT
Type of aircraft:
Operator:
Registration:
N115GS
Survivors:
Yes
Schedule:
Lima - Huánuco
MSN:
AC-715
YOM:
1988
Flight number:
LCB1331
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7590
Captain / Total hours on type:
553.00
Copilot / Total flying hours:
5348
Copilot / Total hours on type:
2050
Aircraft flight hours:
24342
Aircraft flight cycles:
32730
Circumstances:
Following an uneventful flight from Lima, the crew continued the approached while the aircraft was unstabilized. Upon touchdown on runway 07, the aircraft landed relatively hard then bounced three times when the crew retracted the landing gear. The aircraft slid on its belly for about 600 metres before coming to rest. All nine occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Erroneous retraction of the landing gear following three bounces on the runway due to an unstabilized final approach and poor crew resource management.
Contributing factors were:
- Although the descent and landing checklists were followed, the crew did not review stabilized approach criteria or procedures for a possible controlled flight into terrain and did not take into consideration the possibility of any go around procedure
- Several call-outs were non-standard while others were missing
- Descent was continued under visual flight rules, approach was unstabilized and not detected by crew
- Speed was too high on touch down while the power levers were not into idle position
- Lack of corrective action on part of the crew when the aircraft was bouncing
- Loss of situational awareness led to the retraction of the landing gear.
Final Report:

Crash of a Beechcraft 1900C-1 in Karachi: 21 killed

Date & Time: Nov 5, 2010 at 0706 LT
Type of aircraft:
Operator:
Registration:
AP-BJD
Flight Phase:
Survivors:
No
Schedule:
Karachi - Bhit Shah
MSN:
UC-157
YOM:
1991
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
8114
Captain / Total hours on type:
1820.00
Copilot / Total flying hours:
1746
Copilot / Total hours on type:
1338
Aircraft flight hours:
18545
Aircraft flight cycles:
24990
Circumstances:
0C-1 aircraft Reg # AP-BJD was scheduled to fly chartered flight from Jinnah International Airport (JIAP), Karachi to Bhit Shah Oil Fields to convey 17 employees of M/s Eni company including one foreign national from Italy. The flight crew included two cockpit crew ie Captain and First Officer (FO), one JS (Air) ground crew (technician) and one Airport Security Force staff. The Mishap Aircraft (MA) took off from JIAP, Karachi at 02:04:31 UTC. The reported weather was fit for the conduct of ill-fated flight to Bhit Shah Oil Fields. After takeoff aircraft experienced Engine No 2 abnormal operation and cockpit crew decided to land back at JIAP Karachi after calling right hand downwind for runway 25R. While joining for right hand downwind for 25R the mishap aircraft could not sustain flight and crashed at a distance of around 1 nm from runway 07R beginning JIAP, Karachi. All souls (21) onboard got fatally injured as a result of aircraft ground impact and extensive post impact ground fire.
Probable cause:
Detailed investigation and analyses of the examinable evidence confirmed that the aircraft had developed some problem with its Engine No.2 (Right) immediately after takeoff which was observed by the cockpit crew as propeller feathering on its own. No concrete evidence could be found which would have led to the engine’s propeller malfunction as observed. The only probable cause of propeller feathering on its own could be the wear & tear of the beta valve leading to beta system malfunction. However, this anomaly at the most could have led to the non availability of one engine and making a safe landing with a single engine since the aircraft was capable of landing with a single engine operation. Some of the actions by the cockpit crew before takeoff and subsequent to the observed anomaly in the Engine No.2 were not according to the QRH / FCOM which aggravated the situation and resulted into the catastrophic accident.
The following factors contributed to the accident:
The aircraft accident took place as a result of combination of various factors which directly and indirectly contributed towards the causation of accident.
The primary cause of accident includes, inappropriate skill level of Captain to handle abnormal operation of engine No 2 just after takeoff, failure of cockpit crew to raise the landing gears after experiencing the engine anomaly, execution of remedial actions by FO before the attainment of minimum safe altitude of 400 ft AGL resulted in non conformance and non compliance of cockpit crew to OEM recommended procedures to handle such situations.
The lack of situational awareness and CRM failure directly contributed towards ineffective management of the flight deck by the cockpit crew.
The contributory factors include inadequate cockpit crew simulator training monitoring mechanism both at operator and CAA Pakistan levels in respect of correlation of previous / current performance and skill level of cockpit crew during the simulator training sessions along with absence of conduct of recurrent / refresher simulator training between two annual simulator checks in accordance with ICAO Annex-6 guidelines and CAA Pakistan (applicable ANOs) requirements for specific type of aircraft in a year.
Final Report:

Crash of a Boeing 737-4Y0 in Pontianak

Date & Time: Nov 2, 2010 at 1118 LT
Type of aircraft:
Operator:
Registration:
PK-LIQ
Survivors:
Yes
Schedule:
Jakarta – Pontianak
MSN:
24911/2033
YOM:
1991
Flight number:
JT712
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
169
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8190
Copilot / Total flying hours:
656
Aircraft flight hours:
49107
Aircraft flight cycles:
28889
Circumstances:
On 2 November 2010, a Boeing Company B737-400 aircraft, registered PK-LIQ, was being operated by Lion Mentari Airlines on a passenger schedule flight with flight number JT 712. This flight was the first flight for the crew and was scheduled for departure at 09.30 LT (02.30 UTC). On board the flight was 175 person included 2 pilots and 4 flight attendants and 169 passengers consisted 2 infants and one engineer. The pilots stated that the aircraft had history problem on the difficulty of selection the thrust reversers and automatic of the speed brake deployment. This problem was repetitive since the past three months. The aircraft pushed back at 0950 LT (0250 UTC). During taxi out, the yaw damper light illuminated for two times. The pilot referred to the Quick Reference Handbook (QRH) which guided the pilot to turn off the yaw dumper switch then back to turn on. Considered to these problems, the pilot asked the engineer to come to cockpit and asked to witness the problem. The aircraft departed Soekarno Hatta International Airport, Jakarta at 1012 LT (0312 UTC) with destination of Supadio Airport, Pontianak. The Pilot in Command acted as pilot flying (PF) and the Second in Command acted as pilot monitoring (PM). The flight to Pontianak until commenced for descent was uneventful. Prior to descend, the PF performed approach crew briefing with additional briefing included review of the past experiences on the repetitive problems of thrust reversers which sometimes hard to operate and the speed brake failed to auto deploy. Considering these problems, the PF asked to the PM to check and to remind him to the auto deployment of the speed brake after the aircraft touch down. During descend, the pilot was instructed by Pontianak Approach controller to conduct Instrument Landing System (ILS) approach for runway 15 and was informed that the weather was slight rain. On the initial approach, the auto pilot engaged, flaps 5° and aircraft speed 180 knots. After the aircraft captured the localizer at 1300 feet, the PF asked to the PM to select the landing gear down, flaps 15° and the speed decreased to 160 knots. The PF aimed to set the flaps landing configuration when the glide slope captured. When the glide slope captured, the auto pilot did not automatically follow the glide path and the aircraft altitude maintained at 1300 feet, resulted in the aircraft slightly above the normal glide path. The PF realized the condition then disengaged the auto pilot and the auto throttle simultaneously, and fly manually to correct the glide path by pushing the aircraft pitch down. While trying to regain the correct the glide path, the PF commanded for flaps 40° and to complete the landing checklist. The flap lever has been selected to 40°, but the indicator indicated at 30°. Realized to the flaps indication, the PF asked the landing speed for flaps 30° configuration in case the flaps could not move further to 40°. When aircraft altitude was 600 feet and the pilots completing the landing checklist, the PM reselected the flap from 30° to 40° and was successful. The pilots realized that the aircraft touched down was beyond the touchdown zone and during the landing roll the PF tried to select the thrust reverser but the levers were hard to select and followed by the speed brake failed to automatic-deploy. The pilots did not feel the deceleration, and then the PF applied maximum manual braking and selected the speed brake handle manually. Afterward, the thrust reversers successfully operated and a loud sound was heard prior to the aircraft stop. The Supadio tower controller on duty noticed that the aircraft was about to overrun the runway and immediately pressed the crash bell. The aircraft stopped at approximately 70 meters from the runway or 10 meters from the end of stop-way. The PIC then commanded to the flight attendants to evacuate the passengers through the exits. No one injured in this accident.
Probable cause:
The following factors were identified:
- Inconsistency to the Aircraft Maintenance Manual (AMM) for the rectifications performed during the period of the reversers and auto speed brake deployment problem was might probably result of the unsolved symptom problems.
- The decision to land during the un-stabilized approach which occurred from 1000 feet to 50 feet above threshold influenced by lack of crew ability in assessing to accurately perceive what was going on in the flight deck and outside the airplane.
- The effect of delayed of the speed brake and thrust reverser deployment effected to the aircraft deceleration which required landing distance greater than the available landing distance.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Port Mansfield

Date & Time: Oct 29, 2010 at 1611 LT
Registration:
N234PM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Port Mansfield – Sinton
MSN:
46-97200
YOM:
2005
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3500
Captain / Total hours on type:
5.00
Aircraft flight hours:
650
Circumstances:
The pilot reported that shortly after takeoff the engine lost power momentarily, just before losing power completely. The pilot performed an emergency landing in a nearby field. The airplane sustained substantial damage during the forced landing. The airframe, engine, and engine accessories were examined. Fuel was noted at the engine, and no anomalies were revealed that would have contributed to the accident. The cause of the loss of power could not be determined.
Probable cause:
The total loss of engine power for undetermined reasons because examination of the airframe and engine did not reveal any anomalies that would have contributed to the loss of engine power.
Final Report:

Crash of a Piper PA-31-310 Navajo in Wentworth

Date & Time: Oct 26, 2010 at 0708 LT
Type of aircraft:
Operator:
Registration:
G-FILL
Flight Type:
Survivors:
Yes
MSN:
31-7912069
YOM:
1979
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7952
Captain / Total hours on type:
533.00
Circumstances:
The pilot was landing at a private strip at Wentworth. The runway was oriented 110/290° and had several level changes along its length which required all landings to be made in the 110° direction and all takeoffs in the 290° direction. Touchdown was required to take place on a level portion before the ground rose relatively steeply and levelled out again. The final part of the runway sloped gently down towards the end, which was bordered by a dry stone wall. The surface, from police photographs taken soon after the accident, showed it to be closely mown grass and firm, despite the indications of recent rain. The wind at the time was 220°/10 kt and the pilot reported that the approach was made directly into the setting sun, making it difficult to monitor the airspeed indicator. Touchdown was achieved on the first level portion of the runway and the brakes were applied very soon afterwards; however the pilot stated that there was no discernible braking action, despite applying firmer pressure on the brake pedals. Seeing that the stone wall at the end of the runway was approaching, he steered the aircraft to the right and towards a hedge, however he was unable to prevent the left wing striking the walland causing severe damage outboard of the engine. The pilot was uninjured and evacuated the aircraft normally. The police photographs indicate that the mainwheels were skidding on the wet grass almost throughout the landing roll of about 630 metres. Whilst the pilot acknowledged that his airspeed might have been somewhat high, he did not feel at the time of touchdown that his ground speed was unusual and he attributes the lack of braking action to the slippery runway surface.
Final Report:

Crash of a Beechcraft 100 King Air in Kirby Lake: 1 killed

Date & Time: Oct 25, 2010 at 1120 LT
Type of aircraft:
Operator:
Registration:
C-FAFD
Survivors:
Yes
Schedule:
Calgary - Edmonton - Kirby Lake
MSN:
B-42
YOM:
1970
Flight number:
KBA103
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The aircraft was on an instrument flight rules flight from the Edmonton City Centre Airport to Kirby Lake, Alberta. At approximately 1114 Mountain Daylight Time, during the approach to Runway 08 at the Kirby Lake Airport, the aircraft struck the ground, 174 feet short of the threshold. The aircraft bounced and came to rest off the edge of the runway. There were 2 flight crew members and 8 passengers on board. The captain sustained fatal injuries. Four occupants, including the co-pilot, sustained serious injuries. The 5 remaining passengers received minor injuries. The aircraft was substantially damaged. A small, post-impact, electrical fire in the cockpit was extinguished by survivors and first responders. The emergency locator transmitter was activated on impact. All passengers were BP employees.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The conduct of the flight crew members during the instrument approach prevented them from effectively monitoring the performance of the aircraft.
2. During the descent below the minimum descent altitude, the airspeed reduced to a point where the aircraft experienced an aerodynamic stall and loss of control. There was insufficient altitude to effect recovery prior to ground impact.
3. For unknown reasons, the stall warning horn did not activate; this may have provided the crew with an opportunity to avoid the impending stall.
Findings as to Risk:
1. The use of company standard weights and a non-current aircraft weight and balance report resulted in the flight departing at an inaccurate weight. This could result in a performance regime that may not be anticipated by the pilot.
2. Flying an instrument approach using a navigational display that is outside the normal scan of the pilot increases the workload during a critical phase of flight.
3. Flying an abbreviated approach profile without applying the proper transition altitudes increases the risk of controlled flight into obstacles or terrain.
4. Not applying cold temperature correction values to the approach altitudes decreases the built-in obstacle clearance parameters of an instrument approach.
Final Report: