ATL86FA220 · Bellanca 14-19-3A
Bellanca 14-19-3A · Accident: total loss of engine power (non-mechanical) on approach
From X45 · Chuluota, FL to McGhee Tyson Airport (TYS)
Event
- NTSB case
- ATL86FA220
- 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
Bellanca 14-19-3A
- Aircraft type
- Bellanca 14
- 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
- N1297R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From X45 · Chuluota, FLTo McGhee Tyson Airport (TYS), Knoxville, TN
- 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
- Approach · IFR initial approach
- First occurrenceThe 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Fuel supply, misjudged
- Pilot in command › Fuel supply, reduced
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT CHECKED ON THE ACFT THE DAY PRIOR TO THIS FLT AND STATED THAT HE DID NOT WANT IT REFUELED. ON THE DAY OF THE FLT HE WAS OBSERVED DRAINING FUEL FROM THE ACFT. HE AIR FILED AN IFR FLT PLAN AND STATED THAT HE HAD 3 HRS AND 45 MINS OF FUEL AND HIS EN ROUTE TIME WAS 2 HRS AND 10 MINS. ABOUT 2 HRS AND 11 MINS AFTER TAKEOFF THE ACFT CRASHED 1 MILE FROM AN ARPT LOCATED APRX 80 MILES SHORT OF THE INTENDED REFUELING LOCATION. THE PLT STATED TO A PERSON AT THE ARPT THAT HE WAS CONCERNED ABOUT THE GROSS TAKEOFF WEIGHT. HE DID NOT DECLARE AND EMERGENCY WHEN HE STARTED HAVING ENG PROBLEMS. IT WAS DETERMINED AFTER THE ACCIDENT THAT THE PLT HAD DRAINED APRX 8 GALLONS OF FUEL FROM THE ACFT PRIOR TO TAKEOFF. THE ACFT FLT MANUAL DOES NOT PROVIDE FUEL CONSUMPTION INFORMATION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL86FA220
- Event ID
- 20001213X34378
- Case number
- ATL86FA220
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: f27caa89da1e0f844951bd04c3323621e89deeb6f4607412fe9f806647a73313; retrieved 2026-09-21T16:53:03.104Z.