Determining an aircraft's autoland certification from a manufacturer standpoint requires looking beyond the Type Certificate Data Sheet, which is a common starting point but ultimately the wrong document for this purpose. The TCDS is a summary instrument covering basic certification parameters — weights, speeds, powerplant data, and airworthiness limitations — and deliberately omits optional system capabilities because not every serial number of a given type will be equipped identically. Autoland capability, which underpins Category II and Category III ILS operations, is a system-level approval that depends on specific avionics packages being installed and activated. The authoritative document is the **Airplane Flight Manual (AFM)**, and more specifically, an **Airplane Flight Manual Supplement (AFMS)** tied to the installed autoland-capable autopilot/flight director configuration. When a buyer options autoland on a new business jet, the manufacturer produces or references an FAA-approved AFM supplement — sometimes embedded within the main manual — that outlines system architecture, performance data, failure mode behavior, and operational limitations specific to that capability.
For aircraft where autoland was added post-production or certified under a separate avionics suite, the relevant documentation may flow through a **Supplemental Type Certificate (STC)** and its associated STC data sheet, which carries its own FAA approval. The avionics OEM — Honeywell, Collins Aerospace, Garmin — often holds or participates in the approval, and their system description documents will reference the certification basis. Buyers and operators should also examine the **aircraft equipment list** and configuration records, which document exactly which software loads, LRUs, and options are installed, since autoland capability on platforms like the Gulfstream G650 or Bombardier Global 7500 can be granular: the hardware may be present but the capability may not be activated or approved unless specific line-selectable options and software versions are confirmed. In practice, the most direct verification path is to review the AFM's CAT II/III section, confirm the installed avionics match the approved configuration described therein, and cross-reference with the **aircraft logs** showing the avionics installation and any associated field approvals.
The operational authorization layer — OpSpecs, LOAs, training programs — exists entirely downstream of the aircraft capability document and is where the poster's question correctly draws a distinction. Advisory Circulars **AC 120-28** (CAT III criteria) and **AC 120-29** (CAT I/II criteria) define what the FAA requires to be present in AFM documentation for operational approvals to be granted, making them useful cross-references for understanding what to look for in a given AFM. A well-equipped business jet AFM covering CAT IIIa autoland operations will contain specific decision height (or no-DH) data, required system redundancy, alert height information, and go-around performance — all FAA-approved content that constitutes the de facto "certificate" of autoland capability from the manufacturer's standpoint.
This question carries real-world weight for flight departments evaluating pre-owned aircraft acquisitions. A jet may be advertised as autoland-capable, but without verifying the AFM supplement applicability against the actual installed avionics configuration and software load, operators may find the aircraft is not legally authorized to fly CAT III approaches regardless of what the hardware appears to support. This gap — between hardware presence and approved capability — is increasingly relevant as sophisticated avionics suites allow selective feature activation. For Part 91K and 135 operators, this distinction matters before investing in CAT II/III OpSpecs approval, crew training, and simulator currency, only to discover the specific aircraft registration cannot support the intended operation. Due diligence on aircraft purchases should always include an avionics audit against the AFM supplement to confirm the configuration matches the approved autoland capability.
The broader context is that autoland capability, once the exclusive domain of heavy air carrier jets, is now a standard purchase option across most large-cabin business jets and is actively being extended further down the market. Garmin's Autoland system, certified on platforms like the Piper M600 and Cirrus Vision Jet under emergency-use STC approvals, represents a different certification pathway — one tied to a specific STC rather than a type design option — but the documentation principles are similar. As the industry moves toward advanced automation and eventually single-pilot certification for larger aircraft, the question of which document formally establishes a given system's capability will become a more frequent regulatory and legal question for operators, insurers, and flight departments alike.