Crash of a De Havilland DHC-6 Twin Otter 200 in Paulatuk: 2 killed

Date & Time: Dec 17, 1983 at 1310 LT
Registration:
C-FGJK
Survivors:
Yes
Schedule:
Inuvik - Paulatuk
MSN:
213
YOM:
1969
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On approach to Paulatuk Airport, the pilot encountered marginal weather conditions with strong cross winds and blowing snow. On short final, while making a transition from visual to instruments flight rules, the pilot decided to initiate a go-around when the left wing struck the ground. Out of control, the aircraft veered to the left and came to rest. The pilot and a passenger were killed while 10 other occupants were injured.
Probable cause:
It was determined that the accident was the consequence of the combination of the following factors:
- The Paulatuk aerodrome runway is not oriented to correspond with the prevailing winds,
- Environment Canada does not produce an aerodrome forecast for Paulatuk,
- As the aircraft landed, the crosswind from the right increased appreciably reducing visibility in blowing snow,
- During the overshoot, as the pilot was making the transition from visual to instrument flight conditions, control of the aircraft was lost,
- The aircraft was overloaded by 840 lbs.

Crash of a Douglas DC-9-32 in Madrid: 42 killed

Date & Time: Dec 7, 1983 at 0939 LT
Type of aircraft:
Operator:
Registration:
EC-CGS
Flight Phase:
Survivors:
No
Schedule:
Madrid - Santander
MSN:
47645
YOM:
1975
Flight number:
AO134
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
37
Pax fatalities:
Other fatalities:
Total fatalities:
42
Captain / Total flying hours:
13442
Captain / Total hours on type:
4096.00
Copilot / Total flying hours:
10322
Copilot / Total hours on type:
3655
Aircraft flight hours:
20078
Aircraft flight cycles:
17909
Circumstances:
Boeing 727-256 EC-CFJ of Iberia, operating scheduled flight IB350 to Rome, and DC-9-32 EC-CGS of Aviaco, operating schedule AO134 to Santander, crashed on runway 01/19 at Madrid-Barajas Airport. The Boeing 727 had been cleared for takeoff on runway 01 and was at V1 speed. The DC-9 had been cleared to proceed to the holding point at runway 01 through the outer taxiway. The accident occurred approximately at 09h39:29 on December 7, 1983. As a result of the impact and instant fire, the DC-9 aircraft was totally destroyed, dying the whole of its occupants, 5 crew members and 37 passengers. The Boeing 727 aircraft lost almost all of its left wing and main gear of the same side, sliding on the runway about 460 meters, until its final stop, remaining facing the opposite direction of takeoff, on the left edge of runway 01. As a result of the impact and of the spilling of fuel from the left wing, there was an almost instant fire at the time o the crash, which subsequently destroyed the aircraft. 34 passengers and 8 crew members out of the 84 passengers and 9 crew members, survived. 50 passengers and one assistance crew member died as a result of the impact and fire. The conditions of visibility at the airport were of daylight and intense fog.
Probable cause:
The cause of the accident was the unknown incursion of the DC-9 on the runway 01/19 when the Boeing 727 was on takeoff roll. The DC-9 was on the active runway because visibility conditions due to fog, by the zone where the aircraft was taxiing, impeded to the crew obtain sufficient visual references, to determine that, that was not the correct run that they should realize to reach the threshold of runway 01.
Final Report:

Crash of a Boeing 727-200 in Madrid: 51 killed

Date & Time: Dec 7, 1983 at 0939 LT
Type of aircraft:
Operator:
Registration:
EC-CFJ
Flight Phase:
Survivors:
Yes
Schedule:
Madrid - Rome
MSN:
20820
YOM:
1974
Flight number:
IB350
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
84
Pax fatalities:
Other fatalities:
Total fatalities:
51
Captain / Total flying hours:
8860
Captain / Total hours on type:
1919.00
Copilot / Total flying hours:
3474
Copilot / Total hours on type:
2840
Aircraft flight hours:
21525
Aircraft flight cycles:
19936
Circumstances:
Boeing 727-256 EC-CFJ of Iberia, operating scheduled flight IB350 to Rome, and DC-9-32 EC-CGS of Aviaco, operating schedule AO134 to Santander, crashed on runway 01/19 at Madrid-Barajas Airport. The Boeing 727 had been cleared for takeoff on runway 01 and was at V1 speed. The DC-9 had been cleared to proceed to the holding point at runway 01 through the outer taxiway. The accident occurred approximately at 09h39:29 on December 7, 1983. As a result of the impact and instant fire, the DC-9 aircraft was totally destroyed, dying the whole of its occupants, 5 crew members and 37 passengers. The Boeing 727 aircraft lost almost all of its left wing and main gear of the same side, sliding on the runway about 460 meters, until its final stop, remaining facing the opposite direction of takeoff, on the left edge of runway 01. As a result of the impact and of the spilling of fuel from the left wing, there was an almost instant fire at the time o the crash, which subsequently destroyed the aircraft. 34 passengers and 8 crew members out of the 84 passengers and 9 crew members, survived. 50 passengers and one assistance crew member died as a result of the impact and fire. The conditions of visibility at the airport were of daylight and intense fog.
Probable cause:
The cause of the accident was the unknown incursion of the DC-9 on the runway 01/19 when the Boeing 727 was on takeoff roll. The DC-9 was on the active runway because visibility conditions due to fog, by the zone where the aircraft was taxiing, impeded to the crew obtain sufficient visual references, to determine that, that was not the correct run that they should realize to reach the threshold of runway 01.
Final Report:

Crash of a Fokker F28 Fellowship 2000 in Enugu: 53 killed

Date & Time: Nov 28, 1983 at 1113 LT
Type of aircraft:
Operator:
Registration:
5N-ANF
Survivors:
Yes
Schedule:
Calabar - Enugu
MSN:
11090
YOM:
1975
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
66
Pax fatalities:
Other fatalities:
Total fatalities:
53
Aircraft flight hours:
10618
Aircraft flight cycles:
14149
Circumstances:
On final approach to Enugu Airport, the visibility was below minimums due to thick fog. The crew decided to continue the approach and descended below the MDA and below the glide until the airplane struck the ground in a relative flat attitude. Upon impact, the undercarriage were torn off and the aircraft slid on its belly for few dozen meters before coming to rest in flames about 3,3 km short of runway threshold. 53 people were killed while 19 others were seriously injured. The aircraft was destroyed.
Probable cause:
The decision of the crew to continue the approach in below-minima weather conditions until the aircraft impacted the ground. It was reported that the ILS system was unserviceable at the time of the accident.

Crash of a Boeing 747-283B in Madrid: 181 killed

Date & Time: Nov 27, 1983 at 0106 LT
Type of aircraft:
Operator:
Registration:
HK-2910
Survivors:
Yes
Schedule:
Frankfurt – Paris – Madrid – Caracas – Bogotá
MSN:
21381
YOM:
1977
Flight number:
AV011
Country:
Region:
Crew on board:
19
Crew fatalities:
Pax on board:
173
Pax fatalities:
Other fatalities:
Total fatalities:
181
Captain / Total flying hours:
23215
Captain / Total hours on type:
2432.00
Copilot / Total flying hours:
4384
Copilot / Total hours on type:
875
Aircraft flight hours:
20811
Aircraft flight cycles:
5800
Circumstances:
Following an uneventful flight from Paris-Roissy-CDG Airport, the crew was cleared to descent to Madrid-Barajas Airport runway 33. Once the altitude of 9,000 feet reached on descent, the crew was cleared to continue. At 0103LT, he was cleared to land on runway 33 and should complete a turn to the right. Following several errors on approach, the crew initiated a right turn prior to pass over the VOR, causing the aircraft to descent below the MDA. At an altitude of 2,247 feet and at a speed of 142 knots, the right main gear struck the top of a hill. Upon impact, the right main gear and the engine n°4 were torn off. Three seconds later, while in a 4,9° nose-up attitude, at a speed of 135 knots, the aircraft struck the top of a second hill. Then, six seconds later, the right wing struck the ground. The aircraft overturned and crashed upside down, bursting into flames. The wreckage was found 12 km from the runway threshold in an olive plantation. Eleven passengers (among them four members of the same family, father, mother and both children) were injured while 181 other occupants were killed, among them the Peruvian writer Manuel Scorza.
Probable cause:
Following a series of omissions and navigation errors on descent, the crew adopted a wrong approach configuration, causing the aircraft to descend below the MDA without proper visual contact with the runway until initial and final impact with the ground. The following contributing factors were reported:
_ Inaccurate navigation by the crew, which placed them in an incorrect position for initiating the approach manoeuvre,
- Failure of the crew to take corrective action after the GPWS alarm sounded in the cockpit,
- Poor crew coordination,
- Crew fatigue,
- Lack of ATC assistance during the last portion of the flight,
- Misinterpretation of ATC instructions on part of the flying crew,
- Lack of visibility due to the night.

Crash of a De Havilland DHC-6 Twin Otter 300 in Landsdowne House: 4 killed

Date & Time: Nov 23, 1983
Operator:
Registration:
C-GTLA
Survivors:
Yes
Schedule:
Sandy Lake – Landsdowne House – Thunder Bay
MSN:
632
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The Twin Otter was completing a schedule service from Sandy Lake to Thunder Bay with an intermediate stop in Landsdowne House, carrying five passengers and two pilots. On approach, the crew encountered marginal weather conditions and the captain decided to initiate a go-around procedure. A second circuit was completed without losing sight of the airfield. During the second attempt to land, the pilot-in-command reported 'runway in sight' and the copilot called for radioaltimer at 200 feet altitude. On short final, the captain reported he was encountering whiteout conditions when the airplane struck the snow-covered and icy surface of the lake about 1,200 feet short of runway threshold. Upon impact, the nose gear was torn off then the aircraft struck rocky terrain and eventually came to rest in flames about 600 feet short of runway. A passenger was seriously injured while both pilots escaped with minor injuries. Four passengers were killed in the accident.
Probable cause:
The accident occurred during a visual approach in reduced visibility and difficult weather conditions (white conditions). Investigations were unable to determine the exact cause of the accident resulting in a controlled flight into terrain.

Crash of a Tupolev TU-134A in Tbilisi: 8 killed

Date & Time: Nov 18, 1983
Type of aircraft:
Operator:
Registration:
CCCP-65807
Survivors:
Yes
Schedule:
Tbilisi - Batumi - Kiev - Leningrad
MSN:
3352108
YOM:
1973
Flight number:
SU6833
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
59
Pax fatalities:
Other fatalities:
Total fatalities:
7
Aircraft flight hours:
13273
Aircraft flight cycles:
10506
Circumstances:
En route from Tbilisi to Batumi, while in cruising altitude, seven hijackers (young Georgian people) elected to divert the aircraft to Turkey. Hijackers opened fire in the cabin and cockpit but the copilot was able to make sharp maneuvers, forcing the hijacker to leave the cockpit. The crew was able to return to Tbilisi Airport where security forces stormed the aircraft. Seven occupants, three crew members and four passengers (among them three hijackers) were killed. At least 63 bullets holes were found in the fuselage and the aircraft was considered as damaged beyond repair due to serious deformation of the structure caused by excessive g loads during an emergency descent.
Probable cause:
Structural damages caused by excessives g loads and bullets holes due to hijacking situation.

Crash of a Boeing 737-2M2 in Lubango: 130 killed

Date & Time: Nov 8, 1983 at 1520 LT
Type of aircraft:
Operator:
Registration:
D2-TBN
Flight Phase:
Survivors:
No
Schedule:
Lubango - Luanda
MSN:
22775
YOM:
1982
Location:
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
123
Pax fatalities:
Other fatalities:
Total fatalities:
130
Circumstances:
After takeoff from Lubango Airport, while in initial climb at an altitude of 200 feet, the aircraft was hit by a surface-to-air missile. The aircraft turned to the left then lost height and crashed in a huge explosion about 800 meters past the runway end. The aircraft disintegrated on impact and none of the 130 occupants survived the crash.
Probable cause:
Shot down by a UNITA SAM-7 surface-to-air missile.

