CEN14LA375 · Grumman Acft ENG COR-Schweizer G 164A
Precision Aerial Grumman Acft ENG COR-Schweizer G 164A · Accident: loss of engine power (total) en route
From Amelia Earhart Airport (K59) to Sabetha Municipal Airport (K83)
Event
- NTSB case
- CEN14LA375
- 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
Grumman Acft ENG COR-Schweizer G 164A
- 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
- N6743Q
- Operator
- Precision Aerial
- Onboard fatalities
- Unknown
- Route
- From Amelia Earhart Airport (K59), Atchison, KSTo Sabetha Municipal Airport (K83), Sabetha, KS
- 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
- En route
- 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 engine power (total)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while the airplane was cruising at 600 feet above ground level, the engine backfired and experienced a partial loss of power. He subsequently made an emergency landing to a road. During the landing, the engine experienced a total loss of power, and the airplane stalled, which resulted in a bounced hard landing. The airplane then slid sideways into a telephone pole, which resulted in damage to the wings and fuselage.
Due to impact damage, an engine test run could not be conducted. The induction air filter was found distorted outward and opposite from the direction of normal airflow, which is indicative of an engine backfire. A postaccident engine examination revealed that the No. 2 cylinder oil control ring was broken. However, it could not be determined when the oil control ring was broken or if the engine backfiring allowed the ring to break. No other anomalies with the engine were noted. The reason for the engine backfire and subsequent loss of power could not be determined.
Probable cause
The backfire of the engine and its loss of power for reasons that could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA375
- Event ID
- 20140718X25106
- Case number
- CEN14LA375
- 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: e260e5cc43bcaa43e828bcad9cd2ca0e9ae9d4d5e28e5a2a401ab05f08698bec; retrieved 2026-09-16T00:55:42.083Z.