# NTSB CHI96LA071: Piper PA-31-350, N111UC, Zionsville, IN, January 4, 1996

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: January 4, 1996, 18:35 local (23:35 UTC)
- Place: Zionsville, IN
- Location: 39.9509° N, 86.2619° W: Placed by OpenAirDocs: center of Zionsville, IN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.9509&lon=-86.2619&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report May 9, 1996
- Report: Approved by Office Director
- NTSB case key (mKey): 10182
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI96LA071
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/10182/pdf
- Page: https://openairdocs.org/ntsb/CHI96LA071

## Probable cause

the pilot's failure to properly align the airplane for a safe landing on the runway.  Related factors were: the pilot's inadequate preflight planning/preparation, snow, the snow-covered runway, and snowbanks on the sides of the runway.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- On ground/water encounter with terrain/water, landing - roll
  - preflight planning/preparation - inadequate, pilot in command (contributing factor)
  - weather condition - snow (contributing factor)
  - airport facilities,runway/landing area condition - snow covered (contributing factor)
  - airport facilities,runway/landing area condition - snowbank (contributing factor)
  - proper alignment - not attained, pilot in command (cause)

## Analysis

The pilot said while on the ILS approach for runway 36 (5,500' x 100'), he had visual contact with the runway two miles out.  The airplane touched down 42 feet left of centerline and 8 feet right of the runway edge where the airplane contacted 30-inch deep snowdrifts.  There was a NOTAM (D) issued for the snow banks on the sides of the runway and a 75-foot width clearing between the snow banks.

## Factual narrative

On January 4, 1996, at 1835 eastern standard time (est), a Piper PA-31-350, N111UC, registered to Executive Aviation Group, was substantially damaged following a loss of control during the landing roll on runway 36 (5,500'x 100'), at the Indianapolis Terry Airport, Indianapolis, Indiana.  The airline transport pilot reported no injuries.  The 14 CFR Part 91 flight was operating in instrument meteorological conditions.  An IFR flight plan had been filed.  The flight originated from Cleveland, Ohio, at 1730 est.

According to the pilot's written statement, while executing the ILS approach to runway 36, he gained visual contact with the runway two miles out. He also stated that during landing, the left main wheel stuck deep snow and the airplane turned to the left exiting the left side of the runway.

Post accident examination of the airplane by the Federal Aviation Administration Principal Maintenance Inspector (PMI), stated that the airplane touched down 42 feet left of centerline and 8 feet right of the runway edge which was covered by approximately 30 inch deep snowdrifts.  The PMI stated that the pilot allowed the airplane to drift left about 500 feet down the runway where the left gear encountered the snowdrifts causing the airplane to turn left and become totally engulfed in the deep snow.  The airport manager/owner stated that a NOTAM (D) was issued for 2 foot snow banks at the sides with 75 feet width cleared for the runway used.  The runway surface was covered with 1 3/4 inches of dry powdery snow.

## Aircraft

- Registration: [N111UC](https://openairdocs.org/aircraft/N111UC), registered now, S/N 31-7952190, built 1979 (OpenAirDocs)
- Reported make and model: Piper PA-31-350
- Registry model: [Piper PA-31-350](https://openairdocs.org/model/piper-pa-31-350) (registry code 7103110) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 31-7952190
- Airframe hours: 3345
- Engines: LYCOMING TIO-540 350 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Executive Aviation Group
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 13, 1995, 75 hours before
- Departed: IGI, CLEVELAND, OH
- Destination: I52, IN
- Flight plan: IFR
- Airport: I52, Indianapolis Terry, runway 36, 5,500 × 100 ft, concrete

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 34; flight engineer, airline transport; airplane ratings: single-engine sea, multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; seat: left; flight hours: 10,000 total, 600 in this make and model, 5,200 as pilot in command, 210 in the last 90 days, 70 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Instrument (IMC), Dusk
- Wind: 100° at 6 knots
- Visibility: 0.25 statute miles
- Lowest ceiling: 700 ft
- Temperature: 21 °F, dew point 19 °F
- Altimeter: 30.00 inHg
- Observed at: IND, 14 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19960104000069A](https://openairdocs.org/incident/19960104000069A), Jan 4, 1996: Piper PA31350, Indianapolis, IN, Substantial damage. On landing, aircraft slid off end of runway. (-23) on Thursday, January 4, 1996, at approximately 1830 EST, a Piper PA-31, N111UC, on an IFR clearance from…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
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.
