MIA86FLT02 · McCoy Robert-Michael BREEZY
Southwind Rentals McCoy Robert-Michael BREEZY · Accident: total loss of engine power (non-mechanical) en route
From Eutaw Municipal Airport (3A7) to Clarke County Airport (23M)
Event
- NTSB case
- MIA86FLT02
- 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
McCoy Robert-Michael BREEZY
- Aircraft type
- Mccoy Robert Michael BREEZY
- 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
- N3269X
- Operator
- Southwind Rentals
- Onboard fatalities
- Unknown
- Route
- From Eutaw Municipal Airport (3A7), Eutaw, ALTo Clarke County Airport (23M), Quitman, 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
- Tree(s)
- 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, oil › Leak
- Fluid, oil › Low level
- Object › Tree(s)
- Pilot in command › Judgment, poor
- Pilot in command › Operation with known deficiencies in equipment, performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING FLT TESTING OF THE NEWLY PURCHASED ACFT WHICH WAS CONDUCTED PRIOR TO THE X-COUNTRY FLT HOME, OIL CONSUMPTION/LEAKAGE WAS DETERMINED TO BE ABOUT 3 QTS PER HR. THE PLT STATED THAT HE PLANNED THE FLT HOME IN SHORT HOPS SO AS TO MINIMIZE OIL USAGE & HAD DEPARTED WITH THE OIL SUMP FILLED TO CAPACITY WITH 6 QTS OF OIL. DURING THE FLT HOME, THE ENG QUIT & A FORCED LDG WAS ATTEMPTED INTO A FIELD. THE ACFT STRUCK A TREE & CRASHED TO THE GROUND & BURNED. A CHECK OF THE OIL SUPPLY AFTER THE ACCIDENT REVEALED NO READING ON THE OIL DIPSTICK. THE ENG MFGR RECOMMENDS THAT CORRECTIVE ACTION BE TAKEN WHEN OIL CONSUMPTION EXCEEDS 6/10 QT PER HR.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MIA86FLT02
- Event ID
- 20001213X34827
- Case number
- MIA86FLT02
- 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: 2114f623b1ebb66fa0e045ced1f5d4a03f32fbffc1391da19a4cca635246ba59; retrieved 2026-09-21T16:50:55.285Z.