FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96LA079 · Meyers Aircraft Co. MY-200A

27 Dec 1995 · Madill, OK, United States

Meyers Aircraft Co. MY-200A · Accident: total loss of engine power (non-mechanical) during initial climb

From 1F4 to 1F4

Report a problem

Event

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

Meyers Aircraft Co. MY-200A

Aircraft type
Meyers MY-200
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
N484C
Operator
Unknown
Onboard fatalities
Unknown
Route
From 1F4To 1F4
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
Initial climb
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
Fuel starvation
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

  • Fluid, fuel › Starvation
  • Fuel system, line › Blocked(total)
  • Fuel system, line › Deteriorated

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

NTSB narrative

The pilot reported that he had been practicing touch and go landings for about 30 minutes. During the last takeoff, at about 500-600 feet AGL, the 'engine sputtered and quit.' After the loss of power, the pilot attempted to return to the runway, but landed 'just short' of the threshold in a ditch 'that was not visible from the air.' Inspection of the airplane after the accident by the owner revealed that the rubber fuel supply line from the fuel tanks was 'plugged' with rubber material; thereby, 'restricting the fuel' supply to the engine. The rubber material was physically similar to the rubber material of the fuel supply line. Further inspection of the fuel supply line revealed that it was deteriorated.

Probable cause

the deterioration of the fuel supply line resulting in line blockage, fuel starvation, and subsequent loss of engine power. A factor was the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96LA079
Event ID
20001207X05011
Case number
FTW96LA079
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: f7e8a44377fa7bda0acbd4396430c84ac9e6217aebe2eab29b5388d397a7af81; retrieved 2026-09-22T22:56:02.978Z.