DEN99LA082 · Rich RV3-A
Rich RV3-A · Accident: total loss of engine power (non-mechanical) on approach
From ODG · Ogden, UT to Skypark Airport (BTF)
Event
- NTSB case
- DEN99LA082
- 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
Rich RV3-A
- Aircraft type
- Rich RV3
- 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
- N4461V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From ODG · Ogden, UTTo Skypark Airport (BTF), UT
- 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
- 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 › Fuel consumption calculations, exceeded
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot recently purchased the airplane, and had accumulated 6 hours of flight experience in the airplane by the time of the accident. The day before the accident, the pilot topped-off the airplane's 24 gallon fuel tank, and flew touch and go landings for 45 minutes. On the day of the accident, he departed Skypark Airport for Brigham City, where he performed two touch and go landings. He then flew to Ogden-Hinckley Municipal Airport where he did a full stop landing. After a 45 minute stop, the pilot continued his flight to Skypark. As he approached the airport, his engine stopped. He said that his fuel gauge 'showed over 1/2,' and an airborne engine restart was unsuccessful. He performed a forced landing, and encountered a ditch during the landing roll. The FAA inspector, that went to the scene and examined the airplane, reported that he found no fuel or the smell of fuel. The total engine run time since the last refueling was not determined.
Probable cause
The pilot's inadequate preflight planning, and the subsequent fuel exhaustion during the flight. Factor was the airplane's inaccurate fuel gauge.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN99LA082
- Event ID
- 20001212X18751
- Case number
- DEN99LA082
- 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: 34978676d202b99e098296d50390e0bf164dd444d5799d8b6aac967b97deedfe; retrieved 2026-09-22T15:10:23.181Z.