GAA16CA514

NTSB accident investigation · Cessna 205 · Ellington, CT · September 26, 2016

Accident · No injuriesData collectionFinal report
Date
September 26, 2016, 09:05 local (13:05 UTC)
Place
Ellington, CT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N8433ZCessna 205
Defining event
Initial climb: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report December 15, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160926019679A
Case key
94095

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 exceedance of the airplane's critical angle-of-attack during the initial climb after an attempted go-around, which resulted in an aerodynamic stall.

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.

Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 210-5(205): 4 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: angle of attackAircraft › Aircraft oper/perf/capability · Capability exceededCessna 210-5(205): 1 caseAll aircraft: 990 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 reported that during the landing roll he realized the airplane was not going stop within the remaining runway distance. He further reported that he aborted the landing and became airborne, but during the initial climb the airplane entered an aerodynamic stall and impacted terrain about 300 feet beyond the runway threshold. The fuselage and both wings sustained substantial damage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Factual narrative

The pilot reported that during the landing roll he realized the airplane was not going stop within the remaining runway distance. He further reported that he aborted the landing and became airborne, but during the initial climb the airplane entered an aerodynamic stall and impacted terrain about 300 feet beyond the runway threshold. The fuselage and both wings sustained substantial damage. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Aircraft

Registration
N8433Z
Reported as
Cessna 205
Category
Airplane
Serial number
205-0433
Built
1963
Airframe hours
3,520.8
Engine
Continental IO-470-S, 260 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · September 7, 2016
Departed
7B2 · Northampton, MA
Destination
7B9 · Ellington, CT
Airport
7B9 · Ellington, runway 19, 1,800 × 50 ft, asphalt
Equipment
Electronic multifunction display, Auto-pilot, Electronic primary flight display, Angle of attack indicator, Stall warning system, Onboard weather

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
52
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
June 4, 2016
Seat
Left
Restraint
3-point
Flight hours
1,428 total · 500 in this make and model · 1,316 as pilot in command · 20 in the last 90 days

Weather

Conditions
Visual (VMC) · Day
Wind
340° at 4 knots
Visibility
10 statute miles
Temperature
48 °F, dew point 41 °F
Altimeter
30.23 inHg
Observed at
KBDL, 10 nm away

Docket · 2

The files NTSB released with the investigation on November 23, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.3 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.