Crash of an ATR42-300 near Oksibil: 54 killed

Date & Time: Aug 16, 2015 at 1455 LT
Type of aircraft:
Operator:
Registration:
PK-YRN
Flight Phase:
Survivors:
No
Site:
Schedule:
Jayapura - Oksibil
MSN:
102
YOM:
1988
Flight number:
TGN267
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
54
Captain / Total flying hours:
25287
Captain / Total hours on type:
7340.00
Copilot / Total flying hours:
3818
Copilot / Total hours on type:
2640
Aircraft flight hours:
50133
Aircraft flight cycles:
55663
Circumstances:
An ATR 42-300 aircraft registered PK-YRN was being operated by PT Trigana Air Service on 16 August 2015 as scheduled passenger flight with flight number IL267 from Sentani to Oksibil. On board of this flight were 54 persons. This flight was the fifth flight of the day and the second flight from Sentani to Oksibil. The aircraft departed Sentani at 0522 UTC and estimated time of arrival Oksibil was at 0604 UTC. The Second in Command (SIC) acted as Pilot Flying while the Pilot in Command (PIC) acted as Pilot Monitoring. The weather at Oksibil reported that the cloud was broken (more than half area of the sky covered by cloud) and the cloud base was 8,000 feet (4,000 feet above airport elevation) and the visibility was 4 up to 5 km. The area of final approach path was covered by clouds. The flight cruising at 11,500 feet and at 0555 UTC, the pilot made first contact with Oksibil Aerodrome Flight Information Services (AFIS) officer, reported on descent at position Abmisibil and intended to direct left base leg runway 11. At 0600 UTC, Oksibil AFIS officer expected the aircraft would have been on final but the pilot had not reported, the AFIS officer contacted the pilot but did not reply. The AFIS officer informed Trigana in Sentani that they had lost contact with IL267. The aircraft wreckage was found on a ridge of Tanggo Mountain, Okbape District, Oksibil at approximately 8,300 feet AMSL at coordinates of 04°49’17.34” S, 140°29’51.18” E, approximately 10 NM from Oksibil Aerodrome on bearing of 306°. All occupants were fatally injured and the aircraft was destroyed by impact force and post impact fire. The Flight Data Recorder (FDR) and Cockpit Voice Recorder were recovered and transported to KNKT recorder facility. The recovery of FDR data was unsuccessful while the recovery of CVR data successfully retrieved accident flight data. The CVR did not record any crew briefing, checklist reading not EGPWS warning prior to impact. The CVR also did not record EGPWS altitude call out on two previous flights. The investigation concluded that the EGPWS was probably not functioning.
Probable cause:
The following findings were identified:
1. The aircraft had valid Certificate of Airworthiness and was operated within the weight and balance envelope.
2. All crew had valid licenses and medical certificates.
3. The flight plan form was filed with intention to fly under Instrument Flight Rule (IFR), at flight level 155, with route from Sentani to MELAM via airways W66 then to Oksibil. The MORA of W66 between Sentani to MELAM was 18,500 feet.
4. The flight was the 5th flight of the day for the crew with the same aircraft and the second flight on the same route of Sentani to Oksibil.
5. The CVR data revealed that the previous flight from Sentani to Oksibil the flight cruised at altitude of 11,500 feet and the approach was conducted by direct to left base runway 11.
6. The CVR data also revealed that on the accident flight, the flight cruised at altitude 11,500 feet and intended to direct left base leg runway 11 which was deviate from the operator visual guidance approach that described the procedure to fly overhead the airport prior to approach to runway 11.
7. The witness stated that most of the time, the flight crew deviated from the operator visual approach guidance. The deviation did not identify by the aircraft operator.
8. The downloading process to retrieve data from the FDR was unsuccessful due to the damage of the FDR unit that most likely did not record data during the accident flight. The repetition problems of the FDR unit showed that the aircraft operator surveillance to the repair station was not effective.
9. The CVR did not record any crew briefing, checklist reading and EGPWS altitude callout prior to land on two previous flights nor the EGPWS caution and warning prior to impact.
10. The spectrum analysis of the CVR determined that both engines were operating prior to the impact.
11. Several pilots, had behavior of pulling the EGPWS CB to eliminate the nuisance of EGPWS warning. The pilots stated that the reason for pulling the EGPWS CB was due to the pilots considered this warning activation was not appropriate for the flight conditions. The correction to this behavior was not performed prior to the accident.
12. The investigation could not determine the actual EGPWS CB position during the accident flight.
13. The installation of EGPWS by the aircraft operator was not conducted according to the Service Bulletin issued by the aircraft manufacturer.
14. The terrain data base installed in the EGPWS of PK-YRN was the version MK_VIII_Worldwide_Ver_471 that was released in 2014. The Oksibil Airport was not included in the high-resolution update in this version of terrain database.
15. The information for Oksibil published in AIP volume IV (Aerodrome for Light Aircraft/ALA) did not include approach guidance. The operator issued visual guidance of circling approach runway 11 for internal use.
16. The visual approach guidance chart stated that the minimum safe altitude was 8,000 feet while the aircraft impacted with terrain at approximately 8,300 feet. This indicated an incorrect information in the chart. The investigation considered that the pattern on the approach guidance chart was not easy to fly, as many altitudes and heading changes.
17. Several maintenance records such as component status installed on the aircraft and installation of EGPWS was not well documented. This indicated that the maintenance management was not well performed.
18. The investigation could not find any regulation that describes the pilot training requirement for any addition or modification of aircraft system which affect to the aircraft operation.
19. There was no information related to the status of ZX NDB published on NOTAM prior to the accident.
20. Several safety issues indicated that the organization oversight of the aircraft operator by the regulator was not well implemented.
Contributing Factors:
1. The deviation from the visual approach guidance in visual flight rules without considering the weather and terrain condition, with no or limited visual reference to the terrain resulted in the aircraft flew to terrain.
2. The absence of EGPWS warning to alert the crew of the immediate hazardous situation led to the crew did not aware of the situation.
Final Report:

Crash of an Embraer EMB-120 Brasilía in Moscow

Date & Time: Jul 31, 2015 at 1810 LT
Type of aircraft:
Operator:
Registration:
VQ-BBX
Survivors:
Yes
Schedule:
Ulyanovsk - Moscow
MSN:
120-205
YOM:
1990
Flight number:
7R226
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Ulyanovsk, the crew started the descent to Moscow-Domodedovo Airport. While following the approach checklist, the crew realized that the nose gear failed to deploy and remained stuck in its wheel well. Several attempts to lower the gear manually failed and the crew eventually decided to carry out a nose gear-up landing on runway 32L. After a holding circuit of about 45 minutes, the aircraft landed then slid on its nose for few dozen metres before coming to rest. All 31 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of an ATR72-212 in Yangon

Date & Time: Jul 24, 2015 at 1854 LT
Type of aircraft:
Operator:
Registration:
XY-AIH
Survivors:
Yes
Schedule:
Mandalay – Yangon
MSN:
469
YOM:
1995
Flight number:
JAB424
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6603
Captain / Total hours on type:
513.00
Copilot / Total flying hours:
2650
Copilot / Total hours on type:
2650
Aircraft flight hours:
40827
Circumstances:
The route of the aircraft on that day was MDL- MYT- PBU- MYT- MDL- RGN. From Mandalay (MDL) on the way back to Yangon International Airport, the plane took off at 17:20.On the way the weather was not significant. For weather reason, seat belt sign was turned on the way to Yangon International Airport only one time. From Mandalay Airport up to landing phase to Yangon International Airport, first officer took control of the aircraft. At 1730 visibility was 6Km as per ATC verbal information. About 4 Km to Mingaladon Tower, clearance was obtained "Air Bagan 424 ,wind calm ,runway 21,clear to land, caution landing Runway wet, after landed vacate via Charlie" At decision height (250ft), runway was insight, runway lightings were able to be seen so the aircraft continued though there was light rain. At about 50 ft, more rain was falling suddenly consequently visibility became poor. So the pilot took over control of the aircraft. A few seconds later the aircraft made hard landing and skidded and veered off the left side of the runway to the muddy strip, came to rest about 2800ft from the threshold and 75ft from the runway edge.
Probable cause:
Primary cause:
During the final landing phase, the pilot was reluctant to perform a go-around while the plane was unstable and of bounce landing in low visibility condition.
Contributing factors:
a) The visibility was very low and the runway centerline lightings were not able to be seen intermittently.
b) The runway was wet and it was raining heavily.
c) The pilot in command took over the control of the plane from the copilot (14) seconds just before the first impact.
Final Report:

Crash of a Cessna 207A Skywagon near Point Howard: 1 killed

Date & Time: Jul 17, 2015 at 1318 LT
Operator:
Registration:
N62AK
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Juneau – Hoonah
MSN:
207-0780
YOM:
1984
Flight number:
K5202
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
845
Captain / Total hours on type:
48.00
Aircraft flight hours:
26613
Circumstances:
The company flight coordinator on duty when the pilot got her "duty-on" briefing reported that, during the "duty-on" briefing, he informed the commercial pilot that most flights to the intended destination had been cancelled in the morning due to poor weather conditions and that one pilot had turned around due to weather. No record was found indicating that the pilot used the company computer to review weather information before the flight nor that she had received or retrieved any weather information before the flight. If she had obtained weather information, she would have seen that the weather was marginal visual flight rules to instrument flight rules conditions, which might have affected her decision to initiate the flight. The pilot subsequently departed for the scheduled commuter flight with four passengers on board; the flight was expected to be 20 minutes long. Review of automatic dependent surveillance-broadcast data transmitted by the airplane showed that the airplane's flight track was farther north than the typical track for the destination and that the airplane did not turn south toward the destination after crossing the channel. Data from an on board multi-function display showed that, as the airplane approached mountainous terrain on the west side of the channel, the airplane made a series of erratic pitch-and-roll maneuvers before it impacted trees and terrain. Post-accident examination of the airframe and engine revealed no mechanical malfunctions or anomalies that would have precluded normal operation. One of the passengers reported that, after takeoff, the turbulence was "heavy," and there were layers of fog and clouds and some rain. Based on the weather reports, the passenger statement regarding the weather, and the flight's erratic movement just before impact, it is likely that the flight encountered instrument meteorological conditions as it approached the mountainous terrain and that the pilot then lost situational awareness and flew into trees and terrain. According to the company's General Operations Manual (GOM), operational control was delegated to the flight coordinator for the accident flight, and the flight coordinator and pilot-in-command (PIC) were jointly responsible for preflight planning, flight delay, and flight release, which included completing the flight risk assessment (FRA) process. This process required the PIC to fill out an FRA form and provide it to the flight coordinator before flight. However, the pilot did not fill out the form. The GOM stated that one of the roles of the flight dispatcher (also referred to as "flight coordinator") was to assist the pilot in flight preparation by gathering and disseminating pertinent information regarding weather and any information deemed necessary for the safety of flight. It also stated that the dispatcher was to assist the PIC as necessary to ensure that all items required for flight preparation were accomplished before each flight. However, the flight coordinator did not discuss all the risks and weather conditions associated with the flight with the pilot, which was contrary to the GOM. When the flight coordinator who was on duty at the time the airplane was ready to depart did not receive a completed FRA, he did not stop the flight from departing, which was contrary to company policy. By not completing an FRA, it is likely the total risks associated with the accident flight were not adequately assessed. Neither the pilot nor the flight coordinator should have allowed the flight to be released without having completed an FRA form, which led to a loss of operational control and the failure to do so likely contributed to the accident. Interviews with company personnel and a review of a sampling of FRA forms revealed that company personnel, including the flight coordinators, lacked a fundamental knowledge of operational control theory and practice and operational practices (or lack thereof), which led to a loss of operational control for the accident flight. The company provided no formal flight coordinator training nor was a formal training program required. All of the company's qualified flight coordinators were delegated operational control and, thus, were required by 14 Code of Federal Regulations Section 119.69 to be qualified through training, experience, and expertise and to fully understand aviation safety standards and safe operating practice with respect to the company's operation and its GOM. However, the company had no formal method of documenting these requirements; therefore, it lacked a method of determining its flight coordinators' qualifications. In post-accident interviews, the previous Federal Aviation Administration (FAA) principal operations inspector (POI), who became the frontline manager over the certificate, stated that the company used the minimum regulatory standard when it came to ceiling and visibility requirements and that the company did not have any company minimums in place. He further stated that a cloud ceiling of 500 ft and 2 miles visibility would not allow for power-off glide to land even though the company was required to meet this regulation. When asked if he believed the practice of allowing the pilot to decide when to fly was adequate, he said it was not and there should have been route altitudes. However, no action was taken to change SeaPort's operations. The POI at the time of the accident stated that she was also aware that the company was operating contrary to federal regulatory standards for gliding distance to shore. A review of FAA surveillance activities of the company revealed that the POI provided surveillance of the company following the accident, including an operational control inspection, and noted deficiencies with the company's operational procedures; however, the FAA did not hold the company accountable for correcting the identified operational deficiencies. If the FAA had conducted an investigation or initiated an enforcement action pertaining to the company's apparent disregard of the regulatory standard for maintaining glide distance before the accident similar to the inspection conducted following the accident, it is plausible the flight would not have departed or continued when glide distance could not be maintained. The FAA's failure to ensure that the company corrected these deficiencies likely contributed to this accident which resulted, in part, from the company's failure to comply with its GOM and applicable federal regulations, including required glide distance to shore. The company was the holder of a Medallion Shield until they voluntarily suspended the Shield status but retained the "Star" status and continued advertising as a Shield carrier. Medallion stated in an email "With this process of voluntarily suspension, there will be no official communication to the FAA…" Given that Medallion advertises that along with the Shield comes recognition by the FAA as an operator who incorporates higher standards of safety, it seems contrary to safety that they would withhold information pertaining to a suspension of that status.
Probable cause:
The pilot's decision to initiate and continue visual flight into instrument meteorological conditions, which resulted in a loss of situational awareness and controlled flight into terrain.
Contributing to the accident were the company's failure to follow its operational control and flight release procedures and its inadequate training and oversight of operational control
personnel. Also contributing to the accident was the Federal Aviation Administration's failure to hold the company accountable for correcting known regulatory deficiencies and ensuring that it complied with its operational control procedures.
Final Report:

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: