NYC01LA113 · Cessna 172
Cessna 172 · Accident: loss of control in flight during landing
From Bowman Field (LOU) to Lincoln Farm Airport (21KY)
Event
- NTSB case
- NYC01LA113
- 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
Cessna 172
- Aircraft type
- Cessna 172
- 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
- N106ME
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bowman Field (LOU), Louisville, KYTo Lincoln Farm Airport (21KY), LINCOLN FARM, KY
- 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
- Landing · flare/touchdown
- 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
- 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 › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Once over the runway, the pilot identified that the windsock was "slightly moving," so he elected to land on runway 03, which was 1,700 feet long and 60 feet wide. With the flaps set to 30 degrees, the pilot slowed the airplane to 65-70 knots in preparation for a soft field landing. Once over the runway, the pilot flared the airplane. While the pilot was waiting for the airplane to settle onto the runway, it "lurched" to the left. The pilot applied right rudder, but the airplane continued to the left. The airplane departed the runway and came to a stop after impacting some small trees. The pilot reported a total of 57.4 hours of flight experience, all of which was in the accident airplane. In addition, it was the pilot's first attempt at making an actual soft field landing. He had practiced soft field landings on hard surface runways, but had never actually landed on a soft surface. Examination of the airplane revealed no pre impact failures or malfunctions.
Probable cause
The pilot's failure to maintain runway alignment during landing. A factor in the accident was the pilot's lack of experience in conducting soft field landings.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01LA113
- Event ID
- 20010509X00917
- Case number
- NYC01LA113
- 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: 043f742aae2a590b3cfa95d502377c0ec6113c900e08379545ce861f3d951562; retrieved 2026-09-21T19:58:19.171Z.