# Incident 20130311007269I: Piper PA-32R-301T, Palm Springs, CA, March 11, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 11, 2013, 16:38 local time
- Place: Palm Springs, CA
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 33.8303° N, 116.5453° W: Placed by OpenAirDocs: center of Palm Springs, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.8303&lon=-116.5453&mi=10
- Aircraft: N61JW, registered now (https://openairdocs.org/aircraft/N61JW) (OpenAirDocs)
- Registry model: Piper PA-32R-301T (registry code 7103220, https://openairdocs.org/model/piper-pa-32r-301t) (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-32R-301T
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130311007269I

## Narrative

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

PALM SPRINGS, CA (PSP): N61JW, PA32, VFR POP UP, DECLARED AN EMERGENCY 15 MILES NNW OF PALM SPRINGS AIRPORT DUE TO LOW OIL PRESSURE AND LIMITED VISIBILITY FROM OIL COVERING WINDSHIELD. AIRCRAFT WAS INSTRUCTED TO CONTINUE VFR TO PALM SPRINGS AIRPORT, WAS ISSUED CLEARANCE TO LAND RUNWAY 13L OR 13R, AND LANDED ON TAXIWAY ECHO SAFELY AT 11638PDT. 3/11 2338Z

## Other reports on N61JW (1)

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

- [Incident 20101113053259I](https://openairdocs.org/incident/20101113053259I), Nov 13, 2010: Piper PA-32R-301T (N61JW), Ontario, CA, No damage. Upon making a normal landing, the aircraft nose tire deflated upon landing. Aircraft was towed off runway. No injuries and no aircraft damage.

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.