GAA19CA367 · Cessna 172 N
Lexington Flying Club Cessna 172 N · Accident: loss of control on ground during landing
From Georgetown-Scott County Regional Airport (27K) to Lebanon Springfield Airport - George Hoerter Field (6I2)
Event
- NTSB case
- GAA19CA367
- 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 N
- 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
- N75903
- Operator
- Lexington Flying Club
- Onboard fatalities
- Unknown
- Route
- From Georgetown-Scott County Regional Airport (27K), Georgetown, KYTo Lebanon Springfield Airport - George Hoerter Field (6I2), Lebanon, KY
- Aircraft age
- About 43 years (built 1976)
- 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
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during the landing roll, the airplane encountered a "big gust of wind," and the airplane veered left. The airplane exited the runway, impacted a ditch, and nosed over.
The airplane sustained substantial damage to the fuselage, vertical stabilizer, and both wings.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The airport's automated weather observation station reported that, about 10 minutes after the accident, the wind was from 190° at 10 knots, gusting to 18 knots. The pilot landed the airplane on runway 11. The calculated crosswind component was about 14 knots.
The manufacturer's Pilot's Operating Handbook stated, "The maximum allowable crosswind velocity is dependent upon pilot capability as well as aircraft limitations. With average pilot technique, direct crosswinds of 15 knots can be handled with safety."
Probable cause
The pilot's failure to maintain directional control during landing in gusting crosswind conditions, which resulted in a runway excursion, impact with a ditch, and subsequent nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA367
- Event ID
- 20190617X80121
- Case number
- GAA19CA367
- 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: cd8f2667edf7d8e7f5e5db44d45c9532620e2fb2828f41125bf5c9683344be7e; retrieved 2026-09-16T09:17:40.943Z.