Crash of a Beechcraft King Air 100 in Muskoka

Date & Time: Feb 27, 1999 at 0920 LT
Type of aircraft:
Registration:
C-GBTS
Flight Type:
Survivors:
Yes
Schedule:
Kitchener - Muskoka
MSN:
BE-73
YOM:
1979
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Muskoka Airport, while on a cargo flight from Kitchener-Waterloo Airport, the twin engine aircraft descended too low in a slight nose down attitude when it collided with trees and crashed on the ground. Both occupants were seriously injured and the aircraft was damaged beyond repair. At the time of the accident, ceiling was at 1,000 feet with 10 km visibility and wind from 140 at 2 knots.

Crash of a Douglas DC-3C in Mayne Island: 2 killed

Date & Time: Jan 13, 1999 at 0633 LT
Type of aircraft:
Operator:
Registration:
C-GWUG
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Vancouver - Victoria
MSN:
16215/32963
YOM:
1945
Flight number:
KFA301
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18000
Captain / Total hours on type:
9500.00
Copilot / Total flying hours:
9000
Copilot / Total hours on type:
430
Aircraft flight hours:
20123
Circumstances:
The accident aircraft, a Douglas DC-3C, C-GWUG, was owned and operated by Kelowna Flightcraft Air Charter Ltd. (Kelowna Flightcraft) and was under charter to Purolator Courier Ltd. (Purolator). Since April 1998, the aircraft had been dedicated to transporting cargo on a route between Vancouver and Nanaimo, British Columbia. On occasion, it was also used for flights to Victoria to meet Purolator=s scheduling or cargo-loading contingencies. On the day of the accident, the aircraft, operating as KFA300, was rerouted and tasked to fly from Vancouver to Victoria and then proceed to Nanaimo. This change was precipitated by the delayed arrival of Purolator=s Boeing 727 at Vancouver because of inclement weather in the Toronto/Hamilton, Ontario, area. Warning of this route change was passed to the crew members with their pre-flight planning package, which included filed instrument flight rules (IFR) flight plans for the Vancouver-to-Victoria and Victoria-to-Nanaimo legs of the trip. The captain of the occurrence flight cancelled his IFR flight plan and refiled visual flight rules (VFR) on first contact with air traffic control. Vancouver tower cleared KFA300 for take-off at 0622 Pacific standard time (PST) from runway 26L. After take-off, the aircraft turned left on a track toward Active Pass, as seen in Figure 1. During the departure climb, the captain requested an altitude of 1000 feet above sea level (asl); the tower controller approved this request. Recorded radar data indicate that the aircraft climbed to and levelled at 1000 feet asl and then accelerated to a steady en route ground speed of 130 knots. The aircraft left the Vancouver control zone at 0626 and entered Class E (controlled) airspace. There are no special requirements for VFR aircraft operating within this class of airspace, nor are any specific services required of the air traffic control system. As the aircraft approached the Gulf Islands, it descended slightly and remained level at 900 feet asl. It crossed about 0.25 nautical mile (nm) west of the Active Pass non-directional beacon (NDB) at 0632 while remaining steady at 130 knots (ground speed) and level at 900 feet asl. At 0633:04, the aircraft descended to 800 feet asl for about nine seconds. The last radar data show the aircraft at 900 feet asl and 130 knots. The last radar-depicted position of the aircraft is on a bearing of 189 degrees (true) and 21.8 nm from the Sea Island radar source, coincident with the crash location.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The accident flight was not conducted in accordance with the night obstacle clearance requirements of Canadian Aviation Regulation (CAR) 705.32.
2. The Kelowna Flightcraft company operations manual did not reflect the restrictive conditions imposed on night visual flight rules (VFR) flight by CAR 705.32. Such information might have
prevented the accident by ensuring the crew's awareness of those night obstacle clearance standards.
3. As the aircraft approached Mayne Island, it encountered a low cloud ceiling that was based about 800 feet and that reduced visual reference with the surface.
4. When the aircraft struck trees, it was being flown in controlled, level flight at an altitude below the surrounding terrain.
5. The aircraft was not equipped with a ground proximity warning system or any other similar system that could warn the crew of an impending collision with terrain. Such systems were not required by regulation.
Findings as to Risk:
1. Kelowna Flightcraft flight operations personnel were not aware that most of the DC-3 flights were being conducted under VFR.
2. First responders were not aware of the presence of the dangerous goods and were therefore at increased risk during their response activities on the site.
Other Findings:
1. Transport Canada officials responsible for monitoring this operation were not aware that most of the DC-3 flights were being conducted under VFR at night and below the required obstacle
clearance altitudes.
Final Report:

Crash of a Beechcraft 1900C-1 off Saint-Augustin

Date & Time: Jan 4, 1999 at 0859 LT
Type of aircraft:
Operator:
Registration:
C-FGOI
Survivors:
Yes
Schedule:
Lourdes-de-Blanc-Sablon – Saint-Augustin
MSN:
UC-085
YOM:
1989
Flight number:
RH1707
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Copilot / Total flying hours:
4000
Copilot / Total hours on type:
500
Circumstances:
The Régionnair Inc. Beechcraft 1900C, serial number UC-85, with two pilots and 10 passengers on board, was making an instrument flight rules (IFR) flight between Lourdes-de-Blanc-Sablon, Quebec, and Saint-Augustin, Quebec. Just before initiation of descent, the radiotelephone operator of the Saint-Augustin Airport UNICOM (private advisory service) station informed the crew that the ceiling was 300 feet, visibility a quarter of a mile in snow flurries, and the winds from the southeast at 15 knots gusting to 20 knots. The crew made the LOC/DME (localizer transmitter / distance-measuring equipment) non-precision approach for runway 20. The approach proceeded normally until the minimum descent altitude (MDA). When the first officer reported sighting the ground beneath the aircraft, the captain decided to continue descending below the MDA. Thirty-five seconds later, the ground proximity warning system (GPWS) AMINIMUMS@ audible alarm sounded. Three seconds later, the aircraft flew into the frozen surface of the Saint-Augustin River. The occupants escaped the accident unharmed. The aircraft was heavily damaged.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew did not follow the company's SOPs for the briefing preceding the approach and for a missed approach.
2. In the approach briefing, the captain did not specify the MDA or the MAP, and the first officer did not notice these oversights, which shows a lack of coordination within the crew.
3. The captain continued descent below the MDA without establishing visual contact with the required references.
4. The first officer probably had difficulty perceiving depth because of the whiteout.
5. The captain did not effectively monitor the flight parameters because he was trying to establish visual contact with the runway.
6. The chief pilot (the captain of C-FGOI) set a bad example to the pilots under him by using a dangerous method, that is, descending below the MDA without establishing visual contact with the required references and using the GPWS to approach the ground.
Findings as to Risks:
1. The operations manager did not effectively supervise air operations.
2. Transport Canada did not detect the irregularities that compromised the safety of the flight before the occurrence.
3. Régionnair had not developed GPWS SOPs for non-precision approaches.
Other Findings:
1. The GPWS 'MINIMUMS' alarm sounded at a height that did not leave the captain time to initiate pull-up and avoid striking the ground because of the aircraft=s rate of descent and other flight
parameters.
2. Neither the captain nor the first officer had received PDM training or CRM training.
3. At the time of the approach, the ceiling and visibility unofficially reported by the AAU were below the minima published on the approach chart.
4. The decision to make the approach was consistent with existing regulations because runway 02/20 was not under an approach ban.
5. Some Régionnair pilots would descend below the MDA and use the GPWS to approach the ground if conditions made it impossible to establish visual contact with the required references.
Final Report:

Crash of a Britten-Norman BN-2A-26 Islander off Baie-Comeau: 7 killed

Date & Time: Dec 7, 1998 at 1111 LT
Type of aircraft:
Operator:
Registration:
C-FCVK
Flight Phase:
Survivors:
Yes
Schedule:
Baie-Comeau – Rimouski
MSN:
2028
YOM:
1981
Flight number:
ASJ501
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
1000
Captain / Total hours on type:
400.00
Aircraft flight hours:
9778
Circumstances:
Air Satellite=s Flight 501 was scheduled to fly from the airport at Baie-Comeau, Quebec, to Rimouski. After a five-hour delay because of adverse weather conditions, the Britten-Norman aircraft, serial number 2028, took off at 1109 eastern standard time. Eight passengers and two pilots were on board. The reported ceiling was 800 feet, the sky was obscured, and visibility was 0.5 statute mile in moderate snow showers. Shortly after take-off, the aircraft, which was climbing at approximately 500 feet above sea level, pitched up suddenly and became unstable when the flaps were retracted while entering the cloud layer. The pilot-in-command pushed the control column down to level the aircraft. After deciding that the aircraft could not safely continue the flight, he began turning left to return to Baie-Comeau. While turning, the aircraft rolled rapidly to the left and began to dive. The aircraft crashed into the St. Lawrence River approximately 0.5 nautical mile from shore and less than 1 nautical mile from the airport. Four passengers were fatally injured in the crash. Two passengers died while awaiting rescue, which came 98 minutes after take-off. The body of the co-pilot was carried away by the current and has not been recovered. The pilot-in-command and two passengers sustained serious injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The aircraft took off with contaminated surfaces, without an inspection by the pilot-in-command. This contamination contributed to reducing the aircraft' performance and to the subsequent stall.
2. At take-off, the aircraft was more than 200 pounds over the maximum allowable take-off weight. This added weight contributed to reducing the aircraft's performance.
3. During the initial climbout, the pilot-in-command did not follow the recommended procedure when he entered an area of wind shear. Consequently, the aircraft lost more speed, contributing to the stall.
4. Insufficient altitude was available for the pilot to recover from the stall and avoid striking the water.
5. The co-pilot's shoulder harness was not installed properly. The co-pilot received serious head injuries because she was not restrained.
Findings as to Risk
1. The crew's lack of experience in the existing conditions was not conducive to effective decision making during the pre-flight planning and the flight.
2. The stall warning system was defective and, in other circumstances, could not have alerted the crew of an impending stall.
3. The crew did not transmit an emergency message after the pilot-in-command decided to return to Baie-Comeau for landing. This lack of a message delayed the rescue operation.
4. The emergency signal was not received by the Mont-Joli Flight Service Station because the Baie-Comeau remote communications outlet (RCO) was not equipped with the 121.5 MHz emergency frequency. The RCO was not required to be equipped with the emergency frequency.
5. The emergency locator transmitter (ELT) was not installed in accordance with Britten-Norman's instructions. The ELT's installation on the floor of the aircraft increased the risk of damage.
6. Transport Canada did not comply with its established audit standards for regulatory audits of the operator, thus increasing the risk that training and operational deficiencies would not be identified.
7. The emergency signal probably ceased after the ELT was ejected from its mounting plate and the antenna connection contacted the water. The ejection contributed to reducing the signal and
prevented the SARSAT (search and rescue satellite-aided tracking) system from validating the
8. One of the occupants might have had a greater chance of survival had lifejackets been on-board the aircraft. Existing regulations did not require life jackets to be carried on board.
9. The aircraft had numerous mechanical deficiencies that should have been detected by Air Satellite's staff.
10. According to the Baie-Comeau airport emergency plan, a helicopter could be used only after confirmation of a crash in water. The emergency response time was therefore longer than it could
have been.
11. The configuration of the instrument panel made it difficult to read and interpret the flight instruments from the co-pilot's seat.
12. Air Satellite's manual of standard operating procedures did not promote effective crew coordination.
13. The pilot-in-command and the co-pilot had not taken courses in crew resource management or pilot decision making. These courses would have promoted effective crew coordination but were not required under existing regulations.
14. The high turnover of flight personnel and the repeated changes in the position of company chief pilot did not allow adequate supervision of operations.
Final Report:

Crash of an Avro 748-335-2A in Iqaluit

Date & Time: Dec 3, 1998 at 1536 LT
Type of aircraft:
Operator:
Registration:
C-FBNW
Flight Phase:
Survivors:
Yes
Schedule:
Iqaluit - Igloolik
MSN:
1759
YOM:
1978
Flight number:
FAB802
Location:
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
800.00
Copilot / Total flying hours:
2143
Copilot / Total hours on type:
117
Circumstances:
At approximately 1536 eastern standard time, First Air flight 802, a Hawker Siddeley HS-748-2A, serial number 1759, was on a scheduled flight from Iqaluit to Igloolik, Nunavut. On board were two flight crew, one flight attendant, one loadmaster, and three passengers. During the take-off run on runway 36, at the rotation speed (VR), the captain rotated the aircraft; however, the aircraft did not get airborne. Approximately seven seconds after VR, the captain called for and initiated a rejected take-off. The aircraft could not be stopped on the runway, and the nose-wheel gear collapsed as the aircraft rolled through the soft ground beyond the end of the runway. The aircraft hit the localizer antenna and continued skidding approximately 700 feet. It came to rest in a ravine in a nose-down attitude, approximately 800 feet off the declared end of the runway. The flight attendant initiated an evacuation through the left, main, rear cabin door. The two pilots evacuated the aircraft through the cockpit windows and joined the passengers and the flight attendant at the rear of the aircraft. The flight attendant was slightly injured during the sudden deceleration of the aircraft. The aircraft was substantially damaged.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The captain rejected the take-off at a speed well above the engine-failure recognition speed (V1) with insufficient runway remaining to stop before the end of the runway.
2. The far-forward position of the centre of gravity contributed to the pilot not rotating the aircraft to the normal take-off attitude.
3. The aircraft never achieved the required pitch for take-off. The captain=s inability to accurately assess the pitch attitude was probably influenced by the heavier than normal elevator control forces and the limited nighttime visual references.
4. The loadmaster did not follow the company- and Transport Canada-approved procedures to evaluate the excess baggage added to the aircraft, which led to a discrepancy of 450 pounds and a C of G position further forward than expected.
5. The performance analysis suggested that the aircraft was under-rotated as a result of a forward C of G loading and the generated lift never exceeded the aircraft=s weight during the take-off attempt.
Findings as to Risk:
1. The aircraft was approximately 200 pounds over maximum gross take-off weight.
2. The aircraft accelerated more slowly than normal, probably because of the snow on the runway.
3. Although atmospheric conditions were conducive to contamination and the aircraft was not de-iced, it could not be determined if contamination was present or if it degraded the aircraft performance during the attempted take-off.
4. Water methanol was not used for the occurrence take-off. Use of water methanol may have reduced the consequences of the rejected take-off.
5. The captain did not call for the overrun drill, and none of the items on the checklist were covered by the crew.
6. The co-pilot did not follow the emergency checklist and call air traffic control to advise of the rejected take-off or call over the public address system to advise the passengers to brace.
7. The aircraft lost all its electrical systems during the impact with the large rocks, rendering the radios unserviceable.
8. No HS-748 simulator exists that could be used to train pilots on the various take-off and rejected take-off scenarios.
9. There was confusion regarding the aircraft=s location. The flight service station, fire trucks, and intervening teams were not using an available grid map for orientation.
10. There is a risk associated with not de-icing aircraft before take-off in weather conditions such as those on the day of the accident.
11. There is a risk associated with not calculating the WAT limit and performance of an aircraft during an engine-out procedure in an environment with obstacles.
Other Findings
1. The aircraft=s brakes, anti-skid system, and tires functioned properly throughout the rejected take-off.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Victoria: 2 killed

Date & Time: Nov 23, 1998 at 0030 LT
Type of aircraft:
Operator:
Registration:
N9352B
Flight Type:
Survivors:
No
Schedule:
Vancouver - Victoria
MSN:
208-0061
YOM:
1987
Flight number:
RXX434
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1653
Captain / Total hours on type:
400.00
Copilot / Total flying hours:
120
Aircraft flight hours:
6717
Circumstances:
Regency Express Air Operations Flight 434, a Cessna 208 Caravan (serial number 208B0061), was en route from Vancouver International Airport to Victoria International Airport, British Columbia, on a night visual flight rules (VFR) flight when it collided with trees on Saltspring Island, about five nautical miles (nm) north of the Victoria International Airport. The aircraft broke apart on impact and a post-crash fire occurred. The two pilots, who were the sole occupants of the aircraft, sustained fatal injuries, and the aircraft was destroyed. The accident occurred at 0030 Pacific standard time (PST).
Probable cause:
Findings as to Causes and Contributing Factors:
A. Although weather information was available by radio from the Vancouver FSS specialists or from the Victoria Terminal controllers, there is no indication that the pilots requested weather updates from either of these units.
B. The crew of RXX434 would have encountered the lower ceiling in the vicinity of Beaver Point. This lower layer of cloud would have restricted the crew's view of the ground lighting and reduced the ambient lighting available to navigate by visual means.
C. With the loss of ground references, it is unlikely that the crew would have been able to perceive the divergence of the aircraft's flight path away from its intended track by visual means.
D. The crew was unable to maintain separation between the aircraft and the terrain by visual means.
E. The published VFR arrival and departure routes for Victoria were not consistent with obstacle clearance requirements for commercial operators.
F. Regency Express Air Operations' crew manual suggested an en route altitude of 1,500 feet for this particular flight. That route and altitude combination is not consistent with published obstacle clearance requirements.
Other Findings:
1. At the time the crew completed their flight planning, the weather at the departure airport of Vancouver and the arrival airport of Victoria was suitable for a night VFR flight.
2. An amended terminal forecast for Victoria indicating the presence of a temporary ceiling at 2,000 feet asl was issued after the crew had completed their preflight planning activities.
3. The regulation requiring GPWS equipment does not apply to air taxi operations because the aircraft used in those operations do not meet weight or propulsion criteria.
Final Report:

Crash of a McDonnell Douglas MD-11 off Peggy's Cove: 229 killed

Date & Time: Sep 2, 1998 at 2231 LT
Type of aircraft:
Operator:
Registration:
HB-IWF
Flight Phase:
Survivors:
No
Schedule:
New York - Geneva
MSN:
48448
YOM:
1991
Flight number:
SR111
Country:
Crew on board:
14
Crew fatalities:
Pax on board:
215
Pax fatalities:
Other fatalities:
Total fatalities:
229
Captain / Total flying hours:
10800
Captain / Total hours on type:
900.00
Copilot / Total flying hours:
4800
Copilot / Total hours on type:
230
Aircraft flight hours:
36041
Aircraft flight cycles:
6400
Circumstances:
On 2 September 1998, Swissair Flight 111 departed New York, United States of America, at 2018 eastern daylight savings time on a scheduled flight to Geneva, Switzerland, with 215 passengers and 14 crew members on board. About 53 minutes after departure, while cruising at flight level 330, the flight crew smelled an abnormal odour in the cockpit. Their attention was then drawn to an unspecified area behind and above them and they began to investigate the source. Whatever they saw initially was shortly thereafter no longer perceived to be visible. They agreed that the origin of the anomaly was the air conditioning system. When they assessed that what they had seen or were now seeing was definitely smoke, they decided to divert. They initially began a turn toward Boston; however, when air traffic services mentioned Halifax, Nova Scotia, as an alternative airport, they changed the destination to the Halifax International Airport. While the flight crew was preparing for the landing in Halifax, they were unaware that a fire was spreading above the ceiling in the front area of the aircraft. About 13 minutes after the abnormal odour was detected, the aircraft’s flight data recorder began to record a rapid succession of aircraft systems-related failures. The flight crew declared an emergency and indicated a need to land immediately. About one minute later, radio communications and secondary radar contact with the aircraft were lost, and the flight recorders stopped functioning. About five and one-half minutes later, the aircraft crashed into the ocean about five nautical miles southwest of Peggy’s Cove, Nova Scotia, Canada. The aircraft was destroyed and there were no survivors.
Probable cause:
Findings as to Causes and Contributing Factors
1. Aircraft certification standards for material flammability were inadequate in that they allowed the use of materials that could be ignited and sustain or propagate fire. Consequently, flammable material propagated a fire that started above the ceiling on the right side of the cockpit near the cockpit rear wall. The fire spread and intensified rapidly to the extent that it degraded aircraft systems and the cockpit environment, and ultimately led to the loss of control of the aircraft.
2. Metallized polyethylene terephthalate (MPET)–type cover material on the thermal acoustic insulation blankets used in the aircraft was flammable. The cover material was most likely the first material to ignite, and constituted the largest portion of the combustible materials that contributed to the propagation and intensity of the fire.
3. Once ignited, other types of thermal acoustic insulation cover materials exhibit flame propagation characteristics similar to MPET-covered insulation blankets and do not meet the proposed revised flammability test criteria. Metallized polyvinyl fluoride–type cover material was installed in HB-IWF and was involved in the in-flight fire.
4. Silicone elastomeric end caps, hook-and-loop fasteners, foams, adhesives, and thermal acoustic insulation splicing tapes contributed to the propagation and intensity of the fire.
5. The type of circuit breakers (CB) used in the aircraft were similar to those in general aircraft use, and were not capable of protecting against all types of wire arcing events. The fire most likely started from a wire arcing event.
6. A segment of in-flight entertainment network (IFEN) power supply unit cable (1-3791) exhibited a region of resolidified copper on one wire that was caused by an arcing event. This resolidified copper was determined to be located near manufacturing station 383, in the area where the fire most likely originated. This arc was likely associated with the fire initiation event; however, it could not be determined whether this arced wire was the lead event.
7. There were no built-in smoke and fire detection and suppression devices in the area where the fire started and propagated, nor were they required by regulation. The lack of such devices delayed the identification of the existence of the fire, and allowed the fire to propagate unchecked until it became uncontrollable.
8. There was a reliance on sight and smell to detect and differentiate between odour or smoke from different potential sources. This reliance resulted in the misidentification of the initial odour and smoke as originating from an air conditioning source.
9. There was no integrated in-flight firefighting plan in place for the accident aircraft, nor was such a plan required by regulation. Therefore, the aircraft crew did not have procedures or training directing them to aggressively attempt to locate and eliminate the source of the smoke, and to expedite their preparations for a possible emergency landing. In the absence of such a firefighting plan, they concentrated on preparing the aircraft for the diversion and landing.
10. There is no requirement that a fire-induced failure be considered when completing the system safety analysis required for certification. The fire-related failure of silicone elastomeric end caps installed on air conditioning ducts resulted in the addition of a continuous supply of conditioned air that contributed to the propagation and intensity of the fire.
11. The loss of primary flight displays and lack of outside visual references forced the pilots to be reliant on the standby instruments for at least some portion of the last minutes of the flight. In the deteriorating cockpit environment, the positioning and small size of these instruments would have made it difficult for the pilots to transition to their use, and to continue to maintain the proper spatial orientation of the aircraft.
3.2 Findings as to Risk
1. Although in many types of aircraft there are areas that are solely dependent on human intervention for fire detection and suppression, there is no requirement that the design of the aircraft provide for ready access to these areas. The lack of such access could delay the detection of a fire and significantly inhibit firefighting.
2. In the last minutes of the flight, the electronic navigation equipment and communications radios stopped operating, leaving the pilots with no accurate means of establishing their geographic position, navigating to the airport, and communicating with air traffic control.
3. Regulations do not require that aircraft be designed to allow for the immediate de-powering of all but the minimum essential electrical systems as part of an isolation process for the purpose of eliminating potential ignition sources.
4. Regulations do not require that checklists for isolating smoke or odours that could be related to an overheating condition be designed to be completed in a time frame that minimizes the possibility of an in-flight fire being ignited or sustained. As is the case with similar checklists in other aircraft, the applicable checklist for the MD-11 could take 20 to 30 minutes to complete. The time required to complete such checklists could allow anomalies, such as overheating components, to develop into ignition sources.
5. The Swissair Smoke/Fumes of Unknown Origin Checklist did not call for the cabin emergency lights to be turned on before the CABIN BUS switch was selected to the OFF position. Although a switch for these lights was available at the maître de cabine station, it is known that for a period of time the cabin crew were using flashlights while preparing for the landing, which potentially could have slowed their preparations.
6. Neither the Swissair nor Boeing Smoke/Fumes of Unknown Origin Checklist emphasized the need to immediately start preparations for a landing by including this consideration at the beginning of the checklist. Including this item at the end of the checklist de-emphasizes the importance of anticipating that any unknown smoke condition in an aircraft can worsen rapidly.
7. Examination of several MD-11 aircraft revealed various wiring discrepancies that had the potential to result in wire arcing. Other agencies have found similar discrepancies in other aircraft types. Such discrepancies reflect a shortfall within the aviation industry in wire installation, maintenance, and inspection procedures.
8. The consequence of contamination of an aircraft on its continuing airworthiness is not fully understood by the aviation industry. Various types of contamination may damage wire insulation, alter the flammability properties of materials, or provide fuel to spread a fire. The aviation industry has yet to quantify the impact of contamination on the continuing airworthiness and safe operation of an aircraft.
9. Heat damage and several arcing failure modes were found on in-service map lights. Although the fire in the occurrence aircraft did not start in the area of the map lights, their design and installation near combustible materials constituted a fire risk.
10. There is no guidance material to identify how to comply with the requirements of Federal Aviation Regulation (FAR) 25.1353(b) in situations where physical/spatial wire separation is not practicable or workable, such as in confined areas.
11. The aluminum cap assembly used on the stainless steel oxygen line above the cockpit ceiling was susceptible to leaking or fracturing when exposed to the temperatures that were likely experienced by this cap assembly during the last few minutes of the flight. Such failures would exacerbate the fire and potentially affect crew oxygen supply. It could not be determined whether this occurred on the accident flight.
12. Inconsistencies with respect to CB reset practices have been recognized and addressed by major aircraft manufacturers and others in the aviation industry. Despite these initiatives, the regulatory environment, including regulations and advisory material, remains unchanged, creating the possibility that such “best practices” will erode or not be universally applied across the aviation industry.
13. The mandated cockpit voice recorder (CVR) recording time was insufficient to allow for the capture of additional, potentially useful, information.
14. The CVR and the flight data recorder (FDR) were powered from separate electrical buses; however, the buses received power from the same generator; this configuration was permitted by regulation. Both recorders stopped recording at almost the same time because of fire-related power interruptions; independent sources of aircraft power for the recorders may have allowed more information to be recorded.
15. Regulations did not require the CVR to have a source of electrical power independent from its aircraft electrical power supply. Therefore, when aircraft electrical power to the CVR was interrupted, potentially valuable information was not recorded.
16. Regulations and industry standards did not require quick access recorders (QAR) to be crash-protected, nor was there a requirement that QAR data also be recorded on the FDR. Therefore, potentially valuable information captured on the QAR was lost.
17. Regulations did not require the underwater locator beacon attachments on the CVR and the FDR to meet the same level of crash protection as other data recorder components.
18. The IFEN Supplemental Type Certificate (STC) project management structure did not ensure that the required elements were in place to design, install, and certify a system that included emergency electrical load-shedding procedures compatible with the MD-11 type certificate. No link was established between the manner in which the IFEN system was integrated with aircraft power and the initiation or propagation of the fire.
19. The Federal Aviation Administration (FAA) STC approval process for the IFEN did not ensure that the designated alteration station (DAS) employed personnel with sufficient aircraft-specific knowledge to appropriately assess the integration of the IFEN power supply with aircraft power before granting certification.
20. The FAA allowed a de facto delegation of a portion of their Aircraft Evaluation Group function to the DAS even though no provision existed within the FAA’s STC process to allow for such a delegation.
21. FAR 25.1309 requires that a system safety analysis be accomplished on every system installed in an aircraft; however, the requirements of FAR 25.1309 are not sufficiently stringent to ensure that all systems, regardless of their intended use, are integrated into the aircraft in a manner compliant with the aircraft’s type certificate.
22. Approach charts for the Halifax International Airport were kept in the ship’s library at the observer’s station and not within reach of the pilots. Retrieving these charts required both time and attention from the pilots during a period when they were faced with multiple tasks associated with operating the aircraft and planning for the landing.
23. While the SR Technics quality assurance (QA) program design was sound and met required standards, the training and implementation process did not sufficiently ensure that the program was consistently applied, so that potential safety aspects were always identified and mitigated.
24. The Swiss Federal Office for Civil Aviation audit procedures related to the SR Technics QA program did not ensure that the underlying factors that led to specific similar audit observations and discrepancies were addressed.
3.3 Other Findings
1. The Royal Canadian Mounted Police found no evidence to support the involvement of any explosive or incendiary device, or other criminal act in the initiation of the in-flight fire.
2. The 13-minute gap in very-high frequency communications was most likely the result of an incorrect frequency selection by the pilots.
3. The pilots made a timely decision to divert to the Halifax International Airport. Based on the limited cues available, they believed that although a diversion was necessary, the threat to the aircraft was not sufficient to warrant the declaration of an emergency or to initiate an emergency descent profile.
4. The flight crew were trained to dump fuel without restrictions and to land the aircraft in an overweight condition in an emergency situation, if required. 5. From any point along the Swissair Flight 111 flight path after the initial odour in the cockpit, the time required to complete an approach and landing to the Halifax International Airport would have exceeded the time available before the fire-related conditions in the aircraft cockpit would have precluded a safe landing.
6. Air conditioning anomalies have typically been viewed by regulators, manufacturers, operators, and pilots as not posing a significant and immediate threat to the safety of the aircraft that would require an immediate landing.
7. Actions by the flight crew in preparing the aircraft for landing, including their decisions to have the passenger cabin readied for landing and to dump fuel, were consistent with being unaware that an on-board fire was propagating.
8. Air traffic controllers were not trained on the general operating characteristics of aircraft during emergency or abnormal situations, such as fuel dumping.
9. Interactions between the pilots and the controllers did not affect the outcome of the occurrence.
10. The first officer’s seat was occupied at the time of impact. It could not be determined whether the captain’s seat was occupied at the time of impact.
11. The pilots shut down Engine 2 during the final stages of the flight. No confirmed reason for the shutdown could be established; however, it is possible that the pilots were reacting to the illumination of the engine fire handle and FUEL switch emergency lights. There was fire damage in the vicinity of a wire that, if shorted to ground, would have illuminated these lights.
12. When the aircraft struck the water, the electrically driven standby attitude indicator gyro was still operating at a high speed; however, the instrument was no longer receiving electrical power. It is unknown whether the information displayed at the time of impact was indicative of the aircraft attitude.
13. Coordination between the pilots and the cabin crew was consistent with company procedures and training. Crew communications reflected that the situation was not being categorized as an emergency until about six minutes prior to the crash; however, soon after the descent to Halifax had started, rapid cabin preparations for an imminent landing were underway.
14. No smoke was reported in the cabin by the cabin crew at any time prior to CVR stoppage; however, it is likely that some smoke would have been present in the passenger cabin during the final few minutes of the flight. No significant heat damage or soot build-up was noted in the passenger seating areas, which is consistent with the fire being concentrated above the cabin ceiling.
15. No determination could be made about the occupancy of any of the individual passenger seats. Passenger oxygen masks were stowed at the time of impact, which is consistent with standard practice for an in-flight fire.
16. No technically feasible link was found between known electromagnetic interference/high-intensity radiated fields and any electrical discharge event leading to the ignition of the aircraft’s flammable materials.
17. Regulations did not require the recording of cockpit images, although it is technically feasible to do so in a crash-protected manner. Confirmation of information, such as flight instrument indications, switch position status, and aircraft system degradation, could not be completed without such information.
18. Portions of the CVR recording captured by the cockpit area microphone were difficult to decipher. When pilots use boom microphones, deciphering internal cockpit CVR communications becomes significantly easier; however, the use of boom microphones is not required by regulation for all phases of flight. Nor is it common practice for pilots to wear boom microphones at cruise altitude.
19. Indications of localized overheating were found on cabin ceiling material around overhead aisle and emergency light fixtures. It was determined that the overhead aisle and emergency light fixtures installed in the accident aircraft did not initiate the fire; however, their design created some heat-related material degradation that was mostly confined to the internal area of the fixtures adjacent to the bulbs.
20. At the time of this occurrence, there was no requirement within the aviation industry to record and report wiring discrepancies as a separate and distinct category to facilitate meaningful trend analysis in an effort to identify unsafe conditions associated with wiring anomalies.
Final Report:

Crash of an Avro 748-310-2A LFD in Kasabonika

Date & Time: Aug 6, 1998 at 1600 LT
Type of aircraft:
Operator:
Registration:
C-GTAD
Flight Type:
Survivors:
Yes
Schedule:
Pickle Lake - Kasabonika
MSN:
1750
YOM:
1977
Flight number:
WSG804
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20600
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
3000
Copilot / Total hours on type:
500
Aircraft flight hours:
12310
Circumstances:
Wasaya Airways Ltd. Flight 804, a Hawker Siddeley 748-2A, serial number 1750, landed at Kasabonika, Ontario, on a freight flight from Pickle Lake, Ontario. During the landing roll, the aircraft could not be stopped and overran the runway by about 450 feet. The captain, the first officer and one of the freight handlers suffered minor injuries; the other freight handler was not injured. The aircraft was destroyed.
Probable cause:
The aircraft was landed at a point from which it could not be stopped under the prevailing conditions. Contributing to the occurrence were the lack of immediate propeller ground fine pitch and the choice of runway 03 as the landing runway. A possible contributing factor was the inappropriate information in the then-current runway analysis manual.
Final Report:

Crash of a De Havilland DHC-2 Beaver near Kincolith: 5 killed

Date & Time: Aug 4, 1998 at 1758 LT
Type of aircraft:
Operator:
Registration:
C-FOCJ
Survivors:
No
Schedule:
Prince Rupert - Kincolith
MSN:
39
YOM:
1949
Flight number:
H3709
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1700
Captain / Total hours on type:
1250.00
Aircraft flight hours:
22369
Circumstances:
The float-equipped de Havilland DHC-2 Beaver, serial number 0039, departed Prince Rupert, British Columbia, at 1719 Pacific daylight time on a visual flight rules flight to Kincolith, British Columbia, with the pilot and four passengers on board. When the aircraft arrived at Kincolith at about 1750, witnesses watched it carry out three low approaches to the water landing area, each time descending to a few feet above the water before climbing away. On the fourth approach, at about 1758, the aircraft touched down, apparently in a controlled manner, and skipped on the water surface. The floats then dug into the water followed by the right wing, which was severed from the fuselage on water impact. The aircraft quickly overturned and came to rest inverted with only the bottom of the floats visible. Several members of the village community, who had been waiting for the aircraft on the Government Dock, rushed to the sunken aircraft in small boats but were unable to rescue the pilot or passengers inside the submerged cabin. The five occupants drowned in the accident, and the aircraft was substantially damaged.
Probable cause:
On touchdown, the float(s) struck the water and caused a flying attitude that the pilot could not control before the right wing dug in and the aircraft overturned. Contributing to the accident were conflicting wind and water conditions at the time of the occurrence.
Final Report:

Crash of a Swearingen SA226AC Metro II in Montreal: 11 killed

Date & Time: Jun 18, 1998 at 0728 LT
Type of aircraft:
Operator:
Registration:
C-GQAL
Survivors:
No
Schedule:
Montreal - Peterborough
MSN:
TC-233
YOM:
1977
Flight number:
PRO420
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
6515
Captain / Total hours on type:
4200.00
Copilot / Total flying hours:
2730
Copilot / Total hours on type:
93
Aircraft flight hours:
28931
Circumstances:
On the morning of 18 June 1998, Propair 420, a Fairchild-Swearingen Metro II (SA226-TC), C-GQAL, took off for an instrument flight rules flight from Dorval, Quebec, to Peterborough, Ontario. The aircraft took off from Runway 24 left (L) at 0701 eastern daylight time. During the ground acceleration phase, the aircraft was pulling to the left of the runway centreline, and the right rudder was required to maintain take-off alignment. Two minutes later, Propair 420 was cleared to climb to 16 000 feet above sea level (asl). At 0713, the crew advised the controller of a decrease in hydraulic pressure and requested to return to the departure airport, Dorval. The controller immediately gave clearance for a 180° turn and descent to 8000 feet asl. During this time, the crew indicated that, for the moment, there was no on-board emergency. The aircraft initiated its turn 70 seconds after receiving clearance. At 0713:36, something was wrong with the controls. Shortly afterward came the first perceived indication that engine trouble was developing, and the left wing overheat light illuminated about 40 seconds later. Within 30 seconds, without any apparent checklist activity, the light went out. At 0718:12, the left engine appeared to be on fire, and it was shut down. Less than one minute later, the captain took the controls. The flight controls were not responding normally: abnormal right aileron pressure was required to keep the aircraft on heading. At 0719:19, the crew advised air traffic control (ATC) that the left engine was shut down, and, in response to a second suggestion from ATC, the crew agreed to proceed to Mirabel instead of Dorval. Less than a minute and a half later, the crew informed ATC that flames were coming out of the 'engine nozzle'. Preparations were made for an emergency landing, and the emergency procedure for manually extending the landing gear was reviewed. At 0723:10, the crew informed ATC that the left engine was no longer on fire, but three and a half minutes later, they advised ATC that the fire had started again. During this time, the aircraft was getting harder to control in roll, and the aileron trim was set at the maximum. Around 0727, when the aircraft was on short final for Runway 24L, the landing gear lever was selected, but only two gear down indicator lights came on. Near the runway threshold, the left wing failed upwards. The aircraft then rotated more than 90° to the left around its longitudinal axis and crashed, inverted, on the runway. The aircraft immediately caught fire, slid 2500 feet, and came to rest on the left side the runway. When the aircraft crashed, firefighters were near the runway threshold and responded promptly. The fire was quickly brought under control, but all occupants were fatally injured.
Probable cause:
Findings as to Causes and Contributing Factors:
- The crew did not realize that the pull to the left and the extended take-off run were due to the left brakes' dragging, which led to overheating of the brake components.
- Dragging of the left brakes was most probably caused by an unidentified pressure locking factor upstream of the brakes on take-off. The dragging caused overheating and leakage, probably at one of the piston seals that retain the brake hydraulic fluid.
- When hydraulic fluid leaked onto the hot brake components, the fluid caught fire and initiated an intense fire in the left nacelle, leading to failure of the main hydraulic system.
- When the L WING OVHT light went out, the overheating problem appeared corrected; however, the fire continued to burn.
- The crew never realized that all of the problems were associated with a fire in the wheel well, and they did not realize how serious the situation was.
- The left wing was weakened by the wing/engine fire and failed, rendering the aircraft uncontrollable.
Findings as to Risk:
- Numerous previous instances of brake overheating or fire on SA226 and SA227 aircraft had the potential for equally tragic consequences. Not all crews flying this type of aircraft are aware of its history of numerous brake overheating or fire problems.
- The aircraft flight manual and the emergency procedures checklist provide no information on the possibility of brake overheating, precautions to prevent brake overheating, the symptoms that could indicate brake problems, or actions to take if overheated brakes are suspected.
- More stringent fire-blocking requirements would have retarded combustion of the seats, reducing the fire risk to the aircraft occupants.
- A mixture of the two types of hydraulic fluid lowered the temperature at which the fluid would ignite, that is, below the flashpoint of pure MIL-H-83282 fluid.
- The aircraft maintenance manual indicated that the two hydraulic fluids were compatible but did not mention that mixing them would reduce the fire resistance of the fluid.
Other Findings:
- The master cylinders were not all of the same part number, resulting in complex linkage and master cylinder adjustments, complicated overall brake system functioning, and difficult troubleshooting of the braking system. However, there was no indication that this circumstance caused residual brake pressure.
- The latest recommended master cylinders are required to be used only with specific brake assembly part numbers, thereby simplifying adjustments, functioning, and troubleshooting.
- Although the emergency checklist for overheating in the wing required extending the landing gear, the crew did not do this because the wing overheat light went out before the crew initiated the checklist.
- The effect of the fire in the wheel well made it difficult to move the ailerons, but the exact cause of the difficulty was not determined.
Final Report: