Crash of a Canadair RegionalJet CRJ100 in Fredericton

Date & Time: Dec 16, 1997 at 2348 LT
Operator:
Registration:
C-FSKI
Survivors:
Yes
Schedule:
Toronto - Fredericton
MSN:
7068
YOM:
1995
Flight number:
AC646
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
39
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11020
Captain / Total hours on type:
1770.00
Copilot / Total flying hours:
3225
Copilot / Total hours on type:
60
Aircraft flight hours:
6061
Aircraft flight cycles:
5184
Circumstances:
Air Canada Flight 646, C-FSKI, departed Toronto-Lester B. Pearson International Airport, Ontario, at 2124 eastern standard time on a scheduled flight to Fredericton, New Brunswick. On arrival, the reported ceiling was 100 feet obscured, the visibility one-eighth of a mile in fog, and the runway visual range 1200 feet. The crew conducted a Category I instrument landing system approach to runway 15 and elected to land. On reaching about 35 feet, the captain assessed that the aircraft was not in a position to land safely and ordered the first officer, who was flying the aircraft, to go around. As the aircraft reached its go-around pitch attitude of about 10 degrees, the aircraft stalled aerodynamically, struck the runway, veered to the right and then travelled—at full power and uncontrolled—about 2100 feet from the first impact point, struck a large tree and came to rest. An evacuation was conducted; however, seven passengers were trapped in the aircraft until rescued. Of the 39 passengers and 3 crew members, 9 were seriously injured and the rest received minor or no injuries. The accident occurred at 2348 Atlantic standard time.
Probable cause:
Findings as to Causes and Contributing Factors:
1. Although for the time of the approach the weather reported for Fredericton—ceiling 100 feet and visibility c mile—was below the 200-foot decision height and the charted ½ -mile (RVR 2600) visibility for the landing, the approach was permitted because the reported RVR of 1200 feet was at the minimum RVR specified in CAR 602.129.
2. Based on the weather and visibility, runway length, approach and runway lighting, runway condition, and the first officer’s flying experience, allowing the first officer to fly the approach is questionable.
3. The first officer allowed the aircraft to deviate from the flight path to the extent that a go-around was required, which is an indication of his ability to transition to landing in the existing environmental conditions.
4. Disengagement of the autopilot at 165 feet rather than at the 80-foot minimum autopilot altitude resulted in an increased workload for the PF, allowed deviations
from the glide path, and deprived the pilots of better visual cues for landing.
5. In the occurrence environmental conditions, the lack of runway centre line and touchdown-zone lighting probably contributed to the first officer not being able to see the runway environment clearly enough to enable him to maintain the aircraft on the visual glide path and runway centre line.
6. The first officer’s inexperience and lack of training in flying the CL-65 in low-visibility conditions contributed to his inability to successfully complete the landing.
7. The situation of a captain being the PNF when ordering a go-around probably played a part in the uncertainty regarding the thrust lever advance and the raising of the flaps because there was no documented procedure covering their duties.
8. The go-around was attempted from a low-energy situation outside of the flight boundaries certified for the published go-around procedures; the aircraft’s low energy was primarily the result of the power being at idle.
9. The sequential nature of steps within the go-around procedures, in particular, in directing the pitch adjustment prior to noting the airspeed, the compelling nature of the command bars, and the high level of concentration required when initiating the go-around contributed to the first officer’s inadequate monitoring of the airspeed during the go-around attempt.
10. Following the command bars in go-around mode does not ensure that a safe flying speed is maintained, because the positioning of the command bars does not take into consideration the airspeed, flap configuration, and the rate of change of the angle of attack, considerations required to compute stall margin.
11. The conditions under which the go-arounds are demonstrated for aircraft certification do not form part of the documentation that leads to aircraft limitations or boundaries for the go-around procedure; this contributed to these factors not being taken into account when the go-around procedures were incorporated in aircraft and training manuals.
12. The published go-around procedure does not adequately reflect that once power is reduced to idle for landing, a go-around will probably not be completed without the aircraft contacting the runway (primarily because of the time required for the engines to spool up to go-around thrust).
13. The Air Canada stall recovery training, as approved by Transport Canada, did not prepare the crew for the conditions in which the occurrence aircraft stick shaker activated and the aircraft stalled.
14. The limitations of the ice-detection and annunciation systems and the procedures on the use of wing anti-ice did not ensure that the wing would remain ice-free during flight.
15. Ice accretion studies indicate that the aircraft was in an icing environment for at least 60 seconds prior to the stall, and that during this period a thin layer of mixed ice with some degree of roughness probably accumulated on the leading edges of the wings. Any ice on the wings would have reduced the safety margins of the stall protection system.
16. The implications of ice build-up below the threshold of detection, and the inhibiting of the ice advisory below 400 feet, were not adequately considered when the stall margin was being determined during the 1996 certification of the ice-detection system and associated procedures.
17. The stall protection system operated as designed: that it did not prevent the stall is related to the degraded performance of the wings.
18. The Category I approach was without the extra aids and defences required for Category II approaches.
19. Canadian regulations with respect to Category I approaches are more liberal than those of most countries and are not consistent with the ICAO International Standards and Recommended Practices (Annex 14), which defines visibility limits; in Canada, the visibility values, other than RVR, are advisory only.
20. Even though a Category I approach may be conducted in weather conditions reported to be lower than the landing minima specified for the approach, there is no special training required for any flight crew member, and there is no requirement that flight crew be tested on their ability to fly in such conditions.
21. Air Canada’s procedures required that the captain fly the aircraft when conducting a Category II approach, in all weather conditions; however, the decision as to who will fly low-visibility Category I approaches was left to the captain, who may not be in a position to adequately assess the first officer’s ability to conduct the approach.
22. The aircraft stalled at an angle of attack approximately 4.5 degrees lower, and at a CLmax 0.26 lower, than would be expected for the natural stall.
23. On final approach below 1000 feet agl, the wing performance on the accident flight was degraded over the wing performance at the same phase on the previous flight.
24. The engineering simulator comparison indicated two step reductions in aircraft performance, at 400 feet and 150 feet agl, as a result of local flow separation in the vicinity of wing station (WS) 247 and WS 253.
25. Pitting on the leading edges of the wings had a negligible effect on the performance of the aircraft.
26. The sealant on the leading edges of both wings was missing in some places and protruding from the surface 2 to 3 mm in others. Test flights indicate that the effect of the protruding chordwise sealant on the aircraft performance could have accounted for a reduction of 1.7 to 2.0 degrees in maximum fuselage angle of attack and of 0.03 to 0.05 in CLmax.
27. The maximum reduction in angle of attack resulting from ground effect is considered to be in the order of 0.75±0.5 degree: the aircraft angle of attack was influenced by ground effect during the go-around manoeuvre.
28. The performance loss caused by the protruding sealant and by ground effect was not great enough to account for the performance loss experienced; there is no apparent phenomenon other than ice accretion that could account for the remainder of the performance loss.
29. Neither Bombardier Inc., nor Transport Canada, nor Air Canada ensured that the regulations, manuals, and training programs prepared flight crews to successfully and consistently transition to visual flight for a landing or to go-around in the conditions that existed during this flight, especially considering the energy state of the aircraft when the go-around was commenced.
Other Findings:
1. Both the captain and the first officer were licensed and qualified for the duties performed during the flight in accordance with regulations and Air Canada training
and standards, except for minor training deficiencies with regard to emergency equipment.
2. The occurrence flight attendant was trained and qualified for the flight in accordance with existing requirements.
3. The aircraft was within its weight and centre-of-gravity limits for the entire flight.
4. Records indicate that the aircraft was certified, equipped, and maintained in accordance with existing regulations and approved procedures.
5. There was no indication found of a failure or malfunction of any aircraft component prior to or during the flight.
6. When the stick shaker activated, it is unlikely that the crew could have landed the aircraft safely or completed a go-around without ground contact.
7. When power was selected for the go-around, the engines accelerated at a rate that would have been expected had the thrust levers been slammed to the go-around power setting.
8. The aircraft was not equipped with an emergency locator transmitter, nor was one required by regulation.
9. The lack of an emergency locator transmitter probably delayed locating the aircraft and its occupants.
10. Passengers and crew had no effective means of signaling emergency rescue services personnel.
11. The flight crew did not receive practical training on the operation of any emergency exits during their initial training program, even though this was required by
regulation.
12. Air Canada’s initial training program for flight crew did not include practical training in the operation of over-wing exits or the flight deck escape hatch.
13. Air Canada’s annual emergency procedures training for flight crew regarding the operation and use of emergency exits did not include practical training every third year, as required. Annual emergency exit training was done by demonstration only.
14. The flight crew were unaware that a pry bar was standard emergency equipment on the aircraft.
15. The four emergency flashlights carried on board were located in the same general area of the aircraft, increasing the possibility that all could be rendered inaccessible or unserviceable in an accident. (See section 4.1.6)
16. That there was a Flight Service Station specialist, as opposed to a tower controller, at the Fredericton airport at the time of the arrival of ACA 646 was not material to this occurrence.
Final Report:

Crash of a BAe Nimrod MR.2P off Toronto: 7 killed

Date & Time: Sep 2, 1995
Type of aircraft:
Operator:
Registration:
XV239
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Toronto - Toronto
MSN:
8014
YOM:
1969
Location:
Country:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The Nimrod display aircraft and crew had deployed to Canada on 23 August 1995 for displays at Canadian Forces Base Shearwater and the Canadian International Air Show (CIAS) at Toronto. In excellent weather, with a light on-shore wind, the aircraft took off on time for its display. Upon completion of the safety checks, it ran in for the standard Nimrod display sequence which features two orbits and two dumb-bell turns. The latter manoeuvres each involved a turn away from the display line, a climb to not above 1,000 feet, followed by a turn in the opposite direction and descent, to fly back parallel with the display line. Having completed the two orbits, the first dumb-bell turn was completed uneventfully. After a slow flypast with undercarriage down, the aircraft entered its final manoeuvre, the second dumb-bell turn. It was seen to turn away approximately 75° to starboard under full power before the flaps were retracted to 20° and the undercarriage raised. The nose was then pitched up into a climbing attitude of 24°. As the aircraft passed 950 feet, engine power was reduced to almost flight idle, following which the speed reduced rapidly to 122 knots, below the 150 knots recommended and taught for that stage of the display. The aircraft was rolled to 70° of port bank, shortly afterwards reducing to 45°, and the nose lowered to 5° below the horizon. During this turn the airspeed increased slightly and the G-loading increased to 1 .6 G. However, the combination of the low airspeed and the G-loading led the aircraft to stall, whereupon the port wing dropped to 85° of bank and the nose dropped to 18° below the horizon. Full starboard aileron and full engine power were applied in an attempt to recover the aircraft but, by this stage, there was insufficient height to recover and the aircraft hit the water. All seven crew members were killed.
Probable cause:
The Inquiry determined that the captain made an error of judgement in modifying one of the display manoeuvres to the extent that he stalled the aircraft at a height and attitude from which recovery was impossible. The Inquiry considered that contributory factors could have included deficiencies in the flight deck crew's training and in the method of supervision which could have allowed the captain to develop an unsafe technique without full appreciation of the consequences.

Crash of a Douglas DC-9-31 in Erie

Date & Time: Feb 21, 1986 at 0859 LT
Type of aircraft:
Operator:
Registration:
N961VJ
Survivors:
Yes
Schedule:
Toronto - Erie
MSN:
47506
YOM:
1970
Flight number:
US499
Crew on board:
5
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8900
Captain / Total hours on type:
5900.00
Aircraft flight hours:
42104
Circumstances:
During arrival, the crew of USAir flight 499 landed on runway 24, which was covered with snow. Reportedly, while landing, the aircraft touched down approximately 1,800 to 2,000 feet beyond the displaced threshold. Altho armed, the spoilers did not autodeploy, so the captain operated them manually. He lowered the aircraft's nose, actuated reverse thrust and applied brakes. The brakes were not effective. Subsequently, the aircraft continued off the end of the runway, ran over a runway end id light, struck a fence and came to rest straddling a road. The crew had planned on making an ILS approach to runway 06, but the RVR was only 2,800 feet and a minimum RVR of 4 000 feet was requested for that runway. The crew elected to land on runway 24, since 1/2 mile visibility was sufficient for that runway. However, the approach was made with a qtrg tailwind and approximately 10 knots above Vref. Tailwind landings were not authorized on runway 24 in wet/slippery conditions. The runway braking action was reported as fair-to-poor. The pilot's handbook cautioned the crew to monitor the spoilers when landing on slippery runways, since the spoilers auto-deploy only with wheel spin-up or when the nose wheel is on the ground. A passenger was slightly injured while 22 other occupants were uninjured.
Probable cause:
Occurrence #1: overrun
Phase of operation: landing - roll
Findings
1. (f) weather condition - low ceiling
2. (f) weather condition - snow
3. (f) weather condition - fog
4. (f) weather condition - tailwind
5. (c) planning/decision - improper - pilot in command
6. (f) airspeed(vref) - exceeded - pilot in command
7. (f) airport facilities, runway/landing area condition - displaced threshold
8. (f) proper touchdown point - not attained - pilot in command
9. (f) airport facilities, runway/landing area condition - snow covered
10. (c) go-around - not performed - pilot in command
----------
Occurrence #2: on ground/water collision with object
Phase of operation: landing - roll
Findings
11. (f) object - runway light
12. (f) object - fence
----------
Occurrence #3: on ground/water encounter with terrain/water
Phase of operation: landing - roll
Findings
13. (f) terrain condition - rough/uneven
Final Report:

Crash of a Piper PA-31T Cheyenne II in Toronto: 3 killed

Date & Time: Oct 17, 1984
Type of aircraft:
Registration:
C-GAPT
Survivors:
No
MSN:
31-7620004
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On approach to Toronto-Lester Bowles Pearson Airport, the twin engine airplane struck the ground and crashed about 11 km short of runway threshold. All three occupants were killed.

Crash of a Douglas C-47B-20-DK in Saint Louis: 1 killed

Date & Time: Jan 9, 1984 at 2232 LT
Operator:
Registration:
C-GSCA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Saint Louis - Toronto
MSN:
15745/27190
YOM:
1945
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4000
Captain / Total hours on type:
1350.00
Aircraft flight hours:
17933
Circumstances:
After landing, the pilot-in-command (pic) placed a refueling order to fill the aircraft's two 210 gallons main tanks for a return flight to Toronto, Ontario, Canada. After the cargo was unloaded and the aircraft was refueled, the aircrew aborted the 1st two attempts to takeoff due to slow aircraft performance. Engine run-ups were performed after each abort and reportedly, the engines checked normal. After the 2nd aborted takeoff, the aircrew called the fbo and requested that the refueler be asked what type of fuel was added. The response was '100LL Avgas.' On the 3rd attempt to depart, the aircraft took off, but both engines lost power as the landing gear was retracted. The aircrew selected a highway on which to land. However, the left wing hit a utility pole, then the aircraft went thru a fence and hit a highway embankment. Investigation revealed that Jet-A fuel had been added to the aircraft rather than 100LL fuel. The truck containing Jet-A fuel looked similar to the one with 100LL Avgas, but was properly designated with fuel grade markings. A pilot was killed, the second was seriously injured.
Probable cause:
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: takeoff - initial climb
Findings
1. (c) fluid,fuel - improper
2. (c) maintenance, service of aircraft/equipment - improper - fbo personnel
3. Aircraft performance, two or more engines - inoperative
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with object
Phase of operation: descent - emergency
Findings
4. (f) object - utility pole
----------
Occurrence #4: on ground/water collision with object
Phase of operation: landing
Findings
5. (f) object - fence
----------
Occurrence #5: on ground/water encounter with terrain/water
Phase of operation: landing
Findings
6. (f) terrain condition - dirt bank/rising embankment
Final Report:

Crash of a Douglas C-47A-10-DK in Toronto: 2 killed

Date & Time: Jun 22, 1983 at 0858 LT
Operator:
Registration:
C-GUBT
Flight Type:
Survivors:
No
Schedule:
Cleveland - Toronto
MSN:
12424
YOM:
1944
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
A Douglas C-47A cargo plane was destroyed when it crashed while in final approach to Toronto International Airport, ON (YYZ), Canada. Both pilots were killed. Skycraft Air Transport Flight 505 operated on a cargo flight from Cleveland-Hopkins International Airport, OH (CLE), USA. It was loaded with 6 wire mesh baskets, each almost filled with automobile roof bows. On completion of the loading, the crew chief stated he asked the flight crew if they wished the load tied down. They responded by saying they would take care of it. Flight 505 departed Cleveland at 07:45, on a VFR flight plan. The Toronto terminal controller gave a few small heading changes to direct the flight to the instrument landing system (ILS) localizer for an almost straight-in approach to runway 06R, then transferred it to the arrival controller, who continued vectoring the aircraft. During the approach, the arrival controller twice requested Flight 505 to maintain its best speed for spacing from other aircraft. The crew initially reported they were flying their maximum speed, and later indicated they were at their best speed as the aircraft was fairly heavy. Flight 505 called the tower over the outer marker and was cleared to land. After crossing the threshold 100 to 150 ft above the runway, the nose of the aircraft smoothly rose 5 to 10 deg. The nose then dropped an almost equal number of degrees, as if a correction had been made for the nose high attitude. This up, then down pitch movement was quickly followed by two pitch oscillations of increasing speed and magnitude. On the fourth oscillation, the nose continued to rise 45 to 60 deg. and the aircraft started to climb. The engine noise seemed to increase as the aircraft pitched up for the last time. At approximately 200 ft, as the aircraft reached the apex of its climb, the left wing dropped and the aircraft yawed to the left approximately 90 degrees. The wings levelled, then the aircraft fell into the field to the right side of the runway. The time between the beginning of the first oscillation and the impact with the ground is estimated to have been approximately 10 seconds. On impact the right main gear ruptured a fuel tank and a post-impact fuel fire ensued.
Probable cause:
The aircraft's weight and centre of gravity limits were exceeded, and the cargo was not secured. These factors led to loss of control of the aircraft.

Crash of a Douglas DC-9-32 in Cincinnati: 23 killed

Date & Time: Jun 2, 1983 at 1920 LT
Type of aircraft:
Operator:
Registration:
C-FTLU
Survivors:
Yes
Schedule:
Dallas – Toronto – Montreal
MSN:
47196
YOM:
1968
Flight number:
AC797
Crew on board:
5
Crew fatalities:
Pax on board:
41
Pax fatalities:
Other fatalities:
Total fatalities:
23
Captain / Total flying hours:
13000
Captain / Total hours on type:
4939.00
Copilot / Total flying hours:
5650
Copilot / Total hours on type:
2499
Aircraft flight hours:
36825
Aircraft flight cycles:
34987
Circumstances:
The aircraft departed Dallas on a regularly scheduled international passenger flight to Montreal, Quebec, Canada, with an en route stop at Toronto, Ontario, Canada. The flight left Dallas with 5 crew members and 41 passengers on board. About 1903, eastern daylight time, while en route at flight level 330 (about 33,000 feet m.s.l.), the cabin crew discovered smoke in the left aft lavatory. After attempting to extinguish the hidden fire and then contacting air traffic control (ATC) and declaring an emergency, the crew made an emergency descent and ATC vectored Flight 797 to the Greater Cincinnati International Airport, Covington, Kentucky. At 1920:09, eastern daylight time, Flight 797 landed on runway 27L at the Greater Cincinnati International Airport. As the pilot stopped the airplane, the airport fire department, which had been alerted by the tower to the fire on board the incoming plane, was in place and began firefighting operations. Also, as soon as the airplane stopped, the flight attendants and passengers opened the left and right forward doors, the left forward overwing exit, and the right forward and aft overwing exits. About 60 to 90 seconds after the exits were opened, a flash fire engulfed the airplane interior. While 18 passengers and 3 flight attendants exited through the forward doors and slides and the three open overwing exits to evacuate the airplane, the captain and first officer exited through their respective cockpit sliding windows. However, 23 passengers were not able to get out of the plane and died in the fire. The airplane was destroyed.
Probable cause:
The National Transportation Safety Board determines that the probable causes of the accident were a fire of undetermined origin, an underestimate of fire severity, and misleading fire progress information provided to the captain. The time taken to evaluate the nature of the fire and to decide to initiate an emergency descent contributed to the severity of the accident.
Final Report:

Crash of a Rockwell Sabreliner 65 in Toronto: 5 killed

Date & Time: Jan 11, 1983
Type of aircraft:
Operator:
Registration:
N99S
Survivors:
No
Schedule:
Philadelphia - Toronto
MSN:
465-64
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
On approach to Toronto-Lester Bowles Pearson Airport following an uneventful flight from Philadelphia, the airplane rolled left and right then lost altitude and crashed in a field, bursting into flames. The wreckage was found 13 km from runway 24R threshold. The aircraft was destroyed by impact forces and a post crash fire and all five occupants were killed, among them Ross Henningar, President and CEO of Sun Oil Company (Sunoco).
Probable cause:
Loss of control on approach following an internal failure in the low pressure compressor of the right engine while the left engine flamed out and was windmilling at impact. Investigations were unable to determine the cause of these occurrences. It was also noted that the anti-icing systems were not activated prior to the accident while icing conditions have been forecasted.