Crash of a De Havilland DHC-6 Twin Otter 300 off Kuredu Island

Date & Time: Jul 2, 2015 at 1733 LT
Operator:
Registration:
8Q-MAN
Survivors:
Yes
Schedule:
Male - Kuredu Island
MSN:
435
YOM:
1974
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5075
Captain / Total hours on type:
4200.00
Copilot / Total flying hours:
988
Copilot / Total hours on type:
705
Aircraft flight hours:
24132
Circumstances:
Flight FLT371301, a Viking Air (De Havilland) DHC-6-300 aircraft with registration mark 8Q-MAN, crashed into the sea approximately 3 km southeast of Kuredu (KUR) at 1733 hrs on 2 July 2015. The aircraft was flying under visual flight rules (VFR) on a charter flight, carrying 11 passengers from Komandoo (KOM) to Kuredu (KUR). According to the operating crew, the aircraft was on final approach, northwest bound, to land at KUR. At approximately 400 feet, on selection of flaps to the fully down position, the aircraft pitched up and the aircraft was vibrating. The pilot flying (PF) could not control the aircraft and asked the PIC to take over the controls. The aircraft was in a nose-high attitude when the PIC took over the controls. The stall warning light illuminated. The PIC applied full left rudder, moved the control column forward and put the power levers to idle to recover the aircraft. The aircraft, however, did not respond to these actions. Flaps were then moved to the fully up position. The PIC was gaining some control at this stage but the aircraft continued turning right, losing height and impacted the sea before he could regain full control of the aircraft. On initial impact the left float detached. The aircraft then bounced and landed on the right float causing the right float to also detach from the aircraft. The right float was, however, trapped between the airframe and the engine for several minutes. With both floats detached from the aircraft and the right float still trapped between the airframe and engine, the aircraft stayed afloat until all passengers and crew evacuated. At the same time the aircraft started tilting left causing water to rush inside and started sinking. All 11 passengers and three crew were able to evacuate the aircraft without injury, before the aircraft completely sank. The accident was notified to the Aircraft Accident Investigation Committee (AICC) at 1750 hrs. Investigation began on the same day. Inspectors arrived at the scene at 2300 hrs, about five and a half hours after the accident occurred.
Probable cause:
The investigation identified the following causes:
a. The aircraft was operated outside the centre of gravity limitations on the sector in which the accident occurred.
b. The load distribution errors went undetected because the mass and balance calculations were not carried out in accordance with the approved procedures, prior to the accident flight.
c. The co-pilot (PF) was not alerted to the impending stall as she neither saw the stall warning light illuminated nor heard the aural stall warning.
d. The PIC was not able to gain control of aircraft as developing stall was not recognized and incorrect recovery procedures were applied.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 near Port Moresby: 4 killed

Date & Time: Sep 20, 2014 at 0935 LT
Operator:
Registration:
P2-KSF
Survivors:
Yes
Site:
Schedule:
Woitape - Port Moresby
MSN:
528
YOM:
1977
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
19290
Captain / Total hours on type:
5980.00
Copilot / Total flying hours:
432
Copilot / Total hours on type:
172
Aircraft flight hours:
34327
Aircraft flight cycles:
46302
Circumstances:
A DHC-6 Twin Otter aircraft was returning from Woitape, Central Province, to Jacksons Airport, Port Moresby on the morning of 20 September 2014 on a charter flight under the instrument flight rules (IFR). The weather at Woitape was reported to have been clear, but at Port Moresby the reported weather was low cloud and rain. Witnesses reported that the summit of Mt Lawes (1,700 ft above mean sea level (AMSL)) was in cloud all morning on the day of the accident. When the aircraft was 36 nm (67 km) from Port Moresby, air traffic control gave the flight crew a clearance to descend maintaining visual separation from terrain and to track to a left base position for runway 14 right (14R) at Jacksons Airport, Port Moresby. The clearance was accepted by the crew. When the aircraft was within 9.5 nm (17.5 km) of the airport, the pilot in command (PIC) contacted the control tower and said that they were “running into a bit of cloud” and that they “might as well pick up the ILS [instrument landing system] if it’s OK”. The flight crew could not have conducted an ILS approach from that position. They could have discontinued their visual approach and requested radar vectoring for an ILS approach. However, they did not do so. The Port Moresby Aerodrome Terminal Information Service (ATIS), current while the aircraft was approaching Port Moresby had been received by the flight crew. It required aircraft arriving at Port Moresby to conduct an ILS approach. The PIC’s last ILS proficiency check was almost 11 months before the accident flight. A 3-monthly currency on a particular instrument approach is required under PNG Civil Aviation Rule 61.807. It is likely the reason the PIC did not request a clearance to intercept the ILS from 30 nm (55.5 km) was that he did not meet the currency requirements and therefore was not authorized to fly an ILS approach. During the descent, although the PIC said to the copilot ‘we know where we are, keep it coming down’, it was evident from the recorded information that his assessment of their position was incorrect and that the descent should not have been continued. The PIC and copilot appeared to have lost situational awareness. The aircraft impacted terrain near the summit of Mt Lawes and was substantially damaged by impact forces. Both pilots and one passenger were fatally injured in the impact, and one passenger died on the day after the accident from injuries sustained during the accident. Of the five passengers who survived the accident, three were seriously injured and two received minor injuries. One of the fatally injured passengers was not wearing a seat belt.
Probable cause:
The following contributing factors were identified:
- The flight crew continued the descent in instrument meteorological conditions without confirming their position.
- The flight crew’s assessment of their position was incorrect and they had lost situational awareness
- The flight crew deprived themselves of the “Caution” and “Warning” alerts that would have sounded about 20 sec and about 10 sec respectively before the collision, by not deactivating the EGPWS Terrain Inhibit prior to departure from Woitape.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 near Dihidanda: 18 killed

Date & Time: Feb 16, 2014 at 1330 LT
Operator:
Registration:
9N-ABB
Flight Phase:
Survivors:
No
Site:
Schedule:
Pokhara – Jumla
MSN:
302
YOM:
1971
Flight number:
RNA183
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
18
Captain / Total flying hours:
8373
Captain / Total hours on type:
8131.00
Copilot / Total flying hours:
365
Aircraft flight hours:
43947
Aircraft flight cycles:
74217
Circumstances:
On 16 February 2014, the Twin Otter (DHC6/300) aircraft with registration number 9N-ABB, owned and operated by Nepal Airlines Corporation (NAC), departed Kathmandu at 0610 UTC (1155 LT) on its schedule flight to Jumla carrying 18 persons on board including 3 crews. Detailed sectors to be covered by the flight No. RA 183/718 was Kathmandu–Pokhara–Jumla-Nepālganj (Night stop). Flight from Kathmandu to Pokhara completed in normal condition. After 17 minutes on ground at Pokhara airport and refueling 9N-ABB departed Pokhara at 0658 for Jumla. After Jumla flight, the aircraft was scheduled to Night stop at Nepālganj. Next day it was to do a series of shuttle flights from Nepālganj. Prevailing westerly weather had a severe impact on most of the domestic flights since last two days. A.M.E. of Engineering Department of NAC who had performed D.I. of 9N ABB had mentioned in his written report to the Commission that he had reminded the diversion of Bhojpur flight of NAC due weather and asked the Captain whether he had weather briefing of the Western Nepal or not. In response to the AME's query the Captain had replied casually that- "weather is moving from west to east and now west is improving". Pilots behavior was reported normal by the ground staffs of Kathmandu and Pokhara airports prior to the commencement of flight on that day. All the pre and post departure procedure of the flight were completed in normal manner. Before departure to Jumla from Pokhara, Pilots obtained Jumla and Bhairahawa weather and seems to be encouraged with VFR Weather at both stations. However, they were unable to make proper assessment of en route weather. PIC decided to remain south of track to avoid the terrain and weather. CVR read out revealed that pilots were aware and concerned about the icing conditions due to low outside air temperature. After around 25 minutes, probably maneuvering to avoid weather, the PIC instructed the co-pilot to plan a route further south of their position, to fly through the Dang valley. The copilot selected Dang in the GPS, on a bearing of 283°, and determined the required altitude was 8500ft. He then raised concerns that the aircraft may not have enough fuel to reach the planned destination. Approximately two and a half minutes before the accident, the PIC initiated a descent, and the copilot advised against this. As per CVR read out, last heading recorded by copilot, approximately one minute before the crash, was 280. The last one minute was a very critical phase of the flight during which PIC said I am entering (perhaps inside the cloud). At that time copilot called Bhairahawa Tower on his own and got latest Bhairahawa weather. While copilot was transmitting its last position report to Bhairahawa Control Tower (approximately 25 miles from Bhairahawa), PIC interrupted and declared to divert Bhairahawa. Bhairahawa Control Tower wanted the pilots to confirm their present position. But crews were very much occupied and copilot said STANDBY. Just few seconds before crash copilot had told PIC not to descend. Copilot also suggested PIC in two occasions - sir don't turn. Very unfortunately aircraft was crashed. The aircraft disintegrated on impact and all 18 occupants were killed.
Probable cause:
Controlled flight into terrain after the pilot-in-command lost situation awareness while cruising in IMC.
The following factors were considered as contributory:
- Deteriorated weather associated with western disturbance, unstable in nature and embedded CB,
- Inappropriate and insufficient crew coordination while changing course of action.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 310 in Kudat: 2 killed

Date & Time: Oct 10, 2013 at 1450 LT
Operator:
Registration:
9M-MDM
Survivors:
Yes
Schedule:
Kota Kinabalu - Kudat
MSN:
804
YOM:
1983
Flight number:
MWG3002
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4700
Aircraft flight hours:
56828
Aircraft flight cycles:
108882
Circumstances:
A de Havilland Canada DHC-6 Twin Otter 310, operated by MASwings, sustained substantial damage in an accident at Kudat Airport (KUD), Malaysia. The copilot and one passenger died, four others were injured. MASwings flight MH3002 operated on a domestic flight from Kota Kinabalu Airport (BKI) to Kudat. The captain was the pilot flying for this sector and the first officer was pilot monitoring. As the aircraft was approaching Kudat Airfield, Kudat Tower reported the weather conditions to be: wind at 270 degrees at 17 kts gusting 31 kts. The aircraft continued the approach on runway 04 and leveled off at 500 feet with flaps set at 10°. At this point the crew noticed that the approach for runway 04 had a strong tail wind. This was evident from the indicated airspeed observed by the crew which indicated 100 kts where the airspeed for flaps 10° should be 65kts. The windsock also indicated a tail wind. Noticing the approach for runway 04 was a tail wind condition, the crew decided to go around at a height of 500ft. Maintaining runway heading, the crew initiated a go around climbing to 1,000ft making a left tear drop and reposition for runway 22. On the approach for runway 22 the captain informed the first officer that if they could not land they would return to Kota Kinabalu. The aircraft was aligned with the centerline of runway 22 and 20° flaps was set. The aircraft continued to descend to 300ft. At this point the wind appeared to be calm as the aircraft did not experience any turbulence and the captain told the first officer that he was committed to land. Upon reaching 200ft the captain called for the flaps to be lowered to full down. As they were about to flare the aircraft to land, approximately 20ft above the runway, the aircraft was suddenly hit by a gust of wind which caused the aircraft to veer to the right with the right wing low and left wing high and the nose was pointing 45° to the right of runway 22. The crew decided to go around by applying maximum power; however the aircraft did not manage to climb successfully. The flaps were not raised and were still in the full flaps down position as the crew thought the aircraft was still low hence the flaps were not raised. The aircraft continued to veer to the right with right wing low and managed to only climb at a shallow rate. The aircraft failed to clear the approaching trees ahead and was unable to continue its climb because the airspeed was reducing. The presence of a full flaps configuration made it more difficult for the aircraft to climb. As the aircraft was on full power on both the engines, it continued to fly almost perpendicularly in relation to the runway and at a low height above the ground. The aircraft hit a tree top at the airfield perimeter fencing, disappeared behind the row of trees, hit another tree behind a house. It hit the right rear roof of the house, ploughed through the roof top of the kitchen, toilet and dining area, hit the solid concrete pillars of the car garage and finally hit the lamp post just outside the house fence. It swung back onto the direction of the runway and came to rest on the ground with its left engine still running. A woman and her 11-year old son who were in the living room at the time escaped unhurt.
Probable cause:
Based on the information from the recorded statements of witnesses and Captain of the aircraft, it clearly indicates that the aircraft was attempting to land on Runway 04 with a tail-wind blowing at 270° 15kts gusting up to 25kts on the first approach, contrary to what was reported by the Captain to the investigators. The demonstrated cross wind landing on the DHC6-310 is 25kts and tailwind landing is 10kts. The aircraft was unsettled and unstable until it passed abeam the terminal building which was not the normal touch down point under normal landing condition. The flap setting on the first approach with the tail-wind condition was at 10°, which is not in accordance with company’s procedures. A tail wind landing condition that will satisfy the criteria for the DHC6-310 is not more than 10kts tail-wind and a flap setting of not more than 20°. One of the stabilized approach criterias for visual conditions (VMC) into Kudat is landing configuration must be completed by 500ft Above Ground Level (AGL) for the DHC6-310 where else if the above conditions could not be met, a go-around should be initiated. Hence, the Crew should have initiated a go-around earlier before the aircraft reached 500ft AGL on the first approach. The aircraft should be in the correct landing configuration at or below the stabilized approach altitude of 500ft AGL, since the aircraft was not stable due to the tail wind and gusting weather. The procedure carried out on the approach for Runway 04 was not consistent with MASwings’ Standard Operating Procedure (SOP) for a tailwind condition. Nonetheless, the first approach for Runway 04 though was uneventful. On the second approach from Runway 22, the wind condition was still not favorable for landing, and gusting. The aircraft was believed to be slightly low on the initial approach and was still unstable. The flap setting for the second approach for Runway 22 was at full flap (37°). As the wind was gusting, a flap setting to full-down should be avoided for the landing as stated in company’s DHC6-310 SOP. With the full-flap configuration, the aircraft had difficulty to settle down on the runway thus dragging the aircraft until abeam the tower which is way beyond the normal touch down zone.
At the point where the aircraft was approaching to land it was reported that the aircraft was hit by a sudden gust, several factors, including the following, have been looked into:
a) Why was the aircraft unable to climb after initiating the go-around?
The full flap setting would require a zero degree pitch attitude to ensure the aircraft speed is maintained. With go-around power set, the zero degree pitch would ensure a climb without speed loss. A pitch above zero degree can cause the aircraft speed to decrease and induce a stall condition resulting in the aircraft being unable to climb.
b) Was the go-around technique executed correctly, taking into consideration that the wind was blowing from 270° and gusting?
The Captain had said that "I applied maximum power and expected the aircraft to climb. At this point, the aircraft was still in left-wing high situation. I noticed the aircraft did make a climb but it was a shallow climb. I did not retract the flaps to 20°, as at that time, in my mind, the aircraft was still low."
c) Under normal conditions, the rule of thumb for initiating a go-around procedure is to apply maximum power, set attitude to climb, confirm airspeed increasing and reduce the flap setting. This procedure was found not to be properly synchronized between MASwings Manuals and DHC6-310 Series 300 SOP.
d) Were the pilots in control of the aircraft?
Based on the Captain’s statement and other associated factors, the pilots were not in total control of the aircraft.

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

Date & Time: May 16, 2013 at 0833 LT
Operator:
Registration:
9N-ABO
Survivors:
Yes
Schedule:
Pokhara - Jomsom
MSN:
638
YOM:
1979
Flight number:
RNA555
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8451
Captain / Total hours on type:
8131.00
Copilot / Total flying hours:
1396
Copilot / Total hours on type:
1202
Aircraft flight hours:
32291
Aircraft flight cycles:
54267
Circumstances:
The Twin Otter (DHC6/300) aircraft with registration number 9N-ABO, owned and operated by Nepal Airlines Corporation (NAC), departed Kathmandu to Pokhara for night stop on 15 May 2013 in order to accomplish up to 5 (five) Pokhara-Jomsom-Pokhara charter flights planned for the subsequent day on 16 May 2013. As per the programme, the aircraft completed first charter flight from Pokhara to Jomsom sector on 16 May 2013 morning after one and half hour waiting on ground due weather. For this second flight, the aircraft departed at 0225 UTC (08:10LT) from Pokhara to Jomsom in the command of Capt. Dipendra Pradhan and Mr. Suresh K.C. as co-pilot. There were 19 passengers including one infant and 3 crew members on board. The aircraft was operating under Visual Flight Rules (VFR). As per the CVR readout there was no reported difficulties and all the pre and post departure procedure and en-route portion of the flight were completed in normal manner. There was no indication of lacking of information and advice from Jomsom Tower. At first contact the co-pilot called Jomsom Tower and reported its position at PLATO (a compulsory reporting point) at 9 miles from Jomsom airport at 12500ft. AMSL. The Jomsom Tower advised runway 24 wind south westerly 08-12 KTS, QNH 1020, Temp 13 degree and advised to report downwind for runway 24.The co-pilot accepted by replying to join downwind for runway 24. There was no briefing and discussion between the two pilots regarding the tail wind at the airport. The PIC, then, took over the communication function from co-pilot and called Jomsom Tower, requesting to use runway 06 instead of runway 24, despite the advice of tower to use runway 24 to avoid tail wind effect in runway 06. Jomsom Tower repeated the wind speed to be 08-12 KTS for the runway 06, to which the PIC read back the wind and answered to have ”no problem”. As per the PIC request the Jomsom Tower designated runway 06 for landing and advised to report on final runway 06. The PIC did read back the same. The pre landing checklist was used, flaps with full fine in propeller rpm were taken and full flaps was also taken before touchdown. In the briefing of “missed approach” the PIC had answered to be “standard”. The aircraft touched down runway of Jomsom airport at 0245 UTC (08:30LT) at a distance of approximately 776 ft, far from the threshold of runway 06. After rolling 194 ft. in the runway, the aircraft left runway and entered grass area in the right side. The aircraft rolled around 705 ft in the grass area and entered the runway again. The maximum deviation from the runway edge was 19 ft. The Commission has observed that when aircraft touched down the runway, it was not heading in parallel to the runway centreline. After touchdown the aircraft rolled around 194ft on the runway, left the paved area and started rolling in the grass area in the right side. During the landing roll, when the aircraft was decelerating, the co-pilot had raised the flaps as per the existing practice of carrying out “after the landing “checks". As per the observation of passenger seated just behind the cockpit, after touchdown of the aircraft there was no communication between pilot and co-pilot. It seemed that pilot was busy in cockpit and facing problem. It was obvious that PIC was in dilemma in controlling aircraft. He added power to bring aircraft into the runway with an intention to lift up the aircraft. He did not brief anything to copilot about his intention and action. He started adding power with the intention of lifting up, but the aircraft was already losing its speed, due to extension of flaps by co-pilot without briefing to PIC and use of brakes (light or heavy, knowingly and unknowingly) simultaneously by the PIC. The accelerating aircraft with insufficient speed and lift to take off ran out of the runway 24 end, continued towards the river, hit the barbed fence and gabion wall with an initial impact and finally fell down into the edge of river. The left wing was rested in the mid of the river preventing the aircraft submerged into the river.
Probable cause:
The Accident Investigation Commission has determined the most probable cause of the accident as 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. Contributory factors to the occurrence is 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.
Final Report:

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

Date & Time: Apr 17, 2013 at 1435 LT
Operator:
Registration:
RDPL-34180
Flight Phase:
Survivors:
Yes
Schedule:
Sam Neua – Vientiane
MSN:
231
YOM:
1969
Flight number:
LOA201
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Sam Neua-Nathong Airport, while in initial climb, the twin engine aircraft collided with trees, lots height and crashed in a small river located 200 metres past the runway end. All 18 occupants were injured, five seriously. The aircraft was damaged beyond repair.

Crash of a De Havilland DHC-6 Twin Otter 300 on Mt Elizabeth: 3 killed

Date & Time: Jan 23, 2013 at 0827 LT
Operator:
Registration:
C-GKBC
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Amundsen-Scott Station - Terra Nova-Zucchelli Station
MSN:
650
YOM:
1979
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
22300
Captain / Total hours on type:
7770.00
Copilot / Total flying hours:
790
Copilot / Total hours on type:
450
Aircraft flight hours:
28200
Circumstances:
The aircraft departed South Pole Station, Antarctica, at 0523 Coordinated Universal Time on 23 January 2013 for a visual flight rules repositioning flight to Terra Nova Bay, Antarctica, with a crew of 3 on board. The aircraft failed to make its last radio check-in scheduled at 0827, and the flight was considered overdue. An emergency locator transmitter signal was detected in the vicinity of Mount Elizabeth, Antarctica, and a search and rescue effort was initiated. Extreme weather conditions hampered the search and rescue operation, preventing the search and rescue team from accessing the site for 2 days. Once on site, it was determined that the aircraft had impacted terrain and crew members of C-GKBC had not survived. Adverse weather, high altitude and the condition of the aircraft prevented the recovery of the crew and comprehensive examination of the aircraft. There were no indications of fire on the limited portions of the aircraft that were visible. The accident occurred during daylight hours.
Probable cause:
The accident was caused by a controlled flight into terrain (CFIT).
Findings:
The crew of C-GKBC made a turn prior to reaching the open region of the Ross Shelf. The aircraft might have entered an area covered by cloud that ultimately led to the aircraft contacting the rising terrain of Mount Elizabeth.
Other findings:
The cockpit voice recorder (CVR) was not serviceable at the time of the occurrence.
The company did not have a practice in place to verify the functionality of the CVR prior to flight.
The rate of climb recorded in the SkyTrac ISAT-100 tracking equipment prior to contacting terrain was consistent with the performance figures in the DHC-6 Twin Otter Series 300 Operating Data Manual 1-63-1, Revision 7.
Final Report:

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

Date & Time: Mar 9, 2012 at 1130 LT
Operator:
Registration:
FAP-317
Flight Type:
Survivors:
Yes
Schedule:
Iquitos - Caballococha
MSN:
324
YOM:
1971
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The seaplane landed hard in the Caballococha's Laguna. Upon landing on water, the right float was torn off, the aircraft overturned and sank. All 11 occupants were rescued and the aircraft was damaged beyond repair. It was performing a flight from Iquitos on behalf of the 42nd Group of the Peruvian Air Force.