Crash of a Piper PA-31-310 Navajo in Panama City: 2 killed

Date & Time: Jun 26, 1990 at 0515 LT
Type of aircraft:
Registration:
N18PA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Panama City - Tampa
MSN:
31-7712068
YOM:
1977
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7524
Captain / Total hours on type:
600.00
Aircraft flight hours:
5993
Circumstances:
Witnesses described the takeoff as a long ground roll, slow climb, and engines not sounding normal. The airplane then settled into trees. Teardown of the left engine revealed water present in the fuel injector lines of #1, #3 and #5 cylinders. #3 nozzle plugged. Intake valves dark and sooty. Pistons 1, 3 and 5 had considerable amounts of dark carbon deposits. Teardown of right engine revealed extensive carbon buildups throughout. An engine test run was performed by the director of maintenance day before accident. Personnel formerly employed by the operator provided written statements of allegations pertaining to the general condition of company airplanes, falsification of maintenance records, and improper maintenance procedures being performed on company airplanes. Both occupants were killed.
Probable cause:
A loss of power on both engines during takeoff as a result of inadequate maintenance. In addition, the pilot failed to abort the takeoff.
Final Report:

Crash of a Piper PA-31-310 Navajo off New Town: 1 killed

Date & Time: Jun 20, 1990 at 0451 LT
Type of aircraft:
Operator:
Registration:
YV-2200P
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fort Lauderdale - Caracas
MSN:
31-7400006
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
On June 20, 1990, at 04:51 Atlantic standard time (AST), a Piper PA-31, YV2200P, registered to and operated by Juan A. Zeley, crashed near New Town, Andros Island, Bahamas, while on a business flight from Fort Lauderdale, Florida, to Caracas, Venezuela. Visual meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed. The Venezuelan registered airplane was destroyed. The pilot, the sole occupant of the airplane, who held a Venezuelan commercial pilot certificate was fatally injured. The flight originated at Fort Lauderdale Executive Airport, Fort, Lauderdale, Florida, on June 20, 1990 at 04:05 AST.

Crash of a Piper PA-31P-425 Pressurized Navajo in Delma Island: 4 killed

Date & Time: May 15, 1990
Type of aircraft:
Operator:
Registration:
SP-FNA
Flight Type:
Survivors:
No
Schedule:
Delma Island - Delma Island
MSN:
31-7400202
YOM:
1974
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The twin engine aircraft was returning to Delma Island Airport following a cartography mission over the area. On final, the aircraft went out of control and crashed short of runway, bursting into flames. All four occupants were killed.
Probable cause:
Engine failure on short final for unknown reasons.

Crash of a Piper PA-31-325 Navajo C/R near Cedar City: 4 killed

Date & Time: Apr 25, 1990 at 2230 LT
Type of aircraft:
Operator:
Registration:
N18PP
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Denver - Reno
MSN:
31-7512046
YOM:
1975
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2000
Aircraft flight hours:
2260
Circumstances:
The pilot reported to ATC that he intended to make an unscheduled fuel stop. ATC advised that Cedar City Airport was 15 minutes away. Radar vectors were requested and were issued. Although dark night conditions existed and the pilot controlled airport lighting was never activated, the pilot reported the airport in sight and was cleared for a visual approach. Three minutes later radar contact was lost. Impact occurred in mountainous terrain at 9,100 feet elevation about six miles east of the 5,622 foot elevation airport. Minimum safe altitude was 12,400 feet. All four occupants were killed.
Probable cause:
The pilot failed to maintain a minimum safe altitude over mountainous terrain during a night VFR approach for landing.
Final Report:

Crash of a Piper PA-31-310 Navajo in British Columbia: 2 killed

Date & Time: Nov 23, 1989
Type of aircraft:
Operator:
Registration:
C-GPMZ
Flight Phase:
Survivors:
No
Site:
MSN:
31-7401120
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Struck a hill somewhere in BC while on a charter flight. Both occupants were killed.
Probable cause:
Controlled flight into terrain.

Crash of a Piper PA-31-310 Navajo in Carnarvon

Date & Time: Aug 18, 1989 at 1856 LT
Type of aircraft:
Operator:
Registration:
VH-DEG
Flight Type:
Survivors:
Yes
Schedule:
Geraldton – Carnarvon
MSN:
31-7812098
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
At approximately 1809, (23 minutes before last light) during final approach to landing at Carnarvon, the pilot noticed that the landing gear had not extended correctly. The aircraft remained in the circuit area whilst the pilot attempted to lower the landing gear using both manual and emergency methods. He also sought assistance from the company's, Perth based, duty pilot and Carnarvon based engineers. After exhausting all possible methods of lowering the gear the pilot decided to land with the landing gear and flaps retracted. The pilot rejected a landing on the sealed runways because he was apprehensive that it would cause unnecessary damage to the aircraft and could result in a fire. He considered landing in a riverbed (rejected by the Senior Operational Controller), alongside one of the sealed runways (the surface was unsuitable) and on one of the dirt strips. The pilot was offered a flare path on dirt runway 27 however, he declined and indicated that he would try to land using the available light. At 1856 (last light was at 1832) the pilot attempted a landing on runway 27. On late final approach the aircraft collided with a one and a half metre high levy bank, 270 metres short and 115 metres to the right of the threshold. The pilot was trapped in the wreckage for some time after the aircraft came to a stop. While the passenger was slightly injured, the pilot was seriously wounded.
Probable cause:
The landing gear problem arose when the left main landing gear would not lower. Examination of the aircraft revealed that both hinges fitted to the inboard landing gear door had fractured. The forward hinge had fractured as a result of fatigue and the rear hinge as a result of overload. The fatigue crack initiation had occurred at a sharp edged, prominent forging flash on the inner radius of the hinge and had grown over approximately 4000 load cycles. A similar fatigue problem had been identified on an earlier version of the hinge (part number 46653-00), however, regular inspections for fatigue cracking were discontinued when hinges with part number 47529-32 (as fitted to VH-DEG) were introduced in 1980. Similar fatigue cracking was found in the forward door hinge of another PA31 during the investigation. The fractured hinges jammed the left main landing gear mechanism and neither the normal or emergency extension systems could extend the gear. The pilot was apprehensive about wheels up landings. Much of his decision making was aimed at reducing the risk of fire and minimising the damage the aircraft would sustain during the landing. eg. Selection of a dirt runway instead of the sealed strip, landing with flaps retracted etc. During the pilot's attempts to rectify the landing gear problem, and up until the time of his touchdown, he was subjected to considerable radio transmission traffic involving questions, directions and suggestions which distracted him from his primary tasks. The pilot indicated on at least two occasions that he was ready to land, however, each time advice and questions from the ground personnel involved overrode his intentions. When the pilot was asked if he wanted a flare path on runway 27 there was still some natural light available and he was intending to land. However, by the time he was able to make his final approach it was dark and he was unable to see the ground. Studies have shown that aircrew subjected to high levels of stress can suffer skill fatigue and cognitive task saturation, which in turn can lead to a breakdown in the decision making process. It was apparent from the pilot's radio transmissions and the quality of the decisions made in the latter part of the flight that his information processing and decision making abilities had been degraded by the stress of continuous radio transmissions and continuous, and sometimes conflicting, instructions. As a result, what should have been a relatively simple wheels up landing in daylight was turned into an extremely difficult wheels up landing at night. With the landing gear retracted the aircraft's taxi and landing lights were not available to the pilot.
The following factors were considered relevant to the development of the accident:
1. Manufacturing defect. A forging flash created a stress concentration which led to fatigue cracking.
2. Inadequate inspection procedures. Previous inspection procedures introduced to disclose similar cracking were withdrawn on the introduction of later part numbered hinges.
3. Apprehension of the pilot. The pilot was apprehensive about apparently significant dangers of landing an aircraft, wheels up, on a sealed runway.
4. Inordinate interference in aircraft operations by ground based advisors. The ground advisors input overrode the pilot's decision on a number of occasions with the result that a simple exercise became very complicated.
5. Cognitive task saturation and skill fatigue. The amount of information, advice and suggestions being passed via the radio communications system overloaded the pilot decision making abilities.
6. Improper in-flight decisions. As a result of task saturation the final decision made by the pilot to attempt a night landing on an unlighted strip was incorrect.
7. The pilot did not see and therefore was unable to avoid the levy bank.
Final Report:

Crash of a Piper PA-31-310 Navajo near Carleton: 1 killed

Date & Time: Apr 4, 1989 at 1150 LT
Type of aircraft:
Operator:
Flight Phase:
Survivors:
Yes
Site:
Schedule:
Quebec - Bonaventure
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The twin engine aircraft was completing a charter flight from Quebec City to Bonaventure, carrying five passengers and one pilot. Just before noon, while cruising in poor visibility due to low clouds, the aircraft struck trees, stalled and crashed in a wooded area located on Mt Saint-Joseph, about 4 km north of Carleton. The pilot was killed instantly and all five passengers were injured, three of them seriously. Both passengers who were slightly injured decided to walk away to find help and walked for about 7 hours before reaching Carleton. Rescue teams arrived on scene the next morning to evacuate the last three passengers.

Crash of a Piper PA-31-310 Navajo in Sparks

Date & Time: Jan 31, 1989 at 2159 LT
Type of aircraft:
Registration:
N88RG
Flight Type:
Survivors:
Yes
Schedule:
Sparks – Long Beach
MSN:
31-667
YOM:
1970
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2200
Captain / Total hours on type:
200.00
Circumstances:
During the climbout, in night visual meteorological conditions, the aircraft lost right engine power. The pilot was initially cleared for one runway, but was unable to get a safe gear indication. The pilot made a 180° turn to land on the opposite runway while attempting to get a safe gear indication. On turn from base to final, with the gear down and locked, the pilot overshot final approach. The pilot then chose an unlit parking lot to make an off-airport landing. The aircraft struck a tree and a power line. The aircraft struck several parked unoccupied vehicles during the landing. The faa reported that an on-site inspection revealed a failed right turbocharger. Both occupants were seriously injured.
Probable cause:
The pilot's misjudgement of the forced landing profile. Contributing to the accident was the failure of the right turbocharger and the pilot's improper handling of the landing gear system. Occurrence #1: loss of engine power (partial) - mech failure/malf
Phase of operation: climb
Findings
1. 1 engine
2. (f) exhaust system, turbocharger - failure, total
----------
Occurrence #2: airframe/component/system failure/malfunction
Phase of operation: approach - vfr pattern - downwind
Findings
3. (f) landing gear, normal retraction/extension assembly - improper
----------
Occurrence #3: in flight collision with object
Phase of operation: approach
Findings
4. (f) light condition - dark night
5. (c) planned approach - misjudged - pilot in command
6. (f) object - tree(s)
7. (f) object - wire, static
----------
Occurrence #4: on ground/water collision with object
Phase of operation: landing - flare/touchdown
Findings
8. Object - vehicle
Final Report:

Crash of a Piper PA-31-310 Navajo in Springfield: 1 killed

Date & Time: Jan 3, 1989 at 0812 LT
Type of aircraft:
Operator:
Registration:
N9034Y
Flight Type:
Survivors:
No
Site:
Schedule:
Indianapolis - Columbus
MSN:
31-47
YOM:
1967
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1041
Captain / Total hours on type:
57.00
Aircraft flight hours:
5906
Circumstances:
The pilot was making a contract cargo flight under far 91 rules and had experienced icing enroute. When just past Dayton, he indicated that he 'had a little fuel problem' and needed to get into OSU without delays. A short time later he indicated that he needed to go to the nearest airport. He was vectored toward SGH for landing. He then indicated that he had lost an engine and a short time later indicated that he had lost the other engine. The aircraft crashed in a residential area. There was no fire and only residual fuel was found in the airplane. The company president indicated that he did not encourage his pilots to carry 'excess fuel'. It was reported that this pilot, along with others, had been 'chewed out' for carrying 'excess fuel'. The operation should have been conducted under far 135 rules since the company had retained operational control of the operation. The pilot, sole on board, was killed.
Probable cause:
Fuel exhaustion precipitated by the inadequate fuel consumption calculations performed by the pilot, pressure from the company president to not carry excess fuel and improper in-flight planning/decisions by the pilot by not refueling enroute before fuel was exhausted. Contributing to the accident was the inadequate surveillance and certification of the operator by the FAA.
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: descent
Findings
1. (c) fuel consumption calculations - inadequate - pilot in command
2. (c) company-induced pressure - company/operator management
3. (c) inadequate surveillance of operation - faa (organization)
4. (c) fluid, fuel - exhaustion
5. (c) aircraft preflight - inadequate - pilot in command
6. (c) inadequate certification/approval - faa (organization)
7. (c) refueling - not performed - pilot in command
8. (c) in-flight planning/decision - inadequate - pilot in command
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Piper PA-31-310 Navajo off Stanwell Park: 3 killed

Date & Time: Nov 1, 1988 at 1740 LT
Type of aircraft:
Registration:
VH-DAP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Nowra - Nowra
MSN:
31-364
YOM:
1968
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The aircraft had been modified by the installation of an air driven winch for the purpose of towing gunnery targets and was operating in conjunction with a warship for scheduled sea/air gunnery practise. Weather conditions in the area were reported as overcast at 4000 feet, wind 060 degrees / 15-20 knots and visibility of 15-20 kilometres. At about 1717 hours the aircraft was instructed to commence carrying out gunnery tracking runs at an altitude of 1000 feet with the sleeve target not deployed. Between 1720 and 1735 hours the aircraft carried out two such runs from the west and east. The aircraft then tracked to the south, away from the ship, to a distance of about 10 kilometres. At about 1738 the aircraft was instructed to turn inbound for a run from astern. At about 1739 hours the pilot reported engine problems and about one minute later advised "I've got problems, Mayday, I'm going in". Crewmen stationed near the stern of the ship, reported seeing the aircraft dive into the sea. The warship was immediately turned back towards the crash position. Other warships and aircraft were also ordered to the crash position. The only wreckage sighted was at the crash datum and was believed to have been a section of wing. This wreckage was located about two metres below the surface and sank before it could be recovered. The approximate depth of water at the crash position is 450 fathoms. No trace of the aircraft or its occupants has been discovered to date.
Probable cause:
The subsequent investigation established that the flight crew were properly qualified to conduct the flight, and that the aircraft was appropriately certified and maintained. The flight was conducted in accordance with the conditions of the operating contract. At the time of the occurrence the aircraft had not deployed the sleeve target and no firing was being carried out. No evidence was found to suggest an in-flight structural failure or fire. The installation of the target towing equipment was not considered to have been a factor in the development of the accident. There was a loss of control of the aircraft following an apparent engine malfunction. The precise reasons for the accident have not been established.
The following factors were considered relevant to the development of the accident:
1. Apparent engine failure or malfunction.
2. Control of the aircraft was lost for reasons which have not been determined.
Final Report: