# N5135R: 1974 Cessna 172M, registration cancelled 2012-04-06

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: April 6, 2012
- Exported to: Canada
- Status when cancelled: Registration pending
- Airframe: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418)
- Engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508)
- Data sheets: [TCDS 3A12](https://openairdocs.org/tcds/3A12), [TCDS E-274](https://openairdocs.org/tcds/E-274) (OpenAirDocs)
- Serial number: 17263352
- Year built: 1974
- Type of aircraft: Fixed wing single engine
- Engine type: Reciprocating
- Airworthiness: Standard, normal, utility
- Airworthiness date: May 31, 1974
- Last registry action: February 27, 2012
- Mode S code: A66FAB
- Location: [Rockville, MD](https://openairdocs.org/faa-place/MD/Rockville)
- Owner type: Individual
- Owner's area on the map: 39.0518° N, 77.1244° W: Placed by OpenAirDocs at the center of ZIP code 20852, within about 2 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N5135R
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=5135R
- Page: https://openairdocs.org/deregistered/N5135R-2012-04-06

From the FAA registry file of October 29, 2026, cancelled registrations. Owners' street addresses are left out. The Mode S code belongs to the N-number, not the airframe.

ADs and bulletins for the Cessna 172M: https://openairdocs.org/model/cessna-172m.md

## NTSB investigations (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB IAD98LA020](https://openairdocs.org/ntsb/IAD98LA020), Jan 4, 1998: Cessna 172M (N5135R), Blue Bell, PA, substantial damage. Probable cause: The pilot's failure to attain the proper touchdown point, and his failure to make a go-around, while there was sufficient runway remaining.

## FAA accident and incident reports (2)

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.

- [Incident 20000531032549I](https://openairdocs.org/incident/20000531032549I), May 31, 2000: Cessna 172M (N5135R), Gaithersburg, MD, Minor damage. (-23)On go around the right flap fully retracted and the left flap stopped at approx. 30 degrees and the system failed in that position. Investigation revealed…
- [Accident 19980104000059A](https://openairdocs.org/incident/19980104000059A), Jan 4, 1998: Cessna 172M (N5135R), Philadelphia, PA, Substantial damage. Overran runway landing. Prop and nose gear damaged on street curb firewall also damaged. (.4)the pilot reported that the airplane touched down long, and…

---
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.