Nepal Airlines Flight 555

2013 aviation accident

Nepal Airlines Flight 555

A Nepal Airlines DHC-6 Twin Otter similar to the aircraft involved in the accident

Accident
Date| 16 May 2013 (2013-05-16)
Summary| Runway overrun on landing due to Pilot error
Site| Jomsom Airport, Jomsom, Manang, Nepal
28°46′57″N 83°43′38″E﻿ / ﻿28.7826°N 83.7273°E﻿ / 28.7826; 83.7273
Aircraft
Aircraft type| de Havilland Canada DHC-6 Twin Otter
Operator| Nepal Airlines
IATA flight No.| RA555
ICAO flight No.| RNA555
Call sign| ROYAL NEPAL 555
Registration| 9N-ABO
Flight origin| Pokhara Airport, Nepal
Destination| Jomsom Airport, Nepal
Occupants| 21
Passengers| 18
Crew| 3
Fatalities| 0
Injuries| 7
Survivors| 21

Nepal Airlines Flight 555 was a short domestic scheduled flight from Pokhara Airport to Jomsom Airport in Nepal of about 20 minutes' flying time, operated by Nepal Airlines. On 16 May 2013 the de Havilland Canada DHC-6 Twin Otter aircraft operating the flight crashed while landing at Jomsom Airport. Seven of the twenty-one on board were seriously injured. There were no fatalities, but the aircraft was damaged beyond economic repair.[1][2][3]

## Aircraft & Crew[edit]

The aircraft involved was a de Havilland Canada DHC-6 Twin Otter bearing the registration 9N-ABO. It was built in 1979 and was operated by Nepal Airlines ever since. Following this incident, the aircraft was written off.[4]

The captain was Pradhan Dipendra 39 years old, with 8,451 total hours,8,131 of those on DHC-6's, the first officer was K.C. Suresh 29 years old, with 1,396 total hours, 1,202 of those on DHC-6's, both are Nepali citizens.[5]

## Passengers[edit]

Nationality  | Passengers  | Crew  | Injured

|
|
|

Nepal | 10 | 3 | 5
Japan | 8 | 0 | 2
Total | 18 | 3 | 7

There were eight Japanese tourists on the flight. All sustained injuries, with four of them in a critical condition according to a police officer.[6]

## Accident[edit]

While descending towards Jomsom, aerodrome flight information service (AFIS) informed the crew about southwesterly winds at 8 to 12 knots, runway 24 was in use. The first officer accepted runway 24 reading back they would report on downwind runway 24. Without discussion the captain took communication over from the first officer and requested runway 06, responded to the query by ATC that 8-12 knots were no problem, ATC therefore assigned runway 06 to the aircraft. A go-around briefing by the captain contained just one word: "standard".

The aircraft was configured for landing with full flaps and touched down on runway 06, 776 feet past the runway threshold. About 194 feet after touchdown the aircraft left the runway surface and entered soft ground to the right of the runway with the maximum deviation being 19 feet from the right hand runway edge. In the meantime the first officer, without communication taking place between the pilots, worked the after landing checklist and retracted the flaps.

While attempting to return the aircraft onto the runway the captain increased engine power with the intention to go around, the aircraft however had already lost a lot of speed due to application of brakes by the captain. Nonetheless, the aircraft accelerated but reached insufficient speed to produce sufficient lift for becoming airborne. The aircraft overran the end of runway 24, continued towards the river, ran through a barbered fence and gabion wall before falling down onto the edge of the river.

The captain, first officer and a female passenger received serious injuries, the flight attendant and 6 passengers received minor injuries, 11 passengers remained uninjured. The aircraft received substantial damage including the right hand wing being sheared off the aircraft.[7]

According to police, just after the aircraft touched down on the runway it veered towards the right and fell 20 metres (66 ft) down the bank of the Gandaki River. The forward fuselage was destroyed, but the rear of the aircraft remained intact. The left wing was found submerged in the river.[6]

## Investigation[edit]

An investigation will be carried out to determine what caused the accident. According to an official at Tribhuvan International Airport, preliminary reports have shown that windy conditions could have played a part in the crash.[1]

The CAAN quoted observers on the ground stating that after the aircraft had veered right onto grassy surface the aircraft sounds changed as if a takeoff was attempted and the speed of the aircraft increased. The CAAN analysed that according to the first officer's statement the approach speed was more than 100 knots while STOL procedures require an approach speed of 70 knots +/- 5 knots.

The weather, facilities and runway conditions at Jomsom were not contributing factors to the accident. The aircraft technical and loading condition were not factors into the accident.

The captain was experienced and had been checked out one by one to operate into STOL (short takeoff and landing) aerodromes by the instructor pilots. Nonetheless, the CAAN analysed, " the STOL landing procedure undertaken by PIC and the final decision taken in this flight were inappropriate." The CAAN analysed that AFIS on STOL aerodromes had been given the authority by Nepalese regulations to declare a runway closed provided there were tail winds in excess of 10 knots.

On 18 February 2014 the Civil Aviation Authority of Nepal (CAAN) released their final report concluding the probable causes of the accident were:

The inappropriate conduct of STOL procedure and landing technique carried out by the PIC, during landing phase and an endeavor to carry out take off again with no sufficient airspeed, no required lifting force and non availability of required runway length to roll. A contributory factor was the absence of proper CRM in terms of communication, coordination and briefing in between crew members on intention and action being taken by PIC, during pre and post landing phase.[7]

## Aftermath[edit]

The accident left Nepal Airlines with only two operational aircraft for its domestic flights. The airline said that it planned an engine exchange that would put three more Twin Otters, currently grounded, back in the air, but that process would take at least five months. In the meantime, the airline was expected to suffer a significant loss of market share.[8]

Contrary to common practices in aviation, Nepal Airlines did not retire the flight number 555 and still operates the flight from Pokhara to Jomsom under this number.[9]

## References[edit]

1. ^ a b Parashar, Utpal (16 May 2013). "7 critically injured in Nepal plane crash". Hindustan Times. Archived from the original on 22 May 2013. Retrieved 24 May 2013.
2. ^ "Five critically injured in Mustang plane crash (with photos)". República. 16 May 2013. Archived from the original on 14 September 2013. Retrieved 16 May 2013.
3. ^ Waldron, Greg (16 May 2013). "Nepal Airlines Twin Otter crashes, crew in critical condition". Flightglobal. Retrieved 16 May 2013.
4. ^ "REGISTRATION DETAILS FOR 9N-ABO (ROYAL NEPAL AIRLINES) DHC-6-300". Planelogger. Retrieved 1 April 2018.
5. ^ https://reports.aviation-safety.net/2013/20130516-1_DHC6_9N-ABO
6. ^ a b "Nepal plane crash injures 21, including 8 Japanese". The Washington Post. Associated Press. 16 May 2013. Archived from the original on 16 May 2013. Retrieved 24 May 2013.
7. ^ a b "Accident: Nepal DHC6 at Jomsom on May 16th 2013, runway excursion". avherald.com. Retrieved 12 October 2023.
8. ^ "NAC to lose market share due to lack of aircraft". The Himalayan Times. 17 May 2013. Archived from the original on 10 August 2014. Retrieved 31 May 2013.
9. ^ "Domestic Schedule". Nepal Airlines. Retrieved 1 April 2018.

* v
* t
* e

Aviation accidents and incidents in Nepal

1970s|

* Nepal plane hijack (June 1973)

1990s|

* Thai Airways International Flight 311 (July 1992)
* Pakistan International Airlines Flight 268 (September 1992)
* Everest Air Dornier 228 crash (July 1993)
* Hinduja Cargo Services Flight 8533 (July 1999)
* Necon Air Flight 128 (September 1999)
* Indian Airlines flight 814 hijacking (December 1999)

2000s|

* Royal Nepal Airlines crash (July 2000)
* Shangri-La Air Twin Otter Crash (August 2002)
* Yeti Airlines crash (June 2006)
* Shree Air Mil Mi-8 crash (September 2006)
* Yeti Airlines Flight 101 (October 2008)

2010s|

* Agni Air Flight 101 (August 2010)
* Tara Air crash (December 2010)
* Buddha Air Flight 103 (September 2011)
* Agni Air crash (May 2012)
* Sita Air Flight 601 (September 2012)
* Nepal Airlines Flight 555 (May 2013)
* Nepal Airlines Flight 183 (February 2014)
* 2015 Charikot Helicopter Crash (May 2015)
* Tara Air Flight 193 (February 2016)
* Air Kasthamandap PAC 750XL crash (February 2016)
* Summit Air Flight 409 (May 2017)
* US-Bangla Airlines Flight 211 (March 2018)
* 2019 Taplejung helicopter crash (February 2019)

2020s|

* Tara Air Flight 197 (May 2022)
* Yeti Airlines Flight 691 (January 2023)
* Manang Air helicopter crash (July 2023)

* v
* t
* e

Aviation accidents and incidents in 2013 (2013)

Jan 4

Transaereo 5074 Islander crash

Jan 16

Vauxhall helicopter crash

Jan 29

SCAT Airlines Flight 760

Feb 13

South Airlines Flight 8971

Feb 26

Luxor hot air balloon crash

Mar 4

Compagnie Africaine d'Aviation crash

Mar 8

ACE Air Cargo Flight 51

Mar 21

Berlin helicopter crash

Apr 7

Helicópteros del Pacífico Mil Mi-8 crash

Apr 13

Lion Air Flight 904

Apr 29

National Airlines Flight 102

May 16

Nepal Airlines Flight 555

Jun 10

Merpati Nusantara Airlines Flight 6517

Jun 29

2013 Eberswalde-Finow Zlin crash

Jul 1

Evo Morales grounding incident

Jul 2

Polar Airlines Flight 9949

Jul 6

Asiana Airlines Flight 214

Jul 7

Rediske Air DHC-3 Otter crash

Jul 22

Southwest Airlines Flight 345

Aug 9

Ethiopian Air Force An-12 crash

Aug 14

UPS Airlines Flight 1354

Aug 23

CHC Helicopters Eurocopter AS332 crash

Oct 3

Associated Aviation Flight 361

Oct 16

Lao Airlines Flight 301

Nov 17

Tatarstan Airlines Flight 363

Nov 19

Florida Learjet 35A crash

Nov 29

LAM Mozambique Airlines Flight 470

Nov 29

Glasgow helicopter crash

2012  ◄ ► 2014
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template