Public Record · As of May 5, 2026
N1995M
As+ AS-4 · 1995 View Type →
Status
Registration Valid
Type
Glider
Engine
AMA/EXPR UNKNOWN ENG
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 N1995M.
Tail Number
N1995M
Serial Number
011
Make
AS+
Model
AS-4
Year of Manufacture
1995
Mfr / Model Code
05601ZH
Type Aircraft
Glider
Type Engine
None
Engines
—
Seats
1
Engine Manufacturer
AMA/EXPR
Engine Model
UNKNOWN ENG
Horsepower
—
Weight Class
CLASS 1
Certification
Experimental (+1 flag) · code 40
Registrant
DANIEL ARTHUR D · Individual
Address
PO BOX 150 · FISHTAIL, MT 59028-0150
FAA Region
Southern · County 095
Status
Registration Valid
Airworthiness Date
—
Cert Issue Date
—
Expiration Date
—
Last FAA Action
—
Mode S Hex (ICAO24)
A18CAD
Mode S (Octal)
50306255
Live position via ICAO24 A18CAD
External services. Live tracks are unaffiliated with TallyAero or the FAA.
02 / NTSB Records
Events on file with the National Transportation Safety Board
-
May 29, 2000
EPHRATA, Washington
03 / Airworthiness Directives
Applicable to AS+ AS-4
Federal Aviation Administration airworthiness directives matched to make and model. Each entry links to the Federal Register publication.
-
May 17, 2006
Federal Register →Airworthiness Directives; McDonnell Douglas Model DC-9-10, DC-9-20, DC-9-30, DC-9-40, and DC-9-50 Series Airplanes; Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), and DC-9-87 (MD-87) Airplanes; Model MD-88 Airplanes; Model MD-90-30 Airplanes; and Model 717-200 Airplanes
The FAA is adopting a new airworthiness directive (AD) for certain McDonnell Douglas transport category airplanes. This AD requires an inspection to determine the part number of the upper and lower stop pad support fittings of all the lower cargo doors, repetitive inspections of all early configuration stop pad support fittings, and corrective action if nec…
-
Aug 20, 2001
Federal Register →Airworthiness Directives; Boeing Model 737-600, -700, and -800 Series Airplanes
This amendment adopts a new airworthiness directive (AD) that is applicable to certain Boeing Model 737-600, -700, and -800 series airplanes. This action requires repetitive inspections for corrosion or cracking of the keel beam splices, and corrective action, if necessary. This action also provides an optional terminating action for the repetitive inspecti…
-
Sep 20, 2000
Federal Register →Airworthiness Directives; Boeing Model 737-100, -200, -200C, -300, -400, and -500 Series Airplanes
This amendment supersedes an existing airworthiness directive (AD); applicable to certain Boeing Model 737-100, -200, -200C, -300, - 400, and -500 series airplanes; that currently requires a one-time inspection of the attachment nuts at each end attachment of the elevator tab push rods to measure run-on torque values, and corrective actions, if necessary. T…
-
Apr 13, 1994
Federal Register →Airworthiness Directives; McDonnell Douglas Model MD-11 and MD- 11F Series Airplanes Equipped With Honeywell Flight Management Computers
This amendment adopts a new airworthiness directive (AD) that is applicable to certain McDonnell Douglas Model MD-11 and MD-11F series airplanes. This action requires revising the FAA-approved Airplane Flight Manual (AFM) to ensure that the flight crews verify the accuracy of data provided by the Flight Management Computer (FMC) under certain conditions. Th…
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.