Aviation Accident Summaries

Aviation Accident Summary NYC03FA008

Trenton, NJ, USA

Aircraft #1

N96WF

Pilatus PC-12/45

Analysis

The Pilatus PC-12/45 departed into instrument meteorological conditions. Just as the airplane entered clouds, loud bangs were heard from the engine and flame was observed coming the left side engine exhaust. The pilot in command pushed the nose over, aimed the airplane to where he thought the airport was, and the second pilot initiated engine shutdown. The airplane touched down long and fast, on a wet runway. The pilot intentionally yawed the airplane, and it departed the runway in a nose right 60-degree skid, and struck a chain link fence about 300 feet beyond the departure end of the runway. Examination of the engine revealed the #1 bearing had failed. Electrical pitting was found on the gears in the accessory drive between the starter-generator (SG) attach point, and the # 1 bearing. About 704 hour earlier, the SG had an unscheduled replacement. Records indicated that the SG had burn marks on the stator vanes and armature; however, the initiating event for the SG failure was not determined. Other engines were identified as having experienced electrical discharge damage (EDD), all of which preceded the accident. Each event occurred on a multi-engine airplane and resulted in an in-flight shutdown, followed by a single engine landing. None of the starter generators that were identified as the source of the EDD were original equipment manufacturer (OEM), and all had been previously overhauled. Additional engines were identified as having experienced EDD; however, the records on the engines were incomplete, and there was no starter generator history to review. Goodrich published an overhaul manual for the starter-generator. In the manual they stated that only Goodrich replacement parts should be used, and the use of non-Goodrich parts would void their warranty. However, there was no FAA requirement that the overhaul be conducted by an FAA approved repair station, or that only Goodrich parts be used as replacement items

Factual Information

HISTORY OF FLIGHT On October 16, 2002, at 1424 eastern daylight time, a Pilatus PC-12/45, N96WF, was substantially damaged during a forced landing at Trenton Mercer Airport (TTN), Trenton, New Jersey. The two certificated airline transport pilots, and one passenger were not injured. One passenger received minor injuries. Instrument meteorological conditions prevailed for the corporate flight, which departed from Trenton, and was destined for Dulles International Airport (IAD), Dulles, Virginia. The flight was conducted on an instrument flight rules (IFR) flight plan under 14 CFR Part 91. According to a Federal Aviation Administration (FAA), transcript of air/ground communications from the Trenton control tower, the pilot made initial contact with Trenton ground control at 1407, and was cleared for takeoff on runway 6 at 1421. At 1423:02, the pilot stated to the local controller, "...nine six whiskey fox declaring an emergency, we're engine out, we're coming back to the airport." The local controller enquired if they had the field in sight, and the pilot replied that they had the field in sight and were going to land on runway 16. The local controller cleared the flight to land on runway 16. The last segment of the landing roll was captured by a security camera. The airplane departed the runway in a right yaw of approximately 45 to 60 degrees. The pilot-in-command (PIC) reported the yaw was intentional, and an attempt to avoid the chain link fence beyond the runway. The PIC stated: "...Engine startup was normal, checklists were completed and we were cleared to taxi to runway six...Then we were cleared for takeoff...Ignition was turned on because of anticipated turbulence, all engine parameters were normal on takeoff including engine and aircraft acceleration...Gear was retracted and then the flaps were retracted. Concurrent with the flaps being retracted there was a squeal...We had been given a clearance to turn to a heading of 290 and we commenced this turn about 700 feet msl [mean sea level] and were in the clouds at that time. About the time we started the turn there was a strong odor of something hot, but not an electrical smell...[the SIC] told the tower we were returning to land and I planned on a downwind to runway six...Before the turn was completed, there was a loud bang that sounded like a compressor stall, but much more violent and a long flame shot out of the engine exhaust. I reduced the PCL (power control lever-throttle) to mid-position, targeting 15 PSI torque. The first bang interrupted thrust and then the engine seemed to regain some power, the second bang followed almost immediately with the same exhaust flame and thrust was lost. The PCL was closed to idle, there was one more lesser bang...[the SIC] announced that he was feathering the engine and did so...A glide was established and the aircraft turned in the direction of where the approach end of runway 16 was believed to be...The runway became visible through ragged clouds and we were high. I extended the gear and lowered the flaps. By that time there were main gear green lights...[the SIC] said that he would pump the [nose] gear, which he did, and he announced the green-gear down...I maneuvered the aircraft to lose altitude and align with the runway, landed on the runway with an estimated 20 knots tailwind in rain, ran off the end and made a right turn to cause a long run-out and attempt to avoid the airport boundary fence, berm, and railroad....We evacuated using the overwing exit (which is on the right side)...." The second pilot stated: "...Touchdown happened at a higher than normal airspeed with a high tailwind about at the intersection of the two runways. Braking action was observed to be minimal. At this point I turned to the passengers and shouted brace. After the announcement, I cycled the electrical crash bar. I felt the right pedal advance to the floor and observed the aircraft yaw to the right and queried...[the PIC] about this. He said he was doing this intentionally to avoid the railroad tracks. I concurred...After impact, I departed the cockpit to evacuate the aircraft. A foreign metal bar blocked the main cabin door, so I continued to the cargo door. The cargo door would only budge an inch or two after the second shove, so I turned around and announced we would be exiting through the window exit. I assisted...[a passenger] in removing the exit window and tossing it out and then helped both him and ...[the other passenger]to evacuate the aircraft. I then stepped through the exit and turned around to assure...[the PIC] was behind me...." When interviewed, the PIC reported that although he was aware of the engine shutdown, he had not called for it at the time it was initiated. He added that based upon his airline experience, the first thing you normally do with a compressor stall is reduce the power. The second pilot reported that he initiated the engine shutdown based upon feeling a reduction of power in the engine. He reported that the PIC had not requested the shutdown at the time that it was initiated. A person employed by Trenton Airport reported: "While doing the mid-day field check, I had just exited off of R/W 16/34. The tower had notified me that a plane coming in with a dead engine onto R/W 16/34. At that time, I turned to look out the window to see the plane passing me. I noticed that the engine was off, and the prop was not spinning...I watched the craft leave the R/W. I saw mud flying all over, the plane hit the fence...I saw 4 people exiting the aircraft...One of the passengers was complaining of side pain, I walked him to the ambulance. I notice the left wing was off and landed on the train tracks...." The accident occurred during the hours of daylight at north 40 degrees, 16 minutes, 18 seconds, and west 74 degrees, 48 minutes, 24 seconds. OTHER DAMAGE Approximately 100 feet of airport chain link security fence was destroyed. PERSONNEL INFORMATION Pilot-In-Command The PIC held an airline transport pilot certificate with a rating for multi-engine land airplanes. He held a commercial pilot certificate with ratings for single engine land and single engine sea airplanes. He also held a flight instructor rating for single and multi-engine airplanes and instrument airplane. He was last issued a second-class FAA Airman medical certificate, with no limitations, on May 23, 2002. He reported his total flight experience as 26,274 hours, which included 3,942 hours in single engine airplane. He reported that he had accumulated 563 hours in make and model, including 45 hours in the preceding 90 days. The PIC had completed Pilatus PC-12 initial ground and flight training on April 19, 2000, and completed his last recurrent Pilatus PC-12 ground and flight training on April 6, 2002. Second Pilot The second pilot held an airline transport pilot certificate with a rating for multi-engine land airplanes. He held a commercial pilot certificate with ratings for single engine land airplanes. He also held a flight instructor rating for single and multi-engine airplanes and instrument airplane. He was last issued a first-class FAA Airman medical certificate, with no limitations, on March 26, 2002. He reported his total flight experience as 12,000 hours, which included 10,500 hours in single engine airplanes. He reported that he had accumulated 1,500 hours in make and model, including 50 hours in the preceding 90 days. The second pilot had completed Pilatus PC-12 initial ground and flight training on June 19, 1999. His last recurrent ground and flight training in the Pilatus PC-12 occurred June 6, 2001. He had completed LearJet 31A, initial ground and flight training on June 14, 2002. Interviews disclosed the airplane was flown both in the single pilot configuration, and with two pilots. AIRCRAFT INFORMATION The wing flaps were electrically operated, and the landing gear was hydraulically operated. The airplane was equipped with a Pratt & Whitney of Canada (PWC) PT6A-67B engine, and certificated for single pilot operations. The engine installation was designed so that feathering the propeller also cut off the fuel, and induced engine shutdown. In addition, a loss of oil pressure on the engine would also cause the propeller to go into feather. A check of the emergency procedures contained in the airplane flight manual revealed that movement of the condition lever to cut-off/feather is part of the ENGINE FAILURE IN FLIGHT checklist. The engine's oil system was equipped with a magnetic chip detector (MCD) that was installed in the reduction gearbox (RGB). The MCD used a dipole magnet, which attracted magnetic materials that may be in the engine's oil. When enough magnetic (or other conductive) material had collected to bridge the two poles, the material completed an electrical circuit that illuminated an amber caution light CHIP on the central advisory and warning system (CAWS) in the cockpit. There was no MCD installed in the accessory gear box (AGB). The CAWS on early serial-numbered PC-12 and PC-12/45 airplanes, including the accident airplane, was designed so that such engine MCD warnings would be enabled only when the airplane was on the ground. The CAWS received a signal from the weight-on-wheels (WOW) switch on the left main landing gear. As soon as the airplane took off and the WOW switch was opened, MCD warnings were disabled. When PC-12 and PC-12/45 airplanes were registered for use in Canada, Transport Canada required that they be modified so that the installed CAWS would display any engine MCD cautions throughout all phases of flight. Pilatus issued Service Bulletin (SB) No. 04-002, "Canadian Registration of PC-12 and PC-12/45 Aircraft," which called for the replacement of the CAWS in these airplanes with a system that would not inhibit any engine MCD cautions when the airplane was in flight. When PC-12 and PC-12/45 airplanes were registered in the United States, the FAA did not impose a similar requirement. The PWC PT6A-60 series engine MCD monitored the oil scavenged from the RGB; the MCD did not monitor the oil scavenged from the AGB and main engine bearings 1 and 2. After the oil was scavenged from the AGB and bearings, it was pumped back into the engine's oil tank and passed through the main oil filter, which trapped any debris in the oil scavenged from these areas before the oil was reused by the engine. On August 20, 2001, Pilatus issued SB No. 79-005, "Oil Indicating, Introduction of Chip Detector in Engine Accessory Gearbox," which made available the installation of a MCD in the AGB to monitor the gearbox oil-drain for metal particles. The airplane was not modified with this service bulletin. AIRDROME INFORMATION Trenton airport had two runways. Runway 6/24 was 6,006 feet long, 150 feet wide, and had an asphalt surface. Runway 16/34 was 4,800 feet long, 150 feet wide, and had an asphalt surface. METEOROLOGICAL INFORMATION The 1408 weather observation at Trenton included winds from 350 degrees at 17 knots, with gusts to 21 knots, visibility 3 statute miles, mist, a few clouds at 800 feet, and broken clouds at 1,200 feet. The 1440 weather observation included winds from 340 degrees at 17 knots, with gusts to 22 knots, visibility 3 statute miles, mist, and clouds at 800 feet overcast. WRECKAGE AND IMPACT INFORMATION The airplane had been moved to a hanger and placed on jacks prior to the arrival of the Safety Board investigator. The outboard portion of the left wing was lying adjacent to the airplane. A compression buckle was observed on the lower wing skin, outboard of the right main landing gear. The right main landing gear retraction cylinder was separated from the airframe. The steel shaft of the retraction cylinder on the left main landing gear had a compression buckle and was fractured. The nose landing gear was separated from the airplane with a compression buckle on the right side of the steel oleo strut. The left wing, outboard of the left main landing gear, was separated from the airplane. The wing flaps were in their maximum extended position of 40 degrees. Flight control continuity was observed on the elevator, rudder, and right aileron. The left wing was separated from the airplane, outboard of the left main landing gear. Flight control continuity was present to the break, and present on the separated portion of the wing. The four propeller blades were bent about mid-span, opposite the direction of rotation. The exhaust stacks were removed, and the turbine blades were smooth to the touch with no rough spots or evidence of damage. The turbine section of the engine rotated freely, with no binding. The compressor section of the engine was frozen. The MCD in the RGB was removed and the two magnetic poles were not bridged. The oil in the RGB contained small particles of ferrous material. The engine oil filter was removed and found to contain small particles of ferrous material. TESTS AND RESEARCH The engine was shipped to the Pratt & Whitney facility in Bridgeport, West Virginia, for further examination. During the engine examination, conducted under the supervision of the Safety Board, small particles of ferrous material were found in the accessory gearbox. The disassembly of the engine revealed that its No. 1 bearing ball cage was fractured into several pieces, which allowed the balls to be loose in the bearing compartment. The disassembly also revealed that the interior surfaces of the AGB were coated with metallic particles and that there was metallic debris in the oil filter. Rubbing was observed on components of the compressor drive shaft consistent with a rearward displacement of the compressor drive shaft. The starter-generator was mounted on the back of the AGB. The splined end of the starter-generator drive shaft connected to the starter-generator drive gear in the AGB. There was a direct link from the starter-generator drive gear to the No. 1 bearing, through the other gears in the AGB. Further, testing of various AGB gear components with a magnetometer revealed that the starter-generator drive gear had a reading of between 18 and 20 Gauss. Other AGB gear components also registered Gauss readings, which were lower the further away they were from the starter-generator drive gear. A gauss meter reading on the propeller drive shaft was negative for a magnetic field. Examination of the gears from the AGB was accomplished by PWC, under the supervision of the Transportation Safety Board of Canada. According to the report published by PWC: "Metallographic examination showed heat affected zones associated to the pits observed at the surface of the gears. The heat affected zone included the untempered martensite (re-hardened zone) and the overtemper zone. This indicates that the pits resulted from electrical erosion. Note that all the affected gears were located upstream of the No. 1 bearing PN3113589." "The primary cause of the No. 1 bearing distress could not determined because of considerable secondary damage obliterating the original surface and thus, preventing to confirm, the presence of pits on the rolling contact surfaces. Pits are spall originating surface defects. Progression of spalls leads to vibration causing eventually fracture of the cage by fatigue." A further examination of the parts was conducted by the Safety Board Metallurgical Laboratory in Washington, DC. They reported: "...The internal splines of the starter generator gear were examined...using an optical stereomicroscope. At the inner edge of the spline tooth flanks, many of the spline teeth had areas that appeared reflective and light in color. The shaft [with internal splines] portion of the gear was sectioned to facilitate the examination and documentation of these areas, and a view of one of these areas...The internal spline teeth flanks generally had a dark gray appearance corresponding to contact with the mating splines. The reflective area...is typical of similar areas seen near the ends of the spline contact regions on many of the spline teeth. These reflective areas had a globular appearance with smooth surfaces consistent with re

Probable Cause and Findings

A power loss, due to failure of the No. 1 bearing, which was a result of previous electrical discharge damage (EDD). Factors were the low ceiling and a wet runway.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports