Crash of a Piper PA-31T-620 Cheyenne II in Munich: 9 killed

Date & Time: Aug 11, 1987 at 1528 LT
Type of aircraft:
Registration:
D-ILRA
Flight Type:
Survivors:
No
Site:
Schedule:
Landsberg - Munich
MSN:
31-8020009
YOM:
1980
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
9
Circumstances:
The twin engine aircraft departed Landsberg-Penzing Airport on a training flight to Munich, carrying one passenger (a secretary of the Southern Bavarian Air Office), one instructor and one pilot. On final approach to Munich-Riem Airport runway 07, at an altitude of 200 feet, the instructor decided to reduce the power on the right engine while the pilot was expecting to initiate a go-around procedure according to the training program. He elected to add power on the left engine but the aircraft lost height, struck the roof of a McDonald's restaurant located in the district of Trudering and eventually crashed in flames on a bus. The aircraft, the restaurant, the bus and several other vehicles were destroyed and seven people were killed, all three occupants in the aircraft and four passengers in the bus. Few days later, two other victims died from their injuries. 30 other people were injured, some of them seriously.
Probable cause:
It was determined that the instructor's decision to reduce power was taken at a critical stage of flight because the aircraft was approaching at a too low altitude of 200 feet and flying vertical to a populated area. Also, the pilot was expecting to initiate a go-around according to the training program.

Crash of a Beechcraft A65 Queen Air in Winnipeg

Date & Time: Jul 31, 1987
Type of aircraft:
Operator:
Registration:
C-GKDX
Flight Phase:
Survivors:
No
Site:
MSN:
LC-271
YOM:
1968
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Winnipeg Airport, the pilot encountered engine problems. The aircraft lost height and crashed on a factory located near the airport. The aircraft was destroyed but all five occupants were rescued.

Crash of a Boeing C-97G Stratofreighter in Mexico City: 65 killed

Date & Time: Jul 30, 1987 at 1703 LT
Registration:
HI-481
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Mexico City - Miami
MSN:
16687
YOM:
1952
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
65
Circumstances:
The four engine airplane departed Mexico City-Benito Juarez Airport at 1700LT on a cargo flight to Miami-Intl, Florida, carrying eight passengers, four crew members and a load consisting of 18 racing horses. After takeoff, during initial climb, the aircraft encountered difficulties to gain sufficient altitude. The crew elected to add power but the aircraft failed to gain height. The captain attempted an emergency landing on a road when the aircraft struck power lines and crashed in the city, few km from the airport. The aircraft as well as several houses and buildings were destroyed. The captain was rescued while 11 other occupants as well as 54 people on the ground were killed. 50 other people were wounded, some seriously.
Probable cause:
It was determined that the total weight of the aircraft was well above the MTOW at the time of the accident. It is also believed that the fuel stored in the tanks did not have the correct octane number since it had an index of 100 when it should have presented an index estimated between 130 and 145. This was presumably caused by poor flight preparation on part of the crew and the ground personnel. Due to insufficient octane index, the engine failed to provide sufficient power during initial climb, which was considered as a contributing factor. It was also reported that the horses panicked and moved in the cabin, causing the CofG to be modified. In such conditions, the aircraft became unstable and difficult to control.

Crash of a Pilatus PC-6/B2-H2 Turbo Porter in Casale Monferrato

Date & Time: Apr 18, 1987
Operator:
Registration:
HB-FIS
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Casale Monferrato - Casale Monferrato
MSN:
685
YOM:
1969
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
1938
Circumstances:
The single engine aircraft departed Casale Monferrato Airfield on a local skydiving flight. While in cruising altitude, all skydivers bailed out when the pilot lost control of the airplane that crashed on a residential area in Casale Monferrato. The pilot, sole on board, was injured.

Crash of a Swearingen SA226TC Metro II in Salt Lake City: 8 killed

Date & Time: Jan 15, 1987 at 1252 LT
Type of aircraft:
Operator:
Registration:
N163SW
Survivors:
No
Site:
Schedule:
Pocatello - Salt Lake City
MSN:
TC-327
YOM:
1980
Flight number:
OO1834
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
3885
Captain / Total hours on type:
1863.00
Copilot / Total flying hours:
4555
Copilot / Total hours on type:
1205
Aircraft flight hours:
15116
Circumstances:
On January 15, 1987, at 1216 mountain standard time, SkyWest flight 1834, a Fairchild Swearingen SA-226TC (METRO II), registration Nl635W, departed Pocatello, Idaho, on a regularly scheduled passenger flight to Salt Lake City, Utah (SLC). The flight was operating under the provisions of Title 14 Code of Federal Regulations Part 121 with two pilots and six passengers aboard. Flight 1834 was handed off from the SLC Air Route Traffic Control Center to the Bear Sector controller at the SLC Terminal Radar Approach Control (TRACON) for a left downwind arrival to SLC International Airport. At 1237:49, the Bear sector controller issued a heading of 100” to flight 1834 and advised the flight to expect vectors for a visual approach to runway 34L. (See Air Traffic Control Transcript in appendix C). During the next few minutes, flight 1834 was given further vectors and descent clearances, and at 1247:21, it was given a frequency change to the TRACON Final controller. At 1250:28, after being cleared to descend to 7,000 feet mean sea level (msl), the Final controller advised, “SkyWest eight thirty four, traffic ten to nine o’clock, four miles, six thousand, Boeing seven, ah, thirty seven three hundred.” Flight 1834 acknowledged, “SkyWest eight thirty four has the traffic.” At 1250:35, the Final controller advised, “SkyWest eight thirty four, plan to follow that traffic, there’s traffic south of him eleven o’clock, six miles north bound, [a] seven thirty seven out of seven thousand five hundred, for the right.” Flight 1834 responded, “OK, we’ll follow the first one, SkyWest eight thirty four.” At 1250:44, the Final controller advised, “SkyWest eight thirty four, wait a minute, report the other one in sight.” Flight 1834 responded, “We’re looking for him.” At 1251:02, the Final controller transmitted, “SkyWest eight thirty four, ten o’clock four miles, seven thousand four hundred.” Flight 1834 replied, “Eight thirty four, we’re looking.” The Final controller then issued instructions at 1251: 15 for flight 1834 to make a left turn to 070”, and the flight acknowledged. At 1251:32, the Final controller transmitted, “SkyWest eight thirty four, traffic’s ten to eleven o’clock, three miles.” Flight 1834 did not acknowledge that transmission, and at 1251:43, the Final controller advised, “SkyWest eight thirty four, turn left heading zero five zero.” The flight acknowledged and reported, “Still have no contact on that traffic.” At 1251:50, the Final controller transmitted, “SkyWest eight thirty four, roger, turn further left heading three six zero.” Flight 1834 acknowledged and at 1251:58, an expletive was transmitted over the TRACON Final control frequency during a transmission from SkyWest flight 575. There were no further transmissions from flight 1834. According to the UNICOM I/ operator at SLC Municipal 2 Airport (SLC 2) about 1115 or 1120, a pilot in Mooney M20C, registration N6485U, operating under 14 CFR Part 91, called to inquire if the runway was clear. The Mooney was occupied by a private pilot in the left seat and an instructor pilot in the right seat. The UNICOM operator advised that the runway was clear, and a few minutes later, a pilot in the Mooney called for and was given an airport advisory. The UNICOM operator observed the Mooney taxi to runway 34 and take off about 1125 or 1130. The Mooney remained in the traffic pattern at SLC 2 performing touch-and-go landings. There were no other aircraft in the traffic pattern at the time. The UNICOM operator stated that she last talked to the Mooney about 1145 to 1150 when a pilot called, “Final for 34.” The UNICOM operator said that she observed the airplane perform a touch-and: go landing, but she did not observe the direction of departure of the airplane. There were no further known communications with the Mooney regarding departing the traffic pattern or any additional aspects of the flight. According to recorded air traffic control (ATC) radar data, after the Mooney departed the SLC 2 traffic pattern at 1235, y the airplane flew south and maneuvered about 25 miles south southeast of SLC International Airport before beginning a turn to the northwest. The airplane continued in a northwesterly direction until it was about 9 miles south of SLC International Airport where it began a gradual left turn until its target merged with the target of SkyWest flight 1834. The targets merged at 1257 :58--the time the expletive was recorded on the ATC tape at the SLC TRACON. The Final approach controller stated that he did observe a visual flight rules (VFR) target about 3 to 4 miles southwest of SLC 2 moving north to northwest when flight 1834 was on downwind. He said he had no more than normal cause to monitor the target. He also stated that it was not unusual to observe VFR targets in the pattern near SLC 2 during visual meteorological conditions. Other controllers at SLC TRACON also stated that it was not uncommon to observe numerous targets operating in the traffic pattern at SLC 2. The Final controller and other controllers added that they normally would observe the VFR targets near SLC 2 disappear from the radarscope and then reappear during practice touch-and-go landings. The Final controller said that he did not recall seeing any VFR targets in the vicinity of SkyWest 1834 as it was turning toward final just before the collision. The Fin.al controller stated that his workload was moderate, and all of his equipment was operating normally before the accident. In addition, the Local controller in the SLC tower stated that he did not observe the target of the Mooney on the tower Bright Radar Indicator Tower Equipment display. There was no evidence that the Mooney pilots were in radio contact with any ATC facility at the time of the accident. Several eyewitnesses were interviewed who observed the airplanes before and after the collision. Some of the witnesses stated that the nose of the METRO II pitched up just before impact. The witnesses stated that the METRO II was headed northeasterly and the Mooney was headed northwesterly just before impact. They stated that the METRO II had made a few left turns as it turned toward the northeast. In general, the eyewitnesses agreed that the two airplanes collided with the Mooney striking the METRO II’s right forward fuselage area with its nose. After the collision, both airplanes fell to the ground with wreckage scattered over 2 square miles in a residential section of Kearns, Utah. There was no fire. The collision occurred at 7,000 feet msl in daylight visual meteorological conditions. All 10 occupants in both aircraft were killed. There were no casualties on the ground.
Probable cause:
Lack of navigational vigilance by the Mooney instructor pilot which led to the authorized intrusion into the Salt Lake City airport radar service area. Contributing to the accident were the absence of a Mode-C transponder on the Mooney airplane and the limitations of the air traffic control system to provide collision protection under the circumstances of this accident.
Final Report:

Crash of a Cessna 411 in Oshawa

Date & Time: Dec 16, 1986
Type of aircraft:
Operator:
Registration:
C-GQSP
Flight Type:
Survivors:
Yes
Site:
MSN:
411-0141
YOM:
1965
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Oshawa Airport, the twin engine aircraft stalled and crashed in a house. Both pilots were seriously injured while both persons into the house were unhurt.

Crash of a BAe 125-600B in Casablanca: 10 killed

Date & Time: Dec 15, 1986
Type of aircraft:
Registration:
5N-AWS
Survivors:
No
Site:
MSN:
256042
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
On approach to Casablanca-Nouasseur Airport, the crew failed to realize his altitude was insufficient when the aircraft crashed into houses located 2 km short of runway. All eight occupants were killed as well as two people on the ground.

Crash of a Cessna T303 Crusader in Bogotá: 2 killed

Date & Time: Oct 19, 1986
Type of aircraft:
Registration:
HK-2853
Flight Phase:
Survivors:
No
Site:
Schedule:
Bogotá - Bogotá
MSN:
303-00092
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The twin engine aircraft departed Bogotá-El Dorado on a short flight to Bogotá-Guaymaral Airport located 15 km to the north. Shortly after takeoff, while climbing, the aircraft went out of control and crashed in the district of Engativá located less than one km northeast of the airport. Both occupants were killed while there was no casualties on the ground.

Crash of a Beechcraft 65-B80 Queen Air in La Carlota: 1 killed

Date & Time: Oct 11, 1986 at 0815 LT
Type of aircraft:
Registration:
YV-247P
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
La Carlota – Los Roques
MSN:
LD-316
YOM:
1967
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
Shortly after takeoff from La Carlota-General Francisco de Miranda AFB, the crew encountered technical problems and elected to return. The aircraft lost height and eventually struck the roof of a garage and crashed in the district of Macaracuay, less than 3 km southeast from the airport. All seven occupants were killed while there were no injuries on ground.

Crash of a Beechcraft E18S in Chicago: 1 killed

Date & Time: Sep 28, 1986 at 2254 LT
Type of aircraft:
Operator:
Registration:
N101VE
Flight Type:
Survivors:
No
Site:
Schedule:
Chicago - Covington
MSN:
BA-190
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6400
Captain / Total hours on type:
2059.00
Aircraft flight hours:
17743
Circumstances:
The aircraft had departed on runway 13. He was then directed to climb to 6,000 feet. Thirty seconds later he advised he had engine trouble and was returning to the airport. Shortly thereafter he advised he could not maintain altitude. The aircraft, one mile southeast of the airport, struck the roofs of two family type residences. Then struck two garages, ground impacted and struck the rear area of a third residence. An intense fire followed. Left engine had impeller failure. Propeller was pitched between low and high rpm. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: loss of engine power (total) - mech failure/malf
Phase of operation: climb - to cruise
Findings
1. (f) eng assembly, blower/impeller/integral supercharger - failure, total
2. (f) lubricating system - lack of
----------
Occurrence #2: airframe/component/system failure/malfunction
Phase of operation: descent - emergency
Findings
3. (c) propeller system/accessories, feathering system - incorrect
4. Propeller feathering - attempted - pilot in command
5. (c) propeller system/accessories, feathering system - movement restricted
----------
Occurrence #3: forced landing
Phase of operation: descent - emergency
----------
Occurrence #4: in flight collision with object
Phase of operation: descent - emergency
Findings
6. (c) object - residence
----------
Occurrence #5: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report: