FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17LA229 · Aviat Aircraft Inc A-1C-180 UNDESIGNAT

4 Jul 2017 · Dillwyn, VA, United States

Aviat Aircraft Inc A-1C-180 UNDESIGNAT · Accident: loss of control in flight on approach

From Farmville Regional Airport (FVX) to Farmville Regional Airport (FVX)

Report a problem

Event

NTSB case
ERA17LA229
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

Aviat Aircraft Inc A-1C-180 UNDESIGNAT

Aircraft type
Aviat A-1
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
N272WY
Operator
Unknown
Onboard fatalities
Unknown
Route
From Farmville Regional Airport (FVX), Farmville, VATo Farmville Regional Airport (FVX), Farmville, VA
Aircraft age
About 1 year (built 2016)
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
Approach · VFR go-around
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 › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot was attempting to land at an unfamiliar grass airstrip. He made two low approaches, and on the third attempt, he elected to land the airplane with full flaps. After touchdown, he realized that he had insufficient runway remaining on which to stop, so he aborted the landing. Shortly after takeoff and after clearing the trees, the airplane abruptly stalled and impacted the ground. The grass airstrip was designed for radio-controlled model airplanes and was only 650 ft long. A large stand of trees formed the boundary of the northeast end of the runway. The pilot reported that he misidentified the grass airstrip and that there were no mechanical malfunctions or anomalies that would have precluded normal operation of the airplane.

Probable cause

The pilot's selection of a grass airstrip that was of insufficient length for landing, and his exceedance of the airplane's critical angle of attack during the go-around, which resulted in an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17LA229
Event ID
20170704X52124
Case number
ERA17LA229
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: d0eab16b76826b9d736e8d4239b92115c780b003c3f9e43f2fc511bc1eadd128; retrieved 2026-09-16T05:29:55.334Z.