# NTSB ERA14CA373: Piper PA-46-350P, N472ST, Statesville, NC, August 2, 2014

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: August 1, 2014, 21:00 local (Aug 2, 2014, 01:00 UTC)
- Place: Statesville, NC
- Coordinates: 35.779956, -80.879249 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.7800&lon=-80.8792&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Landing area overshoot](https://openairdocs.org/ntsb-events/380)
- Highest injury: Minor injuries
- Injuries: 2 minor, 2 uninjured
- Status: Completed, report September 2, 2014
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- NTSB case key (mKey): 89786
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14CA373
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89786/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89786
- Page: https://openairdocs.org/ntsb/ERA14CA373

## Probable cause

The pilot's failure to maintain a proper glide path and airspeed on final approach, which resulted in a long landing and runway excursion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [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 46-350P, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7104620), [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 · Not attained/maintained (probable cause); cases with it: [Piper PA 46-350P, 15 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=7104620), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA 46-350P, 40 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7104620), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Ceiling/visibility/precip: low ceiling](https://openairdocs.org/ntsb-findings/03035010): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Piper PA 46-350P, 1 case](https://openairdocs.org/ntsb-findings/03035010/cases.md?model=7104620), [All aircraft, 190 cases](https://openairdocs.org/ntsb-findings/03035010/cases.md)
- [Object/animal/substance: debris/dirt/foreign object](https://openairdocs.org/ntsb-findings/03022055): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA 46-350P, 1 case](https://openairdocs.org/ntsb-findings/03022055/cases.md?model=7104620), [All aircraft, 101 cases](https://openairdocs.org/ntsb-findings/03022055/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) (defining event); cases with it: [Piper PA 46-350P, 2 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=7104620), [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 46-350P, 20 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7104620), [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 46-350P, 40 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7104620), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

According to the pilot, she was flying an instrument landing system approach when she noted that the glide slope was out of service. She transitioned to a localizer-only approach and continued. Night, instrument meteorological conditions prevailed with a 400-foot ceiling. She noticed that the airplane was "high and fast" on final approach, so she used speed brakes and flaps to slow the airplane and descend to the minimum descent altitude. As the airplane descended below the ceiling, she observed runway lights and attempted to land on the runway. The airplane landed long, departed the runway at the departure end, and struck an embankment before coming to rest. An inspector from the Federal Aviation Administration examined the airplane and confirmed substantial damage to the fuselage, wings, and empennage. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

## Factual narrative

According to the pilot, she was flying an instrument landing system approach when she noted that the glide slope was out of service. She transitioned to a localizer-only approach and continued. Night, instrument meteorological conditions prevailed with a 400-foot ceiling. She noticed that the airplane was "high and fast" on final approach, so she used speed brakes and flaps to slow the airplane and descend to the minimum descent altitude. As the airplane descended below the ceiling, she observed runway lights and attempted to land on the runway. The airplane landed long, departed the runway at the departure end, and struck an embankment before coming to rest. An inspector from the Federal Aviation Administration examined the airplane and confirmed substantial damage to the fuselage, wings, and empennage. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N472ST](https://openairdocs.org/deregistered/N472ST-2015-08-13), registration cancelled 2015-08-13, S/N 4636472, built 2010 (OpenAirDocs)
- Reported make and model: PIPER PA-46-350P
- Registry model: [Piper PA 46-350P](https://openairdocs.org/model/piper-pa-46-350p) (registry code 7104620) (OpenAirDocs)
- Registry engine: [Lycoming TIO-540-AE2A](https://openairdocs.org/engine/lycoming-tio-540-ae2a) (registry code 41999, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 4636472
- Year built: 2010
- Airframe hours: 1656
- Engines: LYCOMING TIO-540-AE2A 350 horsepower reciprocating
- Damage: Substantial damage
- Flight: Business, Part 91
- Operator: Ets Aviation LLC
- Registered owner: Ets Aviation LLC
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, July 18, 2014
- Departed: HEF, Manassas, VA
- Destination: SVH, Statesville, NC
- Flight plan: IFR
- Airport: SVH, Statesville Regional, runway 28, 7,005 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 29; injuries: minor; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review October 12, 2012; seat: left; restraint: 3-point; flight hours: 2,556 total, 1,200 in this make and model, 2,512 as pilot in command, 120 in the last 90 days, 57 in the last 30 days, 6 in the last 24 hours

## Weather

- Conditions: Instrument (IMC), Night
- Wind: 20° at 5 knots
- Visibility: 5 statute miles
- Lowest ceiling: 400 ft overcast
- Temperature: 64 °F, dew point 63 °F
- Altimeter: 30.12 inHg
- Observed at: SVH

## 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 20140801012599A](https://openairdocs.org/incident/20140801012599A), Aug 1, 2014: Piper PA 46-350P, Statesville, NC, Destroyed. Aircraft attempted landing in reported IFR conditions. First evidence of aircraft tire marks were approximately 750 feet from end of runway 28R. Aircraft…

## Docket (6 files)

The files NTSB released with the investigation on August 12, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89786. 6.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414947&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Memorandum of Record - FAA Inspector (item 2, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414948&FileExtension=.PDF&FileName=Memorandum%20of%20Record%20-%20FAA%20Inspector-Master.PDF
- Photo 1. Main Wreckage (Photo Courtesy of FAA) (item 3, .PDF, 83 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414949&FileExtension=.PDF&FileName=Photo%201.%20Main%20Wreckage%20(Photo%20Courtesy%20of%20FAA)-Master.PDF
- Photo 2. Fuselage and Left Wing Root (Photo Courtesy of FAA) (item 4, .PDF, 102 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414950&FileExtension=.PDF&FileName=Photo%202.%20Fuselage%20and%20Left%20Wing%20Root%20(Photo%20Courtesy%20of%20FAA)-Master.PDF
- Photo 3. Aircraft Wreckage (Photo Courtesy of FAA) (item 5, .PDF, 89 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414951&FileExtension=.PDF&FileName=Photo%203.%20Aircraft%20Wreckage%20(Photo%20Courtesy%20of%20FAA)-Master.PDF
- Photo 4. Embankment (Photo Courtesy of FAA) (item 6, .PDF, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40414952&FileExtension=.PDF&FileName=Photo%204.%20Embankment%20(Photo%20Courtesy%20of%20FAA)-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.
