# Incident 20040620013629I: Piper PA32260, Minneapolis, MN, June 20, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 20, 2004, 13:45 local time
- Place: Minneapolis, MN
- Airport: Crystal Airport
- Damage: Minor damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 45.0625° N, 93.3540° W: Placed by OpenAirDocs at CRYSTAL (MIC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.0625&lon=-93.3540&mi=10
- Aircraft: N44782, registered now (https://openairdocs.org/aircraft/N44782) (OpenAirDocs)
- Registry model: Piper PA-32-260 (registry code 7103206, https://openairdocs.org/model/piper-pa-32-260) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32260
- People aboard: 1
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040620013629I

## Narrative

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

(-23) AIRCRAFT LANDED ON RUNWAY 14L AND VEERED OFF THE RUNWAY INTO THE NORTH SIDE OF THE GRASS STRIKING A RUNWAY LIGHT AND CAUSING MINOR DAMAGE TO THE LEFT WING FLAP.

## Other reports on N44782 (2)

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

- [Accident 20230210001759A](https://openairdocs.org/incident/20230210001759A), Feb 10, 2023: Piper PA-32-260 (N44782), Tok, AK, Substantial damage. During the approach at the Tok, Alaska airport runway 7, the pilot decided to practice a short field landing. After pulling the power back, the airspeed…
- [Incident 20000915029419I](https://openairdocs.org/incident/20000915029419I), Sep 15, 2000: Piper PA32260 (N44782), Minneapolis, MN, Minor damage. (-23)Aircraft struck a deer during landing roll out. Only damage reported was to the left wheel landing gear faring, wheel pant attachment plate, and the left…

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.