# Incident 19910207005889I: Cessna 152, Minneapolis, MN, February 7, 1991

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 7, 1991, 11:02 local time
- Place: Minneapolis, MN
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 44.9800° N, 93.2638° W: Placed by OpenAirDocs: center of Minneapolis, MN, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.9800&lon=-93.2638&mi=10
- Aircraft: N6436P, registered now (https://openairdocs.org/aircraft/N6436P) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 735 total, 200 in this make and model, 60 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19910207005889I

## Narrative

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

ENGINE LOST POWER IN FLIGHT. MADE OFF AIRPORT LANDING. TWO FAILED MAGNETO COILS RESULTED IN IGNITION SYSTEM FAILURE

## Other reports on N6436P (2)

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

- [Accident 20111122027059A](https://openairdocs.org/incident/20111122027059A), Nov 22, 2011: Cessna 152 (N6436P), Princeton, MN, Substantial damage. The aircraft was being operated by a student pilot as an instructional flight on his second solo. This was the third takeoff of the solo event. At about 350…
- [Accident 19890502010799A](https://openairdocs.org/incident/19890502010799A), May 2, 1989: Cessna 152 (N6436P), Buffalo, MN, Substantial damage. Student overcorrected on runway alignment. Aircraft veered off runway.

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.