# Incident 19960522044069I: Piper PA32R300, Chicago/West Ch, IL, May 22, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 22, 1996, 00:41 local time
- Place: Chicago/West Ch, IL
- Airport: Dupage
- Damage: Minor damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: Air taxi and commuter (Part 135)
- Operator: CHRA
- Location: 41.9071° N, 88.2480° W: Placed by OpenAirDocs at DUPAGE (DPA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.9071&lon=-88.2480&mi=10
- Aircraft: N4451X, a cancelled registration (https://openairdocs.org/deregistered/N4451X-2002-09-16) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Reported engine: LYC IO540K1A5
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,350 total
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960522044069I

## Narrative

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

NARRATIVE: THE PILOT REPORTED ALL ELECTRICAL POWER WAS LOST AFTER THE LANDING GEAR WAS RETRACTED DURING DEPARTURE. AIRCRAFT SUSTAINED MINOR DAMAGE DURING LANDING. AN INSPECTION CONDUCTED AFTER THE INCIDENT REVEALED THE STARTER SOLENOID FAILED. THE FAILURE CAUSED A SHORT TO GROUND ON THE BATTERY SIDE. MAINTENANCE RECOMMENDED A CURRENT LIMITER BE INSTALLED ON THE BATTERY FEED TO SOLENOID.

## Other reports on N4451X (1)

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

- [Accident 20020314038489A](https://openairdocs.org/incident/20020314038489A), Mar 14, 2002: Piper PA32R300 (N4451X), Sanford, NC, Destroyed, 1 fatal. (-23) On March 14, 2002, about 1630 eastern standard time, a Piper PA32R-300, N4451X, registered to ram air freight inc., a FAR 135 cargo operator had an…

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.