# Incident 20080123010489I: Piper PA23250, Minneapolis, MN, January 23, 2008

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 23, 2008, 23:00 local time
- Place: Minneapolis, MN
- Airport: Flying Cloud
- Damage: Minor damage
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: Air taxi and commuter (Part 135)
- Operator: CYQA
- Location: 44.8275° N, 93.4586° W: Placed by OpenAirDocs at FLYING CLOUD (FCM), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.8275&lon=-93.4586&mi=10
- Aircraft: N25FT, registered now (https://openairdocs.org/aircraft/N25FT) (OpenAirDocs)
- Registry model: Piper PA-23-250 (registry code 7102308, https://openairdocs.org/model/piper-pa-23-250) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA23250
- Reported engine: LYC IO540C4B5
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,850 total, 940 in this make and model, 233 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20080123010489I

## Narrative

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

(-23) AIRCRAFT N25FT ARRIVED AT THE RAMP OF EXECUTIVE SERVICE AT FLYING CLOUD AIRPORT MN AT APPROX 2255HR DATE 01/23/08. UPON DEPARTURE, APPROX 2310HR DATE 01/23/08, AS THE AIRCRAFT WAS PULLING OUT OF ITS PARKING SPOT #2 ON THE EXECUTIVE RAMP, IT RAN INTO AN UNOCCUPIED HELICOPTER PLATFORM BELONGING TO AIR METHODS INC, AN EMERGENCY HELICOPTER SERVICE. THE PLATFORM WAS ON THE EXECUTIVE RAMP (AN UNCONTROLLED AREA). THE AREA WAS WELL LIT FROM FLOOD LIGHTS MOUNTED ON EXECUTIVE'S HANGAR. THE HELICOPTER PLATFORM HAS REFLECTIVE TAPE ON ITS CORNERS. ITS DIMENSIONS ARE 16'L X 14'W X 19"H. DAMAGE TO THE AIRCRAFT WAS RT PROPELLER AND RT GEAR.

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.
