FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Aeroflot Flight 1492

5 May 2019 · Sheremetyevo International Airport, Moscow, Russia

Sukhoi Superjet 100-95B · Major electrical failure after lightning strike, caught fire during bounced emergency landing

From Sheremetyevo International Airport (SVO) to Emperor Nicholas II Murmansk Airport (MMK)

Report a problem

Event

NTSB case
DCA19WA148
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Final · Interstate Aviation Committee final report, 28 Mar 2025 
Event fatalities
41 · all aircraft and ground
Ground fatalities
0
Occupants
78
Survivors
37
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
10
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Sukhoi Superjet 100-95B

Flight
SU1492
Aircraft type
Sukhoi Superjet 100
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
RA-89098
Operator
Aeroflot
Onboard fatalities
41
Route
From Sheremetyevo International Airport (SVO)To Emperor Nicholas II Murmansk Airport (MMK)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Non-U.S., Commercial
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Fire/smoke (non-impact)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Task performance
  • Organizational issues › Development

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Aeroflot Flight 1492 was a scheduled domestic passenger flight operated by Aeroflot from Moscow–Sheremetyevo to Murmansk, Russia. On 5 May 2019, the Sukhoi Superjet 100 aircraft operating the flight was climbing out when it was struck by lightning. The aircraft suffered an electrical failure and returned to Sheremetyevo for an emergency landing. It bounced on landing and touched down hard, causing the landing gear to collapse, fuel to spill out of the wings, and a fire to erupt. The fire engulfed the rear of the aircraft, killing 41 of the 78 occupants.

Accident

Flight 1492 took off from runway 24C at Sheremetyevo International Airport, bound for Murmansk Airport, on 5 May 2019 at 18:03 local time (15:03 UTC). Towering cumulonimbus (thunderstorm) clouds were observed in the vicinity of the airport with a base of 6000 ft and peaking at about 29000 ft. The clouds were moving in a north-easterly direction at a speed of 40 - 45 kph. When the plane was approaching the thunderstorm zone, a 327 degree heading was selected manually at 18:07 local time (15:07 UTC), initiating a right turn earlier than it is prescribed by the КN 24Е standard instrument departure, but the crew did not request active thunderstorm area avoidance clearance. At 15:08 UTC, the aircraft was climbing through flight level 89 (around 8900 ft) when it was struck by lightning. The primary radio and autopilot became inoperative and the flight control mode changed to DIRECT – a degraded, more challenging mode of operation. The captain assumed manual control of the aircraft. The transponder code was changed to 7600 (to indicate radio failure) at 15:09 UTC and subsequently to 7700 (emergency) at 15:26 UTC while on final approach. The secondary radio (VHF2) remained operative and the crew were able to restore communication with air traffic control (ATC) and made a pan-pan call on the emergency frequency.

The aircraft stopped its climb at flight level 106 (around 10600 ft) and was guided towards Sheremetyevo by ATC. It performed a right orbit before lining up for approach to runway 24L; the crew tuned into the instrument landing system and the captain flew the approach manually. Upon capturing the glideslope, the aircraft's weight was 43.5 t, 1.6 t over the maximum landing weight. At 15:18:53 UTC, the captain attempted to contact the controller to request a holding area, but his message was not recorded by the controller's recorder. The flaps were lowered to 25 degrees, which is the recommended setting for an overweight landing in DIRECT mode. The wind was blowing from 190 degrees at 30 kn – a 50-degree crosswind – and the speed stabilised at 155 kn. Between 1100 ft and 900 ft AGL, the predictive windshear warning sounded repeatedly: "GO-AROUND, WINDSHEAR AHEAD". The crew did not acknowledge this warning on tape. Descending through 260 ft, the aircraft began to deviate below the glideslope and the "GLIDESLOPE" aural alert sounded. The captain called "advisory" and increased engine thrust, and the speed rose through 164 kn at 40 ft to 170 kn at 16 ft AGL – 15 kn above the required approach speed, although the airline's own Flight Operations Manual provides pilots with a margin of −5 to +20 kt as a criterion for stabilised approach. As he reduced the thrust to idle for the flare, the captain made several large, alternating sidestick inputs, causing the pitch to vary between +6 and −2 degrees.

The aircraft made simultaneous ground contact with all three landing gear legs 900 m beyond the runway threshold at a speed of 158 kn, resulting in a vertical acceleration of 2.55 g. Concurrently with the touchdown, in the span of 0.4 seconds, the sidestick was moved from full aft to full forward. Though the spoilers were armed, automatic spoiler deployment is inhibited in DIRECT mode and they were not extended manually. The aircraft bounced to a height of 6 ft. The captain attempted to apply maximum reverse thrust while he continued to hold the sidestick in the fully forward position. Reverse thrust and reverser door deployment is inhibited in the absence of weight on the aircraft's wheels (i.e. in flight) and the reverser doors only began to open upon the second touchdown. The aircraft lifted off the ground before the reverse door cycle was completed and reverse thrust did not activate. The second touchdown occurred two seconds after the first, nose-first, at a speed of 155 kn and with a vertical load of 5.85 g. The main landing gear weak links sheared – the weak links are designed to shear under heavy load to minimise damage to the wing – allowing the gear legs to "move up and backwards" and the wing remained intact. The aircraft bounced to a height of 15 - 18 ft. The thrust levers were advanced to take-off power – the reverser doors began to close – and the sidestick was pulled full aft in a possible attempt to go around. Thrust was not allowed to increase until the reverser doors were closed and a third impact was recorded at a speed of 140 kn and with a vertical load in excess of 5 g. The landing gear collapsed, penetrating the wing, and fuel spilled out of the wing tanks. A fire erupted, engulfing the wings, rear fuselage and empennage. Fire alarms sounded in the cockpit for the aft cargo hold and the auxiliary power unit. The aircraft slid down the runway, veered to the left and came to a standstill on the grass between two runway-adjoining taxiways with the nose facing upwind at 15:30 UTC. Power to the engines was cut at 15:31 UTC. Flight recorder data suggest that control over the engines had been lost after the final impact.

An evacuation was carried out from the front passenger doors and their slides were deployed. The first officer used the escape rope to climb out of the right cockpit window. Aeroflot claimed the evacuation took 55 seconds, though video evidence shows the slides still in use 70 seconds after their deployment. Passengers were seen carrying hand luggage out of the aircraft. The rear half of the aircraft was destroyed by the fire, which was extinguished about 45 minutes after landing.

Investigation and cause

Investigation

The Interstate Aviation Committee (IAC) opened an investigation into the accident. The French BEA participated as a representative of the state of design of the aircraft engine and EASA offered technical advice to BEA. Both flight recorders were recovered. The cockpit voice recorder (CVR) was found in satisfactory condition, but the flight data recorder (FDR) casing was damaged by exposure to extremely high temperatures, and data recovery depended on IAC specialists.

Data reading was completed on 17 May 2019, permitting analysis to begin. The IAC sent a follow-up accident report to Rosaviatsiya, the Russian civil aviation authority. Rosaviatsiya issued a safety information bulletin containing a summary of the accident and a number of recommendations.

On 30 May, TASS reported IAC expert Vladimir Kofman was attending the Transport Security Forum where he said that "the disaster occurred because of [the] hard touchdowns". His comment evoked a sharp response from Aeroflot and the IAC issued a six-point press release distancing itself from Kofman. The IAC said they would be conducting an internal investigation and that Kofman was not part of the Flight 1492 investigation. The IAC asked news media to provide video or audio evidence of "published statements made by Kofman". The IAC said they continued to analyse data from the accident and that they were preparing for the 5 June release of the preliminary report, concluding, "in this regard, neither IAC nor other persons currently can not have reliable information about the establishment by the Investigation team of the causes of the fatal accident".

Final report

The final report, issued on March 28, 2025, found no design flaws that would prohibit operation. Investigators concluded that the hard landing was due to human factors, namely the captain's difficulty controlling the aircraft in direct flight control law mode. Also the report noted that deficiencies in the operational documentation were factors that contributed to the accident. Notwithstanding, the inquiry recommended a review of the landing gear design and of the possibility of restoring normal flight control law, as well as an analysis of crew workload faced with multiple failure messages. Additional crew training on piloting issues in direct law was also advised.

Text from the Wikipedia article “Aeroflot Flight 1492” (revision 1373423199, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

The MAK of Russia has notified the NTSB of an accident involving a Sukhoi RRJ95 airplane that occurred on May 05, 2019. The NTSB has appointed a U.S. Accredited Representative to assist the MAK's investigation under the provisions of ICAO Annex 13 as State of Manufacturer of the airplane.All investigative information will be released by the MAK of Russia.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: Aeroflot Flight 1492
Article
Aeroflot Flight 1492
Revision
1373423199 · 2026-09-05 · retrieved 2026-09-18
Wikidata
Q63490143
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA19WA148
Event ID
20190517X21143
Case number
DCA19WA148
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "Aeroflot Flight 1492" (page 60670056, revision 1373423199); merged with NTSB case DCA19WA148 (events / aircraft)
Date
Wikipedia infobox: date; matches the Interstate Aviation Committee (MAK / IAC) final report
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates; matches the Interstate Aviation Committee (MAK / IAC) final report
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA19WA148
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities; matches the Interstate Aviation Committee (MAK / IAC) final report
Ground fatalities
Interstate Aviation Committee (MAK / IAC) final report
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "Aeroflot Flight 1492" and NTSB case DCA19WA148, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • No bulk values were replaced by the NTSB case API.
  • Checked against the Interstate Aviation Committee (MAK / IAC) final report (2025-03-28) on 2026-09-18. The report states the same date, crash-site coordinates, flight number, fatalities, registration, operator, departure and destination. Taken from the report: ground fatalities. Not checked: place, aircraft type, damage and type of operation.