Crash of an Aviation Traders ATL-98 Carvair in Venetie

Date & Time: Jun 28, 1997 at 1618 LT
Registration:
N103
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Venetie - Fairbanks
MSN:
10273/4
YOM:
1943
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20000
Captain / Total hours on type:
3000.00
Aircraft flight hours:
7145
Circumstances:
The air cargo flight had just off loaded its cargo at a remote site. Shortly after takeoff, the number two engine begin to run rough. The engine was shut down, and the propeller feathered. During the shutdown process, a fire warning light illuminated, and fire became visible near the number 2 engine. The crew activated both banks of engine fire extinguishers, but were unable to extinguish the fire. While on approach to an off-airport emergency landing site, the number two engine fell off and ignited a brush fire. The crew made a successful landing and ran away from the airplane. The airplane continued to burn and was destroyed by fire. The number 2 engine was not recovered or located.
Probable cause:
A fire associated with the number 2 engine for undetermined reasons.
Final Report:

Crash of a Cessna 207A Skywagon in Nome: 2 killed

Date & Time: Jun 27, 1997 at 1633 LT
Operator:
Registration:
N207SP
Survivors:
No
Schedule:
Brevig Mission - Nome
MSN:
207-0412
YOM:
1977
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1745
Captain / Total hours on type:
200.00
Aircraft flight hours:
12771
Circumstances:
The flight was landing under special VFR conditions. Special VFR operations are permitted with a visibility of 1 mile, and clear of clouds. The airport was the pilot's base of operations. The flight had held outside the airport surface area for 26 minutes, waiting for a special VFR clearance. While outside the airport surface area, the pilot was required to maintain 500 feet above the ground and 2 miles visibility. While holding, the weather at the airport was reported as 300 feet overcast. The visibility decreased from 4 miles to 1 mile in mist. The pilot was new to the area of operations, having worked at the company for 24 days, during which he accrued 69 hours of flight time. Four minutes after receiving clearance to enter the surface area for landing, the airplane collided with a 260 feet tall radio antenna tower at 222 feet above the ground. The tower was located 3.85 nautical miles east of the airport. The radio tower was not considered by the FAA to be an object affecting navigable airspace, but was depicted as an obstruction on the VFR sectional chart for the area. The tower was equipped with obstruction lighting for night illumination, and was painted alternating aviation orange and white for daytime marking. One minute after the collision, the overcast was reported at 200 feet, and the visibility was 5/8 mile.
Probable cause:
The pilot's continued VFR flight into instrument meteorological conditions, and his failure to maintain adequate clearance from an obstruction (antenna tower). Factors in the accident were low ceilings and visibility, and the pilot's lack of familiarity with the geographic area.
Final Report:

Crash of a Beechcraft D18S in Willow

Date & Time: Jun 25, 1997 at 1130 LT
Type of aircraft:
Operator:
Registration:
N765D
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Willow - Sleetmute
MSN:
A-818
YOM:
1952
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8000
Captain / Total hours on type:
35.00
Aircraft flight hours:
8600
Circumstances:
The pilot took off from a 4400-foot-long gravel airstrip with a near gross weight load of cargo. He said that shortly after lift-off the airplane felt 'sluggish', and he believes the left engine began to lose power. He said the airplane would not climb, and he elected to bring both engines to idle and land on the remaining runway. The airplane touched down a short distance from the end of the runway, and continued off the end and into the woods. A fire erupted, and the airplane was destroyed by fire. The pilot is unsure if the fire occurred in the air, or shortly after the airplane went off the end of the runway. The engines were extensively damaged by fire, and were not examined. FAA inspectors on scene said there was no obvious signs of catastrophic engine failure.
Probable cause:
The loss of engine power for an undetermined reason.
Final Report:

Crash of a Piper PA-31-310 Navajo Chieftain in San Diego: 3 killed

Date & Time: Jun 20, 1997 at 1231 LT
Type of aircraft:
Operator:
Registration:
N266MM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
San Diego - San Diego
MSN:
31-140
YOM:
1968
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
10041
Captain / Total hours on type:
1586.00
Aircraft flight hours:
8473
Circumstances:
The aircraft concluded an aerial survey and landed at Brown Field to clear U.S. Customs. On restart, as the left engine began running, a witness noticed two short, yellow flame bursts exit the exhaust. During taxi, the witness heard a popping sound coming from the aircraft. As power was applied to cross runway 26L, the sound went away. The aircraft stopped for a few seconds prior to pulling onto the runway; the witness did not observe or hear a run-up. Witnesses reported hearing a series of popping sounds similar to automatic gunfire and observed the aircraft between 600 and 1,000 feet above the ground with wings level and the landing gear up. The aircraft was observed to make an abrupt, 45-degree banked, left turn as the nose dipped down. Witnesses reported the nose of the aircraft then raised up toward the horizon. This was followed by the aircraft turning to the left and becoming inverted in an estimated 30-degree nose low attitude. With the nose still low, the aircraft continued around to an upright position and appeared to be in a shallow right bank. Witnesses then lost sight of the aircraft due to buildings and terrain. A May 20, 1997, work order indicated the left manifold pressure fluctuated in flight. Both wastegates were lubricated and a test flight revealed the left engine manifold pressure lagged behind the right engine manifold pressure. On June 18, 1997, the left engine differential pressure controller was noted to have been removed and replaced. This was the corrective action for a discrepancy write up that the left engine manifold pressure fluctuated up and down 2 inHg and the rpm varied by 100 in cruise. A test flight that afternoon by the accident pilot indicated the discrepancy still occurred at cruise power settings, but the engine operated normally at high and low power settings. Post accident functional checks were performed on various components. No discrepancies were noted for the left governor. The left engine differential pressure controller was damaged and results varied on each test. The left density controller was too damaged to test. The right engine density and differential pressure controllers tested satisfactory. The left and right fuel pumps operated within specifications. Both fuel servos were damaged. One injection nozzle on the left engine was partially plugged; all others flow tested within specifications.
Probable cause:
The loss of power in the left engine for undetermined reasons and the pilot's subsequent failure to maintain minimum single-engine control airspeed. A contributing factor was the pilot's decision to fly with known deficiencies in the equipment.
Final Report:

Crash of a Boeing 727-227 in Newark

Date & Time: Jun 7, 1997
Type of aircraft:
Operator:
Registration:
N571PE
Flight Phase:
Survivors:
Yes
MSN:
21264
YOM:
1976
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was transferred from the maintenance facilities to the main terminal by a technical crew when control was lost. The airplane collided with the USAir Terminal and the cockpit was destroyed.

Crash of a Cessna 402C in Rawlins

Date & Time: Jun 1, 1997 at 2240 LT
Type of aircraft:
Operator:
Registration:
N1233P
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Rawlins – Riverton
MSN:
402C-0804
YOM:
1984
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13000
Captain / Total hours on type:
4000.00
Aircraft flight hours:
7674
Circumstances:
During the initial climb after takeoff, while executing a dark-night departure, the pilot failed to maintain clearance from rising terrain about one and one-quarter mile off the end of the runway. Operator records indicated that the pilot had flown out of this airport in the past, and that the aircraft was approximately 600 pounds below maximum certificated gross weight at the time of departure. A teardown inspection of both engines revealed no pre-impact anomalies, and visual and teardown inspections of the propellers showed damage signatures consistent with ground contact in a flat pitch under significant power.
Probable cause:
The pilot's failure to maintain clearance from the terrain during the initial climb after a night takeoff. Factors include a dark night and rising terrain off the departure end of the runway.
Final Report:

Crash of a Learjet 35A in Great Falls

Date & Time: May 16, 1997 at 1314 LT
Type of aircraft:
Registration:
N1AH
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Great Falls - Dallas
MSN:
35-398
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
8700
Captain / Total hours on type:
2000.00
Aircraft flight hours:
8019
Circumstances:
The captain reported: 'Shortly after V1...there was a loss of power to the left engine....' (FAR Part 1 defines V1 as takeoff decision speed.) However, the first officer, who was the pilot flying, stated the captain retarded power on the left engine as a training exercise. The first officer stated there was no preflight discussion of emergency procedure practice. The airplane became airborne about 3,500 feet down the runway; the crew subsequently lost control of the aircraft, and it crashed to the left of the runway, and a fire erupted. The crew escaped with minor injuries. A teardown of the left engine was performed under FAA supervision at the engine manufacturer's facilities; the engine manufacturer reported that damage found during the teardown 'was indicative of engine rotation and operation at the time of impact....' Both airspeed indicator bugs were found set 9 to 11 knots below the V1 speed on the takeoff and landing data (TOLD) card. No evidence of an aircraft or engine malfunction, to include inflight fire, was found at the accident site.
Probable cause:
The captain's inadequate preflight planning/preparation, and the subsequent improper response to a simulated loss of engine power, resulting in liftoff at an airspeed below that for which sustained flight was possible.
Final Report:

Crash of a Piper PA-61P Aerostar (Ted Smith 601P) in Waterford: 2 killed

Date & Time: Apr 27, 1997 at 2052 LT
Registration:
N885JC
Flight Type:
Survivors:
No
Schedule:
Allentown – Leesburg
MSN:
61-0826-8163434
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1600
Captain / Total hours on type:
525.00
Circumstances:
During arrival at night, the flight was being controlled by a developmental controller (DC), who was being supervised by an instructor (IC). The pilot (plt) was instructed to descend & cross the STILL Intersection (Int) at 3,000 ft. STILL Int was aligned with the localizer (loc) approach (apch) course, 10.1 mi from the apch end of runway 17 (rwy 17); the final apch fix (FAF) was 3.9 mi from the rwy. About 5 mi before reaching STILL Int, while on course & level at 3,000 ft, the plt was cleared for a Loc Rwy 17 Apch. Radar data showed the aircraft (acft) continued to STILL Int, then it turned onto the loc course toward the FAF. Shortly after departing STILL Int, while inbound on the loc course, the acft began a descent. Before the acft reached the FAF, the DC issued a frequency change to go to UNICOM. During this transmission, the IC noticed a low altitude alert on the radar display, then issued a verbal low altitude alert, saying, 'check altitude, you should be at 1,500 ft (should have said '1,800 ft' as that was the minimum crossing altitude at the FAF), altitude's indicating 1,200, low altitude alert.' There was no response from the plt. This occurred about 2 mi before the FAF. Minimum descent altitude (MDA) for the apch was 720 ft. The acft struck tree tops at 750 ft, about 1/2 mi before the FAF. The IC's remark 'you should be at 1,500 ft' was based on an expired apch plate with a lower FAF minimum crossing altitude; the current minimum crossing altitude at the FAF was 1,800 ft. Apch control management had not made the current plate available to the controllers. Investigation could not determine whether a current apch plate would have prompted an earlier warning by the controllers.
Probable cause:
Failure of the pilot to follow the published instrument (IFR) approach procedure, by failing to maintain the minimum altitude for that segment of the approach.
Final Report:

Crash of a Piper PA-61P Aerostar (Ted Smith 601P) in Lake of the Woods: 1 killed

Date & Time: Apr 27, 1997 at 1245 LT
Registration:
N30LL
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bellingham – Midland
MSN:
61-0379-124
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6550
Aircraft flight hours:
4000
Circumstances:
About three hours and twenty minutes after departing Bellingham, Washington, for Midland, Texas, the pilot contacted Klamath Falls (Oregon) Tower and told the controller of his intention to land. About 10 minutes later, while about 30 miles north of Klamath Falls, the pilot reported he was low on fuel and was not able to find the city. The tower responded with instructions that would take the pilot south to the airport. But because the pilot seemed not to be following the instructions, but was instead continuing to the west, he was switched to Seattle Center. Center provided the pilot with a southeasterly heading direct to Klamath Falls, but less than a minute later radar and radio contact with the aircraft was lost. Other pilots overheard the pilot transmit that he had lost power in one engine, and later state that he had lost power in both. Soon thereafter the aircraft was seen to descend to about 200 to 300 feet above the surface of Lake of the Woods. The aircraft then began to slow and its nose began to rise. As it was slowing, one of the engines surged back to a high power setting, and the aircraft almost immediately rolled quickly to the side and dove nearly straight down into the lake. During the post-accident inspection of the airframe, the throttle for the right engine was found retarded to idle, but the throttle for the left engine was found in the full-forward (maximum power) position. A review of the Aerostar owner's manual revealed that the Engine Failure/Restart checklist called for the throttle for a failed engine (both engines in this case) to be retarded to the 'Cracked 1/2 inch open' position. Toxicological results indicate the presence in the pilot's blood of chlordiazepoxide and three of its active metabolites, norchlordiazepoxide, nordiazepam, and oxazepam. Chlordiazepoxide (Librium) is a tranquilizer often used to treat anxiety and tension. At sufficient levels it can have significant adverse effects on judgement, alertness, and performance. It is known to cause drowsiness, mental dullness, and euphoria. The results also indicate the presence of diphenhydramine in the pilot's blood. Diphenhydramine is a sedating antihistamine, and in sufficient quantities is known to produce drowsiness, impaired coordination, blurred vision, and reduced mental alertness.
Probable cause:
The pilot's failure to set the throttle of his second failed engine to 'Cracked-1/2-Open' as called for in the Engine Failure/Restart checklist, followed by a high-power engine surge. Factors include the pilot's delay in landing for refueling, the pilot becoming lost/disoriented, drug impairment, and fuel exhaustion.
Final Report:

Crash of a Lockheed PV-2 Harpoon in Blandburg: 2 killed

Date & Time: Apr 20, 1997 at 1437 LT
Type of aircraft:
Registration:
N6856C
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Philipsburg - Philipsburg
MSN:
15-1156
YOM:
1944
Flight number:
Tanker 38
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2000
Captain / Total hours on type:
170.00
Aircraft flight hours:
3497
Circumstances:
The pilot/owner of an air tanker was dispatched to drop a load of retardant on a fire burning up a valley wall. The pilot made radio contact with the firefighters on the ground, who requested that the pilot deliver the entire load on the first drop. A helicopter pilot who was dropping water on the fire positioned himself about a mile away to allow the air tanker to make its drop. The winds were from the northwest at 15 knots and gusting to 20 knots, and the helicopter pilot reported turbulence in the area. The helicopter pilot watched as the air tanker came from the northeast, overflew the fire, and made a descending counterclockwise turn. The airplane flew towards the fire parallel to the valley ridge, and the helicopter pilot observed the air tanker drop its retardant. During the drop, the airplane flew through smoke, and its right wing impacted trees on the upslope side of the valley. The airplane then rolled 90 degrees and descended into the steeply inclined wooded terrain. A review of the pilot's FAA medical records revealed that he lacked color vision.
Probable cause:
Pilot in command misjudged his maneuvering altitude. Factors to this accident were the mountainous terrain, windy conditions, turbulence in the area, and smoke.
Final Report: