FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95LA164 · Cessna 152

10 Apr 1995 · Marlin, TX, United States

North Texas Aero Cessna 152 · Accident: total loss of engine power (non-mechanical) en route

From Aero Valley Airport (52F) to Easterwood Field (CLL)

Report a problem

Event

NTSB case
FTW95LA164
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
N67570
Onboard fatalities
Unknown
Route
From Aero Valley Airport (52F), Roanoke, TXTo Easterwood Field (CLL), College Station, TX
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
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

  • Pilot in command › Refueling, not performed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE ENGINE LOST POWER AND A FORCED LANDING WAS PERFORMED IN DARK NIGHT CONDITIONS TO A SOFT MUDDY FIELD. THE PILOT HAD DEPARTED ON A NIGHT CROSS COUNTRY FROM ROANOKE, TX TO COLLEGE STATION, TX AND HE ENCOUNTERED 'STRONG WINDS' EN ROUTE. THE PILOT FURTHER REPORTED THAT HE 'STRAYED OFF COURSE SEVERAL TIMES.' THE AIRPLANE WAS FOUND TO HAVE FLOWN FOR 3.6 HOURS SINCE TAKEOFF. BOTH WING TANKS WERE DRAINED AND A TOTAL OF ONE GALLON OF FUEL WAS RECOVERED.

Probable cause

FUEL EXHAUSTION ENGINE POWER LOSS DUE TO THE PILOT'S FAILURE TO REFUEL. FACTORS WERE THE LACK OF SUITABLE TERRAIN AVAILABLE FOR THE FORCED LANDING AND THE DARK NIGHT CONDITION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95LA164
Event ID
20001207X03289
Case number
FTW95LA164
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: 47fedf8621fcfeff3a9916cbeb26250ddf21a01a4493aa5f8240d19e1cc3cdc0; retrieved 2026-09-21T22:21:12.277Z.