Universal Avionics documents problems reported during database processing and how they were resolved, and problems found with the data after delivery. This information is updated every database processing cycle, or when a change occurs.
Universal Avionics receives navigation data from multiple data suppliers: specifically, Lufthansa Systems GmbH & Co. KG (Lufthansa Systems), Jeppesen Sanderson, Inc (Jeppesen), NAVBLUE Limited (NAVBLUE), and AeroNavData, Inc (AeroNavData).
Databases purchased directly from Universal Avionics are created with Lufthansa Systems supplied data, unless otherwise noted.
Databases created with NAVBLUE source data are purchased through NAVBLUE. These include part numbers 802-N2, 802-N4, 802-NH, 802-NAB2, 802-NRF, 1000-N2, 1000-N4, 1000-NH, 1000-NAB2, and 1000-NRF.
Please select the appropriate alerts page for your database part number.
Databases created with Lufthansa Systems supplied data are purchased through Universal Avionics. Alerts on this page pertain only to Lufthansa Systems databases.
Universal Avionics documents problems reported during database processing and how they were resolved, and problems found with the data after delivery. This information is updated every database processing cycle, or when a change occurs.
As the holder of a Type 1 Service Provider Certificate, Lufthansa Systems is required by regulatory agencies to report data modified by Lufthansa Systems to end users. The notification of data alteration is included in the Lufthansa Systems Release Statement.
For all Lufthansa Systems Flight Safety Alerts and Nav Data Addendums see Lufthansa Systems page.
Kagoshima (RJFK)
Cycle: 2213
Read Alert Details
Montevideo, Uruguay
Montevideo Carrasco Intl/Gen C L Berisso (SUMU)
Cycle: 2211 & 2212
Corrected in Cycle 2213 Lufthansa Systems source data.
Read Alert Details
Alerts in this section pertain only to the Jeppesen-sourced databases. Databases created with Jeppesen suppled data are purchased directly from Universal Avionics. These include part numbers 1344-*, 1350-*, 604-*, 801-*, 802-JB2, 802-JW4, 802-JZA, 1000-JW2, 1000-JW4, 1000-JW5, 1000-JH, 1000-JAR, 1000-JRF, 1000-FLTIN, 1000-C2, 1000-JZA, 1000-WJE, and 1000-NVC.
Universal Avionics documents problems reported during database processing and how they were resolved, and problems found with the data after delivery. This information is updated every database processing cycle, or when a change occurs.
As the holder of a Type 1 LOA, Jeppesen is required by regulatory agencies to report Jeppesen Modified Data to end users. The listing of Jeppesen Modified Data is provided in the UniNet portion of our website. All data modified by Jeppesen should be considered fit for aeronautical use.
For all Jeppesen NavData Change Notices and Jeppesen NavData Alerts see Jeppesen's Notices and Alerts page.
Databases created with NAVBLUE data are purchased through NAVBLUE. These include part numbers 802-N2, 802-N4, 802-NH, 802-NAB2, 802-NRF, 1000-N2, 1000-N4, 1000-NH, 1000-NAB2, and 1000-NRF. Alerts in this section pertain only to the NAVBLUE-sourced databases.
Universal Avionics documents problems reported during database processing and how they were resolved, and problems found with the data after delivery. This information is updated every database processing cycle, or when a change occurs.
As the holder of a Type 1 DAT certification, NAVBLUE is required by regulatory agencies to report data modified by NAVBLUE to end users. The notification of data alteration is included in the NAVBLUE Statement of Conformity.
NAVBLUE Bulletins are also available on the NAVBLUE Customer pages.
Cycle: 2211 & 2212
Databases created with AeroNavData data are purchased through Universal Avionics. Special Notices in this section pertain only to the AeroNavData-sourced databases.
Universal Avionics documents problems reported during database processing and how they were resolved, and problems found with the data after delivery. This information is updated every database processing cycle, or when a change occurs.
As the holder of a Type 1 LOA, AeroNavData is required by regulatory agencies to report data modified by AeroNavData to end users. AeroNavData provides an Altered Data Report when alterations have been made within the ARINC cycle. The list of alterations can be reviewed in the Altered Data Report posted below.
For all AeroNavData Special Notices see AeroNavData Special Notices page.