Universal Avionics eNews
 
Sign Up to Receive the Universal Avionics eNews
 
Share: 

Discussing Missing Database Information

Jan 27, 2017
By: Mike Michalski, Pilot Instructor - Customer Training

Mike Michalski, Pilot InstructorAs more procedures are being added to digital navigation databases, the number of questions are rising correspondingly when certain procedures or waypoints are not present in the Flight Management System (FMS). There are several tools available on our website to help answer some of these questions, which I’ll walk you through in this article. In addition, I’d like to share some explanations of why certain procedures, leg types or waypoints are not included.

The first place to start your search is under the Navigation Database FAQ or Notice & Alerts pages. The Notices & Alerts lists all of the current Jeppesen alerts as well as the Universal Avionics notices for those alerts, and NavTech database bulletins. Additionally, SIDs and STARs not included in the database are also listed under the Universal Avionics Notices for Jeppesen Alerts with an explanation that the FMS memory limit on SIDs and STARs is 99 of each per airport. Therefore, any number over that will be excluded based on customer input.

To learn what procedures are in your database, visit the Navigation Databases. Under the “Request Your Subscription” section, select the appropriate Software Control Number (SCN) version and a page allowing you to view Contents, What’s Not Included, Coverage, etc. will appear – shown below.

Navigation Databases Tabs for Contents, What's Not Included, Coverage, etc.

The following are several other reasons why a waypoint, procedure or leg may not appear in your database.

SID or STAR with vector leg only will be excluded

SID or STAR with vector leg only will be excluded

No Common Point on SID or STAR will exclude that procedure

No Common Point on SID or STAR will exclude that procedure

Turn Point Fixes are only in SCN 802 and later

Turn Point Fixes are only in SCN 802 and later

DME Arc-to-Fix Leg exceeding 300° excludes that transition

DME Arc-to-Fix Leg exceeding 300° excludes that transition

Different descent angles before and after FAF excludes approach

Different descent angles before and after FAF excludes approach

Unsupported procedure identifiers such as VOR DME instead of VOR DME-A will be excluded

Unsupported procedure identifiers such as VOR DME instead of VOR DME-A will be excluded

No VOR within 40nm of NDB approach will exclude transition

No VOR within 40nm of NDB approach will exclude transition

Named waypoints along Arc-to-Fix track will display as radials

Named waypoints along Arc-to-Fix track will display as radials

Computer Navigation Fixes (CNF) are created when there are no state provided identifiers. Jeppesen will create and include these in square brackets.

Computer Navigation Fixes (CNF) are created when there are no state provided identifiers.

Other reasons you might check for “missing” data include

  1. Procedure excluded by NOTAM.
  2. Resurveyed runways may take more than one database cycle to be re-included.
  3. Approach type not supported by Universal Avionics (LDA, SDF, pre-Software Control Number (SCN) 802 Circle-to-Land only LOC or BC-LOC approaches).
  4. Approach step-down fixes inside FAF in pre-SCN 802 will not appear.
  5. Approaches using True Headings are only available in our 802w2t or 1000w2t database versions.
  6. Any procedure or transition with a Precision Arc (RF) Leg is excluded from the Standard database (non-RF database). An RF database is available to those operators whose aircraft meets the compliance requirements. Operators currently subscribing to an "Approval Required" database will have all RF leg procedures.
  7. Finally, one of the most common mistakes when loading a destination airport is to select the waypoint of the same name and location instead of the airport.  This results in no destination procedures being available for selection. One example of this follows.
One of the most common mistakes when loading a destination airport is to select the waypoint of the same name and location instead of the airport.

If all else fails, contact Universal Avionics Database Technical Support (not Subscription Support) with the following information; SCN, database subscription part number (P/N), airport identifier, instrument procedure/transition, missing waypoint, etc. and a brief description of the problem.

Technical Support
Tel: 520-573-7627 or 800-595-5906
Fax: 520-295-2384
Email Customer Support

Leave a comment