ERA14LA227 · Piper PA-28-181
Dayton Pilots Club Piper PA-28-181 · Accident: fuel exhaustion en route
From Dayton-Wright Brothers Airport (MGY) to Covington Municipal Airport (M04)
Event
- NTSB case
- ERA14LA227
- 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
Piper PA-28-181
- Aircraft type
- Piper PA-28
- 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
- N4506W
- Operator
- Dayton Pilots Club
- Onboard fatalities
- Unknown
- Route
- From Dayton-Wright Brothers Airport (MGY), Springboro, OHTo Covington Municipal Airport (M04), Covington, TN
- Aircraft age
- About 35 years (built 1979)
- 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 · descent
- 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 exhaustion
- 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
- Aircraft › Fluids/miscellaneous hardware
- 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
According to the instrument flight rules flight plan filed by the pilot, the airplane departed on an estimated 3.1-hour-long flight and had sufficient fuel on board for an estimated 4.8-hour-long flight. A direct 20- to 25-knot headwind existed at the airplane's cruise altitude. Based on the tachometer reading, about 4.2 hours into the flight, the pilot announced over the destination airport's common traffic advisory frequency that the airplane was "out of fuel." The airplane subsequently impacted swampy, wooded terrain 3 miles from the airport. The cockpit and cabin areas were destroyed by impact. There was no evidence of fuel in the wreckage or fuel spillage at the accident site. A detailed examination of the wreckage revealed no preimpact mechanical anomaly with the airframe, engine, or fuel system that would have precluded normal operation.
According to the engine manufacturer, at the minimum allowable fuel flow, the engine had a fuel consumption rate of slightly less than 6 gallons per hour (gph) at 45 percent of rated power to slightly less than 15 gph at 100 percent power. Operators of similarly powered airplanes reported that the engine usually consumes 8.8 to 8.9 gph in a cruise configuration, which did not account for fuel used during taxi, takeoff, and climb. A review of flying club logs and aircraft fueling records revealed that the airplane consumed about 10 gph of fuel during the 12 flights in the month before the accident. According to the airplane manufacturer's Pilot's Operating Handbook, the performance charts are unfactored, and the effect of conditions not considered on the charts, including wind aloft on cruise and range performance, must be evaluated by the pilot. The handbook recommends that pilots conduct in-flight fuel flow and quantity checks.
Probable cause
The pilot’s improper preflight and in-flight fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power over unsuitable terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA227
- Event ID
- 20140507X10817
- Case number
- ERA14LA227
- 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: d04c9d3bf0f74082ff26aecf8cf9a982ec7b16d9b0a065b063679954ff4bc3d5; retrieved 2026-09-15T23:35:25.322Z.