Aircraft Registry

Overview#

A financial crimes investigator traces a suspicious shell company to a Cayman Islands-registered entity that owns three aircraft. The planes are listed under different tail numbers across FAA and international registries, each formatted differently, with one entry using an ICAO hex code rather than a standard registration. Without normalisation, those three records look like unrelated assets. With the Aircraft Registry module, they resolve to a single ownership chain in seconds.

The module provides comprehensive management, normalisation, and querying of aircraft registration data from the FAA and international aviation authorities. It enables accurate aircraft identification, deduplication, and enrichment, capabilities that are essential for aviation-related investigations, sanctions compliance, and financial crime analysis.

Key Features#

Tail Number Normalisation: Automatically clean, standardise, and validate aircraft tail numbers from various input formats with confidence scoring.
International Registry Support: Recognize and normalise aircraft identifiers from the United States, United Kingdom, Germany, France, Canada, Australia, Japan, and other international registries.
ICAO Hex Code Processing: Normalise 24-bit ICAO transponder addresses and automatically determine the country of registration from ICAO address ranges.
Registry Lookups: Query the FAA registry and international aviation databases to retrieve complete aircraft information including status, type, manufacturer, model, and ownership details.
Operator History: Track historical and current operators, owners, and lessees for each aircraft, enabling investigation of ownership structures and control chains.
Registration History: Maintain a timeline of aircraft registrations across different countries to identify transfers and flag changes.
Identifier Enrichment: Bulk-enrich aircraft identifiers with registry data for investigative analysis.
Deduplication: Group equivalent aircraft identifiers from different formats and sources into canonical entities with confidence scoring.
Programmable API Access: Full API support for normalisation, lookup, enrichment, and deduplication operations.

Use Cases#

Financial crime investigators extract aircraft identifiers from corporate filings and transaction metadata, normalise them against multiple registries, and cross-reference against sanctions lists to identify prohibited operators.

Sanctions compliance teams at banks and trading firms run batch enrichment on aircraft encountered in due diligence workflows, verifying registration status and ownership history before proceeding with transactions.

Defence and intelligence analysts track aircraft ownership transfers across jurisdictions to identify when assets move into the control of sanctioned entities or state-linked operators.

Border control agencies resolve conflicting aircraft identifiers from different data systems into single canonical records, eliminating duplicate entries that would otherwise fragment the operational picture.

Aviation Asset Tracking: Track aircraft ownership and transfers for compliance monitoring, including sanctions checks on operators and licence verification.
Aviation-Related Investigations: Extract aircraft identifiers from transaction metadata, normalise them, look up registry data, and cross-reference against sanctions lists to assess risk.
Compliance Verification: Verify that aircraft registrations are active, operators are licensed, and there are no sanctions or restrictions on associated entities.
Entity Resolution: Resolve multiple references to the same aircraft across different data sources and formats into a single canonical identity.

Integration#

The Aircraft Registry module integrates with other Argus modules for aviation-focused investigations:

Blockchain Analysis: Cross-reference aircraft identifiers found in cryptocurrency transaction metadata with registry data for financial investigation.
Entity Management: Aircraft and their operators are represented as entities in the knowledge graph for relationship analysis.
Compliance: Registration status and operator history feed into compliance verification workflows.
OSINT: Aviation registry data enriches open-source intelligence gathering with authoritative registration information.

Open Standards#

ICAO Annex 7 (Aircraft Nationality and Registration Marks): The module validates and normalises aircraft tail numbers against the country-prefix conventions defined in ICAO Annex 7, covering US (N-), UK (G-), Germany (D-), France (F-), Canada (C-), Australia (VH-), Japan (JA-), and other ICAO-registered prefixes.
ICAO 24-bit Address Allocation (Annex 10 / Doc 9684): ICAO transponder hex codes are resolved to country of registration by mapping the 24-bit address against the nationally-assigned allocation ranges published by ICAO, enabling automatic country detection from a Mode S address alone.
ICAO Annex 10 / RTCA DO-260B (ADS-B / Mode S SSR): The ICAO hex field stored and exchanged for each aircraft record is the Mode S 24-bit transponder address as specified in the Secondary Surveillance Radar and ADS-B standards, and the module accepts this identifier as a primary lookup key.
ISO 3166-1 alpha-2: Two-letter country codes (US, GB, DE, FR, CA, AU, JP, etc.) are used consistently throughout registration records, operator histories, and ICAO hex country derivation to identify the state of registry.
ISO 8601: All dates and timestamps in registration histories, operator records, and last-updated fields are serialised in ISO 8601 format, ensuring interoperability with downstream analytical and compliance systems.
GraphQL (June 2018 specification): The entire public-facing API for normalisation, lookup, enrichment, and deduplication operations is exposed as a typed GraphQL schema, enabling structured queries and mutations against aircraft registry data.
OAuth 2.0 / JSON Web Tokens (RFC 6749 / RFC 7519): All GraphQL endpoints are protected by bearer-token authentication conforming to OAuth 2.0, with access-control checks applied per operation before any registry data is returned.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14