# NTSB ERA11CA445: Piper PA-32RT-300, N30731, Charleston, SC, August 9, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 9, 2011, 09:45 local (13:45 UTC) - Place: Charleston, SC - Coordinates: 32.910263, -80.090461 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.9103&lon=-80.0905&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 20, 2012 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 81432 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA445 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81432/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81432 - Page: https://openairdocs.org/ntsb/ERA11CA445 ## Probable cause The pilot's decision to continue the approach and landing at a high airspeed, which resulted in an improper touchdown point and subsequent runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32RT-300, 4 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7103215), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-32RT-300, 2 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7103215), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Piper PA-32RT-300, 3 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=7103215), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-32RT-300, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7103215), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Piper PA-32RT-300, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=7103215), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-32RT-300, 5 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103215), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32RT-300, 11 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103215), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot stated that he was approaching the airport for landing at an altitude of 2,500 feet. He requested and received clearance for a 360-degree turn to lose altitude prior to continuing the landing approach. The pilot stated that the airplane's airspeed was too high as it crossed the runway threshold, but he elected to continue the landing. The airplane touched down, but the pilot was unable to stop the airplane before it traveled off the end of the runway and impacted a fence, which resulted in substantial damage to the left wing. The pilot stated that there were no mechanical malfunctions or anomalies with the airplane and that he should have executed a go-around rather than continuing the approach and landing. ## Factual narrative The pilot stated that he was approaching the airport for landing at an altitude of 2,500 feet. He requested from the airport control tower, and was subsequently cleared for, a 360-degree turn to lose altitude prior to continuing the landing approach. The pilot stated that the airplane's airspeed was too high as it crossed the runway threshold, but he elected to continue the landing. The airplane touched down, but the pilot was unable to stop the airplane before it traveled off the end of the runway and impacted a fence, resulting in substantial damage to the left wing. The pilot stated there were no mechanical malfunctions or anomalies with the airplane, and that he should have executed a go-around rather than continuing the approach and landing. ## Aircraft - Registration: [N30731](https://openairdocs.org/aircraft/N30731), registered now, S/N 32R-7885089, built 1978 (OpenAirDocs) - Reported make and model: PIPER PA-32RT-300 - Registry model: [Piper PA-32RT-300](https://openairdocs.org/model/piper-pa-32rt-300) (registry code 7103215) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32R-7885089 - Airframe hours: 1839 - Engines: LYCOMING IO-540 SER 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Arthur Thayer R Jr - Registered owner: Arthur Thayer R Jr - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 21, 2011 - Departed: DYB, Summerville, SC - Destination: CHS, Charleston, SC - Airport: CHS, Charleston International, runway 03, 7,000 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 69; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review August 24, 2009; seat: left; flight hours: 759 total, 411 in this make and model, 691 as pilot in command, 1 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 86 °F, dew point 72 °F - Altimeter: 29.78 inHg - Observed at: CHS ## 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 20110809017359A](https://openairdocs.org/incident/20110809017359A), Aug 9, 2011: Piper PA-32RT-300, Charleston, SC, Substantial damage. On August 9, 2011, at 10:30 am , N30731, a Piper PA-32-RT-300 operating part 91 VFR, landed high, fast and long at Charleston, SC, (chs) airport. The aircraft… ## Docket (1 files) The files NTSB released with the investigation on February 3, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81432. 397 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 397 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40353282&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.