Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 3, 2024 · Piper PA24 250 · N12RD

Moore Haven, FL

Overview

Report Status
Probable Cause
Event Type
Accident
Date
October 3, 2024
Injury Outcomes
No injuries (2 uninjured)
Location
Moore Haven, FL
Aircraft
Piper PA24 250 (1958)
Tail Number
N12RD
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA25LA006

The pilot reported that he departed on the first of two legs of a cross-country flight with full main fuel tanks (30 gallons each, 28 gallons useable). The first leg of the 1 hour and 45-minute flight was uneventful, and the engine performed normally during the flight. The airplane was not refueled after the completion of the first leg, so he checked his fuel both visually and with the fuel gauges. During the cruise portion of the return flight, he noted a partial loss of engine power, with rpm dropping to between 1,000 and 1,200. He initiated the checklist procedures for a partial power loss, declared an emergency with air traffic control, and power was briefly restored. The engine rpm again dropped, and since the closest airport was too far away, he executed a forced landing to a sugar cane field about 1 hour and 18 minutes into the return flight. The pilot stated that the airplane should have had about 2 hours of fuel remaining when the engine lost power. Federal Aviation Administration inspectors responded to the accident site and examined the wreckage; they confirmed substantial damage to the airframe. The fuel system was examined at the scene. The auxiliary wingtip fuel tanks and main fuel tanks contained no quantifiable fuel. The main fuel tanks were not ruptured, and there was no evidence of fuel leakage outside the airplane. The fuel strainer was undamaged and was empty of fuel. After recovery of the wreckage, the engine was prepared for a test run. The engine started on the first attempt and was eventually run up to 2,000 rpm before the run was concluded. Impact damage to the propeller prevented a run at a higher rpm. Also, the fuel tanks were filled with water to check for leaks; no leaks were noted. The pilot reported that the main tanks were “topped” with 8.7 gallons of fuel prior to the first leg of the trip. Prior to this servicing, the tanks were reportedly filled 26 days before the accident, and the pilot stated that his son flew the airplane for three touch-and-go landings after this refueling. Automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane was airborne for 1 hour and 2 minutes and taxied a total of 18 minutes on this flight. Estimated fuel burn for a flight of this duration was about 15 gallons. Therefore, it is unlikely that the pilot initiated the cross-country trip with a full fuel load, and it is possible that he perceived his main fuel tanks to be completely full before beginning the first leg when they were not. The pilot’s operating handbook for the airplane stated that, due to several factors, many fuel cells do not hold their full rated capacity.

NTSB Probable Cause

The pilot’s failure to initiate the cross country flight with an adequate fuel supply, resulting in a loss of engine power and forced landing due to fuel exhaustion.

Full Narrative

The pilot reported that he departed on the first of two legs of a cross-country flight with full main fuel tanks (30 gallons each, 28 gallons useable). The first leg of the 1 hour and 45-minute flight was uneventful, and the engine performed normally during the flight. The airplane was not refueled after the completion of the first leg, so he checked his fuel both visually and with the fuel gauges. During the cruise portion of the return flight, he noted a partial loss of engine power, with rpm dropping to between 1,000 and 1,200. He initiated the checklist procedures for a partial power loss, declared an emergency with air traffic control, and power was briefly restored. The engine rpm again dropped, and since the closest airport was too far away, he executed a forced landing to a sugar cane field about 1 hour and 18 minutes into the return flight. The pilot stated that the airplane should have had about 2 hours of fuel remaining when the engine lost power. Federal Aviation Administration inspectors responded to the accident site and examined the wreckage; they confirmed substantial damage to the airframe. The fuel system was examined at the scene. The auxiliary wingtip fuel tanks and main fuel tanks contained no quantifiable fuel. The main fuel tanks were not ruptured, and there was no evidence of fuel leakage outside the airplane. The fuel strainer was undamaged and was empty of fuel. After recovery of the wreckage, the engine was prepared for a test run. The engine started on the first attempt and was eventually run up to 2,000 rpm before the run was concluded. Impact damage to the propeller prevented a run at a higher rpm. Also, the fuel tanks were filled with water to check for leaks; no leaks were noted. The pilot reported that the main tanks were “topped” with 8.7 gallons of fuel prior to the first leg of the trip. Prior to this servicing, the tanks were reportedly filled 26 days before the accident, and the pilot stated that his son flew the airplane for three touch-and-go landings after this refueling. Automatic dependent surveillance-broadcast (ADS-B) data revealed that the airplane was airborne for 1 hour and 2 minutes and taxied a total of 18 minutes on this flight. Estimated fuel burn for a flight of this duration was about 15 gallons. Therefore, it is unlikely that the pilot initiated the cross-country trip with a full fuel load, and it is possible that he perceived his main fuel tanks to be completely full before beginning the first leg when they were not. The pilot’s operating handbook for the airplane stated that, due to several factors, many fuel cells do not hold their full rated capacity.

Flight

Event TypeAccident
Event Time13:09 EDT
Nearest Airport0nm
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA24 250
Tail NumberN12RD
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-540-A1A5 · Reciprocating · 250
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 62 · First Class · None
Crew 2None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point32 C / 32 C
Altimeter29.93 inHg
Observation Time13:15
Weather SourceWFAC

Appendix: Source Data