Country

Crash of a Sukhoi Superjet 100-95LR near Bokovo-Akulovo: 3 killed

Date & Time: Jul 12, 2024 at 1500 LT
Type of aircraft:
Operator:
Registration:
RA-89049
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Lukhovitsy - Moscow
MSN:
95078
YOM:
2014
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The airplane departed Lukhovitsy-Tretyakovo Airport at 1452LT on a ferry flight to Moscow-Vnukovo Airport, carrying a crew of three. About eight minutes after takeoff, it entered an uncontrolled descent and crashed in an almost vertical attitude in a dense wooded area located near the village of Bokovo-Akulovo, some 37 km northwest of Tretyakovo Airport. The airplane disintegrated on impact and all three crew members were killed. The airplane was ferried back to Moscow following a maintenance program at Tretyakovo Airport.

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 Sukhoi Superjet 100-95B in Yakutsk

Date & Time: Oct 10, 2018 at 0321 LT
Type of aircraft:
Operator:
Registration:
RA-89011
Survivors:
Yes
Schedule:
Ulan-Ude - Yakutsk
MSN:
95019
YOM:
2012
Flight number:
SYL414
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
87
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13125
Captain / Total hours on type:
1080.00
Copilot / Total flying hours:
3200
Copilot / Total hours on type:
1300
Aircraft flight hours:
8115
Aircraft flight cycles:
3320
Circumstances:
Following an uneventful flight from Ulan-Ude, the crew initiated the approach to Yakutsk-Platon Oyunsky Intl Airport Runway 23L. Due to work in progress, the runway 05R threshold was displaced by 1,150 metres, reducing the landing distance to 2,248 metres for the runway 23L on which the touchdown zone lighting system was unserviceable. On approach, the crew was informed by ATC that the friction coefficient was 0,45. The crew completed the landing on runway 23L with a slight tailwind component of 4 knots and started the braking procedure. Unable to stop within the remaining distance, the aircraft overran, entered the construction area and collided with the junction of a concrete section under reconstruction, causing both main landing gear to collapse (the left main gear was torn off). The aircraft slid for another 250 metres before coming to rest. All 92 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The cause of the aviation accident with the RRJ 95B RA-89011 aircraft when landing at night with one deactivated thrust reverser was the transfer to the crew of incorrect information about the value of the friction coefficient, which led to the landing on an icy runway, the average normative friction coefficient which was less than 0.3, which did not allow landing in accordance with current regulations. This led to a significant increase in landing distance, rolling the aircraft out of the runway and collision with the junction of the reconstructed section of the runway with a height of about 0.4 m, which led to the destruction of the main landing gear supports and damage to the engines with fuel leakage without causing a fire.
The contributing factors were the following:
- Absence of a connecting ramp (which was not envisaged by the reconstruction project) between the current and the part of the runway being reconstructed;
- inefficiency of the SMS of Yakutsk Airport JSC in terms of identification and control of risks associated with the possibility of ice formation at the runway, and insufficient control over the implementation of the SMS by aviation authorities;
- erroneous determination of the Xc value at the last measurement;
- inefficiency of ice removal procedure during runway cleaning due to lack of chemical reagents for ice removal and/or thermal machines at the airfield;
- lack of information from the RRJ-95LR-100 RA 89038 aircraft crew about actual rolling out of the runway, which was an aviation incident and was subject to investigation;
- failure by airport and ATC officials to take appropriate action after receiving the RRJ-95LR-100 RA-89038 low friction report from the aircraft crew.
Final Report:

Crash of a Sukhoï Superjet 100-95 on Mt Salak: 45 killed

Date & Time: May 9, 2012 at 1431 LT
Type of aircraft:
Operator:
Registration:
97004
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Jakarta - Jakarta
MSN:
95004
YOM:
2009
Flight number:
RA36801
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
41
Pax fatalities:
Other fatalities:
Total fatalities:
45
Captain / Total flying hours:
10347
Captain / Total hours on type:
1348.00
Copilot / Total flying hours:
3318
Copilot / Total hours on type:
625
Aircraft flight hours:
843
Aircraft flight cycles:
500
Circumstances:
Aircraft was performing a demo flight and left Jakarta-Halim Perdanakasuma Airport at 1400LT with 41 passengers (potential buyers) on board and a crew of four. About thirty minutes later, while turning around Mount Salak, pilots received the authorization to descend from 10,000 feet to 6,000 feet in low visibility. Aircraft hit the edge of a cliff and crashed few yards further and was totally destroyed by impact and post impact fire. SAR teams arrived on scene 18 hours later and all 45 occupants were killed. At the time of the accident, weather conditions were marginal with clouds shrouding both Mount Salak and Mount Gede. First accident involving a Sukhoi Superjet 100. Present model was manufactured 09AUG2009 and totalized 843 flying hours for 500 cycles. Captain had 10,347 flying hours and was a test pilot by Sukhoi Civil Aircraft Company.
Probable cause:
- The flight crew was not aware of the mountainous area in the vicinity of the flight path due to various factors such as available charts, insufficient briefing and statements of the potential customer that resulted in inappropriate response to the TAWS warning. The impact could have been avoided by appropriate action of the pilot up to 24 seconds after the first TAWS warning.
- The Jakarta Radar service had not established the minimum vectoring altitudes and the Jakarta Radar system was not equipped with functioning MSAW for the particular area around Mount Salak.
- Distraction of the flight crew from prolonged conversation not related to the progress of the flight, resulted in the pilot flying not constantly changing the aircraft heading while in orbit. Consequently, the aircraft unintentionally exited the orbit.
Final Report: