# NTSB ERA13CA107: Brewer James M KR2, N216CB, Bear Branch, KY, January 7, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 7, 2013, 17:30 local (22:30 UTC) - Place: Bear Branch, KY - Coordinates: 37.170555, -83.581947 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.1706&lon=-83.5819&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 7, 2013 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 85984 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA13CA107 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/85984/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=85984 - Page: https://openairdocs.org/ntsb/ERA13CA107 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=05621IQ), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) - [Knowledge: knowledge of equipment](https://openairdocs.org/ntsb-findings/02032015): Personnel issues › Experience/knowledge · Pilot (probable cause); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-findings/02032015/cases.md?model=05621IQ), [All aircraft, 69 cases](https://openairdocs.org/ntsb-findings/02032015/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=05621IQ), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=05621IQ), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-events/192/sequence.md?model=05621IQ), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=05621IQ), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=05621IQ), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Brewer James M KR2, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05621IQ), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative The pilot stated that the intended flight duration was about 2.5 hours, and he wanted to land at his destination airport before dark because there are no runway lights at the airport which he believed would be dark at about 1830. The departure was delayed about 15 to 20 minutes, due to a problem at the fuel facility. The flight departed with a full fuel tank, which he thought held 15.0 gallons but actually held 13.0 gallons, and during the climb he kept the engine rpm at a higher setting because of the departure delay. He leaned the fuel to air ratio during climb, and during cruise flight, he leaned the fuel to air ratio using the on-board exhaust gas temperature (EGT) gauge to 1,400 degrees Fahrenheit, then slightly en richened the mixture. He reported that the fuel quantity indicator (sight tube) installed on the instrument panel was working; however, he was not entirely clear at what level the gauge indicated empty. While talking with Indianapolis Air Route Traffic Control Center (Indianapolis ARTCC), about 20 minutes from his destination airport, the engine suddenly quit. He queried the on-board GPS and looked for the nearest airport, which was Hazard, Kentucky, located about 22 miles away. He declared an emergency with Indianapolis ARTCC, and looked around for a place to land, noting there was a four lane road ahead. Also, Indianapolis ARTCC asked him his intentions. He advised the controller that he intended on landing on a road, orbiting the area 2 to 3 times while descending, and about 4,000 feet, he saw traffic was heavier than he hoped for on the four lane road, but saw a side road off the four lane road with no traffic. He maneuvered the airplane for a forced landing on the side road, and side slipped the airplane. Before touchdown when fully committed for landing, he fully deployed the “belly board” or speedbrake. He reported that the flight was high and fast. Before touchdown he straightened the airplane and saw kids walking with their backs to him on the left side of the road. He intentionally maneuvered the airplane to the right to avoid the kids, travelled past them, and while travelling 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 washout ditch causing the left main landing gear to separate. The airplane slid, and the leading edge of a wing was damaged. During recovery of the airplane there was no fuel remaining in the fuel tank. He also stated that the airplane does have wing mounted fuel tanks which are not plumbed into the airplane’s fuel supply system. Additionally, he thought about whether there had been fuel leakage from the fuel strainer or fuel cap but reported he did not see evidence of blue stain from the dye used in 100LL fuel. ## Aircraft - Registration: [N216CB](https://openairdocs.org/deregistered/N216CB-2022-07-02), registration cancelled 2022-07-02, S/N 8475, built 2006 (OpenAirDocs) - Reported make and model: BREWER JAMES M KR2 - Registry model: [Brewer James M KR2](https://openairdocs.org/model/brewer-james-m-kr2) (registry code 05621IQ) (OpenAirDocs) - Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 8475 - Airframe hours: 295 - Engines: Volkswagon 2180 80 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: David L. Styer - Registered owner: Brewer James M - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, June 1, 2012 - Departed: GQQ, Galion, OH - Destination: 1A6, Middlesboro, KY ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review June 15, 2009; seat: left; flight hours: 1,500 total, 60 in this make and model, 1,500 as pilot in command, 30 in the last 90 days, 10 in the last 30 days ## Weather - Conditions: Visual (VMC), Dusk - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 43 °F, dew point 34 °F - Altimeter: 30.31 inHg - Observed at: 1A6 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130107000709A](https://openairdocs.org/incident/20130107000709A), Jan 7, 2013: Brewer James M KR2, Hazard, KY, Substantial damage. Pilot stated to FAA inspectors as well as Kentucky state police he ran out of fuel and landed on road hit guide wire on rollout to avoid pedestrians. Damage to… ## Docket (3 files) The files NTSB released with the investigation on June 3, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=85984. 485 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 384 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40385223&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Reports and Records (item 2, .PDF, 43 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40393475&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Record of NTSB Interview with Pilot-In-Command (item 3, .PDF, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40393476&FileExtension=.PDF&FileName=Record%20of%20NTSB%20Interview%20with%20Pilot-In-Command-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.