Crash of a Let L-410UVP in Kansk

Date & Time: Oct 19, 1983
Type of aircraft:
Operator:
Registration:
CCCP-67315
Survivors:
Yes
Schedule:
Krasnoyarsk - Kansk
MSN:
82 08 15
YOM:
1982
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Krasnoyarsk-Severny Airport, the crew started the approach to Kansk-Tsentralny but was forced to divert to Kansk-Dalniy Airport due to poor weather conditions. Nevertheless, the crew landed in below-minima weather conditions at Dalniy Airport. After touchdown, the airplane was unable to stop within the remaining distance, overran, collided with an obstacle and came to rest. There were no casualties.

Crash of an Avro 748-FAA-2A near Pinckneyville: 10 killed

Date & Time: Oct 11, 1983 at 2053 LT
Type of aircraft:
Operator:
Registration:
N748LL
Flight Phase:
Survivors:
No
Schedule:
Chicago - Springfield - Carbondale
MSN:
1716
YOM:
1972
Flight number:
UX710
Crew on board:
3
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
5891
Captain / Total hours on type:
3170.00
Copilot / Total flying hours:
5119
Copilot / Total hours on type:
1746
Aircraft flight hours:
21182
Aircraft flight cycles:
32350
Circumstances:
Flight 710 departed Chicago, IL for a flight to Carbondale, IL via Springfield, IL. The flight was about 45 minutes behind schedule when it arrived at Springfield, about 20:05. At 20:11, the flightcrew were provided with the latest Carbondale weather: ceiling and visibility were 2,000 feet overcast and 2 miles, respectively, with light rain and fog. The crew then requested its IFR clearance, with 5,000 feet for its en route altitude. At 20:16, Flight 710 was cleared to taxi to runway 15 for takeoff. The aircraft took off at 20:20 and climbed to cruising altitude. At 20:21:34, Flight 710 informed the departure controller that it had experienced a "slight electrical problem..." and that it would keep the controller "advised." The flight then requested and was cleared to maintain 3,000 feet. At 20:23:54, the first officer told the captain that "the left (generator) is totally dead, the right (generator) is putting out voltage but I can't get a load on it." At 20:24:26, the first officer reported, "zero voltage and amps (amperes) on the left side, the right (generator) is putting out twenty-seven and a half (volts) but I can't get it to come on the line." The battery voltage further dropped to 22 volts. The crew a.o. shut off excess cabin lights because of the electrical problem. About 20:38, the first officer mistakenly isolated the right generator and right generator bus bar from the aircraft's dc electrical distribution system. Radio contact was lost when the flight was requested to change radio frequencies. At 20:52 the captain decided to descend to 2,400 feet and the voltage had further dropped to 13 volts. The aircraft continued to descend and struck the ground in an open pasture area.
Probable cause:
The captain's decision to continue the flight toward the more distant destination airport after the loss of d.c. electrical power from both aircraft generators instead of returning to the nearby departure airport. The captain's decision was adversely affected by self-imposed psychological factors which led him to assess inadequately the aircraft's battery endurance after the loss of generator power and the magnitude of the risks involved in continuing to the destination airport. Contributing to the accident was the airline management's failure to provide and the FAA's failure to assure an adequate company recurrent flight crew training programme which contributed to the captain's inability to assess properly the battery endurance of the aircraft before making the decision to continue, and led to the inability of the captain and the first officer to cope promptly and correctly with the aircraft's electrical malfunction."
Patricia A. Goldman, Vice Chairman, filed the following concurring/dissenting statement:
"While the accident report correctly identifies training and surveillance, I believe that inclusion of these items in the probable cause statement obscures and detracts from the basic reason the accident occurred and the attendant safety lesson. The pilot should never have continued the flight to the destination airport, but should have returned to the nearby airport on realizing that electrical d.c. power had been lost."
Final Report: