CHI99LA247 · Ryan NAVION A
Ryan NAVION A · Accident: loss of engine power on approach
From FIO · Paducah, KY to Keokuk Municipal Airport (EOK)
Event
- NTSB case
- CHI99LA247
- 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
Ryan NAVION A
- Aircraft type
- Ryan NAVION
- 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
- N4902K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From FIO · Paducah, KYTo Keokuk Municipal Airport (EOK), IA
- 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 · VFR pattern downwind
- 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 engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated he had topped off the accident airplane's fuel before departure. He said that during the landing approach, he reduced engine power, lowered the landing gear, and extended 1/2 flaps. Subsequently, he applied power and the engine did not respond. A soybean field was selected and a forced landing executed in the field resulting in substantial damage. The investigation revealed engine continuity and no pre-existing engine anomalies were found. Fuel was recovered from the airplane. Fuel was also present on the ground at the scene and the glass gascolator bowl was found broken. The fuel selector was found on the main tank position and was selected to the off position by the first person to arrive at the accident site.
Probable cause
Loss of engine power for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA247
- Event ID
- 20001212X19206
- Case number
- CHI99LA247
- 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: f066ee6bf82ea0d995700702a3406c8512e84d51a2ee15cc873da1e63d470169; retrieved 2026-09-21T20:27:47.527Z.