Crash of an Embraer ERJ-145LR in Ottawa

Date & Time: Sep 4, 2011 at 1529 LT
Type of aircraft:
Operator:
Registration:
N840HK
Survivors:
Yes
Schedule:
Chicago - Ottawa
MSN:
145-341
YOM:
2001
Flight number:
UA3363
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
4000.00
Copilot / Total flying hours:
4800
Copilot / Total hours on type:
3800
Aircraft flight hours:
25655
Aircraft flight cycles:
23335
Circumstances:
At 1406, United Express Flight 3363 (LOF3363), operated by Trans States Airlines LLC (TSA), departed Chicago O’Hare International Airport, Chicago, United States. Before commencing the descent into Ottawa/Macdonald-Cartier International Airport (CYOW), Ontario, the flight crew obtained the automatic terminal information service (ATIS) information Yankee for CYOW issued at 1411. Based on the reported wind speed and direction, the flight crew calculated the approach speed (VAPP) to be 133 knots indicated airspeed (KIAS). Runway 25 was identified in ATIS information Yankee as the active runway. However, as a result of a previous overrun on Runway 07/25 in August 2010, TSA prohibited its flight crews from landing or taking off on Runway 07/25 when the surface is reported as damp or wet. Because rain showers were forecast for CYOW and Runway 32 was the longest runway, the flight crew decided at 1506 to carry out an instrument landing system (ILS) approach to Runway 32. At 1524, the CYOW terminal air traffic controller (ATC) advised the flight crew that it was starting to rain heavily at CYOW. About 2 minutes later, the aircraft intercepted the glideslope for the ILS to Runway 32. Final descent was initiated, the landing gear was extended, and the flaps were selected to 22°. Upon contacting the CYOW tower controller, the flight crew was advised that moderate rain had just started at the airport and the wind was reported as 310° magnetic (M) at 10 knots. The aircraft crossed the GREELY (YYR) final approach fix at 4.3 nautical miles (nm), slightly above the glideslope at 174 KIAS. About 1528, the aircraft passed through 1000 feet above ground level (agl) at 155 knots. Moments later, the flaps were selected to 45°. The airspeed at the time was approximately 145 KIAS. The tower controller advised the flight crew that the wind had changed to 320°M at 13 knots gusting to 20 knots. To compensate for the increased wind speed, the flight crew increased the VAPP to 140 KIAS. About 1 minute later, at 1529, the aircraft crossed the threshold of Runway 32 at about 45 feet agl, at an airspeed of 139 KIAS. As the aircraft crossed the runway threshold, the intensity of the rain increased, so the flight crew selected the windshield wipers to high. When the aircraft was about 20 feet agl, engine power was reduced and a flare was commenced. Just before touchdown, the aircraft encountered a downpour sufficient to obscure the crew’s view of the runway. Perceiving a sudden increase in descent rate, at approximately 5 feet agl, the captain applied maximum thrust on both engines. The master caution light illuminated, and a voice warning stated that the flaps were not in a take-off configuration. Maximum thrust was maintained for 7 seconds. The aircraft touched down smoothly 2700 feet beyond the threshold at 119 KIAS; the airspeed was increasing, and the aircraft became airborne again. The aircraft touched down a second time at 3037 feet beyond the threshold, with the airspeed increasing through 125 KIAS. Airspeed on touchdown peaked at 128 KIAS as the nosewheel was lowered to the ground, and then the thrust levers were retarded to flight idle. The outboard spoilers almost immediately deployed, and about 8 seconds later, the inboard spoilers deployed. The aircraft was about 20 feet right of the runway centreline when it touched down for the second time. Once the nosewheel was on the ground, the captain applied maximum brakes. The flight crew almost immediately noted that the aircraft began skidding. The captain then requested the first officer to apply maximum brakes as well. The aircraft continued to skid, and no significant brake pressure was recorded until about 14 seconds after the outboard spoilers deployed, when brake pressure suddenly increased to its maximum. During this time, the captain attempted to steer the aircraft back to the runway centreline. As the aircraft skidded down the runway, it began to yaw to the left. Full right rudder was applied, but was ineffective in correcting the left yaw. Sufficient water was present on the runway surface to cause the aircraft tires to send a spray of water, commonly known as a rooster tail, to a height of over 22 feet, trailing over 300 feet behind the aircraft. At some point during the landing roll, the captain partially applied the emergency/parking brake (EPB), and when no braking action was felt, the EPB was engaged further. With no perceivable deceleration being felt, the EPB was stowed. The aircraft continued to skid down the runway until about 7500 feet from the threshold, at which point it started skidding sideways along the runway. At 1530, the nosewheel exited the paved surface, 8120 feet from the threshold, at approximately 53 knots, on a heading of 271°M. The aircraft came to rest on a heading of 211°M, just off the left side of the paved surface. After coming to a stop, the flight crew carried out the emergency shutdown procedure as per the company Quick Reference Handbook (QRH), and consulted with the flight attendant on the status of everyone in the passenger cabin. The flight crew determined that there was no immediate threat and decided to hold the passengers on board. When the aircraft exited the runway surface, the tower activated the crash alarm. The CYOW airport rescue and firefighting (ARFF) services responded, and were on scene approximately 3 minutes after the activation of the crash alarm. Once ARFF personnel had conducted a thorough exterior check of the aircraft, they informed the flight crew that there was a fuel leak. The captain then called for an immediate evacuation of the aircraft. The passengers evacuated through the main cabin door, and moved to the runway as directed by the flight crew and ARFF personnel. The evacuation was initiated approximately 12 minutes after the aircraft came to a final stop. After the evacuation was complete, the firefighters sprayed foam around the aircraft where the fuel had leaked.
Probable cause:
Findings as to causes and contributing factors:
1. Heavy rainfall before and during the landing resulted in a 4–6 mm layer of water contaminating the runway.
2. The occurrence aircraft’s airspeed during final approach exceeded the company prescribed limits for stabilized approach criteria. As a result, the aircraft crossed the runway threshold at a higher than recommended VREF airspeed.
3. A go-around was not performed, as per standard operating procedures, when the aircraft’s speed was greater than 5 knots above the appropriate approach speed during the stabilized portion of the approach.
4. The application of engine thrust just before touchdown caused the aircraft to touch down 3037 feet from the threshold at a higher than recommended airspeed.
5. The combination of a less than firm landing and underinflated tires contributed to the aircraft hydroplaning.
6. The emergency/parking brake was applied during the landing roll, which disabled the anti-skid braking system and prolonged the skid.
7. The aircraft lost directional control as a result of hydroplaning and veered off the runway.

Findings as to risk:
1. The typical and frequently used technique for differential braking that pilots are trained to use may not be effective when anti-skid systems require different techniques.
2. If aircraft electrical power is applied with an active fuel leak, there is a risk that an electrical spark could ignite the fuel and start a fire.
3. The use of non-grooved runways increases the risk of hydroplaning, which may result in runway excursions.
4. If there is an absence of information and training about non-grooved runways, there is a risk that crews will not carry out the appropriate landing techniques when these runways are wet.
5. The use of thrust reversers reduces the risk of runway excursions when landing on wet runways.
6. If pilots do not comply with standard operating procedures, and companies do not assure compliance, then there is a risk that occurrences resulting from such deviations will persist.

Other findings:
1. The central maintenance computer was downloaded successfully; however, there were no data present in the memory unit.
2. Although the Transportation Safety Board was able to download high-quality data from the flight data recorder, the parameters that were not recorded due to the model type and input to the flight data recorder made it more difficult to determine the sequence of events.
Final Report:

Crash of a Dassault Falcon 10 in Toronto

Date & Time: Jun 17, 2011 at 1506 LT
Type of aircraft:
Operator:
Registration:
C-GRIS
Flight Type:
Survivors:
Yes
Schedule:
Toronto-Lester Bowles Pearson - Toronto-Buttonville
MSN:
02
YOM:
1973
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12000
Captain / Total hours on type:
4000.00
Copilot / Total flying hours:
7100
Copilot / Total hours on type:
475
Aircraft flight hours:
12697
Circumstances:
Aircraft was on a flight from Toronto-Lester B. Pearson International Airport to Toronto-Buttonville Municipal Airport, Ontario, with 2 pilots on board. Air traffic control cleared the aircraft for a contact approach to Runway 33. During the left turn on to final, the aircraft overshot the runway centerline. The pilot then compensated with a tight turn to the right to line up with the runway heading and touched down just beyond the threshold markings. Immediately after touchdown, the aircraft exited the runway to the right, and continued through the infield and the adjacent taxiway Bravo, striking a runway/taxiway identification sign, but avoiding aircraft that were parked on the apron. The aircraft came to a stop on the infield before Runway 21/03. The aircraft remained upright, and the landing gear did not collapse. The aircraft sustained substantial damage. There was no fire, and the flight crew was not injured. The Toronto-Buttonville tower controller observed the event as it progressed and immediately called for emergency vehicles from the nearby municipality. The accident occurred at 1506 Eastern Daylight Time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew flew an unstabilized approach with excessive airspeed.
2. The lack of adherence to company standard operating procedures and crew resource management, as well as the non-completion of checklist items by the flight crew contributed to the occurrence.
3. The captain’s commitment to landing or lack of understanding of the degree of instability of the flight path likely influenced the decision not to follow the aural GPWS alerts and the missed approach call from the first officer.
4. The non-standard wording and the tone used by the first officer were insufficient to deter the captain from continuing the approach.
5. At touchdown, directional control was lost, and the aircraft veered off the runway with sufficient speed to prevent any attempts to regain control.
Finding as to Risk
1. Companies which do not have ground proximity warning system procedures in their standard operating procedures may place crews and passengers at risk in the event that a warning is received.
Final Report:

Crash of a Rockwell Aero Commander 500B near Armstrong

Date & Time: Nov 30, 2007 at 0917 LT
Operator:
Registration:
C-GETK
Flight Phase:
Survivors:
Yes
Schedule:
Dryden – Geraldton
MSN:
500-1093-56
YOM:
1961
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed from Dryden, Ontario, en route to Geraldton, Ontario. The flight was conducted under visual flight rules at 5500 feet above sea level with ambient temperatures aloft of -33°C. Approximately 40 minutes into the flight, the crew observed an abnormal right engine fuel flow indication. While troubleshooting the right engine, the engine rpm and fuel flow began to decrease and the crew diverted toward Armstrong, Ontario. A short time later, the left engine rpm and fuel flow began to decrease and the crew could no longer maintain level flight. At 0917 central standard time, the crew made a forced landing 20 nautical miles southwest of Armstrong, into a marshy wooded area. The captain sustained serious injuries and the co-pilot and passenger sustained minor injuries. The aircraft was substantially damaged. The crew and passenger were stabilized and transported to Thunder Bay, Ontario, for medical assistance.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Suspended water in the fuel system precipitated out of solution and froze in the fuel distributor valve. This blocked the fuel supply to the fuel nozzles and led to the loss of engine power.
2. The aircraft was being operated without a fuel additive icing inhibiter. Use of such an additive would have inhibited ice formation in the aircraft’s fuel system and would likely have prevented the fuel system blockage.
Findings as to Risk:
1. The fuel distributor valve on the Aero Commander 500B is exposed directly to the cooling blast of the outside air, which under extremely cold conditions, can lead to the freezing of super-cooled water droplets present in the fuel stream.
2. The operator did not have procedures to describe how fuel additive icing inhibiter should be used during winter operations.
Final Report:

Crash of a Canadair RegionalJet CRJ-100ER in Toronto

Date & Time: May 20, 2007 at 1235 LT
Operator:
Registration:
C-FRIL
Survivors:
Yes
Schedule:
Moncton – Toronto
MSN:
7051
YOM:
1994
Flight number:
AC8911
Country:
Crew on board:
37
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft, with 3 crew members and 37 passengers on board, was operating as Air Canada Jazz Flight 8911 from Moncton, New Brunswick, to Toronto/Lester B. Pearson International Airport, Ontario. At 1235 eastern daylight time, the aircraft landed on Runway 06R with a 90º crosswind from the left, gusting from 13 to 23 knots. The aircraft first contacted the runway in a left-wing-down sideslip. The left main landing gear struck the runway first and the aircraft sustained a sharp lateral side load before bouncing. Once airborne again, the flight and ground spoilers deployed and the aircraft landed hard. Both main landing gear trunnion fittings failed and the landing gear collapsed. The aircraft remained upright, supported by the landing gear struts and wheels. The aircraft slid down the runway and exited via a taxiway, where the passengers deplaned. There was no fire. There were no injuries to the crew; some passengers reported minor injuries as a result of the hard landing.
Probable cause:
Findings as to Causes and Contributing Factors:
1. On final approach, the captain diverted his attention from monitoring the flight, leaving most of the decision making and control of the aircraft to the first officer, who was significantly less experienced on the aircraft type. As a result, the first officer was not fully supervised during the late stages of the approach.
2. The first officer did not adhere to the Air Canada Jazz standard operating procedures (SOPs) in the handling of the autopilot and thrust levers on short final, which left the aircraft highly susceptible to a bounce, and without the bounce protection normally provided by the ground lift dump (GLD) system.
3. Neither the aircraft operating manual nor the training that both pilots had received mentioned the importance of conducting a balked or rejected landing when the aircraft bounces. Given the low-energy state of the aircraft at the time of the bounce, the first officer attempted to salvage the landing.
4. When the thrust levers were reduced to idle after the bounce, the GLD system activated. The resultant sink rate after the GLD system deployed was beyond the certification standard for the landing gear and resulted in the landing gear trunnion fitting failures.
5. There was insufficient quality control at the landing gear overhaul facility, which allowed non-airworthy equipment to enter into service. The condition of the shock struts would have contributed to the bounce.
Findings as to Risk:
1. Several passengers took carry-on items with them as they exited the aircraft, despite being instructed not to do so.
2. The location of the stored megaphone did not allow the flight attendant to have ready access after the passengers started moving to the exit door.
Final Report:

Crash of an Airbus A340-313X in Toronto

Date & Time: Aug 2, 2005 at 1602 LT
Type of aircraft:
Operator:
Registration:
F-GLZQ
Survivors:
Yes
Schedule:
Paris - Toronto
MSN:
289
YOM:
1999
Flight number:
AF358
Country:
Crew on board:
12
Crew fatalities:
Pax on board:
297
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15411
Captain / Total hours on type:
1788.00
Copilot / Total flying hours:
4834
Copilot / Total hours on type:
2502
Aircraft flight hours:
28426
Aircraft flight cycles:
3711
Circumstances:
The Air France Airbus A340-313 aircraft (registration F-GLZQ, serial number 0289) departed Paris, France, at 1153 Coordinated Universal Time (UTC) as Air France Flight 358 on a scheduled flight to Toronto, Ontario, with 297 passengers and 12 crew members on board. Before departure, the flight crew members obtained their arrival weather forecast, which included the possibility of thunderstorms. While approaching Toronto, the flight crew members were advised of weather-related delays. On final approach, they were advised that the crew of an aircraft landing ahead of them had reported poor braking action, and Air France Flight 358’s aircraft weather radar was displaying heavy precipitation encroaching on the runway from the northwest. At about 200 feet above the runway threshold, while on the instrument landing system approach to Runway 24L with autopilot and autothrust disconnected, the aircraft deviated above the glideslope and the groundspeed began to increase. The aircraft crossed the runway threshold about 40 feet above the glideslope. During the flare, the aircraft travelled through an area of heavy rain, and visual contact with the runway environment was significantly reduced. There were numerous lightning strikes occurring, particularly at the far end of the runway. The aircraft touched down about 3800 feet down the runway, reverse thrust was selected about 12.8 seconds after landing, and full reverse was selected 16.4 seconds after touchdown. The aircraft was not able to stop on the 9000-foot runway and departed the far end at a ground speed of about 80 knots. The aircraft stopped in a ravine at 2002 UTC (1602 eastern daylight time) and caught fire. All passengers and crew members were able to evacuate the aircraft before the fire reached the escape routes. A total of 2 crew members and 10 passengers were seriously injured during the crash and the ensuing
evacuation.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew conducted an approach and landing in the midst of a severe and rapidly changing thunderstorm. There were no procedures within Air France related to distance required from thunderstorms during approaches and landing, nor were these required by regulations.
2. After the autopilot and autothrust systems were disengaged, the pilot flying (PF) increased the thrust in reaction to a decrease in the airspeed and a perception that the aircraft was sinking. The power increase contributed to an increase in aircraft energy and the aircraft deviated above the glide path.
3. At about 300 feet above ground level (agl), the surface wind began to shift from a headwind component to a 10-knot tailwind component, increasing the aircraft’s groundspeed and effectively changing the flight path. The aircraft crossed the runway threshold about 40 feet above the normal threshold crossing height.
4. Approaching the threshold, the aircraft entered an intense downpour, and the forward visibility became severely reduced.
5. When the aircraft was near the threshold, the crew members became committed to the landing and believed their go-around option no longer existed.
6. The touchdown was long because the aircraft floated due to its excess speed over the threshold and because the intense rain and lightning made visual contact with the runway very difficult.
7. The aircraft touched down about 3800 feet from the threshold of Runway 24L, which left about 5100 feet of runway available to stop. The aircraft overran the end of Runway 24L at about 80 knots and was destroyed by fire when it entered the ravine.
8. Selection of the thrust reversers was delayed as was the subsequent application of full reverse thrust.
9. The pilot not flying (PNF) did not make the standard callouts concerning the spoilers and thrust reversers during the landing roll. This further contributed to the delay in the PF selecting the thrust reversers.
10. Because the runway was contaminated by water, the strength of the crosswind at touchdown exceeded the landing limits of the aircraft.
11. There were no landing distances indicated on the operational flight plan for a contaminated runway condition at the Toronto/Lester B. Pearson International Airport (CYYZ).
12. Despite aviation routine weather reports (METARs) calling for thunderstorms at CYYZ at the expected time of landing, the crew did not calculate the landing distance required for Runway 24L. Consequently, they were not aware of the margin of error available for the landing runway nor that it was eliminated once the tailwind was experienced.
13. Although the area up to 150 m beyond the end of Runway 24L was compliant with Aerodrome Standards and Recommended Practices (TP 312E), the topography of the terrain beyond this point, along the extended runway centreline, contributed to aircraft damage and to the injuries to crew and passengers.
14. The downpour diluted the firefighting foam agent and reduced its efficiency in dousing the fuel-fed fire, which eventually destroyed most of the aircraft.
Findings as to Risk :
1. In the absence of clear guidelines with respect to the conduct of approaches into convective weather, there is a greater likelihood that crews will continue to conduct approaches into such conditions, increasing the risk of an approach and landing accident.
2. A policy where only the captain can make the decision to conduct a missed approach can increase the likelihood that an unsafe condition will not be recognized early and, therefore, increase the time it might otherwise take to initiate a missed approach.
3. Although it could not be determined whether the use of the rain repellent system would have improved the forward visibility in the downpour, the crew did not have adequate information about the capabilities and operation of the rain repellent system and did not consider using it.
4. The information available to flight crews on initial approach in convective weather does not optimally assist them in developing a clear idea of the weather that may be encountered later in the approach.
5. During approaches in convective weather, crews may falsely rely on air traffic control (ATC) to provide them with suggestions and directions as to whether to land or not.
6. Some pilots have the impression that ATC will close the airport if weather conditions make landings unsafe; ATC has no such mandate.
7. Wind information from ground-based measuring systems (anemometers) is critical to the safe landing of aircraft. Redundancy of the system should prevent a single-point failure from causing a total loss of relevant wind information.
8. The emergency power for both the public address (PA) and EVAC alert systems are located in the avionics bay. A less vulnerable system and/or location would reduce the risk of these systems failing during a survivable crash.
9. Brace commands were not given by the cabin crew during this unexpected emergency condition. Although it could not be determined if some of the passengers were injured as a result, research shows that the risk of injury is reduced if passengers brace properly.
10. Safety information cards given to passengers travelling in the flight decks of Air France Airbus A340-313 aircraft do not include illustrations depicting emergency exit windows, descent ropes or the evacuation panel in the flight deck doors.
11. There are no clear visual cues to indicate that some dual-lane slides actually have two lanes. As a result, these slides were used mostly as single-lane slides. This likely slowed the evacuation, but this fact was not seen as a contributing factor to the injuries suffered by the passengers.
12. Although all passengers managed to evacuate, the evacuation was impeded because nearly 50 per cent of the passengers retrieved carry-on baggage.
Other Findings:
1. There is no indication that the captain’s medical condition or fatigue played a role in this occurrence.
2. The crew did not request long aerodrome forecast (TAF) information while en route. This did not affect the outcome of this occurrence because the CYYZ forecast did not change appreciably from information the flight crew members received before departure, and they received updated METARs for CYYZ and Niagara Falls International Airport (KIAG).
3. The possibility of a diversion required the flight crew to check the weather for various potential alternates and to complete fuel calculations. Although these activities consumed considerable time and energy, there is no indication that they were unusual for this type of operation or that they overtaxed the flight crew.
4. The decision to continue with the approach was consistent with normal industry practice, in that the crew could continue with the intent to land while maintaining the option to discontinue the approach if they assessed that the conditions were becoming unsafe.
5. There is no indication that more sophisticated ATC weather radar information, had it been available and communicated to the crew, would have altered their decision to continue to land.
6. It could not be determined why door L2 opened before the aircraft came to a stop.
7. There is no indication that the aircraft was struck by lightning.
8. There is no information to indicate that the aircraft encountered windshear during its approach and landing.
9. The flight crew seats are certified to a lower standard than the cabin seats, which may have been a factor in the injuries incurred by the captain.
Final Report:

Crash of a Short 360-300 in Oshawa

Date & Time: Dec 16, 2004 at 2001 LT
Type of aircraft:
Operator:
Registration:
N748CC
Flight Type:
Survivors:
Yes
Schedule:
Toledo – Oshawa
MSN:
3748
YOM:
1988
Flight number:
SNC2917
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5300
Captain / Total hours on type:
1000.00
Copilot / Total flying hours:
800
Copilot / Total hours on type:
400
Circumstances:
Air Cargo Carriers, Inc. Flight SNC2917, a Short Brothers SD3-60 aircraft (registration N748CC, serial number SH3748), was on a charter cargo flight from Toledo, Ohio, USA, to Oshawa, Ontario, with two pilots on board. The crew conducted an instrument flight rules approach to Oshawa Municipal Airport in night instrument meteorological conditions. At approximately 2000 eastern standard time, the aircraft landed on Runway 30, which was snow-covered. During the landing roll, the pilot flying noted poor braking action and observed the runway end lights approaching. He rejected the landing and conducted a go-around procedure. The aircraft became airborne, but it started to descend as it flew over lower terrain, striking an airport boundary fence. It continued until it struck rising terrain and then a line of forestation, where it came to an abrupt stop. The flight crew exited the aircraft and waited for rescue personnel to render assistance. The aircraft was substantially damaged, and both pilots sustained serious injuries. There was no post-crash fire.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew planned and executed a landing on a runway that did not provide the required landing distance.
2. The flight crew most likely did not reference the Aircraft Flight Manual performance chart “Effect of a Slippery Surface on Landing Distance Required” to determine that landing the aircraft on the 4000-foot, snow-covered runway with flap-15 was inappropriate.
3. After landing long on the snow-covered runway and applying full reverse thrust, the captain attempted a go-around. He rotated the aircraft to a take-off attitude and the aircraft became airborne in ground effect at a slower-than-normal speed.
4. The aircraft had insufficient power and airspeed to climb and remained in ground effect until striking the airport perimeter fence, rising terrain, and a line of large cedar trees.
5. The flight crew conducted a flap-15 approach, based on company advice in accordance with an All Operator Message (AOM) issued by the aircraft manufacturer to not use flap-30. This AOM was superseded on 20 October 2004 by AOM No. SD006/04, which cancelled any potential flap-setting prohibition.
Other Finding:
1. The flight crew members were not advised that the potential Airworthiness Directive announced in the original AOM was not going into effect and that the use of flap-30 was acceptable, as relayed in the follow-up AOM.
Final Report:

Crash of a Noorduyn Norseman VI in Birch Lake

Date & Time: Jul 3, 2004
Type of aircraft:
Operator:
Registration:
C-FOBE
Survivors:
Yes
MSN:
480
YOM:
1944
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing on Birch Lake, the second compartment of the right float ruptured. The aircraft nosed down and sank. All five occupants were able to evacuate the cabin and to swim to the shore. The aircraft was written off.
Probable cause:
Failure of the right float on landing that was leaking probably due to a crack located in the second compartment.

Crash of a De Havilland DHC-2 Beaver in Fawcett Lake: 4 killed

Date & Time: May 18, 2004 at 1800 LT
Type of aircraft:
Registration:
C-GQHT
Survivors:
No
Schedule:
Pickeral Arm Camp - Fawcett Lake
MSN:
682
YOM:
1954
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1688
Captain / Total hours on type:
344.00
Circumstances:
Pickerel Arm Camps is located about 22 km south of Sioux Lookout, Ontario. It operates a main campsite at its water base and several remote fishing lodges. The company operates two float equipped de Havilland DHC-2 Beaver aircraft to fly guests and supplies to their remote sites. Seven guests of the company arrived at the water base on 18 May 2004, the day before their scheduled four-day fishing trip at Fawcett Lake, one of the remote lodges. Because the remote lodge was available, a decision was made to fly in that afternoon. The group was divided in two, and a group of three guests and all the supplies for the seven guests were to go in the first aircraft. The second group of four, with their personal baggage, was to follow in the company’s other Beaver. The occurrence aircraft, a de Havilland DHC-2 Beaver (C-GQHT, serial number 682) with one pilot and three camp guests on board, departed the company water base at approximately 1700 eastern daylight time on a day visual flight rules flight to Fawcett Lake. At approximately 1930, the pilot and the other four guests arrived in the second aircraft to discover that the first group had not arrived. The guests later found the accident aircraft overturned in the lake. Ontario Provincial Police divers recovered the bodies of the pilot and the three passengers. The aircraft sustained substantial damage. There was no fire.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The pilot flew a high-drag approach configuration for which his proficiency was not established.
2. The pilot most likely allowed the airspeed to decrease to the point that the aircraft stalled on approach at an altitude at which recovery was unlikely.
3. The impact was non-survivable because of the high impact forces.
Findings as to Risk:
1. The emergency locator transmitter (ELT) airframe antenna was broken off above the fuselage; however, the flight was within the 30-day period allowed by regulation for flight with an unserviceable ELT.
2. The pilot did not secure the cargo prior to flight, which allowed the cargo to shift forward on impact.
3. The weight and centre of gravity (C of G) were not indicated in the operational flight plan and load record, and the aircraft’s weight and C of G could only be estimated.
Final Report:

Crash of a Cessna 208B Grand Caravan off Pelée Island: 10 killed

Date & Time: Jan 17, 2004 at 1638 LT
Type of aircraft:
Operator:
Registration:
C-FAGA
Flight Phase:
Survivors:
No
Schedule:
Pelée Island – Windsor
MSN:
208B-0658
YOM:
1998
Flight number:
GGN125
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
3465
Captain / Total hours on type:
957.00
Aircraft flight hours:
7809
Circumstances:
On 17 January 2004, the occurrence pilot started his workday in Toronto, Ontario, reporting for duty at 0445 eastern standard time. In the morning, he completed flights in the Cessna 208B Caravan from Toronto to Windsor, Ontario, Windsor to Pelee Island, Ontario, and then Pelee Island to Windsor where the aircraft landed at 0916. At approximately 1500, the pilot received local weather and passenger information by telephone from the Pelee Island office personnel. The 1430 weather was reported as follows: ceiling 500 feet obscured, visibility two miles. There were eight male passengers for pick up at Pelee Island. One additional passenger was travelling with the pilot. There was no discussion concerning the amount of cargo to be carried or the passenger weights. At 1508, the pilot received a faxed weather package that he had requested from the Flight Information Centre (FIC) in London, Ontario. At 1523, the aircraft was refuelled in preparation for the scheduled 1600 departure to Pelee Island. The passengers were loaded earlier than usual to allow time for aircraft de-icing, as wet snow had accumulated on the fuselage and wings since the previous flight. At 1555, the aircraft was de-iced with Type 1 de-icing fluid, and it departed for Pelee Island at 1605 on an instrument flight rules (IFR) flight plan as Flight GGN125. At 1615, the pilot advised the Cleveland Control Centre, Ohio, United States, that he had Pelee Island in sight, was cancelling IFR, and was descending out of 5000 feet. The pilot also advised Cleveland that he would be departing IFR out of Pelee Island in about 20 minutes as GGN126 and asked if a transponder code could be issued. The Cleveland controller issued a transponder code and requested a call when GGN126 became airborne. The pilot advised that the flight would depart on Runway 27 then turn north. These were the last recorded transmissions from the aircraft. The aircraft landed at 1620. While on the ramp, two individuals voiced concern to the pilot that there was ice on the wing. Freezing precipitation was falling. The pilot was observed to visually check the leading edge of the wing; however, he did not voice any concern and proceeded with loading the passengers and cargo. At approximately 1638, GGN126 departed Pelee Island for Windsor. After using most of the runway length for take-off, the aircraft climbed out at a very shallow angle. No one on the ground observed the aircraft once it turned toward the north; however, witnesses who were not at the airport reported that they heard the sound of a crash, then no engine noise. A normal flight from Pelee Island to Windsor in the Cessna Caravan takes 15 to 20 minutes. Shortly after the aircraft departed, the ticket agent in Windsor received a call from Pelee Island reporting that a crash had been heard. At 1705, when the aircraft had not arrived, the ticket agent called Windsor tower. The pilot had not made contact with any air traffic services (ATS) facility immediately before or after departure, so there was nothing in the ATS system to indicate that the aircraft had taken off. It was, therefore, unaccounted for. There was no signal heard from the emergency locator transmitter (ELT). At 1710, the Windsor tower controller contacted the Rescue Coordination Centre in Trenton, Ontario, and a search was initiated. At 1908, the aircraft empennage and debris were spotted by a United States Coast Guard (USCG) helicopter on the frozen surface of the lake, about 1.6 nautical miles (nm) from the departure end of the runway. There were no survivors. The empennage sank beneath the surface some four hours later. The wreckage recovery was not fully completed until 13 days later.
Probable cause:
Findings as to Causes and Contributing Factors:
1. At take-off, the weight of the aircraft exceeded the maximum allowable gross take-off weight by at least 15 per cent, and the aircraft was contaminated with ice. Therefore, the aircraft was being flown significantly outside the limitations under which it was certified for safe flight.
2. The aircraft stalled, most likely when the flaps were retracted, at an altitude or under flight conditions that precluded recovery before it struck the ice surface of the lake.
3. On this flight, the pilotís lack of appreciation for the known hazards associated with the overweight condition of the aircraft, ice contamination, and the weather conditions was inconsistent with his previous practices. His decision to take off was likely adversely affected by some combination of stress and fatigue.
Findings as to Risk:
1. Despite the abbreviated nature of the September 2001 audit, the next audit of Georgian Express Ltd. was not scheduled until September 2004, at the end of the 36-month window.
2. The internal communications at Transport Canada did not ensure that the principal operations inspector responsible for the air operator was aware of the Pelee Island operation.
3. The standard passenger weights available in the Aeronautical Information Publication at the time of the accident did not reflect the increased average weight of passengers and carry-on baggage resulting from changes in societal-wide lifestyles and in travelling trends.
4. The use of standard passenger weights presents greater risks for aircraft under 12 500 pounds than for larger aircraft due to the smaller sample size (nine passengers or less) and the greater percentage of overall aircraft weight represented by the passengers. The use of standard passenger weights could result in an overweight condition that adversely affects the safety of flight.
5. The Cessna Caravan de-icing boot covers up to a maximum of 5% of the wing chord. Research on this wing has shown that ice accumulation beyond 5% of the chord can result in degradation of aircraft performance.
6. At the Pelee Island Airport, the air operator did not provide the equipment that would allow an adequate inspection of the aircraft for ice during the pre-flight inspection and did not provide adequate equipment for aircraft de-icing.
7. Repetitive charter operators are not considered to be scheduled air operators under current Transport Canada regulations, and, therefore, even though the charter air operator may provide a service with many of the same features as a scheduled service, Transport Canada does not provide the same degree of oversight as it does for a scheduled air operator.
8. A review of the Canadian Aviation Regulations regarding simulator training requirements indicates that there is no requirement to conduct recurrent simulator training if currency and/or pilot proficiency checks do not lapse.
9. Commercial Air Service Standard 723.91(2) does not clearly indicate whether there is a requirement for simulator training following expiration of a pilot proficiency check.
10. Incorrect information on the passenger door placards, an incomplete safety features card, and the fact that the operating mechanisms and operating instructions for the emergency exits were not visible in darkness could have compromised passenger egress in the event of a survivable accident.
11. The dogs being carried on the aircraft were not restrained, creating a hazard for the flight and its occupants.
Final Report:

Crash of a Beechcraft A100 King Air in Terrace Bay

Date & Time: Jan 1, 2004
Type of aircraft:
Operator:
Registration:
C-GFKS
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Terrace Bay – Thunder Bay
MSN:
B-247
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On take off roll on runway 25 at dusk, left wing struck a snowbank on left side of the runway. Aircraft veered off runway and came to rest in snow with its nose gear sheared off and several damages to the fuselage. Both pilots were uninjured.
Probable cause:
A NOTAM stated that there were windrows four feet high, 10 feet inside the runway lights on both sides of the runway. This NOTAM also stated that the cleared portion of the runway was covered with ¼ inch of loose snow over 60 percent compacted snow and 40 percent ice patches and that braking action was fair to poor. The take-off was being conducted at dusk in conditions of poor lighting and contrast. Crosswind was not a factor.