Crash of a Fokker 100 in Heho: 2 killed

Date & Time: Dec 25, 2012 at 0853 LT
Type of aircraft:
Operator:
Registration:
XY-AGC
Survivors:
Yes
Schedule:
Mandalay - Heho
MSN:
11327
YOM:
1991
Flight number:
JAB011
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
65
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5937
Captain / Total hours on type:
2547.00
Copilot / Total flying hours:
849
Copilot / Total hours on type:
486
Aircraft flight hours:
27378
Aircraft flight cycles:
32584
Circumstances:
On 25 December 2012 at 0603 local Time, an Air Bagan Ltd Fokker 100 aircraft registered XY-AGC (MSN-11327) departed Yangon International Airport (VYYY) on a scheduled passenger flight to Mandalay International Airport (VYMD) with the Pilot in command (PIC) as pilot flying. The aircraft was refueled after 60 passengers disembarked and 46 passengers boarded. The PIC made briefing and completed the aircraft checks. At 0826 local time, departed Mandalay International Airport (VYMD) to Heho Airport (VYHH). On Board the pilot in command (PIC), first officer (FO), 4 cabin crews and 65 passengers (Total 71 POB) and the First Officer was designated as the Pilot Flying for the flight. The aircraft climbed to FL. 130 and cruised with an indicated airspeed of 250 Kts. The Pilot in command contacted Heho ATC at flight level 130 and 50 NM to Heho. Heho ATC provided the present weather condition (wind calm, visibility 3000M, Distinct fog, Temperature 17. C, QNH 1018 mb, RW 36). At about 0836 local time, the first officer started crew briefing and called out "Radio Altimeter" alive . The aircraft started descend to 9000ft and continued overhead Heho NDB. At about 0847 local time, while heading 220 degrees and descending to 6000ft and commenced a non-precision Non Directional Beacon (NDB) approach to runway 36. During the final inbound track at about 2.5 NM to the runway at 08:52:349, the EGPWS aural warning called out "500". The Pilot in command initiated "Alt hold" at about 0853, just before the EGPWS alert "100" "50" 40" "30" and the aircraft struck 66 KV power lines, trees, telephone cables, fence and collided with terrain short of the runway, coming to rest approximately 0.7 NM from the threshold. During the ground collision, both wings separated and a fire commenced almost immediately. An emergency evacuation was initiated by the cabin crews. One aircraft occupant and one motorcyclist on the ground were fatally injured, 70 of the occupants and one motorcyclist survived and the aircraft was destroyed by fire.
Probable cause:
Primary Cause:
- During the final approach, the aircraft descended below the MDA and the crew did not follow the operator SOP's.
- The pilots had no corrective action against to change VMC to IMC during bad weather condition and insufficient time for effective respond to last moment.
Secondary Cause:
- Captain of the aircraft had insufficient assessment on the risk that assigned the FO as PF.
- There may be under pressure by the following aircrafts as the first plane on that day to Heho.
Final Report:

Crash of a Swearingen SA227AC Metro III in Sanikiluaq: 1 killed

