ARINC SPECIFICATION 816-3-2016 PDF

Full title and description

ARINC Specification 816-3:2016 — Embedded Interchange Format for Airport Mapping Database. This specification defines an open, compact encoding format intended for aerodrome/airport mapping databases (AMDB) that are loaded into airborne systems; it covers file structures, metadata, feature sets and a binary interchange encoding optimized for embedded avionics use.

Abstract

ARINC 816-3 specifies an embedded interchange format for Airport Mapping Databases (AMDB). The document standardizes how airport features and attributes are represented, how metadata and file naming/organization are handled, and how geometric data are encoded (projected coordinates, tessellated polygons, anchor points for labeling). It also defines implementation details such as binary encoding optimizations and a CRC integrity check to support reliable loading into avionics equipment.

General information

• Status: Current (ARINC 816 family — edition 816-3 published and in active use).
• Publication date: 31 August 2016.
• Publisher: Aeronautical Radio, Inc. / SAE Industry Technologies Consortia (ARINC / SAE-ITC).
• ICS / categories: 49: Aircraft and space vehicle engineering (AMDB / avionics data exchange).
• Edition / version: Edition 3 (designated 816-3, 2016).
• Number of pages: 175.

Key bibliographic and product entries list ARINC816-3 as published August 2016 with a 175‑page specification targeted at avionics and aerodrome mapping suppliers.

Scope

The specification defines an open encoding format for airport mapping databases intended for airborne loading and use. It addresses metadata rules, a defined set of features and attributes (building on aeronautical database requirements), an efficient binary interchange format for embedded systems, geometry encoding (projected coordinates, polygon tessellation), file/dataset structure and integrity checking (CRC). ARINC 816 is intended to enable quick, economical and efficient transfer and use of AMDBs in avionics without mandating application-level interpretation.

Key topics and requirements

• Defined feature and attribute set for AMDB content suitable for airborne displays and navigation functions.
• Metadata and file naming conventions to support dataset management and temporal/version control.
• Binary encoding and optimized interchange format for embedded system efficiency and compact storage.
• Geometry rules: use of projected coordinate systems, tessellated polygons, anchors for label placement and precision requirements.
• Integrity and validation mechanisms, including specified Cyclic Redundancy Check (CRC) usage for file-level verification.
• Compatibility/derivation references to aeronautical database models and exchange standards (features derived from established AMDB requirements and exchange schemas).

These topics are implemented to make AMDBs practical for avionics loading, display rendering and other onboard functions while preserving compactness and reliability.

Typical use and users

Primary users are avionics manufacturers, airline data providers, airport/aerodrome mapping producers, flightdeck display and FMS integrators, electronic flight bag (EFB) and flight simulator developers, and systems integrators who load and process airport mapping databases on airborne systems. Regulatory bodies and data certification organizations may reference the format when specifying database delivery for certified avionics.

Related standards

ARINC 816 family is closely related to and builds on aeronautical database requirements and exchange models such as DO-272 / ED-99 and DO-291 / ED-119; it is used alongside or in complement with XML/binary encoding standards referenced by the ARINC family (for example, ARINC 814 and other ARINC AMDB-related documents) and with exchange schemas such as AIXM/AMXM for broader AIM/Airport data exchange workflows. ARINC 816 adds optimized binary and embedded-oriented encodings and some AMDB-specific elements (anchor points, tessellation) beyond generic exchange XML schemas.

Keywords

ARINC 816, AMDB, Airport Mapping Database, Embedded Interchange Format, avionics data, binary encoding, CRC, airport geometry, tessellated polygons, metadata, AEEC.

FAQ

Q: What is this standard?

A: ARINC Specification 816-3:2016 is the ARINC standard that defines an embedded interchange format for Airport Mapping Databases (AMDBs) intended for use in airborne systems, including rules for feature/attribute representation, metadata, and binary encoding.

Q: What does it cover?

A: It covers dataset structure and organization, metadata conventions and file naming, a defined set of aerodrome features and attributes, geometry encoding (projected coordinates, polygon tessellation, anchors for labels), optimized binary encoding for embedded systems and integrity checking (CRC).

Q: Who typically uses it?

A: Avionics OEMs and suppliers, airline data producers, airport mapping/GIS vendors, EFB and display integrators, and system integrators that load AMDBs onto airborne equipment.

Q: Is it current or superseded?

A: The 816-3 edition (2016) is the published edition referenced for ARINC 816 AMDB encoding; product listings and standards catalogs list 816-3 (2016) as the current ARINC 816 edition. Users should check official standards repositories or their organization's standards library for any later amendments or replacements.

Q: Is it part of a series?

A: Yes — ARINC 816 is part of the ARINC family of avionics/data interchange specifications (the 800 series and AMDB-related set). The suffix “-3” denotes this edition/version (third edition in the ARINC 816 family); related ARINC documents (for encoding, terrain, obstacles, etc.) are commonly used together in airport and navigation data workflows.

Q: What are the key keywords?

A: Airport Mapping Database (AMDB), embedded interchange, binary encoding, aerodrome features, metadata, CRC, projected coordinates, tessellation, ARINC 816.