# NTSB ERA13CA393: Cessna 172E, N3513S, Apex, NC, August 30, 2013

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 30, 2013, 16:45 local (20:45 UTC)
- Place: Apex, NC
- Coordinates: 35.738056, -78.920829 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.7381&lon=-78.9208&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report October 21, 2013
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 87948
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA13CA393
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87948/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87948
- Page: https://openairdocs.org/ntsb/ERA13CA393

## Probable cause

The pilot's failure to attain the proper touchdown point on the runway, which resulted in a runway overrun and subsequent aircraft noseover.

## Findings

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

- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172E, 2 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072412), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)
- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172E, 3 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072412), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 172E, 5 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072412), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172E, 4 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072412), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md)

## Analysis

Immediately after the accident, the pilot reported to the responding police officer that he landed “hot,” and “overshot” the 1,950-foot-long turf runway. The airplane overran the departure end of the runway, struck a ditch, nosed over, and came to rest inverted with substantial damage to the wings, empennage, and tail section of the airplane. Interpolation of the airplane manufacturer’s landing distance chart revealed that the required landing distance over a 50-foot obstacle was approximately 1,300 feet. The pilot stated that there were no mechanical deficiencies with the airplane that would have precluded normal operation.

## Factual narrative

Immediately after the accident, the pilot reported to the responding police officer that he landed “hot,” and “overshot” the 1,950-foot-long turf runway. The airplane overran the departure end of the runway, struck a ditch, nosed over, and came to rest inverted with substantial damage to the wings, empennage, and tail section of the airplane. Interpolation of the airplane manufacturer’s landing distance chart revealed that the required landing distance over a 50-foot obstacle was approximately 1,300 feet. The pilot stated that there were no mechanical deficiencies with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N3513S](https://openairdocs.org/deregistered/N3513S-2014-01-27), registration cancelled 2014-01-27, S/N 17250713, built 1963 (OpenAirDocs)
- Reported make and model: CESSNA 172E
- Registry model: [Cessna 172E](https://openairdocs.org/model/cessna-172e) (registry code 2072412) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17250713
- Airframe hours: 4297
- Engines: CONT MOTOR 0-300 SER 145 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Esterly Bryan H
- Registered owner: Esterly Bryan H
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, March 2, 2013
- Departed: 2GC, Fayetteville, NC
- Destination: NC11, Apex, NC
- Airport: NC11, Deck Airpark, runway 04, 1,950 × 10 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 73; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: left; flight hours: 1,520 total, 1,200 in this make and model, 9 in the last 90 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 110° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 88 °F, dew point 61 °F
- Altimeter: 29.96 inHg
- Observed at: RDU, 10 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 20130830017299A](https://openairdocs.org/incident/20130830017299A), Aug 30, 2013: Cessna 172E, Apex, NC, Substantial damage. A landing was made on a 1,900 foot long private grass runway near Apex, NC in a 1966 Cessna 172E. There are tall trees on both ends of the runway. The aircraft…

## Docket (4 files)

The files NTSB released with the investigation on September 25, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87948. 3.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 667 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40401398&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Police Report Narrative Excerpt (item 2, .PDF, 34 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40401189&FileExtension=.PDF&FileName=Police%20Report%20Narrative%20Excerpt-Redacted.PDF
- FAA Inspector Interview Summary (item 3, .PDF, 108 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40400370&FileExtension=.PDF&FileName=FAA%20Inspector%20Interview%20Summary-Master.PDF
- Photo 1 - View of Airplane as Found (FAA) (item 4, .PDF, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40400372&FileExtension=.PDF&FileName=Photo%201%20-%20View%20of%20Airplane%20as%20Found%20(FAA)-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.