Overview#
Aviation compliance teams and safety investigators routinely encounter the same frustrating problem: the same aircraft appears under three different identifiers across a sanctions filing, an ADS-B tracking export, and a maintenance database. The tail number format differs between systems, an ICAO hex code doesn't map cleanly, and a manufacturer serial number sits in a separate spreadsheet with no cross-reference. Resolving that fragmentation manually takes hours and introduces errors that can undermine enforcement or investigation work.
Aircraft Registry Intelligence eliminates that identifier fragmentation through automated normalisation, multi-source enrichment, and deduplication across global aviation registries. Each identifier is resolved to a canonical record enriched with manufacturer data, ownership history, operational status, and registration history, giving compliance teams and flight operations analysts a single authoritative source regardless of which format the data arrived in.
Open Standards#
- ICAO Annex 7 (Aircraft Nationality and Registration Marks): The registration-mark prefix scheme (N-, G-, D-, F-, C-, VH-, JA- etc.) and the country-prefix routing logic that determines which national registry to query are defined by ICAO Annex 7; the service normalises identifiers against this scheme.
- ICAO Doc 9684 / Annex 10 Mode S 24-bit Address: ICAO 24-bit transponder addresses (Mode S hex codes) are allocated per country blocks defined in ICAO Annex 10 and Doc 9684; the service resolves hex codes to country of registration using these allocation ranges.
- RTCA DO-260B / EUROCAE ED-102A (ADS-B): ADS-B position and identity broadcasts carry the ICAO 24-bit address as the primary aircraft identifier; the capability ingests and normalises these hex identifiers as a first-class input format.
- ISO 3166-1 alpha-2: Two-letter country codes are used throughout the data model and registry-routing logic to attribute registrations, operator records, and ICAO hex-range mappings to their respective national authorities.
- GraphQL (June 2018 specification): All registry queries, identifier normalisation, enrichment, and deduplication operations are exposed through a typed GraphQL API, enabling structured batch requests and precise field selection.
- OAuth 2.0 (RFC 6749) / JSON Web Tokens (RFC 7519): API access is gated by bearer token authentication; JWT claims carry the authenticated user identity that is validated before any registry lookup or enrichment operation is permitted.
- JSON (RFC 8259): Registry responses, operator history records, and deduplication groups are serialised as JSON, which is the interchange format for both the external registry integrations and the API responses returned to clients.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14
Key Features#
Multi-Format Identifier Normalisation#
Recognizes and standardises tail numbers, ICAO hex codes, and manufacturer serial numbers across seven major aviation registries. Handles common input variations including case differences, embedded spaces, hyphenated formats, and erroneous prefixes. Batch normalisation processes thousands of identifiers concurrently.
FAA Aircraft Registry Integration#
Integration with the FAA Aircraft Registration Database, covering 330,000 or more active registrations, for authoritative US aircraft data including registration status, aircraft specifications, ownership information, and airworthiness certification. Operator history and registration history tracking captures temporal ownership changes.
International Registry Coverage#
Integration with Aviation Edge for 195 or more country coverage, providing worldwide aircraft tracking and compliance validation. Consistent data models regardless of source, with automatic routing to the appropriate registry based on identifier format.
Deduplication and Alias Resolution#
Groups related identifiers into deduplication groups with canonical IDs, alias lists, and confidence scores. Correlates identifiers across types using registry data, handles temporal deduplication for aircraft that operated under different identifiers sequentially, and supports manual override for edge cases.
Manufacturer Serial Number Tracking#
Tracks manufacturer serial numbers that uniquely identify aircraft throughout their entire lifecycle regardless of registration changes. Cross-referencing queries retrieve all identifiers associated with a given MSN across operational history.
Use Cases#
- Sanctions Compliance: Verify aircraft ownership and operator history against sanctions lists for charter aviation operations, detecting historical links to designated entities through operator history analysis.
- Safety Investigation: Track aircraft maintenance histories across ownership transfers and re-registrations, identifying patterns where mechanical issues were not disclosed during sales.
- Fleet Analytics Deduplication: Consolidate duplicate aircraft records in tracking databases caused by registration changes, ICAO hex variants, and data import inconsistencies.
- Export Control: Enforce export control regulations by correlating controlled aircraft across jurisdiction transfers and re-registrations using MSN-level tracking.
Integration#
All capabilities are available through a typed API supporting batch processing, multi-tenant isolation, and webhook notifications for registry data changes. Client libraries available for JavaScript, Python, and Go.