FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA126 · Classic Aircraft Corp WACO YMF5

26 Dec 2011 · Marathon, FL, United States

Conch Air Classic Aircraft Corp WACO YMF5 · Accident: fuel starvation while maneuvering

From Florida Keys Marathon International Airport (MTH) to Florida Keys Marathon International Airport (MTH)

Report a problem

Event

NTSB case
ERA12LA126
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
Unknown
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

Classic Aircraft Corp WACO YMF5

Aircraft type
Classic WACO YMF5
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
N64JE
Operator
Conch Air
Onboard fatalities
Unknown
Route
From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Florida Keys Marathon International Airport (MTH), Marathon, FL
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
Maneuvering
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
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

  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, at the beginning of the day, each of the main fuel tanks was about 7/8ths full. He completed two aerial sightseeing flights and was making a third flight. The airplane was about 2 nautical miles from the airport, which was located on an island, when, following a left turn climbing maneuver, the engine began to surge. The pilot elected to perform a forced landing in the ocean. Despite the fact that the engine stopped surging and began producing “almost takeoff power” when the airplane was about 500 feet above ground level, the pilot opted to continue with the ditching. Upon impact with the water, the bi-wing airplane nosed over and sustained substantial damage to both left wings. After the airplane was recovered from the water, about 4 gallons of fuel and 16 gallons of sea water were drained from the 36-gallon capacity left fuel tank; there was no fuel in the 36-gallon right fuel tank. Neither fuel tank had been breached. During a postaccident examination of the airframe and engine, no preaccident mechanical malfunctions or failures were found that would have precluded normal engine operation. Given the low fuel quantity, it is likely that, during the left turn climbing maneuver, the fuel tank inlet was unported, and air was introduced into the system, which caused the engine surge. Once the climbing turn was stopped, normal fuel flow began and engine operation resumed.

It was noted that the wires attached to the cork floats of each of the two fuel quantity sight gauges were bent and that this was causing the gauges to register a fuel quantity of 7/8ths, irrespective of the actual fuel quantity. It could not be determined if the wires were bent before the accident or as a result of the impact. If the wires were bent before the accident, then the pilot should have recognized that the indicated fuel quantity was not changing during the first and second flights of the day and should have taken further action to verify the actual fuel quantity aboard the airplane before initiating the accident flight. If the wires were bent as a result of the impact, then the fuel gauges would have been working properly, and the pilot should have noted the low fuel quantity and refueled the airplane before initiating the accident flight.

Probable cause

The pilot did not ensure that there was sufficient fuel aboard the airplane before initiating the flight, which resulted in temporary fuel starvation and an interruption in engine power during maneuvering. Contributing to the accident was the pilot’s decision to continue with the ditching after engine power was restored.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA126
Event ID
20111228X33855
Case number
ERA12LA126
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, coordinates. 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: 23562cf2fed4c5fb34aa46840d36ca14a5537ba476ae60f2024dea622ed33e06; retrieved 2026-09-15T17:01:44.123Z.