Crash of an Airbus A310-204 in Surat Thani: 101 killed

Date & Time: Dec 11, 1998 at 1910 LT
Type of aircraft:
Operator:
Registration:
HS-TIA
Survivors:
Yes
Schedule:
Bangkok - Surat Thani
MSN:
415
YOM:
1988
Flight number:
TG261
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
132
Pax fatalities:
Other fatalities:
Total fatalities:
101
Aircraft flight hours:
23028
Aircraft flight cycles:
22031
Circumstances:
Thai Airways International flight 261, an Airbus A310, left Bangkok-Don Mueang International Airport, Thailand at 17:54 hours local time for a domestic flight to Surat Thani. At 18:26 hours, the copilot first established contact with the Surat Thani approach controller while the aircraft was 70 nautical miles away from Surat Thani Airport. The controller radioed that the crew could expect a VOR/DME instrument approach to runway 22. At that time surface wind was calm with a visibility of 1500 meters, light rain and a cloud base of 1800 feet. At 18:39 hours the copilot contacted Surat Thani aerodrome controller and reported over the Intermediate Fix (IF). The controller informed him that the precision approach path indicators (PAPI) on the right side of runway 22 were unserviceable while the left lights were in use. At 18:41 hours, the copilot reported passing final approach fix (FAF). The controller informed the pilot that the aircraft was not in sight but it was cleared to land on runway 22. The surface wind was blowing from 310 degrees at a velocity of 5 knots so the pilots should be careful or the slippery runway. At 18:42 hours, the copilot reported that the runway was in sight and later on the controller also had the aircraft in sight. The pilot decided to go-around. The controller asked the pilot about the distance where the runway could be seen. The copilot reported that it could be seen at 3 nautical miles and requested for the second approach. The controller requested to report over FAF . When the copilot reported that the flight was over the FAF again, the controller cleared the flight to land although he again could not see the runway. When the flight crew failed to observe the runway lights, the captain decided to go around again. Again the controller instructed the flight to report over the FAF and reported that visibility had decreased to 1,000 meters in light rain. At 19:05, after reporting over the FAF, the flight was cleared to land on runway 22. The flight maintained the Minimum Descent Altitude (MDA) but the crew were unable to see the runway. The autopilot was disconnected and a little later the captain decided to go around. The pitch attitude increased continuously. The pitch attitude reached approximately 40°, when the pilot applied the elevator decreasing the pitch attitude to 32-33°. When he discontinued applying elevator the pitch increased to 47-48°. Consequently the speed decreased to 100 knots. The captain was not aware of the attitude due to stress and the expectation that the go around was flown exactly like the first two go-arounds. The airplane lost altitude until it impacted terrain to the left of the runway. 45 people survived and 101 others were killed, including 11 crew members.
Probable cause:
After careful consideration. the Aircraft Accident Investigation Committee of the Kingdom of Thailand ultimately came to the conclusion that the accident occurred because the aircraft entered into stall condition which might be caused by the followings:
1. The pilot attempted to approach the airport in lower than minimum visibility with rain.
2. The pilot could not maintain the VOR course as set forth in the approach chart. The aircraft flew left of VOR course on every approach.
3. The pilots suffered from the accumulation of stress and were not aware of the situation until the aircraft emerged into the upset condition.
4. The pilots had not been informed of the document concerning the wide-body airplane upset recovery provided by Airbus Industrie for using in pilot training.
5. The lighting system and approach chart did not facilitate the low visibility approach.
6. Stall warning and pitch trim systems might not fully function as described in the FCOM and AMM.

Crash of an Embraer EMB-110P2 Bandeirante in Bangkok

Date & Time: Oct 25, 1993
Operator:
Registration:
HS-SKL
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Bangkok
MSN:
110-229
YOM:
1979
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was engaged in a local post maintenance test flight at Bangkok-Don Mueang Airport. After takeoff, while in initial climb, the crew encountered technical problems with the left main gear. After being cleared by ATC, the crew decided to return for an emergency landing and made a turn then completed a belly landing. The aircraft came to rest on the main runway and was damaged beyond repair. Both pilots escaped uninjured.
Probable cause:
It was determined that a an element of the left main landing gear strut failed during initial climb, causing the loss of several elements of the landing gear.

Crash of a Boeing 737-3Z6 in Muang Khon Kaen: 6 killed

Date & Time: Mar 30, 1993
Type of aircraft:
Operator:
Registration:
33-333
Flight Type:
Survivors:
No
Schedule:
Bangkok - Muang Khon Kaen
MSN:
24480
YOM:
1989
Flight number:
KAT333
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
During the days prior to the accident, various problems with the pitch-trim system and the horizontal stabilizers were noticed and reported. Repairs were conducted by technicians from the Royal Thai Air Force but apparently, not according to the Boeing published procedures, so a Boeing engineer was dispatched in Thailand to proceed to controls and tests. On approach to Muang Khon Kaen Airport, the aircraft started to pitch up and down then stalled. The crew increased engine power and regained control for few seconds when the aircraft stalled a second time few seconds later. The crew elected to regain control and to reduce the rate of descent when the aircraft entered an uncontrolled descent and crashed in a rice paddy field located few km from the airport. The aircraft was destroyed and all six occupants were killed. The aircraft has the dual registration 33-333 (military) and HS-TGQ (civil).
Probable cause:
The loss of control occurred when the crew retracted the flaps and increased engine power, probably following a technical problems with the pitch-trim control system. Investigations were unable to determine the exact cause of the pitch control system malfunction.

Crash of an Airbus A310-304 near Kathmandu: 113 killed

Date & Time: Jul 31, 1992 at 1245 LT
Type of aircraft:
Operator:
Registration:
HS-TID
Survivors:
No
Site:
Schedule:
Bangkok - Kathmandu
MSN:
438
YOM:
1987
Flight number:
TG311
Country:
Region:
Crew on board:
14
Crew fatalities:
Pax on board:
99
Pax fatalities:
Other fatalities:
Total fatalities:
113
Circumstances:
Thai Airways Flight 311 was conducting the Sierra (VOR/DME) approach to runway 02 at Tribhuvan International Airport, in instrument weather conditions. A flap fault occurred while the flight was on the approach; this caused the crew to ask for clearance back to Calcutta, a decision that was in keeping with both Company and performance requirements, which necessitate the use of full flaps for the steep final approach. Shortly (21 seconds) after making this request, at a distance of approximately 12 nm from the Kathmandu VOR, the flap fault was rectified by retracting and then reselecting the flaps. The crew determined that it was not possible to continue the straight-in approach, due to the steep descent angles required and the position of the aircraft. The crew stated to the control tower that they wished to start their approach again and requested a left turn back to the Romeo fix, which is 41 nm south south-west (202 radial) of the Kathmandu VOR. The Controller, in the non-radar environment, responded by clearing the flight to make the Sierra approach, which starts at the 202 radial and 16 nautical miles from the VOR. The crew response to the clearance was to report that, at the moment, they couldn't land and to ask again for left turn back to Romeo to start their approach again. After further dialogue with the controller, which included requests for a left turn, the crew unilaterally initiated a right turn from the aircraft's 025° heading and commenced a climb from an altitude of 10,500 feet to FL180, when the flight was about 7 nm south of the Kathmandu VOR. The crew reported to the tower controller that the flight was climbing and the controller replied by instructing the crew to report at 16 nm for the Sierra approach. During the turn, there was more discussion between the tower controller and the flight, where it was established that the aircraft was to maintain an altitude of FL115 and was to 'proceed to Romeo' and contact the Area Control Center (ACC) controller. The flight, commencing a descent while in the turn, completed a 360° turn, momentarily rolling out on headings of 045° and 340°, and again proceeded toward the north on a heading of 025° magnetic. When the flight was about 5 nm south-west of the Kathmandu VOR, the crew contacted the ACC and stated that the aircraft was 'heading 025' and they wished to proceed to Romeo to start their approach again; adding they had 'technical problems concerned with the flight.' It was again established that the flight was to proceed to Romeo and the crew agreed to 'report over Romeo.' It was determined from the cockpit voice recorder that the crew was in the process of inserting 'Romeo' and other related navigational information in the Flight Management System, but were experiencing difficulties. The flight continued towards the north on a heading of 025° and then, at about 16 nm north, the heading was altered to the left to 005°. Slightly over one minute later, the Ground Proximity Warning System (GPWS) sounded the warning 'terrain, terrain' followed by 'whoop whoop pull-up'; the aural warning continued until impact approximately 16 seconds later. Engine thrust was increasing and 'Level Change' had been announced on the cockpit, just before the impact occurred at the 11,500-foot level of a 16,000-foot peak; the accident site was located on the 015 radial (north-north east) at 23.3 nm from the Kathmandu VOR. The aircraft was destroyed and all 113 occupants were killed.
Probable cause:
TG311 flight crew's management of the aircraft flight path wherein the flight proceeded in a northerly direction which was opposite to the cleared point Romeo to the South; ineffective radio communication between the area control centre and the TG311 flight crew which allowed the flight to continue in the wrong direction, in that the TG311 crew never provided the aircraft's VOR radial when stating DME and the controller never solicited this information and thus the aircraft's position was not transmitted at any time; and ineffective cockpit crew coordination by the TG311 crew in conducting flight navigation duties. Contributing factors were: the misleading depiction of Romeo on the operator's approach chart used by the flight crew; a flap fault, although corrected, required that the initial approach be discontinued; and radio communication difficulties between the TG311 crew and the air traffic controllers that stemmed from language difficulties and ineffective discussion of apparent unresolved problems.

