Accident Details
Probable Cause and Findings
A partial loss of engine power due to contamination in the fuel manifold, which resulted in a collision with terrain shortly after takeoff.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn May 8, 2015, about 0959 eastern daylight time, a Piper PA-32R-300, N5802V, collided with a highway barrier during a forced landing attempt near Chamblee, Georgia. The commercial pilot and three passengers were fatally injured and the airplane was destroyed. The airplane was registered to and operated by TLT and GGBB LLC., as a personal flight. Day, visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules (IFR) flight plan. The flight originated from Peachtree DeKalb airport (PDK), Chamblee, Georgia, about 0956 and was destined for University-Oxford Airport (UOX), Oxford, Mississippi.
The accident flight was the second leg of a cross-country flight that originated earlier that morning from Asheville Regional Airport (AVL), Asheville, North Carolina.
Review of air traffic control (ATC) voice communication data provided by the Federal Aviation Administration (FAA) revealed that the pilot contacted clearance delivery for an IFR clearance. ATC provided the clearance, which included radar vectors, and "climb and maintain 3,000; expect 8,000 in 10 minutes." The pilot read back the clearance correctly and confirmed that he had the most recent automatic terminal information service, which was information "Whiskey." The pilot contacted ground control and indicated that he was ready to taxi. Ground control instructed the pilot to taxi to runway 3R, via taxiway Bravo, hold short of runway 3L and the pilot read back the instructions correctly. The pilot then contacted the tower controller, informing him that he was holding short of runway 3L and ready to depart. The tower controller instructed the pilot to "fly heading 360 and cleared for takeoff." The pilot then questioned the controller regarding which runway to take off from and the controller cleared the pilot for takeoff from runway 3L, which was 3,746 feet long. Approximately 3 minutes after departure, the tower controller called the pilot to verify his heading. The pilot responded "zero-two-victor, I'm having some problem climbing here." The pilot subsequently stated "zero-two-victor; were going down here at the intersection." This was the last transmission made by the pilot.
A witness stated that he was about 2,300 feet off the departure end of the runway. He stopped to look at the airplane because it was moving extremely slow and only 75 to 100 feet above ground level when it went over his head. He added that the engine sounded normal and despite the slow speed. He continued to watch the airplane as it flew out of his view.
Another witness that observed the airplane prior to the accident said he heard a "clacking sound," but the engine rpm did not change. The engine sounded like it was at "wide open throttle" as it descended onto the highway and exploded.
According to the pilot's mechanic, about 4 days prior to the accident flight, the mechanic observed a departure conducted by the pilot. He said that during climbout he watched as the airplane cleared trees at the departure end of the runway by approximately 50 feet. He added that shortly after that flight, the pilot called him and expressed his concern that the airplane was not climbing well. The mechanic mentioned to him that it was a warm day, and he was only a few hundred pounds under gross weight, with a slight tailwind. The mechanic further stated that the pilot said that he would do a run-up and if everything checked out, he would conduct a test flight the next day. The following day the pilot sent a text message to the mechanic and said that the run-up was good, but he wasn't getting full rpm at full power while static. About 30 minutes later, the pilot called the mechanic and told him he flew the airplane and everything was normal.
According to pilot's flight instructor, he said that the pilot called him 4 days prior to the accident flight and told him that he went flying and had some difficulty getting the airplane to gain altitude. He said that he had used up more than half of the runway when he was able to finally get the airplane in the air. The pilot told the instructor that he almost hit the trees near the end of the runway. The pilot also stated to the flight instructor that he did conduct "pre and post flight engine checks and noted no problems." PERSONNEL INFORMATIONThe pilot held a commercial pilot certificate with ratings for airplane single-engine land and instrument airplane. He reported a total flight experience of 667 hours, including 40 hours during the last 6 months, on his FAA second-class medical certificate application, dated November 18, 2014. The medical certificate indicated no restrictions. Review of the pilot's logbook revealed he had accumulated 687 total hours; of which, 672 hours were in the same make and model as the accident airplane. AIRCRAFT INFORMATIONThe airplane was manufactured in 1977. It was powered by a Lycoming O-540-K1G5D engine rated at 300 horsepower at 2,700 rpm, and was equipped with a Hartzell three-bladed constant speed propeller.
The last annual inspection of the airframe and engine occurred on July 22, 2014, at an airframe total time of 5616.03 hours. The last recorded maintenance included the installation of a battery on May 5, 2015.
The airplane's maintenance logbooks were not located and were presumed to have burned in the aircraft wreckage. Copies of airframe and engine logbook entries dated July 22, 2014 were provided by the mechanic who completed an annual inspection of the airplane on that date. The airframe logbook entry noted the tachometer hour meter reading and airframe total time as 5616.03 hours. The engine logbook entry indicated that the engine had accumulated 774.86 hours since major overhaul, as of that date. METEOROLOGICAL INFORMATIONThe recorded weather at PDK, at 0953, included winds from 080 degrees at 4 knots; 6 statute miles visibility, few clouds at 6,000 feet, temperature 24 degrees Celsius (C), dew point temperature 16 degrees C, and an altimeter setting of 30.14 inches of mercury. The calculated density altitude was about 2,259 feet. AIRPORT INFORMATIONThe airplane was manufactured in 1977. It was powered by a Lycoming O-540-K1G5D engine rated at 300 horsepower at 2,700 rpm, and was equipped with a Hartzell three-bladed constant speed propeller.
The last annual inspection of the airframe and engine occurred on July 22, 2014, at an airframe total time of 5616.03 hours. The last recorded maintenance included the installation of a battery on May 5, 2015.
The airplane's maintenance logbooks were not located and were presumed to have burned in the aircraft wreckage. Copies of airframe and engine logbook entries dated July 22, 2014 were provided by the mechanic who completed an annual inspection of the airplane on that date. The airframe logbook entry noted the tachometer hour meter reading and airframe total time as 5616.03 hours. The engine logbook entry indicated that the engine had accumulated 774.86 hours since major overhaul, as of that date. WRECKAGE AND IMPACT INFORMATIONThe wreckage was located in the eastbound lane of interstate 285, approximately 2 miles from PDK. The airplane came to rest in the left service lane against a 5 foot barrier wall on a heading of 021 degrees magnetic. There was a postcrash fire that consumed the majority of the airplane. There were ground scars across four traffic lanes up to the concrete highway divider.
The cockpit and fuselage were fragmented and destroyed by postcrash fire. Flight control cables were attached to fragments of the flight controls. The right and left wings were fragmented and was destroyed by postcrash fire. The flight control surfaces were molten metal on both wings. The aileron bellcranks on the left and right wings were located within the fragments of the wings and connected to the flight control cables and turnbuckles. Flight control cable separations exhibited signs of overstress failures. The empennage was fragmented and fire damaged. The flight control cables to the rudder control sector and stabilator bell crank remained attached to the fragmented fuselage and were traced to the forward section of the cockpit.
The left and right main landing gear were found in the extended position and the flap handle was impact damaged and observed in the 10-degree flap extension position. The throttle was found forward in the "full power" position, the propeller lever was forward at the "full increase" position, and the mixture lever was full forward at the "full rich" position. The fuel boost pump switch and selector was destroyed. Engine control linkage continuity was established from the cockpit controls to their respective engine connections.
An examination of the fuel system revealed that the all of the fuel lines before the firewall were destroyed. The fuel lines from the firewall to the fuel manifold were partially fire damaged. The fuel manifold and injector lines did not show signs of fire damage. The fuel manifold was removed during the examination of the engine and placed on a test bench and did not flow when tested up to 7 psi (normal test pressure is 4.5 psi). The unit was removed from the test bench and the bottom cover was removed. Following removal of the bottom cover, the gasket did not exhibit heat damage. The bottom portion of the movable portion of the body assembly was measured and found to be positioned 0.032 inch below the spool of the body assembly (normal closed position). The bottom of the movable portion of the body assembly was pushed by hand and some resistance was noted at first, but it then moved. The bottom cover was reinstalled and the four screws were torqued to the proper setting. The fuel manifold was placed on the test bench and debris was noted coming from the ports during initial flow. The unit was flowed at 4.5 psi (normal) and it was found to flow equally from all ports at 132 pounds-per-hour (pph); the minimum specification was 135 pph. The fuel manifold was removed ...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA15FA208