Date & Time: Dec 22, 2012 at 1806 LT
Type of aircraft:
Operator:
Registration:
C-GFWX
Survivors:
Yes
Schedule:
Winnipeg - Sanikiluaq
MSN:
AC-650B
YOM:
1986
Flight number:
PAG993
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5700
Captain / Total hours on type:
2330.00
Copilot / Total flying hours:
1250
Copilot / Total hours on type:
950
Aircraft flight hours:
32982
Circumstances:
On 22 December 2012, the Perimeter Aviation LP, Fairchild SA227-AC Metro III (registration C-GFWX, serial number AC650B), operating as Perimeter flight PAG993, departed Winnipeg/James Armstrong Richardson International Airport, Manitoba, at 1939 Coordinated Universal Time (1339 Central Standard Time) as a charter flight to Sanikiluaq, Nunavut. Following an attempted visual approach to Runway 09, a non precision non-directional beacon (NDB) Runway 27 approach was conducted. Visual contact with the runway environment was made and a circling for Runway 09 initiated. Visual contact with the Runway 09 environment was lost and a return to the Sanikiluaq NDB was executed. A second NDB Runway 27 approach was conducted with the intent to land on Runway 27. Visual contact with the runway environment was made after passing the missed approach point. Following a steep descent, a rejected landing was initiated at 20 to 50 feet above the runway; the aircraft struck the ground approximately 525 feet beyond the departure end of Runway 27. The 406 MHz emergency locator transmitter activated on impact. The 2 flight crew and 1 passenger sustained serious injuries, 5 passengers sustained minor injuries, and 1 infant was fatally injured. Occupants exited the aircraft via the forward right overwing exit and were immediately transported to the local health centre. The aircraft was destroyed. The occurrence took place during the hours of darkness at 2306 Coordinated Universal Time (1806 Eastern Standard Time).
Probable cause:
Findings as to causes and contributing factors:
1. The lack of required flight documents, such as instrument approach charts, compromised thoroughness and placed pressure on the captain to find a workaround solution during flight planning. It also negatively affected the crew’s situational awareness during the approaches at CYSK (Sanikiluaq).
2. Weather conditions below published landing minima for the approach at the alternate airport CYGW (Kuujjuarapik) and insufficient fuel to make CYGL (La Grande Rivière) eliminated any favourable diversion options. The possibility of a successful landing at CYGW was considered unlikely and put pressure on the crew to land at CYSK (Sanikiluaq).
3. Frustration, fatigue, and an increase in workload and stress during the instrument approaches resulted in crew attentional narrowing and a shift away from welllearned, highly practised procedures.
4. Due to the lack of an instrument approach for the into-wind runway and the unsuccessful attempts at circling, the crew chose the option of landing with a tailwind, resulting in a steep, unstable approach.
5. The final descent was initiated beyond the missed approach point and, combined with the 14-knot tailwind, resulted in the aircraft remaining above the desired 3- degree descent path.
6. Neither pilot heard the ground proximity warning system warnings; both were focused on landing the aircraft to the exclusion of other indicators that warranted alternative action.
7. During the final approach, the aircraft was unstable in several parameters. This instability contributed to the aircraft being half-way down the runway with excessive speed and altitude.
8. The aircraft was not in a position to land and stop within the confines of the runway, and a go-around was initiated from a low-energy landing regime.
9. The captain possibly eased off on the control column in the climb due to the low airspeed. This, in combination with the configuration change at a critical phase of flight, as called for in the company procedures, may have contributed to the aircraft’s poor climb performance.
10. A rate of climb sufficient to ensure clearance from obstacles was not established, and the aircraft collided with terrain.
11. The infant passenger was not restrained in a child restraint system, nor was one required by regulations. The infant was ejected from the mother’s arms during the impact sequence, and contact with the interior surfaces of the aircraft contributed to the fatal injuries.
Findings as to risk:
1. If instrument approaches are conducted without reference to an approach chart, there is a risk of weakened situational awareness and of error in following required procedures, possibly resulting in the loss of obstacle clearance and an accident.
2. If additional contingency fuel is not accounted for in the aircraft weight, there is a risk that the aircraft may not be operated in accordance with its certificate of airworthiness or may not meet the certified performance criteria.
3. If Transport Canada crew resource management (CRM) training requirements do not reflect advances in CRM training, such as threat and error management and assertiveness training, there is an increased risk that crews will not effectively employ CRM to assess conditions and make appropriate decisions in critical situations.
4. If a person assisting another is seated next to an emergency exit, there is an increased risk that the use of the exit will be hindered during an evacuation.
5. If a person holding an infant is seated in a row with no seatback in front of them, there is an increased risk of injury to the infant as no recommended brace position is available.
6. If young children are not adequately restrained, there is a risk that injuries sustained will be more severe.
7. If a lap-held infant is ejected from its guardian’s arms, there is an increased risk the infant may be injured, or cause injury or death to other occupants.
8. If more complete data on the number of infants and children travelling by air are not available, there is a risk that their exposure to injury or death in the event of turbulence or a survivable accident will not be adequately assessed and mitigated.
9. If temperature corrections are not applied to all altitudes on the approach chart, there is an increased risk of controlled flight into terrain due to a reduction of obstacle clearance.
10. If the missed approach point on non-precision instrument approaches is located beyond the 3-degree descent path, there is an increased risk that a landing attempt will result in a steep, unstable descent, and possible approach-and-landing accident.
11. If there is not sufficient guidance in the standard operating procedures, there is a risk that crews will not react and perform the required actions in the event that ground proximity warning system warnings are generated.
12. If standard operating procedures, the Airplane Flight Manual and training are not aligned with respect to low-energy go-arounds, there is a risk that crews may perform inappropriate actions at a critical phase of flight.
13. If non-compliant practices are not identified, reported, and dealt with by a company’s safety management system, there is a risk that they will not be addressed in a timely manner.
14. If Transport Canada’s oversight is dependent on the effectiveness of a company’s safety management system’s reporting of safety issues, there is a risk that important issues will be missed.
Other findings:
1. The quick response of the people on the ground reduced the exposure of passengers and crew to the elements.
Final Report:

Crash of an Embraer EMB-120ER Brasília off Moroni

Date & Time: Nov 27, 2012 at 1329 LT
Type of aircraft:
Operator:
Registration:
D6-HUA
Flight Phase:
Survivors:
Yes
Schedule:
Moroni - Ouani
MSN:
120-149
YOM:
1989
Flight number:
INZ170
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
25
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
5000
Circumstances:
The aircraft was on its way from Moroni-Hahaya-Iconi-Prince Saïd Ibrahim Airport to the Ouani Airport located on the neighboring island of Anjouan. Shortly after take off from runway 20, while in initial climb, the captain informed ATC about technical problem and elected to return. He realized he could not make it so he attempted to ditch the aircraft some 200 metres off shore, about 5 km from the airport. All 29 occupants were rescued, among them five were slightly injured.

Crash of an Antonov AN-26B-100 in Deputatsky

Date & Time: Nov 21, 2012 at 1431 LT
Type of aircraft:
Operator:
Registration:
RA-26061
Survivors:
Yes
Schedule:
Yakutsk - Deputatsky
MSN:
111 08
YOM:
1981
Flight number:
PI227
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
23
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8845
Captain / Total hours on type:
1150.00
Copilot / Total flying hours:
2566
Copilot / Total hours on type:
245
Aircraft flight hours:
22698
Aircraft flight cycles:
11257
Circumstances:
Following an uneventful flight from Yakutsk-Magan Airport, crew started the descent to runway 10. On touch down on a snow covered runway, aircraft landed slightly to the left of the centerline. After a course of 350 meters, left main gear hit a snow berm of 20-50 cm high. Aircraft continued to the left, veered off runway and came to rest in snow covered field with its right main gear and right wing severely damaged. All 29 occupants were evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
The non-fatal accident with An-26B RA-26061 aircraft was caused by its RWY overrun that resulted in aircraft structure damage. The accident was possible due to combination of the following factors:
- Pilot's error resulted in approach procedure correction up to the moment of landing resulted in offset approach towards unpaved RWY axis and considerably to the left from its axis;
- Non-compliance of unpaved RWY of "Deputatsky" Airport" condition with Civil aerodrome operation manual requirements RF-94, in part of interface between cleaned and uncleaned surface of unpaved RWY with slope no more than 1:10;
- Nose-left moment during main landing gear movement along interface from recent snow up to 30-50 cm as a result of both left landing gear wheels dipping into snow.
Final Report:

Crash of a Let L-410UVP in Butembo

Date & Time: Oct 30, 2012 at 1500 LT
Type of aircraft:
Operator:
Registration:
9Q-CAZ
Survivors:
Yes
Schedule:
Goma - Butembo
MSN:
79 02 05
YOM:
1979
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Goma, the twin engine airplane landed on runway 14/32 which is 770 metres long. After touchdown, the aircraft was unable to stop within the remaining distance. It overran, lost its left main gear and came to rest down an embankment with its left wing damaged. All 18 occupants escaped uninjured while the aircraft was damaged beyond repair.

Ground fire of a Boeing 737-8KN in Antalya

Date & Time: Oct 14, 2012 at 0400 LT
Type of aircraft:
Operator:
Registration:
TC-TJK
Flight Phase:
Survivors:
Yes
Schedule:
Antalya - Trondheim
MSN:
35794/2794
YOM:
2009
Flight number:
CAI773
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
189
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the push back process, the pilots noticed smoke spreading in the cockpit and in the cabin and stopped the aircraft. All 196 occupants were evacuated but some were standing on wings and jumped down to the tarmac. 27 passengers were injured, some of them seriously. The aircraft was considered as damaged beyond repair due to smoke.
Probable cause:
It is believed that a short circuit occurred in the cockpit panel, on the captain side, most probably in the vicinity of the oxygen system.

Crash of a Britten-Norman BN-2A-26 Islander in Saint John's: 3 killed

Date & Time: Oct 7, 2012 at 1610 LT
Type of aircraft:
Operator:
Registration:
VP-MON
Flight Phase:
Survivors:
Yes
Schedule:
Saint John’s – Montserrat
MSN:
82
YOM:
1969
Flight number:
MNT107
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
710
Captain / Total hours on type:
510.00
Aircraft flight hours:
22064
Aircraft flight cycles:
55851
Circumstances:
The aircraft was operating a VFR scheduled commercial air transport flight from VC Bird International Airport, Antigua (TAPA), to John A Osborne Airport, Montserrat (TRPG). The accident occurred during the aircraft’s fourth sector of the day. Prior to the accident flight, another pilot had flown two sectors in it, from John A Osborne to VC Bird and return, before going off duty. The accident pilot reported for duty at 1130 hrs, completed pre-flight preparations, and operated the aircraft to VC Bird. After the aircraft’s arrival at VC Bird, the airport closed to VFR traffic because of cumulonimbus activity and heavy rain. The airport re-opened for VFR operations shortly before the aircraft’s departure. A cumulonimbus cloud was present on the approach to Runway 07, and although the surface wind was westerly, Runway 07 was in use for departures. On board the aircraft were the pilot, three passengers, and bags weighing 150 lb. The fuel load on departure was 65 USG of AVGAS. The takeoff mass was shown on the load sheet as 5,540 lb, which was below the structural maximum takeoff weight of 6,600 lb; the performance-regulated takeoff weight at the ambient temperature of 24 °C was greater than the structural limit. The passengers and pilot travelled in a bus from the airport terminal to the aircraft. The passengers boarded the aircraft, and the baggage was loaded into the compartment behind the rear-most seats. The pilot then boarded the aircraft. The pilot was not observed to carry out a drain of the fuel system’s water traps (the operations manual did not stipulate that a drain check should be carried out). The pilot called the VC Bird Ground Movement Control (GMC) controller for permission to start engines, and was instructed to wait while the controller contacted Montserrat ATC to enquire about the weather there. The pilot then asked for surface wind information for VC Bird and was informed it was from 240° at 10 kts. The controller gave permission for start and passed the Montserrat weather, which was suitable for the operation. The pilot was instructed to taxi to holding position Bravo. The pilot contacted the Tower controller and was instructed to enter, backtrack, and line up on Runway 07. The controller described the weather observed from the Tower to the pilot, and the pilot requested a left-hand turn-out after departure. The surface wind was transmitted as from 270° at 10 kts and the aircraft was cleared for takeoff. The aircraft entered the runway at Bravo but did not backtrack. No power checks were carried out (other evidence indicated that power checks were routinely not carried out other than on each pilot’s first flight of the day). The aircraft took off, and the early part of the climb appeared normal. Analysis of the eye witness reports, and consideration of their locations and fields of view, led to a deduction that this normal climb continued to a height of between 200 and 300 ft above the ground. The aircraft then appeared to ‘sink’, losing a small amount of height without yawing or rolling, before yawing to the right, then rolling to the right, and pitching nose down into an incipient spin to the right. The surviving passenger recalled that the stall warning sounded, and its accompanying red light (which was mounted on the right-hand side of the instrument panel and in his line of sight) illuminated throughout this period and until impact. Witnesses described that the (incipient) spin continued until the aircraft struck the ground. ATC staff in the visual control room activated the airport’s crash alarm. The rescue and fire-fighting service (RFFS) responded promptly from their station; the crew of one RFFS vehicle, working on the airport, observed the accident and responded directly to it. The pilot and one passenger were fatally injured on impact. Another passenger succumbed to her injuries before she could be extricated from the wreckage, and the third passenger, who had sustained serious injuries, was taken to hospital.
Probable cause:
The investigation identified the following causal factors:
1. Significant rainfall, and anomalies in the aircraft’s fuel filler neck and cap, led to the presence of water in the right-hand fuel tank,
2. Shortly after takeoff, the water in the right-hand fuel tank entered the engine fuel system causing the engine to stop running,
3. Control of the aircraft was not retained after the right-hand engine stopped.
Contributing factors:
1. No pre-flight water drain check was carried out; such a check would have allowed the presence of water in the right-hand fuel tank to be detected and corrective action taken.
2. It is possible that performance-reducing windshear, encountered during the downwind departure, contributed to a reduction in airspeed shortly before the aircraft stalled.
Final Report:

Crash of a Dornier DO228-202 in Kathmandu: 19 killed

Date & Time: Sep 28, 2012 at 0618 LT
Type of aircraft:
Operator:
Registration:
9N-AHA
Flight Phase:
Survivors:
No
Schedule:
Kathmandu - Lukla
MSN:
8123
YOM:
1987
Flight number:
SIT601
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
19
Captain / Total flying hours:
8308
Captain / Total hours on type:
7112.00
Copilot / Total flying hours:
772
Copilot / Total hours on type:
519
Circumstances:
A Dornier 228 aircraft, registration 9N-AHA, was planned to operate a flight from Tribhuvan International Airport (TIA), Kathmandu, to Tensing/Hillary Airport, Lukla with 16 passengers and 3 crews. The Commander was the Pilot Flying (PF) which was in accordance with common practice for flight crews operating this route. The 0020Z METAR for TIA reported calm wind, 3,000 m visibility in mist, scattered cloud at 2,000 ft AAL, broken cloud at 10,000 ft AAL, a temperature of 19° C and a QNH of 1017 HPa. ATC broadcast a change in the QNH to 1018 HPa at 0029 hrs. At 0028 hrs (0613 am), the Co-pilot asked ATC for taxi clearance and 9N-AHA taxied towards Intersection 2 for Runway 20. While taxiing towards the runway the flight crew carried out the before takeoff checklist during which the Commander confirmed that Flaps 1 was set and all four booster pumps were ON. There was no emergency brief or discussion about the reference speeds to be used during the takeoff. The flight crew changed frequency and contacted the tower controller who gave them clearance to enter Runway 20 from the intersection and wait for clearance to takeoff. The Commander asked for the line-up checks to be completed during which the Speed Lever was selected to HIGH. After lining up, the Commander said "THERE IS A BIRD" and, three seconds later "I WILL TAKE FLAPS TWO" which was acknowledged by the co-pilot. The aircraft was cleared for departure and began its takeoff run at 0032 hrs. Two seconds after beginning the takeoff roll, the Commander said "WATCH OUT THE BIRD". The Co-pilot called "50 KNOTS " as the aircraft approached 50 kt and the Commander replied "CHECK". Two seconds later, the co-pilot called "BIRD CLEAR SIR" as the aircraft accelerated through 58 kt. Approaching 70 kt, approximately 13 kt below V1 and Vr , the first officer called "VEE ONE ROTATE". The aircraft began to rotate but did not lift off the ground and the nose was briefly lowered again. As the aircraft reached 86 kt, it lifted off the ground and the landing gear was raised immediately. As the aircraft began to climb, it accelerated to 89 kt over approximately 2 seconds. It continued to climb to 100 ft above the runway over the next 11 seconds but, during this time, the speed decreased to 77 kt. The aircraft then flew level for 14 seconds during which time the following occurred: the speed decreased to 69 kt; the air traffic controller asked "ANY TECHNICAL?" to which the pilot replied "[uncertain]….DUE BIRD HIT"; it's heading changed slowly from 200 °M to approximately 173 °M; and the stall warning was triggered for three seconds as the aircraft decelerated through 71 kt. Two seconds after the stall warning ended, it was triggered again for approximately six seconds with the airspeed at 69 kt. The aircraft began a gentle descent at 69 kt with the stall warning sounding and the rate of turn to the left increased rapidly. It departed controlled flight, most probably left wing low, and crashed into a small open area 420 m south-east of the end of Runway 20. A runway inspection found the remains of a bird, identified as a "Black Kite", at a position 408 m from Intersection 2. No bird strike was reported in relation to any other departure.
Probable cause:
Causal Factors:
The investigation identified the following causal factors:
1. During level flight phase of the aircraft, the drag on the aircraft was greater than the power available and the aircraft decelerated. That resulted in excessive drag in such critical phase of ascent lowering the required thrust. The investigation was unable to determine the reason for the reduced thrust.
2. The flight crew did not maintain the airspeed above the stall speed and there was insufficient height available to recover when the aircraft departed controlled flight.
Contributory Factors:
The investigation identified the following contributory factors:
1. The flight crew did not maintain V2 during the climb and so the power required to maintain the level flight was greater than it would otherwise have been.
2. The flight crew did not maintain the runway centreline which removed the option of landing the aircraft on the runway remaining.
Final Report:

Crash of a PZL-Mielec AN-28 in Palana: 10 killed

Date & Time: Sep 12, 2012 at 1220 LT
Type of aircraft:
Operator:
Registration:
RA-28715
Survivors:
Yes
Schedule:
Petropavlovsk-Kamchatsky - Palana
MSN:
1AJ006-25
YOM:
1989
Flight number:
PTK251
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
8955
Captain / Total hours on type:
7732.00
Copilot / Total flying hours:
6543
Copilot / Total hours on type:
6347
Aircraft flight hours:
11947
Aircraft flight cycles:
8891
Circumstances:
Following an uneventful flight from Petropavlovsk-Kamchatsky, the crew started the descent to Palana Airport Runway 11 from the south. In marginal weather conditions, the twin engine aircraft descended too low, impacted trees and crashed in a wooded area located on Mt Pyatibratka. The wreckage was found at a height of 216 meters some 10 km south of the airport. Both pilots and 8 passengers were killed while four other passengers were seriously injured. Thea aircraft was destroyed by impact forces.
Probable cause:
The fatal accident with An-28 RA-28715 aircraft was caused by violation of specified approach pattern in Palan Airport resulted in outbound track and premature descending up to unauthorized low altitude performing flight in mountainous terrain in weather conditions excluding sustained visual reference with ground references resulted in aircraft collision with mountain slope, its destruction and crew and passengers fatality. Alcohol was detected in blood of both crew members.
Contributing factors were:
- Low level of discipline of personnel in Petropavlovsk-Kamchatsky Air Enterprise and inadequate flight methodical work in enterprises in a part of crew preflight training and approach patterns monitoring.
- Crew inaction when the radio altimeter altitude alert was actuated.
- Ground Proximity Warning System at An-28 aircraft could probably prevent the accident.
Final Report:

Crash of an ATR42-500 in Lahore

Date & Time: Aug 31, 2012 at 1510 LT
Type of aircraft:
Operator:
Registration:
AP-BHJ
Survivors:
Yes
Schedule:
Islamabad - Lahore
MSN:
657
YOM:
2006
Flight number:
PK653
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Islamabad, the crew started the descent to runway 36R in marginal weather conditions. Upon touchdown on a wet runway, the right main gear collapsed. The aircraft slid for about 1,700 feet before exiting the runway to the right and coming to rest 60 feet further on. All 46 occupants were unhurt while the aircraft was considered as damaged beyond repair. Five minutes after the accident, the weather briefing was as follow: OPLA 311015Z 16009KT 3000 RA BKN040 OVC100 29/24 Q1003. But ten minutes prior to the crash, the weather briefing was as follow: OPLA 311000Z 33008KT 4000 -RA SCT040 BKN100 32/24 Q1002 TEMPO 31030KT 2000 TSRA FEW030CB. Thus, the conditions were considered as marginal with turbulences, wind to 30 knots and CB's at 3,000 feet. On 11SEP2012, the French BEA reported that the aircraft touched down just at the beginning of the paved surface (undershoot area) to the right of the extended runway 36R centerline, causing the right main gear to collapse. It was reported that the aircraft was unstable on short final and that the crew failed to initiate a go-around procedure while the aircraft was too low on the glide.