Crash of a Beechcraft 1900D in Beni

Date & Time: Sep 28, 2016 at 1230 LT
Type of aircraft:
Operator:
Registration:
ZS-PZE
Survivors:
Yes
Schedule:
Goma - Beni
MSN:
UE-32
YOM:
1992
Flight number:
UNO830
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4728
Captain / Total hours on type:
921.00
Copilot / Total flying hours:
2258
Copilot / Total hours on type:
251
Aircraft flight hours:
21498
Aircraft flight cycles:
30564
Circumstances:
The twin engine aircraft departed Goma on a regular schedule flight (service UNO830) to Beni, carrying eight passengers and two pilots on behalf of the Monusco, the United Nations Organization Stabilization Mission in the Democratic Republic of Congo. On approach to Beni-Mavivi Airport, the crew completed the approach checklist and elected to configure the aircraft but realized that the undercarriage would not extend. After the circuit breaker was reset, the crew was able to lower the landing gear manually and continued the approach with no reporting to ATC. After touchdown on runway 11, the aircraft rolled for about 450 metres when the right main gear collapsed. Out of control the aircraft veered off runway to the right, slid in a grassy area, crossed a ditch and came to rest near the apron. All 10 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The following factors were identified:
- The ovality due to the wear of the junction point of the arm (270) with the actuator (15) over time to the point that it finally broke and released the actuator from the whole undercarriage system.
- Overheating of the time/delay relay caused the circuit breaker to trip.
- The ovality created by the job(65) at the junction of the arm(270) to the actuator(15) eventually thinned and broke off the actuator.
Final Report:

Crash of a BAe 4101 Jetstream 41 in Siddharthanagar

Date & Time: Sep 24, 2016 at 1656 LT
Type of aircraft:
Operator:
Registration:
9N-AIB
Survivors:
Yes
Schedule:
Kathmandu – Siddharthanagar
MSN:
41017
YOM:
1993
Flight number:
YT893
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
29
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Siddharthanagar-Gautam Buddha Airport was completed in good weather conditions with a wind from the southeast at 4 knots and a 8 km visibility. After touchdown on runway 28, the twin engine aircraft was unable to stop within the remaining distance. It overran, lost its undercarriage and came to rest in bushes, some 110 metres past the runway end. All 32 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Cessna 208B Grand Caravan in Russian Mission: 3 killed

Date & Time: Aug 31, 2016 at 1001 LT
Type of aircraft:
Operator:
Registration:
N752RV
Flight Phase:
Survivors:
No
Schedule:
Russian Mission – Marshall
MSN:
208B-5088
YOM:
2014
Flight number:
HAG3190
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
18810
Captain / Total hours on type:
12808.00
Aircraft flight hours:
3559
Circumstances:
The Cessna had departed about 3 minutes prior on a scheduled passenger flight and the Piper was en route to a remote hunting camp when the two airplanes collided at an altitude about 1,760 ft mean sea level over a remote area in day, visual meteorological conditions. The airline transport pilot and two passengers onboard the Cessna and the commercial pilot and the passenger onboard the Piper were fatally injured; both airplanes were destroyed. Post accident examination revealed signatures consistent with the Cessna's outboard left wing initially impacting the Piper's right wing forward strut while in level cruise flight. Examination revealed no mechanical malfunctions or anomalies that would have precluded normal operation of either airplane. Neither pilot was in communication with an air traffic control facility and they were not required to be. A performance and visibility study indicated that each airplane would have remained a relatively small, slow-moving object in the other pilot's window (their fuselages spanning less than 0.5° of the field of view, equivalent to the diameter of a penny viewed from about 7 ft away) until about 10 seconds before the collision, at which time it would have appeared to grow in size suddenly (the "blossom" effect). From about 2 minutes before the collision, neither airplane would have been obscured from the other airplane pilot's (nominal) field of view by cockpit structure, although the Cessna would have appeared close to the bottom of the Piper's right wing and near the forward edge of its forward wing strut. The Cessna was Automatic Dependent Surveillance-Broadcast (ADS-B) Out equipped; the Piper was not ADS-B equipped, and neither airplane was equipped with any cockpit display of traffic information (CDTI). CDTI data would have presented visual information regarding the potential conflict to both pilots beginning about 2 minutes 39 seconds and auditory information beginning about 39 seconds before the collision, providing adequate time for the pilots to react. The see-and-avoid concept requires a pilot to look through the cockpit windows, identify other aircraft, decide if any aircraft are collision threats, and, if necessary, take the appropriate action to avert a collision. There are inherent limitations of this concept, including limitations of the human visual and information processing systems, pilot tasks that compete with the requirement to scan for traffic, the limited field of view from the cockpit, and environmental factors that could diminish the visibility of other aircraft. Given the remote area in which the airplanes were operating, it is likely that the pilots had relaxed their vigilance in looking for traffic. The circumstances of this accident underscore the difficultly in seeing airborne traffic by pilots; the foundation of the "see and avoid" concept in VMC, even when the cockpit visibility offers opportunities to do so, and particularly when the pilots have no warning of traffic in the vicinity. Due to the level of trauma sustained to the Cessna pilot, the autopsy was inconclusive for the presence of natural disease. It was undetermined if natural disease could have presented a significant hazard to flight safety.
Probable cause:
The failure of both pilots to see and avoid each other while in level cruise flight, which resulted in a midair collision.
Final Report:

Crash of a Boeing 777-31H in Dubai

Date & Time: Aug 3, 2016 at 1238 LT
Type of aircraft:
Operator:
Registration:
A6-EMW
Survivors:
Yes
Schedule:
Thiruvananthapuram - Dubai
MSN:
32700/434
YOM:
2003
Flight number:
EK521
Location:
Region:
Crew on board:
18
Crew fatalities:
Pax on board:
282
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7457
Captain / Total hours on type:
5123.00
Copilot / Total flying hours:
7957
Copilot / Total hours on type:
1292
Aircraft flight hours:
58169
Aircraft flight cycles:
13620
Circumstances:
On 3 August 2016, an Emirates Boeing 777-31H Aircraft, registration A6-EMW, operating a scheduled passenger flight UAE521, departed Trivandrum International Airport (VOTV), India, at 0506 UTC for a 3 hour 30 minute flight to Dubai International Airport (OMDB), the United Arab Emirates, with 282 passengers, 2 flight crew and 16 cabin crew members on board. The Commander attempted to perform a tailwind manual landing during an automatic terminal information service (ATIS) forecasted moderate windshear warning affecting all runways at OMDB. The tailwind was within the operational limitations of the Aircraft. During the landing on runway 12L at OMDB the Commander, who was the pilot flying, decided to fly a go-around, as he was unable to land the Aircraft within the runway touchdown zone. The go-around decision was based on the perception that the Aircraft would not land due to thermals and not due to a windshear encounter. For this reason, the Commander elected to fly a normal go-around and not the windshear escape maneuver. The flight crew initiated the flight crew operations manual (FCOM) Go-around and Missed Approach Procedure and the Commander pushed the TO/GA switch. As designed, because the Aircraft had touched down, the TO/GA switches became inhibited and had no effect on the autothrottle (A/T). The flight crew stated that they were not aware of the touchdown that lasted for six seconds. After becoming airborne during the go-around attempt, the Aircraft climbed to a height of 85 ft radio altitude above the runway surface. The flight crew did not observe that both thrust levers had remained at the idle position and that the engine thrust remained at idle. The Aircraft quickly sank towards the runway as the airspeed was insufficient to support the climb. As the Aircraft lost height and speed, the Commander initiated the windshear escape maneuver procedure and rapidly advanced both thrust levers. This action was too late to avoid the impact with runway 12L. Eighteen seconds after the initiation of the go-around the Aircraft impacted the runway at 0837:38 UTC and slid on its lower fuselage along the runway surface for approximately 32 seconds covering a distance of approximately 800 meters before coming to rest adjacent to taxiway Mike 13. The Aircraft remained intact during its movement along the runway protecting the occupants however, several fuselage mounted components and the No.2 engine/pylon assembly separated from the Aircraft. During the evacuation, several passenger door escape slides became unusable. Many passengers evacuated the Aircraft taking their carry-on baggage with them. Except for the Commander and the senior cabin crew member who evacuated after the center wing tank explosion, all of the other occupants evacuated via the operational escape slides in approximately 6 minutes and 40 seconds. Twenty-one passengers, one flight crewmember, and six cabin crew members sustained minor injuries. Four cabin crew members sustained serious injuries. Approximately 9 minutes and 40 seconds after the Aircraft came to rest, the center wing tank exploded which caused a large section of the right wing upper skin to be liberated. As the panel fell to the ground, it struck and fatally injured a firefighter. The Aircraft was eventually destroyed due to the subsequent fire. Following the Accident, the Operator (Emirates), the General Civil Aviation Authority (GCAA), Dubai Airports and Dubai Air Navigation Services (‘dans’) implemented several safety actions. In this Final Report, the AAIS issues safety recommendations addressed to the Operator, the GCAA, The Boeing Company, the Federal Aviation Administration (FAA), Dubai Airports, ‘dans’, and the International Civil Aviation Organization (ICAO).
Probable cause:
The Air Accident Investigation Sector determines that the causes of the Accident are:
(a) During the attempted go-around, except for the last three seconds prior to impact, both engine thrust levers, and therefore engine thrust, remained at idle. Consequently, the Aircraft’s energy state was insufficient to sustain flight.
(b) The flight crew did not effectively scan and monitor the primary flight instrumentation parameters during the landing and the attempted go-around.
(c) The flight crew were unaware that the autothrottle (A/T) had not responded to move the engine thrust levers to the TO/GA position after the Commander pushed the TO/GA switch at the initiation of the FCOM Go-around and Missed Approach Procedure.
(d) The flight crew did not take corrective action to increase engine thrust because they omitted the engine thrust verification steps of the FCOM Go-around and Missed Approach Procedure.
The Investigation determines that the following were contributory factors to the Accident:
(a) The flight crew were unable to land the Aircraft within the touchdown zone during the attempted tailwind landing because of an early flare initiation, and increased airspeed due to a shift in wind direction, which took place approximately 650 m beyond the runway threshold.
(b) When the Commander decided to fly a go-around, his perception was that the Aircraft was still airborne. In pushing the TO/GA switch, he expected that the autothrottle (A/T) would respond and automatically manage the engine thrust during the go-around.
(c) Based on the flight crew’s inaccurate situation awareness of the Aircraft state, and situational stress related to the increased workload involved in flying the go-around maneuver, they were unaware that the Aircraft’s main gear had touched down which caused the TO/GA switches to become inhibited. Additionally, the flight crew were unaware that the A/T mode had remained at ‘IDLE’ after the TO/GA switch was pushed.
(d) The flight crew reliance on automation and lack of training in flying go-arounds from close to the runway surface and with the TO/GA switches inhibited, significantly affected the flight crew performance in a critical flight situation which was different to that experienced by them during their simulated training flights.
(e) The flight crew did not monitor the flight mode annunciations (FMA) changes after the TO/GA switch was pushed because:
1. According to the Operator’s procedure, as per FCOM Flight Mode Annunciations (FMA), FMA changes are not required to be announced for landing when the aircraft is below 200 ft;
2. Callouts of FMA changes were not included in the Operator’s FCOM Go-Around and Missed Approach Procedures.
3. Callouts of FMA changes were not included in the Operator’s FCTM Go-Around and Missed Approach training.
(f) The Operator’s OM-A policy required the use of the A/T for engine thrust management for all phases of flight. This policy did not consider pilot actions that would be necessary during a go-around initiated while the A/T was armed and active and the TO/GA switches were inhibited.
(g) The FCOM Go-Around and Missed Approach Procedure did not contain steps for verbal verification callouts of engine thrust state.
(h) The Aircraft systems, as designed, did not alert the flight crew that the TO/GA switches were inhibited at the time when the Commander pushed the TO/GA switch with the A/T armed and active.
(i) The Aircraft systems, as designed, did not alert the flight crew to the inconsistency between the Aircraft configuration and the thrust setting necessary to perform a successful go-around.
(j) Air traffic control did not pass essential information about windshear reported by a preceding landing flight crew and that two flights performed go-arounds after passing over the runway threshold. The flight crew decision-making process, during the approach and landing, was deprived of this critical information.
(k) The modification of the go-around procedure by air traffic control four seconds after the Aircraft became airborne coincided with the landing gear selection to the ‘up’ position. This added to the flight crew workload as they attentively listened and the Copilot responded to the air traffic control instruction which required a change of missed approach altitude from 3,000 ft to 4,000 ft to be set. The flight crews’ concentration on their primary task of flying the Aircraft and monitoring was momentarily affected as both the FMA verification and the flight director status were missed.
Final Report:

