Accident Details
Probable Cause and Findings
failure of the turbocharger exhaust clamp due to a pre-existing weld crack, which allowed the release of high temperature exhaust gasses in the engine compartment, causing an in-flight fire.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHT
On October 1, 2003, about 1541 Pacific daylight time, a Piper PA-32R-301T, N481CA, declared an in-flight fire emergency, and crashed shortly after takeoff in an unincorporated area of Corona, California. The pilot operated the airplane under the provisions of 14 CFR Part 91. The private pilot and a passenger were fatally injured. The airplane was destroyed in the post-impact fire. The cross-country flight departed the Corona Municipal Airport (AJO) about 1537, en route to Oakland, California. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan had been filed. The primary wreckage was located at 33 degrees 56.46 minutes north latitude and 117 degrees 34.41 minutes west longitude.
An airborne witness, who was practicing Instrument Landing System (ILS) approaches into the Chino Airport (CNO), Chino, California, overheard the radio transmission of the accident pilot declaring an emergency. He said someone contacted Southern California Terminal Radar Approach Control (SoCal TRACON) and had stated that they had a fire.
The airborne witness looked around for the aircraft and saw it off to his left side, and estimated its altitude was 3,000 feet. He saw the airplane flying level with trailing black smoke that did not have an area of concentration. The witness heard the accident pilot say that he had to get out of there, and then saw the airplane turn to the left. The witness watched the airplane make one spiraling turn and then impact the ground. He then saw a fireball. The witness orbited the area until a police helicopter arrived on scene.
Witnesses on the ground reported seeing the airplane in a nose down attitude with smoke and flames coming from the airplane.
PERSONNEL INFORMATION
According to the Federal Aviation Administration (FAA) airman records, the pilot held a private pilot certificate with an airplane single engine land rating issued February 12, 2003, and instrument airplane rating issued June 26, 2003.
The pilot held a third-class medical certificate issued on January 30, 2003. It had no limitations or waivers.
A personal logbook was not obtained for the pilot. According to FAA form 8710-1 titled Airman Certificate and/or Rating Application dated June 26, 2003, the pilot reported a total flight time of 130 hours.
AIRCRAFT INFORMATION
The airplane was a 1999 Piper PA-32R-301T, serial number 3257081. A review of the airplane's logbooks revealed a total airframe time of 772.8 hours at the last annual inspection completed on May 9, 2003. The Hobbs hour meter and tachometer were thermally destroyed the accident site.
The airplane was equipped with a Textron Lycoming TIO-540-AH1A engine, serial number L-10137-61A. Total time on the engine at the last annual inspection was 772.8 hours.
Penn Yan Aero, Penn Yan, New York, completed a logbook entry regarding Textron Lycoming Service Bulletin 553 on April 28, 2003, at a Hobbs hour meter of 772.6 hours. The entry recorded the following information:
"Disassembled, cleaned, inspected, and repaired engine as required to comply with Lycoming Service Bulleting 553. Installed new crankshaft S/N: V537930052, new cylinder kits, and oil sump housing. Reassembled engine using parts as listed on the supplied work order in accordance with data approved by or acceptable to the FAA. Test cell run satisfactory for return to service."
Shoreline Aviation, Inc., Marshfield, Massachusetts, reinstalled the engine on the airplane on May 9, 2003, and performed an annual inspection.
An invoice from High Performance Aircraft, Inc., El Cajon, California, dated August 19, 2003, reported that an adjustment to the manifold pressure for critical altitude was completed. The pilot reported that the pressurized intake system would not achieve critical and maximum pressure. Maintenance personnel noted that the pressurization issue started after Textron Lycoming Service Bulletin 553 - crankshaft replacement had been completed in April 2003. Maintenance personnel indicated that the corrective action was: "Pressurized intake system, found no excessive manifold air leaks, adjusted [variance] to achieve redline [manifold pressure], adjusted waste gate actuator to close, manifold pressure holds to critical altitude at this time." Maintenance personnel completed a logbook entry for the work, and entered the Hobbs hour meter time as 850.6 hours.
An invoice from Procraft Aviation, Inc., Corona, dated September 26, 2003, reported the following work as being completed: "change oil, filter and inspect element, degrease engine, check all engine controls, repair left front baffle as required, fabricate and install doublers." The Hobbs hour meter was recorded as 905 hours. However, there was no corresponding logbook entry.
Logbook Review
Engine logbook entries recorded the fuel pump as an "AN" rotary engine driven fuel pump, part number LW13909, (Lear-Romec part number RG-9080-J4A), serial number D9679, and had been installed on the airplane prior to the accident. The engine manufacturer reported that an Airworthiness Directive (AD) 98-18-12 dated September 11, 1998, and Lycoming Mandatory Service Bulletin (SB) SB529B, dated June 10, 2002, were applicable to the engine driven fuel pump installed on the accident airplane. Both the AD and SB were issued to prevent rotary fuel pump leaks, which could result in an engine failure or engine fire.
The New Piper Aircraft Company issued a mandatory Service Bulletin number 1035 dated September 3, 1999, in response to AD 98-18-12, and Textron Lycoming SB 529A, with instructions to follow the AD and engine manufacturer's SB.
According to the AD under Note 1b, if the fuel pump part number did not have the "/M" suffix, such as the accident fuel pump, it required the performance of an initial and then follow-up torque check inspections of the pump relief valve attaching screws.
The AD and SB required a torque check at 50-hour intervals until two consecutive checks indicated that there was no change in the torque. Then a visual check was to take place every 50 hours. There were two engine logbook entries that showed compliance with the torque check inspection as required AD 98-18-12. There was an engine logbook entry dated February 17, 1999, at 5 hours time in service (TIS). Another logbook entry dated October 21, 1999, showed compliance with the AD at a total time of 174.2 hours TIS.
The AD compliance checklist in the engine logbook indicated under the method of compliance section that the screw torque was checked per AD 98-18-12, and found okay (second check), and that no further action was required. There were no further visual inspections recorded as required per the AD in the engine or airframe logbooks pertaining to the recurring visual checks of the fuel pump.
On August 14, 2004, AD 2003-14-03 was issued superseding AD 98-18-12; however, it still required the screw torque inspection cycle. There were no entries concerning AD 2003-14-03 in either the airframe or engine logbooks.
COMMUNICATIONS
The pilot was in contact with air traffic personnel from Empire Riverside Radar (RALR - Southern California Terminal Radar Control - SoCal TRACON). At 1539, RALR amended the assigned altitude for the accident airplane to 5,000 feet, which the pilot acknowledged. At 1540, while RALR was issuing directions, the accident pilot declared an emergency due to an onboard fire.
Radio communications between the pilot and the controller indicated that the pilot received his IFR release from AJO at 1536. The airplane was airborne at 1537. At 1538, the pilot contacted SoCal TRACON climbing through 1,300 feet. At 1540:32, the pilot declared an emergency saying he thought he had a fire. The airplane crashed at 1541.
WRECKAGE AND IMPACT INFORMATION
Investigators from the National Transportation Safety Board, the FAA, and Textron Lycoming, a party representative to the accident investigation, examined the wreckage at the accident scene.
The airplane came to rest in an open field. The accident site was located on a horse farm about 4 miles southwest of AJO on a magnetic bearing of 192 degrees in flat terrain, surrounded by bamboo and small trees. All of the airplane's major components were at the accident site. The first identified point of contact (FIPC) was the 3-foot-deep crater where the engine came to rest. The engine was at an 85-degree nose down angle. Fire damage consumed most of the accessory section. The crankshaft had separated forward of the number one rod journal. The forward portion of the engine case was extensively fractured. One of the propeller blades had fractured near the hub, and the other two were loose at their respective hub sockets. All three of the propeller blades showed varying degrees of leading and trailing edge gouging, chordwise scratching, and S-bending.
The airplane had been largely consumed by fire. The fuselage was in line with the debris path, and located just forward of the engine. The wing spars, with partial wing skin, were parallel to the longitudinal axis of the fuselage. The tail section was lying over the right side of the fuselage.
Investigators found a portion of wing skin about 150 feet west of the main wreckage site with no fire damage present. The top engine cowling was about 100 feet from the main wreckage with soot present on the outside; however, there was no soot on the inside. A burned aft cargo door (the smaller one) was about 95 feet from the main wreckage.
MEDICAL AND PATHOLOGICAL INFORMATION
The Riverside County Sheriff-Coroner's Department conducted an autopsy on the pilot on October 3, 2003. The cause of death was listed as multiple blunt force trauma.
The FAA Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, performed a toxicological analysis from samples obtained from the pilot during the autopsy. The results of the analysis of the specimens were neg...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# LAX04FA001