Crash of a De Havilland DH.106 Comet 4C off Mumbai: 63 killed

Date & Time: Jul 28, 1963 at 0150 LT
Type of aircraft:
Operator:
Registration:
SU-ALD
Survivors:
No
Schedule:
Tokyo – Hong Kong – Bangkok – Bombay – Bahreïn – Cairo
MSN:
6441
YOM:
1960
Flight number:
MS869
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
63
Captain / Total flying hours:
14841
Captain / Total hours on type:
1473.00
Copilot / Total flying hours:
5463
Copilot / Total hours on type:
475
Circumstances:
Flight 869 was a scheduled international flight from Tokyo, Japan to Cairo, United Arab Republic via Hong Kong, Bangkok, Bombay and Bahrain. A crew change was effected at Bangkok. Based on the tape recordings of messages exchanged between the aircraft and Santa Cruz approach and radar control, the flight was reconstructed. It was uneventful until 2016 hours GMT when it reported arriving over the Santa Cruz VOR at 7 000 ft. It was cleared to descend to 4 000 ft over the VOR and was requested to report what type of approach would be carried out for landing on runway 09. The aircraft reported it would follow the ILS back beam procedure. It was advised by Santa Cruz approach that the back beam of the ILS was not flyable but that it could home on the 270° radial of the VOR. The aircraft agreed to do a VOR letdown for runway 09, and shortly thereafter reported it was leaving 7 000 ft outbound over the sea on the 272° radial of the VOR. At 2018 Santa Cruz radar, which was monitoring the flight, warned it that if it flew more than 6 or 7 miles west of the field it would run into very heavy turbulence. Shortly thereafter the flight requested permission to make a left-hand procedure turn instead of the normal right-hand turn. This was granted. At 2019 the flight commenced the procedure turn inbound. Santa Cruz radar advised the flight that it was then 6 miles west-northwest of the field. Flight 869 acknowledged this message and was not heard from again. During the turn in severe turbulence and heavy rain the pilot lost control of the aircraft. It was found later on that the air- craft had crashed into the sea 9 NM west of Madh Island at approximately 2020 hours.
Probable cause:
The committee was faced with difficulties during the course of the investigation due to the fact that neither the exact location of the wreckage could be fixed no the wreckage salvaged. Moreover, the accident occurred suddenly with no airborne emergency reported and late at night over the sea in limited visibility. There were no eyewitnesses. However, in the presence of the facts available, it can be concluded that the accident was probably due to loss of control while turning in severe turbulence and heavy rain.
Final Report:

Crash of a De Havilland DH.106 Comet 4C on Mt Khao Yai: 26 killed

Date & Time: Jul 19, 1962 at 2244 LT
Type of aircraft:
Operator:
Registration:
SU-AMW
Flight Phase:
Survivors:
No
Site:
Schedule:
Tokyo – Hong Kong – Bangkok – Bombay – Bahrain – Cairo
MSN:
6464
YOM:
1962
Flight number:
MS869
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
26
Circumstances:
Flight UA869 departed from Hong Kong for Bangkok, an intermediate stop, on a scheduled service to Cairo. Takeoff time was 13:30 UTC. The flight climbed to 31000 ft, the selected cruising altitude. At 15:14 UA869 advised Bangkok ATC that the flight had crossed the Bangkok FIR boundary at 15:08 and passed over Ubol NDB at 15:13 and requested to fly direct from Ubol NDB to Bangkok VOR. This request was granted by Bangkok ATC. At this time UA869 advised Bangkok ATC that the ETA for Bangkok VOR would be 15:47. At 15:27 the flight advised Bangkok ATC that it would be over the 100 mile perimeter at 15:30. After reporting that it was 90 miles out the crew requested descent clearance to a lower altitude. Bangkok control cleared the flight to descend to 4000 ft on the Bangkok VOR radial of 073 degrees and to report when commencing descent from 31000 ft. The flight was instructed to contact Bangkok approach control at 15:39. At 15:35 the flight was cleared to 3000 ft and informed that the altimeter setting was 1007.8 mb. At 15:40 the flight transferred to the Bangkok approach control. Immediately after this UA869 reported to approach control that it was descending from 13000 ft and estimating Bangkok VOR at 15:44. Approach control advised the flight to adjust the altimeter setting to 1007.8 mb and then cleared the flight to cross Bangkok VOR for final approach on runway 21R and report immediately on descending from 3000 ft. This was the last contact with the flight. The Comet flew into the side of Khao Yai Mountain, 52 nm NE of Bangkok.
Probable cause:
The principal cause of the accident was the pilot's action in commencing descent at 1530 hours when the aircraft was 137 miles and not 90 miles from the Bangkok VOR as reported to Bangkok Control, and the aircraft, therefore, collided with a mountain at a point 52 miles distant. It is probable that the pilot-in-command did not actually pass over the point he reported to the Flight Control Units, but only estimated he had passed three points which resulted in grave errors of time and distance in his computations. It is also probable that the pilot-in-command had been too self-confident so that his actions were not according to the fundamental principles of air navigation.
Final Report:

Crash of a Douglas DC-8-43 near Junnar: 94 killed

Date & Time: Jul 7, 1962 at 0010 LT
Type of aircraft:
Operator:
Registration:
I-DIWD
Flight Phase:
Survivors:
No
Site:
Schedule:
Sydney – Darwin – Singapore – Bangkok – Bombay – Karachi – Tehran – Rome
MSN:
45631
YOM:
1962
Flight number:
AZ771
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
85
Pax fatalities:
Other fatalities:
Total fatalities:
94
Captain / Total flying hours:
13700
Captain / Total hours on type:
1396.00
Copilot / Total flying hours:
3480
Copilot / Total hours on type:
1672
Aircraft flight hours:
964
Circumstances:
The crew was preparing to land at Bombay-Santa Cruz Airport runway 27 and was cleared to descend to 4,000 feet. After several errors, the pilot-in-command started the descent prematurely and while at an altitude of 3,600 feet, the airplane struck the slope of Mt Davandyachi (1,080 m high) located about eight km north of Junnar. The aircraft disintegrated on impact and all 94 occupants were killed. At the time of the accident, the airplane was off course by 9 km and its altitude was too low.
Probable cause:
The accident was attributed to a navigation error which led the pilot to believe that he was nearer his destination than he actually was and, therefore, caused him to make a premature descent in instrument conditions for a straight-in approach to land at night. The aircraft consequently, crashed into high terrain. Contributing causes were:
- Failure on the part of the pilot to make use of the navigational facilities available in order to ascertain the correct position of the aircraft,
- Infringement of the prescribed minimum safe altitude,
- Unfamiliarity of the pilot with the terrain on the route.
Final Report:

Crash of a Douglas C-54A-15-DC Skymaster in Nagpur

Date & Time: Mar 22, 1961
Type of aircraft:
Registration:
N5519V
Flight Type:
Survivors:
Yes
Schedule:
Bombay – Bangkok
MSN:
10347
YOM:
1944
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Bombay to Bangkok, the crew encountered technical problems with the engines and decided to divert to Nagpur for an emergency landing. On approach, the pilot-in-command was unable to maintain a safe altitude and as the aircraft was losing height, he attempted an emergency landing in a plantation located 12 km from the airport. The four engine aircraft crash landed and came to rest. All three crew members were unhurt while the aircraft was written off.
Probable cause:
Engine problems in flight.

Crash of a Douglas DC-4-1009 in Taipei: 18 killed

Date & Time: Apr 14, 1960
Type of aircraft:
Operator:
Registration:
42919
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Taipei – Bangkok
MSN:
42919
YOM:
1946
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
18
Circumstances:
The four engine aircraft was on its way back to Bangkok, carrying the Royal Thai Air Force Chief of Staff and several officials. After takeoff, while climbing, the airplane struck the slope of Mt Wuzhi located 8 km northeast of the airport. All 18 occupants were killed.

Crash of a Douglas C-47 in Hong Kong

Date & Time: Nov 15, 1959
Operator:
Registration:
L2-28/02
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hong Kong - Bangkok
MSN:
20794
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taxiing, the airplane veered off taxiway and plunged into the bay of Kowloon. There were no injuries but the aircraft was written off. The exact date of the occurrence remains uncertain.

Crash of a Douglas C-47A-15-DK in Korat: 19 killed

Date & Time: Mar 31, 1956
Operator:
Registration:
L2-14/96
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Korat – Bangkok
MSN:
12667
YOM:
1944
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
19
Circumstances:
Crashed shortly after takeoff from Korat Airport, killing all 19 occupants.

Crash of a Douglas C-47B-25-DK in Bangkok: 4 killed

Date & Time: Oct 11, 1954
Operator:
Registration:
L2-10/96
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
15842/32590
YOM:
1945
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Shortly after takeoff from Don Mueang Airport in Bangkok, while climbing, the starboard engine failed. The pilot attempted to return for an emergency landing when the aircraft stalled and crashed in a field located 500 meters from the runway threshold. Four passengers were killed while 14 other occupants were injured.
Probable cause:
Engine failure after liftoff.

Crash of a Lockheed L-749A-79-33 Constellation in Bangkok

Date & Time: Mar 23, 1952
Operator:
Registration:
PH-TFF
Survivors:
Yes
Schedule:
Amsterdam – Rome – Athens – Cairo – Bahrain – Karachi – Bombay – Bangkok – Kuala Lumpur – Jakarta – Darwin – Sydney
MSN:
2652
YOM:
1950
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
34
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route to Bangkok, about 450 km from the intended destination, the crew informed ATC about vibrations coming from the engine number three. The flight was continued uneventfully until the descent was started. On final approach to runway 21, a propeller blade detached from the engine number three that caught fire and suffered severe vibrations. On touchdown, the right main gear collapsed and the airplane skidded for several yards before coming to rest in flames. All 44 occupants were evacuated safely before the aircraft christened 'Venlo' was destroyed by fire.
Probable cause:
Failure of a propeller blade during flight shortly before landing at Don Mueang Airport. This caused the loss of number three engine and fire to break out in the engine nacelle which could not be extinguished. When landing, the right main landing gear collapsed as a consequence of the fire.
Final Report:

Crash of a Douglas C-54B-10-DO Skymaster in Bangkok

Date & Time: Jul 13, 1951
Type of aircraft:
Operator:
Registration:
HS-POA
Flight Phase:
Survivors:
Yes
Schedule:
Bangkok – Hong Kong
MSN:
18368
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the pilot in command pulled on control column but the aircraft failed to rotate. He decided to abandon the takeoff procedure and started an emergency landing. Unable to stop within the remaining distance, the four engine aircraft christened 'Bangkok' overran and came to rest in flames. All occupants were evacuated safely while the airplane was destroyed by fire.
Probable cause:
It was determined that the total weight of the aircraft was well above the MTOW admissible in the actual circumstances.