# Incident 19820817045639I: Cessna 172P, Albuquerque, NM, August 17, 1982

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 17, 1982, 10:30 local time
- Place: Albuquerque, NM
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 35.0845° N, 106.6511° W: Placed by OpenAirDocs: center of Albuquerque, NM, within about 8 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.0845&lon=-106.6511&mi=10
- Aircraft: N54500, a cancelled registration (https://openairdocs.org/deregistered/N54500-2014-11-18) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: CONT O300A
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 530 total, 200 in this make and model, 100 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19820817045639I

## Narrative

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

PILOT LANDED ON HIGHWAY WHEN ENGINE MADE CLANKING NOISE AND WAS SHUT DOWN. INSPECTION OF ENGINE PENDING.

## Other reports on N54500 (2)

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

- [Accident 20121213028099A](https://openairdocs.org/incident/20121213028099A), Dec 13, 2012: Cessna 172P (N54500), Murfreesboro, TN, Substantial damage. Student pilot was solo, practicing for his private pilot checkride. He was attempting a soft field takeoff, in which he had completed before, he loss control…
- [Incident 20051009027089I](https://openairdocs.org/incident/20051009027089I), Oct 9, 2005: Cessna 172P (N54500), Dallas, TX, Minor damage. (-23) Pilot had a hard 3-point landing and blew the front nosewheel tire. The aircraft then became uncontrollable and veered off the right side of the 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.