Crash of a Piper PA-31T3-T1040 Cheyenne in Nuiqsut: 5 killed

Date & Time: Sep 18, 2000 at 1510 LT
Type of aircraft:
Operator:
Registration:
N220CS
Survivors:
Yes
Schedule:
Deadhorse – Nuiqsut
MSN:
31-8275013
YOM:
1982
Flight number:
6C181
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
2517
Captain / Total hours on type:
165.00
Aircraft flight hours:
10157
Circumstances:
The airline transport certificated pilot was landing at a remote village on a scheduled domestic commuter flight with nine passengers. The accident airplane, a twin-engine turboprop certified for single-pilot operations, was equipped with a fuselage-mounted belly cargo pod. Witnesses saw the airplane touch down on the gravel runway with the landing gear retracted. The belly pod lightly scraped the runway for about 40 feet before the airplane transitioned to a climb. The propeller tips did not contact the runway. As the airplane began climbing away from the runway, the landing gear was extended. The airplane climbed to about 100 to 150 feet above the ground, and then began a descending left turn, colliding with tundra-covered terrain. A postcrash fire destroyed the fuselage, right wing, and the right engine. The flaps were found extended to 40 degrees. The balked landing procedure for the airplane states, in part: "power levers to maximum, flaps to 15 degrees, landing gear up, and then retract the flaps." Five passengers seated in the rear of the airplane survived the crash. The survivors did not recall hearing a gear warning horn before ground contact. The airplane was landed gear-up eight months before the accident. The airplane was nearly landed gear-up four months before the accident. Each time, a landing gear warning horn was not heard by the pilot or passengers. A postcrash examination of the airplane and engines did not locate any preimpact mechanical malfunction. The FAA's Fairbanks, Alaska, FSDO conducted an inspection of the operator six months before the accident, and recommended the operator utilize two pilots in the accident airplane. Following the accident, the Fairbanks FSDO required the operator to utilize two pilots for passenger flights in the accident airplane make and model.
Probable cause:
The pilot's failure to extend the landing gear, his improper aborted landing procedure, and inadvertent stall/mush. Factors in the accident were an improper adjustment of the landing gear warning horn system by company maintenance personnel, and the failure of the pilot to utilize the pre-landing checklist.
Final Report:

Crash of a Dornier DO.28D-2 Skyservant in San Pablo: 1 killed

Date & Time: Sep 9, 2000 at 1751 LT
Type of aircraft:
Operator:
Registration:
HC-BNT
Flight Type:
Survivors:
Yes
Schedule:
Manta - San Pablo
MSN:
4342
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Aircraft flight hours:
6234
Circumstances:
The airplane departed Manta-Eloy Alfaro Airport at 1711LT on a cargo flight to San Pablo, carrying one passenger, two pilots (among them an instructor) and a Load consisting of 70 boxes of shrimp larvae. En route, while cruising at an altitude of 5,000 feet, the right engine suffered power fluctuations. The instructor pilot switched on the auxiliary fuel pump and changed the fuel mixture but the engine problems persisted. On final approach to San Pablo, the right engine failed and the crew continued the approach on one engine. Following a high approach, the aircraft landed too far down the runway, about 292 metres from the runway end. It bounced and landed firmly six metres further. Realizing that the runway distance available was insufficient, the instructor pilot decided to initiate a go-around procedure. The aircraft climbed to a height of about 20 metres then impacted ground 140 metres to the right of the runway centreline and 26 metres past the runway end. The copilot was killed and both other occupants were seriously injured.
Probable cause:
The instructor pilot's decision to initiate a go-around procedure after landing in the last third portion of the runway with the right engine inoperative, an insufficient runway length and an aircraft's weight that required to stay on the ground. The following contributing factors were identified:
- The decision of the crew to continue the flight after the failure of the right engine that required an immediate landing,
- The crew failed to follow the checklist,
- Failure of the instructor pilot to proceed to an adequate approach briefing,
- Wrong approach configuration,
- Lack of awareness about the runway's characteristics on part of the pilot-in-command,
- The total weight of the aircraft was above the permissible limit,
- Lack of crew coordination,
- The crew mistakenly feathered the left propeller.

Crash of a Piper PA-31T Cheyenne II in Abong Mbang

Date & Time: Aug 29, 2000 at 1600 LT
Type of aircraft:
Operator:
Registration:
TJ-AIM
Survivors:
Yes
Schedule:
Douala – Djoum – Abong Mbang
MSN:
31-8166061
YOM:
1981
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Douala on a flight to Abong Mbang with an intermediate stop in Djoum, carrying five passengers and one pilot. On final approach to Abong Mbang, the pilot encountered poor weather conditions with limited visibility due to heavy rain falls. On short final, the aircraft struck the ground about 60 metres short of runway threshold. Upon impact, the undercarriage were torn off and the aircraft came to rest on its belly. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft 300 Super King Air in Ensenada: 3 killed

Date & Time: Aug 26, 2000 at 0245 LT
Operator:
Registration:
XC-AA72
Flight Type:
Survivors:
No
Site:
Schedule:
Hermosillo – Ensenada
MSN:
FA-87
YOM:
1986
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8260
Copilot / Total flying hours:
1529
Aircraft flight hours:
3125
Circumstances:
The twin engine aircraft departed Hermosillo Airport at 0121LT on a flight to Ensenada, carrying one passenger and two pilots. On approach by night, the crew initiated a last turn to join the runway 11 approach path when the aircraft struck the slope of mountain and crashed about 14 km from the airport. The aircraft was destroyed and all three occupants were killed.
Probable cause:
Controlled flight into terrain while completing a turn on final approach, in night conditions, towards an airport of daytime operations only, as mentioned in the Aeronautical Information Publication (AIP).
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain off Hilo: 1 killed

Date & Time: Aug 25, 2000 at 1735 LT
Operator:
Registration:
N923BA
Survivors:
Yes
Schedule:
Kona – Kona
MSN:
31-8252024
YOM:
1982
Flight number:
BIA057
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2067
Captain / Total hours on type:
465.00
Aircraft flight hours:
3492
Circumstances:
The pilot ditched the twin engine airplane in the Pacific ocean after experiencing a loss of engine power and an in-flight engine fire while in cruise flight. The flight was operating at 1,000 feet msl, when the pilot noticed a loss of engine power in the right engine. At the same time the pilot was noticing the power loss, passengers noted a fire coming from the right engine cowling. The pilot secured the right engine and feathered the propeller. He attempted to land the airplane at a nearby airport; however, when he realized that the airplane was unable to maintain altitude he elected to ditch the airplane in the ocean. Prior to executing the forced landing, the pilot instructed the passengers to don their life jackets and assume the crash position. After touchdown, all but one passenger exited the airplane through the main cabin and pilot doors. It was reported that the remaining passenger was frightened, and could not swim. One survivor saw the remaining passenger sitting in the seat with the seat belt still secured and the life vest inflated. The pilot and passengers were then rescued from the ocean via rescue helicopter and boat. Postaccident examination of the airplane revealed that the right engine's oil converter plate gasket had deteriorated and extruded from behind the converter plate, allowing oil to spray in the accessory section and resulting in the subsequent engine fire. The engine manufacturer had previously issued a mandatory service bulletin (MSB) requiring inspection of the gasket every 50 hours for evidence of gasket extrusion around the cover plate or oil leakage. Maintenance records revealed that the inspection had been conducted 18.3 hours prior to the accident. At the time of the accident, the right engine had accumulated 386.8 hours since its last overhaul, and gasket replacement. The MSB was issued one month prior to the accident, after the manufacturer received reports of certain oil filter converter plate gaskets extruding around the oil filter converter plate. The protruding or swelling of the gasket allowed oil to leak and spray from between the plate and the accessory housing. A series of tests were conducted on exemplar gaskets by submerging them in engine oil heated to 245 degrees F; after about 290 hours, the gasket material displayed signs of deterioration similar to that of the accident gasket. A subsequent investigation revealed that the engine manufacturer had recently changed gasket suppliers, which resulted in a shipment of gaskets getting into the supply chain that did not meet specifications. As a result of this accident, the engine manufacturer revised the MSB to require the replacement of the gasket every 50 hours. The FAA followed suit and issued an airworthiness directive to mandate the replacement of the gasket every 50 hours.
Probable cause:
Deterioration and failure of the oil filter converter plate gasket, which resulted in a loss of engine power and a subsequent in-flight fire.
Final Report:

Crash of a Cessna 421C Golden Eagle III in Hunt: 1 killed

Date & Time: Aug 24, 2000 at 1549 LT
Registration:
N421NT
Flight Type:
Survivors:
No
Schedule:
Pecos – San Antonio
MSN:
421C-1098
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
18185
Aircraft flight hours:
4499
Circumstances:
Approximately 8 months prior to the accident, during a cross country flight, the owner shutdown the left engine due to low oil pressure and diverted from his intended destination to a nearby airport. During descent, the right alternator failed, and the owner performed the emergency gear extension procedure. Following an emergency gear extension, the landing gear of this model airplane cannot be retracted until the system has been ground serviced. A mechanic reported that about 7 months prior to the accident, with the owner present, he removed the oil filter from the left engine, found it packed with metal shavings and told the owner that the engine needed overhaul. Two other mechanics reported that approximately three weeks before the accident, they installed an oil filter on the left engine, changed the oil, and cleaned the oil pressure regulator. They ground ran both engines with no discrepancies noted. One of the mechanics reported that following the engine run, the left engine oil filter was removed, examined, and no metal was found. The landing gear was not serviced. According to the owner, the pilot was "hired" by one of the two mechanics to ferry the airplane with the gear extended to a location where the gear could be serviced. While en route, the pilot reported a loss of power on the left engine, that he was having trouble feathering the engine, that the airplane would not maintain altitude and he was looking for a place to land. Witnesses observed the airplane flying low, wheels down and losing altitude. They further observed it roll into a steep left bank, hit trees and a fence, catch fire, come to rest inverted on a road and burn. Post accident examination of the left engine revealed a hole in the right crankcase half over the #3 cylinder attach point. Disassembly of the left engine revealed that the #3 connecting rod was separated from the crankshaft, and the rod bolts, rod cap, and top of the rod were deformed. The #5 piston pin had one cap missing. Scoring was noted on the crankshaft journals, and the main bearings exhibited discoloration and deformation consistent with oil starvation. The cylinders exhibited deformation, scoring in the barrels, and deposits on the domes. The camshaft exhibited discoloration and scoring on the camshaft lobes. Disassembly of the left propeller revealed that it was in the vicinity of low pitch/latch position and not rotating at impact. The disassembly of the right engine and propeller did not reveal any discrepancies that would have precluded operation prior to impact. Estimates of the airplane's climb performance indicated that with the landing gear down and the left propeller stopped, it was not capable of sustained flight.
Probable cause:
The loss of left engine power as a result of the owner's failure to overhaul the engine before further flight after the lubrication system was found contaminated with metal. Contributing factors were the pilot's decision to fly the aircraft with a non-operating landing gear system, which resulted in a forced landing, and the lack of suitable terrain for the forced landing.
Final Report:

Crash of an Airbus A320-212 off Bahrain: 143 killed

Date & Time: Aug 23, 2000 at 1930 LT
Type of aircraft:
Operator:
Registration:
A4O-EK
Survivors:
No
Schedule:
Cairo - Bahrain - Muscat
MSN:
481
YOM:
1994
Flight number:
GF072
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
135
Pax fatalities:
Other fatalities:
Total fatalities:
143
Captain / Total flying hours:
4416
Captain / Total hours on type:
1083.00
Copilot / Total flying hours:
608
Copilot / Total hours on type:
408
Aircraft flight hours:
17370
Aircraft flight cycles:
13990
Circumstances:
On 23 August 2000, at about 1930 local time, Gulf Air flight GF072, an Airbus A320-212, a Sultanate of Oman registered aircraft A4O-EK, crashed at sea at about 3 miles north-east of Bahrain International Airport. GF072 departed from Cairo International Airport, Egypt, with two pilots, six cabin crew and 135 passengers on board for Bahrain International Airport, Muharraq, Kingdom of Bahrain. GF072 was operating a regularly scheduled international passenger service flight under the Convention on International Civil Aviation and the provisions of the Sultanate of Oman Civil Aviation Regulations Part 121 and was on an instrument flight rules (IFR) flight plan. GF072 was cleared for a VOR/DME approach for Runway 12 at Bahrain. At about one nautical mile from the touch down and at an altitude of about 600 feet, the flight crew requested for a left hand orbit, which was approved by the air traffic control (ATC). Having flown the orbit beyond the extended centreline on a south-westerly heading, the captain decided to go-around. Observing the manoeuvre, the ATC offered the radar vectors, which the flight crew accepted. GF072 initiated a go-around, applied take-off/go-around thrust, and crossed the runway on a north-easterly heading with a shallow climb to about 1000 feet. As the aircraft rapidly accelerated, the master warning sounded for flap over-speed. A perceptual study, carried out as part of the investigation, indicated that during the go-around the flight crew probably experienced a form of spatial disorientation, which could have caused the captain to falsely perceive that the aircraft was ‘pitching up’. He responded by making a ‘nose-down’ input, and, as a result, the aircraft commenced to descend. The ground proximity warning system (GPWS) voice alarm sounded: “whoop, whoop pull-up …”. The GPWS warning was repeated every second for nine seconds, until the aircraft impacted the shallow sea. The aircraft was destroyed by impact forces, and all 143 persons on board were killed.
Probable cause:
The factors contributing to the above accident were identified as a combination of the individual and systemic issues. Any one of these factors, by itself, was insufficient to cause a breakdown of the safety system. Such factors may often remain undetected within a system for a considerable period of time. When these latent conditions combine with local events and environmental circumstances, such as individual factors contributed by “frontline” operators (e.g.: pilots or air traffic controllers) or environmental factors (e.g.: extreme weather conditions), a system failure, such as an accident, may occur.
The investigation showed that no single factor was responsible for the accident to GF072. The accident was the result of a fatal combination of many contributory factors, both at the individual and systemic levels. All of these factors must be addressed to prevent such an accident happening again.
(1) The individual factors particularly during the approach and final phases of the flight were:
(a) The captain did not adhere to a number of SOPs; such as: significantly higher than standard aircraft speeds during the descent and the first approach; not stabilising the approach on the correct approach path; performing an orbit, a non-standard manoeuvre, close to the runway at low altitude; not performing the correct go-around procedure; etc.
(b) In spite of a number of deviations from the standard flight parameters and profile, the first officer (PNF) did not call them out, or draw the attention of the captain to them, as required by SOP’s.
(c) A perceptual study indicated that during the go-around after the orbit, it appears that the flight crew experienced spatial disorientation, which could have caused the captain to perceive (falsely) that the aircraft was ‘pitching up’. He responded by making a ‘nose-down’ input, and as a result, the aircraft descended and flew into the shallow sea.
(d) Neither the captain nor the first officer perceived, or effectively responded to, the threat of increasing proximity to the ground, in spite of repeated hard GPWS warnings.
(2) The systemic factors, identified at the time of the above accident, which could have led to the above individual factors, were:
(a) Organisational factors (Gulf Air):
(i) A lack of training in CRM contributing to the flight crew not performing as an effective team in operating the aircraft.
(ii) Inadequacy in the airline's A320 training programmes, such as: adherence to SOPs, CFIT, and GPWS responses.
(iii) The airline’s flight data analysis system was not functioning satisfactorily, and the flight safety department had a number of deficiencies.
(iv) Cases of non-compliance, and inadequate or slow responses in taking corrective actions to rectify them, on the part of the airline in some critical regulatory areas, were identified during three years preceding the accident.
(b) Safety oversight factors:
A review of about three years preceding the accident indicated that despite intensive efforts, the DGCAM as a regulatory authority could not make the operator comply with some critical regulatory
requirements.
Final Report:

Crash of a Cessna 207 Skywagon in San Juan de Manapiare: 3 killed

Date & Time: Aug 23, 2000 at 0703 LT
Registration:
YV-753C
Survivors:
Yes
Schedule:
Puerto Ayacucho – San Juan de Manapiare
MSN:
207-0344
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On final approach to San Juan de Manapiare Airport in bad weather conditions, the single engine aircraft crashed on hilly terrain. The pilot and two passengers were killed while three other occupants were injured.

Crash of a Beechcraft B60 Duke in Atlanta:1 killed

Date & Time: Aug 18, 2000 at 2244 LT
Type of aircraft:
Operator:
Registration:
N8WD
Flight Type:
Survivors:
No
Schedule:
Houston – Atlanta-DeKalb-Peachtree
MSN:
P-258
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1800
Aircraft flight hours:
2665
Circumstances:
The pilot had experienced engine problems during a flight and requested maintenance assistance from the local maintenance repair station. Before the maintenance personnel signed off and completed the repairs, the pilot refueled the airplane, and attempted an instrument flight back to the originating airport. While enroute, the pilot reported a low fuel situation, and deviated to a closer airport. During the approach, the airplane lost engine power on both engines, collided with trees, and subsequently the ground, about a half of a mile short of the intended runway. There was no fuel found in the fuel system at the accident site. No mechanical problems were discovered with the airplane during the post-accident examination. This accident was the second time the pilot had exhausted the fuel supply in this airplane.
Probable cause:
The pilot's failure to preflight plan adequate fuel for the flight that resulted in fuel exhaustion and the subsequent loss of engine power.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Hazlehurst: 3 killed

Date & Time: Aug 15, 2000 at 0825 LT
Operator:
Registration:
N801MW
Survivors:
No
Schedule:
Dothan - Hazlehurst
MSN:
31-8152136
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
6400
Circumstances:
The flight was cleared for an NDB or GPS runway 14 instrument approach. The pilot was instructed to report procedure turn. Center radar reported the airplane's altitude was last observed at 200 feet. A witness observed the airplane as it collided with trees and the ground and, subsequently burst into flames. No mechanical problem with the airplane was reported by the pilot or discovered during the wreckage examination. Weather minimums for the approach are 800 feet an one mile. Low clouds were reported in the area at the time of the accident.
Probable cause:
Pilot's failure to follow instrument procedures and descended below approach minimums and collided with trees. A factor was low clouds.
Final Report: