FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA107 · Brewer James M KR2

7 Jan 2013 · Bear Branch, KY, United States

Brewer James M KR2 · Accident: fuel exhaustion en route

From Galion Municipal Airport (GQQ) to Middlesboro-Bell County Airport (1A6)

Report a problem

Event

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

Brewer James M KR2

Aircraft type
Brewer James KR2
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
N216CB
Operator
David L. Styer · private individual
Onboard fatalities
Unknown
Route
From Galion Municipal Airport (GQQ), Galion, OHTo Middlesboro-Bell County Airport (1A6), Middlesboro, KY
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 exhaustion
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
Wire
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 › Task performance

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

NTSB narrative

Before departure, the pilot/owner filled the fuel tank, adding 1 to 2 gallons of fuel. He expected a flight duration of about 2.5 hours and wanted to land at the destination airport before dark. The departure was delayed about 15 to 20 minutes due to a problem at the fuel facility. Because of the departure delay, the pilot kept the engine rpm at a higher setting and leaned the fuel-air mixture during the climb. During cruise flight, he leaned the fuel-to-air mixture using the onboard exhaust gas temperature gauge, then slightly enriched the mixture. He reported that the fuel quantity indicator installed on the instrument panel was working but that he was not entirely clear at what level the gauge indicated empty. While the pilot was in communication with Indianapolis Air Route Traffic Control Center (ARTCC) and about 20 minutes from his destination airport, the engine suddenly quit. He checked the onboard GPS for the nearest airport, which was about 22 miles away. He declared an emergency with Indianapolis ARTCC and looked for a place to land, first noting a four-lane road with some traffic then observing a side road without traffic. He maneuvered the airplane for a forced landing on the side road and sideslipped the airplane. When committed for landing, he fully deployed the speedbrake because the airplane was high and fast. Before touchdown, he straightened the airplane and maneuvered to the right to avoid pedestrians on the left side of the road. While traveling about 20 to 30 mph, the right wingtip collided with a guy wire. The airplane veered to the right and the left main landing gear hit the road and a washout ditch, causing the gear to separate. The airplane slid, and the leading edge of a wing was damaged.

During recovery of the airplane, no remaining fuel was observed in the fuel tank. The pilot considered whether fuel leaked from the fuel strainer or fuel cap but reported that he did not see evidence of a leak. He stated that he believed the airplane’s fuel capacity was 15 gallons, which he used for his preflight planning; however, he noted postaccident that the fuel cap indicated a fuel capacity of 13 gallons. Given that there was less fuel on board than the pilot believed, the higher-than-normal engine rpm setting during the climb, and the lack of fuel postaccident, the evidence is consistent with exhaustion of the airplane’s fuel supply.

Probable cause

The pilot’s improper preflight planning, which resulted in a total loss of engine power due to fuel exhaustion. Contributing to the fuel exhaustion was the pilot’s lack of knowledge about the airplane’s total fuel capacity and fuel quantity instrumentation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA107
Event ID
20130109X40425
Case number
ERA13CA107
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: a4803c7635ec03c359013177e5afe88ef921b7ae4d89c09a236498510a83311d; retrieved 2026-09-15T20:43:14.959Z.