FTW96LA158 · Stafford RV-4
Stafford RV-4 · Accident: loss of engine power on approach
From Greeley–Weld County Airport (GXY) to 2V2
Event
- NTSB case
- FTW96LA158
- 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
Stafford RV-4
- Aircraft type
- Stafford RV-4
- 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
- N84PS
- Operator
- William J. Mansfield · private individual
- Onboard fatalities
- Unknown
- Route
- From Greeley–Weld County Airport (GXY), Greeley, COTo 2V2
- 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
- Approach · VFR pattern base
- 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
- 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 › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Upon arriving at the destination airport from a local cross country flight, the pilot performed three touch and go landings. While on the crosswind leg of the fourth pattern circuit, which was to culminate in a full stop landing, the engine lost power and the pilot made an emergency landing in a plowed field. During the landing roll, one main landing gear collapsed and the airplane nosed over. The flight originated with 11 gallons of fuel on board, and the duration of the flight was 54 minutes. According to the pertinent Lycoming engine chart, the fuel consumption at 75 percent power (2,450 rpm) is 10.5 gallons per hour. A review of the pilot's aero/medical data revealed him to be non-current in flight proficiency and medical certification.
Probable cause
the pilot's inadequate preflight planning and preparation in that he failed to ensure the aircraft had sufficient fuel to complete the flight. A factor was the soft terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA158
- Event ID
- 20001208X05546
- Case number
- FTW96LA158
- 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: 2ccb75f041e275b41a5d8ee6beb713492c8d32baf12d982dba0c3b752dbfb0b4; retrieved 2026-09-21T21:56:06.771Z.