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

Date & Time: Jul 19, 2019 at 1010 LT
Type of aircraft:
Operator:
Registration:
N68083
Flight Phase:
Survivors:
Yes
Schedule:
Seldovia – Anchorage
MSN:
1254
YOM:
1958
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2689
Captain / Total hours on type:
150.00
Aircraft flight hours:
29448
Circumstances:
The pilot stated that, during takeoff in the float-equipped airplane, he saw the left float begin to move into his peripheral vision from the left cockpit window and the airplane began to yaw to the left. The left wing subsequently impacted the water and the airplane nosed over, separating the right wing from the fuselage. The passengers consistently reported choppy water conditions at the time of the accident; one passenger reported that white caps were visible on the ocean waves in the distance. The passengers said that, during the takeoff, the airplane impacted a swell or wave and nosed over abruptly, and the cabin rapidly filled with water. Examination of the float assembly revealed fractures in the left front flying wire attachment fitting and the right rear flying wire attachment strap and hole elongation in the left rear flying wire attachment fitting. Additionally, the bolts attaching the two left flying wire attachment fittings to the left float were bent, and the two flying wires that had been attached to the fractured attachment fitting and attachment strap were buckled. While some areas of corrosion were observed on the fractured left forward fitting, the total area of corrosion was a small percentage of the total cross-section, and the remainder of the fracture and associated deformation of the lug was consistent with ductile overstress fracture. Similar areas of corrosion were also observed on each of the intact flying wire attachment fittings. Post-accident testing completed by the float manufacturer revealed that buckling of flying wires similar to that observed on the accident airplane was only reproduced at strap and fitting failure loads above 9,000 pounds force; the design specification load was 3,453 pounds of force. This indicates that the small amount of corrosion present on the fractured flying wire attachment fitting did not reduce its loadcarrying capability below the design specification load of 3,453 pounds of force, and that both the flying wire attachment fitting and flying wire attachment strap fractured due to overload. Therefore, it is likely that the accident airplane floats were subject to forces that exceeded their design limitations, resulting in overload of the flying wires attached to the left float. It is also likely that, given the lack of damage on either float, the force was due to impact with an ocean wave or swell and not by striking an object.
Probable cause:
The airplane's floats impact with an ocean wave or swell, which exceeded the design load specifications of the flying wire assemblies and resulted in a partial separation of the float assemblies.
Final Report:

Crash of a De Havilland DHC-2 Beaver into Mistastin Lake: 7 killed

Date & Time: Jul 15, 2019
Type of aircraft:
Operator:
Registration:
C-FJKI
Survivors:
No
Schedule:
Crossroads Lake - Mistastin Lake
MSN:
992
YOM:
1956
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
18800
Captain / Total hours on type:
16000.00
Circumstances:
The single engine airplane was chartered by a provider based in Crossroads Lake (near Churchill Falls reservoir) to fly four fisherman and two guides to Mistastin Lake, Labrador. The aircraft was supposed to leave Crossroads Lake at 0700LT but the departure was postponed to 1000LT due to low ceiling. Several attempts to contact the pilot failed during the day and the SAR center based in Trenton was alerted. SAR operations were initiated and four days later, the location of the accident was reached but only four bodies were found. The body of the pilot and two passengers were never recovered as well as the wreckage.
Probable cause:
The aircraft had been seen floating in Mistastin Lake and later sank. To date, the wreckage has not been found. There is no radar coverage at low altitudes in the area, and the aircraft was flying in uncontrolled airspace and not in communication with air traffic services. Without any witnesses and without key pieces of the aircraft, the TSB is unable to conduct a full investigation into this accident. If the aircraft is found, the TSB will assess the feasibility of investigating the accident further.
Final Report:

Crash of a BAe 3212 Jetstream 31 in Canaima

Date & Time: Jun 27, 2019 at 1130 LT
Type of aircraft:
Operator:
Registration:
YV2536
Survivors:
Yes
Schedule:
Puerto Ordaz - Canaima
MSN:
9966
YOM:
1992
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown on runway 18/36 at Canaima Airport, the twin engine airplane went out of control, veered off runway and came to rest in the bush, bursting into flames. All occupants evacuated safely while the aircraft was partially destroyed by fire. It was reported that a tire burst upon landing.

