Jeppesen Symbols
Jeppesen Symbols
APCH-PL
APCH-PL
m m
ENRT-A ENRT-A
ENRT-L ENRT-L
ENRT-H ENRT-H
ENRT-H/L m
ENRT-H/L m
1343086330377
q$z
ENRT-A
m ENRT-L
ENRT-A ENRT-H/L
ENRT-L
ENRT-H
ENRT-H/L APCH-PL
m Offset Localizer
ENRT-A DME
ENRT-L
ENRT-H
ENRT-H/L
APCH-PL Markers
SID/STAR
APCH-PL TACAN
SID/STAR
When co-located, the marker symbol is cleared from the
associated waypoint or navaid.
APCH-PR
ENRT-A
ENRT-L
ENRT-H
ENRT-H/L
APCH-PL NDB/LOCATOR
SID/STAR
APCH-PR VOR/VORDME/VORTAC/NDB
APCH-PL
SID/STAR
ENRT-A
ENRT-L
ENRT-H/L Locator co-located with a Marker (LOM)
ENRT-A
ENRT-L
ENRT-H
APCH-PR ILS Glide Slope
ENRT-H/L
m
APT-PL NAVAIDS
q$z
1343086330377
APCH-PL
APT-PL
SID/STAR ENRT-A Oceanic Control Area,
ENRT-A Special Flight Rules Area (FAA) ENRT-L FAA Control Areas
ENRT-L ENRT-H
ENRT-H
ENRT-H/L
ENRT-A Air Defense Identification Zone
ENRT-A Class A Airspace ENRT-L
ENRT-L Control Area Extensions(Canada),Control Areas,
Military Terminal Control Areas, Transition ENRT-H
ENRT-H Areas(Canada), Terminal Control Areas, Upper ENRT-H/L
ENRT-H/L Control Areas
1343086330377
q$z
1401722561141
APT-PL Tetrahedron
APT-PL Trees
ENRT-A Airports
ENRT-L
ENRT-H
APT-PL Bluff ENRT-H/L
APT-PL Ditch
APCH-PL
ENRT-A
APT-PL Buildings
APT-PL Helicopter Landing Pad
q$z
1303320994000
APCH-PL Compulsory
SID/STAR APCH-PR Standard ALSF-II
ENRT-A
ENRT-L
ENRT-H
ENRT-H/L
ENRT-H/L APCH-PR MALSR
APCH-PL RNAV
SID/STAR Non-Compulsory
ENRT-A
ENRT-L APCH-PR SSALR
ENRT-H
ENRT-H/L
APCH-PL RNAV
SID/STAR Compulsory
ENRT-A
ENRT-L APCH-PR MALS
ENRT-H
ENRT-H/L
APCH-PL Mileage Break/CNF
SID/STAR Non-Compulsory Fix
ENRT-A APCH-PR MALSF
ENRT-L
ENRT-H
ENRT-H/L
APCH-PL Fly Over Fix
SID/STAR Indicated by circle around fix APCH-PR SALS
q$z
1401722561141
q$z
1329340968804
HEADING
1 — Chart number.
2 — Chart name.
3 — Jeppesen company logo.
4 — Chart scale.
5 — Chart region and type.
6 — Chart effective date.
7 — Chart revision date.
8— Chart Change Notice cross reference statement.
1297704888000
1343088774871
q$z
q$i
COVERAGE DIAGRAM
1297704888000
1343088774871
q$z
CHANGES
1297445655000
TABULATED DATA
1329508730203
q$z
1297445655000
REFERENCE NOTES
1329508730203
q$z
CRUISING LEVELS
1297704888000
RANGE SCALE
END PANEL
End Panels on Jeppesen Enroute Charts are primarily used for additional tabulated and reference information
which can not all fit on the Cover Panel.
CHART GRAPHIC
The contents of an IFR Enroute chart include information provided by official government source, as well
as, on rare occasion Jeppesen derived data. Charts are comprised of aeronautical data, cultural data,
hydrography and on some charts terrain data. 1343088774871
q$z
q$i
TENERIFE
NORTH
46 Los Rodeos
GCXO 2073-113
(*
C)
L)2
A(H/
q$z
1343088774871
1— VORDME. Low and High/Low charts include a Compass Rose with VHF Navaids. Shadow box
indicates navaid is airway component, with frequency, identifier, Morse code and INS coordinates.
Small "D" indicates DME/TACAN. Class indicated by: (T) Terminal, (L) Low, (H) High.
2— Airports - Location name, Airport name (if different than Location name), ICAO identifier, airport
elevation and longest runway length to nearest 100 feet with 70 feet as the dividing point (add 00).
"s" indicates soft surface, otherwise hard surface. IFR Airport in blue - Published procedures filed
under the location name. VFR airport in green.
3— Controlled Airspace. Limits add 00. When sectorized vertically, lower limit indicated by under bar, upper
limit indicated by over bar.
4— Special use airspace.
5— Grid Lat-Long values.
6— CTR. Asterisks are used in association with Class C, D and E airspace in the US only to indicate
part time operations, otherwise hours are H24.
7— ILS available at airport.
8— Magnetic Variation.
9— Area chart coverage.
10 — Directional MEAs.
11 — Minimum Crossing Altitude (MCA).
12 — Change to adjoining Enroute chart.
13 — DME.
14 — Grid MORA. Values 10,000 feet and greater are maroon. Values less than 10,000 feet are green.
Values are depicted in hundreds of feet.
15 — Gap in Nav Signal coverage.
16 — "D" indicates DME/TACAN fix. Segment mileage is DME/TACAN distance from navaid. Arrow without
a "D" designates a reporting point from facility.
17 — Non Compulsory RNAV Waypoint.
18 — High Altitude Route included on some low charts for orientation only.
19 — Changeover Point between two navaids.
20 — Intersection or fix formation (Bearing, frequency and ident of remote VHF or LF navaid).
21 — Met report required.
22 — Minimum Reception Altitude (MRA).
23 — VORTAC - High Altitude and off-route Navaids do not include a Compass Rose.
24 — Uncontrolled airway or advisory route.
25 — Route Suffix. D or F indicates ATC Advisory services only. F or G indicates Flight Information services
only.
26 — Enroute Communications.
27 — Total mileage between Navaids.
28 — Compulsory Reporting Point represented by screened fill. Non Compulsory Reporting point is open,
no fill.
29 — Holding pattern.
30 — FIR/UIR Boundary name, identifier and Airspace Class.
31 — Route usability by non B-RNAV equipped aircraft (within Europe only).
32 — Unnamed, official published ATS route with direction indication.
33 — Uncontrolled Airspace (Class F or G).
34 — GPS MEA.
35 — Minimum Obstruction Clea rance Altitude (MOCA).
36 — Conditional Route Category (See Enroute Text pages Europe).
37 — Airway Designator.
38 — Segment mileage.
39 — Maximum Authorized Altitude (MAA).
40 — CNS/ATM Equipment Requirement Boundary.
41 — Non Standard Flight Levels (Even Flight Levels in direction indicated).
42 — RNAV ATS route when not identified by designator (used outside Europe). 1329508730203
q$z
43 — Named or unnamed airspace fix or mileage break. Database identifiers are enclosed in square
brackets [ABROC]. They may be designated by the State (country) as Computer Navigation Fixes
(CNFs) or derived by Jeppesen. These identifiers should not be used in filing flight plans nor should
they be used when communicating with ATC; however they are also included in computer planning
systems. They are shown only to enable the pilot to maintain orientation when using charts in concert
with database navigation systems.
44 — Altitude Change.
45 — Route Minimum Off-Route Altitude (Route MORA).
46 — Direct Route (Requires ATC Approval, will not be accepted in Flight Plans).
47 — NDB.
48 — Communications related to Airport listed above Airport label. App/Arr, Dep, Twr and Gnd listed in Chart
tabulations. Asterisk indicates part time operation.
1329508730203
q$z
q$z
1303320940000
1303320940000
HEADING
1303327466000
1329502730348
q$z
BRIEFING INFORMATION
1— Indicates the service is part time. 5— All available primary frequencies are depicted.
2— SID/DP Initial Departure Control Services 6— Indicates that radar services are available.
or STAR Weather Services (e.g. ATlS) are 7— Airport elevation is provided for
depicted. Arrival/Departure airport.
3— Function of the service is shown when 8— Procedure restrictions and instructions.
applicable. Required equipment notes are prominently
4— Service call sign is shown when transmit and displayed.
receive, or transmit only ops are available. 9— Transition Level and Altitude.
The call sign is omitted when the service is
broadcast only or has a secondary function.
1303320940000
Tabulated Text boxes, which include a wide variety of actions, instructions, or restrictions for the pilot, have
certain common elements of design for SID, DP and STAR procedures.
1 — General identification applying to certain 3 — Textual description, which compliments the
sections of the procedure, such as Runway, graphic-based depictions or unique instructions,
Arrival or SID identification. that cannot be graphically represented.
2 — Segment of flight, such as Initial Climb, Routing, 4 — General restriction that cannot be incorporated
or Landing may be identified. in the graphic or that would enhance
understanding of procedure.
1329502730348
q$z
1303320940000
1303320940000
1303320940000
Unique lost communication instructions, provided by the governing authority for a procedure, are placed
within the graphic and are outlined by the lost communication boundary.
1303320940000
Speed restrictions vary widely within individual procedures. They can be in the tabulated text, boxed, and/or
placed in information boxes at the associated track, fix or phase of flight.
GRAPHIC — STARTING POINT AND END POINT OF STAR, DP, AND SID PROCEDURES
Navaids, intersections, or waypoints identified in the procedure title are shown prominently for easy
identification of the starting points on STARs, and the ending points on SID or DP procedures.
1329502730348
q$z
GRAPHIC
1303327466000
1 — Type of procedure.
2 — Arrival/Departure code.
3 — Arrival/Departure name.
4 — Database identifiers are included when different than the Arrival/Departure code or name.
5 — Specified qualifying statements, such as runways, navigational requirements, or aircraft type.
6— Runway layout is provided for all hard surface runways.
7— Arrival/Departure airport is highlighted with circular screen.
8— Arrival/Departure track of procedure represents a common course used by multiple transitions.
9— Airport is listed only when SID, DP, or STAR also serves multiple airports, which are screened.
10 — Starting Point of STAR and end point of SID/DP procedures are shown prominently.
11 — T placed after altitude denotes a Minimum Obstruction Clearance Altitude (MOCA).
12 — Radial and DME forms the fix. The DME, if not displayed is the segment distance, if shown it is the
total distance from the forming Navaid.
13 — Altitude T is placed when the altitude changes along a track at other than a Navaid.
14 — Certain Special Use Airspace Areas are charted when referenced in procedure source. 1329502730348
q$z
15 — Transition name placed on the last segment of the SID/DP and the first segment of STAR procedures.
16 — Minimum Enroute Altitude (MEA) unless otherwise designated.
17 — Segment distance.
18 — Coordinates of fix or Navaids.
19 — Formation radials are presented in many ways based on Navaid position & compositional space.
20 — Route identification code.
21 — At the Changeover point, the pilot changes primary navigation to the next Navaid.
22 — Transition track.
23 — VOR radial on which aircraft is flying inbound towards the Navaid. 1409754014530
1483739290874
q$z
1483739290874
FORMAT
1303320999000
HEADING
1342041780592
q$z
COMMUNICATIONS
For Communications Information See Approach Chart Legend — Page APPROACH-2
1303320999000
AIRPORT PLANVIEW
1— The planview is a "To Scale" graphical depiction of the airport layout, a latitude/longitude grid in
degrees, minutes, and tenths of minutes is depicted along the inside of the neat line.
2— The airport magnetic variation is graphically and numerically depicted.
3— Airport operational notes are placed within the planview. Notes pertaining to a specific area are placed
within the area or tied to it.
4— Runway designators (numbers) are magnetic unless followed by a "T" for true. Runway bearings
are included when known.
5— Physical length of the runway which does not include stopways, overruns, or adjustments for displaced
thresholds. Shown in feet with the meter equivalent included at International Airports.
6 — The runway end elevation is depicted when known.
7 — When applicable, the physical location of displaced thresholds along the runway are shown.
8 — Stopping points along the runway are depicted for Land and Hold Short Operations.
9 — "Hot Spot" areas are depicted along with a corresponding label when applicable. A textual description
is included within the planview or below the additional runway information band.
10 — When available, stopways and overruns are depicted with the applicable length.
11 — When known, the location of RVR transmissometers are shown with any applicable identifiers.
12 — All active taxiways and ramp areas are depicted using a grey area fill color. All taxiway identifiers and
ramp names are included when known.
13 — All known permanently closed taxiways are shown.
14 — One of two depictions is used for closed runways depending on the nature of the closure:
a. Lengths and designators (numbers) are retained when the closure is temporary.
b. Lengths and designators (numbers) are removed when the closure is permanent.
15 — The configuration and length of all known approach light systems are shown. 1363984942909
q$z
572549100851
q$z
572549100851
q$z
572549100851
q$z
572549100851
q$z
FORMAT
1303315984000
HEADING
1303315984000
1329509389463
q$z
COMMUNICATIONS
1303315984000
1 — Communications are shown left to right in the 6 — Indicates that radar services are available.
order of normal use.
2 — Communication service, call sign is omitted 7 — Sectors are defined for each frequency when
when the service is broadcast only. applicable.
3 — Functionality of the service is shown when 8 — Indicates the service is part time.
applicable.
4 — The service call sign is shown when transmit & 9 — When the service is a secondary function, the
receive or transmit only operations are available. call sign is omitted.
5 — All available primary frequencies are depicted.
1304453542000
1304453542000
1303315984000
1303317335000
NOTE: Normal coverage is a 25 NM radius from the forming facility/fix. If the protected coverage is other than
25 NM, that radius is depicted below the forming facility/fix.
1329509389463
q$z
APPROACH PLANVIEW
1303315984000
1— The planview is a graphical "To Scale" depiction of the approach procedure. Latitude and longitude
tics are shown in 10 minute increments along the neatline.
2— Complete runway layout is depicted for the primary airport.
3— Approach transitions are depicted with a medium weight line. The bearing is normally inset within the
track with the mileage and associated altitude placed along the track.
4— Off-chart origination navaid/waypoint name. Navaid frequency, ident, and Morse code is shown when
required for fix formation.
5— VOR cross radials and NDB bearings used in forming a fix. DME formation distances are shown when
applicable. Navaid frequency, ident, and Morse code shown as required.
6— Airspace fixes depicted using several different symbols according to usage.
7— Navaid boxes include the navaid name, identifier, Morse code, and frequency. A letter "D" indicates
DME capability with an asterisk indicating part time.
8— Substitute fix identification information located below facility box when applicable.
9— Initial Approach Fixes and Intermediate Fixes are labeled as (IAF) and (IF) respectively.
10 — A shadowed navaid box indicates the primary navaid upon which lateral course guidance for the
final approach segment is predicated.
11 — The final/intermediate approach course is indicated with a heavy weight line.
12 — The final approach course bearing shown in bold text, with a directional arrow as needed.
13 — Airspace fix names are shown near or tied to the fix, formational info is placed below name.
14 — Jeppesen-derived database identifiers are depicted when different from State-supplied name.
15 — The missed approach segment is shown with heavy weight dashed line work.
16 — Holding/Racetrack patterns are shown with both inbound and outbound bearings. Restrictions are
charted when applicable, heavy weight tracks indicate the holding/racetrack is required.
17 — Some, but not all, terrain high points and man-made structures are depicted along with their elevations.
Generally only high points 400’ or more above the airport elevation are shown. 1341935460082
q$z
q$i
18 — Arrow indicates the highest of the portrayed high points within the planview area only.
19 — Generalized terrain contours may be depicted based on several geographic factors.
20 — Rivers/large water bodies are shown. Smaller and seasonal water areas are not depicted.
21 — Some, but not all, Special Use Airspace boundaries and identifiers are depicted.
22 — All secondary IFR airports, and VFR airports that lie under the final approach, are depicted.
23 — Charting scale used is indicated along the left side of the planview.
1303315984000
1303315984000
1— A primary navaid box is shown for RNAV approach procedures augmented by ground based facilities.
The system type, channel, and system approach ID are shown.
2— Some RNAV procedures utilize Terminal Arrival Area/Terminal Area Altitude (TAA). A graphical
depiction of each TAA sector is placed within the planview in the corresponding area. The TAA’s
foundational waypoint is depicted along with the forming bearings, arrival altitudes, and applicable
NoPT labels. Generally the TAA replaces the MSA as indicated in the MSA box.
3— When the normal TAA coverage of 30 NM (25 NM ICAO) from the base waypoint is modified, the
segmented areas are depicted with the applicable altitudes indicated.
4— Due to the required use of a database, only waypoint names are shown. Formations and coordinates
are omitted.
5— Along track distances, normally to the next named waypoint, are shown per source for un-named
waypoints.
1329509389463
q$z
1303315984000
Insets are used to portray essential procedural information that falls outside of the planview boundary. The
use of insets facilitates larger scales for depicting core segments of the procedure.
1 — A solid line is used to outline the inset when the information has been remoted from the associated "To
Scale" tracks. Labels inside the inset indicate the usage of the contained procedural information.
2 — A dashed line is used to outline the inset when the information remains in line with the associated "To
Scale" tracks. A NOT TO SCALE label is included inside the inset.
1303315984000
General Description: The Recommended Altitude Descent table, shown to facilitate the CDFA technique,
contains "check" altitudes that correlate directly to the Vertical Descent Angle (VDA) used in conjunction with
the final approach segment of the procedure. When the State Authority has not supplied this information,
Jeppesen will derive the altitudes based on the procedure VDA.
1 — The direction of the Recommended Altitude Descent table, top of descent down, is sequenced in the
same direction as the flight tracks in the profile. A grey arrow indicates this left-to-right or right-to-Ieft
direction.
2 — The source for the DME "checkpoints" is indicated by the navaid ident. When the table is
Jeppesen-derived, DME is used whenever possible for the establishment of the checkpoints.
3 — The row of recommended altitudes is labeled to indicate their associated use with the VDA.
4 — The DME distance that defines each checkpoint is depicted in whole and tenths of a NM.
5 — A recommended altitude, (which is defined by a position along the VDA at a given point) is supplied
corresponding to each checkpoint in the table.
6 — When DME is not available, each checkpoint will be defined by a distance to a fix along the final
approach course. This distance is shown in whole and tenths of a NM.
7 — The "to" waypoint is indicated when checkpoints are defined by a distance to a fix.
8 — When a Non-Precision approach is combined with a Precision approach, a qualifier is added to indicate
that the depicted recommended altitudes relate to the non-precision approach only.
9 — Bold text indicates the altitude is charted in the FAF altitude box within the Briefing Strip.
1329509389463
q$z
1303317335000
1— Procedure notes that relate directly to information portrayed in the profile view are charted within the
profile view, normally placed in the upper right or left corners.
2 — A "broken" navaid or fix symbol indicates that it does not fall directly in line with the final approach track.
3 — Outbound bearings associated with procedure turns are included for situational awareness.
4 — Minimum altitude while executing the procedure turn.
5 — The distance to remain within while executing the procedure turn. Distance is measured from the
initiating navaid/fix unless otherwise indicated.
6 — Profile view "ground line". Represents an imaginary straight line originating from the runway threshold.
No terrain high points or man-made structures are represented in the profile view.
7 — Procedure flight tracks are portrayed using a thick solid line. Multiple separate procedures using the
same altitudes are represented by a single line.
8 — Final Approach Point (FAP). Beginning of the final approach segment for precision approaches.
9 — Nautical Mile (NM) distance to the "0" point. Not included at DME fixes.
10 — Nautical Mile (NM) distance between two navaids and or fixes. 1329509389463
q$z
572538675160
q$z
572538675160
q$z
1572538675160
q$z
572538675160
q$z
572538675160
q$z
572538675160
q$z
1484734858953
3. CIRCLING MINIMUMS
Circling minimums are only charted if a circling
OCA(H) or MDA(H) is provided by the procedure
source. Otherwise, the circling box is removed. If
circling is not authorized by the procedure source,
it will be noted in the Briefing Strip header. Where
straight-in minimums are higher than circling min-
imums (DH/MDH or RVR/VIS), a note is added to
remind the pilot that the higher straight-in minimums
have to be used.
q$z
CHART LEGEND - EASA AIR OPS AERODROME OPERATING MINIMUMS (AOM) q$i
Sample of Circling Minimums Normally, only CDFA minimums are shown. They
are identified by the use of a DA/MDA(H) label.
Jeppesen does not apply an add-on when pub-
lishing a DA/MDA(H) for a CDFA non-precision
approach, because this depends on operator
specific factors.
The CDFA condition will always be identified by the
term ‘CDFA” above the DA/MDA(H) label.
Non-CDFA minimums are shown in exceptional
cases and identified by an MDA(H) label. The
MDA(H) label is also charted if the State explicitly
publishes an MDA(H) on procedure source instead of
an OCA(H). The non-CDFA condition will always be
1484567554702
identified by the term ‘non-CDFA” above the MDA(H)
label.
4. NON-PRECISION APPROACH
MINIMUMS AND CHART PROFILE Sample of Non-precision Minimums (CDFA)
VIEW
According to the EASA AIR OPS requirements for
Commercial Air Transport Operations (Part CAT),
all non-precision approaches shall be flown using
the continuous descent final approach (CDFA)
technique with decision altitude (height), and the
missed approach shall be executed when reaching
the DA(H) or the missed approach point (MAP),
whichever occurs first. The lateral part of the missed
approach procedure must be flown via the MAP
unless stated otherwise in the procedure.
Jeppesen criteria for charting of CDFA or non-CDFA
minimums are based on AMC1 CAT.OP.MPA.115 1484567554702
1484567554702
1484567554702
1484567554702
5. CAT I PRECISION AND APV d. for APV operations to runways with FALS and
APPROACH MINIMUMS TDZ and CL when using an approved head-up
display (HUD).
An RVR of less than 750m may be used:
NOTE: A conversion of reported meteorological vis-
a. for CAT I operations to runways with FALS and
ibility to CMV should not be used for any RVR min-
TDZ and CL, or
imum less than 800m. In this case a minimum VIS
b. for CAT I operations to runways with FALS but of 800m applies for the procedure. A charted “RVR
without TDZ and/or CL when using an approved XXXm” (any RVR below 800m) have to be understood
head-up guidance landing system (HUDLS) or as “RVR XXXm or VIS 800m”.
an equivalent approved system, or
The European States publish more and more LPV
c. for CAT I operations to runways with FALS but (SBAS CAT I) procedures. To clearly differentiate
without TDZ and/or CL when conducting a cou- between the CAT I and APV operations, the terms
pled or flight-director-flown approach to decision “LPV CAT I” and “LPV” are used in the minimums
height, or box.
1484734858953
q$z
CHART LEGEND - EASA AIR OPS AERODROME OPERATING MINIMUMS (AOM) q$i
1484567554702
1484567554702
1484567554702
q$z
1484734858953
1484567554702
q$z
CHART LEGEND - EASA AIR OPS AERODROME OPERATING MINIMUMS (AOM) q$i
1484567554702
1484567554702
q$z
1484567554702
11. DEPICTION OF EASA AIR c. If only VIS is charted, the reported VIS has to be
OPS AOM IN CASE OF EXISTING used without conversion.
STATE MINIMUMS d. If CMV is charted, the pilot converts a reported
VIS and compare this value against the charted
If State minimums are officially published, the depic-
CMV.
tion of AOM may differ from the standard depiction
where all values are expressed as RVR or VIS.
a. If RVR and VIS are charted together, the RVR
value is compulsory. If no RVR is reported, the
reported VIS has to be used without conversion.
b. No prefix is charted if RVR and VIS is identical.
The reported RVR is compulsory. If no RVR is
reported, the reported VIS has to be used with-
out conversion.
q$z
PREFACE
The purpose in providing the information contained in these pages is to highlight the major dif-
ferences between Jeppesen’s NavData database and Jeppesen’s Enroute, Area, SID, DP,
STAR, Approach, and Airport Charts.
The basic design for most aeronautical information contained in instrument procedures has
been created for the analog world. The art of entering data into an aeronautical database is
one that balances the intent of the original procedure designer and the requirements of FMS
and GPS systems that require airborne databases.
All of the illustrations in this paper are from Jeppesen’s library and are copyrighted by Jeppe-
sen. The paper will highlight differences that will be found in the charts and databases pro-
duced by all the suppliers.
Virtually all the aeronautical databases are loaded according to the specifications in the Aero-
nautical Radio, Incorporated (ARINC) 424 standard "Navigation Databases." While the
ARINC 424 specification covers a large percentage of the aeronautical requirements, it is
impossible to write a specification that covers every combination of factors used to design
and fly instrument procedures. Many of the differences between charts and databases are
because there can be no standard implemented to have the information in both places
depicted the same. There are some cases where it is desirable not to have the information
the same because of the different type of media where the information is displayed.
Any attempt to detail the many minor differences, which may arise under isolated cases,
would unduly complicate this overview. Therefore, the information provided is an overview
only, and only major differences are included.
There are many different types of avionics equipment utilizing the Jeppesen NavData data-
base. The same database information may be presented differently on different types of air-
borne equipment. In addition, some equipment may be limited to specific types of database
information, omitting other database information. Pilots should check their Operating Hand-
books for details of operation and information presentation. A major factor in "apparent" dif-
ferences between database and charts may be due to the avionics equipment utilized. As
avionics equipment evolves, the newer systems will be more compatible with charts, however
the older systems will still continue with apparent differences.
Due to the continuing evolution caused by aeronautical information changes affecting both
database and charting, items described herein are subject to change on a continual basis.
This document may be revised for significant changes to help ensure interested database
users are made aware of major changes.
1. EFFECTIVE DATES
Because of the required time it takes to physically get the database updated, extracted, pro-
duced, delivered, and loaded into FMS/GPS systems, the database cut-off dates (when aero-
nautical information can no longer be included in the next update) are often earlier for
databases than for charts. This may cause information on charts to be more current than the
information in databases.
The ICAO Aeronautical Information Regulation and Control (AIRAC) governs the 28-day
cycle between effective dates of aeronautical information. These are the same effective
dates used for aeronautical databases. Because governments may use slightly different
cycles, there are differences between charts and databases. Charts typically use 7-day and
14-day cycles for terminal charts and 28-day and 56-day cycles for enroute and area charts.
2. GENERAL DIFFERENCES
Not all the information that is included on the charts is included in the airborne database. The
following is a general listing of some of those items. More specific items are included in indi-
vidual entries throughout this document.
Altimetry:
QNH/QFE information
Alternate altimeter setting sources
Intersection formations (radials, bearings, DME)
Terrain and Obstacles
Airport Operating Minimums
Landing, take-off and alternate minimums
Airport taxiways and ramps
Some types of special use airspace and controlled airspace
LOCATOR IDENTIFIERS
Most locators in the United States have unique five-letter names, but most international loca-
tors have names that do not have five letters.
Some systems may display U.S. locators as "CASSE".
Some systems may display U.S. locators as "AP".
Not all navaids in the database are accessible by their identifier. Some navaids, for reasons
such as duplication within terminal areas or lack of complete information about the navaid,
are in the waypoint file and are accessible by their name or abbreviated name.
4. WAYPOINTS
• Jeppesen's ultimate goal is to include all database identifiers for all waypoints/fixes on the
charts.
• Enroute charts include the five-character identifier for unnamed reporting points, DME
fixes, mileage breaks, and for any reporting point with a name that has more than five
characters.
• SID, DP and STAR charts are being modified to include all identifiers.
Some States publish narrative descriptions of their arrivals, and depict them on their enroute
charts. They are unnamed, not identified as arrival routes, and are not included in the Jeppe-
sen NavData database. Some States publish "DME or GPS Arrivals", and because they are
otherwise unnamed, they are not included in the database.
PROCEDURE TITLES
Procedure identifiers for routes such as STARs, DPs and SIDs are in airborne databases but
are limited to not more than six alpha/numeric characters. The database generally uses the
charted computer code (shown enclosed within parentheses on the chart) for the procedure
title, as
When no computer code is assigned, the name is truncated to not more than six characters.
The database procedure identifier is created according to the ARINC 424 specifications.
Database procedure identifiers are charted in most cases. They are the same as the
assigned computer code (charted within parentheses) or are being added [enclosed within
square brackets]. Do not confuse the bracketed database identifier with the official procedure
name (which will be used by ATC) or the official computer code (which is used in flight plan fil-
ing).
400-FOOT CLIMBS
Virtually all departures in the database include a climb to 400 feet above the airport prior to
turning because of requirements in State regulations and recommendations. The 400-foot
climb is not depicted on most charts. When States specify a height other than 400 feet, it will
be in the Jeppesen NavData database.
ICAO PANS OPS approach procedure titles are officially labeled with the navaid(s) used for
the approach and are different than approach procedure titles labeled according to the
TERPs criteria, which are labeled only with navaids required for the final approach segment.
Because of the limited number of characters that are available for the procedure title, the
name displayed on the avionics equipment may not be the same as the official name shown
on the approach chart.
The Jeppesen NavData database, in accordance with ARINC 424 specifications, codes the
approach procedure according to procedure type and runway number. "Similar" type
approaches to the same runway may be combined under one procedure title, as ILS Rwy 16
and NDB VOR ILS Rwy 16 may read as ILS Rwy 16. The actual avionics readout for the pro-
cedure title varies from manufacturer to manufacturer.
Some avionics systems cannot display VOR and VOR DME (or NDB and NDB DME)
approaches to the same runway, and the approach displayed will usually be the one associ-
ated with DME.
Currently:
Generally, most Cat I, II, and III ILS approaches to the same runway are the same basic
procedure, and the Cat I procedure is in the database. However, in isolated cases, the
Cat I and Cat II/III missed approach procedures are different, and only the Cat I missed
approach will be in the database.
Additionally, there may be ILS and Converging ILS approaches to the same runway.
While the converging ILS approaches are not currently in the database, they may be at
some later date.
Some States are using the phonetic alphabet to indicate more than one "same type, same
runway" approach, such as ILS Z Rwy 23 and ILS Y Rwy 23. The phonetic alphabet
starts are the end of the alphabet to ensure there is no possibility of conflict with circling
only approaches, such as VOR A.
In isolated cases, procedures are intentionally omitted from the database. This occurs prima-
rily when navaid/waypoint coordinates provided by the authorities in an undeveloped area are
inaccurate, and no resolution can be obtained. Additionally, the ARINC 424 specifications
governing navigation databases may occasionally prohibit the inclusion of an approach pro-
cedure.
INITIAL APPROACH FIX (IAF), INTERMEDIATE FIX (IF), FINAL APPROACH FIX (FAF)
DESIGNATIONS
These designations for the type of fix for operational use are included on approach charts
within parentheses when specified by the State, but are not displayed on most avionics sys-
tems.
ARINC 424 and TSO C-129 specifications require the inclusion of GPS approach transitions
originating from IAFs. Authorities do not always standardize the assignment of IAFs, result-
ing in some cases of approach transitions being included in the database that do not originate
from officially designed IAFs
West bound on the 22 DME arc, the leg after the 171° lead-in radial may not be displayed in
all avionics equipment.
*Descent angles for circle-to-land only approaches are currently not in the database and are
not charted.
In the United States, many non-precision approaches have descent angles provided by the
FAA and are depicted on the approach charts. For many of the U.S. procedures, and in other
countries, the descent angles are calculated based on the altitudes and distances provided
by the State authorities. These descent angles are being added to Jeppesen’s charts.
The descent angle accuracy may be affected by temperature. When the outside air tempera-
ture is lower than standard, the actual descent angle will be lower. Check your avionics
equipment manuals since some compensate for nonstandard temperatures.
When there is no intersection or waypoint at the FAF such as at the MONRY LOM, the data-
base identifier will be
"OM09" if the LOM is on the centerline, and
"FF09" if the LOM is not on the centerline.
In some systems, to access the locator on most ILS and localizer approaches, the Morse
code identifier can be used.
In the United States, virtually all locators have a five-letter unique name/identifier so the loca-
tion can usually be accessed in some systems by the navaid Morse code identifier or the five-
letter name. In some systems, the locator is accessed by the name or by adding the letters
"NB" to the Morse code identifier.
NAMED and UN-NAMED STEPDOWN FIXES, FINAL APPROACH FIX (FAF) to MISSED
APPROACH POINT (MAP)
Named and un-named stepdown fixes between the FAF and MAP are currently not included
in the databases, but will be added in the future. They are often DME fixes, and in those
cases, can be identified by DME. The distance to go to the MAP may be labeled on some
GPS/GNSS type charts and VOR DME RNAV charts. Proper identification of these displayed
fixes is necessary to clear all stepdown fix crossing altitudes.
400-FOOT CLIMBS
The database includes a climb to 400 feet above the airport prior to turning on a missed
approach. This climb is not part of the official procedure, but does comply with State regula-
tions and policies. This specific climb to 400 feet is not included on charts. The missed
approach text supplied by the State authority is charted.
The routes in approach procedures, SIDs (DPs), and STARs are coded into the database
using computer codes called path terminators which are defined in the ARINC 424 Navigation
Database Specification. A path terminator 1) Defines the path through the air, and 2) Defines
the way the leg (or route) is terminated. Not all avionics systems have implemented the full
set of path terminators specified in the ARINC 424 document.
Because of the incomplete set of path terminators in some avionics systems, pilots need to
ensure their avionics systems will take them on the routes depicted on the charts. If the avi-
onics systems don’t have all the routes, or don’t have the means to display them, it is the
pilot’s responsibility to fly the routes depicted on the charts.
There are differences between information displayed on your airborne avionics navigation
system and the information shown on Jeppesen charts. The charts, supplemented by NOT-
AMs, are the final authority.
GLOSSARY/ABBREVIATIONS
AIRAC - Aeronautical Information Regulation and Control. Designates the revision cycle
specified by ICAO, normally 28 days.
DATABASE IDENTIFIER - Avionics system use only, not for flight plans or ATC communica-
tions. Identifies a waypoint or fix.
DP - Departure Procedure
FACF - Final Approach Capture Fix. Database includes (usually as an intermediate fix) when
no suitable fix is specified in source.
FLY-BY FIX - Waypoint allows use of turn anticipation to avoid overshoot of the next flight
segment.
FLY-OVER FIX - Waypoint precludes any turn until the fix is over flown and is followed by an
intercept maneuver of the next flight segment.
GPS/GNSS SENSOR FAF - Database fix that changes sensitivity of the Course Deviation
Indicator (CDI) on final approach.
GPS/GNSS TYPE APPROACHES - Any approach that can be flown with GPS/GNSS as the
only source of navigation.
GLOSSARY/ABBREVIATIONS (Cont)
PANS OPS - Procedures for Air Navigation Services - Aircraft Operations (ICAO)
SENSOR FINAL APPROACH FIX (FF) - Included in database and on charts when no FAF is
specified for the approach.
END
AAMEDU
9 NOV 12