Thai Airways International Flight 311

Thai Airways International Flight 311

File:Thai Airways International Airbus A310-300 JetPix.jpg HS-TID, the aircraft involved in the accident seen at Don Mueang International Airport in April 1992
Accident summary
Date	31 July 1992
Summary	Controlled flight into terrain
Site	Langtang National Park, Nepal
Passengers	99
Crew	14
Injuries (non-fatal)	0
Fatalities	113 (all)
Survivors	0
Aircraft type	Airbus A310-304
Operator	Thai Airways International
Registration	HS-TID
Flight origin	Don Mueang International Airport, Bangkok, Thailand
Destination	Tribhuvan International Airport, Kathmandu, Nepal

Thai Airways International Flight 311 was a flight from Bangkok, Thailand's Don Mueang International Airport to Kathmandu, Nepal's Tribhuvan International Airport. On 31 July 1992, an A310-304 on the route, registration HS-TID, crashed on approach to Tribhuvan. All 113 on board were killed.

Accident

Flight 311 departed Don Mueang at 10:30 local time. After crossing into Nepalese airspace the pilots contacted air traffic control and were cleared for an instrument approach from the south called the "Sierra VOR Circling Approach" for Runway 20. Nepalese ATC at the time was not equipped with radar.

Shortly after reporting the Sierra fix ten miles south of the Kathmandu VOR, the aircraft called ATC asking for a diversion to Calcutta, India because of a "technical problem". Before ATC could reply, the flight rescinded their previous transmission. The flight was then cleared for a straight-in Sierra approach to Runway 02 and told to report leaving 9,500 feet (2,896 m). The captain asked numerous times for the winds and visibility at the airport, but ATC merely told him that Runway 02 was available.

Memorial park in Kakani, Nepal

A number of frustrating and misleading communications (due partly to language problems and partly to the inexperience of the air traffic controller, who was a trainee with only nine months on the job) ensued between air traffic control and the pilots regarding Flight 311's altitude and distance from the airport. The captain asked four times for permission to turn left, but after receiving no firm reply to his requests he announced that he was turning right and climbed the aircraft to flight level 200. The controller handling Flight 311 assumed from the flight's transmissions that the aircraft had called off the approach and was turning to the south, and he therefore cleared the aircraft to 11,500 feet (3,505 m), an altitude that would have been safe in the area south of the airport. The flight descended back to 11,500 feet, went through a 360-degree turn, passed over the airport northbound, and crashed on a steep rock face in a remote area of the Langtang National Park at an altitude of 11,500 feet.

Investigation

Investigators from the Nepalese aviation authority, Airbus Industrie, and the Transportation Safety Board of Canada (which assisted with technical details) determined that the aircraft had experienced a minor fault in the workings of the inboard trailing flaps just after the aircraft reached the Sierra reporting fix. Concerned that the complex approach into Kathmandu in instrument conditions would be difficult with malfunctioning flaps and frustrated by ATC and his first officer's inconclusive and weak answers to his questions, the captain decided to divert to Calcutta. The flaps suddenly began to work properly, but the captain was forced to resolve more aspects of the difficult approach himself due to his first officer's lack of initiative. Only after numerous extremely frustrating exchanges with ATC was the captain able to obtain adequate weather information for the airport, but by that time he had overflown Kathmandu and the aircraft was headed towards the Himalayas.

Nepalese authorities found that the probable causes of the accident were the captain's and controller's loss of situational awareness; language and technical problems caused the captain to experience frustration and a high workload; the first officer's lack of initiative and inconclusive answers to the captain's questions; the air traffic controller's inexperience, poor grasp of English, and reluctance to interfere with what he saw as piloting matters such as terrain separation; poor supervision of the inexperienced air traffic controller; Thai Airways International's failure to provide simulator training for the complex Kathmandu approach to its pilots; and improper use of the aircraft's flight management system.

Victims

Nationality	Passengers	Crew	Total
Thailand	21	14	35
Nepal	23	0	23
Japan	17	0	17
United States	11	0	11
Belgium	5	0	5
Finland	5	0	5
Germany	4	0	4
Spain	3	0	3
South Korea	2	0	2
Israel	2	0	2
United Kingdom	2	0	2
Canada	2	0	2
New Zealand	1	0	1
Australia	1	0	1
Total	99	14	113

This accident took place only 59 days before PIA Flight 268 crashed just south of Kathmandu, killing 167.

The remains of the aircraft can still be seen in Langtang National Park, and have been featured in Lonely Planet guidebooks as a point of interest on the trek from Ghopte to the Tharepati Pass.

The flight number since the accident has been re-numbered to 319 for the outbound flight and 320 for the flight back to Bangkok.

See also

• Lists of accidents and incidents on commercial airliners
• Air safety
• Controlled flight into terrain

References and external links

• Media related to at Wikimedia Commons
• Accident description at the Aviation Safety Network
• Google Books description: "Thai Airways International Ltd. Airbus Industrie A310-304, HS-TID, Near Kathmandu, Nepal, 23NM NNE, 31 July 1992." Commission for the Accident Investigation of TG311, 1993.
• Pre-crash photos of HS-TID from Airliners.net
• Air Disaster, Vol. 3, by Macarthur Job, Aerospace Publications Pty. Ltd. (Australia), 1998 ISBN 1-875671-34-X, pp. 98–115.