# Incident 19990117023369I: Piper PA32R300, Logansport, IN, January 17, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 17, 1999, 14:20 local time
- Place: Logansport, IN
- Airport: Logansport Municipal Airport
- Damage: Minor damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 40.7481° N, 86.3547° W: Placed by OpenAirDocs: center of Logansport, IN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.7481&lon=-86.3547&mi=10
- Aircraft: N5602V, registered now (https://openairdocs.org/aircraft/N5602V) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- People aboard: 4
- Fatal injuries: 0
- Pilot flight hours: 2,240 total, 586 in this make and model, 25 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990117023369I

## Narrative

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

(-5)AIRCRAFT ENROUTE FROM DALLAS TO INDIANAPOLIS, INDIANA. WHILE THE PILOT ATTEMPTING TO LAND AT INDIANAPOLIS AIRPORT, HE EXPERIENCED A LANDING GEAR PROBLEM. THERE WAS NO INDICATION THAT THE GEAR WAS EXTENDED.  THE PILOT VIEWED IN THE MIRROR AND DID NOT SEE THE GEAR EXTENSION HE ABORTED THE LANDING AT INDIANAPOLIS AND CONTINUED TO LOGANSPORT.  BEFORE LANDING AT LOGANSPORT, THE PILOT APPLIED THE EMERGENCY PROCEDURES BUT DID NOT BLINK.  ON AND OFF.  HE LOOKED IN THE MIRROR IT SHOWED THAT THE MAIN WAS DOWN AND NOSE WAS TRAILING.  THE PILOT ATTEMPTED THE LANDING AND PULLED THE MIXTURE AT LANDING.  JUST AFTER LANDING, THE AIRCRAFT RAN OFF TO THE LEFT OF THE RUNWAY INTO THE SNOW BANK.  DAMAGE TO THE LEFT PROPELLER  AND NOSE GEAR.  THERE WERE FOURN PERSONS ON BOARD INCLUDING THE PILOT.  NO ONE WAS INJURED.

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.