Crash of an ATR42-500 in Gilgit

Date & Time: Jul 20, 2019 at 0815 LT
Type of aircraft:
Operator:
Registration:
AP-BHP
Survivors:
Yes
Schedule:
Islamabad – Gilgit
MSN:
665
YOM:
2007
Flight number:
PK605
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7951
Captain / Total hours on type:
1210.00
Copilot / Total flying hours:
757
Copilot / Total hours on type:
557
Aircraft flight hours:
22235
Aircraft flight cycles:
22057
Circumstances:
Flight PIA 605 ATR 42-500 aircraft Reg. No. AP-BHP was a scheduled passenger flight from IIAP, Islamabad to Gilgit Airport. There was no abnormality reported in the aircraft prior to the flight. Aircraft loading was within normal limits of 24.7% Centre of Gravity (CG) with Take-off Gross Weight (TOGW) 18,600 kilograms (kg). The aircrew was current and had adequate experience both on the aircraft as well as for flights to Gilgit Airport. Gilgit Airport is located at an altitude of 4,784 ft Above Mean Sea Level (AMSL) with R/W dimensions 5,400 x 100 ft and is deemed fit for operations under PCAA regulations. For this sector, Captain was Pilot Flying (PF) while the First Officer (FO) was Pilot Monitoring (PM). The aircraft took off from IIAP, Islamabad at 02:02 hours (h) and Auto Pilot (AP) was engaged at 260 ft Radio Altimeter (RA) height and the climb was performed under AP using Vertical Speed (VS) mode. This mode is not recommended as per Flight Crew Operations Manual (FCOM). As a consequence the aircraft Indicated Air Speed (IAS) dropped to 130 knots (kt) as opposed to standard climb speed of 160 kt. However, the enroute flight at Flight Level (FL) 165 subsequently remained uneventful. During the cruise, the lowest RA height prior to descent was recorded as 2,636 ft; however, this is in accordance with PIA Standard Operating Procedures (SOPs) for Northern Area flights where minimum separation of 2,000 ft Above Ground Level (AGL) is allowed and considered mandatory due to mountainous terrain. While approaching Gilgit Airport, Captain initiated the descent at 02:36:37 h at the designated point but maintained a higher speed accelerating up to 245 kt as opposed to the standard descent speed of 200 kt as per PIA SOPs. Despite being earlier than planned Estimated Time of Arrival (ETA) for Gilgit Airport, the Captain still elected to maintain higher speeds. The FO pointed out the anomaly of higher-than-normal speed, but Captain did not take any action to bring the aircraft to correct parameters. Moreover, the Enhanced Ground Proximity Warning System (EGPWS) warning also triggered at 02:45:10 h due to higher speeds as the aircraft descended into the valley for Approach. The Approach is mandatorily as per Visual Flight Rules (VFR) whereby the aircrew is to remain visual all the time with the terrain. As Gilgit Airport is located in a valley, Approach for Landing is a visual approach whereby the aircraft executes a base turn to align with the R/W for Landing after Approaching almost perpendicular to the R/W on base leg. This is because a standard Approach is not possible due to the presence of mountains all around. During base leg, at 02:48:54 h Captain announced tail wind picking up, whereas Gilgit Airport was reporting wind as calm. As per data available, the tail wind speed above 1,500 ft AGL was as high as 19 kt; however, it started to reduce progressively with decrease of altitude whereby it reduced to 4-5 kt upon touchdown. Due to high speed maintained by the Captain, the aircraft could not be brought to correct Landing configuration even during base leg. At 02:49:11 h, the Captain asked the FO’s opinion for carrying out a 360° turn to reduce the speed for Landing configuration. However, the FO left the decision to the Captain as, in his opinion, the speed was too high for executing the turn inside the valley. Moreover, as the Captain was more experienced and also his instructor, he trusted the Captain’s judgment and skill to make a successful Landing. Since the FO did not give any opinion on the Captain’s suggestion for a 360° turn, the Captain continued the Approach. As the aircraft continued towards the R/W, Flaps were selected to 15° below 180 kt and 491 ft AGL. Landing Gears (L/G) were lowered immediately after Flaps at 442 ft AGL and speed 174 kt instead of correct speed of 170 kt. Additionally, the Captain made an angling Approach to the R/W instead of executing a correct base turn as per procedure which describes a semi-circular arc. The Flaps came down to 15° position at 257 ft AGL whereas the L/G were in down and locked position only once the aircraft was rolling out on R/W heading at an altitude of approximately 50 ft AGL at a speed of 162-163 kt. Full Flaps could not be lowered and aircraft touched down on the R/W at time 02:47:50 h at approximately 150 kt in Flaps 15° configuration around 2,000 ft down the R/W. After touchdown, the Captain applied brakes, but without using Thrust Reversers. However, aircraft could not be stopped after the Landing Roll and departed from the far end of the R/W coming to a stop at 41 ft from the R/W threshold.
Probable cause:
Primary Causes:
- Involuntary runway excursion due to an intentional high-speed approach and landing by the pilot-in-command (PM).
- Failure to adhere to SOP's.
- Lack of situational awareness and anticipation resulting in inadequate decision making.
Contributing Factors:
- Lack of assertiveness by the pilot-in-command (PM).
- Inadequate application of Crew Resources Management (CRM).
Final Report:

Crash of a Cessna 404 Titan II in Moroni

