Scheduled Revenue Flight | Bureau of Aircraft Accidents Archives

While in cruising altitude on a flight from Blantyre to Lilongwe, the twin engine aircraft was shot down by a surface-to-air missile. Out of control, it crashed in Ulongwé, killing all 10 occupants.

Probable cause:

It is believed the aircraft was mistakenly shot down while flying over an area of heavy fightings.

Crash of a Cessna 402B in Bugelenga

Date & Time: Oct 20, 1987 at 0830 LT

Type of aircraft:

Cessna 402

Operator:

Registration:

5H-TZZ

Flight Phase:

Flight

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Captain / Total flying hours:

6200

Circumstances:

En route, one of the engine failed. The pilot reduced his altitude and completed an emergency landing in a pasture. There were no casualties.

Probable cause:

Engine failure for unknown reasons.

Crash of a Let L-410UVP near Saratov

Date & Time: Oct 18, 1987

Type of aircraft:

Let L-410

Operator:

Registration:

CCCP-67334

Flight Phase:

Flight

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Plain, Valley

MSN:

82 08 34

YOM:

1982

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

En route, both engines failed simultaneously. The crew reduced his altitude and completed a belly landing in a pasture located in the region of Saratov. The aircraft was damaged beyond repair and there were no casualties.

Probable cause:

Double engine failure in flight for unknown reasons.

Crash of an ATR42-312 in Mt Crezzo: 37 killed

Date & Time: Oct 15, 1987 at 1828 LT

Type of aircraft:

ATR42-300

Operator:

Registration:

I-ATRH

Flight Phase:

Flight

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Mountains

Schedule:

Milan - Cologne

MSN:

YOM:

1987

Flight number:

BM460

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

15 minutes after takeoff from Milan-Linate Airport, while climbing to the altitude of 14,700 feet, the crew encountered severe icing conditions. At a constant speed of 133 knots, the aircraft first rolled to the right to an angle of 41° then to the left to 100°, again 105° to the right and finally 135° to the left. Out of control, the aircraft nosed down and crashed on the slope of Mt Crezzo located 50 km north of Linate Airport. The aircraft was totally destroyed and all 37 occupants were killed.

Probable cause:

Loss of longitudinal controllability due to severe icing conditions. The crew was inexperienced, which was considered as a contributing factor.

Crash of a PZL-Mielec AN-2 in Pronin

Date & Time: Oct 14, 1987

Type of aircraft:

PZL-Mielec AN-2

Operator:

Registration:

CCCP-82801

Flight Phase:

Takeoff (climb)

Flight Type:

Scheduled Revenue Flight

Site:

Plain, Valley

MSN:

1G166-19

YOM:

1975

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

Crashed while taking off on an unauthorized flight. Occupant fate unknown.

Crash of a Fokker F27 Friendship 500 near Pagan: 49 killed

Date & Time: Oct 11, 1987

Type of aircraft:

Fokker F27 Friendship

Operator:

Registration:

XY-AEL

Flight Phase:

Landing (descent or approach)

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Mountains

Schedule:

Yangon - Nyaung-U

MSN:

10689

YOM:

1985

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Aircraft flight hours:

3958

Aircraft flight cycles:

3799

Circumstances:

While descending to Nyaung-U Airport deserving the Bagan archaeological region, the crew encountered poor visibility due to heavy rain falls. At an altitude of 1,500 feet, the aircraft struck the slope of a mountain located 32 km from the airport. All 49 occupants were killed.

Crash of a De Havilland DHC-6 Twin Otter 300 in El Poleo: 2 killed

Date & Time: Oct 11, 1987

Type of aircraft:

De Havilland DHC-6 Twin Otter

Operator:

Registration:

HK-2920

Flight Phase:

Landing (descent or approach)

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

Schedule:

Ocaña – El Poleo

MSN:

419

YOM:

1974

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

While approaching El Poleo, the crew encountered limited visibility due to poor weather conditions. On final, the aircraft was too low and struck the top of a hill located few km from the landing area. Both pilots were killed while all seven passengers were rescued.

Crash of a PZL-Mielec AN-2 in Uzbekistan

Date & Time: Oct 4, 1987

Type of aircraft:

PZL-Mielec AN-2

Operator:

Registration:

CCCP-23671

Flight Phase:

Flight

Flight Type:

Scheduled Revenue Flight

Site:

Plain, Valley

MSN:

1G32-04

YOM:

1963

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

Crashed in the Surxondaryo Region following an engine failure. Occupant fate unknown.

Probable cause:

Engine failure for unknown reasons.

Crash of a PZL-Mielec AN-2 at Kushevskaya

Date & Time: Oct 3, 1987

Type of aircraft:

PZL-Mielec AN-2

Operator:

Registration:

CCCP-17887

Flight Phase:

Takeoff (climb)

Flight Type:

Scheduled Revenue Flight

Survivors:

Yes

Site:

Airport (less than 10 km from airport)

MSN:

1G205-28

YOM:

1984

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

Crashed on takeoff after the engine failed because the 4-way gas crane remained in the closed position.

Probable cause:

Engine failure at takeoff after the crew failed to follow the pre-takeoff checklist.

Crash of a Boeing 737-2P5 off Phuket: 83 killed

Date & Time: Aug 31, 1987 at 1536 LT

Type of aircraft:

Boeing 737-200

Operator:

Registration:

HS-TBC

Flight Phase:

Landing (descent or approach)

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Lake, Sea, Ocean, River

Schedule:

Hat Yai - Phuket

MSN:

22267

YOM:

1980

Flight number:

TG365

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Captain / Total flying hours:

19538

Captain / Total hours on type:

5576.00

Copilot / Total flying hours:

5951

Copilot / Total hours on type:

156

Aircraft flight hours:

16963

Aircraft flight cycles:

20864

Circumstances:

Thai Airways Flight 365 was approaching Phuket VOR/DME on radial 119 after a flight from Hat Yai. At the same time Dragon Air Flight 203 (a Boeing 737 registered VR-HYL, carrying 62 occupants) also approached Phuket VOR/DME on radial 090. At 08:34 UTC Dragonair 203 reported at 2500 feet with Thai 365 in sight in front of them. The Thai Boeing was flying at 3000 feet at the time, and was 13 miles from Phuket VOR/DME. Dragonair 203, first priority in approach sequence, then turned right at 12 DME and was going to turn inbound for finals for runway 27. The Thai crew surmised that the other crew were making a false position report to gain landing priority and reported hurriedly that they were at 8 DME inbound and requested visual approach, though they hadn't reached 8 DME yet. This forced Phuket Approach to give Thai 365 landing priority at 08:35. The Dragonair crew (flying IFR) immediately warned that the Thai plane couldn't descend through their flight level. Concentrating on the conflicting traffic the speed decayed to 163 knots until the stick shaker activated. The Thai crew then applied power and raised the landing gear, but the aircraft entered a stall crashed into the sea, disintegrating on impact. All 83 occupants were killed.

Probable cause:

The pilot slowed the aircraft and it stalled while the pilot prepared to be number one on landing as advised by Phuket approach control. It appears that he was worrying and not sure whether he could make number one landing because the pilot if number two aircraft in sequence gave warning that the number one aircraft ahead was above him and could not descend passing through his level. The pilot added power and raised the gear after stick shaker activated but didn't execute a recovery before hitting the sea.