CEN16LA090 · Bellanca 17-30A
Bellanca 17-30A · Accident: loss of engine power (total) en route
From Aero Country Airport (T31) to Aero Country Airport (T31)
Event
- NTSB case
- CEN16LA090
- 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
Bellanca 17-30A
- Aircraft type
- Bellanca 17
- 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
- N194DW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aero Country Airport (T31), McKinney, TXTo Aero Country Airport (T31), McKinney, TX
- Aircraft age
- About 22 years (built 1994)
- 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
- Loss of engine power (total)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot stated that he did not visually check the fuel level in the tanks before the personal cross-country flight but that he estimated that there was sufficient fuel on board for a 1-hour flight; the flight was expected to take 30 minutes. The pilot stated that, about 15 to 20 minutes into the flight, the engine started to surge, and it then experienced a total loss of power. The pilot's attempts to restart the engine were unsuccessful. He then attempted to circle to the north end of a nearby airport so he could land to the south instead of landing to the north with a light tailwind. While on final approach, the airplane contacted trees and terrain about 300 ft north of the runway end. A postaccident examination of the airplane revealed that the fuel system was intact. No fuel was found in the left wing tank, and 1/2 gallon of fuel was found in the right wing tank.
Probable cause
The pilot’s inadequate preflight fuel planning, which resulted in a total loss of engine power due to fuel exhaustion, and his subsequent decision to circle to the north end of the airport due to a light tailwind condition instead of making a downwind landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA090
- Event ID
- 20160119X73042
- Case number
- CEN16LA090
- 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: 2b3f2415040edb41f3fd73180c00e02779ed3e82aab38d4be4ae392f01fbc1d6; retrieved 2026-09-16T03:06:02.450Z.