GAA15CA009 · Beech 76
Beech 76 · Accident: fuel exhaustion en route
From Bolingbrook's Clow International Airport (1C5) to Monroe Municipal Airport (EFT)
Event
- NTSB case
- GAA15CA009
- 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
- 0
- 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 76
- Aircraft type
- Beechcraft 76
- 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
- N6700D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bolingbrook's Clow International Airport (1C5), Bolingbrook, ILTo Monroe Municipal Airport (EFT), Monroe, WI
- Aircraft age
- About 36 years (built 1979)
- 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
The pilot reported that while enroute to his destination, he experienced a loss of power to his left engine about 10 miles from the airport. Shortly after, the right engine experienced a loss of power, and the pilot maneuvered the airplane for an off-airport landing on a paved road. During the descent, the airplane struck power lines along the side of the road, causing substantial damage to the left wing. Upon subsequent investigation by a Federal Aviation Administration air safety inspector, it was determined that the airplane's fuel tanks were empty.
Probable cause
The pilot's improper fuel planning, which resulted in fuel exhaustion, and a loss of engine power enroute.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA009
- Event ID
- 20150317X53153
- Case number
- GAA15CA009
- 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: 6977d0a1b3b2ae170cc7aa779a6305317a59ec8d95a12360aec6fffeba620567; retrieved 2026-09-16T02:09:34.933Z.