ARINC Industry Activities
"Together We Set the Standard"
Top Banner

ARINC IA

AEEC

AMC

FSEMC

ARINC Standards

Upcoming Events

Memberships

Creating Value for Aviation Through Collaboration Image

Aeronautical Databases (ADB) Subcommittee

Last Update: October 27, 2017

Chairman: Brian Gilbert, Boeing
APIM 12-006: Terrain and Obstacle Databases (TODB) (pdf, 200K)
APIM 12-007:
XML Encoding and Compression Standard (pdf, 182K)


Goal: To increase pilot situational awareness both on the ground and airborne to improve safety and efficiency of flight.

Scope:

Airport Mapping Database: ARINC Specification 816 defines encoding formats for airport mapping databases that can be loaded directly into airborne systems, thus enhancing taxi operations. When designed and implemented, this ARINC Standard will enable a quick, economic, and efficient use of airport databases in every aircraft.

Terrain Database: ARINC Project Paper 813 will define encoding formats for terrain databases that can be loaded directly into airborne systems, thus enhancing flight crew situational awareness. This will enhance the value of Terrain Avoidance and Warning Systems (TAWS), Vertical Situation Displays (VSD), Synthetic Vision Systems (SVS), and enroute mapping.

Obstacle Database: ARINC Project Paper 815 will define encoding formats for obstacle databases that can be loaded directly into airborne systems, thus enhancing flight crew situational awareness. This will enhance the value of Terrain Avoidance and Warning Systems (TAWS), Vertical Situation Displays (VSD), Synthetic Vision Systems (SVS), and enroute mapping.

XML Encoding and Compression: ARINC Specification 814 defines a single XML encoding and compression standard that can be invoked by any ARINC Standard to optimize database storage and processing efficiency on the aircraft side. This ARINC Standard was developed in conjunction with Airport, Terrain, and Obstacle Databases.

Benefit:

Standardized airport, terrain, and obstacle databases will enable database providers and airborne system suppliers to use a common encoding format. This fosters competition among the database providers. The airlines can select a supplier of data without impact on the airborne system. Use of standardized airport, terrain and obstacle databases will lead to operational improvements in taxi operations as well as in flight. These improvements translate into economic benefit to the airlines.


Current Drafts:

Draft 1 of ARINC Project Paper 813: Embedded Interchange Format for Terrain Databases

Draft 1 of Supplement 1 to ARINC Specification 814: Extensible Markup Language (XML) Encoding and Compression Standard

Draft 2 of ARINC Project Paper 815: Embedded Interchange Format for Terrain and Obstacle Databases

Working Papers:

Next Meeting Announcement:

Last Meeting Report:

Aeronautical Databases (ADB) Subcommittee
March 7-9, 2017, in Haifa, Israel


 

Staff Contact

Pete Grau
peter.grau@sae-itc.org
240.334.2580