Country
Operator Image

Crash of an ATR72-500 in Pokhara: 72 killed

Date & Time: Jan 15, 2023 at 1057 LT
Type of aircraft:
Operator:
Registration:
9N-ANC
Survivors:
No
Schedule:
Kathmandu - Pokhara
MSN:
754
YOM:
2007
Flight number:
YT691
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
68
Pax fatalities:
Other fatalities:
Total fatalities:
72
Aircraft flight hours:
28731
Aircraft flight cycles:
30104
Circumstances:
The airplane departed Kathmandu-Tribhuvan Airport at 1032LT on a schedule service (YT691) to Pokhara, carrying 68 passengers and a crew of four. On final approach to Pokhara Airport in excellent weather conditions, the airplane entered a slight pitch up attitude, rolled to the left up to 90° (the left wing apparently stalled) then crashed on the bank of the River Seti, bursting into flames. The airplane was totally destroyed and the wreckage was found about 1,9 km short of runway 12 of the new Pokhara International Airport that was open to traffic January 1st, 2023. Part of the debris were found on the top of the hill and others down in the river bed. No one is believed to have survived the crash.
Probable cause:
In a preliminary report, the Nepalese Authorities confirmed the following points:
- At 10:56:27, the PF disengaged the Autopilot System (AP) at an altitude of 721 feet Above Ground Level (AGL). The PF then called for “FLAPS 30” at 10:56:32, and the PM replied, “Flaps 30 and descending”. The flight data recorder (FDR) data did not record any flap surface movement at that time. Instead, the propeller rotation speed (Np) of both engines decreased simultaneously to less than 25%1 and the torque (Tq) started decreasing to 0%, which is consistent with both propellers going into the feathered condition. On the cockpit voice recorder (CVR) area microphone recording, a single Master Caution chime was recorded at 10:56:36. The flight crew then carried out the “Before Landing Checklist” before starting the left turn onto the base leg. During that time, the power lever angle increased from 41% to 44%. At the point, Np of both propellers were recorded as Non-Computed Data (NCD) in the FDR and the torque (Tq) of both engines were at 0%. When propellers are in feather, they are not producing thrust.
- When both propellers were feathered, the investigation team observed that both engines of 9N-ANC were running flight idle condition during the event flight to prevent over torque. As per the FDR data, all the recorded parameters related to engines did not show any anomaly. At 10:56:50 when the radio altitude callout for five hundred feet3 was annunciated, another “click” sound was heard. The aircraft reached a maximum bank angle of 30 degrees at this altitude. The recorded Np and Tq data remained invalid. The yaw damper disconnected four seconds later. The PF consulted the PM on whether to continue the left turn and the PM replied to continue the turn. Subsequently, the PF asked the PM on whether to continue descend and the PM responded it was not necessary and instructed to apply a little power. At 10:56:54, another click was heard, followed by the flaps surface movement to the 30 degrees position.
- When ATC gave the clearance for landing at 10:57:07, the PF mentioned twice that there was no power coming from the engines. At 10:57:11, the power levers were advanced first to 62 degrees then to the maximum power position. It was followed by a “click” sound at 10:57:16. One second after the “click” sound, the aircraft was at the initiation of its last turn at 368 feet AGL, the high pressure turbine speed (Nh) of both engines increased from 73% to 77%.
- It is noted that the PF handed over control of the aircraft to the PM at 10:57:18. At 10:57:20, the PM (who was previously the PF) repeated again that there was no power from the engines. At 10:57:24 when the aircraft was at 311 feet AGL, the stick shaker was activated warning the crew that the aircraft Angle of Attack (AoA) increased up to the stick shaker threshold.

Crash of a BAe 4101 Jetstream 41 in Siddharthanagar

Date & Time: Sep 24, 2016 at 1656 LT
Type of aircraft:
Operator:
Registration:
9N-AIB
Survivors:
Yes
Schedule:
Kathmandu – Siddharthanagar
MSN:
41017
YOM:
1993
Flight number:
YT893
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Siddharthanagar-Gautam Buddha Airport was completed in good weather conditions with a wind from the southeast at 4 knots and a 8 km visibility. After touchdown on runway 28, the twin engine aircraft was unable to stop within the remaining distance. It overran, lost its undercarriage and came to rest in bushes, some 110 metres past the runway end. All 32 occupants evacuated safely and the aircraft was damaged beyond repair.

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

Date & Time: Oct 8, 2008 at 0731 LT
Operator:
Registration:
9N-AFE
Survivors:
Yes
Schedule:
Kathmandu – Lukla
MSN:
720
YOM:
1980
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
18
Captain / Total flying hours:
8185
Captain / Total hours on type:
7180.00
Copilot / Total flying hours:
556
Copilot / Total hours on type:
341
Circumstances:
The aircraft departed Kathmandu-Tribhuvan Airport at 0651LT on a regular schedule service to the Lukla-Tenzing-Hillary Airport. On approach to runway 06, the crew encountered poor visibility due to foggy conditions. Despite the pilot did not establish any visual contact with the ground, he continued the approach when, on short final, the aircraft struck a rock and crashed just below the runway 06 threshold, bursting into flames. The captain was seriously injured while 18 other occupants were killed, among them 12 Germans, 2 Australians and 5 Nepalese.
Probable cause:
Controlled flight into terrain after the captain decided to continue the approach under VFR mode in IMC conditions.

Crash of a De Havilland DHC-6 Twin Otter 300 in Jumla: 9 killed

Date & Time: Jun 21, 2006 at 1203 LT
Operator:
Registration:
9N-AEQ
Survivors:
No
Schedule:
Nepālganj – Surkhet – Jumla
MSN:
708
YOM:
1980
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
9
Aircraft flight hours:
23392
Aircraft flight cycles:
36092
Circumstances:
The twin engine aircraft departed Nepālganj Airport on a domestic service to Jumla with an intermediate stop in Surkhet, carrying six passengers, three crew members and a load consisting of bags containing grains for a total of 941 kilos. While approaching Jumla Airport, the crew was informed that runway 27 was in use with a wind from 240 at 4 knots. For unknown reasons, the captain started the approach to runway 09 at 1201LT. At an excessive speed, he missed the runway, initiated a go-around procedure and passed to the right of the tower. Then, he started a steep turn to the left when the aircraft lost height and speed and crashed in a field located 500 meters east of the airport, bursting into flames. The aircraft was totally destroyed by impact forces and a post crash fire and all 9 occupants were killed.
Probable cause:
The crew's attempt to make a sudden go-around while close to runway 09 threshold with a very low circuit altitude and subsequent attempt to turn in a tight circuit with excessive angle of bank that led to a stall. The aircraft subsequently contacted terrain due to insufficient clearance available for effective stall recovery. The quick decisions to change runway added to the crew workload at a critical period which was aggravated by the breakdown of cockpit discipline. The other contributory factors leading to the accident were:
- Violation of company Standard Operating Procedures by flight crew,
- Insufficient monitoring of its flight training program and line operations by Yeti management,
- Inadequate oversight of Yeti Airlines by CAAN.

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

Date & Time: May 25, 2004 at 1356 LT
Operator:
Registration:
9N-AFD
Flight Type:
Survivors:
No
Site:
Schedule:
Kathmandu - Lukla
MSN:
651
YOM:
1979
Flight number:
YET117
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
While descending to Lukla Airport from the south following a cargo flight from Kathmandu, the crew encountered poor visibility due to clouds when, at an altitude of 11,600 feet, the aircraft struck the slope of a mountain located near the Lamjura Pass, in the Solukhumbu district. The wreckage was found west of the airport and all three crew members were killed.
Probable cause:
Controlled flight into terrain. The following factors were identified:
- Hazardous behaviour and attitudes of the captain such as overconfidence,
- The crew failed to comply with the approach routes, following a direct track,
- The crew failed to follow SOP's,
- The operator's policy for flying in adverse weather were incomplete and not up to date,
- Lack of communication by the operator,
- The operator was unable to perform internal investigations and execute corrective actions when required.