Crash of a Pilatus PC-12/47 in Kamphaeng Saen: 1 killed

Date & Time: Mar 5, 2017 at 1916 LT
Type of aircraft:
Operator:
Registration:
VT-AVG
Flight Type:
Survivors:
Yes
Schedule:
New Delhi – Calcutta – Bangkok
MSN:
888
YOM:
2008
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The single engine aircraft departed New Delhi at 0842LT on an ambulance flight to Bangkok with two pilots and three doctors on board. A refueling stop was completed at Calcutta Airport. At 1903LT, en route to Bangkok-Don Mueang Airport, the crew contacted ATC and requested permission to divert to Kamphaeng Saen Airport due to an emergency. The permission was granted and the crew initiated the descent when the aircraft disappeared from radar screens at 1916LT. The burned wreckage was found an hour and 30 minutes later, at 2048LT, in a wooded area located few km from runway 22L threshold. All five occupants were injured while the aircraft was destroyed. Few hours later, the copilot died from his injuries.

Crash of an ATR72-500 in Dhaka

Date & Time: Apr 30, 2012 at 0851 LT
Type of aircraft:
Operator:
Registration:
60314
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Dhaka
MSN:
881
YOM:
2009
Flight number:
KAT304
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Dhaka-Hazrat Shahjalal Airport, the twin engine aircraft deviated to the right and veered off runway. It collided with an embankment, lost its undercarriage and came to rest against a concrete wall. All 15 occupants were rescued, among them two passengers were slightly injured.

Crash of a McDonnell Douglas MD-82 in Phuket: 90 killed

Date & Time: Sep 16, 2007 at 1540 LT
Type of aircraft:
Operator:
Registration:
HS-OMG
Survivors:
Yes
Schedule:
Bangkok - Phuket
MSN:
49183/1129
YOM:
1983
Flight number:
OG269
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
123
Pax fatalities:
Other fatalities:
Total fatalities:
90
Captain / Total flying hours:
16752
Captain / Total hours on type:
4330.00
Copilot / Total flying hours:
1465
Copilot / Total hours on type:
1240
Aircraft flight hours:
65965
Aircraft flight cycles:
35498
Circumstances:
On 16 September 2007 at approximately 14:30 hours, One Two Go Airlines' McDonnell-Douglas MD-82 airplane with nationality and registration mark HS-OMG, departed on a scheduled passenger flight number OG269 from Don Mueang International Airport for Phuket International Airport with 123 passengers and 7 crew members on board. The Pilot-in-Command (PlC) seated on the left was a Pilot not Flying (PNF) / Pilot Monitoring and the Co-pilot seated on the right was a Pilot Flying (PF). The flight was en route on airways G458 at Flight Level (FL) 320 (32,000 feet) and the estimated time of arrival at Phuket International Airport was 15:50 hours. At 15:36:21, during the time that flight OG269 was approaching the Phuket International Airport, the Orient Thai Airlines flight OX2071, while vacating from Runway 27 after landed at the Phuket International Airport, reported the Air Traffic Controller (ATC) of the weather condition prior to landing that Cumulonimbus (CB) was over the airport area and there was windshear at 5 nautical miles before reaching the Instrument Landing System (ILS) station, resulted in airspeed gain and loss of 15 knots. The ATC asked flight OG269 whether they acknowledged the weather conditions reported by flight OX2071, because both flights were on the same aerodrome radio frequency (118.1 MHz). The PlC of flight OG269 acknowledged the information and extended the landing gears for landing. At 15:37:31, the ATC informed flight OG269 of surface winds from 240 degrees at 15 knots and gave clearance to land on Runway 27 with-wet runway precaution. At 15:38:27, the ATC informed flight OG269 of surface winds from 240 degrees at 30 knots and asked the flight OG269 to state its intention of landing. The flight OG269 affirmed. At 15:39:00, the flight OG269 requested for information of surface wind condition. The ATC informed a surface wind condition of 240 degrees at 40 knots and the flight OG269 acknowledged. At that instant, the Radio Altitude Aural Call-Out system automatically called out '500 feet' and the PlC called out that the airspeed was at 136 knots. At 15:39:23, the PlC ordered for more engine power and reminded the copilot that the airplane was descending below the ILS glide path. The copilot affirmed the correction. The PIC then ordered to increase engine power three more times. During that time, the airplane was at the altitude of 100 feet. At 15:39:45, the Radio Altitude Aural Call-Out system automatically called out '40 feet' and the Enhanced Ground Proximity Warning System (EGPWS) called out 'sink rate - sink rate' . At 15:39:49, the copilot called out for a go-around and the PIC said 'Okay, Go Around'. At 15.39.50, the copilot called for 'flaps 15' and transferred the airplane control to the PIC. Then, the PIC told the copilot to set the autopilot airplane heading and to retract the landing gear. At 15 :40: 11, the airplane veered off and hit an embankment located in the North of Runway 27 and broke up in flames. 40 people were rescued while 90 others were killed, among them five crew members.
Probable cause:
After thorough investigation, the AAIC determined that the probable causes of accident are as follows:
1. the flight crew did not follow the Standard Operating Procedure (SOP) of Stabilized Approach, Call Out, Go Around, and Emergency Situation as specified in the Airlines’ Flight Operation Manual (FOM).
2. the Take Off/ Go Around (TO/GA) switch was not pressed, resulting in the failure of increasing in airspeed and altitude during the go around. Also, there was no monitoring of the change in engine power and movement of throttle levers, especially during the emergency situation.
3. the flight crew coordination was insufficient and the flight crew had heavy workloads.
4. the weather condition changed suddenly over the airport vicinity.
5. the flight crew had accumulated stress, insufficient rest, and fatigue.
6. the transfer of aircraft control took place at a critical moment, during the go around.
Final Report:

