Skip to content
KnownTail
Aircraft record

N3206W1965 Piper PA-32-260

DeregisteredUnclaimedSource: FAA, updated Oct 17, 2026

This N-number isn't registered right now. Below is its last known registration, canceled Feb 25, 2013.

Safety record in brief:1 NTSB accident (destroyed damage, Dec 1983)4 ADs may apply

Registration
Deregistered
Last based in
Portland, OR
owner city / state
Owners
1
since 1982
NTSB events
1
destroyed, 1983
ADs may apply
4
confirm with A&P
Service reports
0
since 1995

Registration

FAA Aircraft Registry · Oct 17, 2026
Last registered owner
Partnership
City, state
Portland, OR
Certificate issued
Sep 1, 1982
Canceled
Feb 25, 2013
Airworthiness
Standard · Normal
Airworthiness date
Jun 30, 1965

We never show street addresses, even though they appear in the public FAA file. Individual owners are shown by city and state only.

Airframe & engine

FAA Registry + type data

Airframe

Manufacturer
Piper
Model
PA-32-260
Year
1965
Serial number
32-6
Aircraft type
Fixed wing single engine
Category
Land
Certification
Type Certificated
Seats
6
Engines
1
Max takeoff weight
Up to 12,499 lb
Mode S code
A3718F

Engine

Make and model
Lycoming 0-540 Series
Type
Reciprocating
Power
250 hp

Total time and engine hours aren't public. They appear here once the owner adds logbooks.

Ownership history

Ownership history from FAA records
  1. 1982 – 2013PartnershipPortland, OR

Individual owners are shown by city and state only.

Safety record

NTSB · Oct 15, 2026 · FAA ADs · Oct 17, 2026 · SDRs · Oct 16, 2026

NTSB events (1)

Accident · destroyed

Dec 2, 1983 · Holtville, CA

THE PLT HAD DEPARTED MAZATLAN, MEXICO AT 0632 PST & HAD LANDED AT LOS MOCHIS & MEXICALI, MEXICO & AT CALEXICO, CA, WHERE HE CLEARED U.S. CUSTOMS. BEFORE DEPARTING CALEXICO, HE TELEPHONED HIS FAMILY & TOLD THEM THE WX HAD BEEN POOR ALL DAY. THE ESTIMATED TIME OF ARRIVAL AT YUMA, AZ WAS 1730 PST. WHEN THE ACFT DD NOT ARRIVE, A SEARCH WAS BEGUN. THE WRECKAGE WAS FOUND ABOUT 17 MI EAST OF IMPERIAL…

Damage
Destroyed
Injuries
Fatal
Report
LAX84FA087

From NTSB records; matched by serial number.Read NTSB report (search CAROL for LAX84FA087)

Accident history for this model

ADs published since 1998 that may apply (4)

These match the airframe or engine model. Whether each one applies, and whether it's been complied with, depends on serial numbers, equipment and logbook entries. Applicability must be confirmed by a mechanic against the aircraft's records.

ADSubjectEffectiveApplies to
2013-02-13Stabilizer Control SystemMar 11, 2013Airframe (PA-32-260)
2010-15-10Piper Aircraft, Inc. PA-28, PA-32, PA-34, and PA-44 Series AirplanesAug 31, 2010Airframe (PA-32-260)Certain serial numbers: PA-28-140 28-20001–28-26946; PA-28-140 28-7125001–28-7725290; PA-28-150 28-03; PA-28-150 28-1–28-4377; PA-28-150 28-1760A; PA-28-160 28-03; …
99-05-09The New Piper Aircraft, Inc. PA-23, PA- 24, PA-28, PA-32, and PA-34 Series AirplanesMar 19, 1999Airframe (PA-32-260)Certain serial numbers: PA-23-235 27-505–27-622; PA-23-250 27-01–27-2504; PA-24-180 24-103–24-3687; PA-24-250 24-103–24-3687; PA-24-260 24-3642; PA-24-260 24-4000–24-5028; …. Only with: Equipped with Purolator air filter P/N 638873, Model CA161PL, or Piper P/N 460-632 (PS60007-2).
95-26-13The New Piper Aircraft, Inc. (Formerly Piper Aircraft Corporation) PA28 and PA32 Series…Feb 5, 1996Airframe (PA-32-260)Only with: Equipped with oil cooler hose assemblies that do not meet TSO-C53a, Type D requirements.

AI-extracted — verify against original. Matched from each AD's applicability section; ADs replaced by a later AD are left out.

Service Difficulty Reports (0)

No Service Difficulty Reports found for this airframe since 1995.

Sources

  • FAA Aircraft RegistryRegistration, owner city and state, airframe, engineupdated Oct 17, 2026
  • NTSB accident and incident databaseAccidents and incidents since 1982updated Oct 15, 2026
  • FAA Airworthiness Directives (Federal Register)ADs published since 1998updated Oct 17, 2026
  • FAA Service Difficulty ReportsReports since 1995updated Oct 16, 2026

Request owner name removalReport an error in this record