Crash of an Antonov AN-124-100 in Novosibirsk

Date & Time: Nov 13, 2020 at 1210 LT
Type of aircraft:
Operator:
Registration:
RA-82042
Flight Type:
Survivors:
Yes
Schedule:
Seoul - Novosibirsk - Vienna
MSN:
9773054055093
YOM:
1991
Flight number:
VI4066
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine airplane departed Seoul-Incheon Airport on a cargo flight to Vienna, with an intermediate stop in Novosibirsk, carrying 14 crew members and a load consisting of 84 tons of automobile parts. Shortly after takeoff from runway 25 at Novosibirsk-Tolmachevo Airport, while in initial climb, a catastrophic failure occurred on the engine n°2. Several debris punctured the fuselage, damaging slats on both left and right side. As a result, radio communications were cut, the power supply failed and the thrust control on all three remaining engines dropped. The crew entered a circuit for an immediate return despite the aircraft was in an overweight condition for an emergency landing. After touchdown on runway 25 that offered an LDA of 3,597 metres, the crew started the braking procedure but the aircraft was unable to stop within the remaining distance. It overran, lost its both nose gears and slid in a snow covered field before coming to rest 300 metres further. All 14 occupants evacuated safely and the aircraft seems to be damaged beyond repair.
Probable cause:
Failure of the high pressure compressor disk on the engine n°2 during the takeoff procedure.

Crash of a Cessna 550 Citation Bravo in Vienna

Date & Time: Sep 3, 2015 at 1227 LT
Type of aircraft:
Operator:
Registration:
OE-GLG
Survivors:
Yes
Schedule:
Salzburg - Vienna
MSN:
550-0977
YOM:
2001
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
1800.00
Copilot / Total flying hours:
1200
Copilot / Total hours on type:
350
Aircraft flight hours:
7525
Aircraft flight cycles:
5807
Circumstances:
Following an uneventful flight from Salzburg, the crew was cleared to descent to Vienna-Schwechat Airport. On approach to runway 34, the crew completed the checklist and lowered the landing gear when he realized the the left main gear remained stuck in its wheel well and that the green light failed to come on on the cockpit panel. The crew agreed to continue. After touchdown on runway 34, the aircraft deviated to the left, veered off runway and came to rest in a grassy area located near taxiway D and taxiway B5 and B6. All five occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident was caused by a metallic foreign body between valve seat and ball of the spring loaded ball check valve in the undercarriage servo valve of the left main landing gear caused the check valve not to close as intended and hydraulic fluid was directed directly to the landing gear cylinder without moving the piston rod. Due to the fact that the piston rod of the undercarriage servo valve did not move as intended, the mechanical unlocking hook of the left undercarriage was also not controlled - the landing gear was therefore not deployed.
Contributing factors:
- The possibility to abort the approach, to Go Around and fly a holding to carry out troubleshooting, as described in the operations manual of the aviation company as well as in the "Emergency / Abnormal Procedures" manual of the aircraft manufacturer, was not used.
- The emergency extension system of the landing gear was not used.
Final Report:

Crash of a Dassault Falcon 100 in Samedan: 2 killed

Date & Time: Feb 12, 2009 at 1612 LT
Type of aircraft:
Operator:
Registration:
VP-BAF
Flight Type:
Survivors:
Yes
Schedule:
Vienna - Samedan
MSN:
210
YOM:
1987
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
17269
Captain / Total hours on type:
739.00
Copilot / Total flying hours:
2591
Copilot / Total hours on type:
119
Aircraft flight hours:
6386
Circumstances:
On 12 February 2009, the Marcel Dassault/Bréguet Aviation Falcon 10 aircraft, registration VP-BAF, took off at 14:06 UTC from Vienna (LOWW) on a private flight under instrument flight rules (IFR) and an ATC flight plan Y, to Samedan (LSZS). Two crew members and one passenger were on board. After an uneventful flight, the IFR flight plan was cancelled at 14:56:32 UTC and the flight continued under visual flight rules (VFR). Over Samedan the crew were informed by the Samedan airport flight information service officer (FISO) that snow clearance work would be taking place on the runway and that they should expect a ten-minute delay. After approximately 15 minutes the crew initiated the approach. On landing, the aircraft made first contact with the ground by scraping the right wing on the left half of the runway and subsequently touched down with the right, and then the left main landing gear. It then drifted to the left and the left wing tip scraped a bank of snow running parallel to the runway. As a result it rotated anti-clockwise around its vertical axis and crashed into a frozen bank of snow about four metres high. The aircraft broke into two pieces as a result of the force of the impact. The two pilots suffered fatal injuries on the impact. The passenger was seriously injured. The aircraft was destroyed. Fire did not break out.
Probable cause:
The accident is attributable to the fact that the crew wanted to make a landing with inadequate visual references from an unfavorable initial position and as a result, after touchdown the aircraft collided with a snowbank running along the runway.
The following factors contributed to the accident:
• The rapidly changing weather conditions on the mountain aerodrome of Samedan were misjudged by the crew.
• A coordinated crew working method in terms of crew resource manage-ment was missing.
• The deactivation of the EGPWS, which meant that acoustic messages con-cerning the aircraft’s height above ground and bank angle were no longer available in the final phase of the approach up to the first contact with the runway.
• A snowbank up to four metres high ran along the edge of the runway.
Final Report:

Crash of an Airbus A310 in Vienna, Austria

Date & Time: Jul 12, 2000 at 1334 LT
Type of aircraft:
Operator:
Registration:
D-AHLB
Survivors:
Yes
Schedule:
Hania - Hanover
MSN:
0528
YOM:
1990
Flight number:
HF3378
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
143
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23400
Copilot / Total flying hours:
2850
Aircraft flight hours:
41307
Aircraft flight cycles:
13789
Circumstances:
After takeoff from Chania-Souda Airport, the crew reported technical problems with the right main gear that could not be raised properly in its wheel well. The captain decided to continue to Munich in a gear down configuration but the fuel consumption increased. En route, the crew realized he could not make it to Munich so diverted to Vienna-Schwechat Airport. At a distance of about 12 NM from the airport, at an altitude of 4,000 feet, both engines failed due to fuel exhaustion. One of the engine could be restarted for a short period of time but on short final, the aircraft stalled and struck the ground (a grassy area) about 500 metres short of runway 34. The left main gear broke off, the aircraft slid for some 600 metres then veered to the left and came to rest on its left wing. All 151 occupants were rescued, among them 26 passengers were slightly injured. The aircraft was damaged beyond repair.
Probable cause:
Continuation of the flight with a landing gear problem until the engines failed due to fuel exhaustion.
The following findings were identified:
Crew:
- Failure to comply with the company's rules on fuel reserves, caused by several human factors, with extreme workload and stress being the important factor (loss of situational awareness).
- Determination of the fuel reserves using only the FMS, which, due to its characteristics did not take into account the additional fuel consumption.
- Failure to develop alternative strategies to curb the fuel problem.
- Failure to comply with a fuel warning (low fuel level warning) and decision to continue the flight to Vienna International Airport, although the plane was in the immediate vicinity of Zagreb Airport.
Manufacturer:
- Inadequate and misleading documentation (FMS scheme, altitude, terms) for this specific case, particularly in relation to the restriction of FMS.
Operator:
- Inadequate documentation for "abnormal landing gear up indication" of the abnormal checklist.
- Lack of review of the fuel needs by the Operations Division.
Contributing factors:
- Missing or inadequate preventive measures by manufacturers, approving authority and airlines following the previous publications of ICAO and EU DG VII about problems which, with the introduction of aircraft equipped with modern technologies, occurred and had been identified.
- Anthropo-technical construction deficiencies, which favour a misinterpretation of the FMS EFOB display.
Final Report:

Crash of a Cessna 340 in Vienna

Date & Time: Oct 29, 1995 at 2252 LT
Type of aircraft:
Registration:
N5736M
Flight Type:
Survivors:
Yes
Schedule:
Barcelona - Vienna
MSN:
340-0039
YOM:
1972
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On October 29, 1995, about 2152 Universal Coordinated Time, a Cessna 340, N5736M, collided with the ground during an instrument landing system approach at Vienna, Austria. The airplane was operated by Austrian Cessna Aviation, Inc. under the provisions of 14 CFR Part 91, and instrument flight rules. Instrument meteorological conditions prevailed. An instrument flight rules flight plan was filed for the personal flight. The private, instrument-rated pilot, and the five passengers had minor injuries, and the airplane was destroyed by a post-crash fire. The flight departed Barcelona, Spain, about 1810 on the same day.

Crash d'un Cessna 421C Golden Eagle III in Heidelberg: 4 killed

Date & Time: Nov 24, 1994 at 1645 LT
Operator:
Registration:
D-IACH
Survivors:
No
Site:
Schedule:
Vienna - Mannheim
MSN:
421C-0672
YOM:
1979
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The twin engine aircraft was approaching Mannheim Airport following an uneventful flight from Vienna-Schwechat. The pilot encountered poor visibility due to fog and failed to realize his altitude was too low when the aircraft struck a tall tree, stalled and crashed in a wooded area, bursting into flames. The wreckage was found on the slope of Mt Königstuhl, east of Heidelberg, about 17 km southeast of Mannheim Airport. A passenger was seriously injured while three other occupants were killed. Two weeks later, on December 7, the only survivor died from his injuries. On board were two pilots aged 34 and 29, and two passengers, Otto Rüdiger and Klaus O. Fleck, both head corporate of the Südzucker Group.

Crash of a Socata TBM-700 near Wieden: 6 killed

Date & Time: Apr 2, 1993 at 1231 LT
Type of aircraft:
Operator:
Registration:
OE-EDU
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Freiburg im Breisgau - Vienna
MSN:
73
YOM:
1993
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The single engine aircraft departed Freiburg im Breisgau Airport at 1216LT on a flight to Vienna-Schwechat Airport, carrying five passengers and one pilot. About 15 minutes later, after he reached the assigned altitude of 8,000 feet, the aircraft entered an uncontrolled descent and crashed in Wiedener Eck, near Wieden. The aircraft disintegrated on impact and all six occupants were killed. At the time of the accident, weather conditions were poor with snow falls and mist. The pilot did not send any distress call.

Crash of a Mitsubishi MU-2B-60 Marquise near Beucherling: 1 killed

Date & Time: Jan 22, 1993
Type of aircraft:
Registration:
N407MA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Cologne - Vienna
MSN:
1503
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
While in cruising altitude in a flight from Cologne-Bonn to Vienna, the pilot lost control of the airplane that entered a dive. He was able to send a brief maybay message but give no indication about the situation he was facing. The aircraft crashed in a field located near Beucherling and was destroyed. The pilot, sole on board, was killed.

Crash of a Cessna 425 Conquest I in Hanover: 7 killed

Date & Time: Oct 8, 1991
Type of aircraft:
Registration:
OE-FPS
Survivors:
No
Schedule:
Vienna - Hanover
MSN:
425-0024
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
On approach to Hanover-Langenhagen Airport, the pilot encountered poor visibility due to foggy conditions. Unable to locate the runway, he decided to initiate a go-around procedure when the aircraft lost height and crashed 200 metres short of runway 27R. The aircraft was destroyed and all seven occupants were killed. At the time of the accident, the visibility was reduced to 400 metres due to fog.
Probable cause:
It is believed that the pilot lost control of the aircraft while initiating a go-around procedure following an asymmetric thrust (the left engine apparently oversped).

Crash of a Boeing 767-3Z9ER near Phu Toey: 223 killed

Date & Time: May 26, 1991 at 2317 LT
Type of aircraft:
Operator:
Registration:
OE-LAV
Flight Phase:
Survivors:
No
Schedule:
Hong Kong - Bangkok - Vienna
MSN:
24628
YOM:
1989
Flight number:
NG004
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
213
Pax fatalities:
Other fatalities:
Total fatalities:
223
Captain / Total flying hours:
11750
Copilot / Total flying hours:
6500
Aircraft flight hours:
7444
Aircraft flight cycles:
1135
Circumstances:
Lauda Air Flight 004 (NG004) was a scheduled passenger flight from Hong Kong to Vienna, Austria with an en route stop in Bangkok, Thailand. The flight departed Bangkok at 1602 hours on May 26, 1991 for the final flight sector to Vienna Austria. All pre-flight, ground, and flight operations appear routine until five minutes and forty five seconds after the cockpit voice recorder (CVR) recorded the sounds of engine power being advanced for takeoff. At this point a discussion ensued between the crew members regarding an event later identified as a crew alert associated with a thrust reverser isolation valve. The crew discussed this alert for some four and one half minutes. The Quick Reference Handbook (QRH) was consulted to determine appropriate crew actions in response to the alert. No actions were required, and none were identified as being taken. Ten minutes and twenty seconds into the flight the co-pilot advised the pilot-in-command of the need for rudder trim to the left. The pilot-in-command acknowledged the co-pilot's statement. Fifteen minutes and one second into the flight, the co-pilot stated "ah reverser's deployed." Sounds similar to airframe shuddering were then heard on the CVR. Twenty nine seconds later the CVR recording ended with multiple sounds thought to be structural breakup. Flight conditions were recovered from non-volatile memory in the left engine electronic engine control (EEC). At the suspected point of reverser deployment, the EEC readout indicated that the airplane was at an approximate altitude of 24,700 feet, a speed of Mach 0.78, and developing climb power. The airplane crashed in mountainous jungle terrain at 14 degrees 44 minutes North latitude and 99 degrees 27 minutes East longitude at approximately 1617 hours. Night time visual meteorological conditions prevailed. All 223 occupants were killed.
Probable cause:
The Accident Investigation Committee of the Government of Thailand determines the probable cause of this accident to be uncommanded in-flight deployment of the left engine thrust reverser, which resulted in loss of flight path control. The specific cause of the thrust reverser deployment has not been positively identified.
Final Report: