Country
code

Sabah

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 Fokker 50 in Tawau: 34 killed

Date & Time: Sep 15, 1995 at 1222 LT
Type of aircraft:
Operator:
Registration:
9M-MGH
Survivors:
Yes
Schedule:
Kota Kinabalu - Tawau
MSN:
20174
YOM:
1990
Flight number:
MH2133
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
34
Captain / Total flying hours:
4892
Captain / Total hours on type:
427.00
Copilot / Total flying hours:
1162
Copilot / Total hours on type:
962
Aircraft flight hours:
10848
Aircraft flight cycles:
17483
Circumstances:
Flight MH2133 A Fokker 27 mark 050 bearing registration 9M-MGH was a scheduled domestic flight from Kota Kinabalu to Tawau, Sabah. The departure from Kota Kinabalu was delayed by approximately 30 minutes due to late arrival of the aircraft operated by a different set of flight crew from Labuan. The flight took off from Kota Kinabalu at 0419 hrs on an Instrument Flight Rules (IFR) flight plan via Airway W 423 direct to Tawau Very Omni Range (VOR) at flight level (FL) 170 with 53 persons on board. The departure out of Kota Kinabalu was uneventful and the weather en-route was insignificant. At 0442 hrs the flight established radio contact with Tawau Tower “MH 2133 we are maintaining FL 170, TMA 40, VTW 0505, presently at 94 DME VTW”. The controller then passed the weather for Tawau which was, “surface wind calm, visibility more than 10 km, rain north to north east, scattered 1600 feet and scattered 2700 feet, broken at 14000 feet, Temperature 30 degree C and QNH 1009 mb, Runway 17”. At 0443 hrs another aircraft call sign TSE 809 (a Cessna 206) flying along the same route as MH2133 but at 9500ft established radio contact with Tawau Tower, TSE 809 then reported that the flight was 65 DME from Tawau VOR. This was immediately followed by Tawau Tower asking MH2133 to report position from Tawau VOR which MH 2133 replied “57 DME and requested descent”. The controller then cleared MH 2133 to descend to 10500 feet. At this point in time there was also another aircraft MH2135 (a Boeing 737) heading towards Tawau cruising at FL 230 and cleared by the TOWER to descent to FL 180. MH 2135 was also notified by the TOWER of the Expected Approach Time (EAT) of 0530 hrs. At 0457 hrs TSE 809 reported that the flight was 44 DME from Tawau VOR. On hearing this transmission, MH 2133 requested a lower descend clearance, as it was 30 DME from Tawau VOR. It must be noted that at this juncture, MH 2133 was ahead of TSE 809 but at a higher altitude. The controller then asked TSE 809 whether there was any objection for MH2133 to descent through its level and become number One (1). Despite the fact that TSE 809 had no objection for MH 2133 to become number One (1), MH 2133 was asked by the controller to still maintain 10500 feet. At 0458:23 hrs, MH 2133 asked “MH 2133 confirm maintain 10500 feet?”. TOWER then replied “Affirm maintain 10500 number 2 in traffic”. At 0458:36 hrs MH 2133 again asked “MH 2133, 26 DME confirm we are still number 2?” TOWER then replied- “Station calling…. say again - MH 2133 then repeated “2133 Maam, and are 25 DME maintain 10500, confirm we are number 2?”. TOWER – responded “That’s affirm 2133, Expected Approach Time 0520 hrs”. At 0459:05 hrs MH2133 asked TSE 809 to check position and whether there would be any objection for the aircraft to descend through its level. TSE 809 replied that they had no objection and MH 2133 was subsequently cleared to descend to 7000 feet. The descent into Tawau by MH 2133 from the cruising altitude of 10500 feet was initiated at about 21 DME. The flight crew discussed the descent technique they were going to use and were aware of all their action. At 0501:15 hrs, as the flight reported leaving 9000 feet and passing 16 DME, the flight crew advised the controller that they had the airfield visual. MH2133 was then cleared for visual approach runway 17. At 0502:48 hrs, MH 2133 reported passing 3500 feet. The aircraft was then configured for landing where landing gears were selected down and flaps set at 25 degrees. The aircraft speed was still fast and since it was also high on the approach, the commander assured the co-pilot “Runway is long so no problem Eh”. On passing 2000 feet and on short final, the copilot reminded the commander “speed, speed check, speed check Ah”. The rate of descent was in excess of 3000 feet per minute and its pitch angle was around minus 13 degrees. The excessive rate of descent triggered the aircraft Ground Proximity Warning System (GPWS) sink rate and pull up warnings. The commander ignored these warnings and insisted that he should continue with approach for a landing. The aircraft first touched down on the runway at 0505 hrs. Its first tyre marks (nose wheel) on the runway was at approximately 3400 ft from the threshold. It then bounced and at 4500 ft point, its left main wheel made a light contact with the runway surface. It subsequently bounced up again and its main wheels made a firm contact at 4800 ft point, thus leaving only 800 ft of runway remaining. The aircraft continued onto the grass verge, momentarily left the ground and hopped over the runway perimeter fence. It subsequently crashed at 571 feet from the end of the runway at almost right angle to the runway. There were a number of explosions followed by a fire. The aircraft was totally destroyed.
Probable cause:
The most probable cause of the accident was due to the commander’s insistence to continue with an approach despite the fact that the runway available after touchdown was not sufficient enough for the aircraft to stop. The perception regarding economic consideration which put pressure on him to save fuel and adhere to schedules was a contributing factor.
Final Report:

Crash of a Cessna 208 Caravan in Tawau

Date & Time: Mar 20, 1995 at 1730 LT
Type of aircraft:
Operator:
Registration:
9M-PMN
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tawau - Kota Kinabalu
MSN:
208B-0295
YOM:
1992
Location:
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine aircraft was completing a cargo flight to Kota Kinabalu, carrying two pilots and a load of 400 kilos of fish. After a course of 860 metres on runway 17, the aircraft lifted off and climbed to a height of about 3 metres when it landed back. It continued in a nose-up attitude, overran for 60 metres and came to rest down an embankment into several houses. Both occupants were slightly injured and the aircraft was damaged beyond repair.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Kota Kinabalu: 3 killed

Date & Time: Nov 15, 1991
Operator:
Registration:
9M-PSF
Flight Phase:
Survivors:
No
MSN:
850
YOM:
1986
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Crashed in unknown circumstances at Kota Kinabalu Airport, killing all three crew members.

Crash of a Gulfstream GII near Keningau: 12 killed

Date & Time: Sep 4, 1991 at 1411 LT
Type of aircraft:
Operator:
Registration:
N204C
Survivors:
No
Site:
Schedule:
Tokyo - Kota Kinabalu - Jakarta
MSN:
143
YOM:
1974
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
12
Circumstances:
The aircraft departed Tokyo-Narita Airport on a flight to Jakarta with a fuel stop at Kota Kinabalu Airport, carrying nine passengers and three crew members, among them four corporate members of the Conoco Group that leased the aircraft from DuPont de Nemours. Following an uneventful flight from Tokyo, the crew started the descent to Kota Kinabalu after being cleared to 10,000 then 5,000 feet. ATC instructed the crew to follow a route to the south (180°) and after passing VJN VOR at 4,000 feet, the crew could expect a clearance for an approach to runway 02. While descending to 4,000 feet, the aircraft disappeared from radar screens after it struck the slope of a mountain located in the Crocker Mountain Range, about 9 km northwest of Keningau and 57 km south of Kota Kinabalu Airport. The aircraft was destroyed upon impact and all 12 occupants were killed.
Probable cause:
The accident was the consequence of a series of error and omissions on part of the flying crew, resulting in a controlled flight into terrain.
The following contributing factors were reported:
- The pilots did not slow the aircraft to approach speed when directed by ATC (Event69). This error put the aircraft over VJN VOR/DME approximately 15 minutes earlier than ATC expected. The average ground speed inbound to the VOR/DME, between Event65 (DME 37 nmi) and Event104 (DME 0.0 nmi), was 400 knots.
- The pilots did not descend according to the published descent profile for their arrival sector. If the pilots had done this the aircraft would have been at 4,000 feet altitude over the VJN VOR/DME and in position for the initial approach segment for a VOR/DME approach procedure.
- The CVR recording indicates the pilots did not consider any published approach other than the ILS approach. Nevertheless, the pilots did not specifically request the ILS approach.
- The radiotelephone communication methods used by copilot Johnston were sloppy and not compliant with ICAO standards. Specifically, Johnston indicated to ATC he understood and would comply with the ATC directive to descend over the VJN VOR/DME to 9,500 feet. He did this by repeating (part of) the directive at Event118 suggesting to ATC he understood the directive and would comply.
- The pilots did not ask for clarification on the ATC directive to “descend south of the airfield” and put the aircraft on a heading 180o. The aircraft ground track suggested by Frank Petersen in his deposition and in his report titled “REPORT OF INVESTIGATION INTO THE ACCIDENT INVOLVING N204C” (April 24, 1992) has the aircraft flying outbound from the VJN VOR/DME on the 180° radial. This ground track can not be correct since it would put the aircraft 3 nmi east of the crash site at the time the pilots initiated the right turn. The 3 nmi distance could not have been covered in the 25 seconds between initiating the right turn and the impact. (At 230 knots it would take over 46 seconds to cover this distance.) Furthermore, the aircraft would have crashed before it did into the mountains along the 180° radial from the VJN VOR/DME.
- The cockpit conversation at Event179 indicates both pilots saw high terrain 52 seconds before impact. At this time the aircraft was less than 1 nmi from eye-level hills at 4,000 feet and less than 1.7 nmi from a peak at 4,875 feet. The pilots should have realized they were violating IFR approach procedures. (At this time of day the cloud cover near these hills would have been broken with cloud bases above 4,000 feet.) The pilots made no comment to ATC about the terrain or the cloud conditions.
Source: DuPont GII N204C Crash by Roger K. Parsons - Seagull Publishing, Houston, TX
Final Report:

Crash of a GAF Nomad N.22B off Kota Kinabalu: 11 killed

Date & Time: Jun 6, 1976 at 1541 LT
Type of aircraft:
Operator:
Registration:
9M-ATZ
Flight Type:
Survivors:
No
Schedule:
Labuan - Kota Kinabalu
MSN:
14
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
The airplane was completing a flight from Labuan to Kota Kinabalu, carrying the Prime Minister of Sabah and his delegation. On final approach to runway 20, while at an altitude of 600 feet and a speed of 86 knots, the airplane stalled and crashed into the shallow sea which was about three feet deep, some 3 km short of runway threshold. The aircraft was totally destroyed and all 11 occupants have been killed.
Crew:
Ghandi Nathan.
Passengers:
Tun Fuad Stephens, Prime Minister of Sabah,
Datuk Peter Mojuntin, Sabah Minister of Local Government and Housing,
Datuk Salleh Sulong, Sabah Finance Minister,
Chong Thien Vun, Sabah Works and Communication Minister,
Datuk Darius Binion, Assistant Minister to Deputy Chief Minister,
Datuk Wahid Peter Andu, secretary to Sabah Finance Minister,
Dr. Syed Hussin Wafa, Director of State Economic Planning Unit,
Datuk Ishak Atan, Private Secretary to Malaysian Federal Finance Minister Tengku Razaleigh Hamzah,
Johari Stephens (Tun Fuad's eldest son),
Corporal Said Mohammad, bodyguard to Tun Fuad Stephens.
Probable cause:
The findings of an investigating team did not reveal any technical errors or sabotage as being the causes of the air crash. What they have instead discovered is that the fault was due to human error. It was also revealed that the aircraft's storage space at the back of the aircraft, was loaded with goods above the maximum load. As a consequence this had resulted in the aircraft losing control when it attempted to land at the Kota Kinabalu Airport, thus resulting in the accident.

Crash of a Beechcraft 65-B80 Queen Air in Sandakan: 3 killed

Date & Time: Nov 30, 1974
Type of aircraft:
Operator:
Registration:
9M-ASU
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Sandakan - Sandakan
MSN:
LD-473
YOM:
1974
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Shortly after takeoff from Sandakan Airport, while completing a local training flight, the twin engine airplane went out of control and crashed in a swampy area. All three pilots were killed.

Crash of a Fokker F27 Friendship 500 in Kota Kinabalu

Date & Time: Nov 23, 1971
Type of aircraft:
Operator:
Registration:
9V-BCU
Flight Type:
Survivors:
Yes
Schedule:
Kota Kinabalu - Kota Kinabalu
MSN:
10463
YOM:
1971
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
669
Aircraft flight cycles:
879
Circumstances:
The crew was engaged in a local training flight at Kota Kinabalu Airport. Following several touch-and-go manoeuvres, the pilot under supervision started a new takeoff procedure when the instructor decided to simulate an engine failure and reduced the power on the right engine. The pilot-in-command reduced power on the left engine and started an emergency braking procedure. Unable to stop within the remaining distance, the airplane overran, struck various obstacles, lost its undercarriage and came to rest. While both pilots were uninjured, the aircraft was damaged beyond repair.

Crash of a De Havilland DHC-4A Caribou into the Cowie Bay: 10 killed

Date & Time: Mar 30, 1970 at 0850 LT
Type of aircraft:
Operator:
Registration:
M21-10
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
278
YOM:
1969
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
Crashed in unknown circumstances into the Cowie Bay. Ten passengers were killed while nine other occupants were rescued.

Crash of a De Havilland DHC-4A Caribou in Meligan: 1 killed

Date & Time: Jan 12, 1967
Type of aircraft:
Operator:
Registration:
M21-02
Flight Type:
Survivors:
Yes
Schedule:
Labuan - Meligan
MSN:
246
YOM:
1966
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
While on a supply mission from Labuan, the airplane crashed while approaching Meligan Airstrip and came to rest 2 km short of runway. The copilot was killed while eight others occupants were injured.