ADSB Specials

Special deals

on ADSB

Installations

(07) 4634 6355

Jeppesen Aviation Notices & Alerts Australia

This page displays a news feed of all current Jeppesen Aviation Notices and Alerts for the Australian region.

A full listing of Jeppesens "worldwide" aviation notices and alerts can be found on the Jeppesen website by clicking here...

 


 

Jeppesen Notices & Alerts feed for Aviation
  1. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  2. The Notice files on these pages are current as of the revision date shown on each page. Always consult all available published Notice information and ask for other pertinent Notices prior to flight.

    Regions:
    Australia (all subregions)
    Pacific Basin - Indonesia, Malaysia, New Guinea, Southeast Asia

  3. The Notice files on these pages are current as of the revision date shown on each page. Always consult all available published Notice information and ask for other pertinent Notices prior to flight.

    Region:
    Australia (all subregions)

  4. NavData Alerts are designed to inform commercial NavData subscribers, including airlines, avionics companies, and aviation service providers, of changes and errors to databases issued by Jeppesen. Alerts are not designed for individual pilot notification but are intended to supplement the NavData Notices by disseminating time critical information that could have a significant impact on flight operations. Alerts contain safety-of-flight information including, but not limited to, incorrect turn directions, altitudes, airway changes, and SID/STAR/Approach procedures. This information typically affects Jeppesen's master database, and as a result, can impact any Jeppesen NavData customer or user of avionics databases derived from Jeppesen NavData. Often the posting of an Alert is the result of late or incorrect aviation information provided by government civil aviation authorities, the c

    Regions:
    Australia (all subregions)
    Pacific Basin - Aleutian Islands, Indonesia, Malaysia, New Guinea, New Zealand, Southeast Asia

  5. The Notice files on these pages are current as of the revision date shown on each page. Always consult all available published Notice information and ask for other pertinent Notices prior to flight.

    Regions:
    Australia (all subregions)
    Pacific Basin - Indonesia, Malaysia, New Guinea, Southeast Asia

  6. The Notice files on these pages are current as of the revision date shown on each page. Always consult all available published Notice information and ask for other pertinent Notices prior to flight.

    Region:
    Australia (all subregions)

  7. Jeppesen delivers Multiple Approach Indicator Procedures to our customers. A Multiple Approach Indicator Procedure is one which has a special designator such as a Y or Z in the approach title; for example, RNAV (GPS) Z Rwy 22. However, not all avionics equipment is able to accept these added procedures. If your avionics equipment cannot handle a Multiple Approach Indicator, it will contain one of the procedures without the Multiple Approach Indicator; for example, RNAV 22. In most cases the first procedure (A or 1) will be contained in your database when A, B, C or 1, 2, 3 designators are used. When the X, Y, Z designators are used, the last procedure (Z) will normally be contained in your database. Yet, in other cases where an RNAV RNP (AR) or an RNAV (GPS) procedure with 'LPV only' or ¿LP only¿ minimums is designated as the Z procedure, we will include the Y, X, etc. procedure

    Regions:
    Worldwide

  8. Currently you are receiving Terminal NDB/Locators and Airports in your file. However, you may be receiving Airports that are outside of your Airport parameters.These extra Airports are extracting as supporting data for the Terminal NDB/Locators in your file and this supporting data logic bypasses any Airport parameter settings for you file, such as minimum runway length. To correct this anomaly, Jeppesen will implement an optional ¿Link to Airport¿ parameter, which will only extract Terminal NDB/Locators for airports that meet your specified Airport parameters. Once implemented, this new parameter will be activated and you will see a drop in Terminal NDB/Locators along with the Airports that do not meet your specified Airport criteria.

    Regions:
    Worldwide

  9. Beginning in AIRAC cycle 1911, Jeppesen will begin extracting the Runway Accuracy Compliance Flag into column 99 and the Landing Threshold Elevation Accuracy Compliance Flag to column 100 on the Runway Primary Record (PG) 4.1.10.1.

    Regions:
    Worldwide

  10. Jeppesen has identified an issue where some Airspace Upper and Lower vertical limits displayed in the Object Details dialogue box are incorrect. The Vertical Limits are incorrect only when either the Upper or the Lower limit is NOTAM or UNK (unknown). This issue exists for both Special Use Airspace and Controlled Airspace worldwide. The corresponding Airspace Upper and Lower vertical limits displayed in the Enroute graphic display are correct and should be used as the primary reference. This issue only exists when using FliteDeck Pro X. This issue affects no other FliteDeck Pro version or any other Jeppesen Electronic Enroute Charting application. Graphic images of a sample Restricted Area and its vertical limits in both the Enroute Graphic (correct limits) and corresponding Object Details (incorrect limits) are provided in the pdf attached to this alert. Jeppesen is actively workin

    Regions:
    Worldwide

  11. Due to database packing constraints the following baseline limits have been set for the respective databases mentioned below. The data below is not a change but only mentioned for clarity of information. DTRM97 - Worldwide Equipment - Approach +2000, 2100, 2101 I/O Main Area Codes - USA LAM CAN SAM EUR ENRT and TERM WP - RCW All SID STARS with RWY limits shorter than 11000 ft were removed All APCH with RWY limits shorter than 6000 ft were removed This will be in effect beginning cycle 1907, effective June 20, 2019. We apologize for any inconvenience this may cause FreeFlight Systems

    Regions:
    Worldwide

  12. This Customer Notice is intended to update and further explain the concerns raised to customer¿s attention in the Customer Notice of Dec 21, 2018 regarding spot elevations in the FliteDeck Application suite. To address the concerns raised with the mis-interpretation of spot heights Jeppesen will be removing all spot elevations from the FliteDeck Application suite, which includes the following: ¿     FDPX ¿     FD Pro 3.x ¿     FD Pro 9.x ¿     Foreflight Mobile ¿     Airbus LPC-NG Reference the attached pdf for complete information concerning this Customer Notice.

    Regions:
    Worldwide

  13. Avidyne has become aware of an issue with the navigation database that will cause the avionics to show the incorrect missed approach procedure for some approaches.  The issue will occur in database cycles 1901 through 1906.  The list of affected airports/approaches is below.  The listed approaches must not be used in either Release 9 or IFD-series equipment.  Starting with cycle 1907, the listed approaches will once again be usable. Airport ID Approaches   Airport ID Approaches BGJN NDB/DME 07   KFCM ILS 10R CJA3 RNAV 10, RNAV 18 RNAV 28   KGYY ILS 30 CJS7 RNAV 08, RNAV 26   KHGR RNAV 09, RNAV 27 CTN6 RNAV 35   KINL ILS 31 EFHK ILS 04R   KLGA ILS 13, ILS 22 EGDY ILS 26   KMKT ILS 33 EGOS ILS 18, VOR 05, VOR 18 VOR 23, VOR 36   KMNV RNAV 23 EHAM ILS 22   KTEB ILS 06 E

    Regions:
    Worldwide

  14. Beginning in AIRAC cycle 1911, Jeppesen will begin extracting the SBAS Final Approach Course into columns 62 through 65 on the Path Point Continuation Record (PP) 4.1.28.2 for fixed wing approach procedures. The Helicopter Procedure course will continue to be extracted into columns 72 through 74 on the Path Point Continuation Record (PP) 4.1.28.2 for helicopter approach procedures.

    Regions:
    Worldwide

  15. Jeppesen receives aeronautical source that contains airways designated for use by helicopters only. Previously, Jeppesen did not offer this type of data. ARINC 424 field definition 5.7 contains a Route Type code of ¿H¿ which is used to designate segments of an airway (ER) record that is intended for helicopter usage. Jeppesen will begin offering route type of ¿H¿ within (ER) records as an option beginning with AIRAC cycle 1905. If your flight management system is able to accept this route type, you will have the option to start receiving this data on (ER) records.

    Regions:
    Worldwide

  16. AFFECTED PRODUCTS Navigation systems listed below using the International Database (Garmin AT P/N 138-0426 or Jeppesen P/N DGAT13) are affected. ¿ GX50, GX55, GX60, GX65 units ¿ Model 2101 Navigation Management Systems See attached PDF

    Regions:
    Worldwide

  17. The following is an update to the Notification published on 31 October 2018. In accordance with EASA Requirements, Jeppesen will begin providing a Statement of Conformity with each NavData database.  This document serves as the required advanced notification for implementation of the updated requirements beginning in AIRAC cycle 1902, effective date 31 January 2019. See Attachment for detailed information.

    Regions:
    Worldwide

  18. GE Aviation Systems LLC (GEAS) has recently implemented the ability to filter Authorization Required (AR) procedures from the NDB.  Effective with cycle 1902, effective 31 January 2019 and beyond GEAS will begin removing RNP AR procedures from NDBs unless we receive a request to retain them in your NDB.  This change affects RNP AR SID, STAR and Approach Procedures.  Therefore, please contact Jeppesen using the contact information below if you wish to retain RNP AR Procedures in your NDB.  See Attachment for detailed information.

    Regions:
    Worldwide

  19. Genesys Aerosystems has discovered an obstruction database production issue that required filtering (removing) all obstructions with a height of less than 175 ft from the source obstruction data in Cycle 1810. Obstructions lower than 175 ft in height will not be shown in the above products and will therefore not generate associated TAWS alerts when the products are updated to Cycle 1810. In the previous database release, obstructions lower than 150 ft were not included in the database. This new height filter will remove more obstructions from the database. Genesys Aerosystems is taking action to correct these issues in future Obstruction Database cycles. If you have any questions concerning this database alert, please contact  (817) 215-7600.

    Regions:
    Worldwide

  20. Genesys Aerosystems has discovered an obstruction database production issue that required filtering (removing) all obstructions with a height of less than 150 ft from the source obstruction data in Cycle 1809. Obstructions lower than 150 ft in height will not be shown in the above products and will therefore not generate associated TAWS alerts when the products are updated to Cycle 1809. In previous database releases, obstructions lower than 100 ft were not included in the database. This new height filter will remove more obstructions from the database. Genesys Aerosystems is taking action to correct these issues in future Obstruction Database cycles. If you have any questions concerning this database alert, please contact  (817) 215-7600.

    Regions:
    Worldwide

  21. Jeppesen now has the ability to update Enroute Navigational Data for FliteDeck Pro iOS v3.0 and higher as well as Windows v9.0 and higher outside of the normally scheduled 28-day updates. Previous cycle Enroute data can now be updated, reprocessed and redelivered and will be available for download within the FliteDeck Pro application versions mentioned.

    Regions:
    Worldwide

  22. Jeppesen now has the ability to update Enroute Navigational Data for FliteDeck Pro iOS v3.0 and higher as well as Windows v9.0 and higher outside of the normally scheduled 28-day updates. Previous cycle Enroute data can now be updated, reprocessed and redelivered and will be available for download within the FliteDeck Pro application versions mentioned.

    Regions:
    Worldwide

  23.   Genesys Aerosystems has discovered a NavData production issue that excluded certain terminal fixes associated with three airports from Cycle 1803 in the World NavData coverage (including Captstone and REGA tailored NavData). The affected terminal fixes will not appear when performing a ¿NRST FIX¿ search or when directly entering the fix identifier. Additionally when viewing the moving map, the affected terminal fixes will not be shown if a procedure containing the fix is not loaded into the active flight plan. The affected terminal fixes are still fully encoded in the associated procedures below. Thus, if guidance to an affected fix or information on an affected fix is needed, first load one of associated procedures into the active flight plan. The fix will then be fully functional from within the associated procedure, viewable on the moving map, and available to other FMS functions.

    Regions:
    Worldwide

  24.   Previously, Jeppesen did not support the Supporting Facility information in columns 103-110 of the Airport/Heliport Localizer and Glide Slope (PI) record 4.1.11.1. Now, Jeppesen can supply the Supporting Facility information on a requested basis.

    Regions:
    Worldwide

  25.   Jeppesen receives Aeronautical source that contain runway surface type information. ARINC 424 5.302 has defined many of the surface types using a 4 character code. Jeppesen will start extracting the Runway Surface Type and associated Runway Surface Code 5.249 values as part of the Runway Continuation record. Jeppesen receives Aeronautical source that contains runway starter extension length information. Jeppesen will start extracting the starter extension length into the ARINC 424 5.312 Starter Extension field. Jeppesen also receives Aeronautical source that contain runway treatment and runway restrictions information. The treatment and restrictions information will be extracted in the notes field of the Runway Continuation record.

    Regions:
    Worldwide

  26.   Jeppesen has used FC-CF leg combination on the last leg of approach transitions to a localizer based procedures when the last leg was greater than 8nm, reference ARINC 6.3.6.5. Due to issues caused by the magnetic variation differences between VORs and Localizers being used as recommended navaids, for these legs, Jeppesen has decided to code a TF leg verses FC-CF on the last leg of an approach transition to a Localizer based procedure. Jeppesen will only code FC-CF leg combination when VOR and Localizer have the same magnetic variation.

    Regions:
    Worldwide

  27.  If an airport having greater than 200 charts is entered into the Electronic Chart Application, Destination or Alternate Airport fields (most typically via auto-population from the FMS flight plan), or directly via the Other Airport field, the Chart feature may become unavailable or contain reduced information. See attached for more details.

    Regions:
    Worldwide

  28.   Jeppesen receives ILS or LOC approach procedures from Air Navigation Service Providers (ANSPs) that contain approach transitions and missed approaches using RNAV procedure design criteria.  These procedures have transitions that are RNAV waypoints based and are meant to be coded using TF path and terminator legs.  These procedures contain various notes stating GNSS or GPS required.

    Regions:
    Worldwide

  29.   Jeppesen will begin offering additional VFR Airports/Heliports previously not available in Jeppesen NavData.  This document serves as the contractually required advanced notification for the availability of additional VFR Airports/Heliports, which is scheduled for implementation in AIRAC cycle 1707, effective date 22 June 2017.

    Regions:
    Worldwide

  30.   Jeppesen will begin offering additional Airport Communication Types, Enroute Communication Types (5.101), and Service Indicator codes (5.106). This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1611, effective date 13 October 2016. See PDF for details.

    Regions:
    Worldwide

  31.   Jeppesen receives Aeronautical source that contains Conventional Visual Approaches and (CVFPs). Jeppesen was providing some of these procedures as RNAV Visual Approaches. Jeppesen will continue providing published RNAV Visual Approaches but will potentially no longer provide Conventional Visual Approaches and (CVFPs) as Standard RNAV Visual Approaches.  Jeppesen will continue to offer these procedures as Tailored data.

    Regions:
    Worldwide

  32.  Garmin G900X, G950, G1000, Cirrus PerspectiveTM, and Embraer ProdigyTM Integrated Avionics Systems with GDU software versions 15.09 and earlier using the Worldwide Navigation Database are affected. Garmin G2000, G3000, G5000, and Embraer Prodigy Touch Integrated Avionics Systems with GDU software version 6.49 and earlier using the Worldwide Navigation Database are also affected. Additionally, all Garmin GTN 6XX/7XX, GNS 400W/500W, and G500/600 systems using the Worldwide Navigation Database are also affected See attached

    Regions:
    Worldwide

  33.   In order to uniquely identify terminal procedures that have been designated as Special Use or Restricted Use, Jeppesen will offer a Special Indicator field ¿L¿ in the Airport SID/STAR/APP Primary Extension Continuation Record. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1606, effective date 26 May 2016. 

    Regions:
    Worldwide

  34. For users running Mobile FliteDeck 2.7 and FliteDeck Pro 2.5.7, a taxi chart for a location along your route may display in flight if GPS signal is lost. In this event, the terminal chart library and any pre-selected charts will also be reset for origin and destination locations. Mitigation ¿ Please disable ¿Show Taxi On Landing¿ to mitigate the risk of an unexpected switch to a taxi chart and reset your origin and destination terminal chart library. In the event that a taxi chart does display unexpectedly and the terminal chart library resets, disable ¿Show Taxi On Landing¿ and re-select the charts for that location. The ¿Show Taxi On Landing¿ setting can be disabled by tapping the Settings icon within the app in the upper-right corner. See also attached PDF for graphic example.     

    Regions:
    Worldwide

  35.   A NavData Notice was issued in cycle 1408, effective 03 July 2014, as notification of the change to ILS procedure coding.   That change included coding a missed approach fix at the Missed Approach Point/DA(H), instead of the runway fix.   When state source for an ILS procedure indicates a missed approach turn prior to the runway, a missed approach fix may be coded at the Missed Approach Point/Decision Altitude (Height)/DA(H).   A result of having a missed approach fix coded at the Missed Approach Point/DA(H) is that the ILS procedure may not appear in some systems due to software limitations which will not allow a missed approach fix other than the runway on an ILS procedure.  In those cases where the ILS is removed, a Localizer procedure will be available for that runway.

    Regions:
    Worldwide

  36.  Incorrect CDI indications on some WAAS approaches

    Regions:
    Worldwide

  37.  Incorrect CDI indications on some SBAS approaches

    Regions:
    Worldwide

  38.   In the past, Jeppesen has provided helicopter LPV or LP procedures to heliports as PF records with an ident of Rxx, xx being a runway ident. Jeppesen also provided a PG record to support the procedure with an ident Rxx.  Beginning with cycle 1508, Jeppesen will  provide Helicopter LPV or LP to heliports with an ident of Rxxx, xxx being the source provided final approach course.  Jeppesen will no longer provide PG records to support the LPV or LP procedures.

    Regions:
    Worldwide

  39. In October 2014, Jeppesen announced our intentions to change how we code helicopter LPV or LP procedures to heliports for both our Standard and By Request Formats.  In order to support some of our customers who have not completed the changes necessary to support this new way of coding helicopter approaches, we have decided to delay the implementation until further notice.    Jeppesen will notify our customers through a revised Notice once we determine a new implementation date.

    Regions:
    Worldwide

  40.   Jeppesen receives aeronautical source with named and unnamed RNAV step down fixes (also known as along-track-distances).  Up to now, Jeppesen has only been able to deliver one waypoint description code ¿S¿ for all step down fixes coded on Approach records (PF and HF). Many governments issue RNAV (GNSS) procedures with unnamed RNAV step down fixes. On request from some controlling governments, these unnamed fixes are currently not coded in Jeppesen NavData due to our inability to clearly indicate their status. To resolve this issue and be able to capture these unnamed RNAV fixes, Jeppesen will implement the waypoint description codes for named and unnamed RNAV step down fixes as introduced in ARINC version 14 and supported by ARINC version 19, section 5.17.

    Regions:
    Worldwide

  41. Jeppesen has discovered an abnormality affecting the display of text elements of charts and pages contained in the Terminal Chart content of the EFB applications listed above. The result is that, in rare cases, text elements and labels might not be positioned properly. The effects vary based on the relative complexity of a chart. In some cases, text elements or labels might be spaced unevenly or possibly extend beyond a chart¿s border lines. In other situations text elements might touch or overprint adjoining text or symbols. Overprinting is most evident when text, symbols or lines are located in close proximity to one another. In rare instances, some overprinted text elements may be unreadable. Jeppesen has identified the root cause and is working with urgency to resolve the issue in each of the affected applications.  A remedy has been identified and

    Regions:
    Worldwide

  42.  In an effort to remove display congestion in the vicinity of airports and to address obstruction display errors in earlier software versions, Genesys Aeroystems is implementing a filter to remove shorter obstructions from the obstruction database.   See PDF for more information

    Regions:
    Worldwide

  43. Within some versions of Mobile FliteDeck, FliteDeck Pro and Boeing Class 3, SID or STAR flight tracks (depicted in the enroute application as a dashed line) may be incorrectly displaying multiple and/or overlapping tracks. Jeppesen is working toward a resolution to this issue for inclusion in a future release. As a reminder, the enroute application included within FliteDeck and EFB products currently depict SID/STAR flight tracks for use as general reference only for flight planning and/or situational awareness purposes. Pilots should always refer to the applicable SID or STAR procedure chart(s) for comparison and cross-reference purposes. Always use the applicable SID or STAR chart, in its complete form, when flying any procedure. THEREFORE, USE CAUTION WHEN VIEWING SID OR STAR ROUTE DEPICTIONS WITHIN YOUR ELECTRONIC ENROUTE APPLICATION, AND ALWAYS REFER TO APPLICABLE SID OR STAR CHA

    Regions:
    Worldwide

  44.   In accordance with ARINC 424 ¿ 20 documentation, Jeppesen will offer ILS procedures, where the published missed approach requires a turn prior to the Runway. This document serves as the contractually required advanced notification for implementation of these ILS procedures. The ILS procedures will be available beginning cycle 1408 effective 24 July 2014.

    Regions:
    Worldwide

  45. Within some versions of the electronic Enroute application, in some instances the function which provides the means to overlay SID or STAR flight tracks as general reference may be omitting the Navaid, Intersection or Waypoint which defines the point where a Runway Transition is joined to a corresponding Enroute transition (or vice versa). In these instances the result is an incorrect display of the flight tracks for the Runway and Enroute Transitions. Within the Enroute application the depiction of SID/STAR flight tracks is intended for use as general reference only for flight planning and/or situation awareness purposes. Pilots are reminded of the need to refer to the applicable SID or STAR procedure chart(s) for comparison and cross-reference purposes. Always retrieve and use the applicable SID or STAR chart, in its complete form, when flying the procedure. The problem will be correc

    Regions:
    Worldwide

  46.  Jeppesen will begin offering a GPS/FMS phase indicator of ¿L¿ identifying the Localizer procedure as having been systematically cloned from an ILS procedure. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1403, effective date 03 April 2014

    Regions:
    Worldwide

  47.   In accordance with ARINC 424 documentation, Jeppesen will begin providing NDB and/or VOR procedures with an NDB or VOR as the recommended navaid on approach transitions and missed approach. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1403, effective 06 March 2014.

    Regions:
    Worldwide

  48.   In accordance with ARINC 424 supplement 20, and a change that was accepted at an ARINC NDB working group meeting in Phoenix, AZ (2012)  , Jeppesen will begin coding RNP SAAAR/AR SID¿s and STAR¿s. This implementation will include the use of the Qualifier 1 code of RNP SAAAR/AR -¿F¿ for both the SID (PD,HD) and the STAR (PE,HE) records.This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1404, effective date 03 April 2014.

    Regions:
    Worldwide

  49. Jeppesen has identified an issue related to some of the devices running FliteDeck Pro for iOS. These devices may not display certain charts associated to a given airport when the chart unpacking process is interrupted or canceled. Pilots are encouraged to brief all required charts during a pre-flight to ensure all required charts for the flight are displaying properly. In the event a device is not displaying charts correctly, follow the steps below to repeat the chart download process.   On the affected device, tap on the Settings icon and select FliteDeck Pro along the left side. Toggle the Deactivation setting to ¿ON¿. Launch FliteDeck Pro and tap ¿Proceed¿ to complete the deactivation. Once complete, accept the terms and conditions and the application will automatically reactiv

    Regions:
    Worldwide

  50. Jeppesen produces certain charts with significant but temporary procedure or location changes. In order to ensure that these temporary charts are easy to find and readily identifiable, these procedures/locations are printed on yellow paper. Because of new digital printing technology, these colored sheets are being replaced with standard white background sheets with yellow vertical borders rather than a sheet with the all yellow background. The original objective to have these temporary sheets readily identifiable and distinguishable will still be met with the vertical yellow borders. The affected sheets will be replaced as the location and or procedure normally revises beginning with the revision dated 28 June or 5 July 2013 depending on the geographic coverage. As always, Jeppesen encourages the review of local NOTAMs for the most curr

    Regions:
    Worldwide

  51. Jeppesen produces certain charts with significant but temporary procedure or location changes. In order to ensure that these temporary charts are easy to find and readily identifiable, these procedures/locations are printed on yellow paper. Because of new digital printing technology, these colored sheets are being replaced with standard white background sheets with yellow vertical borders rather than a sheet with the all yellow background. The original objective to have these temporary sheets readily identifiable and distinguishable will still be met with the vertical yellow borders. The affected sheets will be replaced as the location and or procedure normally revises beginning with the revision dated 28 June or 5 July 2013 depending on the geographic coverage. As always, Jeppesen encourages the review of local NOTAMs for the most curr

    Regions:
    Worldwide

  52.   Jeppesen will begin providing Visual Approaches in accordance with ARINC 424 ¿ 20 as RNAV Visual Approaches. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1305, effective 02 May 2013.

    Regions:
    Worldwide

  53. AFFECTED PRODUCTS GNS 480 (CNX80) Units with Software Version 2.1. DESCRIPTION The latest Aviation Database (1302) includes LP* approaches for the first time. While GNS 480 (CNX 80) Software Version 2.3 supports LP approaches, Software Version 2.1 does not. For customers with Software Version 2.1, LP approaches will appear as LPV approaches and will be selectable. If selected, the unit will annunciate ¿LPV¿ in amber while on the approach; however, one minute out from the FAF the approach will downgrade to LNAV. PILOT ACTION Garmin recommends upgrading 480 (CNX80) Units to Software Version 2.3. Refer to Software Service Bulletin 0850 Rev C for instructions on updating to 2.3. *LP or Localizer Performance, is a newer procedure that uses WAAS to deliver the same high precisi

    Regions:
    Worldwide

  54. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  55.   AFFECTED PRODUCTS All Garmin Integrated Flight Deck Systems, G500/G600, GNS 400W/500W-series, and GTN-series navigation systems are affected.   PURPOSE   In some cases, published Standard Instrument Departures (SIDs) and Standard Terminal Arrivals (STARs) contain specific instructions within the Departure Route Description or arrival procedures that differ according to aircraft type, such as ¿JETS¿ or ¿ALL OTHERS.¿  In cases where more than one aircraft type-specific instruction is provided within the same procedure, only the ¿JETS¿ aircraft type-specific instructions are provided in the source data and encoded in the Navigation Database.  Therefore, the navigation system will only provide guidance information according to the JETS-specific instructions.  These instructions may differ significantly fr

    Regions:
    Worldwide

  56.   In accordance with Aeronautical Source documentation, Jeppesen has began including Speed Limits and Altitudes on RF Legs in our NavData.   This document serves as the contractually required notification of the data within Jeppesen¿s NavData.

    Regions:
    Worldwide

  57.  Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers.  Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  58.  Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers.  Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  59.  Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers. Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  60.  Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers.  Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  61. Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers.  Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  62.   Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers. Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  63.  Jeppesen distributes issues related to our products and services using several standard notification methods. One of these notification methods includes issuing time-critical information using Jeppesen Alerts. Until now, Jeppesen Alerts have been distributed through emails to the individually affected customers.  Additionally, Alerts are posted online at http://www.jeppesen.com under ¿Notices & Alerts.¿ Here you will also find RSS feeds, which are an efficient way to monitor the latest information from Jeppesen.

    Regions:
    Worldwide

  64.   As an enhancement to the November 2011 VFR reporting points NavData Notice, Jeppesen is now providing VFR Reporting Points as both VFR Enroute Waypoints (EA) and VFR Terminal Waypoint (PC).

    Regions:
    Worldwide

  65.   Jeppesen receives Aeronautical source that contains RNAV approaches with LP and LNAV level of service. Currently, Jeppesen is providing these RNAV approaches with only the LNAV level of service provided. Jeppesen will be updating our systems to  provide these procedures with LP and LNAV level of service. With the LP level of service, Jeppesen will also provide a Path Point (PP) record.  See PDF for more

    Regions:
    Worldwide

  66. In accordance with ARINC-424 version 18 documentation, Jeppesen will begin offering VFR reporting points as VFR Enroute Waypoints (EA). This document serves as the contractually required advanced notification for the availability of VFR waypoints, which is scheduled for implementation in AIRAC cycle 1113, effective date 15 December 2011.

    Regions:
    Worldwide

  67. Dear Aspen Avionics customers, Thank you for your patience. The 1109 databases for your Aspen EFD 1000, 500 are now available to download from JSUM. Jeppesen and Aspen Avionics have identified a solution and addressed the cause for the loading errors by modifying the navigational databases for Cycle 1109. Obstacles less than 200ft AGL have been removed.  We will continue to evaluate various options to better serve your navigational needs. We will notify you if any changes are made to EFD databases in the future. If you have any questions regarding your account, please don't hesitate to contact Jeppesen Customer Service. If you have any questions regarding JSUM, please contact Jeppesen PC Technical Support. Sincerely, Jeppesen

    Regions:
    Worldwide

  68. In accordance with ARINC 424, version 19 documentation, Jeppesen will begin providing new Route Types and Qualifiers for SID (PD, HD) / STAR (PE, HE) / Approach (PF, HF) records. This document serves as the contractually required advanced notification to offer the advanced data types.    This data will be available beginning in AIRAC cycle 1108, effective date 28 July 2011. See PDF for details

    Regions:
    Worldwide

  69. Jeppesen has implemented the capability to offer the localizer only portion of an ILS procedure as a stand alone localizer procedure when the ILS procedure contains glide slope out information.  This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1106, effective date 02 June 2011. See PDF for details

    Regions:
    Worldwide

  70. The Procedure Design Magnetic Variation as defined in ARINC 424, version 19, field definition 5.290 and 5.291 will be provided in columns 61 through 66 on the Jeppesen PD/HD, PE/HE, PF/HF Primary Extension Supplemental Record .   A ¿P¿ in column 66 will indicate Procedure Magnetic Variation for entire procedure.  An ¿L¿ in column 66 will indicate Procedure Magnetic Variation used for that leg only.  When a ¿P¿ for Procedure Magnetic Variation is present, only the first sequence of each approach transition and final transition will contain Magnetic Variation information. Details see PDF below.

    Regions:
    Worldwide

  71. In accordance with ARINC 424 documentation, Jeppesen will begin providing Procedure Threshold Crossing Height (TCH) data in the Jeppesen APPROACH Primary Extension Supplemental Record (PF/HF). This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 1106, effective date 02 June 2011. See PDF for details

    Regions:
    Worldwide

  72. In response to government source information, Jeppesen will begin coding RF path terminators on conventional (non-RNAV) procedures beginning in AIRAC cycle 1106, effective 02 June 2011.  This includes using a RF path terminator as the ending leg of a transition for all procedure types..   To minimize the impact to our customers, Jeppesen will provide the option to include or exclude terminal procedure transition(s) which contain a RF path terminator.  This new option will be in addition to the current option which allows you to exclude the entire procedure when it contains an RF path terminator anywhere in the procedure.   This new transition level RF path terminator extract option has been set to match your current procedure level RF path terminator extract setting.   This document serves as the contractually required

    Regions:
    Worldwide

  73. Jeppesen is receiving source that designates crossing altitudes as ¿At¿, ¿At or Above¿, ¿At or Below¿, and ¿At or Above to At or Below¿ on the first leg of the missed approach.  According to ARINC Attachment Five section 9.3.1.2 these are all valid options and will be coded as follows: ¿At¿ = (blank) ¿At or Above = (+) ¿At or Below = (-) ¿At or Above to At or Below¿ = (B)  

    Regions:
    Worldwide

  74. Jeppesen receives Aeronautical source with Time Zone corrections of -13 and -14 to Zulu (UTC).   Currently, the two new time zones apply to only to two locations, Phoenix Islands, Tonga and Kiribati Line Island as defined in the table below.  

    Regions:
    Worldwide

  75. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  76. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  77. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  78. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  79. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  80. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  81. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  82. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  83. Jeppesen's ongoing commitment to quality includes using various communication channels to disseminate the latest information that may affect Jeppesen products and services. Issues related to our products and services are communicated using one or more standard notification methods. This Bulletin provides a brief description of each of those notification methods.

    Regions:
    Worldwide

  84. See attached PDF for Tech Note 2010-02 Issued by Aspen Avionics on January 11, 2010 for more details.

    Regions:
    Worldwide

  85. Each time the GNS 480 (CNX80) is powered up, the unit loads the database from the datacard to its internal memory. Units with Software Version 2.1 or later allocate 30 MB of internal memory for this process. Units with Version 2.0 or earlier software allocate only 16 MB.   At this time the size of the GNS 480 (CNX80) database exceeds 15.5 MB and units with Version 2.0 or earlier software are utilizing more than 97% of the internal memory that is allocated for this purpose. The size of the database will exceed 16 MB with Jeppesen Database Cycle 1001 on January 7, 2010. When this occurs, units with Software Version 2.0 or earlier will not be able to load the database from the datacard to the unit¿s internal memory. When this happens, the operator will still be able to update the datacard normally, but when he or she returns the datacard to the unit, the unit will n

    Regions:
    Worldwide

  86. In accordance with ARINC 424 documentation, Jeppesen will begin offering GLS Approach records (PF) and GLS Navaid records (PT) as standard NavData. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices. See PDF below.  

    Regions:
    Worldwide

  87. GENERAL The purpose of this bulletin is to convey to our valued customers our current policy regarding the applications of chart and database changes based on state issued NOTAMs. The following is a summary of that policy and is specific to the processing of state issued NOTAMs only. BACKGROUND The ¿Notice to Airmen¿ (NOTAM) has been an integral part of the system for disseminating critical aeronautical information world wide for a very long time. Typically, NOTAMs publicize aeronautical information that is timecritical as well as temporary in nature. NOTAMs are also used when the information is not known sufficiently in advance to allow for chart publication and/or database extraction. NOTAMs communicate aeronautical information that has a direct impact on a pilot¿s flight preparation. It is for t

    Regions:
    Worldwide

  88. In accordance with ARINC 424 documentation, Jeppesen will begin providing DF/RF path terminator combinations within Terminal Procedure (PD/PE/PF/HE/HD/HF) records when supplied in source.  This document serves as the contractually required advanced notification for implementation of the new coding rules and practices.

    Regions:
    Worldwide

  89. In accordance with ARINC 424 documentation, Jeppesen will begin providing runway gradient data for runway (PG) records as documented in ARINC Specification 424, Section 5.212. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 0907, effective date 02 July 2009. If you want to receive runway gradients in the Runway record, please evaluate your systems to determine the impact of these changes. Make the appropriate adjustments to accept this new information by AIRAC cycle 0907, effective 2 July 2009,and contact your Jeppesen Business Representative. NavData Notices are intended for Jeppesen's Original Equipment Manufacturer (OEM) Customers only.  End Users of the data may contact their Avionics Providers with questions on the avail

    Regions:
    Worldwide

  90.   In accordance with ARINC 424 documentation, Jeppesen will begin providing a second Localizer/GLS identifier in the runway (PG) record. This document serves as the contractually required advanced notification for implementation of the new coding rules and practices scheduled for implementation in AIRAC cycle 0907, effective date 02 July 2009.  If you want to receive the second landing system in the Runway record, please evaluate your systems to determine the impact of these changes. Make the appropriate adjustments to accept this new information by AIRAC cycle 0907, effective 02 July 2009 and contact your Jeppesen Business Representative.  NavData Notices are intended for Jeppesen's Original Equipment Manufacturer (OEM) Customers only.  End Users of the data may contact their Avionics Providers with questions on the availability of

    Regions:
    Worldwide

  91. Many Grid Minimum Off Route Altitudes (Grid MORAs) are incorrectly displaying a value "-5o" in the electronic applications listed above, instead of the correct value of "UNK" (unknown). This value "UNK" reflects the fact that there is no altitude information available to enter in these data fields for that particular Grid MORA. The Grid MORAs with the incorrect values are generally located below S77° and above N85° (Antarctica and the Arctic Circle, respectively), however due to the fact that "UNK" Grid MORAs do exist all over the world, "-5o" appears in locations other than below S77° and above N85°. THEREFORE, WHEREVER THE VALUE -5o IS DISPLAYED, IT REPRESENTS AN UNKNOWN MINIMUM OFF ROUTE ALTITUDE FOR THAT GRID.

    Regions:
    Worldwide

Go to top