ERA10CA313 · Grumman Acft ENG COR-Schweizer G-164B
Kentucky Air Service Grumman Acft ENG COR-Schweizer G-164B · Accident: nose over/nose down during landing
From Mayfield Graves County Airport (M25) to Mayfield Graves County Airport (M25)
Event
- NTSB case
- ERA10CA313
- 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
Grumman Acft ENG COR-Schweizer G-164B
- Aircraft type
- Grumman G-164
- 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
- N6780K
- Operator
- Kentucky Air Service
- Onboard fatalities
- Unknown
- Route
- From Mayfield Graves County Airport (M25), Mayfield, KYTo Mayfield Graves County Airport (M25), Mayfield, 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 137: Agricultural
- 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 · landing roll
- 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
- Nose over/nose down
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was conducting a short-field landing as part of a Federal Aviation Administration Part 137 agricultural certification flight. He reported that as he approached runway 36, his airspeed and altitude were appropriate. Upon initial contact with the runway, the airplane bounced and the pilot corrected the airplane pitch to slightly nose-down and continued the landing sequence. After contacting the runway again, the airplane entered an excessive nose-down attitude, which the pilot tried to correct by pulling aft on the flight controls. The airplane continued to nose over and came to rest inverted, substantially damaging the empennage, forward fuselage, and wings. The pilot did not report any mechanical failures or malfunctions of the airplane. He noted that his total flight experience was approximately 374 hours; of which, about 25 hours were in the same make and model as the accident airplane. The winds reported at an airport 20 miles northwest of the accident location, about the time of the accident, were calm.
Probable cause
The pilot's improper recovery from a bounced landing, resulting in a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA313
- Event ID
- 20100617X92004
- Case number
- ERA10CA313
- 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: 5efe66c9433b636abbc15ffafc636241dab245a4fbbfc1b4d40f1b9e6e946352; retrieved 2026-09-15T14:27:42.903Z.