# Incident 20000826037959I: Piper PA31P, Philadelphia, PA, August 26, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 26, 2000, 14:15 local time
- Place: Philadelphia, PA
- Airport: Philadelphia International
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.8721° N, 75.2407° W: Placed by OpenAirDocs at PHILADELPHIA INTL (PHL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.8721&lon=-75.2407&mi=10
- Aircraft: N57539, registered now (https://openairdocs.org/aircraft/N57539) (OpenAirDocs)
- Registry model: Piper PA-31P (registry code 7103120, https://openairdocs.org/model/piper-pa-31p) (OpenAirDocs)
- Registry engine: Lycoming TIGO-541SER (registry code 41539, https://openairdocs.org/engine/lycoming-tigo-541ser) (OpenAirDocs)
- Reported make and model: PIPER PA31P
- Pilot flight hours: 2,500 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000826037959I

## Narrative

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

(-23) PILOT ATTEMPTING TO LAND ON RWY 35 AT PHL. PILOT THOUGHT HE WAS TOO CLOSE TO CROSSING TRAFFIC LANDING ON 27R.PILOT EXECUTED MISSED APPROACH-CIRCLED AND LANDED ON RWY 26, PILOT ADVISED HE WAS NERVOUS AND PROBABLY FORGOT TO LOWER THE LANDING GEAR, AIRCRAFT LANDED GEAR-UP, DAMAGE TO PROPELLERS/ENGINES, MINOR DAMAGE ALSO UNDERCARRIAGE. PILOT WAS COUNSELED BY THIS WRITER REFERENCE CHECKLIST USAGE AND GEAR DOWN PROCEDURES. NO FURTHER ACTION NEEDED.

## Other reports on N57539 (1)

Matched to the same aircraft by N-number and date.

- [Incident 19860731057159I](https://openairdocs.org/incident/19860731057159I), Jul 31, 1986: Piper PA31P (N57539), Uvalde, TX, Minor damage. Engine power loss en route. Diverted after engine shutdown. Found a broken oil line resulting in a minor fire.

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.