ARINC 424 Aeronautical Navigation Database

AeroNavData is one of only a handful of certified navigation data providers around the world that holds a current FAA audited and certified Type 1 Letter of Agreement (LOA).  Our FAA-certified data processes follow strict AC 20-153 and DO-200A guidelines and standards.   AeroNavData codes and maintains a comprehensive and high-quality  ARINC 424 aeronautical navigation database.

 

Because of our expansive experience, we fully understand that all aeronautical navigation databases must implement the requirements of the Flight Management System (FMS) manufacturers.  Therefore, we work closely with our customers to capture their specific data quality requirements (DQRs).  As a result, our data adhere to the specific data preparation and data transmission criteria.

 

• We work with US DoD, FAA, and foreign Aeronautical Information Publications (AIP)
• We work within published 28 and 56-day Aeronautical Information Regulation and Control (AIRAC) cycles.
• Our RNAV (GPS and RNP), ILS, LOC, VOR, TACAN, NDB, and DP and STAR procedures adhere to ARINC 424 Supplement standards.
• We maintain all Standard Instrument Approach Procedures (SIAPs), Departure Procedures (DPs) and Standard Terminal Arrival Routes (STARs) in the western hemisphere in ARINC 424 data format.

Our Navigation Data includes:

CAN, USA, LAM, US-owned PAC, and SAM ARINC Regions

Our Navigation Database includes all Supplemental and Procedure information contained within the CAN, US, LAM, PAC and SAM ARINC Regions.  The data includes Airport, Heliport, Navaid, Waypoint, Enroute, Airspace, Communication, SID/STAR, RNAV and Conventional Procedure information.

Navigation Source Ingest, Analysis, and Management

Our Aeronautical Analyst teams code and maintain our aeronautical navigation database through the meticulous analysis of official navigation sources.  As a result, our Type 1 LOA coding process ensures that our database reflects authoritative source information contained in Aeronautical Information Publications (AIP) from around the world.

We perform navigation procedure data maintenance within officially published 28 and 56-day AIRAC cycles.  Through our certified process, we ensure that the procedures and supplemental data align with ARINC 424 data standards for use in Flight Management Systems (FMS), and for flight inspection, flight planning, and simulation.

Working with DO-200A Data Quality Requirements (DQR)

One of the requirements of our LOA process is the definition of the specific Data Quality Requirements (DQR) for the navigation data by the data processing organization and the provision of this DQR by the data suppliers.

Aeronautical Navigation Database Validation and Verification

At AeroNavData we use an innovative and unique systematic approach to Validation and Verification processes (V&V). We perform a final V&V after output and publication with our complete Post-Publication Review (PPR).  Consequently, we confirm that all procedures have been initially entered, modified, or corrected since the last AIRAC cycle.

We perform our review, as defined by DO-200A Standards:

Validation:  All data elements are checked as having values that are fully applicable to the identity of the data element, or that a set of data elements are deemed acceptable for their purpose.

Verification:  All data element values are checked against the value originally supplied.

AeroNavData’s unique approach includes visually validating the procedures using our Visual Procedure Check (VPC) to graphically display terminal procedure coding in the ARINC format.

By using this distinctive visualization tool we analyze the coded flight path using a variety of simulated aircraft performance characteristics and weather scenarios.

As a result, we ensure that:

•  the procedure is error-free
•  it meets the procedure designer’s original intent
•  it can be flown according to aircraft specifications

In addition, our analysts use the VPC application to uncover discrepancies in source documentation. Such as:

• Insufficient vertical descent angles
• Misplaced fix or runway threshold coordinates
• Unnecessary or incorrect turn directions
• Incongruent magnetic variations
• Inadequate intercept angles

In all cases, the source originator is notified of any and all discrepancies found for corrective action.