Crash of a De Havilland DHC-3T Otter in the George Inlet: 1 killed

Date & Time: May 13, 2019 at 1221 LT
Type of aircraft:
Operator:
Registration:
N959PA
Flight Phase:
Survivors:
Yes
Schedule:
Ketchikan - Ketchikan
MSN:
159
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
25000
Aircraft flight hours:
30296
Circumstances:
On May 13, 2019, about 1221 Alaska daylight time, a float-equipped de Havilland DHC-2 (Beaver) airplane, N952DB, and a float-equipped de Havilland DHC-3 (Otter) airplane, N959PA, collided in midair about 8 miles northeast of Ketchikan, Alaska. The DHC-2 pilot and four passengers sustained fatal injuries. The DHC-3 pilot sustained minor injuries, nine passengers sustained serious injuries, and one passenger sustained fatal injuries. The DHC-2 was destroyed, and the DHC-3 sustained substantial damage. The DHC-2 was registered to and operated by Mountain Air Service LLC, Ketchikan, Alaska, under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135 as an on-demand sightseeing flight. The DHC-3 was registered to Pantechnicon Aviation LTD, Minden, Nevada, and operated by Venture Travel, LLC, dba Taquan Air, Ketchikan, Alaska, under the provisions of Part 135 as an on-demand sightseeing flight. Visual meteorological conditions prevailed in the area at the time of the accident. According to information provided by the operators, both airplanes had been conducting sightseeing flights to the Misty Fjords National Monument area. They were both converging on a scenic waterfall in the Mahoney Lakes area on Revillagigedo Island before returning to the Ketchikan Harbor Seaplane Base (5KE), Ketchikan, Alaska, when the accident occurred. According to recorded avionics data recovered from the DHC-3, it departed from an inlet (Rudyerd Bay) in the Misty Fjords National Monument area about 1203 and followed the inlet westward toward Point Eva and Manzanita Island. At 1209, at an altitude between 1,900 and 2,200 ft, the DHC-3 crossed the Behm Canal then turned to the southwest about 1212 in the vicinity of Lake Grace. Automatic dependent surveillance-broadcast (ADS-B) tracking data for both airplanes, which were provided by the Federal Aviation Administration (FAA), began at 1213:08 for the DHC-3, and at 1213:55 for the DHC-2. At 1217:15, the DHC-3 was about level at 4,000 ft mean sea level (msl) over Carroll Inlet on a track of 225°. The DHC-2 was 4.2 nautical miles (nm) south of the DHC-3, climbing through 2,800 ft, on a track of 255°. The DHC-3 pilot stated that, about this time, he checked his traffic display and “there were two groups of blue triangles, but not on my line. They were to the left of where I was going.” He stated that he did not observe the DHC-2 on his traffic display before the collision. The ADS-B data indicated that, about 1219, the DHC-3 started a descent from 4,000 ft, and the DHC-2 was climbing from 3,175 ft. During the next 1 minute 21 seconds, the DHC-3 continued to descend on a track between 224° and 237°, and the DHC-2 leveled out at 3,350 ft on a track of about 255°. Between 1220:21 and 1221:14, the DHC-3 made a shallow left turn to a track of 210°, then a shallow right turn back to a track of 226°. The airplanes collided at 1221:14 at an altitude of 3,350 ft, 7.4 nm northeast of 5KE. The ADS-B data for both airplanes end about the time of the collision. The DHC-2 was fractured into multiple pieces and impacted the water and terrain northeast of Mahoney Lake. Recorded avionics data for the DHC-3 indicate that at 1221:14, the DHC-3 experienced a brief upset in vertical load factor and soon after entered a right bank, reaching an attitude about 50° right wing down at 1221:19 and 27° nose down at 1221:22. The DHC-3 began descending and completed a 180° turn before impacting George Inlet at 1222:15 along a northeast track.
Probable cause:
The NTSB determines that the probable cause of this accident was the inherent limitations of the see-and-avoid concept, which prevented the two pilots from seeing the other airplane before the collision, and the absence of visual and aural alerts from both airplanes’ traffic display systems, while operating in a geographic area with a high concentration of air tour activity.
Contributing to the accident were
1) the Federal Aviation Administration’s provision of new transceivers that lacked alerting capability to Capstone Program operators without adequately mitigating the increased risk associated with the consequent loss of the previously available alerting capability and
2) the absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of De Havilland DHC-2 Beaver in the Goerge Inlet: 5 killed

Date & Time: May 13, 2019 at 1221 LT
Type of aircraft:
Operator:
Registration:
N952DB
Flight Phase:
Survivors:
No
Schedule:
Ketchikan - Ketchikan
MSN:
237
YOM:
1952
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
11000
Aircraft flight hours:
16452
Circumstances:
On May 13, 2019, about 1221 Alaska daylight time, a float-equipped de Havilland DHC-2 (Beaver) airplane, N952DB, and a float-equipped de Havilland DHC-3 (Otter) airplane, N959PA, collided in midair about 8 miles northeast of Ketchikan, Alaska. The DHC-2 pilot and four passengers sustained fatal injuries. The DHC-3 pilot sustained minor injuries, nine passengers sustained serious injuries, and one passenger sustained fatal injuries. The DHC-2 was destroyed, and the DHC-3 sustained substantial damage. The DHC-2 was registered to and operated by Mountain Air Service LLC, Ketchikan, Alaska, under the provisions of Title 14 Code of Federal Regulations (CFR) Part 135 as an on-demand sightseeing flight. The DHC-3 was registered to Pantechnicon Aviation LTD, Minden, Nevada, and operated by Venture Travel, LLC, dba Taquan Air, Ketchikan, Alaska, under the provisions of Part 135 as an on-demand sightseeing flight. Visual meteorological conditions prevailed in the area at the time of the accident. According to information provided by the operators, both airplanes had been conducting sightseeing flights to the Misty Fjords National Monument area. They were both converging on a scenic waterfall in the Mahoney Lakes area on Revillagigedo Island before returning to the Ketchikan Harbor Seaplane Base (5KE), Ketchikan, Alaska, when the accident occurred. According to recorded avionics data recovered from the DHC-3, it departed from an inlet (Rudyerd Bay) in the Misty Fjords National Monument area about 1203 and followed the inlet westward toward Point Eva and Manzanita Island. At 1209, at an altitude between 1,900 and 2,200 ft, the DHC-3 crossed the Behm Canal then turned to the southwest about 1212 in the vicinity of Lake Grace. Automatic dependent surveillance-broadcast (ADS-B) tracking data for both airplanes, which were provided by the Federal Aviation Administration (FAA), began at 1213:08 for the DHC-3, and at 1213:55 for the DHC-2. At 1217:15, the DHC-3 was about level at 4,000 ft mean sea level (msl) over Carroll Inlet on a track of 225°. The DHC-2 was 4.2 nautical miles (nm) south of the DHC-3, climbing through 2,800 ft, on a track of 255°. The DHC-3 pilot stated that, about this time, he checked his traffic display and “there were two groups of blue triangles, but not on my line. They were to the left of where I was going.” He stated that he did not observe the DHC-2 on his traffic display before the collision. The ADS-B data indicated that, about 1219, the DHC-3 started a descent from 4,000 ft, and the DHC-2 was climbing from 3,175 ft. During the next 1 minute 21 seconds, the DHC-3 continued to descend on a track between 224° and 237°, and the DHC-2 leveled out at 3,350 ft on a track of about 255°. Between 1220:21 and 1221:14, the DHC-3 made a shallow left turn to a track of 210°, then a shallow right turn back to a track of 226°. The airplanes collided at 1221:14 at an altitude of 3,350 ft, 7.4 nm northeast of 5KE. The ADS-B data for both airplanes end about the time of the collision. The DHC-2 was fractured into multiple pieces and impacted the water and terrain northeast of Mahoney Lake. Recorded avionics data for the DHC-3 indicate that at 1221:14, the DHC-3 experienced a brief upset in vertical load factor and soon after entered a right bank, reaching an attitude about 50° right wing down at 1221:19 and 27° nose down at 1221:22. The DHC-3 began descending and completed a 180° turn before impacting George Inlet at 1222:15 along a northeast track.
Probable cause:
The NTSB determines that the probable cause of this accident was the inherent limitations of the see-and-avoid concept, which prevented the two pilots from seeing the other airplane before the collision, and the absence of visual and aural alerts from both airplanes’ traffic display systems, while operating in a geographic area with a high concentration of air tour activity.
Contributing to the accident were
1) the Federal Aviation Administration’s provision of new transceivers that lacked alerting capability to Capstone Program operators without adequately mitigating the increased risk associated with the consequent loss of the previously available alerting capability and
2) the absence of a requirement for airborne traffic advisory systems with aural alerting among operators who carry passengers for hire.
Final Report:

Crash of a Canadair CL-601-3A Challenger near La Rosita: 13 killed

Date & Time: May 5, 2019 at 1740 LT
Type of aircraft:
Registration:
N601VH
Flight Phase:
Survivors:
No
Site:
Schedule:
Las Vegas - Monterrey
MSN:
5043
YOM:
1989
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
13
Captain / Total flying hours:
3337
Captain / Total hours on type:
329.00
Copilot / Total flying hours:
1541
Copilot / Total hours on type:
147
Aircraft flight hours:
7637
Aircraft flight cycles:
4122
Circumstances:
The airplane departed Las Vegas-McCarran Airport at 1452LT on a charter flight to Monterrey, carrying two pilots and 11 passengers who were returning to Mexico after taking part to a boxing match in Las Vegas. The flight was completed at FL370 until the crew was cleared to climb to FL390 for five minutes then to FL410. Suddenly, the airplane entered an uncontrolled descent and eventually crashed in an almost flat attitude in a desert area located near La Rosita, Coahuila. The aircraft was destroyed by impact forces and a post crash fire and all 13 occupants were killed. The wreckage was found the following day.
Probable cause:
A loss of control at high altitude after the airplane encountered severe atmospheric turbulences coming from an unstable weather area. The crew were unable to detect the presence of this atmospheric phenomenon due to the malfunction of the onboard weather radar system for reasons that could not be determined.
Final Report:

Crash of a Boeing 737-81Q at Jacksonville NAS

Date & Time: May 3, 2019 at 2142 LT
Type of aircraft:
Operator:
Registration:
N732MA
Survivors:
Yes
Schedule:
Guantánamo Bay - Jacksonville
MSN:
30618/830
YOM:
2001
Flight number:
LL293
Crew on board:
7
Crew fatalities:
Pax on board:
136
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7500
Captain / Total hours on type:
2204.00
Copilot / Total flying hours:
7500
Copilot / Total hours on type:
18
Aircraft flight hours:
38928
Aircraft flight cycles:
15610
Circumstances:
According to both pilots, the takeoff, climb, and cruise portions of the flight were uneventful. The No. 1 (left) thrust reverser was not operational and deferred for the flight in accordance with the airplane’s minimum equipment list. The captain was the pilot flying for the accident flight, and the first officer was the pilot monitoring. The captain was also performing check airman duties for the first officer who was in the process of completing operating experience training. During the approach to Jacksonville Naval Air Station (NIP), the flight crew had two runway change discussions with air traffic controllers due to reported weather conditions (moderate to heavy precipitation) near the field; the pilots ultimately executed the area navigation GPS approach to runway 10, which was ungrooved and had a displaced threshold 997 ft from the threshold, leaving an available landing distance of 8,006 ft. As the airplane descended through 1,390 ft mean sea level (msl), the pilots configured it for landing with the flaps set at 30º and the landing gear extended; however, the speedbrake handle was not placed in the armed position as specified in the Landing checklist. At an altitude of about 1,100 ft msl and 2.8 nm from the runway, the airplane was slightly above the glidepath, and its airspeed was on target. Over the next minute, the indicated airspeed increased to 170 knots (17 knots above the target approach speed), and groundspeed reached 180 knots, including an estimated 7-knot tailwind. At an altitude of about 680 ft msl and 1.6 nm from the threshold, the airplane deviated further above the 3° glidepath such that the precision approach path indicator (PAPI) lights would have appeared to the flight crew as four white lights and would retain that appearance throughout the rest of the approach. Eight seconds before touchdown, multiple enhanced ground proximity warning system alerts announced “sink rate” as the airplane’s descent rate peaked at 1,580 fpm. The airplane crossed the displaced threshold 120 ft above the runway (the PAPI glidepath crosses the displaced threshold about 54 ft above the runway) and 17 knots above the target approach speed, with a groundspeed of 180 knots and a rate of descent about 1,450 ft per minute (fpm). The airplane touched down about 1,580 ft beyond the displaced threshold, which was 80 ft beyond the designated touchdown zone as specified in the operator’s standard operating procedures (SOP). After touchdown, the captain deployed the No. 2 engine thrust reverser and began braking; he later reported, however, that he did not feel the aircraft decelerate and increased the brake pressure. The speedbrakes deployed about 4 seconds after touchdown, most likely triggered by the movement of the right throttle into the idle reverse thrust detent after main gear tire spinup. The automatic deployment of the speedbrakes was likely delayed by about 3 seconds compared to the automatic deployment that could have been obtained by arming the speedbrakes before landing. The airplane crossed the end of the runway about 55 ft right of the centerline and impacted a seawall 90 ft to the right of the centerline, 9,170 ft beyond the displaced threshold, and 1,164 ft beyond the departure end of runway 10. After the airplane came to rest in St. Johns River, the flight crew began an emergency evacuation.
Probable cause:
An extreme loss of braking friction due to heavy rain and the water depth on the ungrooved runway, which resulted in viscous hydroplaning. Contributing to the accident was the operator’s inadequate guidance for evaluating runway braking conditions and conducting en route landing distance assessments.
Contributing to the continuation of an unstabilized approach were
1) the captain’s plan continuation bias and increased workload due to the weather and performing check airman duties and
2) the first officer’s lack of experience.
Final Report:

Crash of a Douglas DC-3 in Finca La Bendición: 14 killed

Date & Time: Mar 9, 2019 at 1036 LT
Type of aircraft:
Operator:
Registration:
HK-2494
Flight Phase:
Survivors:
No
Schedule:
San Jose del Guaviare – Villavicencio
MSN:
33105/16357
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
14
Captain / Total flying hours:
12710
Captain / Total hours on type:
7044.00
Copilot / Total flying hours:
12710
Copilot / Total hours on type:
7044
Aircraft flight hours:
23000
Circumstances:
The twin engine airplane departed San José del Guaviare on a charter flight to Villavicencio, carrying 11 passengers and three crew members. While cruising at an altitude of 8,500 feet in good weather conditions, the left engine failed due to an important fuel leak. The crew elected to secure the engine but was unable to feather the propeller. The airplane lost speed and height, and while attempting an emergency landing, the crew lost control of the airplane that stalled and crashed in a palm plantation, bursting into flames. The aircraft was totally destroyed by a post crash fire and all 14 occupants were killed.
Probable cause:
The investigation determined that the accident was caused by the following probable causes:
- Loss of control in-flight as a consequence of the decrease in minimum in-flight control speed and drag generated by the impossibility of performing the No. 1 engine propeller feathering in the face of engine failure.
- Malfunction of the lubrication system of engine No. 1, evident in the abundant oil leakage from the engine, in flight, and in the governor of the left propeller; although discrepancies were found in the maintenance of the propeller feathering pressure line, it was not possible to determine the origin of the oil leakage.
- Weaknesses in the aircraft Operator's operational procedures, lacking a standard that would facilitate a crew's decision making to act in the event of critical failures, in matters such as making an emergency landing on unprepared field or the selection of an alternate airfield.

Contributing Factors:
- Deficiencies in standard maintenance practices during repairs performed on the No. 1 engine's propeller propeller feathering oil pressure line.
- Non-compliance with an effective and reliable maintenance program, which did not verify the operating conditions of the aircraft components; it was not possible to determine compliance with the last 50-hour service, Phase A, to engine No. 1 according to the company's maintenance program, since there are no records of that service in the Flight Log.
- Inefficient safety management system of the Operator for not detecting errors in the maintenance processes and in the conduct and control of operations.
Final Report:

