FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA259 · Moody-Siple A

21 Apr 2012 · Stuttgart, AR, United States

Moody-Siple A · Accident: fuel exhaustion while maneuvering

From Batesville Regional Airport (KBVX) to Searcy Municipal Airport (KSRC)

Report a problem

Event

NTSB case
CEN12LA259
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

Moody-Siple A

Aircraft type
Moody Siple A
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
N78RB
Operator
Broadbent e Ray II · private individual
Onboard fatalities
Unknown
Route
From Batesville Regional Airport (KBVX), Batesville, ARTo Searcy Municipal Airport (KSRC), Searcy, AR
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 exhaustion
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot said that he had been flying for 2 hours, practicing maneuvers in preparation for an upcoming biennial flight review, when the engine lost power due to fuel exhaustion. Examination of the airplane revealed about 300 feet of power line was wrapped around and trailing behind the right main landing gear. The pilot did not recall impacting anything during the flight. No preimpact mechanical malfunctions or failures were found that would have precluded normal operation. The trailing power line could have affected the airplane’s performance, increasing both fuel consumption and drag; however, the timing of the wire strike and actual effect could not be determined.

Probable cause

The pilot’s inadequate fuel monitoring, which resulted in a total loss of engine power due to fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA259
Event ID
20120427X21826
Case number
CEN12LA259
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: 572138e3b8386aef048c032b661ecb5b7bf010955bac9f06a8491e7865eec281; retrieved 2026-09-15T17:53:30.668Z.