GAA19CA069 · Piper PA32R 301
335 Aviation Piper PA32R 301 · Accident: loss of control on ground during landing
From Music City Executive Airport (XNX) to Darke County Airport (VES)
Event
- NTSB case
- GAA19CA069
- 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 PA32R 301
- Aircraft type
- Piper PA32
- 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
- N4137W
- Operator
- 335 Aviation
- Onboard fatalities
- Unknown
- Route
- From Music City Executive Airport (XNX), Gallatin, TNTo Darke County Airport (VES), Versailles, OH
- Aircraft age
- About 19 years (built 1999)
- 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 · flare/touchdown
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the initial approach, the pilot and airplane owner were not able to see the airport environment due to haze, but both of them were able to see the ground. The pilot continued to use the GPS for navigation, and once the airplane was above the airport, they were able to see the runway. The pilot then made a 180º turn to align for a final approach; however, the approach was not stabilized, so the pilot initiated a go-around. After the climbout, he made another 180º turn for final approach to the opposite runway. The airplane touched down on the nose landing gear first and then immediately veered left and exited the runway. The pilot attempted another go-around, but the airplane struck a tree and then an airport perimeter fence. The airplane sustained substantial damage to the left wing. The owner reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot's improper landing flare, which resulted in landing on the landing gear first and a subsequent loss of directional control, a runway excursion, and impact with a tree and a fence during an attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA069
- Event ID
- 20181118X65851
- Case number
- GAA19CA069
- 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. 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: ed176c4771e25ece5a5fc66707b9a784f7347763f6945734f7857fb880d6fb0d; retrieved 2026-09-16T08:26:30.998Z.