ERA13CA393

NTSB accident investigation · Cessna 172E · Apex, NC · August 30, 2013

Accident · No injuriesData collectionFinal report
Date
August 30, 2013, 16:45 local (20:45 UTC)
Place
Apex, NC
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3513SCessna 172E
Defining event
Landing-landing roll: Runway excursion
Weather
Visual (VMC) · Day
Status
Completed · report October 21, 2013
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20130830017299A
Case key
87948

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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 · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Action: incorrect action performancePersonnel issues › Action/decision · PilotCessna 172E: 2 casesAll aircraft: 1,386 casesProbable cause
Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationCessna 172E: 3 casesAll aircraft: 1,285 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Cessna 172E
Category
Airplane
Serial number
17250713
Airframe hours
4,297
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
73
Injuries
None
Certificate
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

Docket · 4

The files NTSB released with the investigation on September 25, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.5 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.