# N65659: 1982 Cessna 172P, registration cancelled 2013-08-23

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: August 23, 2013
- Status when cancelled: Sale reported, canceled
- Airframe: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436)
- Engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509)
- Data sheets: [TCDS 3A12](https://openairdocs.org/tcds/3A12), [TCDS 1E12](https://openairdocs.org/tcds/1E12) (OpenAirDocs)
- Serial number: 17275805
- Year built: 1982
- Type of aircraft: Fixed wing single engine
- Engine type: Reciprocating
- Airworthiness: Standard, normal, utility
- Airworthiness date: July 9, 1982
- Last registry action: July 12, 2011
- Mode S code: A8A62D
- Location: [Baltimore, MD](https://openairdocs.org/faa-place/MD/Baltimore)
- Owner type: Individual
- Owner's area on the map: 39.3428° N, 76.3911° W: Placed by OpenAirDocs at the center of ZIP code 21220, within about 3 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N65659
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=65659
- Page: https://openairdocs.org/deregistered/N65659-2013-08-23

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 172P: https://openairdocs.org/model/cessna-172p.md

## NTSB investigations (2)

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 ERA11CA385](https://openairdocs.org/ntsb/ERA11CA385), Jul 6, 2011: Cessna 172P (N65659), Baltimore, MD, substantial damage. Probable cause: The student pilot's failure to maintain aircraft control following a bounced landing.
- [NTSB NYC06CA221](https://openairdocs.org/ntsb/NYC06CA221), Sep 4, 2006: Cessna 172P (N65659), Baltimore, MD, substantial damage. Probable cause: The pilot's improper flare, which resulted in a hard landing.

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

- [Accident 20110706015459A](https://openairdocs.org/incident/20110706015459A), Jul 6, 2011: Cessna 172P (N65659), Middle River, MD, Destroyed. Student pilot was on second solo and was practicing touch and go landings. On the fourth touch and go the student landed hard and went off the left side of…
- [Accident 20060910022679A](https://openairdocs.org/incident/20060910022679A), Sep 10, 2006: Cessna 172P (N65659), Baltimore, MD, Substantial damage. (-23) Student pilot had a hard landing.

## Other aircraft with N65659

- [Cancelled 1974-01-22](https://openairdocs.org/deregistered/N65659-1974-01-22): Lake LA-4-200, S/N 591. Exported to New Zealand. Owner: [Lake 4 Sales Corp](https://openairdocs.org/faa-owner/LAKE%204%20SALES%20CORP), [Conroe, TX](https://openairdocs.org/faa-place/TX/Conroe)

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