ERA14CA017

NTSB accident investigation · Beech A36 · Burnsville, NC · October 23, 2013

Accident · Serious injuriesData collectionFinal report
Date
October 23, 2013, 10:10 local (14:10 UTC)
Place
Burnsville, NC
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7257WBeech A36
Defining event
Landing-flare/touchdown: Landing area overshoot
Weather
Visual (VMC) · Day
Status
Completed · report February 13, 2014
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
FAA report
20131023024669A
Case key
88277

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 achieve a proper touchdown point during landing, which resulted in a runway excursion.

Findings · 3

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 · PilotBeech A36: 11 casesAll aircraft: 1,386 casesProbable cause
Knowledge: knowledge of geographic areaPersonnel issues › Experience/knowledge · PilotBeech A36: 1 caseAll aircraft: 24 casesProbable cause
Aircraft capability: landing distanceAircraft › Aircraft oper/perf/capability · Capability exceededBeech A36: 1 caseAll aircraft: 68 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

The pilot stated that he was high and fast on the approach to his destination airport. He landed the airplane approximately half way down the runway, and realized that he would not be able to bring the airplane to a full stop. He veered the airplane to left, departed the runway, traveled down an embankment and impacted a road. The airplane sustained substantial damage to both wings and the fuselage. The pilot did not report any mechanical anomalies that would have precluded normal operation prior to the accident.

Factual narrative

The pilot stated that he was high and fast on the approach to his destination airport. He landed the airplane approximately half way down the runway, and realized that he would not be able to bring the airplane to a full stop. He veered the airplane to left, departed the runway, traveled down an embankment and impacted a road. The airplane sustained substantial damage to both wings and the fuselage. The pilot did not report any mechanical anomalies that would have precluded normal operation prior to the accident.

Aircraft

Registration
N7257W
Reported as
Beech A36 (UNDESIGNAT)
Category
Airplane
Serial number
E-2304
Built
1986
Airframe hours
2,400
Engine
Continental Motors IO-550, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
3 Manx Aviation LLC
Registered owner
3 Manx Aviation LLC
Airworthiness certificate
Standard, Normal
Last inspection
Annual · January 25, 2013
Departed
JWN · Nashville, TN
Destination
2NC0 · Burnsville, SC
Airport
2NC0 · Mountain Air Airport, runway 32, 2,900 × 50 ft, asphalt

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
51
Injuries
Serious
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
4,100 total · 120 in this make and model · 4,100 as pilot in command

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 8 knots
Visibility
10 statute miles
Lowest ceiling
5,000 ft broken
Temperature
46 °F, dew point 41 °F
Altimeter
29.82 inHg
Observed at
2NCO

Docket · 8

The files NTSB released with the investigation on February 4, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 10.7 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.