Public Record · As of May 5, 2026
N1017
Glasflugel H 301 LIBELLE · 1967 View Type →
Status
Registration Valid
Type
Glider
Engine
NONE NONE
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 N1017.
Tail Number
N1017
Serial Number
41
Make
GLASFLUGEL
Model
H 301 LIBELLE
Year of Manufacture
1967
Mfr / Model Code
3800337
Type Aircraft
Glider
Type Engine
None
Engines
—
Seats
1
Engine Manufacturer
NONE
Engine Model
NONE
Horsepower
—
Weight Class
CLASS 1
Certification
Standard (+1 flag) · code 1N
Registrant
JEDNACZ SCOTT T · Individual
Address
8383 E 114 ST S · BIXBY, OK 74008
FAA Region
2 · County 143
Status
Registration Valid
Airworthiness Date
—
Cert Issue Date
—
Expiration Date
—
Last FAA Action
—
Mode S Hex (ICAO24)
A00BB8
Mode S (Octal)
50005670
Live position via ICAO24 A00BB8
External services. Live tracks are unaffiliated with TallyAero or the FAA.
02 / NTSB Records
Events on file with the National Transportation Safety Board
-
May 28, 1983
LOS LUNAS, New Mexico
Airport · E98 MID VALLEY
03 / Airworthiness Directives
Applicable to GLASFLUGEL H 301 LIBELLE
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
- FAA Aircraft Registry →
Refreshed May 5, 2026
Available
- NTSB CAROL →
Refreshed May 5, 2026
Available
- Federal Register (FAA Airworthiness Directives) →
Refreshed May 5, 2026
Available
- FAA Service Difficulty Reports →
Refreshed May 5, 2026
Unavailable
We render only what the agency publishes. Found a factual error? Report it → We acknowledge within 5 business days and resolve within 14.