FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04FA064 · Piper PA-30

4 Apr 2004 · Fernandina Bch, FL, United States

Piper PA-30 · Accident: loss of engine power during initial climb

From 55J · Fernandina Bch, FL to Burlington Alamance Regional Airport (KBUY)

Report a problem

Event

NTSB case
MIA04FA064
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
2 · 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-30

Aircraft type
Piper PA-30
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
N14A
Operator
David P. Mack · private individual
Onboard fatalities
Unknown
Route
From 55J · Fernandina Bch, FLTo Burlington Alamance Regional Airport (KBUY), Burlington, NC
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
Initial climb
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
Loss of engine power
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Propeller feathering, not performed

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

NTSB narrative

The airplane was fueled on the day of the accident; the fuel from the fuel truck was contaminant free. No rain was reported at a nearby airport from the time the airplane landed the day before, to the time of departure. After takeoff with the landing gear retracted, the flight climbed to approximately 200 feet, banked left, then quickly to the right. One witness briefly heard a sputtering sound. The airplane was observed to bank to the left, and impacted the ground while in a 25-30 degree left wing low and nose-low attitude. No smoke was noted trailing the airplane in-flight. Both main and auxiliary fuel tanks were ruptured. Examination of the flight controls, and each engine core revealed no evidence of preimpact failure or malfunction. The left propeller was not feathered. Corrosion and a small amount of debris were noted inside the left engine-driven fuel pump. Internal contamination, and corrosion was noted for both servo fuel injectors (fuel servo). Drops of water were noted in the regulator area of the left fuel servo. During troubleshooting for rough running engines in June 2002, a slight amount of water was detected in the fuel tanks; no repairs or work was performed to the airplane's fuel tanks or fuel caps between the troubleshooting date, and March 26, 2004. The pilot noted discrepancies with the fuel injectors on 2 separate flights in October 2003; no corrective action for either entry was taken. During the last annual inspection, a broken screw was removed from a nut plate in the left main fuel cell access hole plate assembly, the left main fuel tank fuel cell cover plate upper gasket was replaced, and both fuel quantity senders were removed, cleaned, and reinstalled with "new hardware." During the accident flight in a six-second period, the EGT readings for each cylinder of the left engine decreased on average approximately 659 degrees Fahrenheit, while the right engine EGT readings remained nearly the same. Testing of a six cylinder engine to determine the EGT drop with reduction to idle and sudden combustion cessation revealed the temperature drops were 86 and 177 degrees, respectively. Postaccident weight and balance calculations revealed the airplane gross weight at the time the engines were started was approximately 3,788 pounds, and the center of gravity (CG) was 89.66 inches; the weight and CG calculations did not include the weight of fuel found in the left tip tank. A limitation for the airplane was that any weight in excess of 3,650 pounds must be carried symmetrically as fuel in the tip tanks.

Probable cause

The failure of the pilot to feather the left propeller and his failure to maintain control of the airplane following a loss of engine power from the left engine resulting in the in-flight collision with terrain. A factor in the accident was the loss of power from the left engine for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04FA064
Event ID
20040413X00455
Case number
MIA04FA064
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: b02945b9110c836fc6c0210a1b565699de8d0c2e9c53e4bbd07c79d477ed9d94; retrieved 2026-09-20T18:30:45.077Z.