Crash of a Cessna 208B Grand Caravan EX off Jinshan: 5 killed

Date & Time: Jul 20, 2016 at 1220 LT
Type of aircraft:
Registration:
B-10FW
Flight Phase:
Survivors:
Yes
MSN:
208B-5222
YOM:
2015
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
While taking off from the bay off Jinshan (south of Shanghai), the single engine aircraft collided with a concrete bridge and crashed in the sea. One pilot and four passengers were killed while five other occupants were injured. The seaplane C208 EX version was destroyed. It is believed that the crew misjudged the distance between the departure point and the bridge as the collision occurred just after rotation while attempted a steep climb.

Crash of a BAe 146-300 in Khark

Date & Time: Jun 19, 2016 at 1335 LT
Type of aircraft:
Operator:
Registration:
EP-MOF
Survivors:
Yes
Schedule:
Ahwaz – Khark
MSN:
E3149
YOM:
1989
Flight number:
IRM4525
Location:
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
79
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5494
Captain / Total hours on type:
1270.00
Copilot / Total flying hours:
300
Copilot / Total hours on type:
110
Circumstances:
On June 19, 2016, Mahan Air flight IRM 4525 was a scheduled passenger flight which took off from Ahwaz Airport at 1257 LMT (0827 UTC) to destination and landed at Khark Island Airport at 1335 LMT (0905 UTC). After delivery of the flight from BUZ approach to Khark tower, the flight was cleared to land on RWY 31 via visual approach. At 10 NM on final the pilot has asked weather information of the destination so, the captain requested to perform a visual approach for RWY 13. Finally the pilot in command accomplished an un-stabilized approach and landed on the runway after passing long distance of the Runway. Regarding to the length of the runway (7,657 feet) the aircraft overran the end of runway and made runway excursion on runway 13 and came to rest on the unpaved surface after 54 meters past the runway end. The nose landing gear strut has broken and collapsed. The captain instructed the cabin crew to evacuate the aircraft. No unusual occurrences were noticed during departure, en-route and descent.
Probable cause:
The main cause of this accident is wrong behavior of the pilot which descripted as:
- Decision to make a landing on short field RWY 13 with tailwind.
- Un stabilized landing against on normal flight profile
- Weak, obviously, CRM in cockpit.
- Poor judgment and not accomplishing a go around while performing a unstabilized approach.
- Improper calculating of landing speed without focusing on the tailwind component
Contributing factors:
- Anti-skid failures of RH landing gear causing prolong landing distance.
- Instantaneous variable wind condition on aerodrome traffic pattern.
- Late activating of airbrakes and spoilers (especially airbrakes) with tailwind cause to increase the landing roll distance.
Final Report:

