Flugunfall 09 FEB 2020 einer Boeing 737-524 (WL) VQ-BPS - Usinsk Airport (USK)
ASN logo

Status:Accident investigation report completed and information captured
Datum:Sonntag 9 Februar 2020
Flugzeugtyp:Silhouette image of generic B735 model; specific model in this crash may look slightly different
Boeing 737-524 (WL)
Kennzeichen: VQ-BPS
Werknummer: 28909/2960
Baujahr: 1997-11-12 (22 years 3 months)
Anzahl Zyklen der Zelle:29162
Triebwerk: 2 CFMI CFM56-3B1
Besatzung:Todesopfer: 0 / Insassen: 6
Fluggäste:Todesopfer: 0 / Insassen: 94
Gesamt:Todesopfer: 0 / Insassen: 100
Sachschaden: schwer beschädigt
Konsequenzen: Written off (damaged beyond repair)
Unfallort:Usinsk Airport (USK) (   Russland)
Flugphase: Landung (LDG)
Betriebsart:Inländischer planmäßiger Passagierflug
Flug von:Moskva-Vnukovo Airport (VKO/UUWW), Russland
Flug nach:Usinsk Airport (USK/UUYS), Russland
Utair flight 595, a Boeing 737-524, suffered a main landing gear collapse after it touched down short of the runway at Usinsk Airport, Russia.
The aircraft took off from Moscow's Vnukovo Airport at 06:59 UTC and landed at Usinsk about 09:20 UTC (12:20 LT). It touched down in the snow, 32 meters short of the threshold of runway 13. The aircraft the it a snow bank, causing the main landing gears to separate.
The aircraft slid down the runway and came to rest on the edge, perpendicular to the runway. All occupants evacuated the aircraft safely.

Probable Cause:

The accident with the Boeing 737-500 VQ-BPS aircraft occurred during the landing as a result of a collision of the aircraft with a snow parapet 1.1 m high at a distance of 32 m to the runway threshold (within the paved section of the runway), which resulted in damage to the main landing gear and their subsequent "folding" in the process of moving along the runway.
The accident was caused by a combination of the following factors:
- the presence of contradictions in the Federal Aviation Rules for flights in the airspace of the Russian Federation, the airline's radio control system and the aircraft operational documentation regarding the need and procedure for introducing temperature corrections to the readings of barometric altimeters at low ambient temperatures;
- Failure by the operator of the Usinsk aerodrome to comply with the FAP-262 requirements for the maintenance of the aerodrome, which resulted in the presence of snow parapets on the paved section of the landing strip;
- the operator of the Usinsk aerodrome did not eliminate the shortcomings in the winter maintenance of the aerodrome, noted based on the results of the inspection by the Rosaviatsia commission on January 22, 2020;
- lack of risk assessment in the airline associated with the execution of approaches in the baro-VNAV mode in the presence of factors that impede such approaches (low ambient temperatures, snow-covered underlying surface, drifting snow (snowstorm), significant changes in the relief in front of the runway end, lack of PAPI-type lights), as well as appropriate recommendations to the crews on the specifics of such approaches, including after the transition to visual flight, and crew training;
- insufficient assessment by the crew during the preparation of the existing threats (hazard factors) and making an insufficiently substantiated decision to perform an RNAV (GNSS) approach (under the control of the autopilot in LNAV/VNAV mode) without introducing a correction for low outside air temperature in altitude overflying waypoints, which led to a flight below the established glide path;
- performing a flight along the "extended glide path" after turning off the autopilot and switching to manual piloting without attempting to enter the set glide path;
- the PIC may have had a visual illusion of a "high glide path" due to a snow-covered underlying surface, a snowstorm and the presence of a ravine directly in front of the runway end in the absence of PAPI type lights, which led to an incorrect assessment of the aircraft's flight altitude after switching to manual piloting, lack of reaction to timely and correct warnings of the co-pilot and exit to the runway end at a height significantly less than the established one.

Accident investigation:

Investigating agency: MAK Russia
Status: Investigation completed
Duration: 1 year and 1 months
Accident number: final report
Download report: Final report

» Ren.tv

METAR Weather report:
05:30 UTC / 08:30 local time:
METAR UUYS 090530Z 17006MPS 9000 – SG OVC007 M24/M26 Q1003 R13/490534 NOSIG RMK QFE744/0993=
Wind 170 at 6 mps; 9000 m visibility, 700 ft overcast, temperature: -24°C

09:10 UTC / 12:10 local time:
SPECI UUYS 090910Z 17006G11MPS 1500 SN BLSN BKN015 M21/M23 Q0999 R13/390238 TEMPO 1000 SN BLSN RMK QFE741/0989=
Wind 170 at 6, gusting to 11 mps; 1500 m visibility in snow and blowing snow, broken clouds at 1500 ft, temperature: -21°C


photo of Boeing-737-524-VQ-BPS
accident date: 09-02-2020
type: Boeing 737-524 (WL)
registration: VQ-BPS
photo of Boeing-737-524-VQ-BPS
accident date: 09-02-2020
type: Boeing 737-524 (WL)
registration: VQ-BPS

Video, social media

Aircraft history
date registration operator remarks
N16648 Boeing 12 November 1997 first flight
N16648 Continental Air Lines 5 December 1997 delivered
N16648 United Airlines 1 October 2010 Continental merged into United
VQ-BPS UTair Aviation 27 March 2012 delivered
VQ-BPS UTair Aviation 15 March 2017 returned to ULLI after nosegear failed to retract after takeoff

This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from Moskva-Vnukovo Airport to Usinsk Airport as the crow flies is 1565 km (978 miles).
Accident location: Approximate; accuracy within a few kilometers.

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages


Boeing 737-500

  • 390 built
  • 11th loss
» safety profile

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2023 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314