# Incident 19960405011819I: Piper PA24260, Bakersfield, CA, April 5, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 5, 1996, 11:15 local time
- Place: Bakersfield, CA
- Airport: Bakersfield Municipal Airport
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.3249° N, 118.9960° W: Placed by OpenAirDocs at BAKERSFIELD MUNI (L45), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.3249&lon=-118.9960&mi=10
- Aircraft: N963J, registered now (https://openairdocs.org/aircraft/N963J) (OpenAirDocs)
- Registry model: Piper PA-24 (registry code 7102402, https://openairdocs.org/model/piper-pa-24) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA24260
- Reported engine: LYC O540A1A5
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,000 total, 256 in this make and model, 36 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960405011819I

## Narrative

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

NARRATIVE: N963J, PA-24-260, DEPARTED BAKERSFIELD MUNI (L45), BAKERSFIELD, CA ABOUT 0655 PST, APRIL 05, 1996, ON A VFR FLIGHT TO GEORGETOWN, CA. UPON ARRIVAL AT THE GEORGETOWN AIRPORT THE LANDING GEAR WOULD ONLY PARTIALLY EXTEND AND WOULD NOT RETRACT. THE PILOT AND HIS PASSENGER, ALSO A PILOT, PERFORMED THE EMERGENCY PROCEDURES, ACCORDING TO THE EMERGENCY CHECK LIST, TO EXTEND THE LANDING GEAR WITHOUT SUCCESS. N963J HAD 6.0 HOURS OF FUEL ONBOARD AT DEPARTURE (L45). WITH FOUR(4) HOURS OF FUEL ONBOARD THE PILOT DETERMINED TO RETURN TO L45 TO MAKE AN EMERGENCY LANDING AT HOME. MINOR DAMAGE WAS SUSTAINED TO THE PROPELLER, LANDING GEAR AND BELLY WITH NO INJURIES TO THE PILOT OR PASSENGER. VISUAL FLIGHT CONDITIONS PREVAILED. NO FLIGHT PLAN WAS FILED.

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.