ERA14FA075 · Beech A36TC
Beech A36TC · Accident: fuel starvation on approach
From Woodbine Municipal Airport (OBI) to Charlottesville Albemarle Airport (CHO)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA14FA075
- 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
- 1 · 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
Beech A36TC
- Aircraft type
- Beechcraft 36
- 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
- N3705Z
- Operator
- Gregory Voit
- Onboard fatalities
- Unknown
- Route
- From Woodbine Municipal Airport (OBI), Woodbine, NJTo Charlottesville Albemarle Airport (CHO), Charlottesville, VA
- Aircraft age
- About 33 years (built 1980)
- 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
- Approach
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
About 1 hour 30 minutes into the cross-country flight and while on approach to the destination airport, the pilot reported a loss of engine power. The pilot was unable to glide the airplane to the airport, and it subsequently impacted trees and the ground in a residential area about 3 miles from the airport.
The pilot had completely fueled the airplane before departure, and adequate fuel remained onboard at the time of the engine power loss. Examination of the wreckage revealed that the three-position fuel selector handle was positioned in between the left and right tank detents, which would have restricted fuel flow to the engine. A subsequent test run of the engine was performed successfully, and no evidence of mechanical malfunctions or failures was found that would have precluded normal engine operation. The airplane's before landing checklist instructed the pilot to move the fuel selector valve to the fuller fuel tank for landing. It is likely that, while on approach and preparing the airplane to land, the pilot switched fuel tanks and then inadvertently failed to ensure that the fuel selector handle was fully positioned in the detent of the fuel tank he intended to select.
During the impact sequence, the pilot's shoulder harness separated, and his cause of death was attributed to blunt force trauma to the torso. The autopsy also reported a near-complete transection of the thoracic aorta. If the pilot's shoulder harness had remained intact, the risk of traumatic transection of the aorta would have been significantly reduced and, thus, the pilot likely would only have incurred serious, not fatal, injuries.
Examination of the shoulder harness revealed that the belt had separated about 31 inches from where the fastener connected to the lapbelt. The location of the separation corresponded approximately to where the belt would pass through the D-ring behind the pilot's shoulder. The belt separation area exhibited about 0.25-inch fraying on one edge and 1.25-inch fraying on the other edge along a total area of about 7.75 inches. The shoulder harness manufacturer's component maintenance manual states that the acceptable limit for webbing fraying was a 6-inch area. Microscopic examination of the separated fibers revealed that they had separated in overload. The airplane's maintenance manual and a Federal Aviation Administration advisory circular contained information pertaining to the inspection of shoulder harnesses during 100-hour or annual inspections. The accident airplane's most recent annual inspection was completed about 1 month before the accident.
Although the pilot's toxicology report was positive for pain medication, the medication was not detected in his blood; thus, it is likely that the pilot took the medication many hours before the accident flight and was not impaired during the flight.
Probable cause
The pilot’s failure to position the fuel selector handle in a fuel tank detent, which resulted in a total loss of engine power due to fuel starvation. Contributing to the pilot’s fatal injuries was the separation of his shoulder harness due to overload in an area of excessive fraying.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14FA075
- Event ID
- 20131218X32603
- Case number
- ERA14FA075
- 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: c7e2cb03b5a9649041cb744feec7183e3dba3af57e338d7b8743522c94860b49; retrieved 2026-09-14T16:08:59.647Z.