Crash of an Airbus A320-232 in the Mediterranean Sea: 66 killed

Date & Time: May 19, 2016 at 0229 LT
Type of aircraft:
Operator:
Registration:
SU-GCC
Flight Phase:
Survivors:
No
Schedule:
Paris – Cairo
MSN:
2088
YOM:
2003
Flight number:
MS804
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
56
Pax fatalities:
Other fatalities:
Total fatalities:
66
Captain / Total flying hours:
6275
Captain / Total hours on type:
2101.00
Copilot / Total flying hours:
2675
Aircraft flight hours:
48000
Circumstances:
The aircraft departed Paris-Roissy-Charles de Gaulle Airport at 2321LT on May 18 on an international schedule flight to Cairo. carrying 56 passengers and 10 crew members. The crew maintained radio contacts with the Greek ATC and was transferred to the Egyptian ATC but failed to respond. Two minutes after the airplane left the Greek Airspace, the aircraft descended from FL370 to FL220 in few seconds, apparently making a first turn to the left and then a 360 turn to the right before disappearing from the radar screen at 0229LT while at an altitude of 10'000 feet. It is believed that the aircraft crashed in the Mediterranean sea about 200 km north of Egyptian coast. The crew did not send any mayday message, thereby all assumptions remains open. It appears that some various debris such as luggage were found on May 20 about 290-300 km north of Alexandria. Two days after the accident, it is confirmed that ACARS messages reported smoke on board, apparently in the lavatory and also in a technical compartment located under the cockpit area. Above that, several technical issues were reported by the ACARS system. The CVR has been recovered on June 16, 2016, and the DFDR a day later. As both recorder systems are badly damaged, they will need to be repaired before analyzing any datas. On December 15, 2016, investigators reported that traces of explosives were found on several victims. Egyptian Authorities determined that there had been a malicious act. The formal investigation per ICAO Annex 13 was stopped and further investigation fell within the sole jurisdiction of the judicial authorities. Contradicting the Egyptian finding, the French BEA considered that the most likely hypothesis was that a fire broke out in the cockpit while the aircraft was flying at its cruise altitude and that the fire spread rapidly resulting in the loss of control of the aircraft.
Probable cause:
It was determined that the accident was the consequence of an in-flight fire in the cockpit but investigations were unable to establish the exact origin of the fire. Following the fire that probably resulted from an oxygen leak from the copilot's quick-fit mask system, both pilots left the cockpit in a hurry and were apparently unable to find and use the fire extinguisher. To this determining element, three possible contributory factors have been identified: a blanket charged with static electricity requested by the captain to sleep; fatty substances being part of the meal served to the pilots, and a high probability of a lit cigarette or a cigarette butt burning in an ashtray while the crew smoked regularly in the cockpit. The experts also noted unprofessional behavior by the flight crew who listened to music, made multiple comings and goings in the cockpit as well as a lack of attention about flight monitoring procedures.

