Skip to content
KnownTail
Aircraft record

N1099X1975 Piper PA-32-300

DeregisteredUnclaimedSource: FAA, updated Oct 19, 2026

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

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

Registration
Deregistered
Last based in
Xxx, OK
owner city / state
Engine
TI0-540 SER · 310 hp
Lycoming
Owners
1
on record
NTSB events
1
destroyed, 1986
ADs may apply
4
confirm with A&P
Service reports
0
since 1995

Registration

FAA Aircraft Registry · Oct 19, 2026
Last registered owner
Individual owner
City, state
Xxx, OK
Canceled
Jun 14, 2013
Airworthiness
Standard · Normal
Airworthiness date
May 7, 1975

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-300
Year
1975
Serial number
32-7540143
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
A029CC

Engine

Make and model
Lycoming Ti0-540 Ser
Type
Reciprocating
Power
310 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. until 2013Individual ownerXxx, OK

Individual owners are shown by city and state only.

Safety record

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

NTSB events (1)

Accident · destroyed

Mar 7, 1986 · Andalusia, AL

THE ACCIDENT FLT WAS TO BE THE LAST IN A SERIES OF FLT TESTS. THIS FLT WAS FOR THE PURPOSE OF DETERMINING THE LANDING CHARACTERISTICS OF THE ACFT WITH A COMBINATION SPEED/STOL KIT INSTALLED. WHEN THE FAA FLT TEST PLT FAILED TO RETURN FROM THE MISSION A SEARCH WAS STARTED. THE ACFT HAD BEEN SEEN SPINNING BY 3 WITNESSES WHO ALSO SAW THE PLT JUMP FROM THE ACFT AT LOW ALT. THE PLT WORE A PARACHUTE…

Damage
Destroyed
Injuries
Fatal
Report
ATL86MA087

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

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-300)
2010-15-10Piper Aircraft, Inc. PA-28, PA-32, PA-34, and PA-44 Series AirplanesAug 31, 2010Airframe (PA-32-300)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-300)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-300)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 19, 2026
  • NTSB accident and incident databaseAccidents and incidents since 1982updated Oct 15, 2026
  • FAA Airworthiness Directives (Federal Register)ADs published since 1998updated Oct 19, 2026
  • FAA Service Difficulty ReportsReports since 1995updated Oct 16, 2026

Request owner name removalReport an error in this record