# Incident 19990805024449I: Piper PA32R300, Indiana, PA, August 5, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 5, 1999, 12:15 local time
- Place: Indiana, PA
- Airport: Indiana Co/Jimmy Stewart Fld A
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 40.6311° N, 79.1015° W: Placed by OpenAirDocs at INDIANA COUNTY/JIMMY STEWART FLD (IDI), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.6311&lon=-79.1015&mi=10
- Aircraft: N38388, registered now (https://openairdocs.org/aircraft/N38388) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Reported engine: LYC IO540K1G5D
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 3,902 total, 1,335 in this make and model, 41 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990805024449I

## Narrative

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

(-23) THE AIRCRAFT BATTERY WAS WEAK WHEN THE PILOT ATTEMPTED TO START THE AIRPLANE FOR A FLIGHT TO BUTLER, PA. THE PILOT ELECTED TO "JUMP START" THE AIRCRAFT AND WAS SUCCESSFUL IN DOING SO.  WHEN THE PILOT ROTATED FROM THE RUNWAY AND SELECTED THE LANDING GEAR TO ITS "UP" POSITION, A COMPLETE ELECTRICAL FAILURE WAS ENCOUNTERED AND HE DECIDED TO RETURN TO THE AIRPORT OF DEPARTURE.  THE PILOT ACCOMPLISHED THE BEFORE LANDING CHECK LIST BUT NEGLECTED TO ACCOMPLISH THE EMERGENCY LANDING GEAR EXTENSION CHECK LIST, CAUSING THE AIRCRAFT TO LAND WITH THE GEAR IN A TRANSIENT POSITION.  THE AIRPLANE SUSTAINED MINOR DAMAGE TO ITS UNDERSIDE, THE PROPELLER, AND ENGINE.

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.