# Incident 20190516004709I: Piper PA-31-310, Milbank, SD, May 16, 2019

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 16, 2019, 08:40 local time
- Place: Milbank, SD
- Airport: Milbank Municipal
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: Air taxi and commuter (Part 135)
- Operator: UQMA
- Location: 45.2305° N, 96.5661° W: Placed by OpenAirDocs at MILBANK MUNI (1D1), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.2305&lon=-96.5661&mi=10
- Aircraft: N9007Y, a cancelled registration (https://openairdocs.org/deregistered/N9007Y-2020-04-24) (OpenAirDocs)
- Registry model: Piper PA-31-310 (registry code 7103102, https://openairdocs.org/model/piper-pa-31-310) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-31-310
- Reported engine: LYCOMING TI0-540 SER
- People aboard: 4
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 14,450 total, 1,870 in this make and model, 85 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20190516004709I

## Narrative

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

ON MAY 15, 2019, THE PILOT LANDED N9007Y A PIPER PA31-310 ON RUNWAY 31 AT THE MILBANK SOUTH DAKOTA MUNICIPAL AIRPORT. THE PILOT FAILED TO EXTEND THE LANDING GEAR RESULTING IN THE GEAR UP INCIDENT. THE FLIGHT WAS CONDUCTED UNDER 14 CFR PART 135 ON-DEMAND OPERATIONS WITH THREE PASSENGERS ON BOARD NONE WERE INJURED IN THE INCIDENT.

## Other reports on N9007Y (1)

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

- [Incident 19850903075269I](https://openairdocs.org/incident/19850903075269I), Sep 3, 1985: Piper PA31 (N9007Y), Minneapolis, MN. Aircraft climbed through terminal control area without a clearance. Insufficient evidence for action.

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.