GAA16CA232

NTSB accident investigation · Piper PA 12 · Simsbury, CT · May 11, 2016

Accident · No injuriesData collectionFinal report
Date
May 11, 2016, 18:30 local (22:30 UTC)
Place
Simsbury, CT
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3506MPiper PA 12
Defining event
Landing: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report July 25, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160511006209A
Case key
93173

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 and the airplane's subsequent impact with a fence during an attempted aborted landing.

Findings · 6

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 · PilotPiper PA-12: 51 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationPiper PA-12: 5 casesAll aircraft: 1,285 casesProbable cause
Aircraft capability: landing distanceAircraft › Aircraft oper/perf/capability · Capability exceededPiper PA-12: 1 caseAll aircraft: 68 casesProbable cause
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Effect on equipmentPiper PA-12: 4 casesAll aircraft: 594 cases
Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Effect on operationPiper PA-12: 4 casesAll aircraft: 594 cases
Object/animal/substance: fence/fence postEnvironmental issues › Physical environment · Contributed to outcomePiper PA-12: 1 caseAll aircraft: 313 cases

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 of the tailwheel equipped airplane reported that his approach to landing was faster than normal. He further reported that after the airplane bounced on touchdown he elected to abort the landing, but reported that it was too late because the airplane was at the end of the runway and impacted a fence, and nosed over. The airplane sustained substantial damage to the empennage. According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. A review of recorded data from the automated weather observation station located about 4 miles to the east, revealed that, about 20 minutes after the accident the wind was 180 degrees true at 11 knots, visibility 10 statute miles, and sky clear. The airplane landed on runway 03. The Federal Aviation Administration has published the Advisory Circular (AC) 91-79A. This AC discusses the effect of a tailwind on landing distance and states in part: The effect of a tailwind on landing distance is significant and is a factor in determining the landing distance required. Given the airplane will land at a particular airspeed, independent of the wind, the principal effect of a tailwind on operational landing distance is the change in the ground speed at which the airplane touches down.

Factual narrative

The pilot of the tailwheel equipped airplane reported that his approach to landing was faster than normal. He further reported that after the airplane bounced on touchdown he elected to abort the landing, but reported that it was too late because the airplane was at the end of the runway and impacted a fence, and nosed over. The airplane sustained substantial damage to the empennage. According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. A review of recorded data from the automated weather observation station located about 4 miles to the east, revealed that, about 20 minutes after the accident the wind was 180 degrees true at 11 knots, visibility 10 statute miles, and sky clear. The airplane landed on runway 03. The Federal Aviation Administration has published the Advisory Circular (AC) 91-79A. This AC discusses the effect of a tailwind on landing distance and states in part: The effect of a tailwind on landing distance is significant and is a factor in determining the landing distance required. Given the airplane will land at a particular airspeed, independent of the wind, the principal effect of a tailwind on operational landing distance is the change in the ground speed at which the airplane touches down.

Aircraft

Registration
N3506M
Reported as
Piper PA 12
Category
Airplane
Serial number
12-2354
Built
1947
Airframe hours
3,987.9
Engine
Lycoming O-320, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 8, 2015
Departed
4B9 · Simsbury, CT
Destination
4B9 · Simsbury, CT
Airport
4B9 · Simsbury, runway 03, 2,205 × 50 ft, asphalt
Equipment
Electronic flight bag or handheld device

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
60
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
March 1, 2016
Seat
Left
Restraint
4-point
Flight hours
519.2 total · 17.6 in this make and model · 371.1 as pilot in command · 24.1 in the last 90 days · 10.3 in the last 30 days · 2.5 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
180° at 11 knots
Visibility
10 statute miles
Temperature
75 °F, dew point 37 °F
Altimeter
30.04 inHg
Observed at
KBDL, 4 nm away

Docket · 2

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