FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR19FA093 · Piper PA23 250

8 Mar 2019 · Pahokee, FL, United States

Piper PA23 250 · Accident: loss of control in flight while maneuvering

From Tampa International Airport (TPA) to North Palm Beach County General Aviation Airport (F45)

Report a problem

Event

NTSB case
WPR19FA093
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
5 · 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 PA23 250

Aircraft type
Piper PA23
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
N5894Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tampa International Airport (TPA), Tampa, FLTo North Palm Beach County General Aviation Airport (F45), West Palm Beach, FL
Aircraft age
About 54 years (built 1965)
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
Maneuvering · low-altitude flying
Defining eventThe 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 control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While descending from cruise altitude toward the destination airport, the pilot reported to air traffic control that he needed to divert to a closer airport because the left engine was "misfiring" and that he was going to "shut it down." Radar data indicated that the airplane flew toward the diversion airport and continued to maneuver south past the airport, where radar contact was lost around 700 ft mean sea level. The airplane subsequently impacted a lake about 1/2 mile west of the airport. Data from the airplane's engine monitoring system revealed a drop in left engine exhaust gas temperature (EGT), cylinder head temperature (CHT), and fuel flow values near the end of the flight. These values then increased again for a few minutes before decreasing a second time. The left engine fuel flow value for the last 3 minutes of the data was 0, and the left propeller was found in the feathered position, consistent with the pilot having shut down and secured the engine in flight. Review of the airframe maintenance logbook indicated that several airframe-related fuel system components were replaced during the 4 months before the accident. An entry in the left engine logbook about 4 days before the accident stated that the left engine No. 5 CHT was fluctuating and that a loss of 300 rpm was experienced when testing the right magneto in flight; however, this issue could not be duplicated on the ground, and the airplane was returned to service. Fuel residue was observed on and around the left engine's electric fuel pump. The pump was removed and functionally tested, during which two leaks were found during pressure tests; however, the effect of these leaks on engine operation could not be determined. No other anomalies of the airframe fuel system were observed; however, the system was heavily fragmented and had been submerged in water for several days before recovery. Based on the available information, the reason for the reported loss of engine power and the extent to which the left engine may have been able to continue to produce power could not be determined. Additionally, the reason for the pilot's low-altitude maneuvering in the vicinity of the runway could not be determined; however, it is likely that the pilot failed to maintain airspeed while maneuvering for landing with the left engine inoperative, which resulted in a loss of control and impact with water.

Probable cause

The pilot's failure to maintain control of the airplane while maneuvering for landing with one engine inoperative following a loss of engine power for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR19FA093
Event ID
20190309X93709
Case number
WPR19FA093
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 81cafb5e4d8ce815030c4799b4b739df8e644f35cedb897383b156643198d445; retrieved 2026-09-15T06:55:12.995Z.