Aeroflot Flight 1492

Aeroflot Flight 1492 was a scheduled passenger flight 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, and 41 of the 78 occupants were not able to evacuate and died.

Aeroflot Flight 1492
Photograph of the aircraft involved
RA-89098, the aircraft involved; seen in November 2017
Accident
Date5 May 2019
SummaryCrash landing; under investigation
SiteSheremetyevo International Airport, Moscow, Russia
55°58′06.20″N 37°24′07.20″E / 55.9683889°N 37.4020000°ECoordinates: 55°58′06.20″N 37°24′07.20″E / 55.9683889°N 37.4020000°E
Aircraft
Aircraft typeSukhoi Superjet 100
Aircraft nameMustai Karim
OperatorAeroflot
IATA flight No.SU1492
ICAO flight No.AFL1492
Call signAEROFLOT 1492
RegistrationRA-89098
Flight originSheremetyevo International Airport
DestinationMurmansk Airport, Russia
Occupants78
Passengers73
Crew5
Fatalities41
Injuries10
Survivors37

Aircraft

The aircraft was a Russian-built Sukhoi Superjet 100, MSN (manufacturer's serial number) 95135, and was registered as RA-89098.[1] It was delivered new to Aeroflot on 27 September 2017 and had accumulated 2,710 flight hours and 1,658 cycles (a flight cycle consists of a take-off and a landing) before the accident.[2][3] Aeroflot Superjets are configured with 87 passenger seats, 12 in business and 75 in economy.[4]

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 6,000 ft (1,800 m) and peaking at about 29,000 feet (8,800 m). The clouds were moving in a north-easterly direction at a speed of 40–45 kilometres per hour (22–24 kn). 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 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.[5] 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.[6]

The aircraft stopped its climb at flight level 106 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 tonnes (96,000 lb), 1.6 tonnes (3,500 lb) 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 knots (15 m/s) – a 50-degree crosswind – and the speed stabilised at 155 knots (287 km/h). Between 1,100 feet (340 m) and 900 feet (270 m) AGL, the predictive windshear warning sounded repeatedly: "GO-AROUND, WINDSHEAR AHEAD". The crew did not acknowledge this warning on tape. Descending through 260 feet (79 m), 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 knots (304 km/h) at 40 feet (12 m) to 170 knots (310 km/h) at 16 feet (4.9 m) AGL – 15 knots (28 km/h) 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.[6][1][2]

The aircraft made simultaneous ground contact with all three landing gear legs 900 metres (3,000 ft) beyond the runway threshold at a speed of 158 knots (293 km/h), resulting in a vertical acceleration of 2.55 g. Concurrently with the touchdown, in the span of 0.4 seconds, the sidestick was pulled 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 feet (1.8 m). 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 knots (287 km/h) 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 feet (4.6–5.5 m). 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 knots (260 km/h) 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.[6][1][7][8]

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 a 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.[4] The rear half of the aircraft was destroyed by the fire, which was extinguished about 45 minutes after landing.[6][9][10]

Passengers and crew

Five crew and 73 passengers were onboard on the aircraft. The crew consisted of the captain, a first officer and three cabin crew members. The captain, aged 42, held an Airline Transport Pilot Licence and had 6,844 flying hours, including 1,570 on the Superjet. He had previously operated the Ilyushin Il-76 and a number of smaller aircraft for the FSB (2,320 flying hours) and the Boeing 737 for Transaero (2,022 flying hours). He was employed by Aeroflot and transitioned onto the SSJ-100 in 2016. The 36-year-old first officer joined Aeroflot in 2017, held a Commercial Pilot Licence and had 773 hours of flying experience, including 623 on the Superjet.[6]

Forty passengers and the flight attendant seated in the rear of the aircraft were killed. Forty of the victims were Russian and one a US citizen, and 26 resided in Murmansk Oblast, including a 12-year-old girl.[11][12] One crew member and two passengers sustained serious, and three crew members and four passengers minor injuries. The remaining 27 passengers were unharmed.[8]

Investigation

The Interstate Aviation Committee (IAC) opened an investigation into the accident. The French BEA is participating as representative of the state of design of the aircraft engine and EASA will offer technical advice to BEA.[13][14] On 6 May 2019, the IAC said in a press release that both flight recorders had been 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 IAC specialists were working to extract the data.[6]

On 17 May, the IAC announced that data from the flight recorders had been read out and their analysis was in progress. The IAC sent a follow-up accident report to Rosaviatsiya, the Russian civil aviation authority.[15] Rosaviatsiya issued a safety information bulletin containing a summary of the accident and a number of recommendations.[16]

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 [sic] reliable information about the establishment by the Investigation team of the causes of the fatal accident".[17][15]

Interim report

On 14 June, the IAC published their interim report,[18] presenting a detailed reconstruction of the accident, but they did not draw any conclusions. The pilots did not request active storm avoidance from air traffic control. However, they entered the second segment of the departure, initiating a right turn away from the storm earlier than prescribed. The pilot flying had difficulty maintaining altitude in manual flight during an orbiting manoeuvre in a 40-degree bank and deviated by more than 200 feet (61 m) from his assigned altitude, triggering multiple aural alerts. The crew omitted to perform the approach briefing and the approach checklist, and did not set the go-around altitude.[19][20] The pilot deviated below the glideslope descending through 270 feet (82 m) AGL and increased engine thrust; the aircraft accelerated to 15 knots (28 km/h) above its required approach speed. Durling landing, sidestick inputs were "of an abrupt and intermittent character", including wide-amplitude, sweepîng pitch movements not observed during approaches in normal flight law, but similar to other Aeroflot pilots' direct flight law approaches. The report also noted that the pilots ignored a windshear warning that would have required a go-around unless it was spurious.[21] Investigators found traces of lightning impact on antennae, various sensors, exit lights and the cockpit windows. Investigators re-examined the design of the landing gear and found that it met certification requirements. The report cited a material provided by Sukhoi claiming that contemporary certification requirements did not consider the effect of "secondary impacts of the airframe on the ground after the destruction of the landing gear". The interim report did not look into the survival factors of the accident.[8]

Criminal proceedings

A criminal investigation was opened into a fatal “violation of the rules of safe movement and exploitation of air transport”. The Investigative Committee said on 6 May it was considering insufficient skill of the pilots, dispatchers and those who performed the technical inspection of the plane, along with mechanical problems and poor weather, as a possible cause of the accident.[22] A high-ranking law enforcement source told Lenta.ru that experts would examine the actions of Sheremetyevo's fire and rescue service. The source said air traffic control were late with raising the alarm and fire engines had not left the fire station at the time of the accident. Only two of the six available engines were involved within the first six minutes and they were not filled with foam, which is more effective against a fuel-fed fire than water. Experts will have to answer more than 50 questions.[23]

On 2 October 2019, investigators filed charges against the captain. According to a spokeswoman for the Russian Investigative Committee, his actions "violated the existing regulations and led to the destruction and outbreak of fire". Prosecutors are seeking a seven-year jail term.[24]

Aftermath

Evacuation with luggage

There was widespread speculation that the evacuation was delayed by passengers retrieving hand luggage, prompted by video footage showing passengers leaving the plane with luggage in hand.[25][26][4][27] According to TASS, citing a law enforcement source, the majority of passengers in the tail end of the aircraft had practically no chance of rescue, many of them did not even have time to unfasten their seat belts. He added that those passengers from the tail section of the aircraft who managed to escape had moved to the front of the aircraft even before it stopped, and that he had no confirmation that retrieval of luggage had slowed the evacuation.[28] Speculation that the observed retrieval of luggage caused an evacuation delay was rejected by one witness.[29][30][31][27]

Response from Aeroflot

On 6 May 2019, Aeroflot announced that they would compensate surviving passengers and the families of the dead. One million rubles (US$15,320) were to be paid to passengers who did not require hospitalization, two million rubles ($30,640) to passengers who were hospitalized and five million rubles ($76,600) were to be paid to the families of the dead.[32]

Following the release of the accident summary by Rosaviatsiya on 17 May, it was reported in the media that the pilots had failed to set some of the surfaces of the wing – variously referred to as the "flaps", "brakes" and "air brakes" in news reports – for landing.[33] On the same day, Aeroflot issued a statement in which it denied the pilots had violated company procedures. Aeroflot said the flaps were properly configured for landing and that the spoilers should be extended manually only when reverse thrust is applied and the aircraft has settled on the runway. The airline said preliminary information by Rosaviatsiya are not evidence of pilot error and criticised the media for jumping to conclusions.[34][2]

Cancellations and public perception

On 5 May, a petition to ground the Sukhoi Superjet 100 (SSJ100) during the investigation was launched on Change.org. On May 8, it had collected over 140,000 signatures and, when asked, Kremlin Press Secretary Dmitry Peskov said the decision should be taken by the competent aviation authorities and not by citizens who sign petitions on the Change.org portal.[35][36] The Ministry of Transport of Russia decided against grounding the SSJ100, stating there was no obvious sign of a design flaw.[37]

Aeroflot cancelled approximately 50 SSJ100 flights in the week after the accident. Kommersant cited industry sources as saying the SSJ100 had lower dispatch reliability than Airbus and Boeing aircraft in the airline's fleet historically and attributed a rise in cancellations to "increased safety measures" at Aeroflot while the accident is investigated.[38][39] The SSJ100 suffered a number of technical failures in the weeks following the accident which attracted media attention in Russia. On 18 May, an Aeroflot SSJ100 from Ulyanovsk to Moscow–Sheremetyevo aborted its take-off due to a hydraulics failure indication following which the passengers refused to fly on the Superjet.[40]

On 17 May, it was reported that Russian regional airline RusLine abandoned its plans to operate 18 SSJ100s. According to the owner, this is because of the "likely reputational risks" associated with the accident.[41] On 22 May, the Russian airline Alrosa retired its Tupolev Tu-134 fleet, announcing that it was not abandoning plans to replace the Tu-134 with up to three SSJ100 by 2021 "despite all the hysteria".[42]

On 24 May, the Russian Association of Air Transport Operators (AEVT) requested a review of the SSJ100 for compliance with certification requirements in a letter sent to Minister of Transport Yevgeny Dietrich. The AEVT questioned whether electrical supply should have been disrupted by the lightning strike and whether the fuel system should have been compromised by impact forces. The letter said the flight control system, engines, cabin protection from an external fire and the crew training programme should all be examined for compliance. United Aircraft Corporation, the manufacturer of the Superjet, said the AEVT appeared to apply pressure on the technical investigation. As of 28 May, AEVT members operated 19 SSJ100s. Aeroflot, the operator of the accident aircraft, is not a member of the AEVT.[43]

See also

References

  1. ^ a b c "Aircraft accident Sukhoi Superjet 100-95B RA-89098 Moskva-Sheremetyevo Airport (SVO)". Aviation Safety Network. 8 May 2019.
  2. ^ a b c Kaminski-Morrow, David (18 May 2019). "Crashed Superjet's pitch fluctuated before fatal touchdown". Flightglobal.com.
  3. ^ "RA-89098 Aeroflot - Russian Airlines Sukhoi Superjet 100". www.planespotters.net. Retrieved 6 May 2019.
  4. ^ a b c Kaminski-Morrow, David (9 May 2019). "ANALYSIS: Superjet fire puts focus on evacuation threat". Flightglobal.com.
  5. ^ Bjorn, Fehrm. "Aeroflot SSJ100 crash at Moscow Sheremetyevo Airport". Leeham News and Analysis. Retrieved 17 May 2019.
  6. ^ a b c d e f Hradecky, Simon (6 May 2019). "Accident: Aeroflot SU95 at Moscow on May 5th 2019, aircraft bursts into flames during rollout and burns down". The Aviation Herald. Retrieved 7 May 2019.
  7. ^ "41 Confirmed Dead After Russian Aeroflot Plane Lands With Fire On Board". The Moscow Times. 5 May 2019. Retrieved 16 May 2019.
  8. ^ a b c Air Accident Investigation Commission. RRJ-95B RA-89098 Interim Report (PDF) (Report). Interstate Aviation Committee.CS1 maint: uses authors parameter (link)
  9. ^ "Aeroflot indicates Superjet engines caught fire on landing". Flight Global. Retrieved 6 May 2019.
  10. ^ "Aeroflot plane crash: Russia jet 'struck by lightning'". BBC News. Retrieved 6 May 2019.
  11. ^ «Мама, мы взлетаем»: как один полет прервал жизнь пассажиров SSJ-100 ["Mama, we take off": how a SSJ-100 flight interrupted the life of passengers]. Газета.Ru.
  12. ^ "Jeremy Brooks of New Mexico ID'd as American killed in Russia plane crash". ABC11 Raleigh-Durham. 6 May 2019.
  13. ^ Франция включилась в расследование ЧП с SSJ100 как разработчик двигателя ["France joins the state investigation of the emergency with the SSJ100 as an engine developer"]. РИА Новости. 14 May 2019.
  14. ^ BEA. "Accident to the Sukhoi RRJ95 registered RA-89098 and operated by Aeroflot on 05/05/2019 at Moscow [Investigation led by MAK / Russia]". BEA - Bureau d'Enquêtes et d'Analyses pour la sécurité de l'aviation civile.
  15. ^ a b "RRJ-95B RA-89098 05.05.2019". mak-iac.org. Retrieved 20 May 2019.
  16. ^ Росавиация не делала выводов по расследованию катастрофы SSJ «Аэрофлота» — ведомство ["Rosaviatsia did not draw conclusions on the investigation of the SSJ Aeroflot disaster - (says a representative of) the (Federal Air Navigation) Agency"]. Рамблер/новости. Retrieved 20 May 2019.
  17. ^ «Аэрофлот» ответил на слова эксперта МАК о причинах катастрофы SSJ [Aeroflot responded to the words of the expert IAC on the causes of the SSJ crash]. РБК (in Russian). RBK Group. 30 May 2019. Retrieved 31 May 2019.
  18. ^ "ПРЕДВАРИТЕЛЬНЫЙ ОТЧЕТ ПО РЕЗУЛЬТАТАМ РАССЛЕДОВАНИЯ АВИАЦИОННОГО ПРОИСШЕСТВИЯ Вид авиационного происшествия Катастрофа Тип воздушного судна Самолет RRJ-95 (модель – RRJ-95B) Государственный и регистрационный опознавательные знаки RA-89098" (PDF). mak-iac.org. Retrieved 3 July 2019.
  19. ^ Кузнец, Дмитрий. Опубликован первый отчет о катастрофе суперджета. Как экипаж управлял аварийным самолетом? Почему он загорелся?. Meduza (in Russian). Retrieved 17 June 2019.
  20. ^ Kaminski-Morrow, David (15 June 2019). "Lightning-struck Superjet did not request storm avoidance". Flightglobal.com.
  21. ^ Kaminski-Morrow, David (15 June 2019). "Superjet accident probe studies heavy-handed pilot inputs". Flightglobal.com.
  22. ^ Luhn, Alec (7 May 2019). "Russia to investigate whether pilot error caused fiery emergency landing that killed 37". The Telegraph. Retrieved 16 May 2019.
  23. ^ "Раскрыты ошибки спасателей при тушении SSJ-100" ["Rescuers' mistakes when extinguishing SSJ-100 are revealed"]. Lenta.ru. Retrieved 14 May 2019.
  24. ^ O'Leary, Abigail (3 October 2019). "Pilot of doomed Russian plane that crashed killing 41 could face seven years in jail". Mirror Online. Retrieved 3 October 2019.
  25. ^ "Were lives lost at the cost of carry-ons in Aeroflot plane crash that killed 41?". USA TODAY.
  26. ^ Mzezewa, Tariro (6 May 2019). "In the Event of an Emergency, Leave Your Luggage on the Plane. Really". Retrieved 14 May 2019 – via NYTimes.com.
  27. ^ a b "What We Know About the Deadly Aeroflot Superjet Crash Landing". The Moscow Times. 6 May 2019. Retrieved 16 May 2019.
  28. ^ "Данные о проблемах с эвакуацией из SSJ-100 из-за ручной клади не подтвердились" [Data on evacuation problems from SSJ-100 due to hand luggage has not been confirmed]. TASS (in Russian). 11 May 2019. Retrieved 11 May 2019.
  29. ^ "ТАСС: версия о спасении багажа из сгоревшего SSJ-100 ценой жизней людей не подтвердилась" [TASS: the version about saving luggage from the burnt SSJ-100 at the cost of people's lives was not confirmed]. NEWSru.com (in Russian). 11 May 2019. Retrieved 11 May 2019.
  30. ^ ""Я снял, как горел наш самолёт": пассажир Sukhoi Superjet 100 рассказал о смертельном рейсе" ["I shot movie while our plane was burning": a passenger of the Sukhoi Superjet 100 told about the deadly flight] (in Russian). 14 May 2019. Retrieved 14 May 2019.
  31. ^ ""Я смотрел в иллюминатор и думал: мы сейчас взорвемся или нет?"" ["I looked out the window and thought: are we going to explode or not?"]. Сибирь. Реалии (in Russian). Retrieved 16 May 2019.
  32. ^ "Aeroflot to pay compensation to all passengers, victim's families after plane crash". TASS (in Russian). Retrieved 13 May 2019.
  33. ^ "Report: Brakes unused on fiery Russian plane that killed 41". Washington Post (2019-05–17). Associated Press.
  34. ^ "Новости компании - Аэрофлот опровергает информацию о нарушении инструкций экипажем рейса SU1492 - Аэрофлот" ["Company News - Aeroflot denies information about violation of instructions by flight crew SU1492 - Aeroflot"]. www.aeroflot.ru. Retrieved 20 May 2019.
  35. ^ "Песков: приостановить эксплуатацию Sukhoi Superjet могут только авиационные органы" [(President of the Russian Federation Dmitry) Peskov: (the decision to) suspend operation of the Sukhoi Superjet can be made only by the competent aviation authorities (and not by citizens who sign petitions on the Change.org portal)"]. ТАСС.
  36. ^ "Петицию за запрет полетов SSJ 100 подписали больше 130 000 человек - Общество" [More than 130,000 people have signed a petition for banning SSJ 100 flights - Society]. Forbes.ru. 7 May 2019.
  37. ^ "Aeroflot plane crash: Pilot error theory probed". BBC. 7 May 2019. Retrieved 7 May 2019.
  38. ^ "SSJ 100 придержали на земле" – via Kommersant.
  39. ^ "Russia's Aeroflot Cancels Dozens of Flights Following Tragic Plane Crash". The Moscow Times. 13 May 2019. Retrieved 16 May 2019.
  40. ^ "Все пассажиры рейса в Москву отказались от полета на SSJ-100" [All passengers in the flight to Moscow refused to fly on the SSJ-100]. Lenta.ru (in Russian). Retrieved 20 May 2019.
  41. ^ Prokopovič, Karolina. "RusLine Ditches its Big Superjet 100 Plans". Aviation Voice. Retrieved 20 May 2019.
  42. ^ "Ту-134 отправился в заключительный пассажирский рейс в России" [Tu-134 went to the final passenger flight in Russia] (in Russian). 22 May 2019. Retrieved 26 May 2019.
  43. ^ Костринский, Герман (28 May 2019). "Superjet просят проверить с нуля. АЭВТ требует подтвердить надежность самолета" [There is a request to check Superjet from the very beginning. AEVT requires confirmation of aircraft reliability]. Газета "Коммерсантъ" (in Russian) (90). p. 7. Retrieved 29 May 2019.

External links

2019 Boeing B-17 Flying Fortress crash

On October 2, 2019, a Boeing B-17 Flying Fortress owned by the Collings Foundation crashed at Bradley International Airport, Windsor Locks, Connecticut, United States. Seven of the thirteen people on board were killed, and the other six, as well as one person on the ground, were injured. The aircraft was destroyed by fire, with only the tail and a portion of one wing remaining.

2019 Colombia DC-3 crash

On 9 March 2019 a Douglas DC-3 operated by Latinoamericana de Servicios Aereo (Laser Aéreo) crashed near San Carlos de Guaroa, Colombia. The plane was on a flight from Jorge Enrique González Torres Airport, San José del Guaviare to La Vanguardia Airport, Villavicencio. All 14 people on board were killed, including the mayor of Taraira, Doris Villegas. The crew were attempting to land at Villavicencio and had just declared an emergency.

2019 George Inlet, Alaska mid-air collision

On 13 May 2019, a de Havilland Canada DHC-2 Beaver floatplane operated by Mountain Air Service collided with a Taquan Air de Havilland Canada DHC-3 Turbine Otter floatplane over George Inlet, Alaska, United States. The DHC-2 broke up in mid-air with the loss of the single pilot and all 4 passengers. The DHC-3 pilot was able to maintain partial control, but the aircraft suffered substantial damage in the collision and the subsequent forced landing; the pilot suffered minor injuries, 9 passengers suffered serious injuries, and 1 passenger was killed. Both aircraft were conducting sightseeing flights. The cause of the accident is under investigation by the National Transportation Safety Board (NTSB).

2019 Indian Air Force An-32 crash

On 3 June 2019, an Antonov An-32 twin engine turboprop transport aircraft of the Indian Air Force en route from Jorhat Airport in Assam to Mechuka in Arunachal Pradesh lost contact with ground control about 33 minutes after takeoff. There were 13 people on board. After a week-long search operation, the wreckage with no survivors was found near Pari hills close to Gatte village in Arunachal Pradesh at the elevation of 12000 feet.

2019 New York City helicopter crash

On June 10, 2019, an Agusta A109E Power crashed onto the AXA Equitable Center on Seventh Avenue in Manhattan, New York City, which sparked a fire on the top of the building. The helicopter involved in the accident, N200BK, was destroyed. The only occupant, the pilot, Tim McCormack, died in the crash. The aircraft was privately owned at the time of the crash.The flight originated from the East 34th Street Heliport (FAA LID: 6N5) at approximately 1:32 PM EDT bound for Linden, New Jersey. At around 1:43 PM EDT on June 10, 2019, the helicopter, an Agusta A109E Power, registration N200BK, crashed on the roof of the AXA Equitable Center, sparking a fire on the top of the building. The first emergency call was made at 1:43 PM. The FDNY has considered the accident as a "hard landing." The fire on the top of the highrise was extinguished quickly.

After the accident, New York City Mayor Bill de Blasio briefed the press, confirming a lack of further victims or apparent terroristic motive. The National Transportation Safety Board sent agents to investigate the accident. The accident prompted Mayor de Blasio to call for a ban on non-emergency helicopters flying over Manhattan. Former City Parks Commissioner Adrian Benepe countered that the mayor had the authority to eliminate ninety percent of helicopter traffic by himself by eliminating the more than 200 daily tourist and charter flights from city-owned heliports.

2019 Northrop N-9M crash

On April 22, 2019, a Northrop N-9MB aircraft crashed in Norco, California, United States, killing the pilot. The aircraft was the last survivor of four built. It was destroyed in the post-crash fire.

2019 Pakistan Army military plane crash

On 30 July 2019, a Beechcraft King Air of the Pakistan Army crashed near Bahria Town, Rawalpindi. All five crew members, as well as 13 civilians, were killed when the plane crashed into a residential area.

2019 Saha Airlines Boeing 707 crash

On 14 January 2019, a Boeing 707 operated by Saha Airlines on a cargo flight crashed at Fath Air Base, near Karaj, Alborz Province in Iran. Fifteen of the 16 people on board were killed. This aircraft was also the last civil Boeing 707 in operation.

2019 Taplejung helicopter crash

On February 27, 2019, Air Dynasty's Eurocopter AS350 B3e carrying six passengers and one pilot was scheduled to travel on a domestic flight from Pathibhara Devi Temple in Taplejung to Chuhandanda in Tehrathum, Nepal. The aircraft crashed at approximately 1.30 p.m. (NPT) due to bad weather in Taplejung. All seven people on board died in the crash, including Nepal's Minister for Tourism and Civil Aviation Rabindra Prasad Adhikari.

2019 in Russia

Events in the year 2019 in Russia.

Angara Airlines Flight 200

Angara Airlines Flight 200 was a domestic scheduled flight from Ulan-Ude Airport to Nizhneangarsk Airport, Russia. On 27 June 2019, the Antonov An-24RV aircraft operating the flight suffered an engine failure on take-off. On returning to Nizhneangarsk, the aircraft departed the runway and collided with a building. All 43 passengers survived the crash whilst two of the four crew, the pilot and flight engineer, were killed.

Biman Bangladesh Airlines Flight 147

Biman Bangladesh Airlines Flight 147 was a scheduled flight from Shahjalal International Airport, Bangladesh to Dubai International Airport via Chittagong on 24 February 2019. The aircraft, a Biman Bangladesh Airlines Boeing 737-800, was hijacked 252 kilometres (157 mi) South-East of Dhaka by lonewolf terrorist Polash Ahmed. The flight performed emergency landing at the Shah Amanat International Airport in Chittagong. Ahmed was shot dead by Bangladeshi special forces. No casualties of passengers or crew were reported although one flight attendant was shot at.

Biman Bangladesh Airlines Flight 60

Biman Bangladesh Airlines Flight 60 was a scheduled international passenger flight from Dhaka Hazrat Shah Jalal International Airport, Bangladesh to Yangon International Airport, Myanmar. On May 8, 2019, the Bombardier Q400 aircraft, skidded off the runway upon landing, breaking into three sections. There were no fatalities, but 18 of the 28 passengers on board including 5 crew members were injured: the aircraft was also declared a hull loss, making it the tenth loss of a Q400 aircraft.

Bounced landing

In aviation, a bounced landing is a behavior of an aircraft that can develop after aircraft touching the runway or water surface, and defined as all aircraft wheels or floats briefly and sometimes repeatedly losing contact with the runway or water surface during landing. It should not be confused with aquaplaning or touch-and-go landing.

Kristian Kostov

Kristian Konstantinov Kostov (Bulgarian: Кристиан Константинов Костов, Russian: Кристиа́н Константи́нов Ко́стов; born 15 March 2000) is a Bulgarian-Russian singer. He was a finalist in season one of The Voice Kids Russia and a runner-up in the fourth season of X Factor Bulgaria. He represented Bulgaria in the Eurovision Song Contest 2017 with the song "Beautiful Mess", finishing in 2nd place. In January 2018, Kostov won the EBBA Public Choice award. In January 2019, Kostov was one of seven first batch singers who would be performing in the seventh season of Hunan Television's singing reality-competition Singer (previously I Am a Singer).

Miami Air Flight 293

Miami Air Flight 293 was a military charter from Guantanamo Bay to Naval Air Station Jacksonville, operated by Miami Air International. On 3 May 2019, the Boeing 737-800 aircraft operating the flight overshot the runway on landing. Twenty-one people were injured. The aircraft was written off, making it the 17th loss of a Boeing 737-800.

Skydive Umeå Gippsland GA8 Airvan crash

On 14 July 2019, a Gippsland GA8 Airvan crashed on a river islet in Sweden, killing all nine people on board. Structural failure of a wing is suspected as the cause of the accident. Consequently, the Gippsland GA8 Airvan was grounded by the Civil Aviation Safety Authority (CASA) in Australia, the Civil Aviation Authority (CAANZ) in New Zealand and the European Aviation Safety Agency (EASA) in the European Union.

The grounding order was issued on 20 July and was due to run until 3 August, but was lifted early as CASA found there is no evidence for an unsafe condition, and the EASA said the wrecked aircraft had been exposed to aerodynamic loads beyond certification.

Taquan Air Flight 20

Taquan Air Flight 20 is a regularly scheduled commuter flight operated by Taquan Air from Ketchikan Harbor Seaplane Base to Metlakatla Seaplane Base. On 20 May 2019, the de Havilland Canada DHC-2 Beaver floatplane operating the flight overturned in the harbor in Metlakatla, Alaska, United States during a water landing, destroying the aircraft and killing both persons aboard. The cause of the crash is under investigation.

Ural Airlines Flight 178

Ural Airlines Flight 178 is a Ural Airlines scheduled passenger flight from Moscow–Zhukovsky to Simferopol, Crimea. On 15 August 2019, the Airbus A321 operating the flight carried 226 passengers and seven crew. The flight suffered a bird strike after taking off from Zhukovsky and crash landed in a cornfield, 5 kilometres (3.1 mi; 2.7 nmi) past the airport. All on board survived; 74 people sustained injuries, but none were severe.

Aviation accidents and incidents in the Soviet Union and Russia
1950s
1960s
1970s
1980s
1990s
2000s
2010s

Languages

This page is based on a Wikipedia article written by authors (here).
Text is available under the CC BY-SA 3.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.