NYC92FA029 · Cessna 340
Cessna 340 · Accident: total loss of engine power (non-mechanical) on approach
From Charleston International Airport (CHS) to John Glenn Columbus International Airport (CMH)
Event
- NTSB case
- NYC92FA029
- 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
- 5 · 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
- Instrument Meteorological Cond
Cessna 340
- Aircraft type
- Cessna 340
- 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
- N7672Q
- Operator
- Robert R. Chenoweth · private individual
- Onboard fatalities
- Unknown
- Route
- From Charleston International Airport (CHS), Charleston, SCTo John Glenn Columbus International Airport (CMH), Columbus, OH
- 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 · IFR final approach
- 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
- Total loss of engine power (non-mechanical)
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Remedial action, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ON FINAL APPROACH THE PILOT REPORTED AN ENGINE FAILURE. HE SAID HE WAS PUTTING THE LANDING GEAR DOWN. THE AIRPLANE CRASHED 3 MILES FROM THE AIRPORT. EXAMINATION OF THE ENGINES REVEALED NO DISCREPANCIES. THE PILOT DID NOT FEATHER THE PROPELLER AFTER THE ENGINE FAILURE. HE HAD NO TRAINING IN THIS AIRPLANE OR ANY OTHER MULTI-ENGINE AIRPLANE IN OVER 5 YEARS. HIS LAST BFR WAS IN A CESSNA 172. IT WAS REPORTED THAT THE PILOT DID NOT MANAGE THE AIRPLANE FUEL SYSTEM IN THE RECOMMENDED MANNER. A WITNESS SAID THE PILOT USED FUEL FROM THE MAIN TANKS UNTIUL THEY WERE NEARLY EMPTY. HE INGORED FORECASTS OF LIGHT ICING CONDITIONS AND DURING HIS FLIGHT HE REPORTED ICE ACCUMULATION.
Probable cause
THE PILOT'S IMPROPER EXECUTION OF AN EMERGENCY PROCEDURE, AFTER AN ENGINE FAILURE, WHICH RESULTED IN THE LOSS OF AIRPLANE CONTROL. FACTORS RELATED TO THE ACCIDENT WERE: THE PILOT'S IMPROPER MANAGEMENT OF THE FUEL SYSTEM; THE PILOT'S LACK OF PROFICIENCY IN EMERGENCY PROCEDURE; AND THE FLIGHT INTO KNOWN ICING CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92FA029
- Event ID
- 20001212X18508
- Case number
- NYC92FA029
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-11-13.
- API snapshot SHA-256: f34ef4f4044acd85bd62f894679bd8b0d0f731b671dd7ba8ecb24cab0b6c36d4; retrieved 2026-09-21T01:28:35.996Z.