Crash of a Beechcraft 65-A90 King Air off Port-de-Paix

Date & Time: Nov 29, 1998 at 0815 LT
Type of aircraft:
Operator:
Registration:
N171TE
Flight Phase:
Survivors:
Yes
Schedule:
North Perry – Cap Haïtien
MSN:
LJ-180
YOM:
1966
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4200
Aircraft flight hours:
10119
Circumstances:
According to the pilot, during pre-flight examination of the airplane performed the evening prior to the flight, the fuel gauges read 'around' 3/4 full. Visual examination of the tanks by the pilot revealed the tanks were not full but he believed the quantity was more than adequate to conduct his flight. While at 17000 feet MSL and approximately 60 miles from his destination, both the left engine and right engine suffered fuel exhaustion. After declaring an emergency, the pilot ditched the airplane in the Atlantic Ocean about ten miles off the coast of Isle De La Tortue, Haiti. The pilot received minor injuries and was rescued by the United States Coast Guard at 1730 the same day. Based on data obtained from the Raytheon Aircraft Company and 3/4 full fuel tanks, the total available flight time for this flight was approximately 4.00 hours. The actual flight time for this flight was 3.25 hours.
Probable cause:
Inadequate preflight planning/preparation by the pilot, which resulted in fuel exhaustion due to an inadequate supply of fuel. A factor was the terrain ( water).
Final Report:

Crash of a Cessna 414A Chancellor off Mattapoisett: 1 killed

Date & Time: Nov 20, 1998 at 1220 LT
Type of aircraft:
Operator:
Registration:
N6820J
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Hyannis - New Bedford
MSN:
414A-0671
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3458
Aircraft flight hours:
2675
Circumstances:
The airplane was level at 2,000 feet, in instrument meteorological conditions, when the pilot reported 'we've just lost our ahh artificial horizon.' About 5 minutes later, air traffic control lost radar contact, and communications with the airplane. A witness about 1 mile north of the accident site stated he heard the sound of engine noise coming from the water and he described the sound as loud and constant. The sound lasted for about 30 seconds and was followed by an 'explosive collision/impact sound.' He further stated he walked to the shore and attempted to locate the source of the sound, but 'because of the fog, I couldn't see anything at all.' The airplane was located in about 25 feet of water, and was scattered over a 150 to 200 foot area. The recovered wreckage consisted of both engines, parts of the airplane's left wing, empennage, fuselage, seats, and interior. The airplane's attitude indicator was not recovered. A faint needle impression was found on the face of the airplane's vertical speed indicator between minus 2,500 and 3,000 feet per minute. Examination of the left and right vacuum pumps did not reveal any malfunctions or failures.
Probable cause:
The pilot's failure to maintain control of the airplane after an undetermined failure of the airplane's attitude indicator. A factor in this accident was fog.
Final Report:

Crash of a Rockwell Shrike Commander 500S off Horn Island

Date & Time: Oct 21, 1998 at 0940 LT
Registration:
VH-YJT
Survivors:
Yes
Schedule:
Boigu Island - Horn Island
MSN:
500-3089
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2045
Captain / Total hours on type:
79.00
Circumstances:
A Shrike Commander departed Horn Island on a charter flight to Saibai and Boigu Islands in accordance with the visual flight rules (VFR). The flight to Saibai took 32 minutes, and a further 13 minutes to Boigu Island. The aircraft then departed Boigu to return to Horn Island with an expected flight time of 35 minutes. The pilot reported that he had maintained 5,500 ft until commencing descent at 35 NM from Horn Island. He tracked to join final approach to runway 14 by 5 NM, reducing power at 1,500 ft. At 5 NM from the runway, the pilot extended the landing gear and approach flap and commenced a long final approach. When the aircraft was approximately 3 NM from the runway both engines commenced to surge, with the aircraft initially yawing to the right. The pilot commenced engine failure procedures and retracted the flaps. He tried a number of times to determine which engine was losing power by retarding the throttle for each engine, before deciding that the right engine was failing. The pilot shut down that engine and feathered the propeller. A short time later, when the aircraft was approximately 200 ft above the water, the left engine also lost power. The pilot established the aircraft in a glide, advised the passengers to prepare for a ditching, and transmitted a MAYDAY report on the flight service frequency before the aircraft contacted the sea. The aircraft quickly filled with water and settled on the seabed. All five occupants were able to escape and make their way ashore.
Probable cause:
The following findings were identified:
- The pilot was correctly licensed and qualified to operate the flight as a VFR charter operation.
- The aircraft was dispatched with an unusable fuel quantity indicator.
- The right engine fuel control unit was worn and allowed additional fuel through the system, increasing fuel consumption by approximately 6 L/hr.
- Inappropriate fuel consumption rates were used for flight planning.
- The aircraft fuel log contained inaccuracies that resulted in a substantial underestimation of the total fuel used.
- At the time of the occurrence, there was no useable fuel in the aircraft fuel system.
- Although the pilot met the Civil Aviation Safety Authority criteria to fulfil his role as chief pilot, he did not have the expertise to effectively ensure the safety of company flight operations.
Final Report:

Crash of an Antonov AN-24RV off Iranativu Island: 55 killed

Date & Time: Sep 29, 1998 at 1354 LT
Type of aircraft:
Operator:
Registration:
EW-46465
Flight Phase:
Survivors:
No
Schedule:
Palaly - Colombo
MSN:
27307901
YOM:
1972
Flight number:
LNS602
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
48
Pax fatalities:
Other fatalities:
Total fatalities:
55
Aircraft flight hours:
42442
Circumstances:
The aircraft departed Palaly Airport at 1340LT on a schedule flight to Colombo, carrying 48 passengers and seven crew members. While climbing to an altitude of 8,000 feet, the captain contacted ATC and reported a cabin depressurization following an explosion. The aircraft entered an uncontrolled descent and crashed in the sea some 2 km south of Iranativu Island, 45 km south of Jaffna. The aircraft disintegrated on impact and all 55 occupants were killed. About 30% of the debris were found in May 2013.
Probable cause:
It was determined that the aircraft was shot down by a LTTE (Liberation Tigers of Tamil Eelam) rebels surface-to-air missile.

Crash of a GAF Nomad N.22S off Mona Island: 1 killed

Date & Time: Sep 18, 1998 at 1428 LT
Type of aircraft:
Operator:
Registration:
N6305U
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Aguadilla - Willemstad
MSN:
160
YOM:
1983
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4286
Captain / Total hours on type:
982.00
Aircraft flight hours:
2983
Circumstances:
Two U.S. Customs Service airplanes collided in formation cruise flight while being evacuated from Borinquen, Puerto Rico, to Curacao, Dutch Antilles, due to an approaching hurricane. While in cruise flight at 6,500 ft. msl, N6305U maneuvered closer to the lead airplane, N6302W, to take some photographs. Several minutes later, N6305U's right side of the vertical stabilizer collided with the left side of the nose of N6302W. N6305U was ditched while on short final to an airstrip due to a lack of airplane controllability, while N6302W returned to Borinquen and landed without incident. Prior to departure, the crewmembers of both airplanes were directed to fly as a flight of two. Neither of the second-in-commands (SICs) of either airplane had any previous formation flying training, nor was it approved for the flight. Interviews with U.S. Customs personnel revealed that formation flight occurred, as did photographs taken from the SIC aboard N6305U during the accident flight. The U.S. Customs Service required two pilots to operate the airplane due to mission equipment installation.
Probable cause:
The failure of the pilot-in-command of N6305U to maintain physical clearance from the other aircraft (N6302W). Contributing factors were the inadequate visual lookout of all four pilots involved.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain off Homer

Date & Time: Sep 7, 1998 at 1513 LT
Registration:
N4072A
Flight Phase:
Survivors:
Yes
Schedule:
Homer - Anchorage
MSN:
31-8152016
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9070
Captain / Total hours on type:
2000.00
Aircraft flight hours:
4133
Circumstances:
The pilot departed from an intersection 2,100 feet from the approach end of the 6,700 feet long runway. Immediately after takeoff the right engine failed. The pilot told the NTSB investigator-in-charge that he feathered the right propeller, and began a wide right turn away from terrain in an attempt to return to the airport. He stated the airspeed did not reach 90 knots, the airspeed and altitude slowly decayed, and the airplane was ditched into smooth water. After recovery, the cowl flaps were found in the 50% open position. No anomalies were found with the fuel system. The airplane departed with full fuel tanks, at a takeoff weight estimated at 6,606 pounds. The right engine was disassembled and no mechanical anomalies were noted. The best single engine rate of climb airspeed is 106 knots, based on cowl flaps closed, and a five degree bank into the operating engine.
Probable cause:
A total loss of power in the right engine for undetermined reasons.
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 a Cessna 402C off Halfmoon Bay: 5 killed

Date & Time: Aug 19, 1998 at 1643 LT
Type of aircraft:
Operator:
Registration:
ZK-VAC
Flight Phase:
Survivors:
Yes
Schedule:
Halfmoon Bay - Invercargill
MSN:
402C-0512
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
14564
Captain / Total hours on type:
27.00
Aircraft flight hours:
13472
Circumstances:
Surviving passengers reported that en route from Stewart Island to Invercargill there were symptoms of a righthand engine failure, which was corrected by the pilot's manipulation of floor-mounted fuel tank selectors. Shortly afterwards, both engines stopped. The pilot broadcast a Mayday and advised the passengers that they would be ditching. A successful ditching was carried out approximately 12 NM south of Invercargill. All occupants escaped from the aircraft, however, four persons exited without life jackets. The pilot entered the cabin but was unable to locate more before the aircraft sank. Rescuers reached the scene about an hour after the ditching only to find that all those without life jackets had perished, as had a young boy who was wearing one.
Probable cause:
A TAIC investigation found that there was no evidence of any component malfunction that could cause a double engine failure, although due to seawater damage the pre-impact condition of most fuel quantity system components could not be verified. Both fuel tank selectors were positioned to the lefthand tank, and it is probable that fuel starvation was the cause of the double engine failure. Company procedures for the Cessna 402 lacked a fuel quantity monitoring system to supplement fuel gauge indications. Dipping of the tanks was not a feasible option. Company pilots believed that the aircraft was fitted with low-fuel quantity warning lights, which was not the case. As three pilots believed the gauges indicated sufficient fuel was on board before the preceding round trip to the island, exhaustion may have followed an undetermined fuel indicating system malfunction. The failure of the company to require the use of operational flight logs, and other deficiencies in record keeping, were identified in the TAIC report. The much-publicised misunderstanding about the ditching location was not considered by the TAIC report to have affected the outcome of the rescue, but provides an example of the continued importance of using the phonetic alphabet in radiotelephony. A safety recommendation that operators use a fuel-quantity monitoring system to supplement fuel gauge indications was also made by the TAIC report.
Final Report:

Crash of a PZL-Mielec AN-2 off Lunacharski

Date & Time: Aug 19, 1998
Type of aircraft:
Registration:
RA-06196
Flight Phase:
Survivors:
Yes
Schedule:
Togliatti - Togliatti
MSN:
1G43-15
YOM:
1978
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane departed Togliatti on a local skydiving mission, carrying 10 skydivers and two pilots. While flying over the region of Lunacharski, all skydivers jumped out but two of them fell in the Volga River and drowned. The crew elected to take part to the SAR operations and wanted to show the location to the rescuers but descended too low over water. The aircraft stuck the water surface and crashed. Both pilots were injured and the aircraft was destroyed.
Probable cause:
The crew misjudged the distance with the water surface and descended too low.

Crash of a PZL-Mielec AN-2R in Yakutia

Date & Time: Aug 14, 1998
Type of aircraft:
Operator:
Registration:
RA-40681
Flight Phase:
MSN:
1G214-39
YOM:
1985
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances in a river bed somewhere in Yakutia. Occupant's fate unknown.