No fatalities

2013-05-16: De Havilland DHC-6 Twin Otter (9N-ABO) — Nepal Airlines — Jomsom, Nepal

Jomsom, NepalLanding (descent or approach)

On May 16, 2013, a De Havilland DHC-6 Twin Otter (registration 9N-ABO) operated by Nepal Airlines was involved in an aviation accident near Jomsom, Nepal during landing or approach. No fatalities were reported. Investigators recorded the probable cause as: The accident was caused by improper STOL landing techniques and an attempt to regain flight at insufficient speed, compounded by poor communication between the crew members. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 1 related events involving the same aircraft type or operator are linked below.

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781194227Data APIEditorial standards
Aircraft registered 9N-ABO
Aircraft registered 9N-ABO. Photo: Solundir / CC BY-SA 4.0, via Wikimedia Commons

A Nepal Airlines Corporation Twin Otter crashed into a riverbank after an overrun during a landing at Jomsom airport, resulting in no fatalities among the 22 people on board.

What happened

On 15 May 2013, a DHC6/3-series Twin Otter, registration 9N-ABO, arrived in Pokhara for an overnight stay to prepare for scheduled charter operations. The following morning, the aircraft departed Pokhara for Jomsom as the second flight of the day's program. On board were 19 passengers and 3 crew members.

During the approach to Jomsom, the pilot in command requested to land on runway 06 instead of the recommended runway 24, despite warnings from the tower regarding a tailwind component. The aircraft touched down on runway 06 at approximately 08:30 local time, significantly past the runway threshold. Following touchdown, the aircraft drifted off the paved surface and onto the grass on the right side of the runway.

As the aircraft decelerated, the co-pilot retracted the flaps as part of standard post-landing procedures without notifying the pilot in command. Simultaneously, the pilot attempted to regain control by applying power to lift the aircraft back onto the runway. However, due to insufficient airspeed and the loss of lift, the aircraft could not maintain flight. The plane exited the end of the runway, struck a barbed wire fence and a gabion wall, and eventually came to rest at the edge of a river, where the left wing became lodged in the water.

Findings

  • The pilot in command utilized improper landing techniques and failed to follow appropriate STOL (Short Takeoff and Landing) procedures.
  • An attempt was made to execute a go-around or lift the aircraft using power without having the necessary airspeed or runway length available.
  • There was a critical lack of Crew Resource Management (CRM), specifically regarding the failure of the crew to communicate intentions and coordinate actions during the landing and post-landing phases.

Probable cause

The accident was caused by improper STOL landing techniques and an attempt to regain flight at insufficient speed, compounded by poor communication between the crew members.