FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA121 · Piper PA-25-235

12 Jun 2003 · Gulf Hammock, FL, United States

Piper PA-25-235 · Accident: total loss of engine power (non-mechanical) en route

From North Perry Airport (KHWO) to Tallahassee International Airport (KTLH)

Report a problem

Event

NTSB case
MIA03LA121
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

Piper PA-25-235

Aircraft type
Piper PA-25
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
N6981Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Perry Airport (KHWO), Hollywood, FLTo Tallahassee International Airport (KTLH), Tallahassee, FL
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 starvation; 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

  • Other maintenance personnel › Fuel tank selector position, information insufficient
  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, encountered

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that the flight departed with 120 gallons of usable fuel on-board, and approximately 1 hour into the flight while flying between 2,000 and 2,500 feel mean sea level with fuel being supplied from the main fuel tank, he turned on the boost pump and the fuel selector for the larger fuel tank (auxiliary fuel tank). The flight continued and approximately 30-45 minutes later with both fuel tank on/off valves "on", the engine experienced a loss of power. He applied carburetor heat but engine power was not restored. He maneuvered the airplane for a forced landing on an east/west oriented dirt road, but recognized that he would be unable to land on the road due to trees. He set up for landing south of and parallel to the dirt road. While descending, the left wing collided with a tree approximately 20 feet above ground level. He did not recall any other part of the accident but remembers waking up and exiting the airplane. Examination of the airplane at the scene by an FAA airworthiness inspector revealed the original fuel tank installed when the airplane was manufactured was empty, and an aluminum fuel tank installed in place of the hopper tank was full. Examination of the cockpit revealed yellow colored placards with black letters by the 2 fuel on/off valves that indicated usable fuel quantity, orientation in terms of position, i.e. "push-on" and "pull-off"; there was no placard that indicated both should not be on at the same time. Check valves which were oriented properly in terms of flow direction were installed at the outlets of both fuel tanks; both check valves were removed for further examination. Examination of the check valves was performed with FAA oversight at a military installation with calibrated equipment. The check valve from the original fuel tank was found to open at less than 1/4 psi, but the check valve from the auxiliary fuel tank was found to open at 3/4 psi. Review of the maintenance records revealed an entry dated May 25, 2003, which indicates the mechanic removed all optional agricultural equipment and installed a 77-gallon aluminum fuel tank and boost pump in place of the hopper tank. The entry references a FAA 337 form, and that all work was performed in accordance with the airplane type certificate data sheet and flight manual, and Advisory Circular 43.132A. The mechanic who signed off the logbook entry for the 77-gallon aluminum tank installation stated the installation into the accident airplane was based on a previous installation of the same system another mechanic had done to an airplane he owned. The previous installation included stainless steel check valves at the outlet of both fuel tanks and the new owner of the airplane wanted them installed as well. The check valves that were installed were purchased from a Yacht company. As part of the installation in the accident airplane, the mechanic stated that he installed a placard by the fuel on/off valves which indicated that both should not be opened at the same time. Following the installation, the engine was operated with fuel being supplied only from the auxiliary fuel tank and the engine driven fuel pump operating. Static testing showed that with fuel in the fuel tank and the fuel line disconnected downstream of the check valve, but only a trickle of fuel was noted. He questioned that with the representative of the company where he purchased the check valves and the response was that was normal. Further testing with pressure applied to the tank revealed fuel flowed from the disconnected line. Additionally, he stated the pilot had asked him if it was acceptable to have both on/off valves "on" at the same time, and he advised the pilot it was not. Both he and the pilot checked the main fuel tank before the accident flight departed and both noted that the fuel level was down 2-3 inches which he estimated was 4-5 gallons less than full. According to the FAA inspector-in-charge, the installation of the 77-gallon fabricated fuel tank (auxiliary tank) was performed without FAA approved data. He also stated that the airplane flight manual (AFM) did not have a supplement indicating how to operate the auxiliary fuel tank system.

Probable cause

The insufficient information provided to the pilot by the mechanic that installed the auxiliary fuel tank for his failure to install a placard to indicate that both fuel on/off valves should not be on at the same time resulting in a total loss of engine power due to fuel starvation. Also, the unsuitable terrain encountered by the pilot during the forced landing. Findings in the investigation was the installation by the mechanic of FAA check valves into the airplane purchased at a yacht company, and modification of the airplane by the mechanic without FAA approval.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA121
Event ID
20030623X00933
Case number
MIA03LA121
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: investigation status, coordinates. 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: 2f5287e4f5aa359765360c528594eec29ce16aad6b7ac8d2837a717b4cc93d64; retrieved 2026-09-21T19:27:16.385Z.