CHI87LA216 · Cessna 170B
Cessna 170B · Accident: loss of control in flight on approach
From Lake Barkley State Park Airport (1M9) to Daviess County Airport (DCY)
Event
- NTSB case
- CHI87LA216
- 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
- 0
- 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
Cessna 170B
- Aircraft type
- Cessna 170
- 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
- N473CJ
- Operator
- John Vanwinkle
- Onboard fatalities
- Unknown
- Route
- From Lake Barkley State Park Airport (1M9), Cadiz, KYTo Daviess County Airport (DCY), Washington, IN
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- 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
- Stall/mush
- 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
- Pilot in command › Airspeed, not maintained
- Pilot in command › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS LANDING THE AIRCRAFT, AFTER RETURNING FROM A PERSONAL CROSS-COUNTRY FLIGHT, WHEN HE ENCOUNTERED A CROSSWIND GUST AND 'VEERED STRONGLY TO THE RIGHT.' THE PILOT THEN DECIDED TO ABORT THE LANDING AND PROCEEDED TO ADD FULL POWER FOR A GO-AROUND. ACCORDING TO THE PILOT, THE GUST OF WIND WAS 'PUSHING' THE AIRCRAFT INTO THE TREES AT THE EAST END OF THE FIELD AND IN AN ATTEMPT TO MISS THE TREES HE PULLED BACK ON THE YOKE. THE AIRCRAFT CLEARED THE TREES BUT JUST AS IT PASSED OVER THE TREE LINE, THE AIRCRAFT STALLED TO THE RIGHT. THE PILOT STATED HE APPLIED LEFT RUDDER AND LOWERED THE NOSE BUT THE AIRCRAFT ATTEMPTED TO ROLL INVERTED AND IMPACTED THE GROUND WITH THE LEFT WING FIRST, CART-WHEELING THE AIRCRAFT IN A CORN FIELD.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record CHI87LA216
- Event ID
- 20001213X32041
- Case number
- CHI87LA216
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 265a8fa3244d3aafd108a12ac53027fd91b4d2abc95e076526cb7524fe83f8da; retrieved 2026-09-22T00:44:09.914Z.