FTW98LA042 · Mooney M20C
Mooney M20C · Accident: total loss of engine power (non-mechanical) en route
From Bud Dryden Airport (TX05) to Ozona Municipal Airport (OZA)
Event
- NTSB case
- FTW98LA042
- 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
Mooney M20C
- Aircraft type
- Mooney M20
- 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
- N1360W
- Operator
- Glen Pruet
- Onboard fatalities
- Unknown
- Route
- From Bud Dryden Airport (TX05), McKinney, TXTo Ozona Municipal Airport (OZA)
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a return flight from McKinney to Ozona, TX, the aircraft's engine lost power due to fuel exhaustion. The pilot had flown the aircraft for 2.4 hours on the flight from Ozona to McKinney on the day before the accident. On the day of the accident, the pilot found that there was no fuel available at the departure airport, therefore he had planned a fuel stop at Abilene, TX. During cruise flight and 'after not encountering anticipated quartering head winds,' the pilot calculated that the time of flight direct to Ozona would be 2.5 hours. He then made the decision to 'continue direct to Ozona.' Approximately 20 miles northeast of Ozona, the engine lost power. The pilot initiated a forced landing to a pasture, and during the landing roll, the wings impacted some 'scrubby' trees. The pilot reported to an FAA inspector that he had 'run out of fuel.' The pilot also reported that he had flown the same route of flight before without refueling; however, the airplane's engine had been changed, and he had not anticipated the higher fuel burn rate.
Probable cause
the pilot's improper planning/decision, which led to fuel exhaustion, loss of engine power, and a forced landing. A related factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA042
- Event ID
- 20001208X09173
- Case number
- FTW98LA042
- 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: 0584aa68b00046bfd3b8e99f348b1e643e5cdeb606dd52b3e503e5d9f0559477; retrieved 2026-09-22T18:13:33.616Z.