DFW06CA131 · Cessna 150M
Cessna 150M · Accident: total loss of engine power (non-mechanical) en route
From Ardmore Municipal Airport (ADM) to Ardmore Downtown Executive Airport (1F0)
Event
- NTSB case
- DFW06CA131
- 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 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
- N714BL
- Operator
- Harley W. Hollingsworth · private individual
- Onboard fatalities
- Unknown
- Route
- From Ardmore Municipal Airport (ADM), Ardmore, OKTo Ardmore Downtown Executive Airport (1F0), Ardmore, OK
- 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, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 79-hour private pilot was on a 697-nautical mile cross-country flight when he decided to stop for the night at an airport approximately 209 nautical miles from his point of departure. Upon landing at the airport the pilot discovered that all airport services were closed. The pilot then contacted the fixed base operator (FBO) at a nearby airport and elected to fly there and spend the night. While en-route to the airport the aircraft engine lost power and the pilot elected to execute a forced landing to a vacant field. The airplane collided with trees during the forced landing. According to the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) the pilot reported he departed the airport with 3 gallons of fuel on-board and the intended destination was approximately 11 miles away. The FAA inspector, who responded to the accident scene, examined the airplane and found no fuel in the fuel system.
Probable cause
The loss of engine power due to fuel exhaustion as a result of the pilot's inadequate preflight planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA131
- Event ID
- 20060607X00704
- Case number
- DFW06CA131
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-05-21.
- API snapshot SHA-256: 5d1c5193bf06f3d6ae5c746404d1b64fc38ae55b0cb56b703aab59377cbc1219; retrieved 2026-09-22T04:54:08.235Z.