NYC02LA182 · Duffy Vans RV-9A
Duffy Vans RV-9A · Accident: total loss of engine power (non-mechanical) en route
From Miami University Airport (OXD) to an unrecorded destination
Event
- NTSB case
- NYC02LA182
- 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
Duffy Vans RV-9A
- Aircraft type
- Duffy VANS RV-9A
- 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
- N945D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami University Airport (OXD), Oxford, OHTo not recorded
- 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
- Pilot in command › Fuel consumption calculations, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During a night flight, the airplane lost total engine power shortly after departure, about 15 miles from the airport. The pilot initially elected to divert to another airport 3 miles away and 2,500 feet below; however, he subsequently decided to land on a road after not being able to see the runway lights. During the landing, the airplane bounced five or six times, struck a sign, veered off the road and nosed over. The pilot had replaced the fuel gauge about 1 week prior to the accident. He had difficulty calibrating the new fuel gauge, and received assistance telephonically from the manufacturer during the calibration. The pilot believed that he had taken off with about 1/2 tank of fuel onboard. An examination of the airplane after the accident revealed that the fuel tanks were empty; however, the fuel gauge indicated 8 gallons. The source of the fuel inaccuracy was undetermined. The airplane had accumulated 11.4 hours of flight time since installation of the fuel gauge. The pilot filled the fuel tanks at 47.0 flight hours, and lost total engine power at 50.9 flight hours. A "must read" notice in the fuel gauge operating manual stated: "Do not solely rely on the FL-2 to determine the fuel level in the fuel tanks."
Probable cause
The pilot's improper fuel calculations, which resulted in fuel exhaustion and a subsequent total loss of engine power. Factors included an inaccurate fuel gauge indication for undetermined reasons, the pilot's reliance on that indication, the night lighting conditions, and a sign alongside the forced landing road.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA182
- Event ID
- 20020909X01557
- Case number
- NYC02LA182
- 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 2002-09-06.
- API snapshot SHA-256: cfba1c367ca85099375f4e4059495e30fe657f6f859ce335820d5a6d412199c0; retrieved 2026-09-21T19:37:28.217Z.