Crash of a Fokker 50 in Catania

Date & Time: Apr 30, 2016 at 1135 LT
Type of aircraft:
Operator:
Registration:
SE-LEZ
Survivors:
Yes
Schedule:
Rimini – Catania
MSN:
20128
YOM:
1988
Flight number:
RVL233
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6850
Captain / Total hours on type:
781.00
Copilot / Total flying hours:
2680
Copilot / Total hours on type:
10
Circumstances:
On April 30, 2016, the aircraft Fokker F27 MK50 registration marks SE-LEZ, operating Air Vallee flight number RVL233, took off from Rimini airport at 06.48 hrs with 18 passengers and 3 crew on board. During the final approach to Catania airport, with the aircraft stabilized on ILS Z RWY 08, the crew noticed that the right and left main landing gear lights were green but the nose landing gear light was amber. The crew informed the ATS (Catania APP) that they were in contact with the problem and informed them of their intention to continue the approach to perform a low pass on the runway followed by a standard missed approach procedure, in order to request a visual verification from the control tower of the actual extension of the nose gear. During the low passage, the control tower informed the crew that the nose gear was not extended despite the opening of the nose gear compartment. After the passage, all lights, including the amber light of the nose landing gear, went off. The aircraft proceeded to the INDAX point to perform a holding at an altitude of 3000 feet as agreed with ATS during which the crew applied the abnormal procedures for nose gear unsafe down after selection and alternate down procedures. Both procedures were unsuccessful and the crew declared an "emergency" informing ATS of their intention to perform a final maneuver (leveled 2G turn). The captain of the flight, who had been PNF up to that moment, took the controls as PF and executed the turn: also in this case without any positive outcome. The crew informed ATS of the situation, stating the number of passengers, the amount of fuel on board and the absence of dangerous goods. The crew decided to follow a VOR procedure for RWY26 followed by a visual approach in order to make a last low passage to check the condition of the nose gear. After this second missed approach, the aircraft was instructed to perform an ILS procedure for RWY 08. Landing took place at 09:34 hrs with the main gear properly extracted and locked, the nose gear in "up" position and the doors open. The following is a sequence of pictures taken from a video of the accident, acquired by ANSV through the Catania airport operator, in which the aircraft is seen landing with the nose landing gear not extended and touching the ground only when it reached the speed necessary to sustain it in the absence of nose landing gear support. After completion of the landing run, with the aircraft remaining in the middle of the runway, the engines were shut down and passengers and crew disembarked without further incident. Some of the passengers were transferred to the airport emergency room and subsequently some of them were sent to hospital for further examination; no passenger was reported to have sustained injuries as a result of the event.
Probable cause:
The accident was caused by the failure of the nose landing gear (nose gear up) due to over-extension of the shock absorber which caused interference between the tires and the NLG compartment and locked the NLG in a retracted position. The over-extension was caused by the incorrect installation of some internal components of the shock absorber during the replacement of the internal seals the day before the accident.
The following factors contributed significantly to the improper activity conducted at maintenance:
- the insufficient experience of technical personnel in carrying out the maintenance tasks conducted on the NLG;
- the lack of controls on the operations carried out, deemed unnecessary by the CAMO engineering department;
- the lack of definition of roles and tasks during the planning phase of the maintenance work;
- the operational pressure on maintenance personnel, arising from the need to conclude maintenance operations quickly in order not to penalize the management of the aircraft;
- the insufficient clarity and lack of sensitive information in the maintenance tasks and related figures contained in the AMM, regarding the replacement of internal shock absorber seals, subsequently made clearer by the manufacturer;
- the reported black and white printing of the applied AMM procedures, which could have made the warnings in the manual barely legible.
Final Report:

Crash of an Embraer ERJ-190-100AR in Cuenca

Date & Time: Apr 28, 2016 at 0751 LT
Type of aircraft:
Operator:
Registration:
HC-COX
Survivors:
Yes
Schedule:
Quito – Cuenca
MSN:
190-00372
YOM:
2010
Flight number:
EQ173
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
87
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
17523
Captain / Total hours on type:
2113.00
Copilot / Total flying hours:
3545
Copilot / Total hours on type:
2077
Aircraft flight hours:
11569
Aircraft flight cycles:
9707
Circumstances:
Following en uneventful flight from Quito, the crew initiated the descent to Cuenca-Mariscal La Mar Airport Runway 23. Weather conditions at destination were poor with rain falls and a contaminated runway. The pilot-in-command continued the approach below the glide and the aircraft passed over the runway threshold at a height of 37 feet instead the recommended 50 feet. The airplane landed 277 metres past the runway threshold at a speed of 127 knots and the crew activated the spoilers and the reverse thrust systems. Due to poor braking action, the captain activated the autobrake system, without success. As the aircraft could not be stopped within the remaining distance, the captain intentionally turn to the right when the aircraft ground looped, overran and came to rest in a grassy area. All 93 occupants were rescued, among them two passengers were slightly injured. The aircraft was damaged beyond repair.
Probable cause:
The following findings were identified:
- The condition of the runway at Cuenca airport, which at the time of the plane's landing was contaminated with water and slippery.
- The landing was made after a non-stabilized approach with a tailwind.
- During seven seconds, the crew continued the approach with an excessive rate of descent of 1,186 feet, 186 feet above the limit of 1,000 feet.
- The non-application of the Maximum Performance Landing procedure recommended by the aircraft manufacturer for landing on contaminated runways.
- The dispatch of the flight with 1,500 kg of fuel more than the amount of fuel usually used for this flight.
- Omission of the runway length calculation necessary to perform the landing using the braking efficiency information.
- The crew's decision to make the final approach with three red and one white lights, using the PAPI system, induced by the information in the Terminal Information document issued by the company, which authorized this procedure.
- The use of confusing terminology in the Terminal Information document, which used terms applicable to the Airbus fleet, instead of Embraer's.
- The crew's decision not to perform the thwarted approach maneuver after the maximum allowable vertical speed was exceeded and visibility was apparently limited after the minima were exceeded.
- Incorrect use of aircraft braking aids, in this case reverse braking aids
- The application of the emergency brake that inhibits the antiskid system.
- Lack of implementation of adequate management of crew resources, particularly within the cockpit.
- Lack of training in the use of tables for track distance calculation.
- In reference to landing conditions, the aircraft needed a runway length of 2,122 metres while the available distance was 1,900 metres.
Final Report:

Crash of a Beechcraft 1900D in Gander

Date & Time: Apr 20, 2016 at 2130 LT
Type of aircraft:
Operator:
Registration:
C-FEVA
Survivors:
Yes
Schedule:
Goose Bay – Gander
MSN:
UE-126
YOM:
1994
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2381
Captain / Total hours on type:
1031.00
Copilot / Total flying hours:
1504
Copilot / Total hours on type:
174
Aircraft flight hours:
32959
Circumstances:
The Exploits Valley Air Services Beechcraft 1900D (registration C-FEVA, serial number UE-126), operating as Air Canada Express flight EV7804, was on a scheduled passenger flight from Goose Bay International Airport, Newfoundland and Labrador, to Gander International Airport, Newfoundland and Labrador. At 2130 Newfoundland Daylight Time, while landing on Runway 03, the aircraft touched down right of the centreline and almost immediately veered to the right. The nosewheel struck a compacted snow windrow on the runway, causing the nose landing gear to collapse. As the aircraft’s nose began to drop, the propeller blades struck the snow and runway surface. All of the left-side propeller blades and 3 of the right-side propeller blades separated at the blade root. A portion of a blade from the right-side propeller penetrated the cabin wall. The aircraft slid to a stop on the runway. All occupants on board — 14 passengers and 2 crew members — were evacuated. Three passengers sustained minor injuries. The aircraft was substantially damaged. There was no post-impact fire. There were insufficient forward impact forces to automatically activate the 121.5 MHz emergency locator transmitter. The accident occurred during the hours of darkness.
Probable cause:
Findings as to causes and contributing factors:
1. Neither pilot had considered that the combination of landing at night, in reduced visibility, with a crosswind and blowing snow, on a runway with no centreline lighting, was a hazard that may create additional risks.
2. The blowing snow made it difficult to identify the runway centreline markings, thereby reducing visual cues available to the captain. This situation was exacerbated by the absence of centreline lighting and a possible visual illusion caused by blowing snow.
3. Due to the gusty crosswind conditions, the aircraft drifted to the right during the landing flare, which was not recognized by the crew.
4. It is likely that the captain had difficulty determining aircraft position during the landing flare.
5. The flight crew’s decision to continue with the landing was consistent with plan continuation bias.
6. During landing, the nosewheel struck the compacted snow windrow on the runway, causing the nose landing gear to collapse.

Findings as to risk:
1. If aircraft are not equipped with a 406 MHz-capable emergency locator transmitter, flight crews and passengers are at increased risk of injury or death following an accident because search-and-rescue assistance may be delayed.
2. If operators do not have defined crosswind limits, there is a risk that pilots may land in crosswinds that exceed their abilities, which could jeopardize the safety of flight.
3. If composite propeller blades contact objects and separate, and then strike or penetrate the cabin, there is a risk of injury or death to occupants seated in the propeller’s plane of rotation.
4. If modern crew resource management training is not a regulatory requirement, then it is less likely to be introduced by operators and, as a result, pilots may not be fully prepared to recognize and mitigate hazards encountered during flight.
5. If organizations do not use modern safety management practices and do not have a robust safety culture, then there is an increased risk that hazards will not be identified and mitigated.
6. When testing an emergency locator transmitter’s (ELT) automatic activation system, a sticking g-switch may go undetected if more than 1 football throw is necessary to activate the ELT. As a result, the ELT might not activate during an accident, and search-and-rescue assistance may be delayed, placing flight crews and passenger at an increased risk for injury or death.
Final Report: