FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09LA266 · McGrath Robert F SONEX

25 Apr 2009 · Louisville, OH, United States

McGrath Robert F SONEX · Accident: fuel exhaustion on approach

From Salem Airpark Inc Airport (38D) to 10A7 · Louisville, OH

Report a problem

Event

NTSB case
CEN09LA266
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
1 · 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

McGrath Robert F SONEX

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
N692RM
Onboard fatalities
Unknown
Route
From Salem Airpark Inc Airport (38D), Salem, OHTo 10A7 · Louisville, OH
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
Defining eventThe 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
Fuel exhaustion
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
Tree(s)
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

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot departed his home airstrip with 3 to 4 gallons of fuel on board to fly to a nearby airport for fuel. The winds at the time of departure were calm. The pilot landed at a nearby airport, but did not purchase fuel. He then took off to fly back to his home airstrip. The accident occurred as the pilot was approaching his home airstrip land. According to witnesses, the engine was not producing power when the airplane banked to the right and descended nose first, consistent with an aerodynamic stall into a wooded area just northwest of the runway. Post accident inspection of the airplane revealed that less than 5 ounces of fuel was present in the fuel tank. No fuel was present in the fuel lines or gascolator, nor was there an odor of fuel at the accident site. According to a global positioning system used by the pilot, the flight was approximately 40 minutes long. The airplane consumes about 4 gallons of fuel per hour. Winds reported 10 miles from the accident site were from 240 degrees at 18 knots gusting to 26 knots.

Probable cause

The pilot's failure to assure an adequate fuel level which resulted in fuel exhaustion. Contributing to the accident were the gusty winds and the pilot's loss of aircraft control during the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09LA266
Event ID
20090428X52819
Case number
CEN09LA266
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: b7a8abcce4741524cff9525f78222b840f1ec51159e3e237faaf2d5dd608e06d; retrieved 2026-09-13T20:05:44.869Z.