Yeti Airlines Flight 691

Yeti Airlines Flight 691

9N-ANC, the aircraft involved in the accident
Accident
Date	15 January 2023
Summary	Stalled and crashed during approach due to accidental feathering of propellers[1]
Site	Pokhara International Airport, Pokhara, Nepal 28°11′51″N 83°59′06″E / 28.19750°N 83.98500°E / 28.19750; 83.98500[2]
Aircraft
Aircraft type	ATR 72-500
Operator	Yeti Airlines
IATA flight No.	YT691
ICAO flight No.	NYT691
Call sign	YETI AIRLINES 691
Registration	9N-ANC
Flight origin	Tribhuvan International Airport
Destination	Pokhara International Airport
Occupants	72
Passengers	68
Crew	4
Fatalities	72
Survivors	0

Yeti Airlines Flight 691 was a scheduled domestic passenger flight flown by Yeti Airlines from Kathmandu to Pokhara in Nepal. On 15 January 2023, an ATR 72, the aircraft being operated on the route, stalled and crashed while landing at Pokhara killing all 68 passengers and 4 crew members on board.

External videos
Last moments of Flight 691, filmed from the ground.[3]
Video of livestream of the crash from inside the aircraft by Sonu Jaiswal[4]

The flight took off from Kathmandu's Tribhuvan International Airport at 10:33 am NST.^[5] It crashed on the bank of the Seti Gandaki River while on final approach to landing at Pokhara International Airport.^[6] A video filmed from the ground showed the aircraft banking steeply to the left before crashing 65 metres (213 ft) away.^[7][3][8] Another video of the crash was streamed live on Facebook from inside the plane by a passenger, Sonu Jaiswal, showing that the passengers were unaware of the situation until seconds before impact.^[9][10]

The crash occurred in Gandaki Province between the old Pokhara Airport and the new Pokhara International Airport, which was opened two weeks earlier and also where the aircraft was intending to land.^[11][12] The accident resulted in the deaths of all 68 passengers and 4 crew on board the ATR 72,^[13] and is Nepal's worst aviation accident since the crash of Pakistan International Airlines Flight 268 in 1992,^[14] the deadliest aviation accident in Nepalese domestic aviation,^[15] and the deadliest accident involving an ATR 72.^[16]

According to an official at the Pokhara International Airport, air traffic control cleared the flight to land on runway 30 heading from east to west, but the captain requested the opposing runway 12 heading from west to east, minutes before the crash. Flight-tracking service Flightradar24 noted that during the flight the aircraft had been transmitting inaccurate speed and altitude data.^[17]

The aircraft involved, manufactured in 2007, was a 15-year-old twin-engine turboprop ATR 72-500 registered as 9N-ANC with serial number 754. The aircraft was powered by two Pratt & Whitney Canada PW127M engines.^{[18][1]: 21–22}

There were 72 people on board, of which 68 were passengers and four were crew members.^[19][20] Among the passengers were 37 men, 25 women, and six children, three of whom were infants.^[21] Seventy-one bodies were found.^[22] On 17 January, authorities began returning the victims' bodies (the majority of which were burnt beyond recognition) to their families.^[23][24] The United States Department of State announced that two U.S. citizens died in the crash,^[25] although Nepalese authorities did not report any American deaths.^[26]

The plane was under the command of senior captain Kamal KC with Anju Khatiwada as copilot. Khatiwada's husband, Dipak Pokhrel, who also worked for Yeti Airlines, died in the 2006 Yeti Airlines Twin Otter crash. Khatiwada was set to qualify as a captain upon the successful completion of the flight.^[27]

The airport was closed as authorities launched a rescue operation.^[36] The Government of Nepal summoned an emergency cabinet meeting following the crash. Prime Minister Pushpa Kamal Dahal said he was deeply saddened by the tragic accident.^[21] The Office of the Prime Minister declared 16 January to be a national day of mourning, and the flag of Nepal was flown at half-staff.^[37] Yeti Airlines cancelled all regular flights scheduled for the day.^[21]

Experts noted that the video from the ground taken moments before the crash showed the aircraft's nose noticeably high before the left wing suddenly dropped, probably indicating a stall.^[38] Hours after the crash, a five-member committee headed by Nagendra Ghimire was set up to investigate the accident in conjunction with the French Bureau of Enquiry and Analysis for Civil Aviation Safety.^[39]

On 16 January, the flight data and cockpit voice recorders were found;^[40] the recorders were examined in Singapore and with assistance from Transportation Safety Board of Canada, Bureau of Enquiry and Analysis for Civil Aviation Safety, and Transport Safety Investigation Bureau of Singapore.^[41][42]

About a month later, on 13 February, a preliminary report was released, which largely reproduced all relevant logs.

(PF = Pilot Flying, PM = Pilot Monitoring):^[43]

At 10:56:27, the PF disengaged the Autopilot System (AP) at an altitude of 721 feet (220 m) 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% and the torque (Tq) started decreasing to 0%, which is consistent with both propellers going into the feathered condition [...]

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 this point, the Np of both propellers was recorded as Non-Computed Data (NCD) in the FDR and the torque (Tq) of both engines was at 0%. When propellers are in feather, they are not producing thrust [...]

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. At 10:57:20, the PM (who was previously the PF) repeated again that there was no power from the engines [...]

The aircraft's propellers had been feathered for about a minute before the crash, causing the engine to produce no thrust and lead the aircraft into a stall; the condition levers, which control the propellers, were discovered from the wreckage set to the feathered position.^[44][a] Seconds preceding the crash, the pilots discussed a total lack of power and even moved the power lever to the extreme but failed to recognize that the condition levers were incorrectly set.^[43] The condition levers and the flap lever are next to each other in an ATR 72; experts speculate that the monitoring pilot (Kamal KC) had inadvertently moved the former in place of the latter, when asked of by the flying pilot. While, about twenty seconds later, he would set the flap lever properly on his own, he failed to account for his previous mistake, implying that the landing checklist was not properly followed.^[44][46]

Due to the shortened final approach leg for runway 12 for this flight and another flight three days before it that landed on the same runway, the stabilization criteria for a visual approach, which is important for a safe landing, was not met at the height of 500 feet (150 m) above ground level. This led the Aircraft Accident Investigation Commission to recommend the Civil Aviation Authority of Nepal (CAAN) conduct a comprehensive study for the determination of an appropriate flight path that allows a stabilized visual approach.^[43]

On 15 March, the Government of Nepal extended the deadline by 45 days to the investigation commission for the final report of the accident.^[47]

On 28 December 2023, the final report was released. It reiterated the preliminary findings that the accidental change of position of both condition levers to the feathered position resulted in the loss of thrust, leading to the aerodynamic stall and crash. Some other contributing factors are also found, mostly human errors due to a high workload, lack of appropriate technical and skill-based training, ineffective crew resource management (CRM), lack of sterile cockpit discipline, and the non-compliance with standard operating procedures (SOP).^[1][48]

• List of accidents and incidents involving airliners by airline (P–Z)
• List of accidents and incidents involving commercial aircraft
• List of airplane accidents in Nepal
• TransAsia Airways Flight 235