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:

Ground fire of a Boeing 737-322 in Aktau

Date & Time: Jun 16, 2015 at 1900 LT
Type of aircraft:
Operator:
Registration:
LY-FLB
Flight Phase:
Survivors:
Yes
Schedule:
Aktau - Mineralnye Vody
MSN:
24667/1893
YOM:
1990
Flight number:
DV831
Location:
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After completing flight DV742 from Astana, the aircraft was parked at a gate, waiting for its passengers to complete the flight DV831 to Mineralnye Vody. The aircraft landed at 1818LT and was scheduled to depart around 1915LT when an explosion occurred in the forward baggage compartment (between STA 380 and STA 440). A fire spread into the cabin and partially destroyed the fuselage. Nobody was hurt in this incident but the aircraft was damaged beyond repair.
Probable cause:
The cause of the fire and the fire on board the aircraft, was the spontaneous destruction of the oxygen hose with compressed oxygen, used for filling the aircraft using a ground source with pressurized oxygen.
Contributing causes of fire and the fire were:
Instant spontaneous combustion of dynamically disturbed and oxygen-enriched air-flow in a fine dust environment in the front luggage compartment in the area of the aircraft oxygen bottle due to constant pressure of oxygen coming from an open oxygen cylinder.

Crash of a Xian MA60 in Fuzhou

Date & Time: May 10, 2015 at 1157 LT
Type of aircraft:
Operator:
Registration:
B-3476
Survivors:
Yes
Schedule:
Hefei – Yiwu – Fuzhou
MSN:
08 05
YOM:
2010
Flight number:
JOY1529
Location:
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
45
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 03 at Fuzhou Airport, a tyre burst on the right main landing gear. The aircraft skidded, veered off runway to the right and entered a grassy area. Both wings detached from the upper side of the fuselage, causing both engines to struck the ground and the fuselage to brake in two. All 52 occupants were rescued, among them three passengers were injured.

Crash of an Airbus A320-232 in Istanbul

Date & Time: Apr 25, 2015 at 1041 LT
Type of aircraft:
Operator:
Registration:
TC-JPE
Survivors:
Yes
Schedule:
Milan – Istanbul
MSN:
2941
YOM:
2006
Flight number:
TK1878
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Milan-Malpensa Airport at 0700LT and proceeded to the east. Following an uneventful flight, the crew initiated the approach to Istanbul-Atatürk Airport Runway 05. At a height of 100 feet above the runway, the aircraft banked to the right, stalled and struck the runway surface. On impact, the right main gear was severely damaged and punctured the right wing. In such condition, the captain decided to abandon the landing manoeuvre and initiated a go-around procedure. The aircraft climbed to an assigned altitude of 3,800 feet then the crew declared an emergency and confirmed that the right engine was out of service. Few minutes later, the right engine caught fire. The crew followed a 20-minutes holding circuit over the bay of Marmara before a second approach to runway 35L. After touchdown, the right main gear collapsed, the aircraft slid for few dozen metres then veered off runway to the right, completed a 180 turn before coming to rest in a grassy area. All 97 occupants evacuated safely while the aircraft was damaged beyond repair. According to the operator, the loss of control during the last segment was caused by turbulences from a preceding Boeing 787 that landed on the same runway 05.

Crash of an Airbus A320-232 in Hiroshima

