FTW03LA109 · Cessna 150G
Cessna 150G · Accident: loss of engine power en route
From Mount Ida-Bearce Airport (7M3) to Hope Municipal Airport (M18)
Event
- NTSB case
- FTW03LA109
- 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 150G
- 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
- N493RA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mount Ida-Bearce Airport (7M3), Mt. Ida, ARTo Hope Municipal Airport (M18), Hope, AR
- 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
- Loss of engine power
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 11,051-hour pilot stated that the 211-nautical mile cross-country flight originated at approximately 1030 that morning. He stated that he departed with a full load of fuel, which should have provided him with a fuel range of 3 hours and 40 minutes. The pilot added that approximately 2 hours and 10 minutes into the flight, he elected to make an intermediate stop at an airport located 162-nautical miles from his point of deptarture. The airport was unattended at the time of his arrival so the pilot did not add any fuel during the intermediate stop. The pilot departed again at 1255 for his final destination. At about 1325, while the airplane was 3 miles north of the landing threshold for his intended destination, the engine began to run tough, followed by a complete "stoppage." The pilot executed a forced landing to a pasture. The reason for the loss of engine power could not be determined.
Probable cause
The loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03LA109
- Event ID
- 20030325X00379
- Case number
- FTW03LA109
- 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, coordinates. 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: 12986f4d7922bb2914f43da12da8333af9ef3184b87ffe5769ae45a58ec3efe9; retrieved 2026-09-22T09:30:34.995Z.