Chitral – Islamabad

On 07 December 2016 morning, after a routine daily inspection at Benazir Bhutto International Airport (BBIAP) Islamabad, Pakistan International Airlines (PIA) aircraft ATR42-500 Reg No AP-BHO operated 05 flights (ie Islamabad to Gilgit and back, Islamabad to Chitral, Chitral to Peshawar and back). As 6th and last flight of that day, it took off from Chitral at time 10:38:50 UTC (15:38:50 PST) with 42 passengers (including 01 engineer) and 05 crew members (03 pilots and 02 cabin crew) aboard for Islamabad. It crashed after 42 minutes of flight at 11:20:38 UTC (16:20:38 PST) about 3.5 Nautical Miles (NM) SSE of Havelian, and 24 NM North of BBIAP Islamabad. All 47 souls aboard were fatally injured. The aircraft remained in air for about 42 minutes before crash (all timings in UTC). These 42 minutes have been split into three stages of flight, described hereunder: (a) Initial Stage: From 10:38 to 11:04 (~26 minutes) degraded speed governing accuracy of the port propeller was evident in the DFDR data, but was apparently not observed by the cockpit crew. The flight stabilized at an altitude 13,500 feet AMSL and a cruising speed of 186 knots IAS (instead of expected 230 knots IAS). There were two latent pre-existing technical anomalies in the aircraft (a Fractured / dislodged PT-1 blade due to a known quality issue and a fractured pin inside the OSG), and one probable latent pre-existing condition (external contamination) inside the PVM of No 1 Engine. Digital Flight Data Recorder (DFDR) analysis indicates that No 1 Engine was degraded. (b) Middle Stage (Series of Technical Malfunctions): From 11:04 to 11:13 (~09 minutes), a series of warnings and technical malfunctions occurred to No 1 Engine (left side) and its related propeller control system. These included Propeller Electronic Control (PEC) fault indications, followed by No 1 Engine power loss, and uncontrolled variation of its propeller speed / blade pitch angle abnormal system operation). The propeller speed which was initially at 82% (cruise setting) decreased gradually to 62% and later at the time of engine power loss it increased to 102% (and stayed at that value for about 15 to 18 seconds). It then reduced down to Non Computed Data (NCD) as per DFDR. At this point, (based on simulation results) the blade pitch angle increased (possibly close to feather position). Later, the propeller speed increased to 120% to 125% (probably caused due to unusual technical malfunctions) and stayed around that value for about 40 to 45 seconds. It finally showed an abrupt drop down to NCD again. At this point, (based on simulation results) the blade pitch angle may have settled at a value, different from the expected feathered propeller. During this unusual variation of propeller speed, there were drastic variations in the aircraft aerodynamic behaviour and sounds. The directional control was maintained initially by the Auto-Pilot. A relatively delayed advancement of power (of No 2 Engine) post No 1 Engine power loss, reduction of power (of No 2 Engine) for about 15 seconds during the timeframe when left propeller rpm was in the range of 120% to 125%, and once again a reduction of power towards the end of this part of flight, were incorrect pilot actions, and contributed in the IAS depletion. Auto-Pilot got disengaged. Towards the end of this part of flight, the aircraft was flying close to stall condition. No 1 Engine was already shutdown and No 2 Engine (right side) was operating normal. At this time, IAS was around 120 knots; aircraft started to roll / turn left and descend. Stick shaker and stick pusher activated. Calculated drag on the left side of the aircraft peaked when the recorded propeller speed was in the range of 120% to 125%. During transition of propeller speed to NCD, the additional component of the drag (possibly caused due to abnormal behaviour of left propeller) suddenly reduced. The advancement of power of No 2 Engine was coupled with excessive right rudder input (to counter the asymmetric condition). This coincided with last abrupt drop in the propeller speed. As a combined effect of resultant aerodynamic forces aircraft entered into a stalled / uncontrolled flight condition, went inverted and lost 5,100 feet AMSL altitude (ie from ~13,450 feet to 8,350 feet AMSL). (c) Final Stage: The final stage of flight from 11:13 to 11:20 (~07 minutes) started with the aircraft recovering from the uncontrolled flight. Although blade pitch position was not recorded (in the DFDR – by design), and it was not possible to directly calculate that from the available data, a complex series of simulations and assumptions estimated that the blade pitch of left propeller may have settled at an angle around low pitch in flight while rotating at an estimated speed of 5%. Aircraft simulations indicated that stable additional drag forces were present on the left side of the aircraft at this time and during the remaining part of flight. Aircraft had an unexpected (high) drag from the left side (almost constant in this last phase); the aircraft behavior was different from that of a typical single engine In Flight Shutdown (IFSD) situation. In this degraded condition it was not possible for the aircraft to maintain a level flight. However, that level of drag did not preclude the lateral control of the aircraft, if a controlled descent was initiated. The aircraft performance was outside the identified performance envelope. It was exceptionally difficult for the pilots to understand the situation and hence possibly control the aircraft. Figure hereunder shows different stages of flight.

Flight / Schedule

Chitral – Islamabad

Aircraft

ATR42-500

Registration

AP-BHO

MSN

663

Year of Manufacture

2007

Date

December 7, 2016 at 04:20 PM

Type

CRASH

Flight Type

Scheduled Revenue Flight

Flight Phase

Flight

Crash Site

Mountains

Crash Location

Havelian Khyber Pakhtunkhwa (<U+062E><U+06CC><U+0628><U+0631><U+067E><U+062E><U+062A><U+0648><U+0646><U+062E><U+0648><U+0627>)

Region

Asia • Pakistan

Crash Cause

Technical failure

Narrative Report

On December 7, 2016 at 04:20 PM, Chitral – Islamabad experienced a crash involving ATR42-500, operated by Pakistan International Airlines - PIA, with the event recorded near Havelian Khyber Pakhtunkhwa (<U+062E><U+06CC><U+0628><U+0631><U+067E><U+062E><U+062A><U+0648><U+0646><U+062E><U+0648><U+0627>).

The flight was categorized as scheduled revenue flight and the reported phase was flight at a mountains crash site.

47 people were known to be on board, 47 fatalities were recorded, 0 survivors were identified or estimated. This corresponds to an estimated fatality rate of 100.0%.

Crew on board: 5, crew fatalities: 5, passengers on board: 42, passenger fatalities: 42, other fatalities: 0.

The listed crash cause is technical failure. On 07 December 2016 morning, after a routine daily inspection at Benazir Bhutto International Airport (BBIAP) Islamabad, Pakistan International Airlines (PIA) aircraft ATR42-500 Reg No AP-BHO operated 05 flights (ie Islamabad to Gilgit and back, Islamabad to Chitral, Chitral to Peshawar and back). As 6th and last flight of that day, it took off from Chitral at time 10:38:50 UTC (15:38:50 PST) with 42 passengers (including 01 engineer) and 05 crew members (03 pilots and 02 cabin crew) aboard for Islamabad. It crashed after 42 minutes of flight at 11:20:38 UTC (16:20:38 PST) about 3.5 Nautical Miles (NM) SSE of Havelian, and 24 NM North of BBIAP Islamabad. All 47 souls aboard were fatally injured. The aircraft remained in air for about 42 minutes before crash (all timings in UTC). These 42 minutes have been split into three stages of flight, described hereunder: (a) Initial Stage: From 10:38 to 11:04 (~26 minutes) degraded speed governing accuracy of the port propeller was evident in the DFDR data, but was apparently not observed by the cockpit crew. The flight stabilized at an altitude 13,500 feet AMSL and a cruising speed of 186 knots IAS (instead of expected 230 knots IAS). There were two latent pre-existing technical anomalies in the aircraft (a Fractured / dislodged PT-1 blade due to a known quality issue and a fractured pin inside the OSG), and one probable latent pre-existing condition (external contamination) inside the PVM of No 1 Engine. Digital Flight Data Recorder (DFDR) analysis indicates that No 1 Engine was degraded. (b) Middle Stage (Series of Technical Malfunctions): From 11:04 to 11:13 (~09 minutes), a series of warnings and technical malfunctions occurred to No 1 Engine (left side) and its related propeller control system. These included Propeller Electronic Control (PEC) fault indications, followed by No 1 Engine power loss, and uncontrolled variation of its propeller speed / blade pitch angle abnormal system operation). The propeller speed which was initially at 82% (cruise setting) decreased gradually to 62% and later at the time of engine power loss it increased to 102% (and stayed at that value for about 15 to 18 seconds). It then reduced down to Non Computed Data (NCD) as per DFDR. At this point, (based on simulation results) the blade pitch angle increased (possibly close to feather position). Later, the propeller speed increased to 120% to 125% (probably caused due to unusual technical malfunctions) and stayed around that value for about 40 to 45 seconds. It finally showed an abrupt drop down to NCD again. At this point, (based on simulation results) the blade pitch angle may have settled at a value, different from the expected feathered propeller. During this unusual variation of propeller speed, there were drastic variations in the aircraft aerodynamic behaviour and sounds. The directional control was maintained initially by the Auto-Pilot. A relatively delayed advancement of power (of No 2 Engine) post No 1 Engine power loss, reduction of power (of No 2 Engine) for about 15 seconds during the timeframe when left propeller rpm was in the range of 120% to 125%, and once again a reduction of power towards the end of this part of flight, were incorrect pilot actions, and contributed in the IAS depletion. Auto-Pilot got disengaged. Towards the end of this part of flight, the aircraft was flying close to stall condition. No 1 Engine was already shutdown and No 2 Engine (right side) was operating normal. At this time, IAS was around 120 knots; aircraft started to roll / turn left and descend. Stick shaker and stick pusher activated. Calculated drag on the left side of the aircraft peaked when the recorded propeller speed was in the range of 120% to 125%. During transition of propeller speed to NCD, the additional component of the drag (possibly caused due to abnormal behaviour of left propeller) suddenly reduced. The advancement of power of No 2 Engine was coupled with excessive right rudder input (to counter the asymmetric condition). This coincided with last abrupt drop in the propeller speed. As a combined effect of resultant aerodynamic forces aircraft entered into a stalled / uncontrolled flight condition, went inverted and lost 5,100 feet AMSL altitude (ie from ~13,450 feet to 8,350 feet AMSL). (c) Final Stage: The final stage of flight from 11:13 to 11:20 (~07 minutes) started with the aircraft recovering from the uncontrolled flight. Although blade pitch position was not recorded (in the DFDR – by design), and it was not possible to directly calculate that from the available data, a complex series of simulations and assumptions estimated that the blade pitch of left propeller may have settled at an angle around low pitch in flight while rotating at an estimated speed of 5%. Aircraft simulations indicated that stable additional drag forces were present on the left side of the aircraft at this time and during the remaining part of flight. Aircraft had an unexpected (high) drag from the left side (almost constant in this last phase); the aircraft behavior was different from that of a typical single engine In Flight Shutdown (IFSD) situation. In this degraded condition it was not possible for the aircraft to maintain a level flight. However, that level of drag did not preclude the lateral control of the aircraft, if a controlled descent was initiated. The aircraft performance was outside the identified performance envelope. It was exceptionally difficult for the pilots to understand the situation and hence possibly control the aircraft. Figure hereunder shows different stages of flight.

Aircraft reference details include registration AP-BHO, MSN 663, year of manufacture 2007.

Fatalities

Total

47

Crew

5

Passengers

42

Other

0

Crash Summary

On 07 December 2016 morning, after a routine daily inspection at Benazir Bhutto International Airport (BBIAP) Islamabad, Pakistan International Airlines (PIA) aircraft ATR42-500 Reg No AP-BHO operated 05 flights (ie Islamabad to Gilgit and back, Islamabad to Chitral, Chitral to Peshawar and back). As 6th and last flight of that day, it took off from Chitral at time 10:38:50 UTC (15:38:50 PST) with 42 passengers (including 01 engineer) and 05 crew members (03 pilots and 02 cabin crew) aboard for Islamabad. It crashed after 42 minutes of flight at 11:20:38 UTC (16:20:38 PST) about 3.5 Nautical Miles (NM) SSE of Havelian, and 24 NM North of BBIAP Islamabad. All 47 souls aboard were fatally injured. The aircraft remained in air for about 42 minutes before crash (all timings in UTC). These 42 minutes have been split into three stages of flight, described hereunder: (a) Initial Stage: From 10:38 to 11:04 (~26 minutes) degraded speed governing accuracy of the port propeller was evident in the DFDR data, but was apparently not observed by the cockpit crew. The flight stabilized at an altitude 13,500 feet AMSL and a cruising speed of 186 knots IAS (instead of expected 230 knots IAS). There were two latent pre-existing technical anomalies in the aircraft (a Fractured / dislodged PT-1 blade due to a known quality issue and a fractured pin inside the OSG), and one probable latent pre-existing condition (external contamination) inside the PVM of No 1 Engine. Digital Flight Data Recorder (DFDR) analysis indicates that No 1 Engine was degraded. (b) Middle Stage (Series of Technical Malfunctions): From 11:04 to 11:13 (~09 minutes), a series of warnings and technical malfunctions occurred to No 1 Engine (left side) and its related propeller control system. These included Propeller Electronic Control (PEC) fault indications, followed by No 1 Engine power loss, and uncontrolled variation of its propeller speed / blade pitch angle abnormal system operation). The propeller speed which was initially at 82% (cruise setting) decreased gradually to 62% and later at the time of engine power loss it increased to 102% (and stayed at that value for about 15 to 18 seconds). It then reduced down to Non Computed Data (NCD) as per DFDR. At this point, (based on simulation results) the blade pitch angle increased (possibly close to feather position). Later, the propeller speed increased to 120% to 125% (probably caused due to unusual technical malfunctions) and stayed around that value for about 40 to 45 seconds. It finally showed an abrupt drop down to NCD again. At this point, (based on simulation results) the blade pitch angle may have settled at a value, different from the expected feathered propeller. During this unusual variation of propeller speed, there were drastic variations in the aircraft aerodynamic behaviour and sounds. The directional control was maintained initially by the Auto-Pilot. A relatively delayed advancement of power (of No 2 Engine) post No 1 Engine power loss, reduction of power (of No 2 Engine) for about 15 seconds during the timeframe when left propeller rpm was in the range of 120% to 125%, and once again a reduction of power towards the end of this part of flight, were incorrect pilot actions, and contributed in the IAS depletion. Auto-Pilot got disengaged. Towards the end of this part of flight, the aircraft was flying close to stall condition. No 1 Engine was already shutdown and No 2 Engine (right side) was operating normal. At this time, IAS was around 120 knots; aircraft started to roll / turn left and descend. Stick shaker and stick pusher activated. Calculated drag on the left side of the aircraft peaked when the recorded propeller speed was in the range of 120% to 125%. During transition of propeller speed to NCD, the additional component of the drag (possibly caused due to abnormal behaviour of left propeller) suddenly reduced. The advancement of power of No 2 Engine was coupled with excessive right rudder input (to counter the asymmetric condition). This coincided with last abrupt drop in the propeller speed. As a combined effect of resultant aerodynamic forces aircraft entered into a stalled / uncontrolled flight condition, went inverted and lost 5,100 feet AMSL altitude (ie from ~13,450 feet to 8,350 feet AMSL). (c) Final Stage: The final stage of flight from 11:13 to 11:20 (~07 minutes) started with the aircraft recovering from the uncontrolled flight. Although blade pitch position was not recorded (in the DFDR – by design), and it was not possible to directly calculate that from the available data, a complex series of simulations and assumptions estimated that the blade pitch of left propeller may have settled at an angle around low pitch in flight while rotating at an estimated speed of 5%. Aircraft simulations indicated that stable additional drag forces were present on the left side of the aircraft at this time and during the remaining part of flight. Aircraft had an unexpected (high) drag from the left side (almost constant in this last phase); the aircraft behavior was different from that of a typical single engine In Flight Shutdown (IFSD) situation. In this degraded condition it was not possible for the aircraft to maintain a level flight. However, that level of drag did not preclude the lateral control of the aircraft, if a controlled descent was initiated. The aircraft performance was outside the identified performance envelope. It was exceptionally difficult for the pilots to understand the situation and hence possibly control the aircraft. Figure hereunder shows different stages of flight.

Cause: Technical failure

Occupants & Outcome

Crew On Board

5

Passengers On Board

42

Estimated Survivors

0

Fatality Rate

100.0%

Known people on board: 47

Operational Details

Schedule / Flight

Chitral – Islamabad

Flight Type

Scheduled Revenue Flight

Flight Phase

Flight

Crash Site

Mountains

Region / Country

Asia • Pakistan

Aircraft Details

Aircraft

ATR42-500

Registration

AP-BHO

MSN

663

Year of Manufacture

2007

Similar Plane Crashes

January 6, 1922 at 12:00 AM2 Fatalities

Royal Air Force - RAF

De Havilland DH.10 Amiens

While making a turn on short final, the aircraft impacted ground and crashed. Two crew members were killed and a third was seriously injured. Crew: F/O J. C. Belford, F/O H. B. D. Harrington, † LAC Woodall. †

April 2, 1927 at 12:00 AM

Bernard M. T. Shute Leete

De Havilland DH.60 Moth

Bernard M. T. Shute Leete, owner of the aircraft, pilot and member of the Royal Aero Club, departed Stag Lane near London on 15NOV1926 on a flight to Pakistan. He arrived at Karachi on 08JAN1927 and in Lahore on 15FEB1927. In Punjab, he decided to make several demonstration flights. After few manoeuvres in the vicinity of the airport, he completed a last turn to join the airport. On final approach, while flying too low, the aircraft hit power cables, stalled and crashed before coming to rest upside down. While both occupants were slightly injured, the aircraft was destroyed. Crew: Bernard M. T. Shute Leete, pilot. Passenger: Mrs. Hailey, wife of Governor of the Punjab.

September 30, 1931 at 12:00 AM

Air Orient

Farman F.303

En route to Karachi, while flying near Somiani, one of the engine caught fire. The crew attempted an emergency landing when the crashed. All four occupants were slightly injured.

October 26, 1936 at 12:00 AM

Air Bleu

Caudron C.440 Goéland

Crashed on landing in unknown circumstances. All three crewmen were unhurt while the aircraft was damaged beyond repair.

February 19, 1937 at 12:00 AM

Indian National Airways - INA

De Havilland DH.83 Fox Moth

Crashed on takeoff for unknown reason. All four occupants were injured and the aircraft was destroyed.

February 23, 1939 at 12:00 AM1 Fatalities

Indian National Airways - INA

Percival D.3 Gull Six

Few minutes after take off from Karachi Airport, while on a positioning flight, the single engine aircraft collided with a Beechcraft E17B flying for Indian National Airways as well. Registered VT-AKJ, this second aircraft was carrying a pilot who was approaching Karachi to land on the Mauripur airfield. Following the collision, both aircraft dove into the ground and crashed in a field located some 50 km north of Karachi. While the pilot of the Percival, B. D. Sharma, was killed, the pilot of the Beechcraft survived.