Date & Time: Apr 14, 2015 at 2005 LT
Type of aircraft:
Operator:
Registration:
HL7762
Survivors:
Yes
Schedule:
Seoul – Hiroshima
MSN:
3244
YOM:
2007
Flight number:
OZ162
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
74
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8242
Captain / Total hours on type:
1318.00
Copilot / Total flying hours:
1588
Copilot / Total hours on type:
1298
Aircraft flight hours:
23595
Circumstances:
The approach to Hiroshima Airport was completed in marginal weather conditions. The autopilot was disengaged at 2,100 feet MSL when the aircraft descended below the glide path and hit approach lights and the localiser antenna located 325 meters short of runway 28. The aircraft continued the descent, hit the soft ground short of runway. Then it rolled on runway for some 1,154 meters, veered to the left, went off runway and came to rest 130 meters to the left of the concrete runway, some 1,477 meters past the runway threshold. All 82 occupants were evacuated, among them 27 (25 passengers and 2 crew members) were injured. The aircraft was considered as written off due to severe damages on both engines, ailerons, wings and the bottom of the fuselage. At the time of the accident, weather conditions were difficult with visibility up to 4 km, RVR on runway 28 variable from 300 to 1,800 meters, light rain, partial fog, one octa cloud at 0 feet, 4 octas at 500 feet, 6 octas at 1,200 feet.
Probable cause:
It is certain that when landing on RWY 28 at the Airport, the Aircraft undershot and the PIC commenced executing a go-around; however, it collided with the Aeronautical Radio Navigation Aids located in front of RWY 28 threshold, just before turning to climb. Regarding the fact that the Aircraft undershot, it is probable that there might be following aspects in causes: The PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below the approach height threshold (Decision Altitude: DA); and as well, the FO, as pilot-monitoring who should have monitored meteorological conditions and flight operations, did not make a call-out of go-around immediately when he could not see the runway at DA. Regarding the fact that the PIC continued approaching without executing a go around while the position of the Aircraft could not be identified by visual references which should have been in view and identified continuously at or below DA, he did not comply with the regulations and SOP, and it is probable that there was a background factor that the education and trainings for compliance of rules in the Company was insufficient. In addition, regarding the fact that the FO did not make an assertion of go around, it is probable that the CRM did not function appropriately.
Final Report:

Crash of an Airbus A320-211 in Halifax

Date & Time: Mar 29, 2015 at 0030 LT
Type of aircraft:
Operator:
Registration:
C-FTJP
Survivors:
Yes
Schedule:
Toronto – Halifax
MSN:
233
YOM:
1991
Flight number:
AC624
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11765
Captain / Total hours on type:
5755.00
Copilot / Total flying hours:
11300
Copilot / Total hours on type:
6392
Aircraft flight hours:
75103
Circumstances:
On 29 March 2015, an Air Canada Airbus Industrie A320-211 (registration C-FTJP, serial number 233), operating as Air Canada flight 624, was on a scheduled flight from Toronto/Lester B. Pearson International Airport, Ontario, to Halifax/Stanfield International Airport, Nova Scotia, with 133 passengers and 5 crew members on board. At approximately 0030 Atlantic Daylight Time, while conducting a non-precision approach to Runway 05, the aircraft severed power lines, then struck the snow-covered ground about 740 feet before the runway threshold. The aircraft continued airborne through the localizer antenna array, then struck the ground twice more before sliding along the runway. It came to rest on the left side of the runway, about 1900 feet beyond the threshold. The aircraft was evacuated; 25 people sustained injuries and were taken to local hospitals. The aircraft was destroyed. There was no post-impact fire. The emergency locator transmitter was not activated. The accident occurred during the hours of darkness.
Probable cause:
Findings as to causes and contributing factors:

1. Air Canada’s standard operating procedure (SOP) and practice when flying in flight path angle guidance mode was that, once the aircraft was past the final approach fix, the flight crews were not required to monitor the aircraft’s altitude and distance from the threshold or to make any adjustments to the flight path angle. This practice was not in accordance with the flight crew operating manuals of Air Canada or Airbus.
2. As per Air Canada’s practice, once the flight path angle was selected and the aircraft began to descend, the flight crew did not monitor the altitude and distance from the threshold, nor did they make any adjustments to the flight path angle.
3. The flight crew did not notice that the aircraft had drifted below and diverged from the planned vertical descent angle flight profile, nor were they aware that the aircraft had crossed the minimum descent altitude further back from the threshold.
4. Considering the challenging conditions to acquire and maintain the visual cues, it is likely the flight crew delayed disconnecting the autopilot until beyond the minimum descent altitude because of their reliance on the autopilot system.
5. The approach and runway lights were not changed from setting 4 to setting 5; therefore, these lights were not at their maximum brightness setting during the approach.
6. The system to control the airfield lighting’s preset selections for brightness setting 4 was not in accordance with the NAV CANADA Air Traffic Control Manual of Operations requirement for the omnidirectional approach lighting system to be at its brightest settings.
7. The limited number of visual cues and the short time that they were available to the flight crew, combined with potential visual illusions and the reduced brightness of the approach and runway lights, diminished the flight crew’s ability to detect that the aircraft’s approach path was taking it short of the runway.
8. The flight crew’s recognition that the aircraft was too low during the approach would have been delayed because of plan continuation bias.
9. The aircraft struck terrain approximately 740 feet short of the runway threshold, bounced twice, and then slid along the runway before coming to a rest approximately 1900 feet beyond the runway threshold.
10. At some time during the impact sequence, the captain’s head struck the glare shield because there were insufficient acceleration forces to lock the shoulder harness and prevent movement of his upper body.
11. The first officer sustained a head injury and serious injury to the right eye as a result of striking the glare shield because the automatic locking feature of the right-side shoulder-harness inertia reel was unserviceable.
12. A flight attendant was injured by a coffee brewer that came free of its mounting base because its locking system was not correctly engaged.
13. Because no emergency was expected, the passengers and cabin crew were not in a brace position at the time of the initial impact.
14. Most of the injuries sustained by the passengers were consistent with not adopting a brace position.

Findings as to risk:

1. If aircraft cockpit voice recorder installations do not have an independent power supply, additional, potentially valuable information will not be available for an investigation.
2. If Transport Canada does not consistently follow its protocol for the assessment of aeromedical risk and ongoing surveillance in applicants who suffer from obstructive sleep apnea, some of the safety benefit of medical examinations will be lost, increasing the risk that pilots will fly with a medical condition that poses a risk to safety.
3. If new regulations on the use of child-restraint systems are not implemented, lap-held infants and young children are exposed to undue risk and are not provided with a level of safety equivalent to that for adult passengers.
4. If passengers do not dress appropriately for safe travel, they risk being unprepared for adverse weather conditions during an emergency evacuation.
5. If the type of approach lighting system on a runway is not factored into the minimum visibility required to carry out an approach, in conditions of reduced visibility, the lighting available risks being less than adequate for flight crews to assess the aircraft’s position and decide whether or not to continue the approach to a safe landing.
6. If they do not incorporate a means of absorbing forces along their longitudinal axis, vertically mounted, non-structural beams (channels, tubes, etc.) in cargo compartments could penetrate the cabin floor when the fuselage strikes the water or ground, increasing the risk of aircraft occupants being injured or emergency egress being impaired.
7. If an aircraft manufacturer’s maintenance instructions do not include the component manufacturer’s safety-critical test criteria, the component risks not being maintained in an airworthy condition.
8. If there is a complete loss of electrical and battery power and the passenger address system does not have an independent emergency power supply, the passenger address system will be inoperable, and the initial command to evacuate or to convey other emergency instructions may be delayed, putting the safety of passengers and crew at risk.
9. If passengers retrieve or attempt to retrieve their carry-on baggage during an evacuation, they are putting themselves and other passengers at a greater risk of injury or death.
10. If passengers do not pay attention to the pre-departure safety briefings or review the safety-features cards, they may be unprepared to react appropriately in an accident, increasing their risk of injury or death.
11. If an organization’s emergency response plan does not identify all available transportation resources, there is an increased risk that evacuated passengers and crew will not be moved from an accident site in a timely manner.
12. If organizations do not practise transporting persons from an on-airport accident site, they may be insufficiently prepared to react appropriately to an actual accident, which may increase the time required to evacuate the passengers and crew.

Other findings:

1. The service director assessed the evacuation flow as good and determined that there was therefore no need to open the R1 door.
2. The flight attendants stationed in the rear of the aircraft noted no life-threatening hazards. Because no evacuation order had been given, and deplaned passengers and firefighters were observed walking near the rear of the aircraft in an area where the deployment of the rear slides may have created additional hazards or risks, the flight attendants determined that there was no requirement to open the L2 and R2 doors.
3. Although Transport Canada required the dual-exit drill to be implemented in training, it did not require all cabin crew to receive the training before an organization implemented the 1:50 ratio.
4. At the time of the accident, neither the service director nor the flight attendants had received the dual-exit training, nor were they aware of the requirement for such training in order for Air Canada to operate with the exemption allowing 1 flight attendant for each unit of 50 passengers.
5. Although Transport Canada had reviewed and approved Air Canada’s aircraft operating manual and the standard operating procedures (SOPs), it had not identified the discrepancy between the Air Canada SOPs and the Airbus flight crew operating manual regarding the requirement to monitor the aircraft’s vertical flight path beyond the final approach fix when the flight path angle guidance mode is engaged.
6. A discrepancy in the Halifax International Airport Authority’s standby generators’ control circuitry caused the 2 standby generators to stop producing power.
7. Air Canada’s emergency response plan for Halifax/Stanfield International Airport indicated that the airline was responsible for the transportation of passengers from an accident site.
8. Air Canada’s emergency response plan did not identify the airport’s Park’N Fly minibuses as transportation resources. 9. The Halifax International Airport Authority’s emergency response plan did not identify that the airport Park’N Fly mini-buses could be used to transport the uninjured passengers, nor did it provide instructions on when and how to request and dispatch any transportation resources available at the airport.
10. The Air Canada Flight Operations Manual did not identify that the required visual reference should enable the pilot to assess aircraft position and rate of change of position in order to continue the approach to a landing.
11. In Canada, the minimum visibility that is authorized by the operations specification for non-precision approaches does not take into account the type of approach lighting system installed on the runway.
12. It is likely that, during the emergency, a passenger activated the L1 door gust lock release pushbutton while trying to expedite his or her exit, which allowed the door to move freely.
13. The passenger seatbacks were dislodged because the shear pins had sheared, likely as a result of contact with passengers during the impact sequence or emergency egress.
14. Recovery of the uninjured passengers from the accident site was delayed owing to a number of factors, including the severe weather conditions; the failure of the airport’s 2 standby generators to provide backup power after the loss of utility power; the loss of the airport operations radio network; and the lack of arrangements for the dispatch of transportation vehicles until after emergency response services had advised that all passengers were evacuated and the site was all clear.
15. Given that the captain rarely used continuous positive airway pressure therapy, he would have been at risk of experiencing fatigue related to chronic sleep disruption caused by obstructive sleep apnea. However, there was no indication that fatigue played a causal or contributory role in this occurrence.
Final Report:

Crash of an Airbus A320-211 near Prads-Haute-Bléone: 150 killed

Date & Time: Mar 24, 2015 at 1041 LT
Type of aircraft:
Operator:
Registration:
D-AIPX
Flight Phase:
Survivors:
No
Site:
Schedule:
Barcelona – Düsseldorf
MSN:
147
YOM:
1990
Flight number:
4U9525
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
144
Pax fatalities:
Other fatalities:
Total fatalities:
150
Captain / Total flying hours:
6763
Captain / Total hours on type:
3811.00
Copilot / Total flying hours:
919
Copilot / Total hours on type:
540
Aircraft flight hours:
58313
Aircraft flight cycles:
46748
Circumstances:
The aircraft left Barcelona at 1000LT on a scheduled flight to Düsseldorf (flight 4U9525/GWI18G). At 1032LT, one minute after reaching its assigned cruising altitude of 38,000 feet near Toulon (level off), the aircraft started to lose altitude and continued a straight in descent during nine minutes, until it reached the altitude of 6,800 feet. It was later confirmed that no distress call was sent by the crew. Radar contact was lost at a height of 6,800 feet at 1041LT when the aircraft hit a mountain slope located near Prads-Haute-Bléone, northeast of Digne-les-Bains. At the time of the accident, weather conditions were considered as good with no storm activity, reasonable wind component and no turbulence. The crash site was reached by first rescuers in the afternoon and the aircraft disintegrated on impact. None of the 150 occupants survived the crash. The second black box (DFDR) was found on April 2, nine days after the accident.
Probable cause:
The collision with the ground was due to the deliberate and planned action of the copilot who decided to commit suicide while alone in the cockpit. The process for medical certification of pilots, in particular self-reporting in case of decrease in medical fitness between two periodic medical evaluations, did not succeed in preventing the copilot, who was experiencing mental disorder with psychotic symptoms, from exercising the privilege of his licence. The following factors may have contributed to the failure of this principle:
-The copilot’s probable fear of losing his ability to fly as a professional pilot if he had reported his decrease in medical fitness to an AME,
-The potential financial consequences generated by the lack of specific insurance covering the risks of loss of income in case of unfitness to fly,
- The lack of clear guidelines in German regulations on when a threat to public safety outweighs the requirements of medical confidentiality.
Security requirements led to cockpit doors designed to resist forcible intrusion by unauthorized persons. This made it impossible to enter the flight compartment before the aircraft impacted the terrain in the French Alps.
Final Report:

Crash of a De Havilland DHC-8-402Q in Hubli

Date & Time: Mar 8, 2015 at 1915 LT
Operator:
Registration:
VT-SUA
Survivors:
Yes
Schedule:
Bangalore – Hubli
MSN:
4373
YOM:
2011
Flight number:
SG1085
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
78
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7050
Captain / Total hours on type:
1850.00
Copilot / Total flying hours:
1343
Copilot / Total hours on type:
1083
Aircraft flight hours:
10224
Aircraft flight cycles:
9440
Circumstances:
On 08.03.2015 M/s Spice Jet Ltd. Bombardier Q-400 aircraft VT-SUA, was operating a scheduled flight from Bangalore to Hubli under the command of ATPL license holder endorsed on type with duly qualified First Officer on type. There were 78 passengers and 4 crew members on board the aircraft. Previous to the accident flight, the aircraft VT-SUA had operated a flight Chennai – Bangalore with the same PIC. The flight was uneventful and there was no snag reported by the PIC on the completion of the flight. Subsequently the aircraft was scheduled for SG-1085, Bangalore - Hubli on 08.03.2015 at around 13:00 UTC. The aircraft took off from Bangalore at around 1300 UTC and the visibility reported for Hubli was 10 km. When the aircraft came in contact with Mangalore ATC, Mangalore ATC cleared aircraft direct to Hubli and informed heavy rains and thunder showers over Hubli with visibility 3000 m. Since the weather at Hubli had deteriorated, the PIC reduced aircraft speed for reassuring the flight parameters. As there is no refueling facility available at Hubli, the sector is a tankering sector hence the aircraft had enough fuel for holding. While approaching into Hubli the pilot requested latest weather from ATC Hubli. At around 60 nm from Hubli, the weather reported by ATC Hubli was heavy rain and visibility 4000 meters. The ATC cleared aircraft for NDB approach runway 26, however the PIC preferred to carry out VOR DME trial procedure for runway 26. The runway condition was neither asked by the cockpit crew nor intimated by the ATC. The descent was commenced and about 25 nm short of Hubli, ATC again advised visibility has reduced to 3000 m due heavy rain and thunderstorm. Thereafter the crew decided to hold over Hubli until the weather improves. 20 minutes into holding, the ATC again informed that visibility has improved to 4000m in moderate rain. Subsequently descent was requested by the pilot for runway 26. The PIC stated that he had established visual reference with runway at about 6 nm on the final approach course. The crew also selected vipers on short finals to have a better visibility. The aircraft landed normally. The PIC had stated that after touch down and reducing power to DISC, as he was concentrating on the far end of the runway as the runway was wet, he did not realize that the aircraft was drifting to the left of the center line. He further mentioned that he selected full reverse on both the engines to maintain the aircraft on the center line however the aircraft veered toward the left side of the runway and in the process overrun the runway edge light followed by LH landing gear collapsed. After the left landing gear collapsed the left propeller blades hit the runway surface and sheared off from the root attachment. The PIC maneuvered the aircraft however the nose wheel tyre failed under over load conditions and the nose landing gear collapsed and the aircraft belly came in contact with the runway surface. Subsequently, the aircraft exited the runway on the left side on Kutcha and came to the final stop at round 52 meters away from the runway center line. The cockpit crew switched off the engines and the electrical power supply and cockpit door and announced evacuation. The cabin crew opened and the cabin doors on the right for evacuation. The ATC had alerted the fire services and the fire vehicles reached the aircraft after it came to final halt position. The fire personnel also assisted in the safe evacuation of all the passengers from the RH side. There was no injury to any of the occupants on board the aircraft. There was no postaccident fire.
Probable cause:
Loss of visual cues after touch down in inclemental weather conditions resulted in veering of the aircraft towards left of the centerline leading to runway excursion and accident.
Following are the contributory factors:
1. Inappropriate handling technique of the aircraft controls by the PIC to maintain the directional control of the aircraft after landing.
2. Non-standards callouts by the first officer to correct situation after landing.
3. Impact of the landing gear with the non-frangible erected runway edge light resulted in retraction of the same.
4. At the time of the accident DGCA O.M. No. AV.15026/006/92- AS dated 3rd February 1992 was in force, which dictated examiners and instructors of the operators only to carry out trial procedures in VMC and during Daytime only. M/s Spice jet instructions to the flight crew did not reflect the same and allowed flight crew with less experience & below VMC flight conditions to carry out trial procedures. This may have contributed to the accident.
Final Report:

Crash of a McDonnell Douglas MD-88 in LaGuardia

Date & Time: Mar 5, 2015 at 1102 LT
Type of aircraft:
Operator:
Registration:
N909DL
Survivors:
Yes
Schedule:
Atlanta – New York
MSN:
49540/1395
YOM:
1987
Flight number:
DL1086
Crew on board:
5
Crew fatalities:
Pax on board:
125
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15200
Captain / Total hours on type:
11000.00
Copilot / Total flying hours:
11000
Copilot / Total hours on type:
3000
Aircraft flight hours:
71196
Aircraft flight cycles:
54865
Circumstances:
The aircraft was landing on runway 13 at LaGuardia Airport (LGA), New York, New York, when it departed the left side of the runway, contacted the airport perimeter fence, and came to rest with the airplane’s nose on an embankment next to Flushing Bay. The 2 pilots, 3 flight attendants, and 98 of the 127 passengers were not injured; the other 29 passengers received minor injuries. The airplane was substantially damaged. Flight 1086 was a regularly scheduled passenger flight from Hartsfield-Jackson Atlanta International Airport, Atlanta, Georgia, operating under the provisions of 14 Code of Federal Regulations Part 121. An instrument flight rules flight plan had been filed. Instrument meteorological conditions prevailed at the time of the accident. The captain and the first officer were highly experienced MD-88 pilots. The captain had accumulated about 11,000 hours, and the first officer had accumulated about 3,000 hours, on the MD-88/-90. In addition, the captain was previously based at LGA and had made many landings there in winter weather conditions. The flight crew was concerned about the available landing distance on runway 13 and, while en route to LGA, spent considerable time analyzing the airplane’s stopping performance. The flight crew also requested braking action reports about 45 and 35 minutes before landing, but none were available at those times because of runway snow clearing operations. The unavailability of braking actions reports and the uncertainty about the runway’s condition created some situational stress for the captain, who was the pilot flying. After runway 13 became available for arriving airplanes, the flight crews of two preceding airplanes (which landed on the runway about 16 and 8 minutes before the accident landing) reported good braking action on the runway, so the flight crew expected to see at least some of the runway’s surface after the airplane broke out of the clouds. However, the flight crew saw that the runway was covered with snow, which was inconsistent with their expectations based on the braking action reports and the snow clearing operations that had concluded less than 30 minutes before the airplane landed. The snowier-than-expected runway, along with its relatively short length and the presence of Flushing Bay directly off the departure end of the runway, most likely increased the captain’s concerns about his ability to stop the airplane within the available runway distance, which exacerbated his situational stress. The captain made a relatively aggressive reverse thrust input almost immediately after touchdown. Reverse thrust is one of the methods that pilots use to decelerate the airplane during the landing roll. Reverse thrust settings are expressed as engine pressure ratio (EPR) values, which are measurements of engine power (the ratio of the pressure of the gases at the exhaust compared with the pressure of the air entering the inlet). Both pilots were aware that 1.3 EPR was the target setting for contaminated runways.As reverse thrust EPR was rapidly increasing, the captain’s attention was focused on other aspects of the landing, which included steering the airplane to counteract a slide to the left and ensuring that the spoilers had deployed (a necessary action for the autobrakes to engage). The maximum EPR values reached during the landing were 2.07 on the left engine and 1.91 on the right engine, which were much higher than the target setting of 1.3 EPR. These high EPR values likely resulted from a combination of the captain’s stress; his relatively aggressive reverse thrust input; and operational distractions, including the airplane’s continued slide to the left despite the captain’s efforts to steer it away from the snowbanks alongside the runway. All of these factors reduced the captain’s monitoring of EPR indications. The high EPR values caused rudder blanking (which occurs on MD-80 series airplanes when smooth airflow over the rudder is disrupted by high reverse thrust) and a subsequent loss of aerodynamic directional control. Although the captain stowed the thrust reversers and applied substantial right rudder, right nosewheel steering, and right manual braking, the airplane’s departure from the left side of the runway could not be avoided because directional control was regained too late to be effective.
Probable cause:
The National Transportation Safety Board determines that the probable cause of this accident was the captain’s inability to maintain directional control of the airplane due to his application of excessive reverse thrust, which degraded the effectiveness of the rudder in controlling the airplane’s heading. Contributing to the accident were the captain’s:
- situational stress resulting from his concern about stopping performance and
- attentional limitations due to the high workload during the landing, which prevented him from immediately recognizing the use of excessive reverse thrust.
Final Report:

Crash of an Airbus A330-303 in Kathmandu

Date & Time: Mar 4, 2015 at 0744 LT
Type of aircraft:
Operator:
Registration:
TC-JOC
Survivors:
Yes
Schedule:
Istanbul – Kathmandu
MSN:
1522
YOM:
2014
Flight number:
TK726
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
224
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14942
Captain / Total hours on type:
1456.00
Copilot / Total flying hours:
7659
Copilot / Total hours on type:
1269
Aircraft flight hours:
4139
Aircraft flight cycles:
732
Circumstances:
The aircraft departed Istanbul at 1818LT on March 3 on a scheduled flight to Tribhuvan International Airport (TIA), Kathmandu with 11 crew members and 224 passengers .The aircraft started contacting Kathmandu Control from 00:02 hrs to 00:11hrs while the aircraft was under control of Varanasi and descending to FL 250 but there was no response because Kathmandu Control was not yet in operation. The airport opened at its scheduled time of 00:15hrs. The aircraft established its first contact with Kathmandu Approach at 00:17 hrs and reported holding over Parsa at FL 270. Kathmandu Approach reported visibility 100 meters and airport status as closed. At 00:22 hrs the aircraft requested to proceed to Simara due to moderate turbulence. The Kathmandu Approach instructed the aircraft to descend to FL 210 and proceed to Simara and hold. At 01:05 hrs when Kathmandu Approach provided an updated visibility of 1000 meters and asked the flight crew of their intentions, the flight crew reported ready for RNAV (RNP) APCH for runway 02. The aircraft was given clearance to make an RNP AR APCH. At 01:23 hrs when the aircraft reported Dovan, Kathmandu Approach instructed the flight crew to contact Kathmandu Tower. Kathmandu Tower issued a landing clearance at 01:24 hrs and provided wind information of 100° at 03 knots. At 01:27 hrs the aircraft carried out a missed approach due to lack of visual reference. The aircraft was given clearance to proceed to RATAN hold via MANRI climbing to 10500 feet as per the missed approach procedure. During the missed approach the aircraft was instructed to contact Kathmandu Approach. At 01:43 hrs the aircraft requested the latest visibility to which Kathmandu Approach provided visibility 3000 m and Kathmandu Tower observation of 1000 meters towards the south east and few clouds at 1000 ft, SCT 2000 ft and BKN 10,000 feet. When the flight crew reported their intention to continue approach at 01:44 hrs, Kathmandu Approach cleared the aircraft for RNAV RNP APCH runway 02 and instructed to report RATAN. The aircraft reported crossing 6700 ft at 01:55 hrs to Kathmandu Tower. Kathmandu Tower cleared the aircraft to land and provided wind information of 160° at 04 kts. At 01:57 hrs Kathmandu Tower asked the aircraft if the runway was insight. The aircraft responded that they were not able to see the runway but were continuing the approach. The aircraft was at 880 ft AGL at that time. At 783 ft AGL the aircraft asked Kathmandu Tower if the approach lights were on. Kathmandu Tower informed the aircraft that the approach lights were on at full intensity. The auto-pilots remained coupled to the aircraft until 14 ft AGL, when it was disconnected, a flare was attempted. The maximum vertical acceleration recorded on the flight data recorder was approximately 2.7 G. The aircraft pitch at touchdown was 1.8 degree nose up up which is lower than a normal flare attitude for other landings. From physical evidence recorded on the runway and the GPS latitude and longitude coordinate data the aircraft touched down to the left of the runway centerline with the left hand main gear off the paved runway surface. The aircraft crossed taxiways E and D and came to a stop on the grass area between taxiway D and C with the heading of the aircraft on rest position being 345 degrees (North North West) and the position of the aircraft on rest position was at N 27° 41' 46", E 85° 21'29" At 02:00 hrs Kathmandu Tower asked if the aircraft had landed. The aircraft requested medical and fire assistance reporting its position at the end of the runway. At 02:03 hrs the aircraft requested for bridge and stairs to open the door and vacate passengers instead of evacuation. The fire and rescue team opened the left cabin door and requested the cabin attendant as well as to pilot through Kathmandu Tower to deploy the evacuation slides. At 02:10 hrs evacuation signal was given to disembark the passengers. All passengers were evacuated safely and later, the aircraft was declared as damaged beyond repair.
Probable cause:
The probable cause of this accident is the decision of the flight crew to continue approach and landing below the minima with inadequate visual reference and not to perform a missed approach in accordance to the published approach procedure. Other contributing factors of the accident are probable fixation of the flight crew to land at Kathmandu, and the deterioration of weather conditions that resulted in fog over the airport reducing the visibility below the required minima. The following findings were reported:
- On March 2, 2015 i.e. two days before the accident, the crews of the flight to Kathmandu reported through RNP AR MONITORING FORM that all the NAV. accuracy and deviation parameter were perfectly correct at MINIMUM but the real aircraft position was high (PAPI 4 whites) and left offset,
- The airlines as well as crews were unaware of the fact that wrong threshold coordinates were uploaded on FMGS NAV data base of the aircraft,
- The flight crew was unable to get ATIS information on the published frequency because ATIS was not operating. ATIS status was also not included in the Daily Facilities Status check list reporting form of TIA Kathmandu,
- Turkish Airlines Safety Department advised to change the scheduled arrival time at Kathmandu Airport,
- It was the first flight of the Captain to Kathmandu airport and third flight but first RNAV (RNP) approach of the Copilot,
- Both approaches were flown with the auto-pilots coupled,
- Crew comments on the CVR during approach could be an indication that they (crews) were tempted to continue to descend below the decision height despite lack of adequate visual reference condition contrary to State published Standard Instrument Arrival and company Standard Operating procedures with the expectation of getting visual contact with the ground,
- The flight crew were not visual with the runway or approach light at MDA,
- The MET Office did not disseminate SPECI representing deterioration in visibility according to Annex 3,
- The Approach Control and the Kathmandu Tower did not update the aircraft with its observation representing a sudden deterioration in visibility condition due to moving fog,
- The Air Traffic Control Officers are not provided with refresher training at regular interval,
- CAAN did not take into account for the AIRAC cycle 04-2015 from 05 Feb 2015 to 04 March 2015 while cancelling AIP supplement,
- The auto-pilots remained coupled to the aircraft until 14ft AGL when it was disconnected and a flare was attempted,
- The crews were not fully following the standard procedure of KTM RNAV (RNP) Approach and company Standard Operating procedures.
Final Report: