# Accident 20230812017009A: Piper PA-32-300, Haines City, FL, August 12, 2023

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 12, 2023, 09:12 local time
- Place: Haines City, FL
- Damage: Substantial damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 27.9691° N, 81.4922° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=27.9691&lon=-81.4922&mi=10
- Aircraft: N898CP, registered now (https://openairdocs.org/aircraft/N898CP) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-32-300
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 236 total
- NTSB investigation: [NTSB ERA23LA337](https://openairdocs.org/ntsb/ERA23LA337) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20230812017009A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

WHILE TAKING THE AIRCRAFT ON AN OPERATIONAL CHECK FLIGHT OVER A PRACTICE AREA POST MAINTENANCE, THE PILOT EXPERIENCED A REDUCTION IN ENGINE SPEED TO APPROXIMATELY 1,200 RPM. THERE WAS NO RESPONSE WHEN COMPLETING THE ENGINE OUT CHECKLIST, INCLUDING SWITCHING FUEL TANKS, ACTIVATING THE ELECTRIC FUEL PUMP, AND ADJUSTING THE THROTTLE FORE AND AFT SEVERAL TIMES. THE PILOT MANAGED TO GLIDE THE AIRCRAFT IN AN OPEN AREA AND LANDED IN BRUSH AND SHORT TREES, SEVERING THE RIGHT WING IN THE PROCESS. THE PILOT SUFFERED MINOR INJURIES AND WAS ABLE TO WALK AWAY FROM THE CRASH ABOUT A MILE TO FIND HELP. LOCAL LAW ENFORCEMENT WAS ABLE TO RESPOND TO THE SCENE AND ASSISTED THE PILOT. THE AIRCRAFT WAS LATER RECOVERED BY ^PRIVACY DATA OMITTED^, WHOM REMOVED THE LEFT WING TO FACILITATE TRANSPORTATION, AND MOVED IT TO THE FT. PIERCE STORAGE FACILITY WHERE AN INSPECTION OF THE AIRCRAFT WAS PERFORMED BY THIS OFFICE WITH THE ASSISTANCE OF THE MANUFACTURER. DATA FROM THE RECENTLY INSTALLED GARMIN AVIONICS SYSTEM REVEALED THAT THE AIRCRAFT EXPERIENCED A LOSS OF FUEL FLOW AND FUEL PRESSURE BEFORE THE CRASH. FURTHER TROUBLESHOOTING OF THE FUEL SYSTEM WAS PERFORMED AND FOUND THAT THE REMAINING FUEL IN THE FUEL SELECTOR VALVE AND ELECTRIC FUEL PUMP REVEALED NO ANOMALIES, THE ELECTRIC FUEL PUMP WAS OPERATIONAL, AND THE PLUMBING HAD FREE AIRFLOW FROM THE FUSELAGE INLET TO THE FUEL CONTROL INLET. THE FAULT WAS NARROWED TO THE FUEL CONTROL SERVO WHERE THE AIR INTAKE ELBOW WAS FOUND WITH A 1.5 INCH HOLE IN THE 90 DEGREE BEND, MAKING CONTACT WITH THE FIREWALL WHERE IT WAS APPERANTLY RUBBING FOR SOME TIME. UPON REMOVAL OF THE INTAKE ELBOW, SIGNIFICANT OIL/SLUDGE MATTER WAS FOUND IN THE INTAKE OPENING OF THE FUEL CONTROL UNIT WHERE UNFILTERED AIR WAS BEING INTRODUCED INTO THE SYSTEM. REMOVAL OF THE FUEL CONTROL UNIT REVEALED THAT THE FOREIGN MATTER WAS CONSISTENT THROUGHOUT THE INTERIOR, LIKELY HAVING A NEGATIVE EFFECT ON PERFORMANCE. THE LAST ANNUAL INSPECTION WAS COMPLETED ON MAY 27, 2023 AT 1,561.7 HOBB METER HOURS. THE AIRCRAFT HOBBS TIME AT THE CRASH WAS 1570.4 HRS. HAD THE HOLE IN THE INTAKE ELBOW BEEN IDENTIFIED DURING THE LAST ANNUAL INSPECTION, THE CONDITION OF THE FUEL CONTROL SERVO MIGHT HAVE ALSO BEEN FOUND.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA23LA337](https://openairdocs.org/ntsb/ERA23LA337), Aug 12, 2023: Piper PA32 (N898CP), Haines City, FL, substantial damage. Probable cause: A total loss of engine power due to fuel starvation for reasons that could not be determined.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.