GAA15CA273 · Piper PA 20
Piper PA 20 · Accident: loss of control on ground during landing
From Marshfield Municipal George Harlow Field (GHG) to Marshfield Municipal George Harlow Field (GHG)
Event
- NTSB case
- GAA15CA273
- 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 20
- Aircraft type
- Piper PA-20
- 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
- N6932K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Marshfield Municipal George Harlow Field (GHG), Marshfield, MATo Marshfield Municipal George Harlow Field (GHG), Marshfield, MA
- Aircraft age
- About 65 years (built 1950)
- 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 · landing roll
- 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 on ground
- 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 on final approach, he realized he was above the normal glide path and performed a forward slip to lose altitude. At the conclusion of the slip, the airplane had a higher than normal approach airspeed. The pilot planned to make a wheel landing and when the airplane touched down, it landed hard, and bounced twice. The pilot then decided to alter his landing to a three point landing after the bounce. At touchdown the airplane "fishtailed" and started to veer left. The pilot was unable to correct the veer with control inputs, the airplane continued off the runway to the left and ground looped. The airplane sustained substantial damage to the right wing, elevator, horizontal stabilizer, and fuselage.
The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's loss of directional control during the landing roll, which resulted in a ground loop and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA273
- Event ID
- 20150924X55029
- Case number
- GAA15CA273
- 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: 055b847f7ff18a89c8a12bab71b04f06479a176e431a79cca7d9d6dd424561ec; retrieved 2026-09-16T02:48:55.554Z.