# Incident 19991014035259I: Piper PA60602P, Lancaster, PA, October 14, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 14, 1999, 14:51 local time
- Place: Lancaster, PA
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 40.0421° N, 76.3010° W: Placed by OpenAirDocs: center of Lancaster, PA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.0421&lon=-76.3010&mi=10
- Aircraft: N555PX, registered now (https://openairdocs.org/aircraft/N555PX) (OpenAirDocs)
- Registry model: Piper PA-60-602P (registry code 7106015, https://openairdocs.org/model/piper-pa-60-602p) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA60602P
- People aboard: 1
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991014035259I

## Narrative

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

(-23) WEATHER CONDITIONS WERE NOT A FACTOR.  VISIBILITY WAS EXCELLENT.  EVEN THOUGH PASSENGER SERVICE AIRCRAFT RESPONDED TO TCAS ALERTS AND ALTERED FLIGHT PATH TO AVOID CONFLICT WITH N555PX NO APPARENT VIOLATION OF THE FARS OCCURRED.  PILOT OF N555PX COMPLIED WITH ALL APPLICALBE FARS.  COUNSELED PILOT ON BETTER METHODS TO KEEP INFORMED ABOUT OTHER TRAFFIC IN AREA WHEN OPERATING IN VFR CONDITIONS.  ^PRIVACY DATA OMITTED^

## Other reports on N555PX (1)

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

- [Incident 19990316021109I](https://openairdocs.org/incident/19990316021109I), Mar 16, 1999: Piper PA60602P (N555PX), Rapid City, SD, Minor damage. On March 16, 1999, at approx. 3:30PM MDT a Piper model PA-60-602P, N555PX, operated by private pilot bruce charles hanson, encountered a crosswind just after…

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.