# NTSB NYC03FA008: Pilatus PC-12/45, N96WF, Trenton, NJ, October 16, 2002 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Field investigation · Final report - Date: October 16, 2002, 14:24 local (18:24 UTC) - Place: Trenton, NJ - Coordinates: 40.271667, -74.806663 - Nearby events: https://openairdocs.org/map.md?lat=40.2717&lon=-74.8067&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 1 minor, 3 uninjured - Status: Completed, report June 2, 2004 - Report: Approved by Office Director - Parties: Pratt & Whitney Canada, Goodrich, Pilatus Aircraft Ltd, Federal Aviation Administration - Safety recommendations: Yes - NTSB case key (mKey): 55884 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC03FA008 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55884/pdf - Page: https://openairdocs.org/ntsb/NYC03FA008 ## Probable cause 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - mech failure/malf, takeoff - initial climb - electrical system,generator - shorted (cause) - engine assembly,bearing - failure (cause) - Forced landing, descent - emergency - Overrun, landing - roll - weather condition - low ceiling - terrain condition - wet - On ground/water collision with object, landing - roll - object - fence ## 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 narrative 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 ## Aircraft - Registration: [N96WF](https://openairdocs.org/deregistered/N96WF-2003-09-09), registration cancelled 2003-09-09, S/N 139, built 1996 (OpenAirDocs) - Reported make and model: Pilatus PC-12/45 - Registry model: [Pilatus PC-12/45](https://openairdocs.org/model/pilatus-pc-12-45) (registry code 7090551) (OpenAirDocs) - Registry engine: [Pratt & Whitney PT6A series](https://openairdocs.org/engine/pratt-whitney-pt6a-series) (registry code 52032, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 139 - Airframe hours: 2627 - Engines: Pratt & Whitney Canada PT6A-67B 1200 horsepower turbo prop - Damage: Substantial damage - Flight: Executive/Corporate, Part 91 - Operator: The Nielsen-Wurster Group, Inc. - Registered owner: Unionville, Aviation - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, September 12, 2002, 32.6 hours before - Departed: TTN, Trenton, NJ - Destination: IAD, Washington, VA - Flight plan: IFR - Airport: TTN, Trenton Mercer, runway 16, 4,800 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: none; commercial, flight instructor, airline transport, flight engineer; airplane ratings: single-engine sea, multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; last flight review April 6, 2002; seat: left; flight hours: 26,274 total, 563 in this make and model, 15,672 as pilot in command, 54 in the last 90 days, 21 in the last 30 days - Co-pilot; age 43; injuries: none; flight instructor, commercial, airline transport; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1; last flight review June 14, 2002; seat: right; flight hours: 12,000 total, 1,500 in this make and model, 11,500 as pilot in command, 130 in the last 90 days, 53 in the last 30 days, 7 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: 340° at 17 knots, gusting 21 - Visibility: 3 statute miles - Lowest ceiling: 800 ft overcast - Temperature: 52 °F, dew point 50 °F - Altimeter: 29.35 inHg - Observed at: TTN ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20021016037609A](https://openairdocs.org/incident/20021016037609A), Oct 16, 2002: Pilats PC1245, Trenton, NJ, Substantial damage. (-23) N96WF departed runway 06 at kttn. At 800 ft. while in a left-hand turn to proceed per IFR on a clearance, the pilot noticed an unidentifiable odor,… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.