FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW97LA036 · Cessna 150M

9 Nov 1996 · Tulsa, OK, United States

Cessna 150M · Accident: total loss of engine power (non-mechanical) on approach

From Vinita Municipal Airport (H04) to Tulsa International Airport (TUL)

Report a problem

Event

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

Cessna 150M

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
N8960U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Vinita Municipal Airport (H04), Vinita, OKTo Tulsa International Airport (TUL)
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 · VFR pattern final
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
Substantial

Cause areas

  • Fluid, fuel › Exhaustion
  • Pilot in command › Refueling, not performed

Approximate · Estimated position: the centre of Tulsa, OK, the place the record names. Not the accident site.

NTSB narrative

During the approach to runway 36L at the Tulsa International Airport, and after being cleared to land, the student pilot reported to ATC that the 'aircraft was out of fuel and going to crash.' The airplane struck some trees and came to a stop with one wing against a house and the other wing on top of a fence, approximately one half mile from the approach end of the runway. A total of 7-quarts of fuel were drained from both fuel tanks. The student pilot's flight instructor had only authorized him to fly solo for the purpose of practicing flight maneuvers, and not to fly at night or fly cross-country. The pilot reported that 'he went sightseeing and knew he would have to stop for fuel.' The pilot intended to land at the Grove Municipal Airport; however, he could not locate the airport. The pilot then flew to the Vinita Municipal Airport; however, fuel is not available at this airport. The pilot reported that he 'sticked the fuel' and found that the airplane's fuel tanks had approximately 2 inches of fuel. The pilot decided to fly the 44 nautical miles to the Tulsa International Airport to get fuel.

Probable cause

Fuel exhaustion due the student pilot's failure to refuel. A factor was the lack of suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97LA036
Event ID
20001208X07028
Case number
FTW97LA036
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1996-11-10.
  • API snapshot SHA-256: 08126c96124082bb69d2bbe49ea9acddc0087f19205cf7b2eb1d8acf33963ec2; retrieved 2026-09-22T20:47:37.828Z.