# N8139A: 1979 Piper PA-32R-301, registration cancelled 2002-03-18

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: March 18, 2002
- Status when cancelled: Triennial form not returned
- Airframe: [Piper PA-32R-301](https://openairdocs.org/model/piper-pa-32r-301) (registry code 7103218)
- Engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530)
- Data sheets: [TCDS A3SO](https://openairdocs.org/tcds/A3SO), [TCDS 1E4](https://openairdocs.org/tcds/1E4) (OpenAirDocs)
- Serial number: 32R-8013040
- Year built: 1979
- Type of aircraft: Fixed wing single engine
- Engine type: Reciprocating
- Airworthiness: Standard, normal
- Airworthiness date: January 11, 1980
- Certificate issued: January 15, 1999
- Last registry action: January 15, 2002
- Mode S code: AB1815
- Owner when cancelled: [Aero Leasing](https://openairdocs.org/faa-owner/AERO%20LEASING)
- Location: [Dayton, NV](https://openairdocs.org/faa-place/NV/Dayton)
- Owner type: Corporation
- Owner's area on the map: 39.2270° N, 119.4749° W: Placed by OpenAirDocs at the center of ZIP code 89403, within about 7 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N8139A
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=8139A
- Page: https://openairdocs.org/deregistered/N8139A-2002-03-18

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 Piper PA-32R-301: https://openairdocs.org/model/piper-pa-32r-301.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 LAX01LA030](https://openairdocs.org/ntsb/LAX01LA030), Nov 1, 2000: Piper PA-32R-301 (N8139A), Dayton Valley, NV, substantial damage. Probable cause: The pilot's failure to attain a proper glide path during the final approach resulting in an undershoot of the runway. Factors were the lack of runway lights and night lighting condition.

## 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 20001031017239A](https://openairdocs.org/incident/20001031017239A), Oct 31, 2000: Piper PA32R301 (N8139A), Dayton, NV, Substantial damage. (-23) During a second approach to land at the unlighted airport at Dayton, Nevada, the pilot misjudged the location of the runway and lost visual reference. He…
- [Incident 19880205009089I](https://openairdocs.org/incident/19880205009089I), Feb 5, 1988: Piper PA32R301 (N8139A), Fresno, CA. On landing rollout the gear lights showed unsafe gear. Found bent tab on the nose gear down limit switch actuator

## Other aircraft with N8139A

- [Cancelled 1963-11-06](https://openairdocs.org/deregistered/N8139A-1963-11-06): Cessna 170B, S/N 20991. Owner: [Richins Clyde](https://openairdocs.org/faa-owner/RICHINS%20CLYDE), [Animas, NM](https://openairdocs.org/faa-place/NM/Animas)

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