GAA16CA232 · Piper PA 12
Piper PA 12 · Accident: loss of control in flight during landing
From Simsbury Airport (4B9) to Simsbury Airport (4B9)
Event
- NTSB case
- GAA16CA232
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA 12
- Aircraft type
- Piper PA-12
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3506M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Simsbury Airport (4B9), Simsbury, CTTo Simsbury Airport (4B9), Simsbury, CT
- Aircraft age
- About 69 years (built 1947)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA232
- Event ID
- 20160516X10337
- Case number
- GAA16CA232
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 8be3931bbe82fbdccc8b6541349e45d6bb3027c2db116f8d59bccae243e07ae8; retrieved 2026-09-16T03:23:21.362Z.