eFlight
Accidents · NTSB ERA09LA441 · Final report

Mooney M20F accident near Suffolk, Virginia, August 3, 2009

On August 3, 2009 at about 9:00 pm local time, a Mooney M20F, registered N3549N, was substantially damaged in an accident during maneuvering near Suffolk, Virginia (Suffolk airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power due to fuel exhaustion as a result of the pilot’s failure to accurately calculate the fuel required for the flight. Contributing to the accident was a malfunction of the fuel quantity indicators.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 3, 2009 · about 9:00 pm local time · cases in 2009
Place
Suffolk, Virginia · Suffolk · cases near this airport · map
Type
Accident
Injuries
1 person was seriously injured; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Mooney M20F · all M20Fs on the register
Registration
N3549N · no longer on the register · serial 680093
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot stated that he departed with ¼ tank of fuel in the right and left fuel tanks. He said that he was flying around for approximately an hour before he began "buzzing" his house. The engine then lost power and he made an emergency forced landing on a road when, during rollout, the airplane collided with a tree. Examination of the fuel system revealed that both fuel tanks were empty and were not breached. Further examination revealed that the airplane was equipped with electronic fuel quantity indicators. Examination of the electronic fuel indicators revealed that both indicators were not functioning correctly. Review of the Dual Fuel Level (FL-2) operating and installation instructions stated: "do not solely rely on the FL-2 to determine the fuel levels in the fuel tanks." Examination of the airframe and engine by a Federal Aviation Administration inspector revealed no evidence of preimpact mechanical failure or malfunction.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Fuel exhaustion during maneuvering defining event
  2. Loss of engine power (total) during maneuvering
  3. Off-field or emergency landing during emergency descent
  4. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management other cases naming the fuel system
  • cause Personnel issues › Task performance › Planning/preparation › Fuel planning › Pilot
  • factor Aircraft › Aircraft systems › Fuel system › Fuel quantity indicator › Malfunction other cases naming the fuel system

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 1,500 hours in all
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming IO-360 SER (piston); 0 hours total
  • Operator: Rg Rentals LTD

The flight

  • Departed from: SFQ Suffolk VA at 8:30 pm
  • Destination: SFQ Suffolk VA
  • Flight plan: none

Weather at the time

  • Light: dawn
  • Wind: from 230° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 91°F (33°C), dew point 70°F (21°C)
  • Altimeter: 29.96 inHg
  • Observation at 9:01 pm from SFQ, 2 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on September 29, 2009. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA09LA441.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.