FTW00LA260 · Cessna 152
Royal Air Cessna 152 · Accident: total loss of engine power (non-mechanical) en route
From Altus Quartz Mountain Regional Airport (AXS) to Shreveport Downtown Airport (DTN)
Event
- NTSB case
- FTW00LA260
- 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 152
- Aircraft type
- Cessna 152
- 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
- N6107Q
- Operator
- Royal Air
- Onboard fatalities
- Unknown
- Route
- From Altus Quartz Mountain Regional Airport (AXS), Altus, OKTo Shreveport Downtown Airport (DTN), Shreveport, LA
- 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
- En route · cruise
- 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 · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The 39-hour student pilot was making a non-endorsed night solo cross-country flight. During the return flight, the pilot 'went further south than had planned', became 'lost' and was radar vectored to his destination. Approximately 10 miles north of the destination airport, at 2,000 feet agl, 3 hours and 35 minutes into the flight, the engine started 'sputtering and quit.' Due to darkness, the pilot could not find a suitable landing area, and subsequently, the airplane impacted trees approximately 10 miles northwest of the airport. Examination of the wreckage revealed that the left and right fuel tanks were empty, and the fuel selector valve was in the ON position.
Probable cause
The student pilot's failure to refuel, which resulted in fuel exhaustion. Factors were the dark night light conditions and lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA260
- Event ID
- 20001212X21981
- Case number
- FTW00LA260
- 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: 2e2cb5033f776665fd5382bf4e4c5825e109fcecc11ace99bebf70741852b581; retrieved 2026-09-21T20:04:54.819Z.