# N9530M: not currently registered

- Registered now: No (not in the FAA registry file). The mark may be reserved or free to assign
- Earlier aircraft: 1
- Last cancelled: March 20, 2013
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=9530M
- Page: https://openairdocs.org/aircraft/N9530M

## Aircraft that carried N9530M

- [Cancelled 2013-03-20](https://openairdocs.org/deregistered/N9530M-2013-03-20): Mooney M20F, S/N 670107. Sale reported, canceled. Owner: [Minneapolis, MN](https://openairdocs.org/faa-place/MN/Minneapolis)

## NTSB investigations on N9530M (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 FTW02LA108](https://openairdocs.org/ntsb/FTW02LA108), Mar 30, 2002: Mooney M20F (N9530M), Grapeland, TX, substantial damage. Probable cause: The loss of engine power due to the #2 connecting rod cap separating from the connecting rod. A contributing factor was the limited forward visibility due to oil on the windscreen.

## FAA accident and incident reports on N9530M (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 20020330006029A](https://openairdocs.org/incident/20020330006029A), Mar 30, 2002: Mooney M20F (N9530M), Palestine, TX, No damage. (.19) On March 30, 2002, at 1524 central standard time, a Mooney M20F single engine airplane, N9530M, was substantially damaged during a forced landing…

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