Public Record · As of May 5, 2026
N64G
Aer-pegaso M-100S · 1962 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 N64G.
Tail Number
N64G
Serial Number
33
Make
AER-PEGASO
Model
M-100S
Year of Manufacture
1962
Mfr / Model Code
0200506
Type Aircraft
Glider
Type Engine
None
Engines
—
Seats
1
Engine Manufacturer
NONE
Engine Model
NONE
Horsepower
—
Weight Class
CLASS 1
Certification
Standard · code 1
Registrant
WILLE CHAD C · Individual
Address
1139 STATE HIGHWAY 148 · CORNING, IA 50841-7507
FAA Region
3 · County 003
Status
Registration Valid
Airworthiness Date
—
Cert Issue Date
—
Expiration Date
—
Last FAA Action
—
Mode S Hex (ICAO24)
A86378
Mode S (Octal)
52061570
Live position via ICAO24 A86378
External services. Live tracks are unaffiliated with TallyAero or the FAA.
02 / NTSB Records
Events on file with the National Transportation Safety Board
-
May 25, 1969
BOCA RATON, Florida serious
Airport · BCT Boca Raton Airport
03 / Airworthiness Directives
Applicable to AER-PEGASO M-100S
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.