NTSB CAROL · Event
Event MIA03LA154
Aircraft involved
Probable cause & findings
The pilot's failure to adequately plan for the flight which resulted in fuel exhaustion, a forced landing, and damage to the airplane during the landing.
Factual narrative
On August 2, 2003, about 1301 eastern daylight time, a Piper PA-31-310, registered to and operated by a private owner as a Title 14 CFR Part 91 personal flight crashed into an orange grove in Jupiter, Florida. Visual meteorological conditions prevailed, and an instrument flight rules flight plan had initially been filed. The private-rated pilot and one passenger received minor injuries, and the airplane incurred substantial damage. The flight originated in Canton, Ohio, the same day, about 0830. The pilot stated that he and his wife departed from the Canton Regional Airport, Canton, Ohio, shortly after 0800, en route to Fort Lauderdale Florida, to attend a conference aboard a cruise ship, scheduled to leave port Everglades, Florida, at 1700. He further stated that when he departed, both fuel tanks were full of fuel, and the fuel selectors were set to the inboard tanks. During the en route phase, he said he leaned the fuel mixture to establish a burn rate of 15.5 gallons per hour for each engine, and maintained this setting throughout the remainder of the flight, until the initial descent. After 1 1/2 hours the fuel gauges pertaining to the inboard tanks showed half a tank of fuel for both tanks. At this point, the pilot said he switched to the outboard tanks which were full of fuel. He said the outboard tanks were then used for the following 2 hours, until the fuel gauges showed that the tanks were 1/4 full. He further said that he believed enough fuel remained in the inboard tanks to reach his destination, and still have the required reserve for VFR operations. While descending to 2,500 feet, the pilot said he was vectored around thunderstorms, and when approximately 12 miles north of Palm Beach International Airport (PBI) the left engine began to surge. At that point, he noticed that both of the inboard fuel gauges showed that the tanks were empty, so he selected the outboard tanks, which had both their indicators showing 1/4 full. The pilot said that 2 minutes later both engines began to surge again, and he then made an emergency radio communications call requesting vectors to the nearest airport. He was advised of the Tailwinds Airport, Jupiter, Florida, which was located 4 miles to the west of his location, but he was unable to reach it, so he made a forced landing in an orange grove. The pilot also said that prior to the accident there had not been any mechanical failure or malfunction to the airplane or any of its systems. An FAA inspector who responded to the accident scene, stated that he observed no evidence of fuel at the scene. Follow-on examination of the airplane revealed no anomalies with the airplane, its fuel system, or its engines. The pilot stated that he and his wife were en route to a medical conference which was to be held aboard a cruise ship that was departing from Fort Lauderdale, Florida, at 1700. He stated that both tanks were full of fuel when he departed the Canton Regional Airport, Canton, Ohio, en route to Fort Lauderdale Executive Airport. According to the pilot, the inboard tanks had been selected for the first hour and a half and the outboard tanks for the following two hours. He said the flight was vectored around thunderstorms, and during the descent, when about 12 miles to the north of Palm Beach International Airport, Palm Beach, Florida, the left engine ceased operating. He said that at this time he noticed that both inboard fuel indicators showed the tanks to be empty, and he switched to the outboard tanks, both of which were shown to be a quarter full. The pilot stated that two minutes later both engines began to surge, and after making an emergency radio communications call, he was advised by the FAA Air Traffic Controller that Tailwinds Airport was located 4 miles to the west. Unable to reach the runway at Tailwinds Airport, the pilot said he made a forced landing in an orange grove. the pilot also said that prior to the accident, there had not been any mechanical failure or malfunctions to the airplane or any of its systems. Examination of the accident site revealed that the airplane had incurred substantial damage, and there was little or no fuel present at the scene. Follow-on examination of the airplane, its fuel system and both engines revealed no anomalies. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_MIA03LA154.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel exhaustion, thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
- NASA NTRS 2019 · Technical Memorandum (TM)
Thunderstorm hazards flight research: Storm hazards 1980 overview
A highly instrumented NASA F-106B aircraft, modified for the storm hazards mission and protected against direct lightning strikes, was used in conjunction with various ground based radar and lightning…
- NASA NTRS 2019 · Conference Proceedings
Operational evaluation of thunderstorm penetration test flights during project Storm Hazards '80
The National Aeronautics and Space Administration is conducting a research project called Storm Hazards '80 in order to study the prediction, detectability and avoidance of the hazards of severe storm…
- NASA NTRS 2019 · Preprint (Draft being sent to journal)
Nowcasting Thunderstorm Anvil Clouds Over KSC/CCAFS
Electrified thunderstorm anvil clouds extend the threat of natural and triggered lightning to space launch and landing operations far beyond the immediate vicinity of thunderstorm cells.
- NASA NTRS 2019 · Contractor Report (CR)
An Examination of Aviation Accidents Associated with Turbulence, Wind Shear and Thunderstorm
The focal point of the study reported here was the definition and examination of turbulence, wind shear and thunderstorm in relation to aviation accidents.
- NASA NTRS 2019 · Reprint (Version printed in journal)
Observations of severe turbulence near thunderstorm tops
Data derived from the flight tapes of two airliners that experienced severe turbulence near thunderstorm tops are used to produce quantitative descriptions of the turbulence and its environment.
Browse the full corpus — academia portal ↗