Public Record · As of May 5, 2026
N669M
Soko GALEB G2-A · 1967 View Type →
Status
Registration Valid
Type
Fixed Wing Single Engine
Engine
ROLLS-ROYC VIPER MK522
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 N669M.
Tail Number
N669M
Serial Number
23172
Make
SOKO
Model
GALEB G2-A
Year of Manufacture
1967
Mfr / Model Code
056184K
Type Aircraft
Fixed Wing Single Engine
Type Engine
Turbo-jet
Engines
1
Seats
2
Engine Manufacturer
ROLLS-ROYC
Engine Model
VIPER MK522
Horsepower
333 hp
Weight Class
CLASS 1
Certification
Experimental (+1 flag) · code 43
Registrant
— · Individual
Address
—
Status
Registration Valid
Airworthiness Date
—
Cert Issue Date
—
Expiration Date
—
Last FAA Action
—
Mode S Hex (ICAO24)
A8D6BB
Mode S (Octal)
52153273
Live position via ICAO24 A8D6BB
External services. Live tracks are unaffiliated with TallyAero or the FAA.
02 / NTSB Records
Events on file with the National Transportation Safety Board
-
Sep 4, 1973
PECOS, Texas fatal
Airport · 96XA Gnaws Farm Airport
03 / Airworthiness Directives
Applicable to SOKO GALEB G2-A
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.