# NTSB CEN12LA337: Piper PA-28-181, N2434M, Put-in-Bay, OH, June 4, 2012 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 4, 2012, 12:17 local (16:17 UTC) - Place: Put-in-Bay, OH - Coordinates: 41.636665, -82.82833 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.6367&lon=-82.8283&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report July 29, 2013 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 83863 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN12LA337 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/83863/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=83863 - Page: https://openairdocs.org/ntsb/CEN12LA337 ## Probable cause The pilot's failure to attain a proper touchdown point at the proper speed, his failure to initiate a go-around, and the airplane’s inadequate climb gradient after the aborted landing, which resulted in impact with the trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-181, 4 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=7102807), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-181, 11 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=7102807), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-181, 6 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102807), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Aircraft capability: climb capability](https://openairdocs.org/ntsb-findings/01061010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-181, 1 case](https://openairdocs.org/ntsb-findings/01061010/cases.md?model=7102807), [All aircraft, 183 cases](https://openairdocs.org/ntsb-findings/01061010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Piper PA-28-181, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=7102807), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Piper PA-28-181, 8 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7102807), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-aborted after touchdown: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Piper PA-28-181, 9 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=7102807), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-181, 70 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102807), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The airplane touched down too far down the runway at a high rate of speed and began to porpoise. The pilot aborted the landing, and during the climb, which was too shallow, the airplane's left wing struck trees near the departure end of the runway and was substantially damaged. The airplane returned to the airport and landed without further incident. Postaccident examination revealed no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation ## Factual narrative On June 4, 2012, at 1217 eastern daylight time, a Piper PA-28-181, N2434M, was substantially damaged when it struck a tree during climbout from an aborted landing at Put-in-Bay Airport (3W2), Put-in-Bay, Ohio. The pilot returned to the airport and landed without further incident. The private pilot and three passengers were uninjured. The airplane was registered to and operated by Bluffton Sky Pirates, Inc., under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed and a flight plan had not been filed for the flight that departed from Bluffton Airport (5G7), Bluffton, Ohio, about 1030, and was destined for 3W2. According to the Federal Aviation Administration inspector, the airplane touched down too far down runway 3 (2,870 feet by 75 feet, asphalt), at a fast speed, and began to porpoise. The pilot then performed an aborted landing. During climbout, the airplane's left wing sustained damage to the left wing rib when it struck trees at the departure end of the runway. No other anomalies were found with the airplane. ## Aircraft - Registration: [N2434M](https://openairdocs.org/aircraft/N2434M), registered now, S/N 28-7890251, built 1977 (OpenAirDocs) - Reported make and model: PIPER PA-28-181 - Registry model: [Piper PA-28-181](https://openairdocs.org/model/piper-pa-28-181) (registry code 7102807) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7890251 - Airframe hours: 6142 - Engines: Lycoming O-360-A4M reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Bluffton Sky Pirates Inc - Registered owner: Bluffton Sky Pirates Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 1, 2011 - Departed: 5G7, Bluffton, OH - Destination: 3W2, Put-in-Bay, OH - Airport: 3W2, Put in Bay Airport, runway 03, 2,870 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 68; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review August 25, 2011; seat: left; flight hours: 1,188 total, 300 in this make and model, 1,062 as pilot in command, 7 in the last 90 days, 2 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 10° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 55 °F - Altimeter: 29.82 inHg - Observed at: PCW, 7 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 20120604010469A](https://openairdocs.org/incident/20120604010469A), Jun 4, 2012: Piper PA-28-181, Put In Bay, OH, Substantial damage. After two failed attempts to land at Put In Bay, airman made contact with the runwayon the second landing attempt, aborted a landing, initiated a go around,… ## Docket (3 files) The files NTSB released with the investigation on June 12, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=83863. 715 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 622 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40387842&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation (item 2, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40387844&FileExtension=.PDF&FileName=Record%20of%20Conversation-Master.PDF - Weather (item 3, .PDF, 43 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40387843&FileExtension=.PDF&FileName=Weather-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.