FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA121 · Cessna 150 F

23 Jan 2017 · Denton, TX, United States

Cessna 150 F · Accident: fuel exhaustion en route

From Clark Airport (3T6) to Denton Enterprise Airport (DTO)

Report a problem

Event

NTSB case
GAA17CA121
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

Cessna 150 F

Aircraft type
Cessna 150
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
N3545L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Clark Airport (3T6), Justin, TXTo Denton Enterprise Airport (DTO), Denton, TX
Aircraft age
About 52 years (built 1965)
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
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
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
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 on base to final, the engine "quit." He added that the airplane could not reach the runway, so he conducted a forced landed in a small field 1/2 mile from the airport.

The airplane impacted a tree during landing, which resulted in substantial damage to the airplane's fuselage and wings.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

The Federal Aviation Administration inspector who responded to the accident stated that, when he arrived, he only observed a few drops of fuel remaining in the airplane's undamaged fuel system. He further stated that, before removal of the wings from the airplane for transport, about 1.5 gallons of total fuel was drained from the fuel tanks.

Probable cause

The pilot’s improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA121
Event ID
20170124X42431
Case number
GAA17CA121
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: bf9f32a0fc6792764fd4743fcf3ba16f6d82cf2b02c80d9444f49e62cbab6882; retrieved 2026-09-16T04:58:01.664Z.