Skip to content

Public Record · As of May 5, 2026

N582UT

Buckeye BREEZE · 2002 View Type →

Status

Registration Valid

Type

Powered Parachute

Engine

ROTAX 582SER

Last Cert Issue

—

Aircraft Resources

Engine · Rotax Aircraft Engines → Search FAA TCDS for BUCKEYE INDUSTRIES BREEZE →

01 /  Registration

Filed with the Federal Aviation Administration

Every cell below is a literal field from the FAA Aircraft Registry. Click any value to open the FAA registry record for N582UT.

Tail Number

N582UT

Serial Number

2137

Make

BUCKEYE INDUSTRIES

Model

BREEZE

Year of Manufacture

2002

Mfr / Model Code

059019K

Type Aircraft

Powered Parachute

Type Engine

2-Cycle

Engines

1

Seats

2

Engine Manufacturer

ROTAX

Engine Model

582SER

Horsepower

65 hp

Weight Class

CLASS 1

Certification

Experimental (+2 flags) · code 48A

Registrant

PRIDMORE SALLY J · Individual

Address

PO BOX 277 · FAIRFIELD, ID 83327-0277

FAA Region

Southern · County 025

Status

Registration Valid

Airworthiness Date

—

Cert Issue Date

—

Expiration Date

—

Last FAA Action

—

Mode S Hex (ICAO24)

A77F2A

Mode S (Octal)

51677452

Live position via ICAO24 A77F2A

ADS-B Exchange → FlightAware → FlightRadar24 →

External services. Live tracks are unaffiliated with TallyAero or the FAA.

02 /  NTSB Records

Events on file with the National Transportation Safety Board

03 /  Airworthiness Directives

Applicable to BUCKEYE INDUSTRIES BREEZE

Federal Aviation Administration airworthiness directives matched to make and model. Each entry links to the Federal Register publication.

No matching airworthiness directives are on file for this make and model in the Federal Register.

04 /  Service Difficulty Reports

FAA SDR filings

The FAA does not currently expose a public API for Service Difficulty Reports. We do not back-fill or paraphrase. Search the FAA SDR portal directly →

05 /  Sources & Methodology

Every fact on this page links to its primary US-government source

We render only what the agency publishes. Found a factual error? Report it → We acknowledge within 5 business days and resolve within 14.