Crash of a Harbin Yunsunji Y-12-II in Lukla

Date & Time: Sep 26, 1992
Type of aircraft:
Operator:
Registration:
9N-ACI
Flight Phase:
Survivors:
Yes
Schedule:
Lukla - Kathmandu
MSN:
0069
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll at Lukla-Tenzing-Hillary Airport, at a speed of 85 knots, the nose gear collapsed. Out of control, the aircraft veered off runway and came to rest in a ditch. All 14 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the nose gear tyre burst after hitting stones coming from a pothole in the runway surface. This caused the nose gear to collapse.

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 De Havilland DHC-6 Twin Otter 300 in Lukla

Date & Time: Jun 9, 1991 at 1010 LT
Operator:
Registration:
9N-ABA
Survivors:
Yes
Schedule:
Kathmandu - Lukla
MSN:
301
YOM:
1971
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While descending to Lukla Airport, weather conditions deteriorated and the captain decided to go-around and to follow a holding pattern. Few minutes later, as he thought weather conditions improved, he decided to attempt to land and initiated a second approach. On short final, the aircraft entered a layer of low clouds and the aircraft was not properly aligned when it struck the runway surface and bounced. Out of control, it veered off runway and came to rest in a ravine. All 17 occupants were injured and the aircraft was destroyed.

Crash of a Short SC.7 Skyvan 3 Variant 100 in Dhangadhi: 25 killed

Date & Time: Dec 30, 1985
Type of aircraft:
Operator:
Registration:
RAN-23
Flight Type:
Survivors:
No
Site:
Schedule:
Katmandu – Dhangadhi
MSN:
1978
YOM:
1982
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
25
Circumstances:
While approaching Dhangadhi Airport, the twin engine airplane crashed in unknown circumstances in a wooded area located on a mountain slope, few km from the airfield. All 25 occupants were killed.

Crash of a Pilatus PC-6 Turbo Porter in Kathmandu: 5 killed

Date & Time: Mar 31, 1975 at 1200 LT
Operator:
Registration:
9N-AAZ
Flight Phase:
Survivors:
No
Schedule:
Kathmandu - Phaplu
MSN:
727
YOM:
1971
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Shortly after takeoff from Kathmandu Airport, while in initial climb, the single engine airplane went out of control and crashed in flames in a cornfield. The aircraft was destroyed by a post crash fire and all five occupants were killed, among them Louise Hillary and Belinda Hillary aged 16, spouse and daughter of the Alpinist Edmund Hillary.
Probable cause:
It was determined that the pilot failed to realize that a ground lock pin on one of the ailerons was still in place and not remove prior to departure.

Crash of a De Havilland DHC-6 Twin Otter 300 in Lukla

Date & Time: Oct 15, 1973
Operator:
Registration:
9N-ABG
Flight Phase:
Survivors:
Yes
Schedule:
Lukla - Kathmandu
MSN:
370
YOM:
1973
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances while taking off from Lukla-Tenzing-Hillary Airport. All six occupants escaped uninjured while the airplane was damaged beyond repair.

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 Pilatus PC-6 Porter in Katmandu

Date & Time: Feb 8, 1967
Operator:
Registration:
HB-FAX
Flight Type:
Survivors:
Yes
MSN:
344
YOM:
1960
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
201
Circumstances:
On short final in strong crosswinds, the airplane stalled and crashed within the runway threshold. There were no casualties but the aircraft was damaged beyond repair. It was reported that the fuel selector was positioned to the lower tank, which prevented the fuel to reach the engine because of the position of the aircraft on final approach.

Special thanks to Claude Rouge who shared the photos and personnel logbook from his father Frédy Rouge who was in charge of HB-FAX at that time.