Country
Operator Image

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

Date & Time: Aug 31, 1987 at 1536 LT
Type of aircraft:
Operator:
Registration:
HS-TBC
Survivors:
No
Schedule:
Hat Yai - Phuket
MSN:
22267
YOM:
1980
Flight number:
TG365
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
74
Pax fatalities:
Other fatalities:
Total fatalities:
83
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.

Crash of an Avro 748-243-2 in Chiang Rai

Date & Time: Apr 28, 1987 at 1005 LT
Type of aircraft:
Operator:
Registration:
HS-THI
Survivors:
Yes
Schedule:
Chiang Mai - Chiang Rai
MSN:
1708
YOM:
1971
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
39
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Chiang Mai, the crew initiated the approach to Chiang Rai Airport in good weather conditions. The copilot was the pilot-in-command when the aircraft completed a gear up landing. It slid on runway for about 1,075 meters before coming to rest on the runway. All 43 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the crew failed to extend the landing gear on approach. The following contributing factors were reported:
- The crew failed to follow the approach checklist,
- Lack of crew coordination,
- The captain failed to supervise properly the copilot's actions.

Crash of a Boeing 737-2P5 in Phuket: 11 killed

Date & Time: Apr 15, 1985 at 2329 LT
Type of aircraft:
Operator:
Registration:
HS-TBB
Survivors:
No
Schedule:
Bangkok - Phuket
MSN:
21810
YOM:
1979
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
Following an uneventful flight from Bangkok, the crew started the descent to Phuket Airport by night and good weather conditions. Four minutes after being cleared to descend to 3,000 feet, the pilot reported that he was unable to receive the DME signal. ATC asked the crew if he wanted to conduct a VOR approach to runway 09 but the captain preferred to attempt a visual approach to runway 27. On final, the aircraft struck a hill (800 feet high) and crashed about 18 km short of runway. The aircraft was destroyed and all 11 occupants were killed.
Probable cause:
Decision of the crew to continue the approach below MDA until the aircraft struck the ground.

Crash of an Avro 748-2-243 in Chiang Rai

Date & Time: Jun 21, 1980
Type of aircraft:
Operator:
Registration:
HS-THG
Survivors:
Yes
Schedule:
Chiang Mai - Chiang Rai
MSN:
1693
YOM:
1970
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at Chiang Rai Airport, the airplane encountered difficulties and was unable to stop within the remaining distance. It overran and came to rest in a ditch. All 21 occupants were evacuated, some of them were injured.

Crash of an Avro 748-2-207 in Bangkok: 44 killed

Date & Time: Apr 27, 1980 at 0655 LT
Type of aircraft:
Operator:
Registration:
HS-THB
Survivors:
Yes
Schedule:
Nakhon Phanom – Udon – Khon Kaen – Bangkok
MSN:
1568
YOM:
1964
Flight number:
TG231
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
44
Captain / Total flying hours:
18096
Captain / Total hours on type:
7796.00
Copilot / Total flying hours:
24372
Copilot / Total hours on type:
11899
Aircraft flight hours:
12791
Circumstances:
On 27 April 1980, HS-748 Series 11, HS-THB was on a scheduled domestic passenger flight. The flight operated the route Bangkok - Khon Kaen - Udon - Nakhon Phanom - Udon - Khon Kaen - Bangkok. The departure flight was flight number TG221 which departed Bangkok International Airport at 0101 h, arrived Khon Kaen Airport at 0210 h, departed Khon Kaen Airport at 0233 h, arrived Udon Airport at 0251 h, departed Udon Airport at 0309 h, arrived Nakhon Phanom Airport at 0349 h. The return flight, flight number TG231, departed Nakhon Phanom Airport at 0408 h, arrived Udon Airport at 0448 h, departed Udon Airport at 0507 h, arrived Khon Kaen Airport at 0532 h, departed Khon Kaen Airport at 0550 h, ETA Bangkok International Airport at 0656 h. At 0559 h, after take-off from Khon Kaen Airport, the pilot reported to Bangkok Area Control Centre that he was climbing to 6 000 ft, ETA Korat at 0626 h, ETA Bangkok International Airport at 0656 h and requested ATC clearance to Bangkok International Airport via W6 - KT - W1 - BKK. Bangkok Area Control Centre cleared HS-THB to Bangkok International Airport via this route, to maintain FL 120 and asked the pilot to report when the aircraft reached FL 120.
- At 0614 h the pilot reported that HS-THB reached FL 120.
- At 0626 h the pilot reported that the aircraft was over KT.
- AT 0627 h Bangkok Area Control Centre informed the pilot that HS-THB was in radar contact, 5 miles northwest of KT.
- At 0642 h Bangkok Area Control Centre cleared HS-THB to descend to 8 000 ft and informed the pilot that the altimeter setting was 1 008 mb. This was acknowledged by the pilot.
- At 0644 h, Bangkok Area Control Centre advised the pilot to contact Bangkok Approach Control on 119.1 MHz.
- At 0644 h, the pilot contacted Bangkok Approach Control and reported that he was maintaining 8 000 ft. Bangkok Approach Control advised the pilot to descend to 6 000 ft and informed him that the altimeter setting was 1 008 mb. This was acknowledged by the pilot.
- At 0648 h Bangkok Approach Control advised HS-THB to descend to 6 000 ft.
- At 0651 h Bangkok Approach Control advised HS-THB to descend to 1 500 ft.
- At 0653 h the pilot reported that HS-THB had reached 1 500 ft.
- At 0654 h Bangkok Approach Control informed the pilot that HS-THB was 7 miles from the Outer Marker and cleared the aircraft to make an ILS approach to runway 21R. This was acknowledged by the pilot.
- At 0656 h Bangkok Approach Control advised the pilot to contact Bangkok Tower on 118.1 MHz but no answer from the pilot was received. Bangkok Approach Control tried to contact HS-THB until 0709 h but no answer was received. HS-THB operated in good weather conditions on both the outbound and return flights until, descending to runway 21R nearly at the airport, it encountered an area of rain. Later, HS-THB lost altitude rapidly. Many things in the passenger cabin fell to the cabin floor. It was raining with hail. Looking through the windows, some passengers saw grey clouds. Then the aircraft could maintain altitude. Thirty seconds later it again lost altitude, more severely than the first time. Finally it crashed into a paddy field and skidded forward about 510 feet. Fire occurred in both wings for a while. The accident site was 8 NM northeast of Bangkok International Airport.
Probable cause:
The pilot directed the aircraft into a thunderstorm in an early dissipating stage. The aircraft was severely affected by a downdraft and lost altitude rapidly. At that time the altitude of the aircraft was only 1500ft and the pilot could not maintain altitude of the aircraft. The aircraft crashed into the ground and ran forward.
Factors which caused the pilot to direct the aircraft into the thunderstorm were:
1. During flight prior to the accident, the pilot did not tune his radio to the ATIS frequency, so he did not receive the special weather report (SPECI) broadcast four minutes before the accident advising that there was a thunderstorm in the area he would soon encounter.
2. The pilot did not make use of airborne weather radar.
3. While the pilot was approaching at high altitude, he could see the thunderstorm, but it was not in his flight path to Bangkok International Airport. When the pilot was descending in compliance with Bangkok Approach Control instruction, he was not aware that the rain area which he was entering was a thunderstorm which was moving and developing severely. The thunderstorm which had developed to the severe stage was moving and intercepted the aircraft.
4. The pilot assumed that flying by radar vector would be safe as he thought that the Approach Control Radar could detect the thunderstorm and Bangkok Approach Control would not vector the aircraft into the thunderstorm.
Final Report:

Crash of a Douglas DC-8-33 in Kathmandu: 1 killed

Date & Time: May 10, 1973
Type of aircraft:
Operator:
Registration:
HS-TGU
Survivors:
Yes
Schedule:
Bangkok - Kathmandu
MSN:
45526/89
YOM:
1960
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
100
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
After touchdown at Kathmandu-Tribhuvan Airport, the four engine airplane was unable to stop within the remaining distance. It overran, lost its undercarriage and one engine before coming to rest in a dump. Onee people on the ground was killed and four passengers were injured. The aircraft was written off.
Probable cause:
Wrong approach configuration on part of the pilot-in-command who landed too far down the runway, causing the braking distance to be insufficient.

Crash of a Douglas DC-3 in Mae Hong Son

Date & Time: May 7, 1971
Type of aircraft:
Operator:
Registration:
HS-TDE
Survivors:
Yes
MSN:
13794/25239
YOM:
1944
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach, the airplane was too low and crashed in unclear circumstances short of runway. All 21 occupants were able to evacuate the cabin and none of them was injured. Nevertheless, the airplane was damaged beyond repair.

Crash of a Sud-Est Aviation SE-210 Caravelle III in Bangkok

Date & Time: Jul 9, 1969
Operator:
Registration:
HS-TGK
Survivors:
Yes
Schedule:
Hong Kong - Bangkok
MSN:
34
YOM:
1960
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
68
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Bangkok-Don Mueang Airport was completed by the copilot in poor weather conditions (low visibility and heavy rain falls due to tropical storm) when the ILS equipment failed. It was decided to continue the approach and at an altitude of 700 feet, the pilot-in-command was able to locate the runway lights. At this time, the aircraft was slightly too high on the glide and too far to the left. Once the altitude of 300 feet was reached on descent, the IAS was 127 knots, about five knots above the planned speed. Thus, the copilot decided to reduce the speed to 122 knots when the airplane suddenly lost height. The captain elected to regain control but it was too late. With a relative high sink rate, the airplane landed very hard, causing both main landing gear to puncture the wings. The aircraft came to rest after a course of several hundred yards. While all 75 occupants escaped uninjured, the aircraft was damaged beyond repair.
Probable cause:
Windshear is suspected.

Crash of a Douglas DC-3 in Chiang Mai: 4 killed

Date & Time: Dec 27, 1967 at 1349 LT
Type of aircraft:
Operator:
Registration:
HS-TDH
Survivors:
Yes
Schedule:
Bangkok – Chiang Mai
MSN:
9189
YOM:
1943
Flight number:
TG002
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
On approach to runway 36, the pilot-in-command was hampered by insufficient visibility due to fog and decided to abandon the landing and to make a low pass over the airport. Few minutes later, he was cleared to make an approach to runway 18 and decided to refer to three roads but referred to the wrong road. On final, the airplane was unstable and banked left, causing the left engine to struck the ground. The airplane crashed 200 meters short of runway threshold and came to rest. Four passengers were killed.

Crash of a Sud Aviation SE-210 Caravelle III in Hong Kong: 24 killed

Date & Time: Jun 30, 1967 at 1610 LT
Operator:
Registration:
HS-TGI
Survivors:
Yes
Schedule:
Tokyo – Taipei – Hong Kong – Bangkok
MSN:
25
YOM:
1960
Flight number:
TG601
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
73
Pax fatalities:
Other fatalities:
Total fatalities:
24
Captain / Total flying hours:
7800
Captain / Total hours on type:
3700.00
Copilot / Total flying hours:
18400
Copilot / Total hours on type:
2300
Aircraft flight hours:
17350
Circumstances:
Thai Airways International Flight 601, a scheduled passenger service from Taipei International Airport, Formosa, to Hong Kong International Airport, departed from Taipei at 0540 hours with an estimated enroute time of 1 hour 27 minutes, and an endurance of 4 hours 19 minutes. The flight was made at flight level 260 and was entirely normal except that, because of turbulence expected from a severe tropical storm, the passenger seat belts were on for the majority of the flight. No turbulence of any importance was in fact experienced. At 0638 hours, when approximately 170 miles from Hong Kong, Flight 601 made contact with Hong Kong airways control and received clearance to descend to flight level 70. At 0658 hours they contacted Hong Kong approach control, which later cleared them to descend to 2 500 feet using an altimeter setting (QNH) of 999 mb, and informed them that there was a heavy rain shower at Hong Kong and that the visibility was very reduced to 2 km. The co-pilot flew the aircraft manually from the right-hand seat, whilst the Captain monitored the approach from the left hand seat and handled the R/T communications, the third pilot, who was acting as the system operator, also monitored the flight instruments. Rhe approach controller provided radar guidance to position the aircraft for an ILS approach to runway 31 and when it was at about 8 miles from touchdown, cleared the pilots to contact the precision controller. This controller cleared them to continue their ILS approach, informed them that there was heavy rain at the field and told them the overshoot procedure to be adopted should this become necessary. The aircraft remained well within the approach safety funnel 2° either side of the localiser centerline and 1/2° above or below the glide slope, until 3 miles from touchdown, the PAR controller having provided information on weather, overshoot instructions and distance from touchdown as shown on the R/T transcript at Appendix C. In his 3 miles distance advisory, the PAR controller informed the pilot that he was just a little to the right; this appeared to be corrected and the aircraft returned to the centre line. At about 2 3/4 miles, the aircraft descended momentarily below the glide slope safety funnel but returned quickly towards the glide slope before the PAR controller had made any advisory comment. At 1 1/2 mile the aircraft was again a little right of centre line and at this time also interference from the heavy rain began to obscure PAR reception, firstly in elevation and, shortly after one mile, also in azimuth. Correlation of the flight recorder readout and the R/T transcript indicates that-approximately 2 seconds after receiving the 1 1/2 mile advisory that he was a little to the right, the co-pilot made a left turn of 14°. Eight seconds later, the PAR controller advised him that he was coming back to the centre line and almost immediately he began a right turn of similar dimensions. Five seconds after this, the PAR controller save the 1 mile advisory and the information that the aircraft was going left of centre after which the aircraft increased its rate of turn to the right. On hearing the 1 mile advisory, the captain reinforced it by telling the co-pilot to move to the right and a moment or two later, when looking across the cockpit, saw the sea about 100 ft below through the copilot's side window. He immediately attempted to make a pull-up, but the aircraft struck the surface, bounced slightly, and settled on the water about 3 925 ft before the ILS reference point of runway 31 and about 100 ft left of the ILS centre line. According to the survivors the impact was not unduly greater than that of a heavy landing but the starboard wing and undercarriage broke away, the latter ripping open the underside of the fuselage; in addition, the rear end of the fuselage broke open. As a result of this damage the aircraft sank very rapidly and 14 of the passengers did not escape from the fuselage and were drowned, 6 were dead on arrival at hospital, 4 were missing and later found drowned. The remaining passengers and the crew were rescued by nearby surface vessels and a helicopter.
Probable cause:
The causes of the accident were:
- The pilots did not adhere to the Thai Airways procedure for a 'Captain monitored' approach in bad visibility,
- The captain did not monitor the approach adequately,
- The copilot mishandled the aircraft after descending below minimum altitude,
- Downdraughts may have contributed to the height loss which resulted from this mishandling.
Final Report: