# N4646F: Piper PA-32R-300, registration cancelled 2018-01-05

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: January 5, 2018
- Status when cancelled: Registration expired, pending cancellation
- Airframe: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213)
- Data sheets: [TCDS A3SO](https://openairdocs.org/tcds/A3SO) (OpenAirDocs)
- Serial number: 32R-7680471
- Type of aircraft: Fixed wing single engine
- Airworthiness: Standard, normal
- Airworthiness date: September 2, 1976
- Certificate issued: August 26, 2010
- Last registry action: January 25, 2012
- Mode S code: A5ABA7
- Owner when cancelled: [Sedlacek Steven G](https://openairdocs.org/faa-owner/SEDLACEK%20STEVEN%20G)
- Location: [Boise, ID](https://openairdocs.org/faa-place/ID/Boise)
- Owner type: Individual
- Owner's area on the map: 43.7065° N, 116.2767° W: Placed by OpenAirDocs at the center of ZIP code 83714, within about 4 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N4646F
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=4646F
- Page: https://openairdocs.org/deregistered/N4646F-2018-01-05

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-300: https://openairdocs.org/model/piper-pa-32r-300.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 WPR14LA336](https://openairdocs.org/ntsb/WPR14LA336), Aug 10, 2014: Piper PA 32R-300 (N4646F), West Jordan, UT, destroyed. Probable cause: A partial loss of engine power during initial climb for reasons that could not be determined due to the severity of the damage to the engine.

## FAA accident and incident reports (3)

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 20140810014769A](https://openairdocs.org/incident/20140810014769A), Aug 10, 2014: Piper PA-32R-300 (N4646F), Salt Lake City, UT, Destroyed. Aircraft departed runway 16 at South Valley Regional Airport (U42) at approximately 0901 local time. Aircraft impacted the ground at an approximate heading of…
- [Incident 19890311026379I](https://openairdocs.org/incident/19890311026379I), Mar 11, 1989: Piper PA32R300 (N4646F), Fort Wayne, IN. Complete power failure. Forced landing without incident. Had faulty voltage regulator.
- [Incident 19800301027989I](https://openairdocs.org/incident/19800301027989I), Mar 1, 1980: Piper PA32R300 (N4646F), Dubuque, IA, Minor damage. Electrical failure. Pilot failed to extend gear for precautionary 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.