ERA09LA383 · Rans S5 COYOTE
Rans S5 COYOTE · Accident: fuel starvation en route
From Morristown, TN (no airport) to GYC · Greeneville, TN
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA09LA383
- 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
Rans S5 COYOTE
- Aircraft type
- Rans S5
- 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
- N284AH
- Operator
- Devault David Hodges
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Morristown, TN (no airport)To GYC · Greeneville, TN
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was descending through 2,500 feet mean sea level when the engine lost total power. He attempted an engine restart, but the engine started and lost power again. A forced landing was initiated towards an open field. The flaps were not extended and the airspeed was about 31 mph when the airplane stalled. The right wing dropped down, the nose pitched down, and airplane collided with the ground. Performance data for the airplane revealed it would stall at 31 mph in a clean configuration. Examination of the airframe, flight controls, the engine assembly, and accessories revealed no anomalies. The fuel selector valve, located behind the pilot seat, was found in the on position. The right main fuel tank shutoff valve was found in the on position. The left fuel tank shutoff valve was found in the off position. The left and right shutoff valves were marked correctly, manually operated, and functioned. The pilot stated both fuel valves were in the on position during his preflight inspection. First responders who responded to the accident site stated they only cut the battery cable. No other switches or buttons were disturbed.
Probable cause
The pilot's failure to maintain airspeed during a forced landing. Contributing to the accident was the loss of engine power due to fuel starvation resulting from the pilot's inadequate preflight inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA383
- Event ID
- 20090707X30405
- Case number
- ERA09LA383
- 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. 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: 06d712847abdc1b041fb8bbaf8a6b818d8f227f9124cee70e38193d636351a04; retrieved 2026-09-15T11:43:14.628Z.