# Incident 20130108000039I: Cessna 172N, Eden Prairie, MN, January 8, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 8, 2013, 10:30 local time
- Place: Eden Prairie, MN
- Airport: Flying Cloud
- Damage: No damage
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- 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: N738JX, registered now (https://openairdocs.org/aircraft/N738JX) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 250 total, 250 in this make and model, 13 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130108000039I

## Narrative

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

THE PILOT  WAS ENROUTE FROM  THE SUPERIOR WI. AIRPORT (SUW) TO THE MANKATO MN.  AIRPORT (MKT).   AT APPROXIMATELY 10 MILES WEST OF THE FLYING CLOUD AIRPORT (FCM) THE PILOT NOTICED SMOKE ON THE RIGHT SIDE OF THE DASH.  THE PILOT TOLD THE CONTROLLER (MSP APPROACH) THAT THERE WAS SMOKE IN THE COCKPIT BUT IT CLEARED UP.  THE CONTROLLER ADVISED THE PILOT THAT THE FLYING CLOUD AIRPORT WAS JUST 10 MILES WEST.  THE CONTROLLER ALSO ASKED IF HE WANTED TO DECLARE AN EMERGENCY.  JUST THEN THE PILOT  SAW MORE SMOKE AND TOLD THE CONTROLLER THAT YES HE DID WANT TO DECLARE AN EMERGENCY, AND LAND AT THE FLYING CLOUD AIRPORT.  THE PILOT LANDED SAFELY WITHOUT ANY FURTHER PROBLEMS.

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.