ERA14CA373 · Piper PA-46-350P
Ets Aviation Piper PA-46-350P · Accident: landing area overshoot
From Washington Manassas Harry P. Davis Field (HEF) to Statesville Regional Airport (SVH)
Event
- NTSB case
- ERA14CA373
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Piper PA-46-350P
- Aircraft type
- Piper PA-46
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N472ST
- Operator
- Ets Aviation
- Onboard fatalities
- Unknown
- Route
- From Washington Manassas Harry P. Davis Field (HEF), Manassas, VATo Statesville Regional Airport (SVH), Statesville, NC
- Aircraft age
- About 4 years (built 2010)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area overshoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA373
- Event ID
- 20140803X82134
- Case number
- ERA14CA373
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-08-02.
- API snapshot SHA-256: d0bcac93b1d7588174afe69a3d187e0571725df62acb16a60f71fbaf4ed34bf2; retrieved 2026-09-16T01:35:42.393Z.