Letter of Compliance as US Navy Aeronautical Data Provider
AeroNavData supported the U. S. Navy, Naval Air Systems Command, NAVAIR, Program Manager Air Combat Electronics (PMA209) by providing a certified Navigation Database for use in the E-2D Advanced Hawkeye aircraft during its initial fielding and to support related aircrew training.
AeroNavData already holds FAA Type 1 Letter of Acceptance (LOA)* that was issued by the FAA Aircraft Certification Office (ACO) on February 18th, 2009. Our LOA certifies our process quality assurance, data quality requirements (DQR) and continuous process improvement criteria. AeroNavData welcomed and fully supported the US Navy’s requested audit our FAA Type 1 Letter of Acceptance (LOA) aeronautical navigation data process.
Upon successful conclusion of the audit, the US Navy’s PMA-209 office certified our process and summarized the audit process and its findings with regard to our aeronautical navigation data process in a formal letter of compliance, dated Dec 22, 2014.
Data Quality Requirements (DQR)
A DQR provides clear and unambiguous requirements for the development and maintenance of tailored navigation data. The agreement certifies that the Data Quality Requirements (DQRs) meet the requirements for the data’s intended function. A formal Data Quality Requirements (DQR) agreement between the customer and AeroNavData’s coding team is mandatory in the FAA’s Type 1 Letter of Acceptance (LOA)* compliance plan. AeroNavData leads the development of this DQR by coordinating with the involved military departments to ensure their specific requirements were properly captured and were compatible with the LOA Type 2 DQR*.
Coding and Validating Instrument Flight Procedures
To include the US Military’s Office of Primary Responsibility (OPR) Procedures within our navigation database, AeroNavData would perform a robust series of steps to code and validate the needed procedures.
These steps include our certified capability to:
- Perform a source review and analysis of all FAA, Air Force, Army, and Navy procedure source. In the event of a missing, errant, or conflicting source, AeroNavData contacts the source organization to resolve the discrepancy.
- Verify and input all supplemental aeronautical information used in the design of each procedure.
- Code the procedures using ARINC and DAFIF procedure standards.
- Perform a quality check on all supplemental and procedure data.
- Utilize DO-200 qualified tools to ensure the quality coding of all supplemental and procedure data.
- Code procedures in compliance with the FAA AC 20-153, and FAA Type 1 LOA process for delivery to the Type 2 LOA Holder FMS vendors for FMS navigation use.
ARINC 424 Data File
AeroNavData has the processes in place and the full capability to deliver, on a 28-day cycle, an ARINC 424 navigation database data file of all of the US FAA OPR procedures and the required military OPR procedures based on the criteria in ARINC 424 Data File Requirements.
Letters of Acceptance for Navigation Data Providers
* Type 1 LOA
This Letter of Acceptance is granted when a Navigation Data supplier is formally audited and found to comply with EUROCAE ED-76 or RTCA DO-200A documents and with no identified compatibility with any specific aircraft system. A Type 1 LOA designation confirms that the processes for producing navigation data comply with all documented Data Quality Requirements. A Type 1 LOA Navigation Data provider may not release navigation databases directly to end users. They must only release data that will be used for navigation of flight to a certified Type 2 LOA holder.
* Type 2 LOA
This Letter of Acceptance is granted when a Navigation Database supplier complies with EUROCAE ED-76 or RTCA DO-200A documents and provides data compatible with specified avionics system(s).
A Type 2 LOA confirms that the processes for producing navigation data comply with all required conditions and with the documented Data Quality Requirements for specific avionics systems. The Data Quality Requirements must be provided by or agreed with the specified equipment design organization in accordance with a formal arrangement. A Type 2 LOA may release navigation databases directly to end users.
A Type 2 LOA holder may interface directly with data originators (such as State AIP providers and operators) or may use data supplied by a Type 1 LOA, in which case interfaces with data originators may not be necessary.