Crash of a Learjet 35A in Buenos Aires

Date & Time: Mar 7, 2019 at 1930 LT
Type of aircraft:
Operator:
Registration:
LV-BNR
Survivors:
Yes
Schedule:
Rosario – Buenos Aires
MSN:
35-373
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Rosario-Islas Malvinas Airport at 1900LT on a charter flight to Buenos Aires, carrying two passengers and two pilots. On approach to Buenos Aires-Aeroparque-Jorge Newbury Airport by night, the crew encountered poor weather conditions with thunderstorm activity, heavy rain falls and strong winds. The aircraft landed 200 metres past the runway 13 threshold and the crew stated the braking procedure. After a course of about 500 metres, the aircraft deviated to the left and veered off runway. It rolled on a grassy area then contacted the concrete taxiway, causing both main landing gear to be torn off. The aircraft came to rest 860 metres from the runway threshold and was damaged beyond repair. All four occupants evacuated safely.
Probable cause:
Conclusions regarding factors related to the accident:
- At the time of the event, meteorological conditions were poor with a strong storm, rain and gusts of wind.
- Visual cues may have been reduced due to heavy rain falls.
- The aircraft was displaced from the runway center line when it made contact with the ground.
- The aircraft made contact with the left landing gear off the runway due to strong gusts of wind.
- The lateral excursion to the grassy area occurred due to the impossibility of recovering the trajectory of the aircraft, once it was displaced by the action of the wind.
Final Report:

Crash of a Gulfstream G200 in Moscow

Date & Time: Feb 26, 2019 at 1244 LT
Type of aircraft:
Operator:
Registration:
4K-AZ88
Survivors:
Yes
Schedule:
Baku - Moscow
MSN:
189
YOM:
2008
Flight number:
EWS88
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7608
Captain / Total hours on type:
2356.00
Copilot / Total flying hours:
2554
Copilot / Total hours on type:
609
Aircraft flight hours:
4174
Aircraft flight cycles:
1787
Circumstances:
The airplane departed Baku-Bina Airport on a charter flight to Moscow, carrying three passengers and three crew members. Following an uneventful flight, the crew was cleared for an approach to Moscow-Sheremetyevo Airport runway 24C. The aircraft landed at a speed of 150 knots some 250 metres past the runway threshold. After touchdown, the crew started the braking procedure and activated the thrust reversers. After a course of several hundred metres, the aircraft deviated to the left, made an almost 180 turn and veered off runway to the left. While contacting soft ground, the right main gear was torn off and the aircraft came to rest in a snow covered area. All six occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The reason for the accident with the Gulfstream G200 4K-AZ88 was the stowing of the right-engine reverser by the pilot KVS from maximum thrust reversal while maintaining maximum thrust reversal on the left engine, which led to the appearance of a significant turning moment to the left. The aircraft turning to the left in the presence of a cross wind to the right, as well as turbulence of the airflow near the rudder due to the open thrust reversal mechanism of the left engine and possible ice deposition on the outer surfaces of the aircraft, which led to the development of a significant swing moment on the rudder. The development of a significant articulated moment on the rudder, in the absence of power steering in the rudder control system, led to its deviation to the leftmost position despite significant (up to 82 kg or 180 pounds) forces exerted by the crew on the pedals. The deviation of the rudder (pedals) to the left also led to the deviation of the nose wheel to the left. The total moment from the running reverse of the left engine, from the right engine in direct draft mode, and from the rudder and nose wheel deflection to the left, led to the aircraft rolling out of the runway and its damage. Separate braking applied by the crew could not prevent the aircraft from rolling out.

The following contributing factors were identified:
- The crew did not take into account the provisions of the AOM about the possible "destabilizing" effect of the thrust reverse when landing with a cross wind on the runway with a reduced braking coefficient;
- Increased psycho-emotional tension of the crew members due to long dissatisfaction and emotional discussion of instructions and actions of ATC controllers. At the same time, the instructions and actions of the ATC service controllers were in line with established procedures.
Final Report: