# NTSB CEN11LA364: Piper PA30, N7248Y, Phillipsburg, OH, May 21, 2011 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: May 21, 2011, 07:45 local (11:45 UTC) - Place: Phillipsburg, OH - Coordinates: 39.913612, -84.399719 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.9136&lon=-84.3997&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report August 29, 2012 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 79277 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11LA364 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/79277/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=79277 - Page: https://openairdocs.org/ntsb/CEN11LA364 ## Probable cause The pilot’s failure to maintain directional control during takeoff following a loss of left engine power for undetermined reasons. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-30, 28 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103002), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [Piper PA-30, 2 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=7103002), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-30, 13 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103002), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-30, 16 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7103002), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Piper PA-30, 11 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103002), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Piper PA-30, 24 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7103002), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Takeoff: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); cases with it: [Piper PA-30, 3 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=7103002), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The pilot was taking off on a solo flight when the airplane veered off the runway. The pilot stated that the airplane experienced a loss of left engine power during the takeoff rotation. The pilot stated that he did not retard engine power quickly enough and that the airplane did not respond to his application of right rudder control. The airplane sustained substantial damage to the wings when it impacted trees. Postaccident examination of the accident site revealed only left main landing gear tire skid marks leading to the accident site. Functional testing of the left engine was precluded by impact damage. However, a teardown inspection of the engine revealed no issues that would have precluded its normal operation. The examination of the remaining airplane systems showed no anomalies. ## Factual narrative On May 21, 2011, about 0745 eastern daylight time, a Piper PA-30, N7248Y, experienced a loss of left engine power during takeoff roll from Phillipsburg Airport, Phillipsburg, Ohio. The airplane veered off the left side of runway 21 and impacted terrain. The certificated private pilot sustained minor injuries. The airplane received substantial damage to the fuselage and wings. The airplane was registered to Miller Aircraft Inc and operated by the pilot as an personal flight under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan had been filed for the local flight that was to remain in the airport traffic pattern. The flight was originating at the time of the accident. The pilot held a private pilot certificate with single-engine land and instrument airplane ratings but did not hold a multiengine airplane rating. The pilot had received a solo endorsement for a Piper PA-30 from his flight instructor. The flight instructor, who had been providing flight multiengine flight training to the pilot and instrument flight training in a Cessna 172 over the past year, held a valid airman medical certificate. The pilot stated that the purpose of the flight was to remain in the airport traffic pattern to practice solo takeoff and landings. The pilot began his first takeoff using runway 21 and during the takeoff rotation, the airplane yawed left and did not respond to an application of right rudder. He retarded the throttles and attempted to steer the airplane to toward the right but could not regain directional control of the airplane. The airplane went off the runway and impacted a wooded area. According to Federal Aviation Administration (FAA) inspectors, the pilot stated that the left yaw occurred about 85-90 mph and that he did not react quickly enough to retard engine power. The pilot stated that he was thrown forward and cut his forehead on the cabin roof and his right forearm was bruised from hitting the controls. The pilot reported that he did not use the airplane shoulder harness that was available. The pilot's flight instructor told FAA inspectors that on the morning of the accident, he was at the hanger, where the airplane was kept, waiting for the pilot because they were suppose to go flying. The flight instructor waited for awhile and then noticed the pilot walking up the taxiway and that he was injured. The pilot told the flight instructor that he was involved in an accident and asked the flight instructor to check the airplane. The flight instructor said that he turned the magnetos and all the switches off. The flight instructor was not sure what switches were on. The airplane was moved from the accident site to the registered aircraft owner's (previous owner's) hangar. The airplane was purchased by the pilot from the registered owner (previous owner) about a year prior to the accident and was not registered to the pilot. The accident was then reported on May 23, 2011, whenthe pilot contacted the FAA's Cincinnati Flight Standards District Office. According to the FAA, the pilot did not provide an explanation of why he had waited to report the accident. Examination of the accident site by FAA inspectors revealed the presence of several skid marks consistent with the left main landing gear tire leading up to the where the airplane impacted trees. The accident site was located about half down runway 21 and 107 feet from its left edge. The skid marks were oriented along a direction from runway towards the accident site. The skid marks were about 18 feet long and separated by about 100 feet from each other along the direction of travel. A third skid mark along the same direction was about 145 feet in length. There were numerous damaged trees around the accident site. Examination of the wreckage was performed at the registered owner's hangar. The position of all switches and engine controls could not be verified since the pilot and the registered owner stated that everything had been shut off after the accident. The fuel controls were also in the off position. The circuit breakers for the fuel boost pumps, turn and bank indicator, and the gear motor were out. There were three 40 lb bags of water softener salt and a portable oxygen canister in the rear cargo compartment. The upper left head lining showed signs of impact from the pilot. The flaps were in the retracted position. Examination of the flight controls confirmed flight control continuity. The right wing main and auxiliary fuel tanks were almost full. There were no fuel contaminants noted. The left wing separated from the fuselage and fuel leakage was exhibited out of the cross over tube. The left wing main and auxiliary fuel tanks were empty. Examination of the left engine revealed impact damage from the airplane's collision with the trees. The number one cylinder was cracked due to impact forces. The engine was crushed rearward and downward resulting in many of the engine accessories being broken off. Fuel was present in the fuel line leading to the fuel manifold. The propeller blades were bent and exhibited ground strikes consistent with low power. The engine was able to be rotated through using the propeller. Damage to the engine precluded functional testing. ## Aircraft - Registration: [N7248Y](https://openairdocs.org/deregistered/N7248Y-2011-08-09), registration cancelled 2011-08-09, S/N 30-273, built 1964 (OpenAirDocs) - Reported make and model: PIPER PA30 (NO SERIES) - Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs) - Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30-273 - Airframe hours: 5970 - Engines: Lycoming IO-320-B1A 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Pilot - Registered owner: Miller Aircraft Inc. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 15, 2010, 53 hours before - Departed: 3I7, Philipsburg, OH - Destination: 3I7, Philipsburg, OH - Airport: 3I7, Phillipsburg Airport, runway 21, 3,000 × 40 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 58; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review April 14, 2011; seat: left; flight hours: 304 total, 26 in this make and model, 196 as pilot in command, 32 in the last 90 days, 11 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Observed at: DAY, 8 nm away ## 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 20110521009589A](https://openairdocs.org/incident/20110521009589A), May 21, 2011: Piper PA-30, Phillipsburg, OH, Destroyed. On 21 may 2011, a Piper PA-30, registration # N7248Y, was taking off on runway 21 at Phillipsburg Airport (3I7) in Phillipsburg, Ohio. According to the pilot,… ## Docket (2 files) The files NTSB released with the investigation on July 6, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=79277. 1.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371296&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Examination (item 2, .PDF, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371586&FileExtension=.PDF&FileName=Record%20of%20Examination-Master.PDF 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.