Date & Time: Jul 18, 2019
Type of aircraft:
Operator:
Registration:
D6-FAT
Flight Phase:
Survivors:
Yes
Schedule:
Moroni - Mohéli
MSN:
404-0216
YOM:
1978
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Moroni-Prince Saïd Ibrahim-Hahaya Airport, while climbing, the pilot encountered an unexpected situation and apparently attempted an emergency landing when the twin engine airplane struck the ground past the runway end and came to rest inverted. All 11 occupants were evacuated, a passenger and the pilot were injured. The aircraft was partially destroyed by a post crash fire.

Crash of a Cessna 208B Grand Caravan in Bethel

Date & Time: Jul 8, 2019 at 1505 LT
Type of aircraft:
Operator:
Registration:
N9448B
Survivors:
Yes
Schedule:
Newtok – Bethel
MSN:
208B-0121
YOM:
1988
Flight number:
GV262
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2258
Captain / Total hours on type:
787.00
Aircraft flight hours:
21206
Circumstances:
The commercial pilot was conducting a visual flight rules scheduled passenger flight with five passengers. During the return leg to the company’s base airport, the pilot requested, and was given clearance to, a short gravel runway of 1,858 ft that terminated at parallel cross-runways and had inbound airplanes. The wind was reported as variable at 3 knots, and the outside air temperature was 88°F which was 25° warmer than usual. The pilot stated that he conducted a steeper than normal approach and performed a normal 30° flap landing flare; however, the airplane floated halfway down the runway. He initiated a go-around by advancing the throttle to takeoff power and retracting the flaps to 20° as the main landing gear briefly touched down. Automatic dependent surveillance-broadcast (ADS-B) data indicated that the airplane arrived 0.1 mile from the runway threshold at 149 ft above ground level (agl) and 110 knots of ground speed, which was 32 knots faster than the short field landing approach speed listed in the pilot operating handbook. A witness in the air traffic control tower (the ground controller) stated that the airplane “bled off a lot of airspeed,” during the landing attempt and climbed out in a very flat profile. The tower local controller stated that after liftoff, the airplane’s right wing dropped and the airplane appeared to be turning right into conflicting landing traffic, so he twice instructed the airplane to “left turn out immediately.” The pilot stated that he attempted to comply with the tower controller’s instruction, but when he applied left aileron, the airplane appeared to stall, rolled rapidly right, and descended in a right-wing-low attitude. It subsequently impacted the surface between runways. A postimpact fire ensued, and the pilot helped the passengers egress. The airplane was destroyed by postimpact fire. Given the evidence, it is likely that the pilot decided to land on the short runway to expedite the arrival and did not perform an appropriate short field landing approach, which resulted in excessive airspeed and altitude over the runway threshold, a long landing flare, rapid deceleration, and a self-initiated go-around from a slow airspeed. Had the pilot initiated the go-around as he approached the runway with indications of an unstable visual approach, the airspeed would have been well above stall speed, which would have allowed for the desired positive climb out on runway heading. The pilot likely attempted to comply with the tower local controller’s urgent commands to turn while the airplane was near the limit of performance (the temperature was about 25 degrees warmer than average, which would have resulted in a higher density altitude than the pilot was accustomed to and degraded aircraft and engine performance). The pilot’s maneuvering resulted in the exceedance of the critical angle-of-attack of the high wing (right wing) during the left turn, and an aerodynamic stall.
Probable cause:
The pilot’s failure to maintain adequate airspeed while maneuvering during an attempted go around, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall at low altitude. Contributing to the accident, was the pilot’s decision to perform an approach to a short runway at an excessive airspeed and his late decision to perform a go-around, which resulted in a slow climb at a reduced safe margin above stall airspeed.
Final Report:

Crash of a Boeing 737-85R in Mumbai

Date & Time: Jul 1, 2019 at 2351 LT
Type of aircraft:
Operator:
Registration:
VT-SYK
Survivors:
Yes
Schedule:
Jaipur - Mumbai
MSN:
30410/1228
YOM:
2002
Flight number:
SG6237
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
160
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5355
Captain / Total hours on type:
5113.00
Copilot / Total flying hours:
4826
Copilot / Total hours on type:
4625
Circumstances:
On 01.07.2019, B737-800 aircraft was involved in an accident (runway excursion) at Mumbai airport while landing in moderate to heavy rain. The aircraft was under the command of an ATPL holder (PF) with a CPL holder as First Officer (PM). There were 160 passengers and 7 crew members on board. There was no injury to any of the passengers or crew members. The aircraft suffered substantial damage. The subject flight was fifth of the day for the aircraft and second for the flight crew. The flight crew had earlier operated Mumbai-Jaipur sector and the incident flight was from Jaipur to Mumbai. There were no technical issues reported by the flight crew either during Mumbai Jaipur sector or on the return leg (Jaipur- Mumbai) till descent into Mumbai. The pilots had carried out briefing amongst themselves for the approach including the weather and Go Around actions, if required. The aircraft commenced descent into Mumbai in the late evening hours. As per the reported weather at the time of approach visibility was 2100 metres in rain making it dark. Reported winds were 090/12 Knots. Runway was wet and the trend provided was ³temporary reduction in visibility to 1500 metres with thunder/ showers of rain´. During descend at approximately 7000' Pressure Altitude, the crew observed an indication for IAS disagree, indicating a discrepancy of airspeed between the instrument sources for the flight crew. Although this indication was momentary, the 'Non-Normal Checklist' was carried out. The indication discrepancy did not recur for the remainder of the flight. The aircraft was radar vectored for an ILS approach for Runway 27 at Mumbai. The approach was stabilized by 3800' Pressure Altitude with landing gear down, flaps 30 and auto brake selected at 3. The autopilot was engaged throughout the descent phase and during approach, the second autopilot was also coupled for the ILS approach. At 100', the autopilot and the auto-throttle were disengaged by the PF. The flare manoeuvre consumed approximately 5807' of the runway length prior to the aircraft touchdown with 3881' of runway remaining. After touchdown, the speed brakes deployed automatically and maximum reverse thrust and wheel brakes were applied. The aircraft exited the paved surface at 65 Knots and came to rest at a distance of 615' beyond the end of the runway. Once the aircraft came to rest, the flight crew advised cabin crew to be at their stations. The pilots were unable to contact ATC through VHF communication. The PF contacted his airline personnel using mobile phone and informed that the aircraft had overrun the runway and requested for step ladders. The ATC activated fire services and the runway was closed for operation. The Cabin crew carried out check on the passengers in the cabin. The fire services reached the aircraft location and verbal communication was established with the flight crew once the cockpit window was opened. Two Fire Services personnel boarded the aircraft from the L1 door using a fire ladder. An assessment of the aircraft structure and occupants was made and the fire services personnel informed the cabin crew that deplaning was to be carried out using fire ladders. There were no injuries during evacuation or otherwise.
Probable cause:
The runway excursion occurred because of combination of:
- Disconnection of auto pilot at an altitude 118' RA with the nose up trim bias without adequate compensation.
- Disconnection of auto throttle at 118' RA at a higher thrust setting for that phase of flight.
- Late touchdown of the aircraft on the runway.
- Reduced visual cues due to heavy rain impacting depth perception and ascertaining of actual touchdown position.
- Tailwind conditions at the time of landing resulting In increasing the distance covered during the extended flare (float).
- Approach with lower flaps (30) than recommended (40).
Final Report:

Crash of an Antonov AN-24RV in Nizhneangarsk: 2 killed

Date & Time: Jun 27, 2019 at 1025 LT
Type of aircraft:
Operator:
Registration:
RA-47366
Survivors:
Yes
Schedule:
Ulan-Ude - Nizhneangarsk
MSN:
7 73 108 04
YOM:
1977
Flight number:
AGU200
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
43
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
15167
Captain / Total hours on type:
10667.00
Copilot / Total flying hours:
6012
Copilot / Total hours on type:
1325
Aircraft flight hours:
38014
Aircraft flight cycles:
18584
Circumstances:
On a flight from Ulan-Ude to Nizhneangarsk, while descending to an altitude of 3,050 metres about 30 km from the destination airport, the crew contacted ATC and reported the failure of the left engine. The approach was continued to runway 22. After touchdown, the crew initiated the braking procedure when the airplane deviated to the right then veered off runway. It rolled in a grassy area, went through the perimeter fence and eventually impacted the building of a sewage treatment plant located 380 metres to the right of the runway centerline. The airplane was destroyed by a post crash fire. The captain and the flight engineer were killed while the copilot was seriously injured. 10 other occupants were injured.
Probable cause:
The accident occurred during landing with one engine inoperative as a result of a longitudinal-lateral rollout beyond the runway and subsequent collision with a building outside the aerodrome, resulting in damage to the aircraft structure and a fire. The landing was performed on a runway with an available landing distance of 1,503 metres that was significantly less than the distance required of 2,160 metres for the actual conditions.
Most likely, the accident was the result of the combination of the following factors:
- The decision by the pilot-in-command (pilot flying) to land without calculating the required landing distance;
- The incorrect choice by the pilot-in-command of the type and trajectory of the approach, which made it impossible to reduce the flight speed in time. Instead of visual maneuvering ('circle-to-land' maneuver) provided for in the approach pattern and agreed upon by the crew with the air traffic controller, the crew performed a visual approach;
- The absence in the airline's flight manual and the aircraft's flight manual of procedures for performing a visual approach maneuver ('circle-to-land' maneuver);
- Failure of the crew to take measures to go around for a second approach despite a significant discrepancy between the actual flight parameters and the criteria for a stabilized approach specified in the airline's flight procedures;
- Lack of crew coordination and cross-checking;
- Failure to follow a number of standard operating procedures in terms of informing the PIC (pilot in command) by other crew members about significant deviations of actual flight parameters from the published values;
- Insufficient crew resource management;
- Landing at a significant high speed (275 km/h instead of the recommended 220 km/h), which led the aircraft to land 530 metres pas the runway threshold;
- Incorrect use of the main landing gear wheel braking system by the crew, resulting in premature compression of the brake pedals (in the air), which, upon repeated contact, led to landing on the braked wheels of the right main landing gear with destruction of the tires and, subsequently, to the aircraft rolling sideways;
- Increased psychological and emotional stress on the part of the captain, compounded by his particular mental characteristics, contributed to the adoption of unreasonable decisions in the situation that had arisen.
- The left engine failed in flight due to abnormal operation of the fuel control system, probably the ADT-24. Due to the high degree of destruction of the system due to fire, it was not possible to definitively determine which unit failed and the cause of the failure. The abnormal adjustments of the left engine and deviations in the operation of its fuel control system manifested themselves long before the day of the accident and could have been detected by both flight and engineering personnel.
Final Report:

Crash of a De Havilland DHC-2 Beaver off Metlakatla: 2 killed

Date & Time: May 20, 2019 at 1556 LT
Type of aircraft:
Operator:
Registration:
N67667
Survivors:
No
Schedule:
Ketchikan – Metlakatla
MSN:
1309
YOM:
1959
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1623
Captain / Total hours on type:
20.00
Aircraft flight hours:
29575
Circumstances:
The commercial pilot was conducting his first scheduled commuter flight from the company’s seaplane base to a nearby island seaplane base with one passenger and cargo onboard. According to company pilots, the destination harbor was prone to challenging downdrafts and changing wind conditions due to surrounding terrain. Multiple witnesses at the destination stated that the airplane made a westerly approach, and the wind was from the southeast with light chop on the water. Two witnesses reported the wings rocking left and right before touchdown. One witness stated that a wind gust pushed the tail up before the airplane landed. A different witness reported that the airplane was drifting right during the touchdown, and another witness saw the right (downwind) float submerge under water after touchdown, and the airplane nosed over as it pivoted around the right wingtip, which impacted the water. Flight track and performance data from the cockpit display units revealed that, as the airplane descended on the final approach, the wind changed from a right headwind of 6 knots to a left quartering tailwind of 8 knots before touchdown. The crosswind and tailwind components were within the airplane’s operational limitations. Examination of the airframe, engine, and associated systems revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation or egress. During the final approach and descent, the pilot had various wind information available to him; the sea surface wind waves and signatures, the nearest airport observation winds, the cockpit display calculated wind, and the visual relative ground speed. Had the pilot recognized that the winds had shifted to a quartering tailwind and the airplane’s ground speed was faster than normal, he could have aborted the landing and performed another approach into the wind. Although crosswind landings were practiced during flight training, tailwind landings were not because new pilots were not expected to perform them. Although the crosswind component was well within the airplane’s limits, it is possible that combined with the higher ground speed, the inexperienced pilot was unable to counteract the lateral drift during touchdown in a rapidly shifting wind. The pilot was hired the previous month with 5 hours of seaplane experience, and he completed company-required training and competency checks less than 2 weeks before the accident. According to the chief pilot (CP), company policy was to assign newly hired pilots to tour flights while they gained experience before assigning them to commuter flights later in the season. The previous year, the CP distributed a list of each pilot’s clearances for specific types of flights and destinations; however, an updated list had not been generated for the season at the time of the accident, and the flight coordinators, who were delegated operational control for assigning pilots to flights, and station manager were unaware of the pilot’s assignment limitations. Before the flight, the flight coordinator on duty completed a company flight risk assessment that included numerical values based on flight experience levels. The total risk value for the flight was in the caution area, which required management notification before releasing the flight, due to the pilot’s lack of experience in the accident airplane make and model and with the company, and his unfamiliarity with the geographical area; however, the flight coordinator did not notify management before release because the CP had approved a tour flight with the same risk value earlier in the day. Had the CP been notified, he may not have approved of the pilot's assignment to the accident flight. The pilot's minimal operational experience in seaplane operations likely affected his situational awareness in rapidly changing wind conditions and his ability to compensate adequately for a quartering tailwind at a higher-than-normal ground speed, which resulted in a loss of control during the water landing and a subsequent nose-over.
Probable cause:
The pilot’s inadequate compensation for a quartering tailwind during a water landing, which resulted in a loss of control and subsequent nose-over. Contributing to the accident was the company’s inadequate operational control of the flight release process, which resulted in assignment of an inexperienced pilot to a commuter seaplane flight.
Final Report:

Crash of a De Havilland Dash-8-Q402 in Yangon

Date & Time: May 8, 2019 at 1852 LT
Operator:
Registration:
S2-AGQ
Survivors:
Yes
Schedule:
Dhaka - Yangon
MSN:
4367
YOM:
2011
Flight number:
BG060
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9646
Captain / Total hours on type:
1474.00
Copilot / Total flying hours:
580
Copilot / Total hours on type:
405
Aircraft flight hours:
8115
Circumstances:
The route of the aircraft on that day was DAC-RGN-DAC. At (18:03) the Bombardier DHC-8-402 aircraft, registered (S2-AGQ) contacted Yangon control tower and at (18:16) had ILS established and reported to the Yangon control tower. Due to adverse weather, Yangon control tower asked them to execute a go-around and the aerodrome operations was closed for the aviation safety for 2 hours. When the weather condition got better, the aerodrome operations was opened. And then the DHC-8-402 aircraft, registered S2-AGQ made RNP approach because only localizer was available at that moment. While the Bombardier DHC-8-402 aircraft was and making approach to runway 21, it was a bit higher than on slope 3 degree and landed on runway 21, remaining on the ground for upwards of 7 seconds, but the aircraft ran parallel to the runway, and then it flew up in the air up to 44 ft above the ground and sank again and collided with runway 03 and slid forward out of the runway and came to a complete stop on the over-run of the runway 03. There was no fire. All gears were collapsed and fuselage was broken into three sections. All 33 occupants were evacuated, among them 20 were injured. The aircraft was destroyed.
Probable cause:
While the aircraft was unstabilized on approach, the pilot did not execute a go-around.
Final Report:

Crash of a Sukhoi Superjet 100-95B in Moscow: 41 killed

Date & Time: May 5, 2019 at 1830 LT
Type of aircraft:
Operator:
Registration:
RA-89098
Survivors:
Yes
Schedule:
Moscow - Murmansk
MSN:
95135
YOM:
2017
Flight number:
SU1492
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
73
Pax fatalities:
Other fatalities:
Total fatalities:
41
Captain / Total flying hours:
6801
Captain / Total hours on type:
1570.00
Copilot / Total flying hours:
774
Copilot / Total hours on type:
624
Aircraft flight hours:
2710
Aircraft flight cycles:
1658
Circumstances:
On May 05, 2019 the Aeroflot, PJSC flight crew out of the PIC and F/O was performing the SU-1492 scheduled passenger flight en route from Sheremetyevo airport (UUEE) to Murmansk airport (ULMM) aboard the RRJ-95B RA-89098 aircraft. 3 cabin crew members were also indicated in the flight assignment. The crew arrived to the airport at about 2 hrs prior to departure. After having undergone the mandatory preflight procedures (the medical check, briefing etc) the crew took up their duties at the flight deck. The passengers boarding was proceeded through the left front door. By 14:40 all the passenger and baggage holds doors had been closed. At 14:45:30 the ATC officer approved the engines start up. At 14:50:15 the crew initiated taxiing. At 14:57:20, after having been issued the clearance, the crew lined up at RWY 24C, where held the position for about 5 min. At 15:02:23 the ATC officer issued clearance for takeoff. After takeoff at 15:03:36 at the QNH altitude of 1250 ft. (380 m), the radio altitude of 690 ft. (210 m) and the IAS of 160 kt (296 km/h) the A/P was engaged. At 15:03:56 the Sheremetyevo Radar ATC officer cleared the climb to the QFE 1200 m altitude as per the KN 24E SID. At 15:05:18 the Sheremetyevo Radar ATC officer instructed the crew to climb to FL60. At 15:05:33 the crew set QNE of 760 mm of mercury/1013 hPa. At 15:06:57 the Sheremetyevo Radar ATC officer instructed the crew to climb to FL70 and contact the Approach ATC. After having initiated the contact with the Approach ATC officer the crew was instructed to climb to FL90. Between 15:07:30 and 15:07:33 the dialogue as follows was recorded in the crew: PIC: «It is going to bump now», – F/O: «Crap», – PIC: «That's all right». At 15:07:34 the Approach ATC officer instructed to climb to FL100. At 15:08:03 the Approach ATC officer instructed to climb to FL110. After the F/O confirmed this instruction the CVR recorded the noise effect of 1.5 sec. duration, starting from 15:08:09.7. Most probably at that point the aircraft encountered the atmospheric electricity strike. At 15:08:11.9 the A/P was disconnected, accompanied by the respective sound warning, as well as by the reversion of the FBWCS to DIRECT MODE with the DIRECT MODE. DIRECT MODE synthetic voice triggered. The A/T continued to operate. The aircraft at that moment was proceeding flight in right roll of about 20°, passing FL89 (2700 m) in climb. From 15:08:16 the manual control from the left duty station was initiated. The aircraft was proceeding the right turn as per the KN 24E SID and climb. At 15:08:47 the A/T was disconnected with the «override» (the TLA was changed from ~ 29.5° to ~ 19°). The further flight was continued by a manual control at the FBWCS DIRECT MODE. At 15:09:17 the aircraft was pulled out of the right turn to a heading of about 60°. After a short discussion in the crew the PIC made the decision to return to the departure aerodrome and commanded the F/O to declare PAN–PAN (an urgency signal). After several unsuccessful attempts to establish contact with the ATC officer at the operating frequency with the use of VDR 1 (this radio unit was used for communications from the beginning of the flight), at 15:09:32, after discussion, the 7600 squawk code was set by the crew. At 15:09:35, the radio communication was resumed on the emergency frequency (121.5 MHz) with the use of VDR 2. After radio communication was restored, at 15:09:39, the F/O reported to the Approach ATC officer: «Moscow Approach, and we request return 14 -92, radio contact lost and aircraft in DIRECT MODE». The ATC officer instructed to descend to FL80. The maximum altitude the aircraft reached was 10600 ft. (3230 m) QNE. The crew replied: «Aeroflot 14-92, heading 0-57, descending 8-0». The flight further on until glideslope interception was proceeded by vectoring. At 15:24:38 to the ATC request on the approach type for landing the crew advised that it would be an ILS approach. At 15:26:30 the crew set the 7700 squawk code. The reason for setting was not reported to the ATC. At 15:27:20 the glideslope descent was initiated. At 15:27:51 the ATC officer relayed the weather information to the crew and cleared landing: «Aeroflot 14-92 surface wind 160 7, gusts 10 meters per second, runway 24L, cleared for landing». At 15:30:00 at the distance of ≈ 900 m off the RWY entry threshold and at IAS of 158 kt (293 km/h) there occurred the RWY first touchdown. The touchdown occurred practically on «three points», with the vertical acceleration of not less than 2.55G with a subsequent aircraft separation/bounce off the RWY. Another touchdown occurred in 2.2 sec. after the first one at the IAS of 155 kt (287 km/h). The touchdown occurred with the advancement on the NLG. Vertical acceleration amounted to not less than 5.85G. There occurred another aircraft bounce off the RWY. At 15:30:06 at the IAS of 140 kt (258 km/h) the third touchdown occurred with the vertical acceleration of not less than 5G. As a consequence of hard touchdowns the MLG legs and the airframe structural elements were destroyed with the fuel spillage and the subsequent onset of fire. Into the further movement of the aircraft there occurred its RWY veering off to the left. At 15:30:38 the airplane stopped. The aircraft stop occurred on the soil between TWY2 and TWY3 at the point with the reference position 55°58′06.20″ N, 37°24′07.20″ E, ∆h = 185 m, with true heading ≈ 128°. The distance off the RWY 24L entry threshold amounted to ≈ 2720 m, lateral deviation was about 110 m to the left off the RWY 24L centerline.
Probable cause:
The air accident to the RRJ-95B RA-89098 aircraft was caused by the uncoordinated control inputs by the PIC at the flare, landing and through the several repeated bounces of the aircraft off the RWY (the porpoising), having manifested in the several disproportionate alternating sidestick inputs in pitch with keeping the sidestick retained against each stop. The indicated control inputs had resulted in three hard touchdowns of the aircraft, as a consequence at the second and third touchdowns the absorbed energy significantly exceeded the maximum values, for which the structural integrity had been evaluated at the aircraft type certification, which led to the destruction of the airframe structural elements, the fuel tanks with the fuel spillage and the fire onset.
The contributing factors to the accident were:
- The ineffectiveness of the RRJ-95 flight personnel approved training programs as for the actions into the major failure condition//abnormal situation at the FBWCS reversion to DIRECT MODE and, consequently, the insufficient knowledge and skills at the flight crew members to operate the airplane in this mode. The training programs met the minimum requirements, determined by FAR, but did not account for the specific nature of a particular emergency;
- The ineffectiveness of the airline SMS in terms of the monitoring of the piloting sustainable skills development at the pilots, which prevented the identification and elimination of the PIC’s common systematic errors at the sidestick pitch control at the stage of landing, including these, associated with its forward inputs beyond neutral (to nose down) into the flare;
- The failure to identify the biases (hazards) in the airline flight crews’ piloting technique as far the previous events of the FBWCS reversion to DIRECT MODE are concerned and thus the failure to implement preventive measures;
- The aircraft operational documentation unclear wording in terms of the piloting peculiarities at flare and the correction of the deviations at the landing (counteracting the consecutive aircraft separations off the RWY);
- The failure of the crew to comply to the FAR and OM requirements at the flight preparation and performance at the actual and forecast thunderstorm activity, as well as at the availability to observe these zones on the weather radar display, which had resulted in the aircraft encounter the atmospheric electricity, the EIUs reboot and the FBWCS reversion to DIRECT MODE. As per the certification results the FBWCS reversion to DIRECT MODE had been assessed as «the major failure condition», the in-flight onset of «the major failure condition» at the lightning or static electricity exposure does not contradict the applicable certification requirements;
- The dramatic increase of the psycho emotional stress at the PIC because of the aircraft exposure to atmospheric electricity and the failure within a long time to ensure the acceptable piloting precision at the FBWCS in DIRECT MODE, which led to the psychological dominant mindset formation to perform immediate landing together with the lack of readiness to initiate go around (not go-around minded);
- Psychological personality traits of the flight crew members that determine their behavior in the stress environment, as well as the PIC’s insufficient training in human factor/performance and threat and error management approach, which prevented the objective assessment of his psycho emotional condition and the ability to control the airplane, to choose the optimal strategy to proceed the flight, as well as to establish the required interaction and CRM;
- The failure of the PIC to ensure the aircraft pitch trim under the manual control, including at the glideslope descent;
- The incorrect assessment of the situation by the crew at the Predictive Windshear warning (GO AROUND WINDSHEAR AHEAD) trigger at the flight on glideslope and, consequently, the non-initiation of a go-around maneuver, that resulted in the aircraft encounter the wind microburst at the early flare and affected the aircraft flight path. The documentation by the aircraft designer and the airline allows the crew to ignore the subject warning activation, if it made sure there is «no windshear threat», still the operational documentation and the OM do not integrate the respective clear criteria of «no threat»;
- The purposeful ducking under the glideslope by the PIC at the final approach (after passing DH);
- The difference between the airline OM provisions as for the crew actions at the glideslope warning activation (the excessive deviation off the glideslope equisignal zone) and the similar provisions in the aircraft designer documentation. Subject to the provisions of the aircraft designer documentation the crew should have performed go-around;
- The unjustified extension by the airline of the approach «stabilized condition» criteria as for the acceptable deviations range off the target speed, which at the actual IAS of 15 kt higher against the target one and the FBWCS in DIRECT MODE resulted in the unexpected for the PIC increased aircraft response to the sidestick input in pitch;
- The failure by the crew to carry out the SOP on the manual speed brakes deployment at the aircraft touchdown. The operational documentation unclear wording and the monitoring algorithms of the landing configuration, used at the aircraft that require to arm the speedbrakes for the automatic deployment, including at FBWCS in DIRECT MODE, in which the automatic deployment is disabled, degrade the crew’s situational awareness as for this aspect.
- The TR actuation after the first bounce off the RWY, which had made the subsequent go-around impossible. As per the results of the forensic medical examination the death of 40 out of 41 fatally injured people had been caused by the exposure to open flame, accompanied with the burns of the upper respiratory tract through the inhalation of hot air. The fire erupted after the aircraft third touchdown due to the disintegration of the wing fuel tanks and the fuel spillage. The fuel spillage occurred as due to the destruction at the landing gear retraction/extension actuating cylinders attachment points, as well as due to the destruction of the other wing parts. The landing gear structure had been damaged at the second touchdown that is at the third touchdown functioned beyond the expected operational conditions and had not been able to bear the applied landing loads as designed. The operation (destruction) of the landing gear fuse pins («weak links») at the second touchdown had been consistent with the design integrated logic. With that the loads, actually accomplished, had been less of those in use to demonstrate compliance to AR-25 item 25.721 at the aircraft type certification, which prevented the MLG legs to completely separate off the airplane structure (it is only the Attachment A fuse pins that had been destructed). No correlation between the certification requirements for the structure, including MLG legs structure, and the conditions for demonstrating their safe separation off results in actual significant risks of the fuel tanks disintegration and the fuel spillage even in case of compliance demonstration to every single of these requirements. At its very onset the fire by its nature had been the deflagration flash, which had been accompanied with an intense smoke release with the onset of a steady burning in two seconds. By the point of the evacuation initiation the fire had been propagated inside the cabin through a row of cabin windows at the rear fuselage along the right and left sides, with that the airworthiness standards do not set up the requirements for the cabin windows as to the external fire protection. That situation had been beyond the expected operational conditions as there had been no time margin (90 sec), at which the crew and passengers’ emergency evacuation is demonstrated at the type certification.
Most probably the following factors had contributed to the increase in the severity of the consequences:
- The running engines of the aircraft, having been not timely shut down by the crew;
- Large amount of fuel, spilling out of both wing panels, which penetrated the area of the exhaust-mixing nozzles, exposed directly to their jet streams;
- The inability to evacuate through both of the rear emergency exits;
- The manifestation of the flashover effect at the rear passenger cabin;
- The crush and panic among the passengers;
- The efforts by a number of passengers to pick up their carry-on luggage at the evacuation;
- The CFA’s error in operating the PACIS, and consequently the decline in the passengers’ situational awareness as for the evacuation procedure.
Final Report:

Crash of a Britten Norman BN-2B-27 Islander in Puerto Montt: 6 killed

Date & Time: Apr 16, 2019 at 1050 LT
Type of aircraft:
Registration:
CC-CYR
Flight Phase:
Survivors:
No
Site:
Schedule:
Puerto Montt - Ayacara
MSN:
2169
YOM:
1983
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
1414
Captain / Total hours on type:
437.00
Aircraft flight hours:
22330
Circumstances:
The twin engine airplane departed Puerto Montt-Marcel Marchant (La Paloma) Airport Runway 01 at 1050LT on a charter flight to Ayacara, carrying five passengers and one pilot. About 36 seconds after takeoff, while climbing, the pilot declared an emergency. The airplane entered a left turn then stalled and crashed onto a house located in a residential area, about 450 metres from the runway end, bursting into flames. The houses and the airplane were destroyed by a post crash fire and all six occupants were killed. One person in the house was injured.
Probable cause:
Loss of control of the airplane in flight, during a left turn, due to the failure of the right engine (n°2) during takeoff, caused by a fuel exhaustion.
The following contributing factors were identified:
- Failure of the pilot to comply with the pre takeoff checklist,
- Failure of the pilot to check the fuel selector switch and the fuel quantity prior to start the engines,
- Failure of the pilot to feather the propeller of the right engine (n°2) during an emergency situation,
- Failure of the pilot to bring the flaps to the neutral position during an emergency situation,
- Decrease of the speed and altitude of the airplane,
- Increase bank of the wing during a left turn.
Final Report:

Crash of a Boeing 737 MAX 8 near Debre Zeit: 157 killed

Date & Time: Mar 10, 2019 at 0844 LT
Type of aircraft:
Operator:
Registration:
ET-AVJ
Flight Phase:
Survivors:
No
Schedule:
Addis Ababa – Nairobi
MSN:
62450/7243
YOM:
2018
Flight number:
ET302
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
149
Pax fatalities:
Other fatalities:
Total fatalities:
157
Captain / Total flying hours:
8122
Captain / Total hours on type:
1417.00
Copilot / Total flying hours:
361
Copilot / Total hours on type:
207
Aircraft flight hours:
1330
Aircraft flight cycles:
382
Circumstances:
On March 10, 2019, at 05:38 UTC, Ethiopian Airlines flight 302, Boeing 737-8(MAX), ET-AVJ, took off from Addis Ababa Bole International Airport bound to Nairobi, Kenya Jomo Kenyatta International Airport. ET302 was being operated under the provisions of the Ethiopian Civil Aviation Regulations (ECARAS) as a scheduled international flight between Addis Ababa Bole International Airport (HAAB), Ethiopia and Jomo Kenyatta Int. (HKJK) Nairobi, Kenya. It departed Addis Ababa with 157 persons on board: 2 flight crew (a Captain and a First Officer), 5 cabin crew and one IFSO, 149 regular passengers. At 05:36:12 the Airplane lined up on runway 07R at field elevation of 7,656 ft with flap setting of 5 degrees and a stabilizer trim setting of 5.6 units. Both flight directors (F/D) were ON with LNAV and VNAV modes armed. At 05:37:17the F/O reported to Tower ready for takeoff and at 05:37:36ATC issued take off clearance to ET-302 and advised to contact radar on 119.7MHz. The takeoff roll and lift-off was normal, including normal values of left and right angle-of-attack (AOA). During takeoff roll, the engines stabilized at about 94% N1. Shortly after liftoff, the left Angle of Attack sensor recorded value became erroneous and the left stick shaker activated and remained active until near the end of the recording. In addition, the airspeed and altitude values from the left air data system began deviating from the corresponding right side values. The left and right recorded AOA values began deviating. Left AOA decreased to 11.1° then increased to 35.7° while the right AOA indicated 14.94°. Then after, the left AOA value reached 74.5° in ¾ seconds while the right AOA reached a Maximum value of 15.3°, the difference between LH and RH AOA was59°and near the end of the recording it was 490. At 05:39:30, the radar controller identified ET-302 and advised to climb FL 340 and when able to turn right direct to RUDOL. At 5:39:51, the selected heading increased from 072° to 197°. After the flaps were fully retractedthe1stautomatic nose-down trim activated and engaged for 9 seconds positioning the stabilizer trim to 2.1 units. The pilot flying pulled to pitch up the Airplane with a force more than 90lbs. He then applied electric trim-up inputs. Five seconds after the end of these inputs a second automatic nose-down trim activated. At 5:40:22, the second automatic nose-down trim activated. Following nose-down trim activation GPWS DON’T SINK sounded for 3 seconds and “PULL UP” also displayed on PFD for 3 seconds. At 05:40:43, approximately five seconds after the end of the crew manual electrical trim up inputs, a third automatic trim nose-down was recorded but with no associated movement of the stabilizer. At 05:40:50, the captain told the F/O: “advise we would like to maintain one four thousand. We have a flight control problem”. The F/O complied and the request was approved by ATC. Following the approval of the ATC, the new target altitude of 14,000ft was set on the MCP. The Captain was unable to maintain the flight path and requested to return back to the departure airport. At 05:43:21, approximately five seconds after the last main electric trim up input, an automatic nose-down trim activated for about 5s. The stabilizer moved from 2.3 to 1 unit. The rate of climb decreased followed by a descent in 3s after the automatic trim activation. One second before the end of the automatic trim activation, the average force applied by the crew decreased from 100 lbs to 78 lbs in 3.5 seconds. In these 3.5 seconds, the pitch angle dropped from 0.5° nose up to -7.8° nose down and the descent rate increased from -100 ft/min to more than -5,000 ft/min. Following the last automatic trim activation and despite calculated column force of up to 110lbs, the pitch continued decreasing. The descent rate and the airspeed continued increasing between the triggering of the 4th automatic trim activation and the last recorded parameter value. At the end of the flight, Computed airspeed values reached 500Kt, Pitch values were greater than 40° nose down and descent rate values were greater than 33,000 ft/min. Finally, both recorders stopped recording at around 05 h 43 min 44s. At 05:44 The Airplane impacted terrain 28 NM South East of Addis Ababa near Ejere (located 8.8770 N, 39.2516 E.) village at a farm field and created a crater approximately 10 meters deep (last Airplane part found) with a hole of about 28 meters width and 40 meters length. Most of the wreckage was found buried in the ground; small fragments of the Airplane were found scattered around the site in an area by about 200 meters width and 300 meters long. The damages to the Airplane were consistent with a high energy impact. All 157 persons on board: 2 flight crew (a Captain and a First Officer), 5 cabin crew and one IFSO, 149 regular passengers were fatally injured.
Probable cause:
Repetitive and uncommanded airplane-nose-down inputs from the MCAS due to erroneous AOA input, and its unrecoverable activation system which made the airplane dive with the rate of -33,000 feet per minute close to the ground was the most probable cause of the accident.
The following contributing factors were identified:
1. The MCAS design relied on a single AOA sensor, making it vulnerable to erroneous input from the sensor;
2. During the design process, Boeing failed to consider the potential for uncommanded activation of MCAS, but assumed that pilots would recognize and address it through normal use of the control column, manual electric trim, and the existing Runaway Stabilizer NNC. The OMB and Emergency AD issued after the Lion Air accident included additional guidance but did not have the intended effect of preventing another MCAS-related accident;
3. While Boeing considered the possibility of uncommanded MCAS activation as part of its FHA, it did not evaluate all the potential alerts and indications that could accompany a failure leading to an uncommanded MCAS;
4. The MCAS contribution to cumulative AOA effects was not assessed;
5. The combined effect of alerts and indications that impacted pilot’s recognition and procedure prioritization were not evaluated by the Manufacturer;
6. Absence of AOA DISAGREE warning flag on the flight display panels (PFD);
7. The B737 MAX Crew difference CBT training prepared by Boeing and delivered to Pilots did not cover the MCAS system;
8. Failure by the manufacturer to design simulator training for pilots with regards to safety critical systems like MCAS with catastrophic consequences during undesired activation.
9. The manufacturer failed to provide procedures regarding MCAS operation to the crew during training or in the FCOM;
10. Failure by the manufacturer to address the safety critical questions raised by the airline which would have cleared out crew confusion and task prioritization;
Final Report: