FTW95LA153 · Mooney M20J
Mooney M20J · Accident: total loss of engine power (mechanical failure) en route
From Las Vegas Municipal Airport (LVS) to Sierra Vista Municipal Airport / Libby Army Air Field (FHU)
Event
- NTSB case
- FTW95LA153
- 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 M20J
- 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
- N4478H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Las Vegas Municipal Airport (LVS), Las Vegas, NMTo Sierra Vista Municipal Airport / Libby Army Air Field (FHU), FORT HUACHUCA, AZ
- 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 (mechanical failure)
- 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 starvation
- 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 › Starvation
- Fuel system, screen › Blocked(partial)
- Fuel system, screen › Foreign material/substance
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE WAS IN CRUISE FLIGHT IN INSTRUMENT METEOROLOGICAL CONDITIONS WHEN THE ENGINE SUDDENLY BEGAN RUNNING ROUGH, THEN LOST ALL POWER. THE PILOT ATTEMPTED TO RESTORE POWER, BUT WAS UNSUCCESSFUL. HE COULD NOT REMEMBER IF HE SWITCHED FUEL TANKS. HE MADE A FORCED LANDING ON A MOUNTAIN ROAD. DURING THE LANDING ROLL, THE LEFT WING STRUCK A PARKED CAR. THE FUEL SELECTOR WAS FOUND POSITIONED ON THE LEFT FUEL TANK. THE LEFT FUEL TANK FINGER SCREEN WAS FOUND TO BE BLOCKED BY GREEN LEAVES. THE ENGINE OPERATED SUCCESSFULLY AT FULL POWER AFTER THE FUEL SCREEN WAS CLEANED AND REINSTALLED.
Probable cause
FUEL STARVATION DUE TO FOREIGN MATERIAL PARTIALLY BLOCKING THE FUEL SCREEN, AND THE PILOT'S FAILURE TO SWITCH FUEL TANKS. A FACTOR WAS THE LACK OF SUITABLE TERRAIN FOR THE FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA153
- Event ID
- 20001207X03281
- Case number
- FTW95LA153
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-04-03.
- API snapshot SHA-256: a7a00411ac8423b4c1ba88e871dde36ecd11dcd862c76fb2172d4d537207bf9e; retrieved 2026-09-23T00:05:36.464Z.