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:

Crash of a Gulfstream GIII in Biggin Hill

Date & Time: Nov 24, 2014 at 2030 LT
Type of aircraft:
Operator:
Registration:
N103CD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Biggin Hill - Gander
MSN:
418
YOM:
1984
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4120
Captain / Total hours on type:
3650.00
Circumstances:
On 24 November 2014 the crew of Gulfstream III N103CD planned for a private flight from Biggin Hill Airport to Gander International Airport in Canada. The weather reported at the airport at 2020 hrs was wind ‘calm’, greater than 10 km visibility with fog patches, no significant cloud, temperature 5°C, dew point 4°C and QNH 1027 hPa. At 2024 hrs, the crew was cleared to taxi to Holding Point J1 for a departure from Runway 03. After the crew read back the taxi clearance, the controller transmitted: “we are giving low level fog patches on the airfield, general visibility in excess of 10 km but visibility not measured in the fog patches. it seems to be very low, very thin fog from the zero three threshold to approximately half way down the runway then it looks completely clear”. The crew acknowledged the information. At 2028 hrs, the aircraft was at the holding point and was cleared for takeoff by the controller. The aircraft taxied towards the runway from J1 but lined up with the runway edge lights, which were positioned 3 m to the right of the edge of the runway. The aircraft began its takeoff run at 2030 hrs, passing over paved surface for approximately 248 m before running onto grass which lay beyond. The commander, who was the handling pilot, closed the thrust levers to reject the takeoff when he realized what had happened and the aircraft came to a halt on the grass having suffered major structural damage. The crew shut down the engines but were unable to contact ATC on the radio to tell the controller what had happened. The co-pilot moved from the flight deck into the passenger cabin and saw that no one had been injured. He vacated the aircraft through the rear baggage compartment and then helped the commander, who was still inside, to open the main exit door. The commander and the five passengers used the main exit to vacate the aircraft. The controller saw that the aircraft had stopped but did not realize that it was not on the runway. He attempted to contact the crew on the radio but, when he saw the lights of the aircraft switch off, he activated the crash alarm, at 2032 hrs, declaring an aircraft ground incident. At 2034 hrs the airport fire service reached the aircraft and declared an aircraft accident, after which the airport emergency plan was activated.
Probable cause:
This was a private flight which could not depart in conditions of less than 400 m RVR. RVR cannot be measured at the threshold end of Runway 03 but the prevailing visibility was reported as being more than 10 km. The crew reported that there was moisture on the windscreen from the mist and they could see a “glow” around lights which were visible to them. They were also aware while taxiing that there was some patchy ground fog on the airfield. The ATC controller transmitted that visibility had not been measured in the fog patches but there seemed to be ‘very low, very thin fog from the zero three threshold to approximately half way down the runway’. With hindsight, this piece of information is significant but, at the time, the crew did not consider the fog to be widespread or thick; operating under FAR Part 91 in the United States, they were used to making their own judgments as to whether the visibility was suitable for a takeoff. However, after the aircraft came to a halt following its abortive takeoff attempt, the controller could only see the top of the fuselage and tail above the layer of fog. It is likely, therefore, that the visibility was worse than the crew appreciated at the time N103CD taxied from Holding Point J1. The route from J1 to the runway The information on the aerodrome chart used by the crew, and the source of information in the UK AIP, suggested that the aircraft would be required to taxi in a straight line from J1 to the runway and then make a right turn onto the runway heading. In fact, in order to taxi from J1 onto the runway, an aircraft must: taxi in a straight line; follow a curve to the right onto runway heading but still displaced to the right of the runway itself; turn left towards the runway; and then turn right again onto runway heading. The UK AIP states that there is no centreline lighting on Runway 03, and that the pavement width at the beginning of the runway is twice the normal runway width. It recognizes the potential for confusion and urges crews to ensure that they have lined up correctly. This information was not available to the crew on their aerodrome charts and both crew members believed that the runway had centreline lighting. Further, the light from those left-side runway edge lights covered in fog would have been scattered, making it harder for the crew to perceive them as a distinct line of lights. The situation is likely to have been made worse by the bright lights reflecting off the top of the fog layer, making the underlying runway lights even harder to see, or swamping them completely as shown in Figure 5. The CCTV images in Figure 5 show that peripheral lighting can interact with low fog layers to reduce the visibility of underlying aerodrome lighting. Current standards associated with apron lighting only address the minimum light levels required to make the areas safe and there are no standards relating to light spilling into other areas.
Human and environmental factors Five of the factors identified by the ATSB as being present in misaligned takeoffs were present in this accident:
1. It was dark.
2. It was potentially a confusing taxiway environment given that the aerodrome chart did not reflect the actual layout of the taxiways. Pilots had previously reported having difficulty when vacating the runway near the Runway 03 threshold because of a lack of taxiway lighting.
3. There was an additional paved area (the ORP) near the runway.
4. There was no runway centreline lighting and the runway edge lights before the displaced threshold were recessed.
5. There was reduced visibility.
It appeared that the information available to the crew caused them to develop an incorrect expectation of their route to the runway. Both crew members believed that the runway had centreline lighting and, when the first right turn almost lined the aircraft up with some lights, their incorrect expectation was reinforced and they believed that the aircraft was lined up correctly. Cues to the contrary, such as runway edge lights on the other side of the runway, or the fact that the first three lights ahead of the aircraft were red (indicating that they were edge lights before the displaced threshold), did not appear to have been strong enough to make the crew realize that they had lost situational awareness. Figure 8 indicates that the apparent intensity of the white left-side runway edge lights was significantly less than that of the right-side lights, when viewed from the position where the aircraft lined up. This, along with other visual issues relating to contrast and the fog, is a plausible explanation as to why they were not noticed by the crew. The aircraft began its takeoff roll from a location beyond the first red runway edge light and approximately 46 m short of the next light, as shown in Figure 1. Aircraft structure only obscures approximately the first 13 m of pavement ahead of pilots within a Gulfstream III aircraft and therefore these lights would not have been obscured by the aircraft. However, it is likely that the recessed nature of the red edge lights before the displaced threshold made them less compelling than the elevated white edge lights beyond, which would explain why their significance – that they could only have been runway edge lights – was not appreciated by the flight crew.
Final Report:

Crash of a Boeing 757-225 off Puerto Plata: 189 killed

Date & Time: Feb 6, 1996 at 2347 LT
Type of aircraft:
Operator:
Registration:
TC-GEN
Flight Phase:
Survivors:
No
Schedule:
Puerto Plata - Gander - Berlin - Frankfurt
MSN:
22206
YOM:
1983
Flight number:
KT301
Crew on board:
13
Crew fatalities:
Pax on board:
176
Pax fatalities:
Other fatalities:
Total fatalities:
189
Captain / Total flying hours:
24750
Captain / Total hours on type:
1875.00
Copilot / Total flying hours:
3500
Copilot / Total hours on type:
71
Aircraft flight hours:
29269
Aircraft flight cycles:
13499
Circumstances:
On behalf of Alas Nacionales, the aircraft was completing a charter flight from Puerto Plata to Frankfurt with intermediate stops in Gander and Berlin, carrying 176 Germans and 13 Turkish crew members. During the takeoff roll, at a speed of 80 knots, the captain noted that his air speed indicator (ASI) seemed to be incorrect while the copilot's ASI seemed to be correct. During initial climb, at an altitude of about 4,700 feet, the captain's ASI read 350 knots while the real speed was 220 knots. This resulted in an autopilot/autothrottle reaction to increase the pitch-up attitude and a power reduction in order to lower the airspeed. At that time the crew got 'Rudder ratio' and 'Mach airspeed' advisory warnings. Both pilots got confused when the copilot stated that his ASI read 200 knots decreasing while getting an excessive speed warning, followed by a stick shaker warning. This led the pilots to believe that both ASIs were unreliable. Finally realizing that they were losing speed and altitude they disconnected the autopilot. The autopilot, fed by the captain's faulty ASI, had reduced the speed close to the stall speed. Full thrust was then applied. At 23:47:17 an aural GPWS warning sounded and eight seconds later, the aircraft crashed in the ocean. All 189 occupants were killed.
Probable cause:
The crew's failure to recognize the activation of the stick shaker as a warning of an imminent stall, and the failure of the crew to execute the procedures for recovery from the onset of loss of control. Before the stick shaker warning activated, there was a confusion by the flight crew due to erroneous indications of relative speed increase and an overspeed warning. It is believed that the incorrect ASI readings was the consequence of an obstructed Pitot tube, maybe by mud and/or debris from a small insect that was introduced in the Pitot tube during the time the aircraft was on the ground. The aircraft was not flown for 20 days before the crash and was returned for service without a verification of the Pitot static system as recommended by Boeing.
Final Report:

Crash of a Boeing 727-247 in the Atlantic Ocean: 16 killed

Date & Time: Sep 11, 1990 at 1530 LT
Type of aircraft:
Operator:
Registration:
OB-1303
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Valetta – London – Reykjavik – Gander – Miami – Lima
MSN:
20266
YOM:
1969
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
16
Circumstances:
After being leased to Air Malta for few months, the aircraft was repatriated to Peru via London, Reykjavik, Gander and Miami. On the leg from Reykjavik to Gander, while at cruising altitude, the crew declared an emergency and elected to ditch the aircraft when contact was lost. Apparently, the aircraft crashed in the Atlantic Ocean about 290 km southeast from the Newfoundland coast. SAR operations were initiated but eventually abandoned few days later as no trace of the aircraft was found.
Probable cause:
Due to lack of evidences, the exact cause of the accident could not be determined. However, it is believed that the crew reported a low fuel warning.

Crash of a Douglas DC-8-63CF in Gander: 256 killed

Date & Time: Dec 12, 1985 at 0645 LT
Type of aircraft:
Operator:
Registration:
N950JW
Flight Phase:
Survivors:
No
Schedule:
Cairo – Cologne – Gander – Fort Campbell
MSN:
46058
YOM:
1969
Flight number:
MF1285R
Country:
Crew on board:
8
Crew fatalities:
Pax on board:
248
Pax fatalities:
Other fatalities:
Total fatalities:
256
Captain / Total flying hours:
7001
Captain / Total hours on type:
1081.00
Copilot / Total flying hours:
5549
Copilot / Total hours on type:
918
Aircraft flight hours:
50861
Circumstances:
On 11 December 1985, Arrow Air Flight MF1285R, a Douglas DC-8-63, U.S. registration N950JW, departed Cairo, Egypt on an international charter flight to Fort Campbell, Kentucky (Ky), U.S.A. via Cologne, Germany, and Gander, Newfoundland. On board were 8 crew members and 248 passengers. The flight was the return portion of the second in a series of three planned troop rotation flights originating at McChord Air Force Base (AFB), Washington, U.S.A. and terminating in Fort Campbell. The flight had been chartered by the Multinational Force and Observers (MFO) to transport troops, their personal effects, and some military equipment to and from peacekeeping duties in the Sinai Desert. All 248 passengers who departed Cairo on 11 December 1985 were members of 101st Airborne Division (United States Army), based in Fort Campbell. The flight departed Cairo at 2035 Greenwich Mean Time (GMT) and arrived at Cologne at 0121, 12 December 1985 for a planned technical stop. A complete crew change took place following which the flight departed for Gander at 0250. The flight arrived at Gander at 0904. Passengers were deplaned, the aircraft was refuelled, trash and waste water were removed, and catering supplies were boarded. The flight engineer was observed to conduct an external inspection of portions of the aircraft. The passengers then reboarded. Following engine start-up, the aircraft was taxied via taxiway "D" and runway 13 to runway 22 for departure. Take-off on runway 22 was begun from the intersection of runway 13 at 1015. The aircraft was observed to proceed down the runway and rotate in the vicinity of taxiway "A". Witnesses to the take-off reported that the aircraft gained little altitude after rotation and began to descend. Several witnesses, who were travelling on the Trans-Canada Highway approximately 900 feet beyond the departure end of runway 22, testified that the aircraft crossed the highway, which is at a lower elevation than the runway, at a very low altitude. Three described a yellow/orange glow emanating from the aircraft. Two of the witnesses testified that the glow was bright enough to illuminate the interior of the truck cabs they were driving. The third attributed the glow to the reflection of the runway approach lighting on the aircraft. Several witnesses observed the aircraft in a right bank as it crossed the Trans-Canada Highway. The pitch angle was also seen to increase, but the aircraft continued to descend until it struck downsloping terrain approximately 3,000 feet beyond the departure end of the runway. The aircraft was destroyed by impact forces and a severe fuel-fed fire. All 256 occupants on board sustained fatal injuries.
Probable cause:
The Canadian Aviation Safety Board was unable to determine the exact sequence of events which led to this accident. The Board believes, however, that the weight of evidence supports the conclusion that, shortly after lift-off, the aircraft experienced an increase in drag and reduction in lift which resulted in a stall at low altitude from which recovery was not possible. The most probable cause of the stall was determined to be ice contamination on the leading edge and upper surface of the wing. Other possible factors such as a loss of thrust from the number four engine and inappropriate take-off reference speeds may have compounded the effects of the contamination.
Final Report:

Crash of a Mitsubishi MU-2B-25 Marquise in Gander: 2 killed

Date & Time: Mar 24, 1974
Type of aircraft:
Registration:
N333MA
Flight Phase:
Flight Type:
Survivors:
No
MSN:
288
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Gander Airport, while in initial climb, the twin engine airplane encountered difficulties to gain height. It struck trees, stalled and crashed in flames in a wooded area. The aircraft was destroyed by a post crash fire and both pilots, en route to Europe, were killed.

Crash of a Cessna 340A in Gander: 1 killed

Date & Time: Mar 31, 1973 at 2350 LT
Type of aircraft:
Operator:
Registration:
N7691Q
Flight Type:
Survivors:
No
Schedule:
Wichita – Portland – Gander
MSN:
340A-0190
YOM:
1973
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole on board, was completing a delivery flight from Wichita to France via Portland and Gander. The approach to Gander was initiated by night and good weather conditions. On final, the pilot descended too low when the twin engine airplane struck trees and crashed few km short of runway threshold. The aircraft was destroyed and the pilot was killed. Still owned by Cessna Aircraft, the airplane was on its way to France to be delivered to its future operator Flo Air.
Probable cause:
Improper IFR operation on part of the pilot who misjudged distance and altitude on final approach. The following factors were reported:
- High obstructions,
- Visual conditions,
- Dark night,
- No visual reference.
Final Report:

Crash of an Ilyushin II-18D in Gander: 37 killed

Date & Time: Sep 5, 1967 at 0240 LT
Type of aircraft:
Operator:
Registration:
OK-WAI
Flight Phase:
Survivors:
Yes
Schedule:
Prague – Shannon – Gander – Havana
MSN:
187 0097 05
YOM:
1967
Flight number:
OK523
Country:
Crew on board:
8
Crew fatalities:
Pax on board:
61
Pax fatalities:
Other fatalities:
Total fatalities:
37
Captain / Total flying hours:
17303
Captain / Total hours on type:
5360.00
Copilot / Total flying hours:
10749
Copilot / Total hours on type:
1291
Aircraft flight hours:
766
Circumstances:
Flight 523 was a scheduled international flight from Prague, Czechoslovakia to Havana, Cuba, via Shannon, Ireland, and Gander, Newfoundland. It departed Prague at 1649 hours GMT on 4 September and proceeded to Shannon where it arrived at 2020 hours for a routine servicing stop. It departed Shannon at 2131 hours arriving at Gander at 0326 hours on 5 September following an uneventful flight. The crew which had flown the aircraft from Prague disembarked at Gander and was replaced by a crew which had been off duty in Gander from 3 September. At Gander the aircraft was serviced and refuelled under the supervision of the flight engineer of the outgoing flight. A flight plan to Havana was filed at about 0405 hours and at 0504 hours the aircraft began taxiing to the threshold of runway 14. It was cleared to take-off at 0508 hours. The length of the ground roll was normal, the undercarriage and flaps were retracted, but the angle of climb was abnormally shallow. At 0509 hours the flight advised the tower controller that the aircraft was airborne, the tower controller acknowledged the transmission and advised the flight to contact Air Traffic Control Centre on a frequency of 119.7 MHz. Whilst the radio operator was changing frequency the aircraft struck the ground about 4 000 feet beyond the end of the runway. The accident occurred at 0510 hours GMT. Debris scattered on 1,500 meters and 32 occupants were wounded while 37 others were killed, among them 4 crew members.
Probable cause:
Investigations were unable to determine the exact cause of the accident.
Final Report:

Crash of a Douglas C-47A-1-DK into the Trinity Bay: 2 killed

Date & Time: Mar 18, 1965 at 1810 LT
Operator:
Registration:
N4997E
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Miami – Gander – Santa Maria – Manila
MSN:
12191
YOM:
1943
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
30000
Captain / Total hours on type:
6000.00
Circumstances:
The aircraft has to be delivered to Air Manila in the Philippines and the crew departed Miami for Manila with intermediate stops in Gander and Santa Maria, Azores Islands. While cruising over Newfoundland, the crew was able to send a brief mayday message when the airplane went out of control and crashed into the Trinity Bay. The aircraft was lost and both pilots were killed.
Probable cause:
Loss of control following an emergency of an undetermined nature.
Final Report:

Crash of a Curtiss C-46A-15-CU Commando into the Atlantic Ocean: 3 killed

Date & Time: Dec 9, 1963
Type of aircraft:
Operator:
Registration:
N5160V
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Gander – Santa Maria
MSN:
26512
YOM:
1943
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The twin engine aircraft crashed in unknown circumstances into the Atlantic Ocean about 240 km northwest of the Azores Islands while on a flight from Gander to Santa Maria. All three crew members were killed.