Crash of a PZL-Mielec AN-2R in Šiauliai

Date & Time: Feb 20, 1990
Type of aircraft:
PZL-Mielec AN-2
Operator:
Registration:
CCCP-56472
Flight Phase:
Flight
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Plain, Valley
MSN:
1G182-29
YOM:
1978
Location:
Šiauliai
Apskritis of Šiauliai
Country:
Lithuania
Region:
Europe
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances. There were no casualties.

Crash of a Douglas DC-9-32 in Mahón

Date & Time: Feb 17, 1990 at 2030 LT
Type of aircraft:
Douglas DC-9
Operator:
Registration:
EC-BIQ
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
Palma de Mallorca - Mahón
MSN:
47092
YOM:
1967
Location:
Mahón
Balearic Islands
Country:
Spain
Region:
Europe
Crew on board:
7
Crew fatalities:
Pax on board:
82
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Mahón Airport was completed by night and poor weather conditions. On final, the crew lost visual contact with the runway and the captain instructed the pilot to initiate a go-around. In a certain confusion, the aircraft continued its approach until it struck the runway surface with a positive acceleration of 3,56 G. The captain took over control, initiated a go-around and decided to return to Palma de Mallorca where a safe landing wa completed. All 89 occupants evacuated safely while the aircraft was considered as damaged beyond repair due to severe structural damages.
Probable cause:
It was determined that the copilot (pilot-in-command) did not understand the captain's instructions to initiate a go-around procedure due to non standard phraseology used by the captain. Poor crew coordination and lack of visibility were considered as contributing factors.

Crash of an Airbus A320-231 in Bangalore: 92 killed

Date & Time: Feb 14, 1990 at 1303 LT
Type of aircraft:
Airbus A320
Operator:
Registration:
VT-EPN
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
Bombay - Bangalore
MSN:
79
YOM:
1989
Flight number:
IC605
Location:
Bangalore-Hindustan
Karnataka
Country:
India
Region:
Asia
Crew on board:
7
Crew fatalities:
Pax on board:
139
Pax fatalities:
Other fatalities:
Total fatalities:
92
Captain / Total flying hours:
10339
Captain / Total hours on type:
212.00
Copilot / Total flying hours:
9307
Copilot / Total hours on type:
68
Aircraft flight hours:
370
Aircraft flight cycles:
302
Circumstances:
Indian Airlines Flight 605 took off from Mumbai, India, at 11:58 for a domestic flight to Bangalore. At 12:25 Bangalore approach was contacted and prevailing weather was passed on to the crew (wind variable 5 knots, visibility 10 km, clouds 2 octa 2,000 feet, temperature 27° C, QNH 1018). At 12:44 the aircraft was cleared to descend to FL110. Reaching FL110, vectors were given for a visual runway 09 approach. On final approach, the aircraft descended well below the normal approach profile and kept descending until it struck the boundaries of the Karnataka Golf Club (2,300 feet short of the runway and 200 feet right of the extended centerline. The aircraft rolled for 80 feet and lifted off again for about 230 feet and came down again on the 17th green of the golf course. The landing gear wheels dug into the ground and the aircraft impacted a 12 feet high embankment, causing the gears and engines to be sheared off. The aircraft continued over the embankment and came to rest in a grassy, marshy and rocky area.
Probable cause:
Failure of the pilots to realize the gravity of the situation and respond immediately towards proper action of moving the throttles, even after the radio altitude call-outs of "Four hundred", "Three hundred" and "Two hundred" feet, in spite of knowing that the plane was in idle/open descent mode. However, identification of the cause for the engagement of idle/open descent mode in short final approach during the crucial period of the flight is not possible.
Final Report:

Crash of a Fokker F27 Friendship 200 in Bauru: 3 killed

Date & Time: Feb 12, 1990 at 0929 LT
Type of aircraft:
Fokker F27 Friendship
Operator:
Registration:
PT-LCG
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
São Paulo – Bauru – Araçatuba
MSN:
10206
YOM:
1962
Location:
Bauru
São Paulo
Country:
Brazil
Region:
South America
Crew on board:
3
Crew fatalities:
Pax on board:
38
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The aircraft departed São Paulo-Congonhas Airport on a domestic schedule flight to Araçatuba with an intermediate stop in Bauru. The pilot-in-command was a captain under training, accompanied by an instructor and a third pilot. Because the Brasilia ARTCC frequency was congested, the crew was cleared to initiate the descent from FL140 at a distance of 50 km from Bauru Airport instead of the standard 74 km. This caused the aircraft to approach at an excessive speed and as the captain estimated the situation as unsafe, he prefered to initiate a go-around but the instructor decided to continue. Due to a lack of coordination between the captain and the instructor, it was not clear who would perform the landing but finally, the instructor took over control. Following a rate of descent of 2,500 feet per minute, the aircraft landed at a speed of 130 knots some 775 meters past the runway 32 threshold. After touchdown, the aircraft floated, causing the left and right main gear to land alternatingly. The instructor realized that he would not be able to stop the aircraft within the remaining distance so he decided to initiate a go-around procedure and added full power. As this was against the published procedure and due to a lack of sufficient air in the engine in combination with a high angle of attack, the aircraft stalled after the engine failed to develop enough power. The aircraft crashed 600 meters past the runway end, struck vehicles and houses and came to rest in flames. One of the pilot and two people in car were killed. All other occupants were rescued, among them three were seriously injured. The aircraft was destroyed.
Probable cause:
The accident was the consequence of a poor approach planning and wrong approach configuration.
The following contributing factors were reported:
- Deficiencies in crew training,
- Deficiencies in flight controls,
- Poor crew coordination,
- Poor judgment,
- Poor planning,
- Lack of supervision.

Crash of a PZL-Mielec AN-2TP in Vozhdoroma: 4 killed

Date & Time: Feb 1, 1990 at 1544 LT
Type of aircraft:
PZL-Mielec AN-2
Operator:
Registration:
CCCP-07207
Flight Phase:
Flight
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Plain, Valley
Schedule:
Rochegda – Bereznik – Arkhangelsk
MSN:
1G146-36
YOM:
1973
Flight number:
SU744
Location:
Vozhdoroma
Arkhangelsk oblast
Country:
Russia
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Aircraft flight hours:
13463
Aircraft flight cycles:
13919
Circumstances:
En route to Arkhangelsk, weather conditions deteriorated and the crew decided to continue rather than to return to Bereznik. After being cleared to descend to an altitude of 150 meters, the aircraft entered an area of poor visibility when the crew lost his orientation. This caused the aircraft to deviate from the prescribed routing when, shortly later, it struck the cable of an antenna located in a military zone, about one km from Vozhdoroma. The aircraft lost height and crashed 250 meters further, bursting into flames. All four occupants were killed.
Probable cause:
The decision of the crew to continue the flight under VFR mode in IMC conditions (below weather mimina conditions) at an unsafe altitude and the failure to return to the departure point.

Crash of an Antonov AN-24RV in Uliastay

Date & Time: Jan 26, 1990 at 2130 LT
Type of aircraft:
Antonov AN-24
Operator:
Registration:
BNMAU-10208
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Plain, Valley
Schedule:
Ulan Bator - Uliastay
MSN:
5 73 102 08
YOM:
1975
Location:
Uliastay
Zavkhan
Country:
Mongolia
Region:
Asia
Crew on board:
5
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Ulan Bator Airport at 1835LT, bound for Uliastay. On approach to Uliastay by night, the crew got lost and was unable to locate the airfield. The crew followed a holding pattern and three hours after takeoff, due to fuel shortage, he decided to make an emergency landing. The aircraft crash landed in a desert area located few km from the airport, slid on the ground, lost a wing and came to rest. All 30 occupants escaped uninjured.

Crash of a Boeing 707-321B in Cove Neck: 73 killed

Date & Time: Jan 25, 1990 at 2134 LT
Type of aircraft:
Boeing 707
Operator:
Registration:
HK-2016
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Plain, Valley
Schedule:
Bogotá – Medellín – New York
MSN:
19276/592
YOM:
1967
Flight number:
AV052
Location:
Cove Neck
New York
Country:
United States of America
Region:
North America
Crew on board:
9
Crew fatalities:
Pax on board:
149
Pax fatalities:
Other fatalities:
Total fatalities:
73
Captain / Total flying hours:
16787
Captain / Total hours on type:
1534.00
Copilot / Total flying hours:
1837
Copilot / Total hours on type:
64
Aircraft flight hours:
61764
Circumstances:
Avianca flight 052 (AV052), a Boeing 707-321B with Colombian registration HK-2016, crashed in a wooded residential area in Cove Neck, Long Island, NY. AV052 was a scheduled international passenger flight from Bogotá, Colombia, to New York-JFK Intl Airport, NY, with an intermediate stop at Jose Maria Cordova Airport, near Medellín, Columbia. Of the 158 persons aboard, 73 were fatally injured. Because of poor weather conditions in the northeastern part of the United States, the flightcrew was placed in holding 3 times by ATC for a total of about 1 hour and 17 minutes. During the 3rd period of holding, the flightcrew reported that the aircraft could not hold longer than 5 minutes, that it was running out of fuel, and that it could not reach its alternate airport, Boston-Logan Intl. Subsequently, the flightcrew executed a missed approach to JFK Intl Airport. While trying to return to the airport, the aircraft experienced a loss of power to all 4 engines and crashed approximately 21 miles northeast of JFK Airport.
Probable cause:
The failure of the flightcrew to adequately manage the airplane's fuel load, and their failure to communicate an emergency fuel situation to air traffic control before fuel exhaustion occurred. Contributing to the accident was the flightcrew's failure to use an airline operational control dispatch system to assist them during the international flight into a high-density airport in poor weather. Also contributing to the accident was inadequate traffic flow management by the faa and the lack of standardized understandable terminology for pilots and controllers for minimum and emergency fuel states. The safety board also determines that windshear, crew fatigue and stress were factors that led to the unsuccessful completion of the first approach and thus contributed to the accident.
Final Report:

Crash of an Avro 748-2-207 on Mt Rinjani: 19 killed

Date & Time: Jan 25, 1990
Type of aircraft:
Avro 748
Operator:
Registration:
PK-OBW
Flight Phase:
Flight
Flight Type:
Scheduled Revenue Flight
Survivors:
No
Site:
Mountains
Schedule:
Ujung Pandang - Lombok
MSN:
1567
YOM:
1964
Location:
Mt Rinjani
West Nusa Tenggara
Country:
Indonesia
Region:
Asia
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
Following an uneventful flight from Ujung Pandang (Makassar), the crew started the descent to Lombok Airport when he encountered poor weather conditions with heavy rain falls. The captain was cleared by ATC to divert to Mataram-Selaparang Airport when, in limited visibility, the aircraft struck the slope of Mt Rinjani located on north part of the island. The aircraft was destroyed upon impact and all 19 occupants were killed.
Probable cause:
Controlled flight into terrain after the crew continued the approach at an unsafe altitude in poor weather conditions.

Crash of a PZL-Mielec AN-2R in Kurkachi

Date & Time: Jan 16, 1990
Type of aircraft:
PZL-Mielec AN-2
Operator:
Registration:
CCCP-05703
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
MSN:
1G153-16
YOM:
1974
Location:
Kurkachi
Republic of Tatarstan
Country:
Russia
Region:
Asia
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While approaching Kurkachi Airport, the engine failed. The crew attempted an emergency landing when the aircraft collided with the mast of a high-voltage powerline and crashed. All 13 occupants were injured and the aircraft was destroyed.
Probable cause:
Engine failure on approach after a newspaper had blocked the air intake.

Crash of a Swearingen SA227AC Metro III in Elko

Date & Time: Jan 15, 1990 at 1028 LT
Type of aircraft:
Swearingen SA227 Metro III
Operator:
Registration:
N2721M
Flight Phase:
Landing (descent or approach)
Flight Type:
Scheduled Revenue Flight
Survivors:
Yes
Site:
Airport (less than 10 km from airport)
Schedule:
Salt Lake City - Elko
MSN:
AC-716
YOM:
1988
Flight number:
OO5855
Location:
Elko
Nevada
Country:
United States of America
Region:
North America
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14314
Captain / Total hours on type:
5337.00
Aircraft flight hours:
2928
Circumstances:
During arrival, the flight crew of SkyWest Airlines flight 5855 requested a VOR/DME-B approach to the Elko Airport, which was approved. As the approach continued, the flight crew reported over the Bullion VOR. Approximately 30 seconds later, the aircraft crashed. Impact occurred at the top of a mountain, about 100 feet before reaching the VOR station. Elevation of the crash site was about 6,460 feet; minimum published crossing altitude at the VOR was 7,000 feet. The airport was 4.1 miles from the VOR at an elevation of 5,135 feet.
Probable cause:
Improper ifr procedure by the captain, and inadequate monitoring of the approach by the first officer, which resulted in a failure to maintain proper altitude during the approach. Factors related to the accident were: the terrain and weather conditions at the accident site.
Final Report:
Subscribe to Scheduled Revenue Flight