Crash of a BAe 146-100 in Cap de Trois Fourhces: 38 killed

Date & Time: Sep 25, 1998 at 0750 LT
Type of aircraft:
Operator:
Registration:
EC-GEO
Survivors:
No
Site:
Schedule:
Málaga – Melilla
MSN:
E1007
YOM:
1983
Flight number:
PV4101
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
34
Pax fatalities:
Other fatalities:
Total fatalities:
38
Captain / Total flying hours:
7818
Captain / Total hours on type:
1648.00
Copilot / Total flying hours:
3501
Copilot / Total hours on type:
408
Circumstances:
Following an uneventful flight from Málaga-Pablo Ruiz Picasso Airport, the crew initiated the descent to Melilla Airport in marginal weather conditions. After being cleared to descend to 7,000 feet from Sevilla ATC, the crew contacted Melilla Tower and was cleared to descend to 5,000 feet. Melilla Tower then reported that runway 33 was in use and reported wind at 270° at 5 knots, visibility 8 km with few clouds at 1,000 feet. At 0645LT the copilot reported that they were at 22 nm at an altitude of 3,000 feet. From this point, the crew descended below the minimum safe altitude of 4,000 feet and crossed the coast line in limited visibility due to low clouds. At 0749 and 52 seconds, the GPWS alarm sounded twice in the cockpit. Few seconds later, the aircraft struck the slope of a mountain located near Cap de Trois Fourche. The aircraft disintegrated on impact and all 38 occupants were killed.
Probable cause:
Given the facts and analysis conducted, the Commission concluded that the accident was caused by a collision with terrain in IMC conditions. This confirms the hypothesis put forward by members of the committee of investigation from the beginning of their investigations, it is a type of CFIT accident (collision with the ground without loss of control) due to the combination of the following factors:
- Non application of the arrival procedure, including descending below the minimum safe altitude,
- Inadequate crew coordination,
- Non application of company procedures regarding the GPWS alarm.
Final Report:

Crash of a Boeing 737-524 in Guadalajara

Date & Time: Sep 16, 1998 at 2253 LT
Type of aircraft:
Operator:
Registration:
N20643
Survivors:
Yes
Schedule:
Houston - Guadalajara
MSN:
28904
YOM:
1997
Flight number:
CO475
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
102
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On September 16, 1998, at 2253 central daylight time, a Boeing 737-524 transport airplane, N20643, operating as Continental Airlines flight 475, was substantially damaged following a loss of control during the landing roll at the Don Miguel Hidalgo International Airport near Guadalajara, Mexico. The 2 airline transport rated pilots, the 4 flight attendants, and the 102 passengers were not injured. The airplane was owned and operated by Continental Airlines of Houston, Texas, under Title 14 CFR Part 121. Night visual meteorological conditions prevailed for the scheduled international passenger-cargo flight for which an IFR flight plan was filed. The flight was dispatched from the George Bush International Airport near Houston, Texas, at 2056, for the two hour flight to Guadalajara, State of Jalisco, Mexico. The flight's scheduled arrival time was 2254. After executing a missed approach on their first ILS approach to runway 28, the flight was vectored for a second approach to runway 28. The second approach was reported by both pilots to be uneventful; however, after touchdown, the aircraft drifted to the left side of the runway. The left main landing gear exited the hard surface of the runway approximately 2,700 feet from the landing threshold and eventually all 3 landing gears exited the 197 foot wide asphalt runway. The first officer, who was flying the airplane, stated that he never felt any anti-skid cycling during the landing roll and did not feel any "radical braking" which was expected with the auto-brake in the number 3 setting. The airplane's nose landing gear collapsed resulting in structural damage to the avionics bay, the forward baggage compartment, the engine cowlings and pylons. Both engines incurred FOD. A total of 15 runway lights on the southern edge of runway 28 were found either sheared or knocked down. The tower operator reported that intermittent heavy rain showers accompanied with downdrafts and strong winds associated with a thunderstorm northeast of the airport prevailed throughout the area at the time of the accident. The two transport category airplanes that landed prior to Continental flight 475 reported windshear on final approach. The winds issued to Continental 475 by the tower while on short final were from 360 degrees at 20 knots, gusting to 40 knots. Prior to the arrival of Continental flight 475, an Aeromexico MD-82, drifted to the left side of the runway to the point where the left main gear exited the hard surface of the runway. The pilot of that flight stated that he used differential power to regain control and bring the aircraft back on the runway. The flight taxied to the gate without further incident.

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 Antonov AN-26B near Malanje: 24 killed

Date & Time: Sep 2, 1998
Type of aircraft:
Operator:
Registration:
RA-26028
Flight Phase:
Survivors:
No
Schedule:
Luanda - Malanje
MSN:
104 08
YOM:
1980
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
24
Circumstances:
Crashed in the Angolan province of Malanje about 30 minutes after takeoff from Luanda-4 de Fevereiro Airport, probably after being shot down by UNITA rebels. The pilot reported an engine fire and that he was going to attempt an emergency landing at Malanje. About 3 minutes later, the pilot reported that they were going to attempt an immediate landing straight ahead. This was the last contact with the crew. It was reported that at impact the right propeller was feathered, the landing gear was up and flaps were deployed at 25°. All four crew members and 20 passengers were killed. The wreckage was found in an isolated area in 2003 only.

Crash of a Tupolev TU-154M in Quito: 80 killed

Date & Time: Aug 29, 1998 at 1303 LT
Type of aircraft:
Operator:
Registration:
CU-T1264
Flight Phase:
Survivors:
Yes
Schedule:
Quito - Guayaquil - Havana
MSN:
85A720
YOM:
1985
Flight number:
CU389
Country:
Crew on board:
14
Crew fatalities:
Pax on board:
77
Pax fatalities:
Other fatalities:
Total fatalities:
80
Aircraft flight hours:
9256
Circumstances:
While parked on the apron at Quito-Mariscal Sucre Airport, the crew started the engine when a pneumatic valve blocked. The problem was resolved and two engines were started with ground power unit while the third engine was started during taxi. During the takeoff roll on runway 17, at Vr speed, the pilot-in-command started the rotation but the aircraft failed to respond. For unknown reasons, the crew took 10 seconds to decide to abort the takeoff. The captain initiated an emergency braking procedure but the remaining distance of 800 metres was insufficient. Unable to stop, the aircraft overran, struck a concrete wall, an auto spare parts building and crashed near a soccer field, bursting into flames. Seventy people in the aircraft was well as 10 people on the ground were killed while 21 people in the airplane and 15 on the ground were injured, some seriously. At the time of the accident, the total weight of the aircraft was 73,309 kilos, within limits.
Probable cause:
It is believed that the crew failed to follow the taxi and pre-takeoff checklist and forgot to select the switches for the hydraulic valves of the control system. No technical anomalies were found on the aircraft and engines.

Crash of a Fokker F27 Friendship 600 in Tachilek: 36 killed

Date & Time: Aug 24, 1998 at 0835 LT
Type of aircraft:
Operator:
Registration:
XY-AEN
Survivors:
No
Schedule:
Yangon - Tachilek
MSN:
10476
YOM:
1972
Flight number:
UB635
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
32
Pax fatalities:
Other fatalities:
Total fatalities:
36
Circumstances:
While descending to Tachilek Airport following an uneventful flight from Yangon, the captain informed ATC he just passed 9,500 feet. Shortly later, on final approach, the aircraft struck the slope of the hill of Payakha located 3 km short of runway. The aircraft was totally destroyed and all 36 occupants were killed.
Probable cause:
For unknown reasons, the crew descended below MDA until the aircraft impacted the ground.

Crash of an Antonov AN-26 in Norilsk

Date & Time: Aug 24, 1998
Type of aircraft:
Registration:
RA-26568
Survivors:
Yes
Schedule:
Dikson – Norilsk
MSN:
38 08
YOM:
1976
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Dikson, the aircraft landed at Norilsk-Alykel Airport at a speed of 200 km/h. After touchdown, the crew started the braking procedure when the captain inadvertently raised the landing gear. As the gear were locked down, they remained extended but after entering the taxiway, the crew increased power and the speed reached 135 km/h when an unloading of the landing gear and a decompression of the right hand main landing gear damper occurred. This caused the right main gear to collapse slowly. The airplane went out of control, veered to the right and came to rest out of the taxiway. All 20 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the crew who mistakenly raised the landing gear during the deceleration procedure and an excessive speed while taxiing.

Crash of a Cessna 402C in Roseau: 11 killed

Date & Time: Aug 23, 1998 at 1740 LT
Type of aircraft:
Operator:
Registration:
N2748J
Survivors:
No
Schedule:
Saint Martin - Marigot
MSN:
402C-0244
YOM:
1980
Flight number:
DCF947
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
On August 23, 1998, at 1740 eastern daylight time a Cessna 402C, N2748J, impacted rising terrain following a go-around from runway 09, at the Melville Hall Airport, Dominica. The airplane was registered to Hartford Holding Corporation, Wilmington, Delaware, and operated by Air Anguilla, Incorporated, St Thomas, Virgin Islands as Cardinal Airlines Flight 947 Dominica. The airplane was operated under the provisions of Title 14 CFR Part 135, and visual flight rules. Visual meteorological conditions prevailed in heavy rain, and a VFR flight plan was filed. The commercial pilot and 10 passengers sustained fatal injuries and the airplane was destroyed. There was no fire. The airplane departed Princess Juliana Airport in St. Maarten, West Indies about 1600.

Crash of a Pilatus PC-6/B2-H2 Turbo Porter in Iquitos

Date & Time: Aug 22, 1998
Operator:
Registration:
FAP322
Flight Phase:
Survivors:
Yes
MSN:
723
YOM:
1974
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2874
Circumstances:
Shortly after takeoff from Iquitos-Moronacocha Airport, while climbing, the single engine aircraft went out of control and crashed in the Moronacocha River bed. Both passengers escaped uninjured while both pilots were injured. The aircraft had also the civil registration OB-1167.

Crash of a De Havilland DHC-6 Twin Otter near Ghorepani: 18 killed

Date & Time: Aug 21, 1998 at 1124 LT
Registration:
9N-ACC
Flight Phase:
Survivors:
No
Site:
Schedule:
Jomsom - Pokhara
MSN:
710
YOM:
1980
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
18
Circumstances:
The twin engine aircraft departed Jomsom Airport at 1110LT on a 20-minutes flight to Pokhara, carrying 15 passengers and three crew members. While cruising at an altitude of 10,500 feet in good weather conditions, the aircraft struck the slope of a mountain. The wreckage was found two days later and all 18 occupants were killed.