# N80355: Cessna 172M, registration cancelled 2018-02-26

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: February 26, 2018
- Status when cancelled: Registration expired, pending cancellation
- Airframe: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418)
- Data sheets: [TCDS 3A12](https://openairdocs.org/tcds/3A12) (OpenAirDocs)
- Serial number: 17266545
- Type of aircraft: Fixed wing single engine
- Certificate issued: May 24, 2012
- Last registry action: May 24, 2012
- Mode S code: AAF027
- Owner when cancelled: [Blue Skies Aircraft LLC](https://openairdocs.org/faa-owner/BLUE%20SKIES%20AIRCRAFT%20LLC)
- Location: [Wilmington, DE](https://openairdocs.org/faa-place/DE/Wilmington)
- Owner type: Corporation
- Owner's area on the map: 39.7376° N, 75.6671° W: Placed by OpenAirDocs at the center of ZIP code 19808, within about 2 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N80355
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=80355
- Page: https://openairdocs.org/deregistered/N80355-2018-02-26

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 ATL03LA044](https://openairdocs.org/ntsb/ATL03LA044), Feb 11, 2003: Cessna 172 (N80355), Hendersonville, NC, substantial damage. Probable cause: The pilot's failure to maintain directional control and clearence from power lines during a go-around, resulting in an in-flight collision with a powerline.

## FAA accident and incident reports (1)

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 20030211008529A](https://openairdocs.org/incident/20030211008529A), Feb 11, 2003: Cessna 172M (N80355), Hendersonville, NC, Substantial damage. (-23) On February 11, 2003 at approximately 15:20 EST, the pilot made an approach to grass runway 14 at johnson field (8NC9) during high and gusty crosswinds.…

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