FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC92LA037 · Convair CV-240

28 Nov 1991 · Akron, OH, United States

Rhoades Aviation Convair CV-240 · Accident: partial loss of engine power (non-mechanical) en route

From an unrecorded airport to BAK · Columbus, OH

Report a problem

Event

NTSB case
NYC92LA037
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

Convair CV-240

Aircraft type
Convair CV-240
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
N450GA
Onboard fatalities
Unknown
Route
From not recordedTo BAK · 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
En route · climb to cruise
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
Partial 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
Wire, static
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

  • Fluid, fuel › Improper
  • Other maintenance personnel › Loading of cargo, improper
  • Pilot in command › Supervision, inattentive

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

SHORTLY AFTER DEPATURE THE AIRPLANE WAS SEEN CLIMBING TO AN ALTITUDE OF ABBOUT 200 FEET AGL. WITNESSES SAW SMOKE COMING FROM ONE OF THE ENGINES AND HERD A 'POPPING NOISE.' THE PILOT EXECUTED A FORCED LAANDING IN A FIELD. THE AIRPLANE STRUCK ELECTRICAL WIRES AND FENCE THEN BURST INTO FLAMES. THE AIRPLANE HAD REFUELED JUST PRIOR TO TAKE OFF, AND THE FUEL RECEIPT SHOWE THAT 300 GALLONS OF JET (A) FUEL WAS PUT INTO THE TANKS. THE NORMAL FUEL USED IN THE AIRPLANE WAS 100 LL.

Probable cause

THE USE OF AN IMPROPER GRADE OF FUEL, WHICH WAS APPROVED BY THE CAPTAIN AND RESULTED IN A LOSS OF ENGINE POWER DUIRNG CLIMBOUT AND AN IN FLIGHT COLLISION WITH TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC92LA037
Event ID
20001212X18519
Case number
NYC92LA037
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: ed5524eab664fa81b7c206f84743398ef82a9700fcd0d6a9cc200e6462ef7b91; retrieved 2026-09-21T23:23:08.246Z.