Skip to content

Public Record · As of May 5, 2026

N3284V

Six Chuter SR2CL View Type →

Status

Registration Valid

Type

Powered Parachute

Engine

—

Last Cert Issue

—

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

Tail Number

N3284V

Serial Number

SKRII 2416

Make

SIX CHUTER INC

Model

SR2CL

Year of Manufacture

—

Mfr / Model Code

059025T

Type Aircraft

Powered Parachute

Type Engine

2-Cycle

Engines

1

Seats

2

Engine Manufacturer

—

Engine Model

—

Horsepower

—

Weight Class

CLASS 1

Registrant

BRAATZ ROGER C · Individual

Address

37384 COUNTY ROAD 75 · LAKE CITY, MN 55041-3903

FAA Region

Central · County 157

Status

Registration Valid

Airworthiness Date

—

Cert Issue Date

—

Expiration Date

—

Last FAA Action

—

Mode S Hex (ICAO24)

A38F00

Mode S (Octal)

50707400

Live position via ICAO24 A38F00

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 SIX CHUTER INC SR2CL

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 /  Related

More on Six Chuter SR2CL in the Atlas

Six Chuter SR2CL type page → — 1 registered · 1 NTSB records

Search the full US registry → · All airworthiness directives → · Accident & safety surface →

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