Crash of a Douglas VC-47A in Bangkok

Date & Time: Jan 21, 1992
Operator:
Registration:
L2-41/18
Flight Type:
Survivors:
Yes
MSN:
15026/26471
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Bangkok-Don Mueang Airport, the aircraft went out of control, veered off runway to the left, struck a fence and crossed a drainage ditch before coming to rest. There were no casualties.

Crash of a Boeing 767-3Z9ER near Phu Toey: 223 killed

Date & Time: May 26, 1991 at 2317 LT
Type of aircraft:
Operator:
Registration:
OE-LAV
Flight Phase:
Survivors:
No
Schedule:
Hong Kong - Bangkok - Vienna
MSN:
24628
YOM:
1989
Flight number:
NG004
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
213
Pax fatalities:
Other fatalities:
Total fatalities:
223
Captain / Total flying hours:
11750
Copilot / Total flying hours:
6500
Aircraft flight hours:
7444
Aircraft flight cycles:
1135
Circumstances:
Lauda Air Flight 004 (NG004) was a scheduled passenger flight from Hong Kong to Vienna, Austria with an en route stop in Bangkok, Thailand. The flight departed Bangkok at 1602 hours on May 26, 1991 for the final flight sector to Vienna Austria. All pre-flight, ground, and flight operations appear routine until five minutes and forty five seconds after the cockpit voice recorder (CVR) recorded the sounds of engine power being advanced for takeoff. At this point a discussion ensued between the crew members regarding an event later identified as a crew alert associated with a thrust reverser isolation valve. The crew discussed this alert for some four and one half minutes. The Quick Reference Handbook (QRH) was consulted to determine appropriate crew actions in response to the alert. No actions were required, and none were identified as being taken. Ten minutes and twenty seconds into the flight the co-pilot advised the pilot-in-command of the need for rudder trim to the left. The pilot-in-command acknowledged the co-pilot's statement. Fifteen minutes and one second into the flight, the co-pilot stated "ah reverser's deployed." Sounds similar to airframe shuddering were then heard on the CVR. Twenty nine seconds later the CVR recording ended with multiple sounds thought to be structural breakup. Flight conditions were recovered from non-volatile memory in the left engine electronic engine control (EEC). At the suspected point of reverser deployment, the EEC readout indicated that the airplane was at an approximate altitude of 24,700 feet, a speed of Mach 0.78, and developing climb power. The airplane crashed in mountainous jungle terrain at 14 degrees 44 minutes North latitude and 99 degrees 27 minutes East longitude at approximately 1617 hours. Night time visual meteorological conditions prevailed. All 223 occupants were killed.
Probable cause:
The Accident Investigation Committee of the Government of Thailand determines the probable cause of this accident to be uncommanded in-flight deployment of the left engine thrust reverser, which resulted in loss of flight path control. The specific cause of the thrust reverser deployment has not been positively identified.
Final Report:

Crash of a Tupolev TU-134AK-1 in Ho Chi Minh-City

Date & Time: Jan 12, 1991
Type of aircraft:
Operator:
Registration:
VN-A126
Survivors:
Yes
Schedule:
Bangkok - Ho Chi Minh-City
MSN:
60435
YOM:
1978
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
72
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the last segment on approach to Ho Chi Minh-Ville-Tan Son Nhat Airport, at a height of about 30 feet, the aircraft lost height, causing the left main gear to struck the ground short of runway threshold. The aircraft then landed hard and came to a halt on the main runway. All 79 occupants were evacuated, among them five passengers were injured.
Probable cause:
It is believed the aircraft lost height on short final due to an insufficient speed.
The following contributing factors were reported:
- Poor planned approach on part of the crew.
- Poor crew coordination.
- Lack of supervision and crew cross checks.

Crash of a De Havilland Dash-8-103 in Koh Samui: 38 killed

Date & Time: Nov 21, 1990 at 1815 LT
Operator:
Registration:
HS-SKI
Survivors:
No
Schedule:
Bangkok - Koh Samui
MSN:
172
YOM:
1989
Flight number:
PG125
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
38
Captain / Total flying hours:
14764
Captain / Total hours on type:
521.00
Copilot / Total flying hours:
674
Copilot / Total hours on type:
235
Aircraft flight hours:
3416
Aircraft flight cycles:
2998
Circumstances:
On final approach to Koh Samui Airport runway 35, the aircraft entered an area of heavy rain falls. As the crew was unable to locate the runway, the captain decided to initiate a go-around procedure. With flaps fully extended, the crew increased power and started to gain height when the aircraft rolled to the left to an angle of 75° then entered an uncontrolled descent and crashed at a speed of 147 knots about 5 km short of runway threshold. The aircraft disintegrated on impact and all 38 occupants were killed.
Probable cause:
The pilot suffered a spatial disorientation which resulted in an improper control of the aircraft. The following contributing factors were reported:
- The pilot continued the approach in bad weather conditions with limited or no visual reference with the ground.
- Both pilots attention was focused on trying to locate the runway, neglecting the standard cross checks and mutual checks on approach and failing to monitor the aircraft attitude.
- Poor crew coordination,
- Lack of teamwork,
- Poor flight monitoring that contributed to the loss of situational awareness and improper control of the aircraft.

Crash of a Tupolev TU-134A in Bangkok: 76 killed

Date & Time: Sep 9, 1988 at 1138 LT
Type of aircraft:
Operator:
Registration:
VN-A102
Survivors:
Yes
Schedule:
Hanoi - Bangkok
MSN:
60925
YOM:
1978
Flight number:
VN831
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
76
Aircraft flight hours:
4068
Aircraft flight cycles:
1537
Circumstances:
The approach to Bangkok-Don Mueang Airport was initiated in poor weather conditions with a reduced visibility due to heavy rain falls. On final, the aircraft was too low when it struck the ground and crashed about 6 km short of runway. 14 occupants were rescued while 76 others were killed. The aircraft was destroyed.
Probable cause:
It was determined that after passing the outer marker, without visual contact with the ground due to heavy rain falls, the crew passed the decision height when the aircraft struck the ground and crashed. A loss of altitude caused by possible windshear is not ruled out.

Crash of a Douglas AC-47 in Bangkok

Date & Time: Feb 8, 1988
Operator:
Registration:
L2-34/13
Flight Type:
Survivors:
Yes
MSN:
13740
YOM:
1944
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed upon landing at Bangkok-Don Mueang Airport for unknown reasons. There were no casualties but the aircraft was damaged beyond repair.