Crash of a NAMC YS-11-500R in Mae Sot

Date & Time: Sep 11, 2005 at 0900 LT
Type of aircraft:
Operator:
Registration:
HS-KVO
Survivors:
Yes
Schedule:
Bangkok – Mae Sot
MSN:
2116
YOM:
1969
Flight number:
VAP326
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
24
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach and landing at Mae Sot Airport were completed in rainy conditions. After touchdown, the aircraft was unable to stop within the remaining distance, collided with a fence and came to rest. All 28 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
On final approach, the aircraft was too high and landed too far down the runway at an excessive speed. The runway surface was wet and the braking action was poor.

Crash of an Avro 748-208-2A in Bangkok

Date & Time: Nov 22, 2004
Type of aircraft:
Operator:
Registration:
99-999
Flight Type:
Survivors:
Yes
MSN:
1715
YOM:
1972
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing, the nose gear collapsed. The aircraft slid for few dozen metres before coming to rest. All occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the nose gear on landing for unknown reasons.

Crash of a Piper PA-46-350P Malibu Mirage near Lop Buri: 3 killed

Date & Time: Apr 26, 2003 at 1430 LT
Operator:
Registration:
HS-AKS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bangkok – Chiang Mai
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The single engine aircraft departed Bangkok-Don Mueang on a private flight to Chiang Mai with two passengers and one pilot on board. During climbout in marginal weather conditions, the pilot was cleared to climb to 11,000 feet when control was lost. The aircraft crashed in a cornfield located near Lop Buri. All three occupants were killed. There was some thunderstorm activity in the area at the time of the accident.

Ground explosion of a Boeing 737-4D7 in Bangkok: 1 killed

Date & Time: Mar 3, 2001 at 1448 LT
Type of aircraft:
Operator:
Registration:
HS-TDC
Flight Phase:
Survivors:
Yes
Schedule:
Bangkok – Chiang Mai
MSN:
25321
YOM:
1991
Flight number:
TG114
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
While parked at gate 62 at Bangkok-Don Mueang Airport, the aircraft suffered an explosion and caught fire. On board were eight crew members awaiting 148 passengers to embark, among them Thaksin Shinawatra, Thai Prime Minister. Seven crew members were able to evacuate the cabin while the eighth crew member died. The aircraft was completely destroyed by fire. It was reported that the first explosion occurred in the center fuel tank, about 27 minutes prior to the expected takeoff time, followed by a second explosion in the right wing tank 18 minutes later.
Probable cause:
An explosion of the center wing tank resulting from ignition of the flammable fuel/air mixture in the tank. The source of the ignition energy for the explosion could not be determined with certainty, but the most likely source was an explosion originating at the center wing tank pump as a result of running the pump in the presence of metal shavings and a fuel/air mixture.

Crash of an Antonov AN-12BP in Colombo: 9 killed

Date & Time: Mar 24, 2000 at 1804 LT
Type of aircraft:
Operator:
Registration:
RA-11302
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Colombo
MSN:
8 3 460 04
YOM:
1968
Flight number:
SCB702
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
9
Captain / Total flying hours:
6719
Captain / Total hours on type:
961.00
Copilot / Total flying hours:
10802
Copilot / Total hours on type:
1702
Aircraft flight hours:
7241
Aircraft flight cycles:
4651
Circumstances:
The Sky Cabs flight SCB701 originated in Colombo (Bandaranaike International Airport Colombo - hereinafter known as BIA Colombo), Sri Lanka at 1940 hours on 23rd March 2000. It landed in Bangkok, Thailand at 0120 hours on the following day after an uneventful flight. The alternate airport for Bangkok was Rayong/Ban U-Taphao (VTBU). The crew had recent experience in operating AN 12 flights between BIA Colombo and Bangkok International Airport, Thailand. The same flight crew made the return flight back to BIA Colombo after 4 hours and 20 minutes ground time in Bangkok. The crew had received the weather report from Aero Meteorological Division (AMD), prior to departure. An air traffic control flight plan was filed to BIA Colombo, the filed alternate airport was Male International (VRMM) in the Republic of Maldives. The aircraft was refueled adding 6681 kgs of fuel to the remaining 8300 kgs bringing the total fuel onboard to 14981 kg. Flight SCB702, cargo flight, departed Bangkok at 0540 hours on 24th March 2000 to BIA Colombo. The scheduled flight time for Bangkok – BIA Colombo was five hours and twenty minutes with a scheduled time of arrival of 1100 hours (17:00 hours Sri Lanka time). SCB702 made the first radio contact with Sri Lanka air traffic control at 1016 hours. The area controller passed SCB702 the latest weather report effective for BIA Colombo and later, a Sigmet valid at the time. When the control of the flight was handed to the approach radar controller (Director) by the area controller, at 1042 hours SCB 702 was asked to report his radial and DME from Colombo, (i.e. from “DVOR/DME KAT”). SCB702 reported as saying “074 radial and 55 DME ready for descent”, thus the two-way communication was established. Later, the flight SCB702 made two unsuccessful ILS approaches to runway 04. While on a radar heading to get established on the ILS to Runway 22 for a third attempt to land, the aircraft crashed 1.2 N.M. north-northwest of the threshold of Runway 22 (3.2 N.M. north-northeast of the DVOR/DME 'KAT') at BIA Colombo at 1204 hours (or 1804 hours in the evening, local time) on 24th March 2000. Six crew members and three people on the ground were killed.
Probable cause:
The aircraft accident occurred due to fuel starvation. Contributory factors to the accident are as follows:
i) Violation of Air Navigation Regulations on fuel planning;
ii) Failure of the flight crew to declare an emergency;
iii) Being unable to land due to adverse weather situation;
iv) Lack of communicability of the flight crew in English language;
v) Non-availability of established air traffic control procedures to assist an aircraft in distress;
vi) Failure of Sky Cabs (Pvt.) Ltd. to comply with the Air Navigation Regulations and the Conditions set-forth in Schedules issued with the Airline Lisence; and
vii) Absence of an effective Safety Oversight Program implemented by the Department of Civil Aviation, Sri Lanka.
Final Report:

Crash of a McDonnell Douglas MD-11 in Hong Kong: 3 killed

Date & Time: Aug 22, 1999 at 1843 LT
Type of aircraft:
Operator:
Registration:
B-150
Survivors:
Yes
Schedule:
Bangkok - Hong Kong - Taipei
MSN:
48468
YOM:
1992
Flight number:
CI642
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
300
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
17900
Captain / Total hours on type:
3260.00
Copilot / Total flying hours:
4630
Copilot / Total hours on type:
2780
Aircraft flight hours:
30700
Aircraft flight cycles:
5800
Circumstances:
China Airline’s flight CI642 was scheduled to operate from Bangkok to Taipei with an intermediate stop in Hong Kong. The crew had carried out the sector from Taipei to Bangkok, passing through Hong Kong on the previous day. On that flight, the crew were aware of the Severe Tropical Storm (STS) ‘Sam’ approaching Hong Kong and the possibility that it would be in the vicinity of Hong Kong at about the scheduled time of arrival on the following evening. Weather information provided at the preflight briefing for the return flight indicated the continuing presence of STS ‘Sam’ with its associated strong winds and heavy precipitation. The flight departed from Bangkok on schedule with 300 passengers and 15 crew on board, with an estimated time of arrival (ETA) of 1038 hour (hr) in Hong Kong. The commander had elected to carry sufficient fuel to permit a variety of options on arrival – to hold, to make an approach, or to divert. If an immediate approach was attempted, the aircraft would be close to its Maximum Landing Weight (MLW) involving, in consequence, a relatively high speed for the approach and landing. Throughout the initial stages of the flight and during the cruise, the commander was aware of the crosswind component to be expected in Hong Kong and reviewed the values of wind direction and speed which would bring it within the company’s crosswind limit as applicable to wet runways of 24 kt. In the latter stage of the cruise, the crew obtained information ‘Whisky’ from the Automatic Terminal Information Service (ATIS) timed at 0940 hr, which gave a mean surface wind of 320 degrees (º) / 30 knots (kt) maximum 45 kt in heavy rain, and a warning to expect significant windshear and severe turbulence on the approach. Although this gave a crosswind component of 26 kt which was in excess of the company’s wet runway limit of 24 kt, the commander was monitoring the gradual change in wind direction as the storm progressed, which indicated that the wind direction would possibly shift sufficiently to reduce the component and thus permit a landing. Hong Kong Area Radar Control issued a descent clearance to the aircraft at 1014 hr and, following receipt of ATIS information ‘X-ray’ one minute later, which included a mean surface wind of 300º at 35 kt, descent was commenced at 1017 hr. Copies of the information sheets used by Air Traffic Control (ATC) as the basis for ATIS broadcasts ‘Whisky’ and ‘X-ray’ are at Appendix 1. The approach briefing was initiated by the commander just after commencing descent. The briefing was given for an Instrument Landing System (ILS) approach to Runway 25 Right (RW 25R) at HKIA. However, the active runway, as confirmed by the ATIS was RW 25L. Despite the inclusion in the ATIS broadcasts of severe turbulence and possible windshear warnings, no mention was made in the briefing of the commander’s intentions relating to these weather phenomena nor for any course of action in the event that a landing could not be made, other than a cursory reference to the published missed approach procedure. The descent otherwise continued uneventfully and a routine handover was made at 1025 hr to Hong Kong Approach Control which instituted radar vectoring for an ILS approach to what the crew still believed was RW 25R. At 1036 hr, after having been vectored through the RW 25L localizer for spacing, CI642 was given a heading of 230º to intercept the localizer from the right and cleared for ILS to RW 25L. The co-pilot acknowledged the clearance for ILS 25L but queried the RVR (runway visual ranges); these were passed by the controller, the lowest being 1300 m at the touchdown point. The commander then quickly re-briefed the minimums and go-around procedure for RW 25L. At 1038 hr, about 14 nautical miles (nm) to touchdown, the aircraft was transferred to Hong Kong Tower and told to continue the approach. At 1041 hr, the crew were given a visibility at touchdown of 1600 metres (m) and touchdown wind of 320º at 25 kt gusting 33 kt, and cleared to land. The crew of flight CI642 followed China Airline’s standard procedures during the approach. Using the autoflight modes of the aircraft, involving full use of autopilot and autothrottle systems, the flight progressed along the ILS approach until 700 ft where the crew became visual with the runway and approach lights of RW 25L. Shortly after this point the commander disconnected the autopilot and flew the aircraft manually, leaving the autothrottle system engaged to control the aircraft’s speed. After autopilot disconnect, the aircraft continued to track the runway centreline but descended and stabilized slightly low (one dot) on the glideslope. Despite the gustiness of the wind, the flight continued relatively normally for the conditions until approximately 250 ft above the ground at which point the co-pilot noticed a significant decrease in indicated airspeed. Thrust was applied as the co-pilot called ‘Speed’ and, as a consequence, the indicated airspeed rose to a peak of 175 kt. In response to this speed in excess of the target approach speed, thrust was reduced and, in the process of accomplishing this, the aircraft passed the point (50 ft RA) at which the autothrottle system commands the thrust to idle for landing. Coincidentally with this, the speed decreased from 175 kt and the rate of descent began to increase in excess of the previous 750-800 feet per minute (fpm). Although an attempt was made to flare the aircraft, the high rate of descent was not arrested, resulting in an extremely hard impact with the runway in a slightly right wing down attitude (less than 4º), prior to the normal touchdown zone. The right mainwheels contacted the runway first, followed by the underside of the right engine cowling. The right main landing gear collapsed outward, causing damage to the right wing assembly, resulting in its failure. As the right wing separated, spilled fuel was ignited and the aircraft rolled inverted and came to rest upside-down alongside the runway facing in the direction of the approach. The cockpit crew were disorientated by the inverted position of the aircraft and found difficulty in locating the engine controls to carry out engine shut down drills. After extricating themselves, they went through the cockpit door into the cabin and exited the aircraft through L1 door and began helping passengers from the aircraft through a hole in the fuselage. Airport fire and rescue services were quickly on the scene, extinguishing the fuel fire and evacuating the passengers through the available aircraft exits and ruptures in the fuselage. As a result of the accident, two passengers were found dead on arrival at hospital, and six crew members and 45 passengers were seriously injured. One of the seriously injured passengers died five days later in hospital.
Probable cause:
The cause of the accident was the commander’s inability to arrest the high rate of descent existing at 50 feet RA. Probable contributory causes to the high rate of descent were:
- The commander’s failure to appreciate the combination of a reducing airspeed, increasing rate of descent, and with the thrust decreasing to flight idle.
- The commander’s failure to apply power to counteract the high rate of descent prior to touchdown.
- Probable variations in wind direction and speed below 50 feet RA may have resulted in a momentary loss of headwind component and, in combination with the early retardation of the thrust levers, and at a weight only just below the maximum landing weight, led to a 20 kt loss in indicated airspeed just prior to touchdown. A possible contributory cause may have been a reduction in peripheral vision as the aircraft entered the area of the landing flare, resulting in the commander not appreciating the high rate of descent prior to touchdown.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 600) in Tambon Tha Chalab: 2 killed

Date & Time: May 3, 1999 at 2230 LT
Operator:
Registration:
N602PK
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Calcutta – Bangkok
MSN:
60-8365-016
YOM:
1983
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On May 3, 1999, at an unknown time before 2300 Bangkok, Thailand, local time, a Piper PA-60-602P, N602PK, crashed on an air rally flight between Calcutta, India, and Bangkok. The German national pilot was confirmed to have been fatally injured, and his German national passenger was reported missing at the accident scene. The crash site was at the Srinakarin Reservoir, Tambon Tha Chalab, Srisawat district in Kanchanaburi province, west of Bangkok. The airplane was reported to have been due to land at Bangkok's Don Muang airport at 2300 local time on May 3. Adverse weather was reported in the vicinity at the time of the accident. There was no report of an ELT actuation.