# Incident 20240113000199I: Piper PA-22, Cleveland, TX, January 13, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 13, 2024, 12:00 local time
- Place: Cleveland, TX
- Damage: Minor damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 30.3382° N, 95.0903° W: Placed by OpenAirDocs: center of Cleveland, TX, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=30.3382&lon=-95.0903&mi=10
- Aircraft: N1691A, registered now (https://openairdocs.org/aircraft/N1691A) (OpenAirDocs)
- Registry model: Piper PA-22 (registry code 7102202, https://openairdocs.org/model/piper-pa-22) (OpenAirDocs)
- Registry engine: Lycoming 0-290 series (registry code 41506, https://openairdocs.org/engine/lycoming-0-290-series) (OpenAirDocs)
- Reported make and model: PIPER PA-22
- Reported engine: LYCOMING 0-290 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 780 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240113000199I

## Narrative

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

DURING A DAY, VFR FLIGHT, AIRCRAFT WAS FLYING FROM KPSN TO KGLS. AT ABOUT 12:00PM CENTRAL TIME AND 1500 MSL THE ENGINE STARTED TO "SPUTTER". PILOT TRIED CYCLING CARB HEAT - NO CHANGE, CYCLED THRU LEFT THEN RIGHT MAG - NO CHANGE. PILOT TURNED TOWARDS CLEVELAND AIRPORT, WHICH WAS THE CLOSEST AIRPORT, WHEN THE ENGINE FAILED COMPLETELY. NOT BEING ABLE TO MAKE AN AIRPORT, PILOT MADE EMERGENCY LANDING TO THE HWY. NO AIRFRAME DAMAGE WAS INCURRED DURING LANDING. EXTERNAL INSPECTION OF ENGINE REVEALED THE NUMBER 3 INTAKE VALVE PUSH ROD WAS BENT AND A CRACK WAS EMMINATING FROM THE SPARK PLUG HOLE. INTERNAL INSPECTION THE NUMBER 3 CYLINDER REVEALED THE NUMBER 3 PISTON AND INTAKE VALVE ASSEMBLY COMPLETLY DESTROYED.

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.