ATL85LA093 · Beech A36
Metro Flying Club Beech A36 · Accident: total loss of engine power (non-mechanical) en route
From Montgomery Regional (Dannelly Field) Airport (MGM) to Olive Branch Airport (OLV)
Event
- NTSB case
- ATL85LA093
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N6088S
- Operator
- Metro Flying Club
- Onboard fatalities
- Unknown
- Route
- From Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, ALTo Olive Branch Airport (OLV), Olive Branch, MS
- 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 · 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
- 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
- Pilot in command › Emergency procedure, inadequate
- Pilot in command › Fuel boost pump selector position, not selected
- Pilot in command › Lack of familiarity with aircraft
- Pilot in command › Remedial action, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PIC HAD 1/2 HOUR CHECK-OUT IN A-36 BUT OVER 3900 TOTAL FLIGHT HOURS. HIS 14 HOURS IN THIS ACFT WAS CROSS COUNTRY FLYING. HE STATED THAT THE FUEL WAS KEPT EVENLY DIDTRIBUTED BY SWITCHING THE FUEL SELECTOR BETWEEN TANKS DURING THE NEARLY THREE HOUR FLIGHT. THE PIC/CFI COMMENTED THAT WHEN THE ENGINE QUIT IT SOUNDED LIKE FUEL STARVATION. POST CRASH EXAMINATION OF THE UNDAMAGED FUEL SYSTEM AND INSTRUMENT PANEL SHOWED 15 GALLONS OF FUEL IN THE RIGHT TANK, 0 IN THE LEFT, FUEL SELECTOR ON THE RIGHT TANK, & THE AUXILIARY FUEL BOOST PUMP OFF-PILOT'S HANDBOOK CALLS FOR AUXILIARY PUMP 'ON' WITH LOSS OF ENGINE POWER DURING FLIGHT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL85LA093
- Event ID
- 20001214X35631
- Case number
- ATL85LA093
- 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 1985-02-10.
- API snapshot SHA-256: a370646a4ecf9986bead674aef1fc55a25eb2ce16fc667d937b5919aff783b64; retrieved 2026-09-22T01:59:05.957Z.