NAVIGATION SYSTEM DATA BASE

ARINC SPECIFICATION 424-17

PUBLISHED: AUGUST 31, 2004

AN DOCUMENT
Prepared by
AIRLINES ELECTRONIC ENGINEERING COMMITTEE
Published by
AERONAUTICAL RADIO, INC.
2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401
This document is based on material submitted by various
participants during the drafting process. Neither AEEC nor ARINC
has made any determination whether these materials could be
subject to valid claims of patent, copyright or other proprietary
rights by third parties, and no representation or warranty, express or
implied, is made in this regard. Any use of or reliance on this
document shall constitute an acceptance thereof “as is” and be
subject to this disclaimer.

Material included in this document is copyrighted by Jeppesen

Sanderson and is reproduced with their consent. ARINC makes no
claims to the accuracy of the material.
 © 2004 by
AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

ARINC SPECIFICATION 424-17

NAVIGATION SYSTEM DATA BASE

Published: August 31, 2004

Prepared by the Airlines Electronic Engineering Committee

Specification 424 Adopted by the Airlines Electronic Engineering Committee: May 21, 1975
Specification 424 Approved by the Industry: July 15, 1975

Summary of Document Supplements

Supplement Adoption Date Published

Specification 424-1 June 19, 1980 September 8, 1980
Specification 424-2 December 9, 1981 February 5, 1982
Specification 424-3 November 4, 1982 January 17, 1983
Specification 424-4 October 12, 1983 November 10, 1983
Specification 424-5 October 10, 1984 March 18, 1985
Specification 424-6 November 7, 1985 January 31, 1986
Specification 424-7 October 8, 1986 January 14, 1987
Specification 424-8 February 28, 1989 October 15, 1989
Specification 424-9 October 26, 1989 March 2, 1990
Specification 424-10 August 16, 1993 August 20, 1993
Specification 424-11 August 16, 1983 August 20, 1993
Specification 424-12 May 17, 1994 September 15, 1994
Specification 424-13 May 23, 1995 December 31, 1995
Specification 424-14 August 24, 1999 February 11, 2000
Specification 424-15 January 12, 2000 February 11, 2000
Specification 424-16 April 8, 2002 August 30, 2002
Specification 424-17 May 5, 2004 August 31, 2004
A description of the changes introduced by each Supplement is included on goldenrod paper at the end of this document.
 FOREWORD

Aeronautical Radio, Inc., the AEEC, and ARINC Standards

Aeronautical Radio, Inc. (ARINC) was incorporated in 1929 by four fledgling airlines in the United
States as a privately-owned company dedicated to serving the communications needs of the air transport
industry. Today, the major U.S. airlines remain the Company’s principal shareholders. Other
shareholders include a number of non-U.S. airlines and other aircraft operators.

ARINC sponsors aviation industry committees and participates in related industry activities that benefit
aviation at large by providing technical leadership and guidance and frequency management. These
activities directly support airline goals: promote safety, efficiency, regularity, and cost-effectiveness in
aircraft operations.

The Airlines Electronic Engineering Committee (AEEC) is an international body of airline technical
professionals that leads the development of technical standards for airborne electronic equipment-
including avionics and in-flight entertainment equipment-used in commercial, military, and business
aviation. The AEEC establishes consensus-based, voluntary form, fit, function, and interface standards
that are published by ARINC and are known as ARINC Standards. The use of ARINC Standards results
in substantial benefits to airlines by allowing avionics interchangeability and commonality and reducing
avionics cost by promoting competition.

There are three classes of ARINC Standards:

a) ARINC Characteristics – Define the form, fit, function, and interfaces of avionics and other
airline electronic equipment. ARINC Characteristics indicate to prospective manufacturers of
airline electronic equipment the considered and coordinated opinion of the airline technical
community concerning the requisites of new equipment including standardized physical and
electrical characteristics to foster interchangeability and competition.
b) ARINC Specifications – Are principally used to define either the physical packaging or
mounting of avionics equipment, data communication standards, or a high-level computer
language.
c) ARINC Reports – Provide guidelines or general information found by the airlines to be good
practices, often related to avionics maintenance and support.
The release of an ARINC Standard does not obligate any airline or ARINC to purchase equipment so
described, nor does it establish or indicate recognition or the existence of an operational requirement for
such equipment, nor does it constitute endorsement of any manufacturer’s product designed or built to
meet the ARINC Standard.

In order to facilitate the continuous product improvement of this ARINC Standard, two items are included
in the back of this volume:
a) An Errata Report solicits any corrections to the text or diagrams in this ARINC Standard.
b) An ARINC IA Project Initiation/Modification (APIM) form solicits any recommendations for
addition of substantive material to this volume which would be the subject of a new
Supplement.

ii
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
1.0 INTRODUCTION 1
1.1 Purpose of this Document 1
1.1.1 Coverage of Flight Simulator Needs 1
1.1.2 Coverage of Flight Planning Needs 1
1.2 Data Format Standardization Philosophy 1
1.3 Organization of this Document 2
1.3.1 Coverage of Helicopter Operation Needs 2
1.4 Reference Documentation 2
FIGURE
1-1 ARINC Specification 424 Information Presentation 3

ITEM
2.0 GLOSSARY OF TERMS 4
2.1 Data Processing Terms 4
2.2 Special Navigation Terms 4
2.3 Precision RNAV Terms 5

3.0 NAVIGATION DATA 6

3.1 User File Organization 6
3.2 Master Airline User File Content 6
3.2.1 General 6
3.2.2 NAVAID Section (D) 6
3.2.2.1 VHF Navaid Section (D), Subsection (Blank) 6
3.2.2.2 NDB Navaid Section (D), Subsection (B) 6
3.2.3 Enroute Section 6
3.2.3.1 Enroute Waypoint Section (E), Subsection (A) 6
3.2.3.2 Enroute Airway Marker Section (E), Subsection (M) 6
3.2.3.3 Holding Patterns (E), Subsection (P) 6
3.2.3.4 Enroute Airways Section (E), Subsection (R) 6
3.2.3.5 Enroute Airways Restrictions Section (E), Subsection (U) 6
3.2.3.6 Enroute Communications Section (E), Subsection (V) 6
3.2.4 Airport Section (P) 6
3.2.4.1 Airport Reference Points Section (P), Subsection (A) 6
3.2.4.2 Airport Gates Section (P), Subsection (B) 6
3.2.4.3 Airport Terminal Waypoints Section (P), Subsection (C) 7
3.2.4.4 Airport Standard Instrument Departures (SIDs) Section (P), Subsection (D) 7
3.2.4.5 Airport Standard Terminal Arrival Routes (STARs) Section (P), Subsection (E) 7
3.2.4.6 Airport Approaches Section (P), Subsection (F) 7
3.2.4.7 Airport Runway Section (P), Subsection (G) 9
3.2.4.8 Airport and Heliport Localizer/Glide Slope Section (P), Subsection (I) 9
3.2.4.9 Airport and Heliport MLS Section (P), Subsection (L) 9
3.2.4.10 Airport and Heliport Marker/Locator Marker Section (P), Subsection (M) 9
3.2.4.11 MSA Section (P), Subsection (S) 9
3.2.4.12 Airport Communications Section (P), Subsection (V) 9
3.2.4.13 Airport and Heliport Terminal NDB Section (P), Subsection (N) 9
3.2.4.14 Airport and Heliport Path Point Section (P), Subsection (P) 9
3.2.4.15 Flight Planning Arrival/Departure Data Record Section (P), Subsection (R) 9
3.2.4.16 GNSS Landing System (GLS) Section (P), Subsection (T) 9
3.2.4.17 Airport Terminal Arrival Altitude Section (P), Subsection (K) 9
3.2.5 Company Route and Alternation Destination Section (R) 9
3.2.5.1 Company Route Section (R), Subsection (Blank) 9
3.2.5.2 The Alternate Record Section (R), Subsection (A) 9
3.2.6 Special Use Airspace Section (U) 9
3.2.6.1 Restrictive Airspace Section (U), Subsection (R) 9
3.2.6.2 FIR/UIR Section (U), Subsection (F) 9
3.2.6.3 Controlled Airspace Section (U), Subsection (C) 10
3.2.7 Cruising Table Section (T) 10
3.2.7.1 Cruising Tables Section (T), Subsection (C) 10
3.2.7.2 Geographical Reference Table Section (T), Subsection (G) 10
3.2.8 MORA Section (A), Subsection (S) 10
3.2.9 Preferred Routes Section (E), Subsection (T) 10

iii
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
3.3 Master Helicopter User File Content 10
3.3.1 General 10
3.3.2 Jointly and Specifically Used Sections/Subsections 10
3.3.3 Heliport Section (H), Subsection (A) 10
3.3.4 Heliport Terminal Waypoints Section (H), Subsection (C) 10
3.3.5 Heliport Standard Instrument Departures (SIDs) Section (H), Subsection (D) 10
3.3.6 Heliport Standard Terminal Arrival Routes (STARs) Section (H), Subsection (E) 10
3.3.7 Heliport Approaches Section (H), Subsection (F) 10
3.3.8 Heliport MSA Section (H), Subsection (S) 10
3.3.9 Heliport Communications Section (H), Subsection (V) 11
3.3.10 Heliport Terminal Arrival Area Section (H), Subsection (K) 11

FIGURE

3-1 Figure 3-1 Data Sorting Necessary to Achieve Step 1 of FDSU File Production Process 8

ITEM
4.0 NAVIGATION DATA - RECORD LAYOUT 12
4.0.1 General 12
4.1 Master Airline User File 12
4.1.2 VHF NAVAID Record (D) 12
4.1.2.1 VHF NAVAID Primary Records 12
4.1.2.2 VHF NAVAID Continuation Records 12
4.1.2.3 VHF NAVAID Simulation Continuation Records 13
4.1.2.4 VHF NAVAID Flight Planning Continuation Records 13
4.1.2.5 VHF NAVAID Flight Planning Continuation Records 13
4.1.2.6 VHF NAVAID Limitation Continuation Record 13
4.1.3 NDB NAVAID Record (DB or PN) 13
4.1.3.1 NDB NAVAID Primary Records 14
4.1.3.2 NDB NAVAID Continuation Records 14
4.1.3.3 NDB NAVAID Simulation Continuation Records 14
4.1.3.4 NDB NAVAID Flight Planning Continuation Records 14
4.1.3.5 NDB NAVAID Flight Planning Continuation Records 14
4.1.4 Waypoint Record (EA) or (PC) 14
4.1.4.1 Waypoint Primary Records 15
4.1.4.2 Waypoint Continuation Records 15
4.1.4.3 Waypoint Flight Planning Continuation Records 15
4.1.4.4 Waypoint Flight Planning Continuation Records 15
4.1.5 Holding Pattern Records (EP) 15
4.1.5.1 Holding Primary Records 16
4.1.5.2 Holding Pattern Continuation Records 16
4.1.6 Enroute Airways Records (ER) 16
4.1.6.1 Enroute Airways Primary Records 16
4.1.6.2 Enroute Airways Continuation Records 17
4.1.6.3 Enroute Airways Flight Planning Continuation Records 17
4.1.6.4 Enroute Airways Flight Planning Continuation Records 17
4.1.7 Airport Records (PA) 17
4.1.7.1 Airport Primary Records 17
4.1.7.2 Airport Continuation Records 18
4.1.7.3 Airport Flight Planning Continuation Records 18
4.1.7.4 Airport Flight Planning Continuation Records 18
4.1.8 Airport Gate Records (PB) 18
4.1.8.1 Airport Gate Primary Records 18
4.1.8.2 Airport Gate Continuation Records 18
4.1.9 Airport SID/STAR/Approach (PD, PE and PF) 18
4.1.9.1 Airport SID/STAR/Approach Primary Records 19
4.1.9.2 Airport SID/STAR/Approach Continuation Records 19
4.1.9.3 Airport SID/STAR/Approach Flight Planning Continuation Records 20
4.1.9.4 Airport SID/STAR Flight Planning Continuation Records 20
4.1.10 Runway Records (PG) 20
4.1.10.1 Runway Primary Records 20
4.1.10.2 Runway Continuation Records 20
4.1.10.3 Runway Simulation Continuation Records 20

iv
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
4.1.11 Airport and Heliport Localizer and Glide Slope Records (PI) 21
4.1.11.1 Airport and Heliport Localizer and Glide Slope Primary Records 21
4.1.11.2 Airport and Heliport Localizer and Glide Slope Continuation Records 21
4.1.11.3 Airport and Heliport Localizer and Glide Slope Simulation Continuation Records 21
4.1.12 Company Route Records (R) 21
4.1.12.1 Company Route Primary Records 22
4.1.13 Airport and Heliport Localizer Marker Records (PM) 22
4.1.13.1 Airport and Heliport Localizer Primary Records 22
4.1.13.2 Airport and Heliport Localizer Continuation Records 22
4.1.14 Airport Communications Records (PV) 23
4.1.14.1 Airport Communications Primary Records 23
4.1.14.2 Airport Communications Continuation Records 23
4.1.14.3 Airport Communications Continuation Records 23
4.1.15 Airways Marker Records (EM) 23
4.1.15.1 Airways Marker Primary Records 23
4.1.15.2 Airways Marker Continuation Records 24
4.1.16 Cruising Tables Records (TC) 24
4.1.16.1 Cruising Table Primary Records 24
4.1.17 FIR/UIR Records (UF) 24
4.1.17.1 FIR/UIR Primary Records 24
4.1.18 Restrictive Airspace Records (UR) 24
4.1.18.1 Restrictive Airspace Primary Records 25
4.1.18.2 Restrictive Airspace Continuation Records 25
4.1.18.3 Restrictive Airspace Flight Planning Continuation Records 25
4.1.19 Grid MORA Records (AS) 25
4.1.19.1 Grid MORA Primary Records 25
4.1.20 Airport MSA (Minimum Sector Altitude) Records (PS) 26
4.1.20.1 Airport MSA Primary Records 26
4.1.20.2 Airport MSA Continuation Records 26
4.1.21 Enroute Airways Restrictive Records (EU) 26
4.1.21.1 Enroute Airways Restriction Altitude Exclusion Primary Records 26
4.1.21A.1 Enroute Airways Restriction Note Restriction Primary Records 27
4.1.21A.2 Enroute Airways Restriction Note Restriction Continuation Records 27
4.1.21B.1 Enroute Airways Restriction Seasonal Closure Primary Records 27
4.1.21C.1 Enroute Airways Restriction Cruising Table Replacement Primary Records 28
4.1.21C.2 Enroute Airways Restriction Cruising Table Replacement Continuation Records 28
4.1.21.2 Enroute Airways Restriction Altitude Exclusion Continuation Records 28
4.1.22 Airport and Heliport MLS (Azimuth, Elevation and Back Azimuth) Records 28
4.1.22.1 Airport and Heliport MLS Primary Records 29
4.1.22.2 Airport and Heliport MLS Continuation Records 29
4.1.23 Enroute Communications Records (EV) 29
4.1.23.1 Enroute Communications Primary Records 29
4.1.23.2 Enroute Communications Continuation Records 30
4.1.23.3 Enroute Communications Continuation Records 30
4.1.24 Preferred Routes Records (ET) 30
4.1.24.1 Preferred Routes Primary Records 30
4.1.24.2 Preferred Route Continuation Records 31
4.1.24.3 Preferred Route Continuation Records (ET) 31
4.1.25 Controlled Airspace Records (UC) 31
4.1.25.1 Controlled Airspace Primary Records 31
4.1.25.2 Controlled Airspace Continuation Records 31
4.1.26 Geographical Reference Table Records (TG) 32
4.1.26.1 Geographical Reference Table Primary Records (TG) 32
4.1.26.2 Geographical Reference Table Continuation Records 32
4.1.27 Flight Planning Arrival/Departure Data Records (PR) 32
4.1.27.1 Flight Planning Primary Records 32
4.1.27.2 Flight Planning Continuation Records 33
4.1.27.3 Flight Planning Continuation Records 33
4.1.28 Path Point Records (PP) 33
4.1.28.1 Path Point Primary Records 33
4.1.28.2 Path Point Continuation Records 34
4.1.29 GLS Record (PT) 34
4.1.29.1 GLS Primary Records 34
4.1.29.2 GLS Continuation Records 34

v
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
4.1.30 Alternate Record (RA) 34
4.1.30.1 Alternate Primary Records 34
4.1.31 Airport TAA (PK) 35
4.1.31.1 Airport TAA Primary Records 35
4.1.31.2 Airport Terminal Arrival Altitude Continuation Records 35
4.2 Master Helicopter User File (HA) 35
4.2.1 Heliport Records 35
4.2.1.1 Heliport Primary Records 35
4.2.1.2 Heliport Continuation Records 35
4.2.1.3 Heliport Flight Planning Continuation Records 36
4.2.1.4 Heliport Flight Planning Continuation Records 36
4.2.2 Heliport Terminal Waypoint Records (HC) 36
4.2.2.1 Heliport Terminal Waypoint Primary Records 36
4.2.2.2 Heliport Terminal Waypoint Continuation Records 36
4.2.2.3 Heliport Terminal Waypoint Flight Planning Continuation Records 36
4.2.2.4 Heliport Terminal Waypoint Flight Planning Continuation Records 37
4.2.3 Heliport SID/STAR/Approach (HD/HE/HF) 37
4.2.3.1 Heliport SID/STAR/Approach Primary Records 37
4.2.3.2 Heliport SID/STAR/Approach Continuation Records 38
4.2.3.3 Heliport SID/STAR/Approach Flight Planning Continuation Records 38
4.2.3.4 Heliport SID/STAR/Approach Flight Planning Continuation Records 38
4.2.4 Heliport MSA (MS) 38
4.2.4.1 Heliport MSA Primary Records 39
4.2.4.2 Heliport MSA Continuation Records 39
4.2.5 Heliport Communications Records (HV) 39
4.2.5.1 Heliport Communications Primary Records 39
4.2.5.2 Heliport Communications Continuation Records 39
4.2.5.3 Heliport Communications Continuation Records 40
4.2.6 Heliport (TAA) 40
4.2.6.1 Heliport TAA Primary Records 40
4.2.6.2 Heliport Terminal Arrival Altitude Continuation Records 40

FIGURES

ARINC Specification 424 Record Layouts 41

ITEM

5.0 NAVIGATION DATA - FIELD DEFINITIONS 55

5.1 General 55
5.2 Record Type (S/T) 55
5.3 Customer/Area Code (CUST/AREA) 55
5.4 Section Code (SEC CODE) 55
5.5 Subsection Code (SUB CODE) 55
5.6 Airport/Heliport Identifier (ARPT/HELI IDENT) 56
5.7 Route Type (RT TYPE) 58
5.8 Route Identifier (ROUTE IDENT) 59
5.9 SID/STAR Route Identifier (SID/STAR IDENT) 60
5.10 Approach Route Identifier (APPROACH IDENT) 60
5.11 Transition Identifier (TRANS IDENT) 61
5.12 Sequence Number (SEQ NR) 62
5.13 Fix Identifier (FIX IDENT) 62
5.14 ICAO Code (ICAO CODE) 63
5.15 Intentionally Left Blank 63
5.16 Continuation Record Number (CONT NR) 63
5.17 Waypoint Description Code (DESC CODE) 63
5.18 Boundary Code (BDY CODE) 67
5.19 Level (LEVEL) 67
5.20 Turn Direction (TURN DIR) 67
5.21 Path and Termination (PATH TERM) 67
5.22 Turn Direction Valid (TDV) 67
5.23 Recommended NAVAID (RECD NAV) 67
5.24 Theta (THETA) 70
5.25 Rho (RHO) 70

vi
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
5.26 Outbound Magnetic Course (OB MAG CRS) 70
5.27 Route Distance From, Holding Distance/Time (RTE DIST FROM, HOLD DIST/TIME) 70
5.28 Inbound Magnetic Course (IB MAG CRS) 70
5.29 Altitude Description (ALT DESC) 71
5.30 Altitude/Minimum Altitude 71
5.31 File Record Number (FRN) 72
5.32 Cycle Date (CYCLE) 72
5.33 VOR/NDB Identifier (VOR IDENT/NDB IDENT) 72
5.34 VOR/NDB Frequency (VOR/NDB FREQ) 73
5.35 NAVAID Class (CLASS) 73
5.36 Latitude (LATITUDE) 75
5.37 Longitude (LONGITUDE) 75
5.38 DME Identifier (DME IDENT) 76
5.39 Magnetic Variation (MAG VAR, D MAG VAR) 76
5.40 DME Elevation (DME ELEV) 77
5.41 Region Code (REGN CODE) 77
5.42 Waypoint Type (TYPE) 77
5.43 Waypoint Name/Description (NAME/DESC) 78
5.44 Localizer/MLS/GLS Identifier (LOS, MLS, GLS IDENT) 78
5.45 Localizer Frequency (FREQ) 78
5.46 Runway Identifier (RUNWAY ID) 79
5.47 Localizer Bearing (LOC BRG) 79
5.48 Localizer Position (LOC FR RW END Azimuth/Back Azimuth Position (AZ/BAZ FR RW 79
END)
5.49 Localizer/Azimuth Position Reference (@, +, -) 79
5.50 Glide Slope Position (GS FR RW THRES) Elevation Position (EL FR RW THRES) 79
5.51 Localizer Width (LOC WIDTH) 79
5.52 Glide Slope Angle (GS ANGLE) Minimum Elevation Angle (MIN ELEV ANGLE) 80
5.53 Transition Altitude/Level (TRANS ALTITUDE/LEVEL) 80
5.54 Longest Runway (LONGEST RWY) 80
5.55 Airport/Heliport Elevation (ELEV) 80
5.56 Gate Identifier (GATE IDENT) 80
5.57 Runway Length (RUNWAY LENGTH) 81
5.58 Runway Magnetic Bearing (RWY BRG) 81
5.59 Runway Description (RUNWAY DESCRIPTION) 81
5.60 Name (NAME) 81
5.61 Notes (Continuation Records) (NOTES) 81
5.62 Inbound Holding Course (IB HOLD CRS) 81
5.63 Turn (TURN) 81
5.64 Leg Length (LEG LENGTH) 81
5.65 Leg Time (LEG TIME) 81
5.66 Station Declination (STN DEC) 82
5.67 Threshold Crossing Height (TCH) 82
5.68 Landing Threshold Elevation (LANDING THRES ELEV) 82
5.69 Threshold Displacement Distance (DSPLCD THR) 85
5.70 Vertical Angle (VERT ANGLE) 85
5.71 Name Field 85
5.72 Speed Limit (SPEED LIMIT) 85
5.73 Speed Limit Altitude 85
5.74 Component Elevation (GS ELEV, EL ELEV, AZ ELEV, BAZ ELEV) 85
5.75 From/To - Airport/Fix 86
5.76 Company Route Ident 86
5.77 VIA Code 86
5.78 SID/STAR/App/AWY (S/S/A/AWY) SID/STAR/Awy (S/S/AWY) 88
5.79 Stopway 88
5.80 ILS/MLS/GLS Category (CAT) 88
5.81 ATC Indicator (ATC) 88
5.82 Waypoint Usage 88
5.83 To FIX 89
5.84 RUNWAY TRANS 89
5.85 ENRT TRANS 89
5.86 Cruise Altitude 89
5.87 Terminal/Alternate Airport (TERM/ALT ARPT) 89
5.88 Alternate Distance (ALT DIST) 89

vii
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
5.89 Cost Index 90
5.90 ILS/DME Bias 90
5.91 Continuation Record Application Type (APPL) 90
5.92 Facility Elevation (FAC ELEV) 90
5.93 Facility Characteristics (FAC CHAR) 90
5.94 True Bearing (TRUE BRG) 91
5.95 Government Source (SOURCE) 91
5.96 Glide Slope Beam Width (GS BEAM WIDTH) 92
5.97 Touchdown Zone Elevation (TDZE) 92
5.98 TDZE Location (LOCATION) 92
5.99 Marker Type (MKR TYPE) 92
5.100 Minor Axis Bearing (MINOR AXIS TRUE BRG) 92
5.101 Communications Type (COMM TYPE) 92
5.102 Radar (RADAR) 93
5.103 Communications Frequency (COMM FREQ) 93
5.104 Frequency Units (FREQ UNIT) 94
5.105 Call Sign (CALL SIGN) 94
5.106 Service Indicator (SER IND) 94
5.107 ATA/IATA Designator (ATA/IATA) 95
5.108 IFR Capability (IFR) 95
5.109 Runway Width (WIDTH) 95
5.110 Marker Ident (MARKER IDENT) 95
5.111 Marker Code (MARKER CODE) 95
5.112 Marker Shape (SHAPE) 95
5.113 High/Low (HIGH/LOW) 95
5.114 Duplicate Identifier (DUP IND) 96
5.115 Direction Restriction 96
5.116 FIR/UIR Identifier (FIR/UIR IDENT) 96
5.117 FIR/UIR Indicator (IND) 97
5.118 Boundary Via (BDRY VIA) 97
5.119 Arc Distance (ARC DIST) 97
5.120 Arc Bearing (ARC BRG) 97
5.121 Lower/Upper Limit 97
5.122 FIR/UIR ATC Reporting Units Speed (RUS) 98
5.123 FIR/UIR ATC Reporting Units Altitude (RUA) 98
5.124 FIR/UIR Entry Report (ENTRY) 98
5.125 FIR/UIR Name 98
5.126 Restrictive Airspace Name 98
5.127 Maximum Altitude (MAX ALT) 98
5.128 Restrictive Airspace Type (REST TYPE) 100
5.129 Restrictive Airspace Designation 100
5.130 Multiple Code (MULTI CD) 100
5.131 Time Code (TIME CD) 100
5.132 NOTAM 101
5.133 Unit Indicator (UNIT IND) 101
5.134 Cruise Table Identifier (CRSE TBL IDENT) 101
5.135 Course FROM/TO 101
5.136 Cruise Level From/To 101
5.137 Vertical Separation 101
5.138 Time Indicator (TIME IND) 102
5.139 Intentionally Left Blank 102
5.140 Controlling Agency 102
5.141 Starting Latitude 102
5.142 Starting Longitude 102
5.143 Grid MORA 102
5.144 Center Fix (CENTER FIX) 103
5.145 Radius Limit 105
5.146 Sector Bearing (SEC BRG) 105
5.147 Sector Altitude (SEC ALT) 105
5.148 Enroute Alternate Airport (EAA) 105
5.149 Figure of Merit (MERIT) 105
5.150 Frequency Protection Distance (FREQ PRD) 105
5.151 FIR/UIR Address (ADDRESS) 106
5.152 Start/End Indicator (S/E IND) 106

viii
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
5.153 Start/End Date 106
5.154 Restriction Identifier (REST IDENT) 106
5.155 Intentionally Left Blank 106
5.156 Intentionally Left Blank 106
5.157 Airway Restriction Start/End Date (START/END DATE) 106
5.158 Intentionally Left Blank 107
5.159 Intentionally Left Blank 107
5.160 Units of Altitude (UNIT IND) 107
5.161 Restriction Altitude (REST ALT) 107
5.162 Step Climb Indicator (STEP) 107
5.163 Restriction Notes 107
5.164 EU Indicator (EU IND) 107
5.165 Magnetic/True Indicator (M/T IND) 107
5.166 Channel 108
5.167 MLS Azimuth Bearing (MLS AZ BRG) MLS Back Azimuth Bearing (MLS BAZ BRG) 108
5.168 Azimuth Proportional Angle Right/Left (AZ PRO RIGHT/LEFT) Back Azimuth Proportional 108
Angle Right/Left (BAZ PRO RIGHT/LEFT)
5.169 Elevation Angle Span (EL ANGLE SPAN) 108
5.170 Decision Height (DH) 108
5.171 Minimum Descent Height (MDH) 108
5.172 Azimuth Coverage Sector Right/Left (AZ COV RIGHT/LEFT)Back Azimuth Coverage 109
Sector Right/Left (BAZ COV RIGHT/LEFT)
5.173 Nominal Elevation Angle (NOM ELEV ANGLE) 109
5.174 Restrictive Airspace Link Continuation (LC) 109
5.175 Holding Speed (HOLD SPEED) 109
5.176 Pad Dimensions 109
5.177 Public/Military Indicator (PUB/MIL) 109
5.178 Time Zone 110
5.179 Daylight Time Indicator (DAY TIME) 110
5.180 Pad Identifier (PAD IDENT) 110
5.181 H24 Indicator (H24) 110
5.182 Guard/Transmit (G/T) 110
5.183 Sectorization (SECTOR) 111
5.184 Communication Altitude (COMM ALTITUDE) 111
5.185 Sector Facility (SEC FAC) 111
5.186 Narrative 111
5.187 Distance Description (DIST DESC) 111
5.188 Communications Distance (COMM DIST) 111
5.189 Remote Site Name 112
5.190 FIR/RDO Identifier (FIR/RDO) 112
5.191 Triad Stations (TRIAD STA) 112
5.192 Group Repetition Interval (GRI) 112
5.193 Additional Secondary Phase Factor (ASF) 112
5.194 Initial/Terminus Airport/Fix 112
5.195 Time of Operation 112
5.196 Name Format Indicator (NAME IND) 113
5.197 Datum Code (DATUM) 113
5.198 Modulation (MODULN) 113
5.199 Signal Emission (SIG EM) 114
5.200 Remote Facility (REM FAC) 114
5.201 Restriction Record Type (REST TYPE) 114
5.202 Exclusion Indicator (EXC IND) 114
5.203 Block Indicator (BLOCK IND) 114
5.204 ARC Radius (ARC RAD) 115
5.205 Navaid Limitation Code (NLC) 115
5.206 Component Affected Indicator (COMP AFFTD IND) 115
5.207 Sector From/Sector To (SECTR) 115
5.208 Distance Limitation (DIST LIMIT) 116
5.209 Altitude Limitation (ALT LIMIT) 116
5.210 Sequence End Indicator (SEQ END) 117
5.211 Required Navigation Performance (RNP) 117
5.212 Runway Gradient (RWY GRAD) 117
5.213 Controlled Airspace Type (ARSP TYPE) 117
5.214 Controlled Airspace Center (ARSP CNTR) 117

ix
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
5.215 Controlled Airspace Classification (ARSP CLASS) 118
5.216 Controlled Airspace Name (ARSP NAME) 118
5.217 Controlled Airspace Indicator (CTLD ARSP IND) 118
5.218 Geographical Reference Table Identifier (GEO REF TBL ID) 118
5.219 Geographical Entity (GEO ENT) 118
5.220 Preferred Route Use Indicator (ET IND) 119
5.221 Aircraft Use Group (ACFT USE GP) 119
5.222 GPS/FMS Indicator (GPS/FMS IND) 119
5.223 Operations Type (OPS TYPE) 120
5.224 Route Indicator (RTE IND) 120
5.225 Ellipsoidal Height 120
5.226 Glide Path Angle (GPA) 120
5.227 Orthometric Height (ORTH HGT) 120
5.228 Course Width at Threshold (CRSWDTH) 120
5.229 Final Approach Segment DATA CRC Remainder (FAS CRC) 121
5.230 Procedure Type (PROC TYPE) 121
5.231 Along Track Distance (ATD) 121
5.232 Number of Engines Restriction (NOE) 121
5.233 Turboprop/Jet Indicator (TURBO) 121
5.234 RNAV Flag (RNAV) 122
5.235 ATC Weight Category (ATC WC) 122
5.236 ATC Identifier (ATC ID) 122
5.237 Procedure Description (PROC DESC) 122
5.238 Leg Type Code (LTC) 122
5.239 Reporting Code (RPT) 122
5.240 Altitude (ALT) 123
5.241 Fix Related Transition Code (FRT Code) 123
5.242 Procedure Category (PRO CAT) 123
5.243 GLS Station Identifier 123
5.244 GLS Channel 123
5.245 Service Volume Radius 123
5.246 TDMA Slots 124
5.247 Station Type 124
5.248 Station Elevation WGS84 124
5.249 Longest Runway Surface Code (LRSC) 124
5.250 Alternate Record Type (ART) 124
5.251 Distance To Alternate (DTA) 124
5.252 Alternate Type (ALT TYPE) 125
5.253 Primary and Additional Alternate Identifier (ALT IDENT) 125
5.254 Fixed Radius Transition Indicator (FIXED RAD IND) 125
5.255 SBAS Service Provider Identifier (SBAS ID) 125
5.256 Reference Path Data Selector (REF PDS) 125
5.257 Reference Path Identifier (REF ID) 125
5.258 Approach Performance Designator (APD) 125
5.259 Length Offset (OFFSET) 125
5.260 Terminal Procedure Flight Planning Leg Distance (LEG DIST) 126
5.261 Speed Limit Description 126
5.262 Approach Type Identifier (ATI) 126
5.263 HAL 126
5.264 VAL 126
5.265 Path Point TCH 126
5.266 TCH Units Indicator 127
5.267 High Precision Latitude (HPLAT) 127
5.268 High Precision Longitude (HPLONG) 127
5.269 Helicopter Procedure Course (HPC) 127
5.270 TCH Value Indicator (TCHVI) 127
5.271 Procedure Turn (PROC TURN) 127
5.272 TAA Sector Identifier 127
5.273 TAA IAF Waypoint 128
5.274 TAA Sector Radius 128

FIGURES

5-1 Section and Subsection Encoding Scheme 56

x
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
5-2 Geographic Area Codes 57
5-3 Transition Identifier Field Content 61
5-4 Waypoint Description 64
5-5 7 Subdivisions for United States 66
5-6 Boundary Codes 67
5-7 Procedure Use 69
5-8 Navigation Reference Points 76
5-9 Runway Plan Use 83
5-10 Holding Pattern Leg Length 84
5-11 Company Route Record (R) Field Content 87
5-12 Controlled and Restrictive Airspace and FIR/UIR Boundaries 99
5-13 GRID MORA Sample 104
5-14 Precision Approach Path Points 120
ITEM

6.0 ENCODING STANDARDS 129

6.1 General 129
6.2 Number of Tape Tracks 129
6.2.1 Header Record 1 129
6.2.2 Header Record 2 130
6.2.3 Additional Header Records 130
6.3 Bit Density 130
6.4 Coding 130
6.5 Parity Convention 130
6.6 Reel-File Relationship 130
6.7 Labels 130
6.7.1 Volume Header Label (VOL) 130
6.7.2 Header 1 Label (HDR 1) 130
6.7.3 Header 2 Label (HDR 2) 130
6.7.4 End-of-File Trailer Label (EOF) 130
6.7.5 End-of-Volume Trailer Label (EOV) 130
6.8 Tape Marks 130
6.9 Summary of Tape Data Layout 130
6.9.1 One File, One Reel 130
6.9.2 One File, Multiple Reels 130
6.9.3 Multiple Files, One Reel 130
6.10 CRC Calculations 130
6.10.1 Precision Approach Path Point Cyclic Redundancy Check (CRC) Overview 130
6.10.2 Generator Polynomials 131
6.10.3 32 Bit CRC Calculation 131
6.11 Application of CRC for Integrity Protection of Straight & Advanced Landing Approach 131
Operations
6.11.1 Data Block Structure, M(x) 131
6.11.2 RNAV – GPS/GLS Approach Procedure Path Point Data Field Bits 131
6.11.3 CRC – Generator Polynomial, G(x) 132

7.0 NAMING CONVENTIONS 133

7.1 General 133
7.2 Fix Identifiers 133
7.2.1 VOR, VORDME, VORTAC, TACAN, and Non-Directional Beacons (NDB) 133
7.2.2 Non-Directional Beacons (NDB) 133
7.2.2.1 Navaid Waypoint 133
7.2.2.2 Airport Waypoint 133
7.2.3 Named RNAV Waypoints, Intersections, and Reporting Points 133
7.2.4 Unnamed Waypoints 134
7.2.5 Reporting Positions Defined by Coordinates 134
7.2.6 Terminal Waypoints 136
7.3 Waypoint Name/Description 139
7.3.1 Named Waypoints 139
7.3.2 Unnamed Waypoints 139
7.3.3 Airport-Related Waypoints 140
7.3.4 Navaid Waypoint 140

xi
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
7.3.5 Airport Waypoint 140
7.3.6 VFR Waypoints 140
7.4 SID/STAR Procedure Identifiers 140
7.5 Preferred Route Identifiers 142
7.5.1 North American Routes 142
7.5.2 Multiple Routes - Same Fix 142
7.5.3 Preferred or Preferential Routes 142
7.5.4 Multiple Routes - Same Points/Areas/Regions 142
7.5.5 Preferred or Preferential Overfly Routings 142
7.5.6 Multiple Routes - Overfly 142
7.5.7 Preferred Weekday/Weekend 143
7.5.8 Weekday/Weekend 143
7.5.9 Geographical Routings 143
7.5.10 Multiple Routes - Geographical 143
7.5.11 Off Load Route 143
7.5.12 Multiple Routes - Off Load 143
7.6 Transition Identifiers 143
FIGURE

7-1 Multiple Approaches/Multiple Waypoints 138

ATTACHMENTS

1 Flow Diagram 144

2 Local Horizontal Reference DATUM Name, Datum Code, and Ellipsoid List 146
3 Navigation Data/File Data Relationship 154
4 Airway Minimum Altitudes and Required Navigation Performance (RNP) 170
5 Path and Terminator 173

Attachment 5 –
Subsections
1.0 General Rules 174
1.1 NAVAID Related Leg Types 174
1.2 Beginning And Ending Leg Types 175
1.3 Leg Sequencing 176
1.4 Leg Type Descriptions 177
1.5 Leg Data Fields 182
2.0 Coding Rules Applicable To All Procedures 183
3.0 Path and Termination Related Rules Valid For All Procedure Types 184
4.0 Standard Instrument Departure (SID) Coding Rules 188
5.0 Standard Terminal Arrival Route (STAR) Coding Rules 198
6.0 Approach Procedure Rules Valid For All Procedure Types 203
6.1 Multiple Approach Procedure Coding 203
6.2 General Rules, Applicable To All Approach Route Coding 204
6.3 Approach Transition Route Coding Rules 206
6.4 Localizer Based Approach Procedure Coding 208
6.5 MLS Approach Procedure Coding 209
6.6 VOR, VORDME, VORTAC and RNAV Approach Procedure Coding 210
6.7 TACAN Approach Procedure Coding 211
6.8 NDB Approach Procedure Coding 211
6.9 Loran Coding Rules Deleted by Supplement 14 212
6.10 Circle-to-Land Approach Procedure Coding 212
6.11 FMS and GPS Procedure Coding 213
6.12 Helicopter Procedure Coding 213
7.0 Precision Approach Procedure Coding 227
7.1 Final Approach Segment 227
7.3 GLS Precision Approach Procedure Coding 228
7.4 MLS Approach Procedure Coding 228
8.0 Non-precision Approach Procedure Coding 229
8.1 General 229

xii
 ARINC SPECIFICATION 424
TABLE OF CONTENTS
ITEM SUBJECT PAGE
8.2 Final Approach Path Coding – Localizer-Based Procedures 229
8.3 Final Approach Path Coding – VOR-Based Procedures 229
8.4 Final Approach Path Coding – NDB-Based Procedures 230
8.5 Intentionally Left Blank 231
8.6 Final Approach Path Coding – Circle-to-Land Procedures 231
8.7 Final Approach Path Coding – GNSS-Based Procedure 231
8.8 Final Approach Path Coding – Helicopter Approach Procedures 231
8.9 Vertical Navigation Path (VNAV Path) or Descent Gradient Considerations 231
8.10 VNAV Coding of Non-Precision Approach Procedures with Missed Approach Points – Other 232
Than Landing Threshold
9.0 Missed Approach Procedure Rules Valid For All Procedure Types 251
9.1 Missed Approach Point 251
9.2 First Leg of Missed Approach Procedure 251
9.3 Vertical Path of Missed Approach Procedure 251
9.5 Other Missed Approach Procedure Considerations 252

APPENDIXES

1 Chronology and Bibliography 255

2 Straight-In Criteria 258
3 Subject Index 260
ARINC IA Project Initiation/Modification (APIM) Guidelines for Submittal and ARINC End
Standard – Errata Report

xiii
 ARINC SPECIFICATION 424 – Page 1

1.0 INTRODUCTION

1.1 Purpose of this Document wish to support both airborne navigation system and flight
planning system operations can also do so without having
This document sets forth the air transport industry’s to modify this merging software. Only the flight planning
recommended standards for the preparation of airborne navigation data base systems need to take into account the
navigation system reference data files. The data on these presence of the flight planning related components in the
files are intended for merging with airborne navigation input (Specification 424) data.
computer operational software to produce media for use by
such computers on board aircraft. Since the industry does 1.2 Data Format Standardization Philosophy
not desire to standardize the operational software of these
computers, this merging process is not described in this The production of navigation data for use with onboard
document, nor do the standards set forth necessarily apply navigation computers may be viewed as a four-step
to the aircraft-employed data. process (Attachment 1). The first step is the assembly of
a data bank. The second is the production of data files
The data bases prescribed by this document are also used organized such that individual airlines’ operational needs
by computer flight planning systems, flight simulators, and can be met. The third step is the merging of these data
other applications. with the operational software of those airlines’ navigation
computers. The final step is the production of final
The purpose of the ARINC 424 Navigation System Data storage media containing these merged data for use on
Base Standard is to be an enabling document. It enables individual aircraft.
data base suppliers, avionics systems, and other users of
the data bases to fly and flight plan procedures as Data banks will contain world-wide navigation reference
prescribed by procedure designers. The document is not information obtained both from “public” sources (ICAO,
meant to be a prescriptive document for procedure governments, etc.) and from navigation system users.
designers. They could be assembled and maintained by public
bodies (e.g., government agencies or international
This document is also not a requirements document for organizations), by commercial institutions, or both. The
airborne navigation systems. information needed by an airline to make use of a
navigation system over its own routes will consist of a
Procedures that are not compatible with this data base section from the “public” part of the bank and the data it
standard in some cases cannot be coded for inclusion in requires from the “user” part of the bank. It will occupy
some airborne data bases. one of the “airline nav. data files” shown at the step 2
level in Attachment 1.
1.1.1 Coverage of Flight Simulator Needs
To facilitate the sorting process necessary to produce
Supplement 4 to this document added material related to individual airline files, every record in the data bank is
the special navigation data base needs of flight simulators. encoded as to type. Those in the “public” part of the bank
The approach taken, i.e., the definition of three new are termed “standard” records, and may appear in any
subsections to the master file and the exploitation of airline’s file. The “Master Airline User File” shown at the
previously unused continuation record capability, was step 1 level in the diagram of Attachment 1 is made up of
designed to ensure that users who wish to continue using such records. They contain the data specified in Chapter 3
the document solely as the basis for supporting airborne of this document, and are formatted according to the
navigation system operation can do so without rules set forth in Chapters 4 and 5. Records in the “user”
simulator-related records nor be concerned that the part of the bank are termed “tailored” records, and each
software used to merge Specification 424 data with one is entered into the bank to support the operations of
airborne equipment operational software will need the particular user (airline) that requires it. Chapter 4 of
modification as the result of the changes. Users who wish this document sets forth a standard format for encoding
to support both airborne navigation system and flight tailored route information, while Chapter 5 includes
simulator operations can also do so without having to definitions of certain fields used exclusively for this
modify this merging software. Only the simulator purpose.
navigation data base compilers need take into account the
presence of the simulator-related components in the input Individual airline files are used in step 3 of the airborne
(Specification 424) data. navigation system media production process. This may be
performed either by the airline itself (as may step 4), or
1.1.2 Coverage of Flight Planning Needs by an agency contracted to support the airline’s
navigation system operations, such as the airborne
Supplement 5 of this document added material related to equipment manufacturer.
the special navigation data base needs to flight planning
computer systems. The approach taken, i.e., the definition It can readily be seen that in the absence of air transport
of the new material and the exploitation of previously industry guidance, individual navigation system
unused continuation record capability, was designed to manufacturers could follow equipment design approaches
ensure that users who wish to continue using the document that impose different requirements on the format of the
solely as the basis for supporting airborne navigation navigation reference data. Although, as implied in
system operations can do so without penalty. Such users paragraph 1.1 above, the airlines do not wish
need not obtain the flight planning related records nor be unnecessarily to constrain equipment design, the cost to
concerned that the software used to merge Specification them as an industry of supporting the production of files
424 data with airborne equipment operational software will in several different formats would be prohibitively high.
need modification as the result of the changes. Users who For this reason they have produced in this document data
ARINC SPECIFICATION 424 – Page 2
1.0 INTRODUCTION

format and encoding standards to be applied in the 1.4 Reference Documentation

production of these files. These standards are not
intended to be used in the final two steps of file ARINC Characteristic 702: Flight Management
production, nor are any obligation imposed on anyone to Computer System
make use of every data element defined. In this way
manufacturers are free to optimize their hardware and ARINC Characteristic 702A: Advanced Flight
software designs as they see fit, and reference data Management Computer System
acquisition costs are minimized.
ARINC Characteristic 756: GNSS Navigation and
COMMENTARY Landing Unit (GNLU)

In some cases in this document data fields are

defined offering greater resolution than is usually
available for the data in question from the source
data bases. This is intended to reflect the airlines’
desire for the use of the best available data. It is not,
however, intended to suggest a need for special
surveys in order to provide the data to the resolutions
shown. Also, consideration of the application of the
data base described in this document, with the aim of
determining whether or not a standard earth model
reference should be defined, produced the conclusion
that such action was not necessary.

Readers should note that ARINC 424 Specification is not

a data base specification per se. It is a standard for the
preparation and transmission of data for assembly of
airborne navigation system data bases.

1.3 Organization of this Document

A glossary of data processing and special navigation

terms precedes the chapters of the document in which the
recommended standards are defined. In the first of these
chapters, the organization and content of the “master
airlines user file” (see Attachment 1) is defined. The next
chapter describes records in terms of their field structures.
Following that, individual fields are defined in terms of
the data elements from which they are constructed. Figure
1-1 pictorially relates these methods of information
presentation to the layout of data on one of the individual
airline files shown at the step 2 level in the diagram of
Attachment 1. With the file structure definition complete,
attention is turned to the encoding of data for computer
processing.

1.3.1 Coverage of Helicopter Operation Needs

Supplement 14 of this document added material related to
the special navigation database needs of rotorwing flight
operations. The approach taken was to define as “dual
use” as much of the database as possible, specifically the
ground base navigation and landing aids. These records
are defined as the Master Airline User File. Where dual
use was not possible, new content was defined as the
Master Helicopter User File. The new content was all
related directly to the heliport and flight operations into
and out of heliports. It included helicopter SIDs, STARs
and Approach Procedures and Heliport Terminal
Waypoint. Minor adjustments to the content of records
that are dual usage were required; an example would be a
new route type code for Enroute Airways dedicated to
helicopter airways. All changes were made so as to have
no impact on any other application of ARINC
Specification 424, provided database suppliers avail
themselves of the data selection capabilities built into that
revision.
 ARINC SPECIFICATION 424 – Page 3

1.0 INTRODUCTION

Record Record Record Record Record

LEVEL 2
Field

Field

Field

Field
Field
Field
Field
Field
Field
Field
Field
Field

Field

Field
Field

Field

Field

Field

Field
AIRLINES FILES
(See Attachment 1)

CHAPTER 3 defines content and organization of the Master

Airline User File (See Attachment 1)

CHAPTER 4 defines locations for fields in RECORDS

CHAPTER 5 describes FIELDS

CHAPTER 6 defines data ENCODING STANDARDS

Figure 1-1 - ARINC Specification 424 Information Presentation

ARINC SPECIFICATION 424 – Page 4

2.0 GLOSSARY OF TERMS

2.1 Data Processing Terms Nonessential Nonessential Waypoints include all other
Waypoints waypoints of an airway not included
This Section contains definitions for the data processing under Essential Waypoints.
terms used in this document. They are listed
alphabetically. Transition A waypoint which normally would be
Essential classified as non-essential might be
Waypoints required to transition from the enroute
Alpha The terms employed to describe any letter of structure to the terminal structure.
the alphabet (A through Z); any punctuation; Waypoints falling into this category are
or any printable character, other than a classified as Transition Essential
numeric, including space. Waypoints.
Character The basic human-oriented data element, e.g.,
a single letter of the alphabet or a single Final The Final Approach Course Fix (FACF)
number (0 through 9). The entry RW26L is Approach is a waypoint located on the coded final
said to consist of five characters. Course Fix approach path. For Localizer-based
(FACF) Approach procedures, the location of the
Column The spaces for data entry on each record. FACF is on the localizer beam center at a
One column can accommodate one distance of 2 to 8 NM from the coded
character. FAF. If the government source provides a
Field The collection of characters needed to define named fix on the localizer beam at a
one item of information. The entry RW26L distance of more than 8NM and this fix is
identifies “runway 26 left” and is described within the reception range of the
as a five-character field. localizer, this fix may be designated as
Numeric The term employed to describe any single the FACF. On non-localizer based
number in the range 0 through 9. procedures, the FACF will be positions
not less than 2NM from the coded FAF
Record A single line of computer data made up of on the coded final approach path.
the fields necessary to define fully a single
useful piece of data. A VORTAC station Final For all non-precision approach
record, for example, contains fields for Approach procedures, the coded FAF shall be the
station name, coordinates, frequency, Fix (FAF) fix designated by the government source
elevation, variation, ICAO code, ident code, as the procedure FAF, when one is
plus certain administrative data pertaining to published. If there is no published FAF
the record itself. for the non-precision procedure, one must
be established according to the rules in
Sub Section A collection of records of functional data Attachment Five to this Specification.
items. The records for Approach routes form For localizer-based precision approach
a subsection of the Airport data base. procedures, the coded FAF shall be either
Section The first division of the database. Each the Outer Marker (OM) associated with
section is made up of subsections as defined the localizer or, if no OM is present, at
above. the glide slope intercept point. For OM
positions that do not lie on the localizer
beam and would result in a course change
2.2 Special Navigation Terms of 3 degrees or more at the FAF, a point
shall be computed abeam the OM, on the
This section contains definitions of certain special localizer beam center.
navigation-related terms used in this Specification. They
are listed alphabetically. Enroute The “ER” to “UR” Link indicates the
Airway to physical affect of Airway to a Restrictive
ATC Essential or nonessential waypoints may Restrictive Airspace on an Enroute Airway segment
Compulsory be classified as ATC compulsory points. Airspace Link defined by the airway segment centerline.
Reporting ATC requires the pilot to make a Gateway A Gateway Fix is a waypoint associated
Point communications report at these Fix with organized track systems across large
waypoints. All other waypoints may be areas which no ATS Routes have been
classified as non-compulsory reporting established such as the Atlantic Ocean. It
points and are reported only when is coded into the database to indicate the
specifically requested by ATC. point at which a change is made from
Essential An Essential Waypoint is defined as any ATS Route flying to random track flying.
Waypoints waypoint at which a change in course is Initial An Initial Approach Fix is that fix
required or as the intersection of two or Approach Fix designated by the source document as the
more airways. (IAF) point at which the Initial Approach
Off-Route Waypoints which are not part of any segment begins. An Approach Procedure
Floating route system but are designated by the may have no IAF or multiple IAFs.
Waypoint ATC authority to be charted are
considered to be Off-Route Floating
Waypoints.
 ARINC SPECIFICATION 424 – Page 5
2.0 GLOSSARY OF TERMS

Intermediate An Intermediate Approach Fix is a point a name considered for an offset LTP.
Approach Fix and associated Intermediate Approach When used in calculations and
Segment at which the initial approach databases, it will generally be
segment can be blended into the final shown/referred to as an LTP/FTP.
approach segment. Criteria will appear in appropriate
Localizer Unless this term is specifically related to documents as the concept evolves.
a particular type of approach, it can be COMMENTARY
used as a general reference for all types
of approach facilities that provide an
electronic course guidance signal, i.e. The term RNAV-GPS/GLS is used
“localizer,” including ILS, LOC, BC, throughout this document to
IGS, LDA and SDF. reference RNAV procedures
formerly referenced as RNP
Phantom A database waypoint established during RNAV.
Waypoint procedure coding to facilitate more
accurate navigation by the Flight Flight Path The FPCP is a point above the LTP used
Management Computer than would be Control to define the vertical component of the
allowed using air-mass related Path Point (FPCP) precision final approach path. It is in
Terminators to replicate source data. The the vertical plane containing the LTP
waypoint finds use when such and FPAP. Horizontally the FPCP has
considerations as increased the same coordinates as the LTP.
environmental restrictions and the Vertically, the elevation of the FPCP is
congestion of the available airspace come the LTP elevation plus the threshold
into play. Used to permit route crossing height.
construction with “track to a fix (TF)” Flight Path The FPAP is a point used to define the
legs. Alignment lateral alignment of the vertical plane
Precision A point where the glidepath intercepts the Point (FPAP) containing the final approach path. For
Approach Fix intermediate altitude. This point is the approaches that are aligned with the
beginning of the precision final approach runway, it is located at the designated
segment. center of the opposite runway threshold
or an extension of a geodesic line
Precision A circular arc flight path between two calculated between the LTP and the
ARC known points, whose construction is designated center of the opposite
tangent to the inbound and outbound runway landing threshold. It is
paths to/from these points. positioned at a distance from the LTP to
Final The Final End Point (FEP) is a waypoint support a prescribed angular splay of
End located on the coded final approach path. lateral deviations. The FPAP is defined
Point It is located at a point defined by the by latitude and longitude. Orthometric
(FEP) intersection of the final approach course height should also be provided for
and a line perpendicular to that course compatibility with non-GNSS systems.
through the runway threshold (LTP) or The FPAP may be located beyond the
first usable landing surface for circling opposite end of the landing runway,
only procedures. It is used in non- particularly on short runways.
precision approach procedures with a Glide Path Angle The glide path angle defines the descent
published missed approach point beyond angle of the final approach path. It is
the LTP and a final approach course that defined relative to the horizontal plane,
facilitates the calculation of vertical tangent to the WGS-84 ellipsoid at the
coding as the anchor point of the vertical LTP.
angle.
Final Approach (Replacing Precision Approach Path
Mandatory Any Flight maneuver of a holding nature Segment (FAS) Point Data CRC) - An 8 character
Hold defined in a terminal procedure where CRC hexadecimal representation of the
execution is part of the source defined calculated remainder bits used to ensure
flight path. the integrity of the FAS data block
during transmission and storage.
2.3 Precision RNAV Terms Examples: 243BC649, A6934B72. See
Chapter Six of this Specification for
Landing The LTP is a point at the designated details on CRC calculations.
Threshold center of the landing runway threshold
Point/Fictitious defined by latitude, longitude, and
Threshold Point height above the WGS-84 reference
(LTP/FTP) ellipsoid. Orthometric height should also
be provided for compatibility with non-
GNSS systems. The LTP is used in
conjunction with the FPAP to determine
the lateral alignment of the vertical
plane containing the final approach path.
A “Fictitious Threshold Point (FTP)” is
ARINC SPECIFICATION 424 - Page 6

3.0 NAVIGATION DATA

3.1 User File Organization 3.2.4.12, 3.2.5, 3.2.10, 3.3.5, 3.3.6, 3.3.7 and 3.3.8
should be available in the NDB NAVAID Subsection.
The records defined in Chapter 4 of this document are
sorted such that they appear on the master file in 3.2.3 Enroute Section
alphabetical/numerical order by column. The sorting
necessary to achieve this process is as follows. Records 3.2.3.1 Enroute Waypoint Section (E), Subsection (A)
are first divided into “standard” and “tailored” groups by
the content of the first column. “Standard” or “S” records The Enroute Waypoint Subsection file should contain all
are located on the file ahead of the “tailored” or “T” named intersections defined in the enroute structure. The
records. The next columns order the “standard” records file will also contain those VFR waypoints not associated
alphabetically by AREA Code and “tailored” records by with Airports or Heliports. As a minimum, all enroute
Airline Code. After that the column content orders both waypoints referenced in Sections 3.2.3.3, 3.2.3.4, 3.2.4.4,
“standard” and “tailored” records by sections. This 3.2.4.5, 3.2.4.6, 3.2.5, 3.2.10, 3.3.5, 3.3.6 and 3.3.7
process is illustrated in Figure 3-1. Sorting continues this should be available in the Enroute Waypoint Subsection.
way, column by column, until each record is uniquely
defined. 3.2.3.2 Enroute Airway Marker Section (E), Subsection
(M)
The column number at which this occurs for each record
type may be determined by inspecting the record layout The Enroute Airway Markers Subsection file should
forms of Figure 4-1 of this document. The master file may contain all government-published airways marker
then be assembled with records located in the positions facilities.
thus defined.
3.2.3.3 Holding Patterns (E), Subsection (P)
While the sorting process is basically alphabetical, it has
to accommodate columns that are permitted to contain The Holding Pattern Subsection file should contain all
blanks or numeric characters. When this occurs, blank holding patterns shown on aeronautical charts.
characters will be sorted before numerics and numeric
characters will be sorted before alphabetic characters. 3.2.3.4 Enroute Airways Section (E), Subsection (R)

3.2 Master Airline User File Content The Enroute Airways Subsection file should contain all
government-designated airways.
3.2.1 General
3.2.3.5 Enroute Airways Restrictions Section (E),
This section of this document defines the content of each Subsection (U)
section of the Master Airline User File. As indicated in
Section 1.2 of this document, this file can be composed of The Enroute Airways Restrictions Subsection file
the “standard” records or “standard” and “tailored” contains the official altitude, time and usage restrictions
records, sorted according to the procedure set forth in for Enroute Airways referenced in Section 3.2.3.4.
Section 3.1 above.
3.2.3.6 Enroute Communications Section (E),
The Master Airline User File includes all records listed in Subsection (V)
Section 3.2.
The Enroute Communications Subsection file should
3.2.2 Navaid Section (D) contain all government-published enroute
communications facilities.
3.2.2.1 VHF Navaid Section (D), Subsection (Blank)
3.2.4 Airport Section (P)
The VHF NAVAID Subsection should contain all the
VORs, VORDMEs, VORTACs, DMEs, ILS DMEs and 3.2.4.1 Airport Reference Points Section (P), Subsection
MLS DMEs as well as all TACANs paired with civil-use (A)
VHF NAVAID frequencies. It may also contain TACANs
paired with military-use VHF frequencies for specific The Airport Reference Points subsection file should
applications. As a minimum, all VHF NAVAIDs contain reference points for all airports having at least
referenced by records in Sections 3.2.3.3, 3.2.3.4, 3.2.4.1, one hard surfaced runway. As a minimum, all airport
3.2.4.4, 3.2.4.5, 3.2.4.6, 3.2.4.11, 3.2.4.12, 3.2.5, 3.2.10, reference points referenced in Sections 3.2.3.4, 3.2.3.5
3.3.5, 3.3.6, 3.3.7 and 3.3.8 should be available in the and 3.2.5 should be included.
VHF NAVAID Subsection. ILS DMEs and MLS DMEs
included can be for either Airports or Heliports. 3.2.4.2 Airport Gates Section (P), Subsection (B)
3.2.2.2 NDB Navaid Section (D), Subsection (B) The Airport Gates Subsection should contain all gates
published in official government documents to support
The NDB NAVAID Subsection file should contain all LF the Airport referenced in Section 3.2.4. If the Airport is
and MF NDBs and selected Marine Beacons defined in provided as “standard” data, the Gates may be provided
the enroute structure. As a minimum, all Enroute NDB as “standard” or “tailored” data, depending on whether
NAVAIDs referenced by records in Sections 3.2.3.3, the gate owner and operator is the public sector or a
3.2.3.4, 3,2,3.6, 3.2.4.4, 3.2.4.5, 3.2.4.6, 3.2.4.11, specific airline. If the Airport is provided as “tailored”
data, the Gates must also be provided as “tailored” data.
 ARINC SPECIFICATION 424 - Page - 7

3.0 NAVIGATION DATA

3.2.4.3 Airport Terminal Waypoints Section (P),

Subsection (C)
The Terminal Waypoints Subsection file should contain
those waypoints necessary to support Standard Instrument
Departures (SIDs), Standard Terminal Arrival Routes
(STARs) and Approaches specified in Sections 3.2.4.4,
3.2.4.5 and 3.2.4.6, excluding the landing threshold as a
fix. The file will also contain those VFR waypoints
associated with Airports. If a waypoint is used in both the
terminal and enroute areas, it should appear in the
Enroute (EA) file.
3.2.4.4 Airport Standard Instrument Departures (SIDs)
Section (P), Subsection (D)
The SIDs Subsection file should contain all government
published SIDs from airports referenced in Section
3.2.4.1.
3.2.4.5 Airport Standard Terminal Arrival Routes
(STARs) Section (P), Subsection (E)

The STARs Subsection file should contain all

government published STARs to the airports referenced
in Section 3.2.4.1.
3.2.4.6 Airport Approaches Section (P), Subsection (F)

The Approach Route Subsection file should contain at

least one instrument approach, if published, for each
runway to the airports referenced in Section 3.2.4.1
except Radar Approaches. Approach Procedures types
have been identified and are covered by coding rules
elsewhere in this specification.
This specification originally subscribed to an approach
procedures coding system known as the Multiple
Approach Coding Concept. The concept is defined as one
approach procedure for a given reference facility to a
given single runway. For example, an ILS based and a
VOR based procedure to the same runway may be
included but not an ILS and an ILS Localizer only or a
VORDME and a VOR only to the same runway. Through
several Supplements to this specification, modifications
to this concept have been incorporated and it is now
possible to have multiples of the same reference facility
or to address reference facilities in a more specific
manner. For details see Chapter Five, Sections 5.7 and
5.10. Data Suppliers are requested to supply to either the
original or to the expanded concept.
ARINC SPECIFICATION 424 - Page 8

3.0 NAVIGATION DATA

WORLD-WIDE DATA (ALL SOURCES)

STANDARD DATA TAILORED DATA (T)

AREA CODES AIRLINE CODES

USA CAN EUR ••• ••• UAL DAL TWA ••• •••

DATA SELECTIONS

D - VHF NAVAID
E – Enroute
P – Airport
R – Company Routes

MASTER AIRLINE USER FILE A/L A/L A/L ….

Format & Content Specified in this Document #1 #2 #3
T T T T

Figure 3-1 – Data Sorting Necessary to Achieve Step 1 of FDSU File Production Process
 ARINC SPECIFICATION 424 - Page 9

3.0 NAVIGATION DATA

3.2.4.7 Airport Runway Section (P), Subsection (G) industry and other governments. Most of the items
in the pathpoint record have been finalized;
The Runway Subsection file should contain all runways however, many of the fields have not had final
referenced in Sections 3.2.4.4, 3.2.4.5 and 3.2.4.6. resolution and therefore care should be taken
before creating software for implementation. The
3.2.4.8 Airport and Heliport Localizer/Glide Slope pathpoint record continues to be included in
Section (P), Subsection (I) ARINC Specification 424 as a concept that will
have changes as the concept is matured.
The Localizer/Glide Slope Subsection file should contain
all government published localizer facilities to airport 3.2.4.15 Flight Planning Arrival/Departure Data Record
runways and/or helipad referenced in Section 3.2.4.7 or Section (P), Subsection (R)
3.3.3. As a minimum, the section should contain all
localizer facilities referenced in Sections 3.2.4.6 and The Flight Planning Arrival/Departure Data Subsection
3.3.7. should contain a set of data that meet the needs of
computerized flight planning for Arrival and Departure
3.2.4.9 Airport and Heliport MLS Section (P), designations, transitions and distances for airports
Subsection (L) referenced in Section 3.2.4.1.
The MLS Subsection file should contain all government 3.2.4.16 GNSS Landing System (GLS) Section (P),
published MLS facilities for airport runways and/or Subsection (T)
helipads referenced in Section 3.2.4.7 or 3.3.3.
The GLS Subsection file should contain all those
3.2.4.10 Airport and Heliport Marker/Localizer Section government-published GNSS Landing System approaches
(P), Subsection (M) for airport runways and/or helipads referenced in Sections
3.2.4.7 and 3.3.3. As a minimum, the section should
The Airport and Heliport Localizer Marker Subsection contain all GLS approaches referenced in Sections 3.2.4.6
file should contain all government published Markers and and 3.3.7.
locators associated with the localizers referenced in
Section 3.2.4.8. As a minimum, this Subsection should 3.2.4.17 Airport Terminal Arrival Altitude Section (P),
contain all markers referenced in Sections 3.2.4.6 and Subsection (K)
3.3.7.
The Airport TAA (Terminal Arrival Altitude) Subsection
3.2.4.11 MSA Section (P), Subsection (S) should contain the Sector Bearings, Sector Radii, and
Sector Altitudes for all government published Approach
The MSA (Minimum Sector Altitude) Subsection should Procedures referenced in Section 3.2.4.6.
contain the Sector Altitude for all government published
SIDs referenced in Section 3.2.4.4, published STARs 3.2.5 Company Route and Alternation Destination
referenced in Section 3.2.4.5 and approach procedures Section (R)
referenced in Section 3.2.4.6.
3.2.5.1 Company Route Section (R), Subsection (Blank)
3.2.4.12 Airport Communications Section (P), Subsection
(V) The Company Route information is available only as
tailored data records.
The Airport Communications Subsection file should
contain all government-published airport communications 3.2.5.2 The Alternate Record Section (R),
facilities for airports referenced in Section 3.2.4.1. Subsection (A)
3.2.4.13 Airport and Heliport Terminal NDB Section (P), The Alternate Record Section defines departure,
Subsection (N) destination or enroute alternate airports or alternate
company routes. The data is only available as tailored
The Terminal NDB Subsection file should contain those data records.
Terminal NDB NAVAIDS referenced by records in
Sections 3.2.3.3, 3.2.4.4, 3.2.4.5, 3.2.4.6, 3.2.4.11, 3.2.5, 3.2.6 Special Use Airspace Section (U)
3.2.9, 3.3.5, 3.3.6, 3.3.7 and 3.3.8. If a NDB is used in
both the terminal and enroute environments, it should 3.2.6.1 Restrictive Airspace Section (U), Subsection (R)
appear in the Enroute NDB NAVAID (DB) file.
The Restrictive Airspace Subsection should contain all
3.2.4.14 Airport and Heliport Path Point Section (P), government published restrictive airspace areas containing
Subsection (P) their lateral and vertical limits.
The Path Point Subsection file should contain the Path 3.2.6.2 FIR/UIR Section (U), Subsection (F)
Point records required to support all RNAV-GPS/GLS
Approach Procedures referenced in Sections 3.2.4.6 and The FIR/UIR Subsection file should contain all
3.3.7. government-published FIR and UIR boundaries, including
both lateral and vertical limits.
Note: The pathpoint concept is currently being
developed by the FAA in cooperation with
ARINC SPECIFICATION 424 - Page 10
3.0 NAVIGATION DATA
3.2.6.3 Controlled Airspace Section (U), Subsection (C) 3.2.7 Tables Section
3.2.8 MORA Section
The Controlled Airspace Subsection file should contain 3.2.9 Preferred Route Section
those government-published airspaces required to support 3.2.11 GLS
the specific needs of this Specification, see Chapter Five,
Section 5.217, as they relate to Airports and Heliports, Section 3.3, Master Helicopter User File will include the
including their lateral and vertical limits. following specifically used paragraphs:

3.2.7 Cruising Tables Section (T) 3.3.3 Heliport Section (H), Subsection (A)
3.3.4 Heliport Terminal Waypoint Section (H),
3.2.7.1 Cruising Tables Section (T), Subsection (C) Subsection (C) Heliport Terminal Procedure
Section (H),
The Cruising Table Subsection file should contain the 3.3.5 SID Subsection (D)
standard ICAO Cruising Level Table and all modified 3.3.6 STAR Subsection (E)
Cruising Level Tables required to support Sections 3.2.3.4 3.3.7 Approach Subsection (F)
and 3.2.6.2. 3.3.8 Heliport MSA Section (H), Subsection (S)
3.3.9 Heliport Communications Section (H),
3.2.7.2 Geographical Reference Table Section (T), Subsection (V)
Subsection (G)
3.3.3 Heliport Section (H), Subsection (A)
The Geographical Reference Table Subsection file should
contain all geographical cross reference entries required to The Heliport Subsection file should contain reference
create linkage to Preferred Route Identifiers, Section points for all government-published helipads at heliport
3.2.9, for wide area origin or destination entries. and airport facilities.

3.2.8 MORA Section (A), Subsection (S ) 3.3.4 Heliport Terminal Waypoints Section (H),
Subsection (C)
The MORA Subsection should contain all grid MORA
values for each degree of latitude and longitude. The Heliport Terminal Waypoint Subsection should
contain those waypoints necessary to support Standard
3.2.9 Preferred Routes Section (E), Subsection (T) Terminal Departures (SIDs), Standard Terminal Arrival
Routes (STARs) and Approaches specified in Sections
The Preferred Route Subsection file will contain 3.3.5, 3.3.6 and 3.3.7, excluding Helipads as a fix. The
frequently used routes (i.e., North American Preferred file will also contain those VFR waypoints associated with
Routes, North American Routes to the North Atlantic Heliports. If a waypoint is used in both the terminal area
Traffic, and Europe Preferential Route System). These and the enroute areas, is should appear in the Enroute
routes will, in effect, combine existing Subsection files (EA) file.
[SID (PD), STAR (PE), Enroute Airway (ER), Enroute
Waypoint (EA), Terminal Waypoint (PC, VHF NAVAID 3.3.5 Heliport Standard Instrument Departures (SIDs)
(D), NDB NAVAID (DB), Airport (P)] to form a Section (H), Subsection (D)
continuous route structure. This route structure may be
referenced by the Company Route records. The SIDs Subsection file should contain all government
published SIDs from Heliports referenced in Section
3.3 Master Helicopter User File Content 3.3.3.
3.3.1 General 3.3.6 Heliport Standard Terminal Arrival Routes
(STARs) Section (H), Subsection (E)
The Master Helicopter User File will incorporate the use
of records from Section 3.2, Master Airline User File as The STARs Subsection file should contain all government
well as sections unique to helicopter operations. published STARs to Heliports referenced in Section 3.3.3.

3.3.2 Jointly and Specifically Used Sections/Subsections 3.3.7 Heliport Approaches Section (H), Subsection (F)

Section 3.3, Master Helicopter User File will jointly use The Approach Route Subsection file should contain all
the following sections from Section 3.2, Master Airline government published approaches to Heliports referenced
User File: in Section 3.3.3. Approach procedure types have been
identified and are covered by coding rules elsewhere in
3.2.2 VHF Navaid Section this specification.
3.2.3 Enroute Section
3.2.4 Airport Section, but limited to Airports with 3.3.8 Heliport MSA Section (H), Subsection (S)
Helipads
3.2.4.8 Airport and Heliport Localizer/Glide Slope The MSA (Minimum Sector Altitude) Subsection should
Section contain the Sector Altitude for all government published
3.2.4.9 Airport and Heliport MLS Section SIDS referenced in Section 3.3.5, published STARs
3.2.4.10 Airport and Heliport Localizer Marker Section referenced in Section 3.3.6 and approach procedures
3.2.4.13 Airport and Heliport Terminal NDB Section referenced in Section 3.3.7.
3.2.5 Company Route Section
3.2.6 Special Use Airspace Section
 ARINC SPECIFICATION 424 - Page 11

3.0 NAVIGATION DATA

3.3.9 Heliport Communications Section (H),
Subsection (V)
The Heliport Communications Subsection file should
contain all government published heliport
communications facilities for heliports referenced in
Section 3.3.3.

3.3.10 Heliport Terminal Arrival Altitude Section (H),

Subsection (K)
The Heliport TAA (Terminal Arrival Altitude) Subsection
should contain the Sector Bearings, Sector Radii, and
Sector Altitudes for all government published Approach
Procedures referenced in Section 3.3.7.
ARINC SPECIFICATION 424 - Page 12
4.0 NAVIGATION DATA - RECORD LAYOUT
4.0.1 General 4.1.2.1 VHF NAVAID Primary Records
In an effort to describe the Master Airline and Master Column Field Name (Length) Reference
Helicopter sections, Section 4 is divided into Section 4.1
Navigation Data - Record Layout, Master Airline User 1 Record Type (1) 5.2
Content and Section 4.2 Navigation Data - Record 2 thru 4 Customer/Area Code (3) 5.3
Layout, Master Helicopter User Content. 5 Section Code (1) 5.4
6 Subsection Code (1) 5.5
Each record is made up of combinations of the fields 7 thru 10 Airport ICAO Identifier (4) 5.6
described in Chapter 5 of this document. This chapter sets 11 thru 12 ICAO Code (2) 5.14
forth the standard layout of each type of record found in 13 Blank (Spacing) (1)
the data base. These layouts are also presented 14 thru 17 VOR Identifier (4) 5.33
diagrammatically at the end of this section. Paragraphs 18 thru 19 Blank (Spacing) (2)
and Tables in the 4.1 series are the record types, which 20 thru 21 ICAO Code (2) 5.14
have been identified as being a part of Master Airline 22 Continuation Record No. (1) 5.16
User Content. Paragraphs and Tables in the 4.2 series are 23 thru 27 VOR Frequency (5) 5.34
the record types, which have been identified as being part 28 thru 32 NAVAID Class (5) 5.35
of the Master Helicopter User Content. This paragraph 33 thru 41 VOR Latitude (9) 5.36
and table numbering system does not prevent any given 42 thru 51 VOR Longitude (10) 5.37
data base from including any of the records defined in this 52 thru 55 DME Ident (4) 5.38
document. The separation is for editorial and reference 56 thru 64 DME Latitude (9) 5.36
purposes only. 65 thru 74 DME Longitude (10) 5.37
75 thru 79 Station Declination (5) 5.66
Each record contains 132 character positions or columns. 80 thru 84 DME Elevation (5) 5.40
Not all of these are used in every record. Some are left 85 Figure of Merit (1) 5.149
blank to permit like information to appear in the same 86 thru 87 ILS/DME Bias (2) 5.90
columns of different records and others are reserved for the 88 thru 90 Frequency Protection (3) 5.150
possible future expansion of the record’s content. In the 91 thru 93 Datum Code (3) 5.197
tables that follow, the former are identified by the term 94 thru 123 VOR Name (30) 5.71
“Blank (Spacing)” under the “Field” heading. The latter are 124 thru 128 File Record No. (5) 5.31
identified by the term “Reserved,” followed by the function 129 thru 132 Cycle Date (4) 5.32
for which the reservation is made (where it can specifically
be stated). 4.1.2.2 VHF NAVAID Continuation Records

The tables show the record columns occupied by each field. Column Field Name (Length) Reference
For convenience, the number of characters in each field is
shown in brackets following the field name. Also, the 1 thru 21 Fields as on Primary Records
paragraph numbers in Chapter 5 of this document wherein 22 Continuation Record No. (1) 5.16
individual fields are defined are referenced. Each table 23 Application Type (1) 5.91
appears under a paragraph heading that is followed by the 24 thru 92 Notes (69) 5.61
data base section and subsection codes employed in the 93 thru 123 Reserved (Expansion) (31)
record described. 124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
4.1 Master Airline User File
4.1.2.3 VHF NAVAID Simulation Continuation Records
4.1.2 VHF NAVAID Record (D)
Column Field Name (Length) Reference
The VHF NAVAID file contains details of all VOR,
VOR/DME, VORTAC, DME and TACAN stations within 1 thru 21 Fields as on Primary Records
the geographical area of interest. For VOR and TACAN 22 Continuation Record No. (1) 5.16
stations having the same identifier but different operating 23 Application Type (1) 5.91
frequencies, the TACAN is available and the VOR is 24 thru 27 Blank (Spacing) (4)
suppressed unless the VOR is required to support Sections 28 thru 32 Facility Characteristics (5) 5.93
3.2.3.3, 3.2.3.4, 3.2.4.4, 3.2.4.5, 3.2.4.6, 3.2.4.11, 3.2.5, 33 thru 74 Reserved (Spacing) (42)
3.2.9, 3.3.5, 3.3.6, 3.3.7 or 3.3.8. In such cases the VOR 75 thru 79 Magnetic Variation (5) 5.39
is available and the TACAN is suppressed. 80 thru 84 Facility Elevation (5) 5.92
85 thru 123 Reserved (Expansion) (39)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
 ARINC SPECIFICATION 424 - Page 13

4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.2.4 VHF NAVAID Flight Planning Continuation

Records
Column Field Name (Length) Reference
This Continuation Record is used to indicate the FIR and 1 thru 21 Fields as on Primary Records
UIR within which the VHF NAVAID defined in the 22 Continuation Record No. (1) 5.16
Primary Record is located and the Start/End validity 23 Application Type (1) 5.91
dates/times of the Primary Record. 24 Navaid Limitation Code (1) 5.205
25 Component Affected Indicator (1) 5.206
26 thru 27 Sequence Number (2) 5.12
Column Field Name (Length) Reference
28 thru 29 Sector From/Sector To (2) 5.207
1 thru 21 Fields as on Primary Records 30 Distance Description (1) 5.187
22 Continuation Record No. (1) 5.16 31 thru 36 Distance Limitation (6) 5.208
23 Application Type (1) 5.91 37 Altitude Description (1) 5.29
24 thru 27 FIR Identifier (4) 5.116 38 thru 43 Altitude Limitation (6) 5.209
28 thru 31 UIR Identifier (4) 5.116 44 thru 45 Sector From/Sector To (2) 5.207
32 Start/End Indicator (1) 5.152 46 Distance Description (1) 5.187
33 thru 43 Start/End Date (11) 5.153 47 thru 52 Distance Limitation (6) 5.208
44 thru 123 Reserved (Expansion)(80) 53 Altitude Description (1) 5.29
124 thru 128 File Record No. (5) 5.31
54 thru 59 Altitude Limitation (6) 5.209
129 thru 132 Cycle Date (4) 5.32
60 thru 61 Sector From/Sector To (2) 5.207
62 Distance Description (1) 5.187
4.1.2.5 VHF NAVAID Flight Planning Continuation 63 thru 68 Distance Limitation (6) 5.208
Records 69 Altitude Description (1) 5.29
70 thru 75 Altitude Limitation (6) 5.209
This Continuation Record is used to indicate the fields of 76 thru 77 Sector From/Sector To (2) 5.207
the Primary Record that are changed. Used in conjunction 78 Distance Description (1) 5.187
with Section 4.1.2.4. 79 thru 84 Distance Limitation (6) 5.208
85 Altitude Description (1) 5.29
Column Field Name (Length) Reference 86 thru 91 Altitude Limitation (6) 5.209
92 thru 93 Sector From/Sector To (2) 5.207
1 thru 21 Fields as on Primary Records
94 Distance Description (1) 5.187
22 Continuation Record No. (1) 5.16
95 thru 100 Distance Limitation (6) 5.208
23 thru 123 Fields as on Primary Records (101)
101 Altitude Description (1) 5.29
124 thru 128 File Record No. (5) 5.31
102 thru 107 Altitude Limitation (6) 5.209
129 thru 132 Cycle Date (4) 5.32
108 Sequence End Indicator (1) 5.210
109 thru 123 Blank (Spacing) (15)
Note: Flight Planning continuation records are 124 thru 128 File Record No. (5) 5.31
designed to carry off-cycle updates to the 129 thru 132 Cycle Date (4) 5.32
primary record, and cannot carry an Application
Type column.
4.1.3 NDB NAVAID Record (DB or PN)
4.1.2.6 VHF NAVAID Limitation Continuation Record
The Enroute NDB NAVAID file (DB) contains all
This Continuation Record is used to provide details on enroute on-airway and off-airway NDBs within the
signal limitations of the VHF Navaid contained in the geographical area of interest. The Terminal NDB
Primary Record Section 4.1.2.1. Note that multiple NAVAID file (PN) contains NDBs associated with the
records formatted as in Section 4.1.2.6 may be included Airports contained in Subsection 3.2.4.1 and Heliport
for a single Primary Record. As “Service Volume” or contained in Section 3.3.3. Terminal NDBs referenced to
“Designated Operational Coverage” may also be two or more Airports or Heliports will be available in the
considered limitations, this information is also provided Enroute NDB Subsection unless that handling would
for each navaid listed in the Primary Records, where such create duplicate NDB identifiers within that Subsection.
information is available. Marine Beacons shown on aeronautical charts may also be
included in this record type.
ARINC SPECIFICATION 424 - Page 14
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.3.1 NDB NAVAID Primary Records 4.1.3.4 NDB NAVAID Flight Planning Continuation
Records
Columns Field Name (Length) Reference
This Continuation Record is used to indicate the FIR and
1 Record Type (1) 5.2 UIR within which the NDB NAVAID defined in the
2 thru 4 Customer/Area Code (3) 5.3 Primary Record is located and the Start/End validity
5 Section Code (1) 5.4 dates/times of the Primary Record.
6 Subsection Code (1) 5.5
7 thru 10 Airport ICAO Identifier (4) 5.6
11 thru 12 ICAO Code (2) 5.14 Columns Field Name (Length) Reference
13 Blank (Spacing) (1) 1 thru 21 Fields as on Primary Records
14 thru 17 NDB Identifier (4) 5.33 22 Continuation Record No. (1) 5.16
18 thru 19 Blank (Spacing) (2) 23 Application Type (1) 5.91
20 thru 21 ICAO Code (2) 5.14 24 thru 27 FIR Identifier (4) 5.116
22 Continuation Record No. (1) 5.16 28 thru 31 UIR Identifier (4) 5.116
23 thru 27 NDB Frequency (5) 5.34 32 Start/End Indicator (1) 5.152
28 thru 32 NDB Class (5) 5.35 33 thru 43 Start/End Date 911) 5.153
33 thru 41 NDB Latitude (9) 5.36 44 thru 123 Reserved (Expansion( (80)
42 thru 51 NDB Longitude (10) 5.37 124 thru 128 File Record No. (5) 5.31
52 thru 74 Blank (Spacing) (23) 129 thru 132 Cycle Date (4) 5.32
75 thru 79 Magnetic Variation (5) 5.39
80 thru 85 Blank (Spacing) (6) 4.1.3.5 NDB NAVAID Flight Planning Continuation
86 thru 90 Reserved (Expansion) (5) Records
91 thru 93 Datum Code (3) 5.197
94 thru 123 NDB Name (30) 5.71 This Continuation Record is used to indicate the fields of
124 thru 128 File Record No. (5) 5.31 the Primary Record that are changed. Used in conjunction
129 thru 132 Cycle Data (4) 5.32 with Section 4.1.3.4.

4.1.3.2 NDB NAVAID Continuation Records Column Field Name (Length) Reference
1 thru 21 Fields as on Primary Records
Columns Field Name (Length) Reference 22 Continuation Record No. (1) 5.16
1 thru 21 Fields as on Primary Records 23 thru 123 Fields as on Primary Records
22 Continuation Record No. (1) 5.16 24 thru 128 File Record No. (5) 5.31
23 Application Type (1) 5.91 129 thru 132 Cycle Date (4) 5.32
24 thru 92 Notes (69) 5.61
93 thru 123 Reserved (Expansion) (31) Note: Flight Planning continuation records are
124 thru 128 File Record No. (5) 5.31 designed to carry off-cycle updates to the
129 thru 132 Cycle Data (4) 5.32 primary record, and cannot carry an Application
Type column.
4.1.3.3 NDB NAVAID Simulation Continuation Record
4.1.4 Waypoint Record (EA ) or (PC )
Columns Field Name (Length) Reference
1 thru 21 Fields as on Primary Records The Enroute Waypoint file (EA) contains all enroute on-
22 Continuation Record No. (1) 5.16 airway and off-airway waypoints within a desired
23 Application Type (1) 5.91 geographical area. The Airport Terminal Waypoint file
24 thru 27 Blank (Spacing) (4) (PC) contains all terminal waypoints and VFR waypoints
28 thru 32 Facility Characteristics (5) 5.93 within the geographical area of each airport. Airport
33 thru 79 Reserved (Spacing) (47) Terminal Waypoints utilized by two or more airports will
80 thru 84 Facility Elevation (5) 5.92 be stored in the Enroute Waypoint Subsection (EA) to
85 thru 123 Reserved (Expansion) (39) eliminate duplication. Terminal Waypoints used jointly by
124 thru 128 File Record No. (5) 5.31 an airport and a heliport are also stored in the Enroute
129 thru 132 Cycle Data (4) 5.32 Waypoint file. The Enroute Waypoint File will contain
waypoints established for Helicopter Airways. For
Heliport Terminal Waypoints (HC) see Section 4.2.2.
 ARINC SPECIFICATION 424 - Page 15

4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.4.1 Waypoint Primary Records 4.1.4.3 Waypoint Flight Planning Continuation Records

Column Field Name (Length) Reference This Continuation Record is used to indicate the FIR and
1 Record Type (1) 5.2
UIR within which the Waypoint defined in the Primary
2 thru 4 Customer/Area Code (3) 5.3
Record is located and the Start/End validity dates/times of
5 Section Code (1) 5.4
the Primary Record.
6 Subsection Code (1) 5.5 Note 1
7 thru 10 Region Code (4) 5.41 Note 2 Column Field Name (Length) Reference
11 thru 12 ICAO Code (2) 5.14
13 Subsection (1) 5.5 Note 1 1 thru 21 Fields as on Primary Records
14 thru 18 Waypoint Identifier (5) 5.13 22 Continuation Record No. (1) 5.16
19 Blank (Spacing) (1) 23 Application Type (1) 5.91
20 thru 21 ICAO Code (2) 5.14 24 thru 27 FIR Identifier (4) 5.116
22 Continuation Record No. (1) 5.16 28 thru 31 UIR Identifier (4) 5.116
23 thru 26 Blank (Spacing) (4) 32 Start/End Indicator (1) 5.152
27 thru 29 Waypoint Type (3) 5.42 33 thru 43 Start/End Date (11) 5.153
30 thru 31 Waypoint Usage (2) 5.82 44 thru 123 Reserved (Expansion) (80)
32 Blank (Spacing) (1) 124 thru 128 File Record No. (5) 5.31
33 thru 41 Waypoint Latitude (9) 5.36 129 thru 132 Cycle Date (4) 5.32
42 thru 51 Waypoint Longitude (10) 5.37
52 thru 74 Blank (Spacing) (23) 4.1.4.4 Waypoint Flight Planning Continuation Records
75 thru 79 Dynamic Mag. Variation (5) 5.39
80 thru 84 Reserved (Expansion) (5) This Continuation Record is used to indicate the fields of
85 thru 87 Datum Code (3) 5.197 the Primary Record that are changed. Used in conjunction
88 thru 95 Reserved (Expansion) (8) with Section 4.1.4.3.
96 thru 98 Name Format Indicator (3) 5.196
99 thru 123 Waypoint Name/ Description (25) 5.43 Column Field Name (Length) Reference
124 thru 128 File Record No. (5) 5.31
1 thru 21 Fields as on Primary Records
129 thru 132 Cycle Date (4) 5.32
22 Continuation Record No. (1) 5.16
23 thru 123 Fields as on Primary Records (101)
Note 1: In Enroute Waypoint Records, the Subsection 124 thru 128 File Record No. (5) 5.31
Code occupies column 6, with column 13 blank. In 129 thru 132 Cycle Date (4) 5.32
Airport or Heliport Terminal Waypoint Records,
the Subsection Code occupies Column 13, with Note: Flight Planning continuation records are
column 6 blank. designed to carry off-cycle updates to the
primary record, and cannot carry an Application
Note 2: In Enroute Waypoint Records the code “ENRT” is Type column.
used. In Terminal Waypoint records, the region
code field contains the Airport ICAO 4.1.5 Holding Pattern Records (EP)
Identification code.
The Enroute Holding Patterns contained in this file are
4.1.4.2 Waypoint Continuation Records holding patterns recommended by the official government
authority for inclusion on enroute aeronautical charts. The
Columns Field Name (Length) Reference Terminal Holding Patterns included in this file are
1 thru 21 Fields as on Primary Records holding patterns recommended for aeronautical charts for
22 Continuation Record No. (1) 5.16 the geographical area of an airport or heliport. The type,
23 Application Type (1) 5.91 Enroute or Terminal, will be determined by the
24 thru 92 Notes (69) 5.61 Subsection of the fix upon which the holding is
93 thru 123 Reserved (Expansion) (31) predicated.
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Data (4) 5.32
ARINC SPECIFICATION 424 - Page 16
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.5.1 Holding Pattern Primary Records 4.1.6 Enroute Airways Records (ER)

Column Field Name (Length) Reference The Enroute Airways file will contain the sequential listing
1 Record Type (1) 5.2 of officially published airways and other established ATS
2 thru 4 Customer/Area Code (3) 5.3 Routes by geographical areas. The file also contains
5 Section Code (1) 5.4 published airways specific to helicopter operations.
6 Subsection Code (1) 5.5
7 thru 10 Region Code (4) 5.41 Note 1 4.1.6.1 Enroute Airways Primary Records
11 thru 12 ICAO Code (2) 5.14 Note 1
13 thru 27 Blank (Spacing) (15) Column Field Name (Length) Reference
28 thru 29 Duplicate Identifier (2) 5.114 1 Record Type (1) 5.2
30 thru 34 Fix Identifier (5) 5.13 2 thru 4 Customer/Area Code (3) 5.3
35 thru 36 ICAO Code (2) 5.14 5 Section Code (1) 5.4
37 Section Code (1) 5.4 6 Subsection Code (1) 5.5
38 Subsection Code (1) 5.5 7 thru 13 Blank (Spacing) (7)
39 Continuation Record No. (1) 5.16 14 thru 18 Route Identifier (5) 5.8
40 thru 43 Inbound Holding Course (4) 5.62 19 Reserved (1) Note 1
44 Turn Direction (1) 5.63 20 thru 25 Blank (Spacing) (6)
45 thru 47 Leg Length (3) 5.64 26 thru 29 Sequence Number (4) 5.12
48 thru 49 Leg Time (2) 5.65 30 thru 34 Fix Identifier (5) 5.13
50 thru 54 Minimum Altitude (5) 5.30 35 thru 36 ICAO Code (2) 5.14
55 thru 59 Maximum Altitude (5) 5.127 37 Section Code (1) 5.4
60 thru 62 Holding Speed (3) 5.175 38 Subsection (1) 5.5
63 thru 65 RNP (3) 5.211 39 Continuation Record No. (1) 5.16
66 thru 71 Arc Radius (6) 5.204 40 thru 43 Waypoint Description Code (4) 5.17
72 thru 98 Reserved (Expansion) (27) 44 Boundary Code (1) 5.18
99 thru 123 Name (25) 5.60 45 Route Type (1) 5.7
124 thru 128 File Record No. (5) 5.31 46 Level (1) 5.19
129 thru 132 Cycle Date (4) 5.32 47 Direction Restriction (1) 5.115
48 thru 49 Cruise Table Indicator (2) 5.134
Note1: In Enroute Fix Holding Pattern records, the code 50 EU Indicator (1) 5.164
of “ENRT” is used in the Region Code field and 51 thru 54 Recommended NAVAID (4) 5.23
the ICAO Code field is blank. In Terminal Fix 55 thru 56 ICAO Code (2) 5.14
Holding Records, the Region Code field contains 57 thru 59 RNP (3) 5.211
the identifier of the Airport or Heliport with 60 thru 62 Blank (Spacing) (3)
which the holding is associated. The ICAO Code 63 thru 66 Theta (4) 5.24
field will not be blank. This information will 67 thru 70 Rho (4) 5.25
uniquely identify the Terminal NDB, Airport 71 thru 74 Outbound Magnetic Course (4) 5.26
Terminal Waypoint or Heliport Terminal 75 thru 78 Route Distance From (4) 5.27
Waypoint. 79 thru 82 Inbound Magnetic Course (4) 5.28
83 Blank (Spacing) (1)
4.1.5.2 Holding Pattern Continuation Records 84 thru 88 Minimum Altitude (5) 5.30
89 thru 93 Minimum Altitude (5) 5.30
94 thru 98 Maximum Altitude (5) 5.127
Column Field Name (Length) Reference
99 thru 101 Fix Radius Transition Indicator (3) 5.254
1 thru 38 Fields as on Primary Records 102 thru 123 Reserved (Expansion) (22)
39 Continuation Record No. (1) 5.16 124 thru 128 File Record No (5) 5.31
40 Application Type (1) 5.91 129 thru 132 Cycle Date (4) 5.32
41 thru 109 Notes (69) 5.61
110 thru 123 Reserved (Expansion) (14) Note 1: The standard length for the Route Identifier is five
124 thru 128 File Record No. (5) 5.31 characters. Some users envisage the need for a
129 thru 132 Cycle Date (4) 5.32 six-character field. This reserved column will
permit this usage. Some data suppliers may use
this position for the ATS Service suffix associated
with some Route Identifiers.
 ARINC SPECIFICATION 424 - Page 17

4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.6.2 Enroute Airways Continuation Records

Column Field Name (Length) Reference
Column Field Name (Length) Reference
1 thru 38 Fields as on Primary Records 1 thru 38 Fields as on Primary Records
39 Continuation Record No. (1) 5.16 39 Continuation Record No. (1) 5.16
40 Application Type (1) 5.91 40 thru 123 Fields as on Primary Records
41 thru 109 Notes (69) 5.61
122 thru 128 Field Record No. (5) 5.31
110 thru 23 Reserved (Expansion) (14)
124 thru 128 File Record No. (5) 5.31 129 thru 132 Cycle Date (4) 5.32
129 thru 132 Cycle Date (4) 5.32
Note: Flight Planning continuation records are
4.1.6.3 Enroute Airways Flight Planning Continuation designed to carry off-cycle updates to the
Records primary record, and cannot carry an Application
Type column.
This Continuation Record is used to indicate the Start/End
validity times of the Primary Record, and to indicate 4.1.7 Airport Records (PA)
restrictive airspace that affects the Primary Record
according to the definition given in Section 2.0, Glossary of This file contains airport information for all airports within
Terms. the desired geographical reference area and meeting other
criteria on available runways. Additionally, the file
Column Field Name (Length) Reference contains all airports required to support Enroute Airway
1 thru 38 Fields as on Primary Records structure coding for those areas where Airport reference
39 Continuation Record No. (1) 5.16 points are used as enroute airway fixes.
40 Application Type (1) 5.91
41 Start/End Indicator (1) 5.152 4.1.7.1 Airport Primary Records
42 thru 52 Start/End Date (11) 5.153
53 thru 66 Blank (Spacing) (14)
67 thru 68 Restr. Airspace ICAO Code (2) 5.14 Column Field Name (Length) Reference
69 Restr. Airspace Type (1) 5.128 1 Record Type (1) 5.2
70 thru 79 Restr. Airspace Designation (10) 5.129 2 thru 4 Customer/Area Code (3) 5.3
80 Restr. Airspace Multiple Code (1) 5.130 5 Section Code (1) 5.4
81 thru 82 Restr. Airspace ICAO Code (2) 5.14 6 Blank (Spacing) (1)
83 Restr. Airspace Type (1) 5.12 7 thru 10 Airport ICAO Identifier (4) 5.6
84 thru 93 Restr. Airspace Designation (10) 5.129 11 thru 12 ICAO Code (2) 5.14
94 Restr. Airspace Multiple Code (1) 5.130 13 Subsection Code (1) 5.5
95 thru 96 Restr. Airspace ICAO Code (2) 5.14 14 thru 16 ATA/IATA Designator (3) 5.107
97 Restr. Airspace Type (1) 5.12 17 thru 18 Reserved (Expansion) (2)
98 thru 107 Restr. Airspace Designation (10) 5.129 19 thru 21 Blank (Spacing) (3)
108 Restr. Airspace Multiple Code (1) 5.130 22 Continuation Record Number (1) 5.16
109 thru 110 Restr. Airspace ICAO Code (2) 5.14 23 thru 27 Speed Limit Altitude (5) 5.73
111 Restr. Airspace Type (1) 5.128 28 thru 30 Longest Runway (3) 5.54
112 thru 121 Restr. Airspace Designation (10) 5.129
31 IFR Capability (1) 5.108
122 Restr. Airspace Multiple Code (1) 5.130
32 Longest Runway Surface Code (1) 5.249
123 Restr. Airspace Link Continuation (1) 5.174
33 thru 41 Airport Reference Pt. Latitude (9) 5.36
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32 42 thru 51 Airport Reference Pt. Longitude (10) 5.37
52 thru 56 Magnetic Variation (5) 5.39
57 thru 61 Airport Elevation (5) 5.55
4.1.6.4 Enroute Airways Flight Planning Continuation
62 thru 64 Speed Limit (3) 5.72
Records
65 thru 68 Recommended Navaid (4) 5.23
69 thru 70 ICAO Code (2) 5.14
This Continuation Record is used to indicate the fields of
71 thru 75 Transitions Altitude (5) 5.53
the Primary Records that are changed when used in
76 thru 80 Transition Level (5) 5.53
conjunction with Start/End Indication in Section 4.1.6.3,
81 Public/Military Indicator (1) 5.177
or to indicate additional Enroute Airway to Restrictive
82 thru 84 Time Zone (3) 5.178
Airspace links in continuation of Section 4.1.6.3. In this
85 Daylight Indicator (1) 5.179
latter case, fields are defined as in Section 4.1.6.3, except
86 Magnetic/True Indicator (1) 5.165
that columns 41 through 52 are always blank.
87 thru 89 Datum Code (3) 5.197
90 thru 93 Reserved (Expansion) (4)
94 thru 123 Airport Name (30) 5.71
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 18
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.7.2 Airport Continuation Records 4.1.8 Airport Gate Records (PB)

Column Field Name (Length) Reference This file contains passenger gate information.
1 thru 21 Field as on Primary Records 4.1.8.1 Airport Gate Primary Record
22 Continuation Record No. (1) 5.16
23 Application Type (1) 5.91 Column Field Name (Length) Reference
24 thru 92 Notes (69) 5.61 1 Record Type (1) 5.2
93 thru 123 Reserved (Expansion) (59) 2 thru 4 Customer/Area Code (3) 5.3
124 thru 128 File Record No. (5) 5.31 5 Section Code (1) 5.4
129 thru 132 Cycle Date (4) 5.32 6 Blank (Spacing) (1)
7 thru 10 Airport ICAO Identifier (4) 5.6
4.1.7.3 Airport Flight Planning Continuation Records 11 thru 12 ICAO Code (2) 5.14
13 Subsection Code (1) 5.5
This Continuation Record is used to indicate the FIR and 14 thru 18 Gate Identifier (5) 5.56
UIR within which the Airport define in the Primary 19 thru 21 Blank (Spacing) (3)
Record resides in and the Start/End validity dates/times of 22 Continuation Record No. (1) 5.16
the Primary Record and provide an indication if the 23 thru 32 Blank (Spacing) (10)
Airport defined in the Primary Record is associated with 33 thru 41 Gate Latitude (9) 5.36
Controlled Airspace. 42 thru 51 Gate Longitude (10) 5.37
52 thru 98 Reserved (Expansion) (47)
99 thru 123 Name (25) 5.60
Column Field Name (Length) Reference 124 thru 128 File Record No. (5) 5.31
1 thru 21 Fields as on Primary Records 129 thru 132 Cycle Date (4) 5.32
22 Continuation Record No. (1) 5.16
23 Application Type (1) 5.91 4.1.8.2 Airport Gate Continuation Records
24 thru 27 FIR Identifier (4) 5.116
28 thru 31 UIR Identifier (4) 5.116
32 Start/End Indicator (1) 5.152 Column Field Name (Length) Reference
33 thru 43 Start/End Date (11) 5.153 1 thru 21 Field as on Primary Records
44 thru 66 Blank (Spacing) (23) 22 Continuation Record No. (1) 5.16
67 Controlled A/S Indicator (1) 5.217
68 thru 71 Controlled A/S Arpt Ident (4) 5.6 23 Application Type (1) 5.91
72 thru 73 Controlled A/S Arpt ICAO (2) 5.14 24 thru 92 Notes (69) 5.61
74 thru 123 Blank (Spacing) (50) 93 thru 123 Reserved (Expansion) (59)
124 thru 128 File Record No. (5) 5.31 124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Data (4) 5.32
129 thru 132 Cycle Date (4) 5.32
4.1.7.4 Airport Flight Planning Continuation Records

This Continuation Record is used to indicate the fields of 4.1.9 Airport SID/STAR/Approach (PD, PE and PF)
the Primary Record that are changed. Used in conjunction
Airport SID/STAR/Approach Records comprise three files,
with Section 4.7.3. (PD) for SIDs, (PE) for STARs and (PF) for Approaches.
The SID File contains the sequential listing of published
Column Field Name (Length) Reference
Airport Standard Instrument Departures. The STAR File
1 thru 21 Fields as on Primary Records contains the sequential listing of published Airport Standard
22 Continuation Record No. (1) 5.16 Terminal Arrival Routes. The Approach File contains the
23 thru 123 Fields as on Primary Records sequential listing of published approach procedures.
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32

This Continuation Record is used to indicate the fields on

the Primary Record that have changed, used in conjunction
with Section 4.1.7.3.

Note: Flight Planning continuation records are designed

to carry off-cycle updates to the primary record,
and cannot carry an Application Type column.
 ARINC SPECIFICATION 424 - Page 19

4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.9.1 Airport SID/STAR/Approach Primary Records Note 2: Columns 119 and 120 (Apch Route Qualifier 1
and 2) are required to match the Primary Record
to the Continuation Record. This non-standard
Column Field Name (Length) Reference
sorting sequence was selected to preserve the
1 Record Type (1) 5.2 Primary Record for SID/STAR/Approach
2 thru 4 Customer/Area Code (3) 5.3 Records as much as possible as these new fields
5 Section Code (1) 5.4 were introduced in Supplement 14.
6 Blank (Spacing) (1)
7 thru 10 Airport Identifier (4) 5.6 Note 3: When columns 107 thru 116 are providing a
11 thru 12 ICAO Code (2) 5.14 reference to a MSA or the center fix for an RF
13 Subsection Code (1) 5.5 leg, all of the columns are used. When they are
14 thru 19 SID/STAR/Approach Identifier (6) 5.9, 5.10 providing a reference to a TAA, only columns
20 Route Type (1) 5.7 107 thru 112 are used and 113 thru 116 are
21 thru 25 Transition Identifier (5) 5.11 blank.
26 Blank (Spacing) (1)
27 thru 29 Sequence Number (3) 5.12 4.1.9.2 Airport SID/STAR/Approach Continuation
30 thru 34 Fix Identifier (5) 5.13 Records
35 thru 36 ICAO Code (2) 5.14
37 Section Code (1) 5.4
38 Subsection Code (1) 5.5 Column Field Name (Length) Reference
39 Continuation Record Number (1) 5.16 1 thru 38 Fields as on Primary Records
40 thru 43 Waypoint Description Code (4) 5.17 39 Continuation Record Number (1) 5.16
44 Turn Direction (1) 5.20 40 Application Type (1) 5.91
45 thru 47 RNP (3) 5.211 41 thru 44 CAT A Decision Height (4) 5.170
48 thru 49 Path and Termination (2) 5.21 45 thru 48 CAT B Decision Height (4) 5.170
50 Turn Direction Valid (1) 5.22 49 thru 52 CAT C Decision Height (4) 5.170
51 thru 54 Recommended Navaid (4) 5.23 53 thru 56 CAT D Decision Height (4) 5.170
55 thru 56 ICAO Code (2) 5.14 57 thru 60 CAT A Minimum Descent Altitude (4) 5.171
57 thru 62 ARC Radius (6) 5.204 61 thru 64 CAT B Minimum Descent Altitude (4) 5.171
63 thru 66 Theta (4) 5.24 65 thru 68 CAT C Minimum Descent Altitude (4) 5.171
67 thru 70 Rho (4) 5.25 69 thru 72 CAT D Minimum Descent Altitude (4) 5.171
71 thru 74 Magnetic Course (4) 5.26 73 thru 75 Procedure TCH (3) 5.67
75 thru 78 Route Distance/Holding Distance or 5.27 76 Localizer Only Altitude Description (1) 5.29
Time (4) 77 thru 81 Localizer Only Altitude (5) 5.30
79 RECD NAV Section (1) 5.4 82 thru 85 Localizer Only Vertical Angle (4) 5.70
80 RECD NAV Subsection (1) 5.5 86 thru 89 Procedure Category (4) 5.242
81 thru 82 Reserved (expansion) (2) 90 thru 92 RNP (3) 5.211
83 Altitude Description (1) 5.29 93 thru 118 Reserved (expansion) (26)
84 ATC Indicator (1) 5.81 119 Apch Route Qualifier 1 (1) 5.7
85 thru 89 Altitude (5) 5.30 120 Apch Route Qualifier 2 (1) 5.7
90 thru 94 Altitude (5) 5.30 121 thru 123 Blank (Spacing) (3)
95 thru 99 Transition Altitude (5) 5.53 124 thru 128 File Record Number (5) 5.31
100 thru 102 Speed Limit (3) 5.72 129 thru 132 Cycle Date (4) 5.32
103 thru 106 Vertical Angle (4) 5.70
107 thru 111 Center Fix or TAA Procedure Turn 5.144 or Note 1: Columns 119 and 120 (Apch Route Qualifier 1
Indicator (5) 5.271 and 2) are part of the sort key required to match
112 Multiple Code or TAA Sector Identifier 5.130 or the Continuation Record to the Primary Record.
(1) 5.272 This non-standard sorting sequence was selected
113 thru 114 ICAO Code (2) Note 3 5.14 to preserve the Primary Record for
115 Section Code (1) Note 3 5.4 SID/STAR/Approach Records as much as
116 Subsection Code (1) Note 3 5.5 possible as these new fields were introduced in
117 GPS/FMS Indication (1) 5.222 Supplement 14.
118 Speed Limit Description (1) 5.261
119 Apch Route Qualifier 1 (1) Note 2 5.7 Note 2: For records used to define RNAV Procedures
120 Apch Route Qualifier 2 (1) Note 2 5.7 with multiple minimums, the RNP value is
121 thru 123 Blank (Spacing) (3) carried in columns 90 thru 92 of the
124 thru 128 File Record Number (5) 5.31 Continuation Record and is associated with the
129 thru 132 Cycle Date (4) 5.32 Procedure Category. In these cases, the RNP
value in column 45 thru 47 of the Primary
Note 1: For approach route idents including “Multiple Record will be blank.
Indicator,” see Section 5.101.
ARINC SPECIFICATION 424 - Page 20
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.9.3 Airport SID/STAR/Approach Flight Planning 4.1.10.1 Runway Primary Records
Continuation Records
Column Field Name (Length) Reference
This Continuation Record is used to indicate the Leg
Distance for each segment of the Route and the Start/End 1 Record Type (1) 5.2
validity times of the Primary Record. 2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4
6 Blank (Spacing) (1)
Column Field Name (Length) Reference
7 thru 10 Airport ICAO Identifier (4) 5.6
1 thru 38 Field as on Primary 11 thru 12 ICAO Code (2) 5.14
39 Continuation Record No. (1) 5.16 13 Subsection Code (1) 5.5
40 Application Type (1) 5.91 14 thru 18 Runway Identifier (5) 5.46
41 Start/End Indicator (1) 5.152 19 thru 21 Blank (Spacing) (3)
42 thru 52 Start/End Date (11) 5.153 22 Continuation Record No. (1) 5.16
53 thru 74 Blank (Spacing) (22) 23 thru 27 Runway Length (5) 5.57
75 thru 78 Leg Distance (4) 5.260 28 thru 31 Runway Magnetic Bearing (4) 5.58
79 thru 123 Reserved (Expansion) (45) 32 Blank (Spacing) (1)
124 thru 128 File Record No. (5) 5.31 33 thru 41 Runway Latitude (9) 5.36
129 thru 132 Cycle Date (4) 5.32 42 thru 51 Runway Longitude (10) 5.37
52 thru 56 Runway Gradient (5) 5.212
4.1.9.4 Airport SID/STAR Flight Planning Continuation 57 thru 66 Blank (Spacing) (10)
Records 67 thru 71 Landing Threshold Elevation (5) 5.68
72 thru 75 Displaced Threshold Distance (4) 5.69
This Continuation Record is used to indicate the fields of 76 thru 77 Threshold Crossing Height (2) 5.67
the Primary Record that are changed. Used in conjunction 78 thru 80 Runway Width (3) 5.109
with Section 4.1.9.3. 81 TCH Value Indicator (1) 5.270
82 thru 85 Localizer/MLS/ GLS Ref Path 5.44
Identifier (4)
Column Field Name (Length) Reference
86 Localizer/ MLS/ GLS Category/ 5.80
1 thru 38 Fields as on Primary Class (1)
39 Continuation Record No. (1) 5.16 87 thru 90 Stopway (4) 5.79
40 thru 123 Fields as on Primary Records 91 thru 94 Second Localizer/ MLS/ GLS Ref 5.44
124 thru 128 File Record No. (5) 5.31 Path Ident (4)
129 thru 132 Cycle Date (4) 5.32 95 Second Localizer/ MLS/ GLS 5.80
Category/ Class (1)
Note: Flight Planning continuation records are 96 thru 101 Reserved (Expansion) (6)
designed to carry off-cycle updates to the 102 thru 123 Runway Description (22) 5.59
primary record, and cannot carry an Application 124 thru 128 File Record No. (5) 5.31
Type column. 129 thru 132 Cycle Date (4) 5.32

4.1.10 Runway Records (PG) 4.1.10.2 Runway Continuation Records

This file contains runway information.
Column Field Name (Length) Reference
1 thru 21 Fields as on Primary Records
22 Continuation Record No. (1) 5.16
23 Application Type (1)
24 thru 92 Notes (69) 5.61
93 thru 123 Reserved (Expansion) (31)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32

4.1.10.3 Runway Simulation Continuation Records

Column Field Name (Length) Reference

1 thru 21 Fields as on Primary Records
22 Continuation Record No. (1) 5.16
23 Application Type (1) 5.91
24 thru 51 Reserved (Spacing) (28)
52 thru 56 Runway True Bearing (5) 5.94
57 True Bearing Source (1) 5.95
58 thru 65 Reserved (Spacing) (8)
66 TDZE Location (1) 5.98
67 thru 71 Touchdown Zone Elevation (5) 5.97
72 thru 123 Reserved (Expansion) (52)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
 ARINC SPECIFICATION 424 - Page 21
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.11 Airport and Heliport Localizer and Glide Slope 4.1.11.2 Airport and Heliport Localizer and Glide Slope
Records (PI) Continuation Records

This file will contain a sequential listing of all localizers and Column Field Name (Length) Reference
glide slopes associated with those localizers. The glide
slope portion of the record may contain blanks if no glide 1 thru 21 Fields as on Primary Records
slope is associated with the localizer (Category 0 localizer, 22 Continuation Record No. (1) 5.16
see Section 5.80). When a glide slope is installed, a glide 23 Application Type (1) 5.91
slope angle will be provided. The latitude and longitude 24 thru 92 Notes (69) 5.61
fields for the glide slope may be set to blanks when such 93 thru 123 Reserved (Expansion) (31)
information is not available to the data supplier for a 124 thru 128 File Record (5) 5.31
particular glide slope installation due to insufficient 129 thru 132 Cycle Date (4) 5.32
government source.
4.1.11.3 Airport and Heliport Localizer and Glide Slope
4.1.11.1 Airport and Heliport Localizer and Glide Slope Simulation Continuation Records
Primary Records
Column Field Name (Length) Reference
Column Field Name (Length) Reference 1 thru 21 Fields as on Primary Record
1 Record Type (1) 5.2 22 Continuation Record No. (1) 5.16
2 thru 4 Customer/Area Code (3) 5.3 23 Application Type (1) 5.91
5 Section Code (1) 5.4 24 thru 27 Blank (Spacing) (4)
6 Blank (Spacing) (1) 28 thru 32 Facility Characteristics (5) 5.93
7 thru 10 Airport Identifier (4) 5.6 33 thru 51 Blank (Spacing) (19)
11 thru 12 ICAO Code (2) 5.14 52 thru 56 Localizer True Bearing (5) 5.94
13 Subsection Code (1) 5.5 57 Localizer Bearing Source (1) 5.95
14 thru 17 Localizer Identifier (4) 5.44 58 thru 87 Reserved (Spacing) (30)
18 ILS Category (1) 5.80 88 thru 90 Glide Slope Beam Width (3) 5.96
19 thru 21 Blank (Spacing) (3) 91 thru 96 Approach Route Ident (6) 5.10
22 Continuation Record No. (1) 5.16 97 thru 102 Approach Route Ident (6) 5.10
23 thru 27 Localizer Frequency (5) 5.45 103 thru 108 Approach Route Ident (6) 5.10
28 thru 32 Runway Identifier (5) 5.46 109 thru 114 Approach Route Ident (6) 5.10
33 thru 41 Localizer Latitude (9) 5.36 115 thru 120 Approach Route Ident (6) 5.10
42 thru 51 Localizer Longitude (10) 5.37 120 thru 123 Blank (Spacing) (4)
52 thru 55 Localizer Bearing (4) 5.47 124 thru 128 File Record No. (5) 5.31
56 thru 64 Glide Slope Latitude (9) 5.36 129 thru 132 Cycle Date (4) 5.32
65 thru 74 Glide Slope Longitude (10) 5.37
75 thru 78 Localizer Position (4) 5.48 4.1.12 Company Route Records (R)
79 Localizer Position Reference (1) 5.49
80 thru 83 Glide Slope Position (4) 5.50 This file contains company tailored route information.
84 thru 87 Localizer Width (4) 5.51
88 thru 90 Glide Slope Angle (3) 5.52
91 thru 95 Station Declination (5) 5.66
96 thru 97 Glide Slope Height at Landing Threshold 5.67
(2)
98 thru 102 Glide Slope Elevation (5) 5.74
103 thru 106 Supporting Facility ID (4) Note 1 5.33
107 thru 108 Supporting Facility ICAO Code (2) 5.14
Note 1
109 Supporting Facility Section Code (1) 5.4
Note 1
110 Supporting Facility Subsection Code (1) 5.5
Note 1
111 thru 123 Reserved (Expansion) (13)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32

Note 1: Terminal Navaids used as Supporting Facilities

must be located at the same airport as the ILS.
ARINC SPECIFICATION 424 - Page 22
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.12.1 Company Route Primary Records 4.1.13.1 Airport and Heliport Localizer Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 Record Type (1) 5.2 1 Record Type (1) 5.2
2 thru 4 Customer (3) 5.3 2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4 5 Section Code (1) 5.4
6 Subsection Code (1) 5.5 6 Blank (Spacing) (1)
7 thru 11 From Airport/Fix (5) 5.75 7 thru 10 Airport Identifier (4) 5.6
12 Blank (Spacing) (1) 11 thru 12 ICAO Code (2) 5.14
13 thru 14 ICAO Code (2) 5.14 13 Subsection Code (1) 5.5
15 Section Code (1) 5.4 14 thru 17 Localizer Identifier (4) 5.44
16 Subsection Code (1) 5.5 18 thru 20 Marker Type (3) 5.99
17 thru 21 To Airport/Fix (5) 5.75 21 Blank (Spacing) (1)
22 Blank (Spacing) (1) 22 Continuation Record No. (1) 5.16
23 thru 24 ICAO Code (2) 5.14 23 thru 27 Locator Frequency (5) 5.34
25 Section Code (1) 5.4 28 thru 32 Runway Identifier (5) 5.46
26 Subsection Code (1) 5.5 33 thru 41 Marker Latitude (9) 5.36
27 thru 36 Company Route ID (10) 5.76 42 thru 51 Marker Longitude (10) 5.37
37 thru 39 Sequence No. (3) 5.12 52 thru 55 Minor Axis Bearing (4) 5.100
40 thru 42 VIA (3) 5.77 56 thru 64 Locator Latitude (9) 5.36
43 thru 48 SID/STAR/App/Awy (6) 5.78 65 thru 74 Locator Longitude (10) 5.37
49 thru 51 Area Code (3) 5.3 75 thru 79 Locator Class (5) 5.35
52 thru 57 To Fix (6) 5.83 80 thru 84 Locator Facility Characteristics (5) 5.93
58 thru 59 ICAO Code (2) 5.14 85 thru 88 Locator Identifier (4) 5.33
60 Section Code (1) 5.4 89 thru 90 Blank (Spacing) (2)
61 Subsection Code (1) 5.5 91 thru 95 Magnetic Variation (5) 5.39
62 thru 66 Runway Trans (5) 5.84 96 thru 97 Blank (Spacing) (2)
67 thru 71 ENRT Trans (5) 5.85 98 thru 102 Facility Elevation (5) 5.92
72 Reserved (1) 103 thru 123 Reserved (Expansion) (21)
73 thru 77 Cruise Altitude (5) 5.86 124 thru 128 File Record No. (5) 5.31
78 thru 81 Terminal/Alternate Airport (4) 5.87 129 thru 132 Cycle Date (4) 5.32
82 thru 83 ICAO Code (2) 5.14
84 thru 87 Alternate Distance (4) 5.88 4.1.13.2 Airport and Heliport Localizer Continuation
88 thru 90 Cost Index (3) 5.89 Records
91 thru 94 Enroute Alternate Airport (4) 5.148
95 thru 123 Reserved (Expansion) (29)
Column Field Name (Length) Reference
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32 1 thru 21 Fields as on Primary Records
22 Continuation Record No. (1) 5.16
4.1.13 Airport and Heliport Localizer Marker Records 23 Application Type (1) 5.91
(PM) 24 thru 123 Reserved (Expansion) (100)
124 thru 128 File Record No. (5) 5.31
The Airport and Heliport Localizer Marker File (PM) 129 thru 132 Cycle Date (4) 5.32
contains details of all markers and locators associated with
all types of localizers. It does not contain airway markers,
see Section 4.1.15.
 ARINC SPECIFICATION 424 - Page 23
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.14 Airport Communications Records (PV) 4.1.14.3 Airport Additional Continuation Records

4.14.1 Airport Communications Primary Records Column Field Name (Length) Reference
1 thru 25 Fields as on Primary Records
Column Field Name (Length) Reference 26 Continuation Record No. (1) 5.16
1 Record Type (1) 5.2 27 Application Type (1) 5.91
2 thru 4 Customer/Area Code (3) 5.3 28 Time Code (1) 5.131
5 Section Code (1) 5.4 29 NOTAM (1) 5.132
6 Blank (Spacing) (1) 30 Time Indicator (1) 5.138
7 thru 10 Airport Identifier (4) 5.6 31 thru 40 Time of Operation (10) 5.195
11 thru 12 ICAO Code (2) 5.14 41 thru 50 Time of Operation (10) 5.195
13 Subsection Code (1) 5.5 51 thru 60 Time of Operation (10) 5.195
14 thru 16 Communications Type (3) 5.101 61 thru 70 Time of Operation (10) 5.195
17 thru 23 Communications Freq (7) 5.103 71 thru 80 Time of Operation (10) 5.195
24 Guard/Transmit (1) 5.182
81 thru 90 Time of Operation (10) 5.195
25 Frequency Units (1) 5.104
91 thru 100 Time of Operation (10) 5.195
26 Continuation Record No. (1) 5.16
101 thru 123 Reserved (Expansion) (23)
27 thru 29 Service Indicator (3) 5.106
30 Radar Service (1) 5.102 124 thru 128 File Record No. (5) 5.31
31 Modulation (1) 5.198 129 thru 132 Cycle Date (4) 5.32
32 Signal Emission (1) 5.199
33 thru 41 Latitude (9) 5.36 4.1.15 Airways Marker Records (EM)
42 thru 51 Longitude (10) 5.37
52 thru 56 Magnetic Variation (5) 5.39 The Airways Marker file contains details of all airways
57 thru 61 Facility Elevation (5) 5.92 markers.
62 H24 Indicator (1) 5.181
63 thru 68 Sectorization (6) 5.183 4.1.15.1 Airways Marker Primary Records
69 Altitude Description (1) 5.29
70 thru 74 Communication Altitude (5) 5.184
75 thru 79 Communication Altitude (5) 5.184 Column Field Name (Length) Reference
80 thru 83 Sector Facility (4) 5.185 1 Record Type (1) 5.2
84 thru 85 ICAO Code (2) 5.14 2 thru 4 Customer/Area Code (3) 5.3
86 Section Code (1) 5.4 5 Section Code (1) 5.4
87 Subsection Code (1) 5.5 6 Subsection Code (1) 5.5
88 Distance Description (1) 5.187 7 thru 13 Blank (Spacing) (7)
89 thru 90 Communications Distance (2) 5.188 14 thru 17 Marker Identifier (4) 5.110
91 thru 94 Remote Facility (4) 5.200 18 thru 19 Blank (Spacing) (2)
95 thru 96 ICAO Code (2) 5.14 20 thru 21 ICAO Code (2) 5.14
97 Section Code (1) 5.4 22 Continuation Record No. (1) 5.16
98 Subsection Code (1) 5.5 23 thru 26 Marker Code (4) 5.111
99 thru 123 Call Sign (25) 5.105 27 Reserved (Expansion) (1)
124 thru 128 File Record No. (5) 5.31 28 Marker Shape (1) 5.112
129 thru 132 Cycle Date (4) 5.32 29 Marker Power (1) 5.113
30 thru 32 Blank (Spacing) (3)
4.1.14.2 Airport Communications Continuation Records 33 thru 41 Marker Latitude (9) 5.36
42 thru 51 Marker Longitude (10) 5.37
52 thru 55 Minor Axis (4) 5.100
Column Field Name (Length) Reference 56 thru 74 Blank (Spacing) (19)
1 thru 25 Fields as on Primary Records 75 thru 79 Magnetic Variation (5) 5.39
26 Continuation Record No. (1) 5.16 80 thru 84 Facility Elevation (5) 5.92
27 Application Type (1) 5.91 85 thru 87 Datum Code (3) 5.197
28 thru 87 Narrative (60) 5.186 88 thru 93 Blank (Spacing) (6)
88 thru 123 Reserved (Expansion) (36) 94 thru 123 Marker Name (30) 5.71
124 thru 128 File Record No. (5) 5.31 124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32 129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 24
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.15.2 Airways Marker Continuation Records 4.1.17.1 FIR/UIR Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 thru 21 Fields as on Primary Records 1 Record Type (1) 5.2
22 Continuation Record No. (1) 5.16 2 thru 4 Customer/Area Code (3) 5.3
23 Application Type (1) 5.91 5 Section Code (1) 5.4
24 thru 123 Reserved (Expansion) (100) 6 Subsection Code (1) 5.5
7 thru 10 FIR/UIR Identifier (4) 5.116
124 thru 128 File Record No. (5) 5.31
11 thru 14 FIR/UIR Address (4) 5.151
129 thru 132 Cycle Date (4) 5.32 15 FIR/UIR Indicator (1) 5.117
16 thru 19 Sequence Number (4) 5.12
4.1.16 Cruising Tables Records (TC) 20 Continuation Record No. (1) 5.16
21 thru 24 Adjacent FIR Identifier (4) 5.116
The Cruising Tables file contains details relating to 25 thru 28 Adjacent UIR Identifier (4) 5.116
available Cruising Levels for IFR flights. 29 Reporting Units Speed (1) 5.122
30 Reporting Units Altitude (1) 5.123
31 Entry Report (1) 5.124
4.1.16.1 Cruising Table Primary Records 32 Blank (Spacing) (1)
33 thru 34 Boundary Via (2) 5.118
Column Field Name (Length) Reference 35 thru 43 FIR/UIR Latitude (9) 5.36
44 thru 53 FIR/UIR Longitude (10) 5.37
1 Record Type (1) 5.2 54 thru 62 Arc Origin Latitude (9) 5.36
2 thru 4 Blank (Spacing) (3) 63 thru 72 Arc Origin Longitude (10) 5.37
5 Section Code (1) 5.4 73 thru 76 Arc Distance (4) 5.119
6 Subsection Code (1) 5.5 77 thru 80 Arc Bearing (4) 5.120
7 thru 8 Cruise Table Identifier (2) 5.134 81 thru 85 FIR Upper Limit (5) 5.121
9 Sequence Number (1) 5.12 86 thru 90 UIR Lower Limit (5) 5.121
10 thru 28 Blank (Spacing) (19) 91 thru 95 UIR Upper Limit (5) 5.121
29 thru 32 Course From (4) 5.135 96 thru 97 Cruise Table Ind (2) 5.134
33 thru 36 Course To (4) 5.135 98 Reserved (Expansion) (1)
37 Mag/True (1) 5.165 99 thru 123 FIR/UIR Name (25) 5.125
38 thru 39 Blank (Spacing) (2) 124 thru 128 File Record No. (5) 5.31
40 thru 44 Cruise Level From (5) 5.136 129 thru 132 Cycle Date (4) 5.32
45 thru 49 Vertical Separation (5) 5.137
50 thru 54 Cruise Level To (5) 5.136
55 thru 59 Cruise Level From (5) 5.136 4.1.17.2 FIR/UIR Continuation Records
60 thru 64 Vertical Separation (5) 5.137
65 thru 69 Cruise Level To (5) 5.136 Column Field Name (Length) Reference
70 thru 74 Cruise Level From (5) 5.136
75 thru 79 Vertical Separation (5) 5.137 1 thru 19 Fields as on Primary Records
80 thru 84 Cruise Level To (5) 5.136 20 Continuation Record No. (1) 5.16
85 thru 89 Cruise Level From (5) 5.136 22 Application Type (1) 5.91
90 thru 94 Vertical Separation (5) 5.137 23 thru 123 Reserved (Expansion) (101)
95 thru 99 Cruise Level To (5) 5.136 124 thru 128 File Record No. (5) 5.31
100 thru 123 Reserved (Expansion) (24) 129 thru 132 Cycle Date (4) 5.32
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
4.1.18 Restrictive Airspace Records (UR)
4.1.17 FIR/UIR Records (UF)
The Restrictive Airspace Record File contains a sequential
The FIR/UIR file contains the lateral boundary description listing of vertical and lateral limits of restrictive areas.
of the FIR/UIR in a sequence of records and the vertical
boundary description of the FIR/UIR in the first of the
sequence.
 ARINC SPECIFICATION 424 - Page 25
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.18.1 Restrictive Airspace Primary Records 4.1.18.3 Restrictive Airspace Flight Planning
Continuation Record
Column Field Name (Length) Reference
1 Record Type (1) 5.2 Column Field Name (Length) Reference
2 thru 4 Customer/Area Code (3) 5.3 1 thru 24 Fields as on Primary Records
5 Section Code (1) 5.4 25 Continuation Record No. (1) 5.16
6 Subsection Code (1) 5.5 26 Application Type 5.91
7 thru 8 ICAO Code (2) 5.14 27 thru 29 Blank (Spacing) (3)
9 Restrictive Type (1) 5.128 30 Start/End Indicator (1) 5.152
10 thru 19 Restrictive Airspace Designation (10) 5.129 31 thru 41 Start/End Date (11) 5.153
20 Multiple Code (1) 5.130 42 thru 123 Reserved (Expansion) (82)
21 thru 24 Sequence Number (4) 5.12 124 thru 128 File Record No. (5) 5.31
25 Continuation Record No. (1) 5.16 129 thru 132 Cycle Date (4) 5.32
26 Level (1) 5.19
27 Time Code (1) 5.131
4.1.19 Grid MORA Records (AS)
28 NOTAM (1) 5.132
29 thru 30 Blank (Spacing) (2)
The Grid MORA (Minimum Off Rate Altitude) file
31 thru 32 Boundary Via (2) 5.118
contains a table of Minimum Off Route Altitudes.
33 thru 41 Latitude (9) 5.36
42 thru 51 Longitude (10) 5.37
4.1.19.1 Grid MORA Primary Records
52 thru 60 Arc Origin Latitude (9) 5.36
61 thru 70 Arc Origin Longitude (10) 5.37
71 thru 74 Arc Distance (4) 5.119 Column Field Name (Length) Reference
75 thru 78 Arc Bearing (4) 5.120 1 Record Type (1) 5.2
79 thru 81 Blank (Spacing) (3) 2 thru 4 Blank (Spacing) (3)
82 thru 86 Lower Limit (5) 5.121 5 Section Code (1) 5.4
87 Unit Indicator (1) 5.133 6 Subsection Code (1) 5.5
88 thru 92 Upper Limit (5) 5.121 7 thru 13 Blank (Spacing) (7)
93 Unit Indicator (1) 5.133 14 thru 16 Starting Latitude (3) 5.141
94 thru 123 Restrictive Airspace Name (30) 5.126 17 thru 20 Starting Longitude (4) 5.142
124 thru 128 File Record No. (5) 5.31 21 thru 30 Blank (Spacing) (10)
129 thru 132 Cycle Date (4) 5.32 31 thru 33 MORA (3) 5.143
34 thru 36 MORA (3) 5.143
4.1.18.2 Restrictive Airspace Continuation Records 37 thru 39 MORA (3) 5.143
40 thru 42 MORA (3) 5.143
Column Filed Name (Length) Reference 43 thru 45 MORA (3) 5.143
46 thru 48 MORA (3) 5.143
1 thru 24 Fields as on Primary Records
49 thru 51 MORA (3) 5.143
25 Continuation Record Number (1) 5.16
52 thru 54 MORA (3) 5.143
26 Application Type 5.91
55 thru 57 MORA (3) 5.143
27 Time Code (1) 5.131
58 thru 60 MORA (3) 5.143
28 NOTAM (1) 5.132
61 thru 63 MORA (3) 5.143
29 Time Indicator (1) 5.138
64 thru 66 MORA (3) 5.143
30 thru 39 Time of Operations (10) 5.195
67 thru 69 MORA (3) 5.143
40 thru 49 Time of Operations (10) 5.195
70 thru 72 MORA (3) 5.143
50 thru 59 Time of Operations (10) 5.195
73 thru 75 MORA (3) 5.143
60 thru 69 Time of Operations (10) 5.195
76 thru 78 MORA (3) 5.143
70 thru 79 Time of Operations (10) 5.195
79 thru 81 MORA (3) 5.143
80 thru 89 Time of Operations (10) 5.195
82 thru 84 MORA (3) 5.143
90 thru 99 Time of Operations (10) 5.195
85 thru 87 MORA (3) 5.143
100 thru 123 Controlling Agency (24) 5.140
88 thru 90 MORA (3) 5.143
124 thru 128 File Record Number (5) 5.31
91 thru 93 MORA (3) 5.143
129 thru 132 Cycle Date (4) 5.32
94 thru 96 MORA (3) 5.143
97 thru 99 MORA (3) 5.143
100 thru 102 MORA (3) 5.143
103 thru 105 MORA (3) 5.143
106 thru 108 MORA (3) 5.143
109 thru 111 MORA (3) 5.143
112 thru 114 MORA (3) 5.143
115 thru 117 MORA (3) 5.143
118 thru 120 MORA (3) 5.143
121 thru 123 Reserved (Expansion) (3)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 26
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.20 Airport MSA (Minimum Sector Altitude) Records 4.1.21 Enroute Airways Restriction Records (EU)
(PS)
The Enroute Airway Restriction file will contain altitude
The Minimum Sector Altitude (MSA) file contains details and time restrictions for an airway, airway segment or
relating to available sector altitudes. sequence of airway segments. The Enroute Airway
Restriction file may contain four different types of primary
4.1.20.1 Airport MSA Primary Records records, dependent on the type of restriction. A Restriction
Code will identify the type of restriction contained in the
Column Field Name (Length) Reference
record. Continuation Records may be used if a single record
does not provide sufficient space for coding a single,
1 Record Type (1) 5.2 complete restriction.
2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4 4.1.21.1 Enroute Airways Restriction Altitude Exclusion
6 Blank (Spacing) (1) Primary Records
7 thru 10 Airport Identifier (4) 5.6
11 thru 12 ICAO Code (2) 5.14
13 Subsection Code (1) 5.5 Column Field Name (Length) Reference
14 thru 18 MSA Center (5) 5.144 1 Record Type (1) 5.2
19 thru 20 ICAO Code (2) 5.14 2 thru 4 Customer/Area Code (3) 5.3
21 Section Code (1) 5.4 5 Section Code (1) 5.4
22 Subsection Code (1) 5.5 6 Subsection Code (1) 5.5
23 Multiple Code (1) 5.130 7 thru 11 Route Identifier (5) 5.8
24 thru 38 Reserved (Expansion) (15) 12 Reserved (1) Note 1
39 Continuation Record No. (1) 5.16 13 thru 15 Restriction Identifier (3) 5.154
40 thru 42 Reserved (Spacing) (3) 16 thru 17 Restriction Type (2) 5.201
43 thru 48 Sector Bearing (6) 5.146 18 Continuation Record No. (1) 5.16
49 thru 51 Sector Altitude (3) 5.147 19 thru 23 Start Fix Identifier (5) 5.13
52 thru 53 Sector Radius (2) 5.145 24 thru 25 Start Fix ICAO Code (2) 5.14
54 thru 59 Sector Bearing (6) 5.146 26 Start Fix Section Code (1) 5.4
60 thru 62 Sector Altitude (3) 5.147 27 Start Fix Subsection Code(1) 5.5
63 thru 64 Sector Radius (2) 5.145 28 thru 32 End Fix Identifier (5) 5.13
65 thru 70 Sector Bearing (6) 5.146 33 thru 34 End Fix ICAO Code (2) 5.14
71 thru 73 Sector Altitude (3) 5.147 35 End Fix Section Code (1) 5.4
74 thru 75 Sector Radius (2) 5.145 36 End Fix Subsection Code (1) 5.5
76 thru 81 Sector Bearing (6) 5.146 37 Blank (Spacing) (1)
82 thru 84 Sector Altitude (3) 5.147 38 thru 44 Start Date (7) 5.157
85 thru 86 Sector Radius (2) 5.145 45 thru 51 End Date (7) 5.157
87 thru 92 Sector Bearing (6) 5.146 52 Time Code (1) 5.131
93 thru 95 Sector Altitude (3) 5.147 53 Time Indicator (1) 5.138
96 thru 97 Sector Radius (2) 5.145 54 thru 63 Time of Operation (10) 5.195
98 thru103 Sector Bearing (6) 5.146 64 thru 73 Time of Operation (10) 5.195
104 thru 106 Sector Altitude (3) 5.147 74 thru 83 Time of Operation (10) 5.195
107 thru 108 Sector Radius (2) 5.145 84 thru 93 Time of Operation (10) 5.195
109 thru 114 Sector Bearing (6) 5.146 94 Exclusion Indicator (1) 5.202
115 thru 117 Sector Altitude (3) 5.147 95 Units of Altitude (1) 5.160
118 thru 119 Sector Radius (2) 5.145 96 thru 98 Restriction Altitude (3) 5.161
120 Magnetic/True Indicator (1) 5.165 99 Block Indicator (1) 5.203
121 thru 123 Reserved (Expansion) (3) 100 thru 102 Restriction Altitude (3) 5.161
124 thru 128 File Record No. (5) 5.31 103 Block Indicator (1) 5.203
129 thru 132 Cycle Date (4) 5.32 104 thru 106 Restriction Altitude (3) 5.161
107 Block Indicator (1) 5.203
4.1.20.2 Airport MSA Continuation Records 108 thru 110 Restriction Altitude (3) 5.161
111 Block Indicator (1) 5.203
112 thru 114 Restriction Altitude (3) 5.161
Column Field Name (Length) Reference
115 Block Indicator (1) 5.203
1 thru 38 Field as on Primary Records 116 thru 118 Restriction Altitude (3) 5.161
39 Continuation Record No. (1) 5.16 119 Block Indicator (1) 5.203
40 Application Type (1) 5.91 120 thru 122 Restriction Altitude (3) 5.161
41 thru 109 Notes (69) 5.61 123 Block Indicator (1) 5.203
110 thru 123 Reserved (Expansion) (14) 124 thru 128 File Record Number (5) 5.31
124 thru 128 File Record No. (5) 5.31 129 thru 132 Cycle Date (4) 5.32
129 thru 132 Cycle Date (4) 5.32
Note 1: The standard length for the Route Identifier is
five characters. Some users envisage the need for
a six-character field. This reserved column will
permit this usage.
 ARINC SPECIFICATION 424 - Page 27
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.21A.1 Enroute Airways Restriction Note 4.1.21B.1 Enroute Airways Restriction Seasonal
Restriction Primary Records Closure Primary Records
Column Field Name (Length) Reference
1 Record Type (1) 5.2 Column Field Name (Length) Reference
2 thru 4 Customer/Area Code (3) 5.3 1 Record Type (1) 5.2
5 Section Code (1) 5.4 2 thru 4 Customer/Area Code (3) 5.3
6 Subsection Code (1) 5.5 5 Section Code (1) 5.4
7 thru 11 Route Identifier (5) 5.8 6 Subsection Code (1) 5.5
12 Reserved (1) Note 1 7 thru 11 Route Identifier (5) 5.8
13 thru 15 Restriction Identifier (3) 5.154 12 Reserved (1) Note 1
16 thru 17 Restriction Type (2) 5.201 13 thru 15 Restriction Identifier (3) 5.154
18 Continuation Record No. (1) 5.16 16 thru 17 Restriction Type (2) 5.201
19 thru 23 Start Fix Identifier (5) 5.13 18 Continuation Record No. (1) 5.16
24 thru 25 Start Fix ICAO Code (2) 5.14 19 thru 23 Start Fix Identifier (5) 5.13
26 Start Fix Section Code (1) 5.4 24 thru 25 Start Fix ICAO Code (2) 5.14
27 Start Fix Subsection Code (1) 5.5 26 Start Fix Section Code (1) 5.4
28 thru 32 End Fix Identifier (5) 5.13 27 Start Fix Subsection Code (1) 5.5
33 thru 34 End Fix ICAO Code (2) 5.14 28 thru 32 End Fix Identifier (5) 5.13
35 End Fix Section Code (1) 5.4 33 thru 34 End Fix ICAO Code (2) 5.14
36 End Fix Subsection Code (1) 5.5 35 End Fix Section Code (1) 5.4
37 Blank (Spacing) (1) 36 End Fix Subsection Code (1) 5.5
38 thru 44 Start Date (7) 5.157 37 Blank (Spacing) (1)
45 thru 51 End Date (7) 5.157 38 thru 44 Start Date (7) 5.157
52 thru 120 Restriction Notes (69) 5.163 45 thru 51 End Date (7) 5.157
121 thru 123 Blank (Spacing) (3) 52 Time Code (1) 5.131
124 thru 128 File Record Number (5) 5.31 53 Time Indicator (1) 5.138
129 thru 132 Cycle Date (4) 5.21 54 thru 63 Time of Operation (10) 5.195
64 thru 73 Time of Operation (10) 5.195
Note 1: The standard length for the Route Identifier is 74 thru 83 Time of Operation (10) 5.195
five characters. Some users envisage the need for 84 thru 93 Time of Operation (10) 5.195
a six-character field. This reserved column will 94 thru 95 Cruise Table Ident (2) 5.134
permit this usage. 96 thru 123 Blank (Spacing) (28)
124 thru 128 File Record Number (5) 5.31
4.1.21A.2 Enroute Airways Restriction Note Restriction 129 thru 132 Cycle Date (4) 5.32
Continuation Records
Note 1: The standard length for the Route Identifier is
Column Field Name (Length) Reference five characters. Some users envisage the need for
a six-character field. This reserved column will
1 thru 17 Fields as on Primary Records
permit this usage.
18 Continuation Record No. (1) 5.16
19 Application Type (1) 5.91
20 thru 51 Reserved (Expansion) (32)
52 thru 120 Restriction Notes (69) 5.163
121 thru 123 Blank (Spacing) (3)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 28
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.21C.1 Enroute Airways Restriction Cruising Table
Replacement Primary Records 4.1.21.2 Enroute Airways Restriction Altitude Exclusion
Continuation Records
Column Field Name (Length) Reference
1 Record Type (1) 5.2 Column Field Name (Length) Reference
2 thru 4 Customer/Area Code (3) 5.3 1 thru 17 Fields as on Primary Records
5 Section Code (1) 5.4 18 Continuation Record No. (1) 5.16
6 Subsection Code (1) 5.5 19 Application Type 5.91
7 thru 11 Route Identifier (5) 5.8 20 thru 51 Reserved (Expansion) (32)
12 Reserved (1) Note 1 52 Time Code (1) 5.131
13 thru 15 Restriction Identifier (3) 5.154 53 Time Indicator (1) 5.138
16 thru 17 Restriction Type (2) 5.201 54 thru 63 Time of Operation (10) 5.195
18 Continuation Record No. (1) 5.16 64 thru 73 Time of Operation (10) 5.195
19 thru 23 Start Fix Identifier (5) 5.13 74 thru 83 Time of Operation (10) 5.195
24 thru 25 Start Fix ICAO Code (2) 5.14 84 thru 93 Time of Operation (10) 5.195
26 Start Fix Section Code (1) 5.4 94 Exclusion Indicator (1) 5.202
27 Start Fix Subsection Code (1) 5.5 95 Units of Altitude (1) 5.160
28 thru 32 End Fix Identifier (5) 5.13 96 thru 98 Restriction Altitude (3) 5.161
33 thru 34 End Fix ICAO Code (2) 5.14 99 Block Indicator (1) 5.203
35 End Fix Section Code (1) 5.4 100 thru 102 Restriction Altitude (3) 5.161
36 End Fix Subsection Code (1) 5.5 103 Block Indicator (1) 5.203
37 Blank (Spacing) (1) 104 thru 106 Restriction Altitude (3) 5.161
38 thru 44 Start Date (7) 5.157 107 Block Indicator (1) 5.203
45 thru 51 End Date (7) 5.157 108 thru 110 Restriction Altitude (3) 5.161
52 Time Code (1) 5.131 111 Block Indicator (1) 5.203
53 Time Indicator (1) 5.138 112 thru 114 Restriction Altitude (3) 5.161
54 thru 63 Time of Operation (10) 5.195 115 Block Indicator (1) 5.203
64 thru 73 Time of Operation (10) 5.195 116 thru 118 Restriction Altitude (3) 5.161
74 thru 83 Time of Operation (10) 5.195 119 Block Indicator (1) 5.203
84 thru 93 Time of Operation (10) 5.195 120 thru 122 Restriction Altitude (3) 5.161
94 thru 95 Cruise Table Ident (2) 5.134 123 Block Indicator (1) 5.203
96 thru 123 Blank (Spacing) (28) 124 thru 128 File Record No. (5) 5.31
124 thru 128 File Record Number (5) 5.31 129 thru 132 Cycle Date (5) 5.32
129 thru 132 Cycle Date (4) 5.32
4.1.22 Airport and Heliport MLS (Azimuth, Elevation
Note 1: The standard length for the Route Identifier is and Back Azimuth) Records
five characters. Some users envisage the need for
a six-character field. This reserved column will This file will contain a listing of all Microwave Landing
permit this usage. Systems, including the Azimuth station, the Elevation
station and the Back Azimuth station if installed.
4.1.21C.2 Enroute Airways Restriction Cruising Table
Replacement Continuation Records

Column Field Name (Length) Reference

1 thru 17 Fields as on Primary Records
18 Continuation Record No. (1) 5.16
19 Application Type 5.91
20 thru 51 Reserved (Expansion) (32)
52 Time Code (1) 5.131
53 Time Indicator (1) 5.138
54 thru 63 Time of Operation (10) 5.195
64 thru 73 Time of Operation (10) 5.195
74 thru 83 Time of Operation (10) 5.195
84 thru 93 Time of Operation (10) 5.195
94 thru 95 Cruise Table Ident (2) 5.134
96 thru 123 Blank (Spacing) (28)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
 ARINC SPECIFICATION 424 - Page 29
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.22.1 Airport and Heliport MLS Primary Records 4.1.22.2 Airport and Heliport MLS Continuation Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 Record Type (1) 5.2 1 thru 21 Field as on Primary Records
2 thru 4 Customer/Area Code (3) 5.3 22 Continuation Record No. (1) 5.16
5 Section Code (1) 5.4 23 Application Type (1) 5.91
6 Blank (Spacing( (1) 24 thru 27 Blank (Spacing) (4)
7 thru 10 Airport Identifier (4) 5.6 28 thru 32 Facility Characteristics (5) 5.93
11 thru 12 ICAO Code (2) 5.14 33 thru 41 Back Azimuth Latitude (9) 5.36
13 Subsection Code4 (1) 5.5 42 thru 51 Back Azimuth Longitude (10) 5.37
14 thru 17 MLS Identifier (4) 5.44 52 thru 55 Back Azimuth Bearing (4) 5.167
18 MLS Category (1) 5.80 56 thru 64 MLS Datum Point Latitude (9) 5.36
19 thru 21 Blank (Spacing) (3) 65 thru 74 MLS Datum Point Longitude (10) 5.37
22 Continuation Record No. (1) 5.16 75 thru 78 Back Azimuth Position (4) 5.48
23 thru 25 Channel (3) 5.166 79 Back Azimuth Position Reference (1) 5.49
26 thru 27 Blank (Spacing) (2) 80 thru 83 Blank (Spacing) (4)
28 thru 32 Runway Identifier (5) 5.46 84 thru 86 Back Azimuth Proportional Sector Right (3) 5.168
33 thru 41 Azimuth Latitude (9) 5.36 87 thru 89 Back Azimuth Proportional Sector Left (3) 5.168
42 thru 51 Azimuth Longitude (10) 5.37 90 thru 92 Back Azimuth Coverage Right (3) 5.172
52 thru 55 Azimuth Bearing (4) 5.167 93 thru 95 Back Azimuth Coverage Left (3) 5.172
56 thru 64 Elevation Latitude (9) 5.36 96 thru 100 Back Azimuth True Bearing (5) 5.94
65 thru 74 Elevation Longitude (10) 5.37 101 Back Azimuth Bearing Source (1) 5.95
75 thru 78 Azimuth Position (4) 5.48 102 thru 106 Azimuth True Bearing (5) 5.94
79 Azimuth Position Reference (1) 5.49 107 Azimuth Bearing Source (1) 5.95
80 thru 83 Elevation Position (4) 5.50 108 thru 109 Glide Path Height at Landing Threshold (2) 5.67
84 thru 86 Azimuth Proportional Angle Right (3) 5.168 110 thru 123 Reserved (Expansion) (14)
87 thru 89 Azimuth Proportional Angle Left (3) 5.168 124 thru 128 File Record No. (5) 5.31
90 thru 92 Azimuth Coverage Right (3) 5.172 129 thru 132 Cycle Date (4) 5.32
93 thru 95 Azimuth Coverage Left (3) 5.172
96 thru 98 Elevation Angle Span (3) 5.169 4.1.23 Enroute Communications Records (EV)
99 thru 103 Magnetic Variation (5) 5.39
104 thru 108 EL Elevation (5) 5.74 4.1.23.1 Enroute Communications Primary Records
109 thru 112 Nominal Elevation Angle (4) 5.173
113 thru 115 Minimum Glide Path Angle (3) 5.52
116 thru 119 Supporting Facility Identifier (4) 5.33 Note 1 Column Field Name (Length) Reference
120 thru 121 Supporting Facility ICAO Code (2) 5.14 Note 1 1 Record Type (1) 5.2
122 Supporting Facility Section Code (1) 5.4 Note 1 2 thru 4 Customer/Area Code (3) 5.3
123 Supporting Facility Subsection Code (1) 5.5 Note 1 5 Section Code (1) 5.4
124 thru 128 File Record No. (5) 5.31 6 Subsection Code (1) 5.5
129 thru 132 Cycle Date (4) 5.32 7 thru 10 FIR/RDO Ident (4) 5.190
11 thru 14 FIR/UIR Address (4) 5.151
15 Indicator (1) 5.117
Note 1: Terminal Navaids used as Supporting Facilities 16 thru 18 Reserved (Expansion) (3)
must be located at the same airport as the MLS. 19 thru 43 Remote Name (25) 5.189
44 thru 46 Communications Type (3) 5.101
47 thru 53 Comm Frequency (7) 5.103
54 Guard/Transmit (1) 5.182
55 Frequency Units (1) 5.104
56 Continuation Record No. (1) 5.16
57 thru 59 Service Indicator (3) 5.106
60 Radar Service (1) 5.102
61 Modulation (1) 5.198
62 Signal Emission (1) 5.199
63 thru 71 Latitude (9) 5.36
72 thru 81 Longitude (10) 5.37
82 thru 86 Magnetic Variation (5) 5.39
87 thru 91 Facility Elevation (5) 5.92
92 H24 Indicator (1) 5.181
93 Altitude Descript. (1) 5.29
94 thru 98 Communication Altitude (5) 5.184
99 thru 103 Communication Altitude (5) 5.184
104 thru 107 Remote Facility (4) 5.200
108 thru 109 ICAO Code (2) 5.14
110 Section Code (1) 5.4
111 Subsection Code (1) 5.5
112 thru 123 Reserved (Expansion) (12)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 30
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.23.2 Enroute Communications Continuation Records 4.1.24.1 Preferred Route Primary Records

Column Field Name (Length) Reference Columns Field Name (Length) Reference
1 thru 55 Fields as on Primary Records 1 Record Type (1) 5.2
56 Continuation Record No. (1) 5.16 2 thru 4 Customer/Area Code (3) 5.3
57 Application Type (1) 5.91 5 Section Code (1) 5.4
58 Time Code (1) 5.131 6 Subsection Code (1) 5.5
59 NOTAM (1) 5.132 7 thru 13 Blank (Spacing) (7)
60 Time Indicator (1) 5.138 14 thru 23 Route Identifier (10) 5.8
61 thru 70 Time of Operation (10) 5.195 24 thru 25 Preferred Route Use Ind (2) 5.220
71 thru 93 Reserved (Expansion) (23) 26 thru 29 Sequence Number (4) 5.12
94 thru 123 Call Sign (30) 5.105 30 thru 38 Blank (Spacing) (9)
124 thru 128 File Record No. (5) 5.31 39 Continuation Record No. (1) 5.16
129 thru 132 Cycle Date (4) 5.32 40 thru 44 To Fix Identifier (5) 5.83
45 thru 46 ICAO Code (2) 5.14
4.1.23.3 Enroute Communications Continuation Records 47 Section Code (1) 5.4
48 Subsection Code (1) 5.5
49 thru 51 VIA Code (3) 5.77
Column Field Name (Length) Reference 52 thru 57 SID/STAR/AWY Ident (6) (See 5.78
1 thru 55 Fields as on Primary Records Note 1)
56 Continuation Record No. (1) 5.16 58 thru 60 AREA Code (3) 5.3
57 Application Type (1) 5.91 61 Level (1) 5.19
58 thru 60 Blank (Spacing) (3) 62 Route Type (1) 5.7
61 thru 70 Time of Operation (10) 5.195 63 thru 67 Initial Airport/Fix (5) 5.194
71 thru 80 Time of Operation (10) 5.195 68 thru 69 ICAO Code (2) 5.14
81 thru 90 Time of Operation (10) 5.195 70 Section Code (1) 5.4
91 thru 100 Time of Operation (10) 5.195 71 Subsection Code (1) 5.5
101 thru 110 Time of Operation (10) 5.195 72 thru 76 Terminus Airport/Fix (5) 5.194
111 thru 120 Time of Operation (10) 5.195 77 thru 78 ICAO Code (2) 5.14
121 thru 123 Reserved (Expansion) (3) 79 Section Code (1) 5.4
124 thru 128 File Record No. (5) 5.31 80 Subsection Code (1) 5.5
129 thru 132 Cycle Date (4) 5.32 81 thru 85 Minimum Altitude (5) 5.30
86 thru 90 Maximum Altitude (5) 5.127
4.1.24 Preferred Routes Records (ET) 91 Time Code (1) 5.131
92 thru 93 Aircraft Use Group (2) 5.221
The Preferred Routes file contains details defining the 94 Direction Restriction (1) 5.115
Preferred Routes, North America Routes for North Atlantic 95 Altitude Description (1) 5.29
Traffic, the Traffic Orientation System, and the similar 96 thru 100 Altitude One (5) 5.30
predefined routings that do not meet the requirements of the 101 thru 105 Altitude Two (5) 5.30
Enroute Airway Record. 106 thru 123 Reserved (Expansion) (18)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32

Note 1: The Standard Enroute Airway Identifier is five

characters. Some users envision the need for a
sixth character. This field length will permit
such coding, see Section 5.8.
 ARINC SPECIFICATION 424 - Page 31
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.24.2 Preferred Route Continuation Records 4.1.25.1 Controlled Airspace Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 thru 38 Fields as on Primary Records 1 Record Type (1) 5.2
39 Continuation Record No. (1) 5.16 2 thru 4 Customer/Area Code (3) 5.3
40 Application Type (1) 5.91 5 Section Code (1) 5.4
41 Time Code (1) 5.131 6 Subsection Code (1) 5.5
42 Time Indicator (1) 5.138 7 thru 8 ICAO Code (2) 5.14
43 thru 52 Time of Operation (10) 5.195 9 Airspace Type (1) 5.213
53 thru 62 Time of Operation (10) 5.195 10 thru 14 Airspace Center (5) 5.214
63 thru 72 Time of Operation (10) 5.195 15 Section Code (1) 5.4
73 thru 82 Time of Operation (10) 5.195 16 Subsection Code (1) 5.5
83 thru 92 Time of Operation (10) 5.195 17 Airspace Classification (1) 5.215
93 thru 102 Time of Operation (10) 5.195 18 thru 19 Reserved (Spacing) (2)
103 thru 112 Time of Operation (10) 5.195 20 Multiple Code (1) 5.130
113 thru 123 Reserved (Expansion) (11) 21 thru 24 Sequence Number (4) 5.12
124 thru 128 File Record No. (5) 5.31 25 Continuation Record Number (1) 5.16
129 thru 132 Cycle Date (4) 5.32 26 Level (1) 5.19
27 Time Code (1) 5.131
4.1.24.3 Preferred Route Continuation Record (ET) 28 NOTAM (1) 5.132
29 thru 30 Blank (Spacing) (2)
31 thru 32 Boundary Via 5.118
Columns Field Name (Length) Reference 33 thru 41 Latitude (9) 5.36
1 thru 38 Fields as on Primary Records 42 thru 51 Longitude (10) 5.37
39 Continuation Record No. (1) 5.16 52 thru 60 Arc Origin Latitude (9) 5.36
40 Application Type (1) 5.91 61 thru 70 Arc Origin Longitude (10) 5.37
41 thru 109 Notes (69) 5.61 71 thru 74 Arc Distance (4) 5.119
110 thru 123 Reserved (Expansion) (14) 75 thru 78 Arc Bearing (4) 5.120
124 thru 128 File Record Number (5) 5.31 79 thru 81 RNP (3) 5.211
129 thru 132 Cycle Date (4) 5.32 82 thru 86 Lower Limit (5) 5.121
87 Unit Indicator (1) 5.133
Note: Section 5.221 describes the use of this record for 88 thru 92 Upper Limit (5) 5.121
Aircraft Use Groups. 93 Unit Indicator (1) 5.133
94 thru 123 Controlled Airspace Name (30) 5.216
4.1.25 Controlled Airspace Records (UC ) 124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
The Controlled Airspace Record file contains a sequential
listing of vertical and lateral limits of all types and 4.1.25.2 Controlled Airspace Continuation Records
classifications of Controlled Airspace. It includes Controlled
Airspace associated with Airports and Heliports. Column Filed Name (Length) Reference
1 thru 24 Fields as on Primary Records
25 Continuation Record Number (1) 5.16
26 Application Type 5.91
27 Time Code (1) 5.131
28 NOTAM (1) 5.132
29 Time Indicator (1) 5.138
30 thru 39 Time of Operations (10) 5.195
40 thru 49 Time of Operations (10) 5.195
50 thru 59 Time of Operations (10) 5.195
60 thru 69 Time of Operations (10) 5.195
70 thru 79 Time of Operations (10) 5.195
80 thru 89 Time of Operations (10) 5.195
90 thru 99 Time of Operations (10) 5.195
100 thru 123 Controlling Agency (24) 5.140
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 32
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.26 Geographical Reference Table Records (TG) 4.1.27.1 Flight Planning Primary Records

The Geographical Reference Table file contains information Column Field Name (Length) Reference
that permits the cross referencing of otherwise undefined 1 Record Type (1) 5.2
geographical entities and Route Identifiers in the Preferred 2 thru 4 Customer/Area Code (3) 5.3
Route file. The contents are not standardized and may vary 5 Section Code (1) 5.4
from data supplier to data supplier. The contents of such a 6 Blank (Spacing) (1)
file can only be used in conjunction with the Preferred Route 7 thru 10 Airport Identifier (4) 5.6
file of the same database in which the file is presented. 11 thru 12 ICAO Code (2) 5.14
13 Subsection Code (1) 5.5
4.1.26.1 Geographical Reference Table Primary Records (TG) 14 thru 19 SID/STAR/Approach Identifier (6) 5.9, 5.10
20 Procedure Type (1) 5.230
Column Field Name (Length) Reference 21 thru 25 Runway Transition Identifier (5) 5.11
1 Record Type (1) 5.2 26 thru 30 Runway Transition Fix (5) 5.13
2 thru 4 Customer/Area Code (3) 5.3 31 thru 32 ICAO Code (2) 5.14
5 Section Code (1) 5.4 33 Section Code (1) 5.4
6 Subsection Code (1) 5.5 34 Subsection Code (1) 5.5
7 thru 8 Geographical Ref Table ID (2) 5.218 35 thru 37 Runway Transition Along Track 5.231
9 Sequence Number (1) 5.12 Distance (3)
10 thru 38 Geographical Entity (29) 5.219 38 thru 42 Common Segment Transition Fix (5) 5.13
39 Continuation Record No (1) 5.16 43 thru 44 ICAO Code (2) 5.14
40 Reserved (1) 45 Section Code (1) 5.4
41 thru 50 Preferred Route Ident (10) 5.8 46 Subsection Code (1) 5.5
51 thru 52 Preferred Route Use Ind (2) 5.220 47 thru 49 Common Segment Along Track 5.231
53 thru 62 Preferred Route Ident (10) 5.8 Distance (3)
63 thru 64 Preferred Route Use Ind (2) 5.220 50 thru 54 Enroute Transition Identifier (5) 5.11
65 thru 74 Preferred Route Ident (10) 5.8 55 thru 59 Enroute Transition Fix (5) 5.13
75 thru 76 Preferred Route Use Indi (2) 5.220 60 thru 61 ICAO Code (2) 5.14
77 thru 86 Preferred Route Ident (10) 5.8 62 Section Code (1) 5.4
87 thru 88 Preferred Route Use Indi (2) 5.220 63 Subsection Code (1) 5.5
89 thru 98 Preferred Route Ident (10) 5.8 64 thru 66 Enroute Transition Along Track 5.231
99 thru 100 Preferred Route Use Indi (2) 5.220 Distance (3)
101 thru 110 Preferred Route Ident (10) 5.8 67 thru 69 Sequence Number (3) 5.12
111 thru 112 Preferred Route Use Ind (2) 5.220 70 Continuation Number (1) 5.16
113 thru 123 Blank (Spacing) (11) 71 thru 74 Number of Engines (4) 5.232
124 thru 128 File Record Number (5) 5.31 75 Turboprop/Jet Indicator (1) 5.233
129 thru 132 Cycle Date (4) 5.32 76 RNAV Flag (1) 5.234
77 ATC Weight Category (1) 5.235
78 thru 84 ATC Identifier (7) 5.236
4.1.26.2 Geographical Reference Table Continuation Records
85 Time Code (1) 5.131
86 thru 100 Procedure Description (15) 5.237
Column Field Name (Length) Reference 101 thru 102 Leg Type Code (2) 5.238
1 thru 38 Fields as on Primary Records 103 Reporting Code (1) 5.239
39 Continuation Record No. (1) 5.16 104 thru 107 Initial Departure Magnetic Course (4) 5.26
40 Application Type (1) 5.91 108 Altitude Description (1) 5.29
41 thru 123 Reserved (Expansion) (83) 109 thru 111 Altitude (3) 5.240
124 thru 128 File Record No. (5) 5.31 112 thru 114 Altitude (3) 5.240
129 thru 132 Cycle Date (4) 5.32 115 thru 117 Speed Limit (3) 5.72
118 thru 119 Initial Cruise Table (2) 5.134
4.1.27 Flight Planning Arrival/Departure Data Records 120 Speed Limit Description (1) 5.261
(PR) 121 thru 123 Blank (Spacing) (3)
124 thru 128 File Record Number (5) 5.31
The Flight Planning Arrival/Departure Data Record is used to 129 thru 132 Cycle Date (4) 5.32
provide the sub-set of data defining SIDs (PD), STARs (PE)
and Approach Procedures (PF) from paragraph 4.1.9 required
for the computer generation of Flight Plans which include
Terminal Procedures. The file contains a sequential listing of
published Arrival Procedures, Approach Procedures and
Departure Procedures, the available Enroute and Runway
Transitions for those procedures, the Transition waypoints, the
appropriate along track distance fields and the intermediate
fixes along those routes.
 ARINC SPECIFICATION 424 - Page 33
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.27.2 Flight Planning Continuation Records 4.1.28.1 Path Point Primary Records
This Flight Planning Arrival/Departure Data Continuation
Column Field Name (Length) Reference
Record is provided when Intermediate Fix information is
required for the procedure coded in the Primary Record. 1 Record Type (1) 5.2
2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4
Column Field Name (Length) Reference
6 Blank (1)
1 thru 69 Fields as on Primary Records 7 thru 10 *Airport Identifier (4) 5.6
70 Continuation Number (1) 5.16 11 thru 12 ICAO Code (2) 5.14
71 Application Type (1) 5.91 13 Subsection Code (1) 5.5
72 thru 76 Intermediate Fix Identifier (5) 5.13 14 thru 19 Approach Procedure Ident (6) 5.10
77 thru 78 ICAO Code (2) 5.14 20 thru 24 *Runway or Helipad Identifier (5) Note 3 5.46 or 5.180
79 Section Code (1) 5.4 25 thru 26 *Operation Type (2) 5.223
80 Subsection Code (1) 5.5 27 Continuation Record Number (1) 5.16
81 thru 83 Intermediate Distance (3) 5.231 28 *Route Indicator (1) 5.224
84 Fix Related Transition Code (1) 5.241 29 thru 30 *SBAS Service Provider Identifier (2) 5.255
85 thru 89 Intermediate Fix Identifier (5) 5.13 31 thru 32 *Reference Path Data Selector (2) 5.256
90 thru 91 ICAO Code (2) 5.14 33 thru 36 *Reference Path Identifier (4) 5.257
92 Section Code (1) 5.4 37 *Approach Performance Designator (1) 5.258
93 Subsection Code (1) 5.5 38 thru 48 *Landing Threshold Point Latitude (11) 5.267
94 thru 96 Intermediate Distance (3) 5.231 49 thru 60 *Landing Threshold Point Longitude (12) 5.268
97 Fix Related Transition Code (1) 5.241 61 thru 66 *(LTP) Ellipsoid Height (6) 5.225
98 thru 102 Intermediate Fix Identifier (5) 5.13 67 thru 70 *Glide Path Angle (4) 5.226
103 thru 104 ICAO Code (2) 5.14 71 thru 81 *Flight Path Alignment Point Latitude 5.267
105 Section Code (1) 5.4 (11)
106 Subsection Code (1) 5.5 82 thru 93 *Flight Path Alignment Point Longitude 5.268
107 thru 109 Intermediate Distance (3) 5.231 (12)
110 Fix Related Transition Code (1) 5.241 94 thru 98 *Course Width at Threshold (5) 5.228
111 thru 115 Intermediate Fix Identifier (5) 5.13 Note 4
116 thru 117 ICAO Code (2) 5.14 99 thru 102 *Length Offset (4) 5.259
118 Section Code (1) 5.4 103 thru 108 *Path Point TCH (6) 5.265
119 Subsection Code (1) 5.5 109 *TCH Units Indicator (1) 5.266
120 thru 122 Intermediate Distance (3) 5.231 110 thru 112 *HAL (3) 5.263
123 Fix Related Transition Code (1) 5.241 113 thru 115 *VAL (3) 5.264
124 thru 128 File Record Number (5) 5.31 116 thru 123 SBAS FAS Data CRC Remainder (8) 5.229
129 thru 132 Cycle Date (4) 5.32 124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
4.1.27.3 Flight Planning Continuation Records
Note 1: In the Path Point Record description, the field
Column Field Name (Length) Reference prefixed with * in the Field Name are those
1 thru 69 Fields as on Primary Records columns that have been determined as required
70 Continuation Number (1) 5.16 for the data wrap for CRC calculations
71 Application Type (1) 5.91
72 Time Code (1) 5.131 Note 2: In order to properly convert values and binary
73 Time Indicator (1) 5.138 pack these fields for the CRC data wrap, refer
74 thru 83 Time of Operation (10) 5.195 to RTCA/DO-229C “Minimum Operational
84 thru 93 Time of Operation (10) 5.195 Performance Standards for Global Positioning
94 thru 103 Time of Operation (10) 5.195 System/Wide Area Augmentation System
104 thru 113 Time of Operation (10) 5.195 Airborne Equipment” for Final Approach
114 thru 123 Time of Operation (10) 5.195 Segment (FAS) Data Block and CRC standards.
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32 Note 3: For procedures designed for helicopter options
to a pad or point in space, the runway number is
Note: Record 4.1.27.4 would carry Time of Operation in set to “00”, the runway letter is set to blank and
“note” form starting with column 74 and ending in the pad identifier and/or final approach course
column 123, where required. are carried in the Continuation Record.

4.1.28 Path Point Records (PP) Note 4: When the runway number is set to 00, then the
Course Width field is ignored and the course
This file will contain Path Point records for RNAV width is 38 meters.
GPS/GLS Approach Procedures.
ARINC SPECIFICATION 424 - Page 34
4.0 NAVIGATION DATA - RECORD LAYOUT

4.1.28.2 Path Point Continuation Records Note 2: All the latitudes/longitudes of the record refer
to the same datum code.
Column Field Name (Length) Reference
4.1.29.2 GLS Continuation Records
1 thru 26 Fields as on Primary Record Type
27 Continuation Record Number (1) 5.16
28 Application Type (1) 5.91 Column Field Name (Length) Reference
29 thru 34 (FPAP) Ellipsoid Height (6) 5.225 1 thru 21 Fields as on Primary Records
35 thru 40 (FPAP) Orthometric Height (6) 5.227 22 Continuation Record No. (1) 5.16
41 thru 46 (LTP) Orthometric Height (6) 5.227 23 Application Type (1) 5.91
47 thru 56 Approach Type Identifier (10) 5.262 24 thru 123 Reserved (Expansion) (100)
57 thru 61 GNSS Channel Number (5) 5.244 124 thru 128 File Record No. (5) 5.31
62 thru 71 Blank (Spacing) (10) 129 thru 132 Cycle Date (4) 5.32
72 thru 74 Helicopter Procedure Course (3) 5.269
75 thru 123 Blank (Spacing) (49) 4.1.30 Alternate Record (RA)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32 The Alternate Record file contains a listing of up to six
Alternate Airport Identifiers or, up to six Alternate
4.1.29 GLS Record (PT) Company Route Identifiers or any combination of
Alternate Airport or Alternate Route Identifiers for a
This record contains a sequential listing of all GNSS given departure airport, destination airport or enroute
Landing Systems (GLS) approaches, including the slope, fix. The data content of the record is customer defined.
course and reference path idents of the GLS approach. A
GLS approach is identified by its ident and channel. Note 4.1.30.1 Alternate Primary Records
that several GLS approaches can be supported by a single
differential GLS ground station. Column Field Name (Length) Reference
4.1.29.1 GLS Primary Records 1 Record Type (1) 5.2
2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4
Column Field Name (Length) Reference
6 Subsection Code (1) 5.5
1 Record Type (1) 5.2 7 thru 11 Alternate Related Airport or Fix (5) 5.75
2 thru 4 Customer/Area Code (3) 5.3 12 thru 13 Alternate Related ICAO Code (2) 5.14
5 Section Code (1) 5.4 14 Alternate Related Section Code (1) 5.4
6 Blank (1) 15 Alternate Related Subsection Code (1) 5.5
7 thru 10 Airport or Heliport Identifier (4) 5.6 16 thru 17 Alternate Record Type (2) 5.250
11 thru 12 ICAO Code (2) 5.14 18 thru 19 Blank (Spacing) (2)
13 Subsection code (1) 5.5 20 thru 22 Distance to Alternate (3) 5.251
14 thru 17 GLS Ref Path Identifier (4) 5.44 23 Alternate Type (1) 5.252
18 GLS Category (1) 5.80 24 thru 33 Primary Alternate Identifier (10) 5.253
19 thru 21 Blank (3) 34 thru 35 Blank (Spacing) (2)
22 Continuation Number (1) 5.16 36 thru 38 Distance to Alternate (3) 5.251
23 thru 27 GLS Channel (5) 5.244 39 Alternate Type (1) 5.252
28 thru 32 Runway Identifier (5) 5.46 40 thru 49 Additional Alternate Identifier One (10) 5.253
33 thru 51 Blank (19) 50 thru 51 Blank (Spacing) (2)
52 thru 55 GLS Approach Bearing (4) (Note 1) 5.47 52 thru 54 Distance to Alternate (3) 5.251
56 thru 64 Station Latitude (9) 5.36 55 Alternate Type (1) 5.252
65 thru 74 Station Longitude (10) 5.37 56 thru 65 Additional Alternate Identifier Two (10) 5.253
75 thru 78 GLS Station ident (4) 5.243 66 thru 67 Blank (Spacing) (2)
79 thru 83 Blank (5) 68 thru 70 Distance to Alternate (3) 5.251
84 thru 85 Service Volume Radius (2) 5.245 71 Alternate Type (1) 5.252
86 thru 87 TDMA Slots (2) 5.246 72 thru 81 Additional Alternate Identifier Three (10) 5.253
88 thru 90 GLS Approach Slope (3) 5.52 82 thru 83 Blank (Spacing) (2)
91 thru 95 Magnetic Variation (5) 5.39 84 thru 86 Distance to Alternate (3) 5.251
96 thru 97 Reserved (2) 87 Alternate Type (1) 5.252
98 thru 102 Station Elevation (5) 5.74 88 thru 97 Additional Alternate Identifier Four (10) 5.253
103 thru 105 Datum Code (3) 5.197 98 thru 99 Blank (Spacing) (2)
106 thru 108 Station Type (3) 5.247 100 thru 102 Distance to Alternate (3) 5.251
109 thru 110 Blank (2) 103 Alternate Type (1) 5.252
111 thru 115 Station Elevation WGS 84 (5) 5.248 104 thru 113 Additional Alternate Identifier Five (10) 5.253
116 thru 123 Blank (8) 114 thru 123 Reserved (expansion) (10)
124 thru 128 File Record Number (5) 5.31 124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32 129 thru 132 Cycle Date (4) 5.32

Note 1: GLS reference point should be equal to IFR landing

threshold position, as it is the trajectory reference
point.
 ARINC SPECIFICATION 424 - Page 35
4.0 NAVIGATION DATA - RECORD LAYOUT
4.1.31 Airport TAA (PK) 4.2 Master Helicopter User File (HA)
The Airport Terminal Arrival Altitude (TAA) file contains This Section contains record information unique to
details relating to TAA sectorization and sector altitudes. helicopter operations. In addition to the records
identified in this Section, records identified in Section
4.1.31.1 Airport TAA Primary Records 4.1 Master Airline User File are used in the Master
Helicopter User File.
Column Field Name (Length) Reference
4.2.1 Heliport Records
1 Record Type (1) 5.2
2 thru 4 Customer/Area Code (3) 5.3 This file will contain heliport information.
5 Section Code (1) 5.4
6 Blank (Spacing) (1) 4.2.1.1 Heliport Primary Records
7 thru 10 Airport Identifier (4) 5.6
11 thru 12 ICAO Code (2) 5.14
13 Subsection Code (1) 5.5 Column Field Name (Length) Reference
14 thru 19 Approach Identifier (6) 5.10 1 Record Type (1) 5.2
20 TAA Sector Identifier (1) 5.272 2 thru 4 Customer/Area Code (3) 5.3
21 thru 24 TAA Procedure Turn (4) 5.271 5 Section Code (1) 5.4
25 thru 29 Blank (Reserved) (5) 6 Blank (Spacing) (1)
30 thru 34 TAA IAF Waypoint (5) 5.273 7 thru 10 Heliport Identifier (4) 5.6
35 thru 36 ICAO Code (2) 5.14 11 thru 12 ICAO Code (2) 5.14
37 Section Code (1) 5.4 13 Subsection Code (1) 5.5
38 Subsection Code (1) 5.5 14 thru 16 ATA/IATA Designator (3) 5.107
39 Continuation Record No. (1) 5.16 17 thru 21 PAD Identifier (5) 5.180
40 Reserved (1) 22 Continuation Record No. (1) 5.16
41 Mag/True Indicator 5.165 23 thru 27 Speed Limit Altitude (5) 5.73
42 thru 45 Sector Radius 1 (4) 5.274 28 thru 30 Datum Code (3) 5.197
46 thru 51 Sector Bearing (6) 5.146 31 IFR Indicator (1) 5.108
52 thru 54 Sector Minimum Altitude (3) 5.147 32 Blank (Spacing) (1)
55 thru 58 Sector Radius 1 (4) 5.274 33 thru 41 Latitude (9) 5.36
59 thru 64 Sector Bearing (6) 5.146 42 thru 51 Longitude (10) 5.37
65 thru 67 Sector Minimum Altitude (3) 5.147 52 thru 56 Magnetic Variation (5) 5.39
68 thru 71 Sector Radius 1 (4) 5.274 57 thru 61 Heliport Elevation (5) 5.55
72 thru 77 Sector Bearing (6) 5.146 62 thru 64 Speed Limit (3) 5.72
78 thru 80 Sector Minimum Altitude (3) 5.147 65 thru 68 Recommended VHF Navaid (4) 5.23
81 thru 84 Sector Radius 1 (4) 5.274 69 thru 70 ICAO Code (2) 5.14
85 thru 90 Sector Bearing (6) 5.146 71 thru 75 Transition Altitude (5) 5.53
91 thru 93 Sector Minimum Altitude (3) 5.147 76 thru 80 Transition Level (5) 5.53
94 thru 97 Sector Radius 1 (4) 5.274 81 Public Military Indicator (1) 5.177
98 thru 103 Sector Bearing (6) 5.146 82 thru 84 Time Zone (3) 5.178
104 thru 106 Sector Minimum Altitude (3) 5.147 85 Daylight Indicator (1) 5.179
107 thru 110 Sector Radius 1 (4) 5.274 86 thru 91 Pad Dimensions (6) 5.176
111 thru 116 Sector Bearing (6) 5.146 92 Magnetic/True Indicator (1) 5.165
117 thru 119 Sector Minimum Altitude (3) 5.147 93 Reserved (Expansion) (1)
120 thru 123 Blank (Spacing ) (4) 94 thru 123 Heliport Name (30) 5.71
124 thru 128 File Record No. (5) 5.31 124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32 129 thru 132 Cycle Date (4) 5.32

4.1.31.2 Airport Terminal Arrival Altitude Continuation 4.2.1.2 Heliport Continuation Records
Records
Column Field Name (Length) Reference
Column Field Name (Length) Reference 1 thru 21 Fields as on Primary Records
1 thru 38 Fields as on Primary Records 22 Continuation Record No. (1) 5.16
39 Continuation Record No (1) 5.16 23 Application Type (1) 5.91
40 Application Type (1) 5.91 24 thru 92 Notes (69) 5.61
41 thru 109 Notes (69) 5.61 93 thru 123 Reserved (Expansion) (31)
110 thru 123 Reserved (Expansion) (14) 124 thru 128 File Record No. (5) 5.31
124 thru 128 File Record No. (5) 5.31 129 thru 132 Cycle Date (4) 5.32
129 thru 132 Cycle Date (4) 5.32
ARINC SPECIFICATION 424 - Page 36
4.0 NAVIGATION DATA - RECORD LAYOUT

4.2.1.3 Heliport Flight Planning Continuation Records 4.2.2.1 Heliport Terminal Waypoint Primary Records

This Continuation Record is used to indicate the FIR and Column Field Name (Length) Reference
UIR within which the Airport defined in the Primary Record
1 Record Type (1) 5.2
resides, to provide the Start/End validity dates/times of the
2 thru 4 Customer/Area Code (3) 5.3
Primary Record, and to provide an indication if the Heliport
5 Section Code (1) 5.4
defined in the Primary Record is associated with Controlled
6 Blank (Spacing) (1)
Airspace.
7 thru 10 Heliport Identifier (4) 5.6
11 thru 12 ICAO Code (2) 5.14
Column Field Name (Length) Reference 13 Subsection Code (1) 5.5
1 thru 21 Fields as on Primary Records 14 thru 18 Waypoint Identifier (5) 5.13
22 Continuation Record Number (1) 5.16 19 Blank (Spacing) (1)
23 Application Type (1) 5.91 20 thru 21 ICAO Code (2) 5.14
24 thru 27 FIR Identifier (4) 5.116 22 Continuation Record Number (1) 5.16
28 thru 31 UIR Identifier (4) 5.116 23 thru 26 Blank (Spacing) (4)
32 Start/End Indicator (1) 5.152 27 thru 29 Waypoint Type (3) 5.42
33 thru 43 Start/End Date/Time (11) 5.153 30 thru 31 Waypoint Usage (2) 5.82
44 thru 66 Blank (Spacing) (23) 32 Blank (Spacing) (1)
67 Controlled A/S Indicator (1) 5.217 33 thru 41 Waypoint Latitude (9) 5.36
68 thru 71 Controlled A/S Airport Identifier (4) 5.6 42 thru 51 Waypoint Longitude (10) 5.37
72 thru 73 Controlled A/S Airport ICAO (2) 5.14 52 thru 74 Blank (Spacing) (23)
74 thru 123 Blank (Spacing) (50) 75 thru 79 Dynamic Magnetic Variation (5) 5.39
124 thru 128 File Record Number (5) 5.31 80 thru 84 Reserved (Expansion) (5)
129 thru 132 Cycle Date (4) 5.32 85 thru 87 Datum Code (3) 5.197
88 thru 95 Reserved (Expansion) (8)
4.2.1.4 Heliport Flight Planning Continuation Records 96 thru 98 Name Format Indicator (3) 5.196
99 thru 123 Waypoint Name/Description (25) 5.43
124 thru 128 File Record Number (5) 5.31
Column Field Name (Length) Reference 129 thru 132 Cycle Date (4) 5.32
1 thru 21 Fields as on Primary Records
22 Continuation Record No. (1) 5.16 4.2.2.2 Heliport Terminal Waypoint Continuation
23 Application Type (1) 5.91 Records
24 thru 92 Notes (69) 5.61
93 thru 123 Reserved (Expansion) (31) Column Field Name (Length) Reference
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32 1 thru 21 Fields as on Primary Records
22 Continuation Record Number (1) 5.16
23 Application Type) (1) 5.91
4.2.2 Heliport Terminal Waypoint Records (HC)
24 thru 92 Notes (69) 5.61
The Heliport Terminal Waypoint file contains all terminal 93 thru 123 Reserved (Expansion) (31)
waypoints and VFR waypoint within the geographical area of 124 thru 128 File Record Number (5) 5.31
each heliport. Heliport Terminal Waypoints utilized by two 129 thru 132 Cycle Date (4) 5.32
or more heliports will be stored in the Enroute Waypoint file
to eliminate duplication. Terminal Waypoints used jointly by Note: Column 23 is reserved for an Application
an airport and a heliport are also stored in the Enroute Type character.
waypoint file.
4.2.2.3 Heliport Terminal Waypoint Flight Planning
Continuation Records
This Continuation Record is used to indicate the FIR
and UIR within which the Waypoint defined in the
Primary Records is located and to provide the Start/End
validity dates/times of the Primary Record where
applicable.

Column Field Name (Length) Reference

1 thru 21 Fields as on Primary Records
22 Continuation Record Number (1) 5.16
23 Application Type (1) 5.91
24 thru 27 FIR Identifier (4) 5.116
28 thru 31 UIR Identifier (4) 5.116
32 Start/End Indicator (1) 5.152
33 thru 43 Start/End Date (11) 5.153
44 thru 123 Reserved (Expansion) (80)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32
 ARINC SPECIFICATION 424 - Page 37
4.0 NAVIGATION DATA - RECORD LAYOUT
4.2.3.1 Heliport SID/STAR/Approach Primary Records
4.2.2.4 Heliport Terminal Waypoint Flight Planning
Continuation Records
Column Field Name (Length) Reference
This Continuation Record is used to indicate the fields of the 1 Record Type (1) 5.2
Primary Record that are changed on the Start/End Date used in 2 thru 4 Customer/Area Code (3) 5.3
conjunction with Section 4.2.2.3. 5 Section Code (1) 5.4
6 Blank (Spacing) (1)
7 thru 10 Heliport Identifier (4) 5.6
Column Field Name (Length) Reference
11 thru 12 ICAO Code (2) 5.14
1 thru 21 Fields as on Primary Records 13 Subsection Code (1) 5.5
22 Continuation Record Number (1) 5.16 14 thru 19 SID/STAR/APP Identifier (6) 5.9, 5.10
23 thru 123 Fields as on Primary Records 20 Route Type (1) 5.7
124 thru 128 File Record Number (5) 5.31 21 thru 25 Transition Identifier (5) 5.11
129 thru 132 Cycle Date (4) 5.32 26 Multiple Indicator (1) Note 1 5.130
27 thru 29 Sequence Number (3) 5.12
4.2.3 Heliport SID/STAR/Approach (HD/HE/HF) 30 thru 34 Fix Identifier (5) 5.13
35 thru 36 ICAO Code (2) 5.14
The Heliport Terminal Procedure records comprise three 37 Section Code (1) 5.4
files, (HD) for SIDs, (HE) for STARS and (HF) for 38 Subsection Code (1) 5.5
Approaches. The SID File contains the sequential listing of 39 Continuation Record Number (1) 5.16
published Heliport Standard Instrument Departures. The 40 thru 43 Waypoint Description Code (4) 5.17
STAR File contains the sequential listing of published 44 Turn Direction (1) 5.20
Heliport Standard Terminal Arrival Routes. The Approach 45 thru 47 RNP (3) 5.211
Files contain the sequential listing of Heliport Standard 48 thru 49 Path and Termination (2) 5.21
Instrument Approach Procedures. SIDs/STARs/Approach 50 Turn Direction Valid (1) 5.22
Procedures to be used by rotor-wing aircraft at airports are 51 thru 54 Recommended Navaid (4) 5.23
included in the Airport SID/STAR/Approach files, Section 55 thru 56 ICAO Code (2) 5.14
4.1.9. 57 thru 62 ARC Radius (6) 5.204
63 thru 66 Theta (4) 5.24
67 thru 70 Rho (4) 5.25
71 thru 74 Magnetic Course (4) 5.26
75 thru 78 Route Distance/Holding Distance or 5.27
Time (4)
79 Recommended Navaid Section (1) 5.4
80 Recommended Navaid Subsection (1) 5.5
81 thru 82 Reserved (Spacing) (2)
83 Altitude Description (1) 5.29
84 ATC Indicator (1) 5.81
85 thru 89 Altitude (5) 5.30
90 thru 94 Altitude (5) 5.30
95 thru 99 Transition Altitude (5) 5.53
100 thru 102 Speed Limit (3) 5.72
103 thru 106 Vertical Angle (4) 5.70
107 thru 111 Center Fix or TAA Procedure Turn 5.144 or
Indicator (5) 5.271
112 Multiple Code or TAA, Sector 5.130 or
Identifier (1) 5.272
113 thru 114 ICAO Code (2) Note 3 5.14
115 Section Code (1) Note 3 5.4
116 Subsection Code (1) Note 3 5.5
117 GPS/FMS Indicator (1) 5.222
118 Speed Limit Description (1) 5.261
119 Apch Route Qualifier 1 (1) Note 2 5.7
120 Apch Route Qualifier 2 (1) Note 2 5.7
121 thru 123 Blank (Spacing) (3)
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32

Note 1: The Multiple Indicators are used on Approach

Procedures only.

Note 2: Columns 119 and 120 (Approach Route

Qualifier 1 and 2) are required to match the
Primary Record to the Continuation Record.
This non-standard sorting sequence was
selected to preserve the Primary Record
Layout for SID/STAR/Approach Records as
ARINC SPECIFICATION 424 - Page 38
4.0 NAVIGATION DATA - RECORD LAYOUT

much as possible as these new fields were 4.2.3.3 Heliport SID/STAR/Approach Flight Planning
introduced in Supplement 14. Continuation Records

Note 3: When columns 107 thru 116 are providing a This Continuation Record is used to indicate the Leg
reference to a MSA or the center fix for an RF leg, Distance for each segment of the Route and to provided
all of the columns are used. When they are the Start/End validity dates/times of the Primary
providing a reference to a TAA, only columns 107 Record where applicable.
thru 112 are used and 113 thru 116 are blank.
Column Field Name (Length) Reference
4.2.3.2 Heliport SID/STAR/Approach Continuation
Records 1 thru 38 Fields as on Primary Records
39 Continuation Record Number (1) 5.16
40 Application Type (1) 5.91
Column Field Name (Length) Reference 41 Start/End Indicator (1) 5.152
1 thru 38 Field as on Primary Records 42 thru 52 Start/End Date (11) 5.153
39 Continuation Record Number (1) 5.16 53 thru 74 Blank (Spacing) (22)
40 Application Type (1) 5.91 75 thru 78 Route Distance (4) 5.27
41 thru 44 CAT A Decision Height (4) 5.170 79 thru 123 Reserved (Expansion) (45)
45 thru 48 CAT B Decision Height (4) 5.170 124 thru 128 File Record Number (5) 5.31
49 thru 52 CAT C Decision Height (4) 5.170 129 thru 132 Cycle Date (4) 5.32
53 thru 56 CAT D Decision Height (4) 5.170
57 thru 60 CAT A Minimum Descent Height (4) 5.171 4.2.3.4 Heliport SID/STAR/Approach Flight Planning
61 thru 64 CAT B Minimum Descent Height (4) 5.171 Continuation Records
65 thru 68 CAT C Minimum Descent Height (4) 5.171
69 thru 72 CAT D Minimum Descent Height (4) 5.171
Column Field Name (Length) Reference
73 thru 75 Procedure TCH (3) 5.67
76 Localizer Altitude Description (1) 5.29 1 thru 38 Fields as on Primary Records
77 thru 81 Localizer Altitude (5) 5.30 39 Continuation Record Number (1) 5.16
82 thru 85 Localizer VNAV (4) 5.70 40 thru 123 Fields as on Primary Records
86 thru 89 Procedure Category (4) 5.242 124 thru 128 File Record Number (5) 5.31
90 thru 92 RNP (3) 5.211 129 thru 132 Cycle Date (4) 5.32
93 thru 118 Reserved (Expansion) (26)
119 Apch Route Qualifier 1 (1) 5.7 Note: Flight Planning continuation records are
120 Apch Route Qualifier 2 (1) 5.7 designed to carry off-cycle updates to the
121 thru 123 Blank (Spacing) (3) primary record, and cannot carry an
124 thru 128 File Record Number (5) 5.31 Application Type column.
129 thru 132 Cycle Date (4) 5.32
4.2.4 Heliport MSA (HS)
Note 1: Columns 119 and 120 are part of the sort key
required to match the Continuation Records to the The Heliport Minimum Sector Altitude (MSA) file
Primary Record. This non-standard sorting contains details relating to available Sector Altitudes.
sequence was selected to preserve the Primary
Record for SID/STAR/Approach as much as
possible at the time the record was introduced in
Supplement 14.
Note 2: For records used to define the “RNAV” procedures
with multiple minimums, the RNP value is carried
in columns 90 through 92 of the Continuation
Record and is associated with the Procedure
Category. In these cases, the RNP value in column
45 through 47 of the Primary Record will be blank.
 ARINC SPECIFICATION 424 - Page 39
4.0 NAVIGATION DATA - RECORD LAYOUT
4.2.4.1 Heliport MSA Primary Records 4.2.5.1 Heliport Communications Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 Record Type (1) 5.2 1 Record Type (1) 5.2
2 thru 4 Customer/Area Code (3) 5.3 2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4 5 Section Code (1) 5.4
6 Blank (Spacing) (1) 6 Blank (Spacing) (1)
7 thru 10 Heliport Identifier (4) 5.6 7 thru 10 Heliport Identifier (4) 5.6
11 thru 12 ICAO Code (2) 5.14 11 thru 12 ICAO Code (2) 5.14
13 Subsection Code (1) 5.5 13 Subsection Code (1) 5.5
14 thru 18 MSA Center (5) 5.144 14 thru 16 Communications Type (3) 5.101
19 thru 20 ICAO Code (2) 5.14 17 thru 23 Communications Freq (7) 5.103
21 Section Code (1) 5.4 24 Guard/Transmit (1) 5.182
22 Subsection Code (1) 5.5 25 Frequency Units (1) 5.104
23 Multiple Code (1) 5.130 26 Continuation Record No. (1) 5.16
24 thru 38 Reserved (Expansion) (15) 27 thru 29 Service Indicator (3) 5.106
39 Continuation Record Number (1) 5.16 30 Radar Service (1) 5.102
40 thru 42 Reserved (Spacing) (3) 31 Modulation (1) 5.198
43 thru 48 Sector Bearing (6) 5.146 32 Signal Emission (1) 5.199
49 thru 51 Sector Altitude (3) 5.147 33 thru 41 Latitude (9) 5.36
52 thru 53 Sector Radius (2) 5.145 42 thru 51 Longitude (10) 5.37
54 thru 59 Sector Bearing (6) 5.146 52 thru 56 Magnetic Variation (5) 5.39
60 thru 62 Sector Altitude (3) 5.147 57 thru 61 Facility Elevation (5) 5.92
63 thru 64 Sector Radius (2) 5.145 62 H24 Indicator (1) 5.181
65 thru 70 Sector Bearing (6) 5.146 63 thru 68 Sectorization (6) 5.183
71 thru 73 Sector Altitude (3) 5.147 69 Altitude Description (1) 5.29
74 thru 75 Sector Radius (2) 5.145 70 thru 74 Communication Altitude (5) 5.184
76 thru 81 Sector Bearing (6) 5.146 75 thru 79 Communication Altitude (5) 5.184
82 thru 84 Sector Altitude (3) 5.147 80 thru 83 Sector Facility (4) 5.185
85 thru 86 Sector Radius (2) 5.145 84 thru 85 ICAO Code (2) 5.14
87 thru 92 Sector Bearing (6) 5.146 86 Section Code (1) 5.4
93 thru 95 Sector Altitude (3) 5.147 87 Subsection Code (1) 5.5
96 thru 97 Sector Radius (2) 5.145 88 Distance Description (1) 5.187
98 thru103 Sector Bearing (6) 5.146 89 thru 90 Communications Distance (2) 5.188
104 thru 106 Sector Altitude (3) 5.147 91 thru 94 Remote Facility (4) 5.200
107 thru 108 Sector Radius (2) 5.145 95 thru 96 ICAO Code (2) 5.14
109 thru 114 Sector Bearing (6) 5.146 97 Section Code (1) 5.4
115 thru 117 Sector Altitude (3) 5.147 98 Subsection Code (1) 5.5
118 thru119 Sector Radius (2) 5.145 99 thru 123 Call Sign (25) 5.105
120 Magnetic/True Indicator (1) 5.165 124 thru 128 File Record Number (5) 5.31
121 thru 123 Reserved (Expansion) (3) 129 thru 132 Cycle Date (4) 5.32
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32 4.2.5.2 Heliport Communications Continuation Records
4.2.4.2 Heliport MSA Continuation Records
Column Field Name (Length) Reference
Column Field Name (Length) Reference 1 thru 25 Fields as on Primary Records
26 Continuation Record No. (1) 5.16
1 thru 38 Fields as on Primary Records
27 Application Type (1) 5.91
39 Continuation Record Number (1) 5.16
28 thru 87 Narrative (60) 5.186
40 Application Type (1) 5.91
88 thru 123 Reserved (Expansion) (36)
41 thru 109 Notes (69) 5.61
124 thru 128 File Record No. (5) 5.31
110 thru 123 Reserved (Expansion) (14)
129 thru 132 Cycle Date (4) 5.32
124 thru 128 File Record Number (5) 5.31
129 thru 132 Cycle Date (4) 5.32

4.2.5 Heliport Communications Records (HV )

These files will contain Heliport Communications Facilities.

ARINC SPECIFICATION 424 - Page 40
4.0 NAVIGATION DATA - RECORD LAYOUT

4.2.5.3 Heliport Communications Continuation Records 4.2.6.1 Heliport TAA Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 thru 25 Fields as on Primary Records 1 Record Type (1) 5.2
26 Continuation Record No.(1) 5.16 2 thru 4 Customer/Area Code (3) 5.3
27 Application Type (1) 5.91 5 Section Code (1) 5.4
28 Time Code (1) 5.131 6 Blank (Spacing) (1)
29 NOTAM (1) 5.132 7 thru 10 Heliport Identifier (4) 5.6
30 Time Indicator (1) 5.138 11 thru 12 ICAO Code (2) 5.14
31 thru 40 Time of Operation (10) 5.195 13 Subsection Code (1) 5.5
41 thru 50 Time of Operation (10) 5.195 14 thru 19 Approach Identifier (6) 5.10
51 thru 60 Time of Operation (10) 5.195 20 Section Code (1) 5.4
61 thru 70 Time of Operation (10) 5.195 20 TAA Sector Identifier (1) 5.272
71 thru 80 Time of Operation (10) 5.195 21 thru 24 TAA Procedure Turn (4) 5.271
81 thru 90 Time of Operation (10) 5.195 25 thru 29 Blank (Reserved) (5)
91 thru 100 Time of Operation (10) 5.195 30 thru 34 TAA IAF Waypoint (5) 5.273
101thru 123 Reserved (Expansion) (23) 35 thru 36 ICAO Code (2) 5.14
124 thru 128 File Record No. (5) 5.31 37 Section Code (1) 5.4
129 thru 132 Cycle Date (4) 5.32 38 Subsection Code (1) 5.5
39 Continuation Record Numbers (1) 5.16
4.2.6 Heliport (TAA) 40 Reserved (1)
41 Mag/True Indicator 5.165
The Heliport Terminal Arrival Altitude (TAA) file contains 42 thru 45 Sector Radius 1 (4) 5.274
details relating to TAA sectorization and sector altitudes. 46 thru 51 Sector Bearing (6) 5.146
52 thru 54 Sector Minimum Altitude (3) 5.147
55 thru 58 Sector Radius 1 (4) 5.274
59 thru 64 Sector Bearing (6) 5.146
65 thru 67 Sector Minimum Altitude (3) 5.147
68 thru 71 Sector Radius 1 (4) 5.274
72 thru 77 Sector Bearing (6) 5.146
78 thru 80 Sector Minimum Altitude (3) 5.147
81 thru 84 Sector Radius 1 (4) 5.274
85 thru 90 Sector Bearing (6) 5.146
91 thru 93 Sector Minimum Altitude (3) 5.147
94 thru 97 Sector Radius 1 (4) 5.274
98 thru 103 Sector Bearing (6) 5.146
104 thru 106 Sector Minimum Altitude (3) 5.147
107 thru 110 Sector Radius 1 (4) 5.274
111 thru 116 Sector Bearing (6) 5.146
117 thru 119 Sector Minimum Altitude (3) 5.147
120 thru 123 Blank (Spacing) (4)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32

4.2.6.2 Heliport Terminal Arrival Altitude

Continuation Records

Column Field Name (Length) Reference

1 thru 38 Fields as on Primary Records
39 Continuation Record No. (1) 5.16
40 Application Type (1) 5.91
41 thru 109 Notes (69) 5.61
110 thru 123 Reserved (Expansion) (14)
124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
 ARINC SPECIFICATION 424 - Page 41

4.0 NAVIGATION DATA - RECORD LAYOUT Page 1 of 14

ARINC 424 - 17 RECORD FORMAT

5.3 5.6 5.14 5.33 5.34 5.35 5.36 5.37 5.38 5.36 5.37 5.66 5.40 5.90 5.150 5.197 5.71 5.31 5.32
VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.1 CUST/ ARPT VOR VOR VHF VOR DME DME STA DME VHF NAVAID NAME FILE
VOR LONGITUDE DME LONGITUDE FREQ DATUM RECORD CYCLE
AREA IDENT IDENT FREQ CLASS LATITUDE IDENT LATITUDE DECL ELEV (30)
PRIMARY PRO CODE NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.61 5.31 5.32

VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.93 5.39 5.92 5.31 5.32

VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.3 FAC
D
FAC FILE
CONTINUATION RECORD SAME AS ABOVE MAG RESERVED (39) RECORD CYCLE
SIMULATION CONTINUATION CHAR ELEV
VAR NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.116 5.116 5.153 5.31 5.32

VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.4 FIR UIR START/END FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (80) RECORD CYCLE
IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS PRIMARY RECORD

SAME PARAGRAPH AS ABOVE 5.31 5.32
(4.1.2.1)
VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.5 CONTINUATION RECORD SAME AS PRIMARY RECORD FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
(4.1.2.1)
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.208 5.209 5.208 5.209 5.208 5.209 5.208 5.209 5.208 5.209 5.31 5.32
VHF NAVAID (D) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.2.6 DIST ALT DIST ALT DIST ALT DIST ALT DIST ALT FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
LIMITATION CONTINUATION LIMIT LIMIT LIMIT LIMIT LIMIT LIMIT LIMIT LIMIT LIMIT LIMIT
NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 42

4.0 NAVIGATION DATA - RECORD LAYOUT Page 2 of 14

ARINC 424 - 17 RECORD FORMAT

5.3 5.6 5.14 5.33 5.34 5.35 5.36 5.37 5.39 5.197 5.71 5.31 5.32
NDB NAVAID (DB)(PN) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.3.1 CUST/ ARPT NDB NDB NDB MAG DATUM FILE
NDB LATITUDE NDB LONGITUDE RESERVED NDB NAVAID NAME (30) RECORD CYCLE
AREA IDENT IDENT FREQ CLASS VAR CODE
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
NDB NAVAID (DB)(PN) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.3.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.93 5.92 5.31 5.32
NDB NAVAID (DB)(PN) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.3.3 FAC FAC FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (39) RECORD CYCLE
SIMULATION CONTINUATION CHAR ELEV
NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.116 5.116 5.153 5.31 5.32

NDB NAVAID (DB)(PN) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.3.4 FIR UIR START/END FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (80) RECORD CYCLE
IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
SAME PARAGRAPH AS PRIMARY RECORD
SAME PARAGRAPH AS ABOVE
(4.1.3.1) 5.31 5.32
NDB NAVAID (DB)(PN) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.3.5 CONTINUATION RECORD SAME AS PRIMARY RECORD FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
(4.1.3.1)
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 43

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT Page 3 of 14

5.XX
5.3 5.41 5.14 5.13 5.42 5.36 5.37 5.39 5.197 5.196 5.43 5.31 5.32
X
WAYPOINT (EA)(PC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.4.1 CUST/ REGN WAYPOINT
D WP ELEV
DATUM NAME FILE
/ARPT TYPE LATITUDE LONGITUDE MAG (REST FOR NAME/DESC (25) RECORD CYCLE
AREA IDENT CODE IND
PRIMARY CODE VAR SIM) NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
WAYPOINT (EA)(PC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.4.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.116 5.116 5.153 5.31 5.32

WAYPOINT (EA)(PC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.4.3 FIR UIR START/END FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (80) RECORD CYCLE
IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS PRIMARY RECORD (4.1.4.1)

SAME PARAGRAPH AS ABOVE 5.31 5.32
WAYPOINT (EA)(PC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.4.4 FILE
CONTINUATION RECORD SAME AS ABOVE CONTINUATION RECORD SAME AS PRIMARY RECORD (4.1.4.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

5.3 5.41 5.13 5.62 5.30 5.127 5.175 5.211 5.204 5.60 5.31 5.32
HOLDING PATTERN (EP) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.5.1 CUST/ REGN FIX IB HOLD MINIMUM MAXIMUM HOLD ARC FILE
RNP RESERVED (27) NAME (25) RECORD CYCLE
AREA CODE IDENT CRS ALTITUDE ALTITUDE SPEED RADIUS
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
HOLDING PATTERN (EP) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.5.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 44

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424-17 RECORD FORMAT Page 4 of 14

5.3 5.8 5.12 5.13 5.17 5.23 5.211 5.24 5.25 5.26 5.27 5.28 5.30 5.30 5.127 5.254 5.31 5.32
ENROUTE AIRWAYS (ER) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.6.1 CUST/ ROUTE SEQ FIX DESC TC RECD OB MAG ROUTE IB MAG MIN MIN MAX FIX FILE
RNP THETA RHO FROM RESERVED (22) RECORD CYCLE
AREA IDENT NR IDENT CODE IND VHF CRS CRS ALTITUDE ALTITUDE ALTITUDE RADIUS
PRIMARY DIST NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.61 5.31 5.32

ENROUTE AIRWAYS (ER) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.6.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.153 5.129 5.129 5.129 5.129 5.31 5.32
ENROUTE AIRWAYS (ER) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.6.3 START/END RESTRICTIVE RESTRICTIVE RESTRICTIVE RESTRICTIVE FILE
CONTINUATION RECORD SAME AS ABOVE DATE AIRSPACE AIRSPACE AIRSPACE AIRSPACE RECORD CYCLE
FLIGHT PLANNING CONTINUATION DESIGNATION DESIGNATION DESIGNATION DESIGNATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE SAME PARAGRAPH AS PRIMARY RECORD (4.1.6.1)

5.31 5.32
ENROUTE AIRWAYS (ER) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.6.4 FILE
CONTINUATION RECORD SAME AS ABOVE CONTINUATION RECORD SAME AS PRIMARY RECORD (4.1.6.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

5.3 5.6 5.14 5.107 5.73 5.54 5.36 5.37 5.39 5.55 5.72 5.23 5.53 5.53 5.178 5.197 5.71 5.31 5.32
AIRPORT (PA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.7.1 CUST/ ARPT ATA/ SPEED MAG SPEED RECD TRANS TRANS TIME DATUM FILE
LIMIT LATITUDE LONGITUDE ELEV RESVD (4) AIRPORT NAME (30) RECORD CYCLE
AREA IDENT IATA VAR LIMIT VHF ALTITUDE LEVEL ZONE CODE
PRIMARY ALTITUDE NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.31 5.32
AIRPORT (PA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.7.2 FILE
NOTES ON CONTINUATION RECORD (69) RESERVED (59) RECORD CYCLE
CONTINUATION RECORD SAME AS ABOVE NUMBER
CONTINUATION

NOTES:

SAME PARAGRAPH AS ABOVE 5.116 5.116 5.153 5.6 5.31 5.32

AIRPORT (PA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.7.3 FIR UIR START/END
AS FILE
RESERVED (23) ARPT RESERVED (50) RECORD CYCLE
CONTINUATION RECORD SAME AS ABOVE IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION IDENT NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE SAME PARAGRAPH AS PRIMARY RECORD (4.1.7.1) 5.31 5.32
AIRPORT (PA)
35 40 45 50 55 60 65
4.1.7.4
FILE
CONTINUATION RECORD SAME AS PRIMARY RECORD (4.1.7.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION CONTINUATION RECORD SAME AS ABOVE NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 45

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT Page 5 of 14

5.3 5.6 5.14 5.56 5.36 5.37 5.XXX 5.60 5.31 5.32
AIRPORT GATE (PB) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.8.1 CUST/ ARPT GATE
MAG HDG FILE
LATITUDE LONGITUDE RESV FOR RESERVED (43) NAME (25) RECORD CYCLE
AREA IDENT IDENT SIM
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
AIRPORT GATE (PB) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.8.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

AIRPORT 5.3 5.6 5.14 5.9 & 5.10 5.11 5.12 5.13 5.17 5.211 5.23 5.204 5.24 5.25 5.26 5.27 5.30 5.30 5.53 5.72 5.70 5.144 or 5.271 5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(PD/PE/PF) CUST/ ARPT SID/STAR/APP TRANS SEQ FIX DESC RECD ARC MAG RTE DIST
ALTITUDE ALTITUDE TRANS SPEED VERT CENTER FIX FILE
RNP THETA RHO HOLD OR RECORD CYCLE
4.1.9.1 PRIMARY AREA IDENT IDENT IDENT NR IDENT CODE NAVAID RADIUS CRS ALTITUDE LIMIT ANGLE
DIST/TIME TAA PT NUMBER

NOTES:

AIRPORT SAME PARAGRAPH AS ABOVE 5.170 5.170 5.170 5.170 5.171 5.171 5.171 5.171 5.67 5.30 5.70 5.242 5.211 5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(PD/PE/PF) PROC FILE
CAT A CAT B CAT C CAT D CAT A CAT B CAT C CAT D TCH LOC VERT RNP RESERVED (26)
4.1.9.2 CONTINUATION RECORD SAME AS ABOVE CAT RECORD CYCLE
DH DH DH DH MDH MDH MDH MDH ALTITUDE ANGLE
CONTINUATION NUMBER

NOTES:
AIRPORT SAME PARAGRAPH AS ABOVE
5.153 5.260 5.31 5.32
SIDS/STARS/APPROACH
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(PD/PE/PF)
FILE
4.1.9.3 CONTINUATION RECORD SAME AS ABOVE START/END LEG RESERVED (45) CYCLE
RECORD
DATE DISTANCE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
AIRPORT SAME PARAGRAPH AS ABOVE SAME PARAGRAPH AS PRIMARY RECORD (4.9.1)
5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(PD/PE/PF) FILE
4.1.9.4 CONTINUATION RECORD SAME AS ABOVE CONTINUATION RECORD SAME AS PRIMARY RECORD (4.9.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 46

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT Page 6 of 14

5.3 5.6 5.14 5.46 5.57 5.58 5.36 5.37 5.212 5.68 5.69 5.109 5.44 5.79 5.44 5.59 5.31 5.32
RUNWAY (PG) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.10.1 CUST/ ARPT RUNWAY RUNWAY RUNWAY RWY LNDG DSPLCD LOC/MLS/ SEC LOC/ FILE
LATITUDE LONGITUDE THRES WIDTH STOPWAY RESERVED RUNWAY DESCRIPTION (22) RECORD CYCLE
AREA IDENT IDENT LENGTH BEARING GRAD THR GLS MLS/GLS
PRIMARY ELEV NUMBER
IDENT IDENT

NOTES:

SAME PARAGRAPH AS ABOVE 5.61 5.31 5.32

RUNWAY (PG) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.10.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.94 5.97 5.31 5.32

RUNWAY (PG) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.10.3 TRUE TDZ FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (52) RECORD CYCLE
BEARING ELEV
SIMULATION CONTINUATION NUMBER

NOTES:

AIRPORT & HELIPORT 5.3 5.6 5.14 5.44 5.45 5.46 5.36 5.37 5.47 5.36 5.37 5.48 5.50 5.51 5.52 5.66 5.74 5.33 5.14 5.59 5.31 5.32
LOCALIZER & G.S. 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(PI) 4.1.11.1 CUST/ ARPT LOC RUNWAY LOC G.S. G.S. LOC FR G.S. FR LOC G.S. STA G.S SUPPORT ICAO FILE
FREQ LOC LATITUDE LOC LONGITUDE LONGITUDE RESERVED (13) RECORD CYCLE
AREA IDENT IDENT IDENT BRG LATITUDE RW END RW THRES WIDTH ANGLE DECL .
ELEV FACILITY CODE
PRIMARY NUMBER

NOTES:

AIRPORT & HELIPORT SAME PARAGRAPH AS ABOVE 5.61 5.31 5.32

5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
LOCALIZER & G.S.
(PI) 4.1.11.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

AIRPORT & HELIPORT SAME PARAGRAPH AS ABOVE 5.93 5.94 5.97 5.96 5.10 5.10 5.10 5.10 5.10 5.31 5.32
LOCALIZER & G.S. 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(PI) 4.1.11.3 FAC TRUE G.S. APP APP APP APP APP FILE
CONTINUATION RECORD SAME AS ABOVE BEAM IDENT IDENT IDENT IDENT IDENT RECORD CYCLE
CHAR BEARING
SIMULATION CONTINUATION WIDTH 1 2 3 4 5 NUMBER

NOTES:

5.3 5.75 5.75 5.76 5.12 5.77 5.78 5.3 5.83 5.84 5.85 5.86 5.87 5.88 5.89 5.148 5.31 5.32
COMPANY ROUTE (R) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.12.1 CUST/ FROM FROM SEQ TO RUNWAY ENRT CRUISE TERM/ ALT COST ENRT RESERVED (29) FILE
COMPANY ROUTE ID VIA S/S/A AREA ALT ALT RECORD CYCLE
AREA ARPT/FIX ARPT/FIX NO. FIX TRANS TRANS ALTITUDE DIST INDEX
PRIMARY AWY ARPT ARPT NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 47

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT

Page 7 of 14

AIRPORT & HELIPORT

5.3 5.6 5.44 5.99 5.34 5.46 5.36 5.37 5.100 5.36 5.37 5.35 5.93 5.33 5.39 5.92 5.31 5.32
LOCALIZER MARKERS/ 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
LOCATORS (PM) MINOR LCTR FILE
CUST/ ARPT LOC MKR LCTR RUNWAY MKR MKR LOCATOR LOCATOR LCTR LCTR MAG FAC RESERVED (21)
4.1.13.1 AREA IDENT IDENT TYPE FREQ IDENT LATITUDE LONGITUDE AXIS LATITUDE LONGITUDE CLASS FAC IDENT VAR ELEV RECORD CYCLE
PRIMARY TRUE BRG CHAR NUMBER

NOTES:

AIRPORT & HELIPORT SAME PARAGRAPH AS ABOVE

5.31 5.32
LOCALIZER (PM) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.13.2 FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (100) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.3 5.6 5.101 5.103 5.106 5.36 5.37 5.39 5.92 5.183 5.184 5.184 5.185 5.200 5.105 5.31 5.32
AIRPORT COMM (PV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.14.1 CUST/ ARPT COMM COMM SERV MAG FAC ALTITUDE ALTITUDE SECTOR REMOTE CALL SIGN (25) FILE
LATITUDE LONGITUDE SECTOR RECORD CYCLE
AREA IDENT TYPE FREQ IND VAR ELEV 1 2 FAC FAC
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.186 5.31 5.32

AIRPORT COMM (PV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.14.2 RESERVED (36) FILE
CONTINUATION RECORD SAME AS ABOVE NARRATIVE (60) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.195 5.195 5.195 5.195 5.195 5.195 5.195 5.31 5.32
AIRPORT COMM (PV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.14.3 RESERVED (23) FILE
CONTINUATION RECORD SAME AS ABOVE TIME OF TIME OF TIME OF TIME OF TIME OF TIME OF TIME OF RECORD CYCLE
CONTINUATION OPERATION OPERATION OPERATION OPERATION OPERATION OPERATION OPERATION NUMBER

NOTES:

5.3 5.110 5.111 5.36 5.37 5.100 5.39 5.92 5.197 5.71 5.31 5.32
AIRWAY MARKERS (EM) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.15.1 CUST/ MARKER MARKER MINOR MAG FAC DATUM FILE
LATITUDE LONGITUDE AXIS RESERVED (19) MARKER NAME (30) RECORD CYCLE
AREA IDENT CODE VAR ELEV CODE
PRIMARY TRUE BRG NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

AIRWAYS MARKER 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.15.2 (EM)
FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (100) RECORD CYCLE
CONTINUATION NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 48

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT

Page 8 of 14

5.135 5.135 5.136 5.137 5.136 5.136 5.137 5.136 5.136 5.137 5.136 5.136 5.137 5.136 5.31 5.32
CRUISING TABLES (TC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.16.1 FIL
COURSE COURSE CRUISE VERTICAL CRUISE CRUISE VERTICAL CRUISE CRUISE VERTICAL CRUISE CRUISE VERTICAL CRUISE
LEVEL LEVEL LEVEL LEVEL LEVEL LEVEL LEVEL LEVEL RESERVED (24) E CYCLE
FROM TO SEPARATION SEPARATION SEPARATION SEPARATION RECORD
PRIMARY FROM TO FROM TO FROM TO FROM TO NUMBER

NOTES:

5.3 5.116 5.151 5.12 5.116 5.116 5.36 5.37 5.36 5.37 5.119 5.120 5.121 5.121 5.121 5.125 5.31 5.32
FIR/UIR (UF) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.17.1 CUST/ FIR/UIR FIR/UIR SEQ ADJ ADJ FIR/UIR FIR/UIR ARC ORIGIN ARC ORIGIN ARC ARC FIR UIR UIR FILE
FIR UIR UPPER LOWER UPPER FIR/UIR NAME (25) RECORD CYCLE
AREA IDENT ADDRESS NR LATITUDE LONGITUDE LATITUDE LONGITUDE DIST BNG
PRIMARY IDENT IDENT LIMIT LIMIT LIMIT NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

FIR/UIR (UF) 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.17.2
FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (101) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.3 5.14 5.129 5.12 5.36 5.37 5.36 5.37 5.119 5.120 5.121 5.121 5.126 5.31 5.32
RESTRICTIVE AIRSPACE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(UR) 4.1.18.1 CUST/
RESTRICTIVE
SEQ ARC ORIGIN ARC ORIGIN ARC ARC LOWER UPPER FILE
AIRSPACE LATITUDE LONGITUDE RESTRICTIVE AIRSPACE NAME (30) RECORD CYCLE
AREA NR LATITUDE LONGITUDE DIST BNG LIMIT LIMIT
PRIMARY DESIGNATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.195 5.195 5.195 5.195 5.195 5.195 5.195 5.140 5.31 5.32
RESTRICTIVE AIRSPACE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(UR) 4.1.18.2 TIME OF FILE
CONTINUATION RECORD SAME AS ABOVE TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION CONTROLLING AGENCY (24) RECORD CYCLE
OPERATION
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.153 5.31 5.32

RESTRICTIVE AIRSPACE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(UR) 4.1.18.3 START/END FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (82) RECORD CYCLE
DATE
CONTINUATION NUMBER

NOTES:

GRID MINIMUM OFF 5.141 5.142 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.143 5.31 5.32
ROUTE ALTITUDE (MORA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

RECORDS (AS) 4.1.19.1 START START FILE

MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA MORA RESVD RECORD CYCLE
LAT LONG
PRIMARY NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 49

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT Page 9 of 14

AIRPORT MINIMUM SECTOR 5.3 5.6 5.14 5.144 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.31 5.32

ALTITUDE (MSA) (PS)

FILE
4.1.20.1 CUST/ ARPT MSA RESERVED (15) SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC
RECORD CYCLE
AREA IDENT CENTER BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD
PRIMARY NUMBER

NOTES:

AIRPORT MINIMUM SECTOR SAME PARAGRAPH AS ABOVE 5.61 5.31 5.32

ALTITUDE (MSA) (PS) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.20.2 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

ENROUTE AIRWAYS 5.3 5.8 5.154 5.13 5.13 5.157 5.157 5.195 5.195 5.195 5.195 5.161 5.161 5.161 5.161 5.161 5.161 5.161 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(EU) 4.1.21.1 CUST/ ROUTE REST START END START END TIME OF TIME OF TIME OF TIME OF REST REST REST REST REST REST REST FILE
FIX FIX RECORD CYCLE
AREA IDENT IDENT DATE DATE OPERATION OPERATION OPERATION OPERATION ALT ALT ALT ALT ALT ALT ALT
ALTITUDE EXCLUSION PRIMARY IDENT IDENT NUMBER

NOTES:

ENROUTE AIRWAYS 5.3 5.8 5.154 5.13 5.13 5.157 5.157 5.163 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(EU) 4.1.21A.1 CUST/ ROUTE REST

START END
START END RESTRICTION NOTES (69) FILE
FIX FIX RECORD CYCLE
AREA IDENT IDENT DATE DATE
NOTE RESTRICTION PRIMARY IDENT IDENT NUMBER

NOTES:

ENROUTE AIRWAYS SAME PARAGRAPH AS ABOVE

5.163 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(EU) 4.1.21A.2 RESTRICTION NOTES (69)

FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (32) RECORD CYCLE
NOTE RESTRICTION CONTINUATION NUMBER

NOTES:

ENROUTE AIRWAYS 5.3 5.8 5.154 5.13 5.13 5.157 5.157 5.195 5.195 5.195 5.195 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(EU) 4.1.21B.1 CUST/ ROUTE REST START END START END FILE
FIX FIX TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION RECORD CYCLE
AREA IDENT IDENT DATE DATE
SEASONAL CLOSURE PRIMARY IDENT IDENT NUMBER

NOTES:

ENROUTE AIRWAYS 5.3 5.8 5.154 5.13 5.13 5.157 5.157 5.195 5.195 5.195 5.195 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
(EU) 4.1.21C.1 START END FILE
CUST/ ROUTE REST START END
CRUISE TABLE REPLACEMENT FIX FIX TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION RECORD CYCLE
AREA IDENT IDENT DATE DATE
IDENT IDENT NUMBER
PRIMARY
NOTES:

ENROUTE AIRWAYS SAME PARAGRAPH AS ABOVE SAME PARAGRAPH AS ABOVE

5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65
(EU) 4.1.21C.2 FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (32) CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
CRUISE TABLE REPLACEMENT
CONTINUATION NUMBER

NOTES:

ENROUTE AIRWAYS SAME PARAGRAPH AS ABOVE 5.195 5.195 5.195 5.195 5.161 5.161 5.161 5.161 5.161 5.161 5.161 5.31 5.32
RESTRICTION RECORDS 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(EU) 4.1.21.2 TIME OF TIME OF TIME OF TIME OF REST REST REST REST REST REST REST FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (32) OPERATION OPERATION RECORD CYCLE
OPERATION OPERATION ALT ALT ALT ALT ALT ALT ALT
ALTITUDE EXCLUSION CONTINUATION NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 50

ARINC 424 - 17 RECORD FORMAT

4.0 NAVIGATION DATA - RECORD LAYOUT
Page 10 of 14

AIRPORT & HELIPORT 5.3 5.6 5.44 5.166 5.46 5.36 5.37 5.167 5.36 5.37 5.167 5.50 5.168 5.168 5.172 5.172 5.169 5.39 5.74 5.173 5.52 5.33 5.14 5.31 5.32
MLS (PL) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

4.1.22.1 CUST/ ARPT MLS RUNWAY

AZ LATITUDE AZ LONGITUDE
MLS EL
EL LONGITUDE
AZ FR EL FR AZ AZ AZ AZ EL MAG EL NOM MIN FAC FILE
CYCLE
IDENT IDENT AZ LATITUDE PRO PRO COV COV ANGLE VAR ELEV ELEV ELEV IDEN RECORD
AREA IDENT RWY END RWY THR
PRIMARY BRG RIGHT LEFT RIGHT LEFT SPAN ANGLE ANGLE NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

AIRPORT & HELIPORT 5.93 5.36 5.37 5.167 5.36 5.37 5.167 5.168 5.168 5.172 5.172 5.94 5.94 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
MLS (PL)
4.1.22.2 FAC MLS MLS DP MLS DP BAZ FR BAZ BAZ BAZ BAZ BAZ AZ FILE
CONTINUATION RECORD SAME AS ABOVE BAZ LATITUDE BAZ LONGITUDE BAZ PRO PRO COV COV TRUE TRUE RESERVED (14) RECORD CYCLE
CHAR LATITUDE LONGITUDE RWY END
CONTINUATION BRG RIGHT LEFT RIGHT LEFT BRG BRG NUMBER

NOTES:

5.3 5.190 5.189 5.101 5.103 5.106 5.36 5.37 5.39 5.92 5.184 5.184 5.200 5.31 5.32
ENROUTE COMM (EV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.23.1 CUST/ FIR/RDO REMOTE SITE NAME (25) COMM COMM SERV MAG FAC ALTITUDE ALTITUDE REMOTE FILE
LATITUDE LONGITUDE RESERVED (12) RECORD CYCLE
AREA IDENT TYPE FREQ IND VAR ELEV 1 2 FAC
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.195 5.31 5.32
ENROUTE COMM (EV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.23.2 TIME OF
FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (23) CALL SIGN (30) RECORD CYCLE
OPERATION
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.195 5.195 5.195 5.195 5.195 5.195 5.31 5.32
ENROUTE COMM (EV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.23.3 TIME OF TIME OF TIME OF TIME OF TIME OF TIME OF FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
OPERATION OPERATION OPERATION OPERATION OPERATION OPERATION
CONTINUATION NUMBER

NOTES:

5.3 5.8 5.220 5.12 5.83 5.77 5.78 5.3 5.194 5.194 5.30 5.127 5.30 5.30 5.31 5.32
PREFERRED ROUTES (ET) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.1.24.1 CUST/ ROUTE USE SEQ
TO SID/STAR/AWY CUST/ INT APT/ TERM APT/ MIN MAX ALTITUDE ALTITUDE FILE
FIX VIA RESERVED (18) RECORD
AREA IDENT IND NR IDENT AREA FIX FIX ALTITUDE ALTITUDE ONE TWO CYCLE
PRIMARY IDENT NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.195 5.195 5.195 5.195 5.195 5.195 5.31 5.32
PREFERRED ROUTES (ET) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.24.2 FILE
CONTINUATION RECORD SAME AS ABOVE TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION RESERVED (11) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.32

5.61 5.31
PREFERRED ROUTES (ET) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.1.24.3 FILE
CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 51

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT Page 11 of 14

5.3 5.14 5.214 5.12 5.36 5.37 5.36 5.37 5.119 5.120 5.211 5.121 5.121 5.216 5.31 5.32
CONTROLLED AIRSPACE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(UC) 4.1.25.1 CUST/ AIRSPACE SEQ ARC ORIGIN ARC ORIGIN ARC ARC LOWER UPPER FILE
LATITUDE LONGITUDE RNP CONTROLLED AIRSPACE NAME (30) RECORD CYCLE
AREA CENTER NR LATITUDE LONGITUDE DIST BRG LIMIT LIMIT
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.195 5.195 5.195 5.195 5.195 5.195 5.195 5.140 5.31 5.32
CONTROLLED AIRSPACE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(UC) 4.1.25.2 FILE
CONTINUATION RECORD SAME AS ABOVE TIME OF OPERATIONS TIME OF OPERATIONS TIME OF OPERATIONS TIME OF OPERATIONS TIME OF OPERATIONS TIME OF OPERATIONS TIME OF OPERATIONS CONTROLLING AGENCY (24) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

GEOGRAPHICAL 5.3 5.219 5.8 5.8 5.8 5.8 5.8 5.8 5.31 5.32
REFERENCE TABLE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
RECORDS (TG) 4.1.26.1 CUST/ GEOGRAPHICAL ENTITY PREFERRED ROUTE
PREFERRED ROUTE PREFERRED ROUTE FILE
PREFERRED ROUTE PREFERRED ROUTE PREFERRED ROUTE IDENT IDENT RECORD CYCLE
AREA IDENT IDENT IDENT IDENT
PRIMARY NUMBER

NOTES:

GEOGRAPHICAL SAME PARAGRAPH AS ABOVE

5.31 5.32
REFERENCE TABLE 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
RECORDS (TG) 4.1.26.2 FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (83) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.11 5.13 5.14 5.231 5.13 5.14 5.231 5.11 5.13 5.14 5.231 5.12 5.232 5.236 5.237 5.238 5.26 5.240 5.240 5.72 5.134 5.31 5.32
5.3 5.6 5.14 5.9, 5.10
FLIGHT PLANNING 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
ARRIVAL/DEPARTURE (PR) CUST/ ARPT SID/STAR/APRCH
RUNWAY RUNWAY RUNWAY COMMON ENROUTE ENROUTE
SEQ ATC
OB SPEED CRS FILE
TRANS SEGMENT TRANS TRANS LTC
4.1.27.1 PRIMARY AREA IDENT IDENT
TRANS TRANS
NR
NOE
IDENT PROCEDURE DESCRIPTION MAG ALT ALT LIMIT TBL RECORD CYCLE
IDENT FIX ATD FIX IDENT FIX CRS IDENT NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.13 5.14 5.231 5.13 5.14 5.231 5.13 5.14 5.231 5.231
5.13 5.14 5.31 5.32
FLIGHT PLANNING
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
ARRIVAL/DEPARTURE (PR) INTER INTER
INTER INTER FILE
4.1.27.2 FIX ATD FIX FIX
CONTINUATION RECORD SAME AS ABOVE FIX ATD ATD ATD RECORD CYCLE
IDENT IDENT IDENT IDENT NUMBER
CONTINUATION

NOTES:

FLIGHT PLANNING SAME PARAGRAPH AS ABOVE 5.195 5.195 5.195 5.195 5.31 5.32
5.195
ARRIVAL/DEPARTURE (PR) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.27.3 FILE
CONTINUATION RECORD SAME AS ABOVE TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION TIME OF OPERATION RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.46 or 5.257
PATH POINT 5.10 5.266 5.267 5.225 5.226 5.267 5.268 5.227 5.259 5.265 5.263 5.264 5.229
5.3 5.6 5.14 5.180 5.31 5.32
(PP) 4.1.28.1 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
RUNWAY OR OPS REF REF LTP COURSE PATH
CUST/ ARPT APPROACH FPAP FPAP LENGTH FILE
HELIPAD SBAS PATHPATH DATA LTP LATITUDE LTP LONGITUDE ELLIPSOID GPA WIDTH AT POINT HAL VAL CRC RECORD CYCLE
AREA IDENT IDENT DATA LATITUDE LONGITUDE OFFSET
PRIMARY IDENT TYPE SPI IDENTIFIER HEIGHT THRESHOLD TCH NUMBER
SEL
NOTES:

SAME PARAGRAPH AS ABOVE 5.225 5.227 5.227 5.262 5.244 5.269

PATH POINT 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(PP) 4.1.28.2
FPAP FPAP LTP APPROACH GNSS FILE
CONTINUATION RECORD SAME AS ABOVE ELLIPSOID ORTHOMETRIC ORTHOMETRIC TYPE CHANNEL HPC RESERVED (49) RECORD CYCLE
CONTINUATION HEIGHT HEIGHT HEIGHT IDENT NO. NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 52

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT

Page 12 of 14

PRIMARY 5.3 5.6 5.14 5.44 5.244 5.46 5.47 5.36 5.37 5.243 5.2455.246 5.52 5.39 5.74 5.197 5.247 5.248 5.31 5.32
GLS (PT) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
GLS STATION
4.1.29.1 CUST/ ARPT OR
REF PATH
GLS RUNWAY GLS APP STATION STATION GLS MAG STATION DATUM STATION ELEVATION
FILE
CYCLE
AREA IDENT CHANNEL IDENT BEARING LONGITUDE IDENT CODE RECORD
IDENT LATITUDE VAR TYPE (WGS-84)
PRIMARY HEPT ELEVATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.31 5.32
GLS (PT) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.29.2 FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (100) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

ALTERNATE 5.75 5.250 5.251 5.251 5.253 5.251 5.253 5.251 5.253 5.251 5.253 5.251 5.253
5.3 5.14 5.253 5.31 5.32
RECORD (RA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.1.30.1 CUST/ ALTERNATE/ ALT ALT IDENT DTA
ALT IDENT DTA ALT IDENT
DTA ALT IDENT RESERVED FILE
RELATED ART DTA DTA THREE ALT IDENT FOUR DTA RECORD CYCLE
AREA IDENT ONE TWO FIVE EXPANSION
PRIMARY ARPT OR FIX NUMBER

NOTES:

AIRPORT 5.3 5.6 5.14 5.10 5.271 5.273 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.31 5.32
TAA (PK) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
TAA TAA FILE
4.1.31.1 CUST/ ARPT ICAO APPROACH PROCEDURE IAF SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR
RECORD CYCLE
AREA IDENT CODE IDENT TURN WAYPOINT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

AIRPORT 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
TAA (PK)
FILE
4.1.31.2 CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.3 5.6 5.14 5.107 5.180 5.73 5.197 5.36 5.37 5.39 5.55 5.72 5.23 5.14 5.53 5.53 5.178 5.176 5.71 5.31 5.32
HELIPORT (HA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.1.1 CUST/ HEPT ATA/ PAD
SPEED
DATUM MAG SPEED RECD TRANS TRANS TIME PAD FILE
LIMIT LATITUDE LONGITUDE ELEV HELIPORT NAME (30) RECORD CYCLE
AREA IDENT IATA IDENT CODE VAR LIMIT VHF ALTITUDE LEVEL ZONE DIMENSIONS
PRIMARY ALTITUDE NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
HELIPORT (HA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95

4.2.1.2 NOTES ON CONTINUATION RECORD (69) RESERVED (31)

FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.116 5.116 5.153 5.6 5.14 5.31 5.32
HELIPORT (HA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.1.3 FIR UIR START/END
AS FILE
CONTINUATION RECORD SAME AS ABOVE RESERVED (23) ARPT RESERVED (50) RECORD CYCLE
IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION IND NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.31 5.32

HELIPORT (HA) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.1.4 CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69)
FILE
RESERVED (31) RECORD CYCLE
NUMBER
FLIGHT PLANNING CONTINUATION
NOTES:
 ARINC SPECIFICATION 424 - Page 53

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT

Page 13 of 14

5.XX
5.3 5.41 5.14 5.13 5.42 5.36 5.37 5.39 5.197 5.196 5.43 5.31 5.32
X
HELICOPTER TERMINAL 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
WAYPOINT (HC) CUST/
HELIPORT WAYPOINT D
WP ELEV
DATUM NAME FILE
IDENT TYPE LATITUDE LONGITUDE (REST FOR NAME/DESC (25) RECORD CYCLE
4.2.2.1 PRIMARY AREA IDENT MAG VAR
SIM)
CODE IND
NUMBER

NOTES:

HELICOPTER TERMINAL SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
WAYPOINT (HC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95

4.2.2.2 CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (31)
FILE
CYCLE
RECORD
CONTINUATION NUMBER

NOTES:

HELICOPTER TERMINAL SAME PARAGRAPH AS ABOVE

5.116 5.116 5.153 5.31 5.32
WAYPOINT (HC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.2.3 START/END FILE
FIR UIR
CONTINUATION RECORD SAME AS ABOVE RESERVED (80) RECORD CYCLE
IDENT IDENT DATE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

HELICOPTER TERMINAL SAME PARAGRAPH AS ABOVE

SAME PARAGRAPH AS PRIMARY RECORD (4.2.2.1)
5.31 5.32
WAYPOINT (HC) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.2.4 FILE
CONTINUATION RECORD SAME AS ABOVE CONTINUATION RECORD SAME AS PRIMARY RECORD (4.2.2.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:

HELIPORT 5.9 &

5.3 5.6 5.14 5.11 5.12 5.13 5.17 5.211 5.23 5.204 5.24 5.25 5.26 5.27 5.30 5.30 5.53 5.72 5.70 5.271 or 5.144 5.31 5.32
5.10
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130

(HD/HE/HF) RTE DIST CENTER FIX FILE

CUST/ HELIPORT SID/STAR/APP TRANS SEQ FIX DESC RECD ARC THETA RHO MAG ALTITUDE ALTITUDE TRANS SPEED VERT or TAA PROC
RNP HOLD RECORD CYCLE
4.2.3.1 AREA IDENT IDENT IDENT NR IDENT CODE NAVAID RADIUS CRS ALTITUDE LIMIT ANGLE
PRIMARY DIST/TIME TURN IND NUMBER

NOTES:

HELIPORT SAME PARAGRAPH AS ABOVE

5.170 5.170 5.170 5.170 5.171 5.171 5.171 5.171 5.67 5.30 5.70 5.242 5.211 5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(HD/HE/HF) FILE
CAT A CAT B CAT C CAT D CAT A CAT B CAT C CAT D PROC LOC LOC PROC RNP RESERVED (26)
4.2.3.2 CONTINUATION RECORD SAME AS ABOVE CAT RECORD CYCLE
DH DH DH DH MDH MDH MDH MDH TCH ALT VNAV
CONTINUATION NUMBER

NOTES:
HELIPORT SAME PARAGRAPH AS ABOVE
5.153 5.27 5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(HD/HE/HF)
START/END RTE FILE
4.2.3.3 CONTINUATION RECORD SAME AS ABOVE RESERVED (45) CYCLE
RECORD
DATE DIST
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
HELIPORT SAME PARAGRAPH AS ABOVE SAME PARAGRAPH AS PRIMARY RECORD (4.2.3.1)
5.31 5.32
SIDS/STARS/APPROACH 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
(HD/HE/HF) FILE
4.2.3.4 CONTINUATION RECORD SAME AS ABOVE CONTINUATION RECORD SAME AS PRIMARY RECORD (4.2.3.1) RECORD CYCLE
FLIGHT PLANNING CONTINUATION NUMBER

NOTES:
ARINC SPECIFICATION 424 - Page 54

4.0 NAVIGATION DATA - RECORD LAYOUT ARINC 424 - 17 RECORD FORMAT

Page 14 of 14

HELIPORT 5.3 5.6 5.14 5.144 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.146 5.147 5.145 5.31 5.32
MINIMUM SECTOR 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
ALTITUDE (MSA) (HS) RESRVD FILE
CUST/ ARPT MSA RESERVED (15) SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC SEC
4.2.4.1 EXP RECORD CYCLE
AREA IDENT CENTER BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD BRG ALT RAD
PRIMARY (3) NUMBER

NOTES:

HELIPORT SAME PARAGRAPH AS ABOVE

5.61 5.31 5.32
MINIMUM SECTOR 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
ALTITUDE (MSA) (HS) FILE
4.2.4.2 CONTINUATION RECORD SAME AS ABOVE NOTES ON CONTINUATION RECORD (69) RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:

5.106
5.3 5.6 5.14 5.101 5.103 5.36 5.37 5.39 5.92 5.183 5.184 5.184 5.185 5.14 5.200 5.14 5.105 5.31 5.32
HELIPORT COMM (HV) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
4.2.5.1 CUST/ HEPT COMM COMM SERV MAG FAC ALTITUDE ALTITUDE SECTOR REMOTE FILE
LATITUDE LONGITUDE SECTOR CALL SIGN (25) RECORD CYCLE
AREA IDENT TYPE FREQ IND VAR ELEV 1 2 FAC FAC
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE 5.186

HELIPORT COMM (HV) 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95
4.2.5.2
FILE
CONTINUATION RECORD SAME AS ABOVE NARRATIVE (60) RESERVED (36) CYCLE
RECORD
CONTINUATION NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
HELIPORT COMM (HV)
4.2.5.3 FILE
CONTINUATION RECORD SAME AS ABOVE RECORD CYCLE
CONTINUATION NUMBER

NOTES:

HELIPORT 5.3 5.6 5.14 5.10 5.271 5.273 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.274 5.146 5.147 5.31 5.32
TAA (HK) 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
TAA TAA FILE
4.2.6.1 CUST/ HELI ICAO APPROACH PROCEDURE IAF SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR SECTOR
RECORD CYCLE
AREA IDENT CODE IDENT TURN WAYPOINT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT RADIUS BEARING MIN ALT
PRIMARY NUMBER

NOTES:

SAME PARAGRAPH AS ABOVE

HELIPORT 5.31 5.32
5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 105 110 115 120 125 130
TAA (HK)
FILE
4.2.6.2 CONTINUATION RECORD SAME AS ABOVE RESERVED (14) RECORD CYCLE
CONTINUATION NUMBER

NOTES:
 ARINC SPECIFICATION 424 - Page 55
5.0 NAVIGATION DATA - FIELD DEFINITIONS
5.1 General Source/Content: “AREA” Codes should be derived from
Figure 5-2. Airline codes should be derived from the
Chapter 5 sets forth definitions/descriptions and content for standard list of abbreviated identifiers maintained and
each type of field employed in the records discussed in published in the IATA Airline Coding Directory. On
Chapter 4. The following information is presented for each Company Route and Preferred Route Records, an
field: additional AREA field is used as a pointer to the AREA in
which the Route Segment is located. For records, which do
(i) Field Name (paragraph heading) not follow geographical boundaries, the field is blank. For
(ii) Abbreviation used in proportional record layouts Preferred Routes, the field content is “PDR.”
(Chapter 4) when different than Field Name (follows
paragraph heading)
(iii) Field Definition/Description Used On: All records with content as defined
(iv) Source/Content of each field above.
(v) Length of field, expressed in number of characters Length: 3 characters max
(vi) Type of character allowed in each field, alpha or Character Type: Alpha
numeric or alpha/numeric Examples: Areas - USA, CAN, EUR
(vii) Examples of field content when appropriate and/or Customer - UAL, DAL, TWA
necessary Preferred Routes - PDR

The following general rules apply to the format of all the

fields: 5.4 Section Code (SEC CODE)

(i) All numeric fields, and the numeric parts of latitude, Definition/Description: The “Section Code” field defines
longitude, magnetic variation, negative elevation and the major section of the navigation system data base in
station declination fields will be right justified and which the record resides.
filled with leading zeros.
(ii) All alpha and alpha/numeric fields will be left
justified. Source/Content: Figure 5-1 shows the data base section
(iii) Allowable field content of blank is defined as encoding scheme.
alpha/numeric content.
Used On: All records
5.2 Record Type (S/T) Length: 1 character
Character Type: Alpha
Definition/Description: The “Record Type” field content
indicates whether the record data are “standard,” i.e.,
suitable for universal application, or “tailored,” i.e. 5.5 Subsection Code (SUB CODE)
included on the master file for a single user’s specific
purpose (Section 1.2 of this Specification refers). Definition/Description: The “Subsection Code” field
defines the specific part of the database major section in
Source/Content: The field contains the letter “S” when the which the record resides.
field data are “standard” and the letter “T” when they are
“tailored.” Additionally, records that reference other records within
the database use Section/Subsection Codes to make the
Used On: All records reference, together with the record identifier. This is true
Length: 1 character for “fix” information in Holdings, Enroute Airways,
Character Type: Alpha Airport and Heliport SID/STAR/APPROACH, all kinds
of Communications, Airport and Heliport MSA, Airport
5.3 Customer/Area Code (CUST/AREA) and Heliport TAA, Company Routes, Enroute Airway
Restrictions, Preferred Routes and Alternate Records.
Definition/Description: The “Customer Area Code” field The Section Code will define the major database section,
permits the categorization of standard records by the Subsection Code permits the exact section (file) to be
geographical area and of tailored records by the airlines for identified and the “fix” (record) can then be located
whom they are provided in the master file. Several record within this file.
types do not adhere to the established geographical
boundaries. There is no “AREA” in such records.
ARINC SPECIFICATION 424 - Page 56
5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: Figure 5-1 shows the database ICAO Location Identifier of the airport or heliport when
Subsection Encoding Scheme. such is published. It will be the three or four character
Domestic Identifier when published and no ICAO Location
Used On: All records Identifier is available for the airport or heliport. When used
Length: 1 character on Airport or Heliport Flight Planning Continuation
Character Type: Alpha Records, it will be the Airport or Heliport Identifier owning
the terminal controlled airspace referenced in that record.
Section Section Subsection Subsection Name
Code Name Code Note: Within the continental United States and within
A MORA S Grid MORA Canada, in addition to using the published four
D Navaid Blank VHF Navaid character ICAO Location Identifiers, data
B NDB Navaid suppliers append the character “K” for the USA or
E Enroute A Waypoints “C” for Canada to certain Domestic Identifiers to
M Airway Markers present an ICAO look-alike four character
P Holding Patterns identifier.
R Airways and Routes
T Preferred Routes COMMENTARY
U Airway Restrictions
V Communications Where no officially published identifier is available, a
H Heliport A Pads data supplier may create a unique, temporary and
C Terminal Waypoints unofficial identifier. Airports or Heliports within such
D SIDs identifiers may supply Tailored Data only and with full
E STARs knowledge and concurrence of the data user.
F Approach Procedures Whenever possible, such temporary identifiers should
K TAA be coordinated among the various data suppliers prior
S MSA to its release.
V Communications
P Airport A Reference Points The content of this Airport/Heliport Identifier should
B Gates not be confused with the perhaps more familiar
C Terminal Waypoints ATA/IATA two or three character identifiers often
D SIDs user by airlines for other than navigation purposes.
E STARs These ATA/IATA identifiers are included in the
F Approach Procedures ARINC 424 database in accordance with Section
G Runways 5.107 of this Specification.
I Localizer/Glide Slope
K TAA Used On: Airport Identifier - VHF Navaid, NDB
L MLS Navaid, Airport Terminal Waypoint, Airport,
M Localizer Marker Airport Gate, Airport SID/STAR/Approach,
N Terminal NDB Runway, Airport and Heliport Localizer,
P Path Point Airport and Heliport Localizer Marker,
R Flt Planning ARR/DEP Holding Pattern, Airport Communications,
S MSA Airport and Heliport MLS, GLS Airport
T GLS Station MSA, Airport TAA, Path Point Flight
V Communications Planning Arrival Departure Data, GLS
Record, and Enroute Airway Restriction and
R Company Blank Company Routes Company Route to the Airport Identifier.
Routes
A Alternate Records Heliport Identifier - VHF Navaid, NDB
T Tables C Cruising Tables Navaid, Heliport Terminal Waypoint,
G Geographical Heliport, Heliport SID/STAR/Approach,
Reference Airport and Heliport Localizer, Airport and
U Airspace C Controlled Airspace Heliport Localizer Marker, Holding Pattern,
F FIR/UIR Heliport Communications, Airport and MLS,
R Restrictive Airspace GLS Heliport MSA, Heliport TAA, Path
Point Flight Planning Arrival/Departure Data,
Figure 5-1 GLS Records, and Enroute Airway
Section and Subsection Encoding Scheme Restriction and Company Route to the
Airport Identifier.
5.6 Airport/Heliport Identifier (ARPT/HELI IDENT)
Definition/Description: The “Airport Identifier” and the Length: 4 characters maximum
“Heliport Identifier” fields contain the identification of the Character Type: Alpha/numeric
airport or heliport to which the data contained in the record Examples: KJFK, DMIA, 9Y9, CYUL, EDDF,
relates. 53Y, CA14
Source/Content: The content of this field is derived from
official government sources. It will be the four character
 ARINC SPECIFICATION 424 - Page 57

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Figure 5-2
Geographical Area Codes
ARINC SPECIFICATION 424 - Page 58

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.7 Route Type (RT TYPE) Airport STAR (PE) and Heliport STAR (HE) Records

Definition/Description: The “Route Type” field defines Field

the type of Enroute Airway, Preferred Route, Airport and STAR Route Type Description
Content
Heliport SID/STAR/Approach Routes of which the record STAR Enroute Transition 1
is an element. For Airport and Heliport Approach Routes, STAR or STAR Common Route 2
“Route Type” includes a “primary route type,” and up to STAR Runway Transition 3
two “route type qualifiers.” RNAV STAR Enroute Transition 4
RNAV STAR or STAR Common Route 5
Source/Content: The content of this field (for approach RNAV STAR Runway Transition 6
procedures) will be as indicated in the following tables: Profile Descent Enroute Transition 7
Profile Descent Common Route 8
Enroute Airway Records (ER) Profile Descent Runway Transition 9
FMS STAR Enroute Transition F
Airway Type Field FMS STAR or STAR Common Route M
Content FMS STAR Runway Transition S
Airline Airway (Tailored Data) A
Control C Airport Approach (PF) and Heliport Approach
Direct Route D (HF) Records
Helicopter Airways H
Officially Designated Airways, Route
O Approach Route Type Description Type Field
except RNAV, Helicopter Airways
RNAV Airways R Content
Undesignated ATS Route S Approach Transition A
Localizer/Backcourse Approach B
Preferred Route Records (ET) VORDME Approach D
Flight Management System (FMS) F
Field Approach
Route Type Description Instrument Guidance System (IGS)
Content
North American Routes for North Approach G
C
Atlantic Traffic
Common Portion Instrument Landing System (ILS) I
Approach
Preferential Routes D
Pacific Oceanic Transition Routes GNSS Landing System (GLS)Approach J
J Localizer Only (LOC) Approach L
(PACOTS)
TACAN Routes – Australia M Microwave Landing System (MLS) M
North American Routes for North Approach
Atlantic Traffic – Non-common N Non-Directional Beacon (NDB) N
Portion Approach
Preferred/Preferential Overflight 0 Global Positioning System (GPS)
Routes P
Approach
Preferred Routes P Non-Directional Beacon + DME
Traffic Orientation System Routes (NDB+DME) Approach Q
S
(TOS) Area Navigation (RNAV) Approach
Tower Enroute Control Routes R
T (Note 1)
(TEC) VOR Approach using
VORDME/VORTAC S
Airport SID (PD) and Heliport SID (HD) Records TACAN Approach T
Simplified Directional Facility (SDF) U
SID Route Type Description Field Approach
Content VOR Approach V
Engine Out SID 0 Microwave Landing System (MLS), Type
SID Runway Transition 1 W
A Approach
SID or SID Common Route 2 Localizer Directional Aid (LDA)
SID Enroute Transition 3 X
Approach
RNAV SID Runway Transition 4
RNAV SID or SID Common Route 5 Microwave Landing System (MLS), Type Y
RNAV SID Enroute Transition 6 B and C Approach
FMS SID Runway Transition F Missed Approach Z
FMS SID or SID Common Route M
FMS SID Enroute Transition S The listing above for Approach Route Type is alphabetical
Vector SID Runway Transition T and does not represent any kind of priority.
Vector SID Enroute Transition V
 ARINC SPECIFICATION 424 - Page 59
5.0 NAVIGATION DATA - FIELD DEFINITIONS

Airport Approach (PF) and Heliport (HF) Records – the Qualifier 1 and Qualifier 2 are used to sort
Route Type the file content.

Qualifier Qualifier COMMENTARY

Qualifier Description 1 Field 2 Field Although there seems to be universal acceptance of
Content Content GLS as the procedure title for GBAS procedures, the
DME Required for D Qualifier 1 Code of “L” that could be applied to an
Procedure RNAV or RNAV (GPS) procedure published with
GPS required, DME/DME J appropriate minimums has been retained as a
to RNP xx.x not authorized precaution.
GBAS Procedure L
DME Not Required for Used On: Enroute Airways, Airport and Heliport
N SID/STAR/Approach, Preferred Route
Procedure
GPS Required P
Length: 1 character for Enroute Airways, Airport
GPS or DME/DME to RNP R and Heliport SID and STAR and
xx.x required Preferred Routes.
DME/DME Required for T
Procedure 3 characters for Airport and Heliport
RNAV, Sensor Not Approach Procedures.
U
Specified
VOR/DME RNAV V Character Alpha/numeric
Type:
SBAS Procedure (Note 2) W
Primary Missed Approach A Approach LDC = a Localizer-based procedure, for
Secondary Missed Approach B Examples: localizer only, no glide slope, with DME
Engine Out Missed required, Circle-To-Land Minimums.
E
Approach
LNC= A Localizer-based procedure, for
Procedure with Circle-To- C localizer only, no glide slope, DME not
Land Minimums required, Circle-To-Land Minimums
Procedure with Straight-in S
Minimums S S = A VOR procedure, using
VORDME or VORTAC Navaid, the
Not all qualifiers apply to all Route Types. Qualifier fields DME is not required for the procedure,
may be blank where appropriate. the minimums are straight-in.

Note 1: Route Type “R” is used for all types of RNAV S C = A VOR procedure, using
procedure coding except GLS. The type of VORDME or VORTAC Navaid, the
RNAV procedure is further defined through the DME is not required for the procedure,
content of Qualifier 1. Conventional Area the minimums are Circle-To-Land
Navigation Approach using RHO-RHO or RHO- D S = A VOR/DME procedure, using a
THETA equipment is Route Type “R,” Qualifier VORDME or VORTAC Navaid, the
1 “T” or “V.” RNAV (GPS) Approach DME is required for the procedure, the
procedures should be coded as Route Type “R,” minimums are straight-in.
Qualifier 1 “J,” “L,” “R,” “U” or “W,” as
appropriate. V_S = A VOR procedure using VOR
Navaid with only NAVAID, no DME
Note 2: Path Point Data Records are required to support installed, minimums are straight-in.
these Approach Procedure Types. V C = A VOR procedure, using a VOR
Navaid with no DME capability, the
Note 3: The Qualifiers 1 values of “D” and “N” can be minimums are Circle-To-Land
used in conjunction with any Route Type except
for Route Type “R,” “V,” “D,” “S,” “N” and N S = A NDB procedure, minimums are
“Q.” The values in Qualifier 1 should be set straight-in.
consistently for all portions of the coded
procedure. Qualifier 2 is additionally provided Q S = A NDB + DME procedure, the
on the approach and missed approach segments. DME is required, the minimums are
There is no defined qualifier 2 content for straight-in.
approach transitions.
5.8 Route Identifier (ROUTE IDENT)
Note 4 Qualifier 2 values “A” and “B” can be used only
in conjunction with Route Type “Z.” Definition/Description: The “Route Identifier” field
identifies a route of flight or traffic orientation, using the
Note 5: The content of this Route Type is split in the coding employed on aeronautical navigation charts and
record layout. The Primary Route Type is in related publications.
column 20 and the Qualifiers 1 and 2 in columns
119 and 120. Both the Primary Route Type and Source/Content: For Enroute Airways, Route Identifier
codes should be derived from official government
ARINC SPECIFICATION 424 - Page 60

5.0 NAVIGATION DATA - FIELD DEFINITIONS

publications. For Preferred Routes, Route Identifiers may 5.10 Approach Route Identifier (APPROACH IDENT)
or may not be provided in government publications.
Where they are available, they will be used. Definition/Description: The “Approach Route Identifier”
field contains the identifier of the approach route to be
For North American Routes for North Atlantic Traffic, flown. To facilitate the provision of multiple approach
“Common Portion” and other similar route system, route procedures of the same type to a given runway, the field
identifier code shall be those published in government also is used to provide a “multiple indicator.”
sources. For the European Traffic Orientation System or
other similar route systems such as North American Source/Content:
Routes for North Atlantic Traffic, “Non-common
Portion,” Preferred Routes and Preferential Routes Column Contents
published without official and/or flight plan identifiers, Type of Approach-Alpha Character,
but published as between specific airports or other 1 generally the same as the first column of
navigation fixes, route identifiers define the initial fix and field 5.7 Route Type
the terminus fix idents according to the naming rules in Runway Identification- Numeric in tens of
Chapter 7. For routings which do not include a unique 2-3
degrees, valid range 01-36
initial or terminus fix, rules on creating unique Route Runway Designation
Identifiers are also contained in Chapter 7. Those rules Place holder if other runway
have been developed with use of the Geographical
Reference Tables (TG). Refer to Chapter 3, Section - (dash) designation codes are not
present and multiple indicators
3.2.7.2 and Chapter 4, Section 4.1.26 for more detail. required.
4 L Left
Used On: Enroute Airway, Preferred Route R Right
Records and Geographical Reference C Center
Table T Runway oriented to True North
Length: Enroute Airway - 5 character maximum Position 5 and 6 must also be
Preferred Route - 10 character maximum Blank
Blank
Character Type: Alpha/numeric
Examples: Enroute Airway - V216, C1150, J380, 5 Multiple Indicator Alphanumeric or Blank
UA16, UB414 6 Blank
Preferred Routes - N111B, TOS13,
TOS14WK, CYYLCYYC, For Approach procedures that are not specific to a runway
ARTCOLAR, KZTLKSAV, such as circle-to-land procedures a 4 character Alpha
SCNDICANRY entry should be used with the fifth alphanumeric character
used for multiple indicator if necessary.
Refer to Section 7 for specific examples and their meaning.
For Helicopter Approach Procedures to Runways, the first
position of the identifier will be the type of approach. The
5.9 SID/STAR Route Identifier (SID/STAR IDENT) second through fourth positions will carry a three digit
numeric character representing the runway designated or
Definition/Description: “The SID/STAR Route Identifier” the procedure final approach course, expressed in full
field contains the name of the SID or STAR, using the basic degrees. Where the same final approach course is used
indicator, validity indicator and route indicator abbreviated multiple times in official source, the fifth position will
to six characters with the naming rules in Chapter 7 of this carry a multiple indicator.
document.
For Helicopter Approach Procedures to Heliports and
Source/Content: SID/STAR route identifier codes should coded to a specific pad, the first position of the identifier
be derived from official government publications describing will carry a character indicating the type of approach. The
the terminal procedures structure. second through sixth characters will carry the pad
identification. There is no provision for a multiple
Used On: Airport SID/STAR, Heliport SID/STAR indicator for more than one approach of the same type to
and Flight Planning Arrival/Departure the same pad in this identifier field. When required, a
Data Records multiple indicator is provided in a separate field.
Length: 6 characters max
Character Type: Alpha/numeric
Examples: DEPU2, SCK4, TRP7, 41M3, MONTH6
 ARINC SPECIFICATION 424 - Page 61
5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Airport and Heliport Approach Record Route Type Field Content
Route Records, Flight Planning
Engine Out 0 Runway (RWY) or Pad Identifier
Arrival/Departure Data, Path Point SID
and Airport, Heliport Localizer, SID/RNAV 1 or 4 Runway (RWY) or Pad Identifier
Airport and Heliport TAA, and SID
Simulation Continuation Records. 2 or 5 Blank/RWY/PAD/ALL (see Notes 1
Length: 6 characters max. and 3)
Character Type: Alpha/numeric 3 or 6 SID Enroute Transition Identifier
Examples: FMS SID F Runway (RWY) or Pad Identifier
Runway I26L, B08R, R29, V01L, N35 M Blank/RWY/PAD/All (see Notes 1
Dependent L16RA, L16RB, V08-A, V08-B and 3)
I18L1, I18L2, N08T R35-Y, R35- S FMS SID Enroute Transition Identifier
Z Vector SID T Runway (RWY) or Pad Identifier
Circle-To-Land VORA, VORB VOR-A, VOR-B, V Vector SID Enroute Transition
Identifier
NDBB,CVOR, VDMA, LOCD,BI
P168, NDAT (NDB, DME, Alpha, STAR/RNAV 1 or 4 STAR Enroute Transition Identifier
STAR
True), NDB-1, NDB-2 2 or 5 RWY/PAD/ALL/Blank (see Note 3)
Helicopter to I13L, L040, V175, N175B 3 or 6 Runway (RWY) or Pad Identifier
Runway (Note 2)
Helicopter to IA127 = ILS Procedure to a pad Profile Descent 7 Profile Descent Enroute Transition
Helipad designated A127 Ident
VBRAVO =VOR Procedure to a 8 RWY/PAD/ALL/Blank (see Note 3)
Pad designated BRAVO 9 Runway (RWY) or Pad Identifier
N23 =NDB Procedure to a Pad (Note 2)
designated 23 FMS STAR F FMS STAR Enroute Transition
RWESTA RNAV Procedure to a Identifier
Pad designated West Alpha M RWY/PAD/ALL/Blank (See Note 3)
S Runway (RWY) or Pad Identifier
(Note 2)
5.11 Transition Identifier (TRANS IDENT)
Approach A Approach Transition Identifier
Transitions
Definition/Description: The “Transition Identifier” field Missed Z Missed Approach Transition Identifier
describes the type of transition to be made from the Approach (Note 4)
enroute environment into the terminal area and vice versa, Approach All Other
and from the terminal area to the approach or from the Procedure Codes (see Blank
runway or helipad to the terminal area. Section 5.7)

Source Content: The content of the transition identifier Figure 5-3

field should be determined from the content of the Route Transition Identifier Field Content
Type field (See Section 5.7) in accordance with the rules
set forth in Figure 5.3 Note 1: If there is no Route Type 1 or 4 or F for the SID,
then the SID records with the Route Type of 2 or
5 or M will have an entry in the Transition
Identifier field. If there is a Route Type of 1 or 4
or F for the procedure, then the records with the
Route Type of 2 or 5 or M will carry a blank
transition identifier field.
Note 2: If there is no Route Type 3 or 6 or 9 or S for the
STAR, then the STAR record with the Route
Type of 2 or 5 or 8 or M will have an entry in the
Transition Identifier field. If there is a Route
Type 3 or 6 or 9 or S for the procedure, then the
Transition Identifier in the Route Type 2 or 5 or
8 or M will carry a blank transition identifier
field.
Note 3: The use of “ALL” in the Transition Identifier
field indicates that the procedure is valid for two
or more runways at an airport or all helipads at a
heliport. The use of the character “B” along with
a runway designation such as RW08B in the
Transition Identifier field indicates that the
transition is valid for two or more parallel
runways, e.g. RW08L and RW08R.
Note 4: The Missed Approach Transition Identifier will
be the identifier of the Missed Approach Holding
Fix or the last fix in the missed approach path if
ARINC SPECIFICATION 424 - Page 62

5.0 NAVIGATION DATA - FIELD DEFINITIONS

there is no holding fix. If multiple missed preceding and following records at the desired location are
approach paths are published to the same zeros (indicating no previous modification at this point), the
termination but with different paths or units character or the inserted record’s sequence number
constraints, a transition identifier closely aligned should be five (5). For records taken in sequence with one
with the published source indication for each or two digit sequence numbers, additional data must be
missed approach will be used. entered in the proper sequence and all subsequent records
will be up numbered accordingly.
Enroute Transition Identifiers are normally the identifier
of a navaid or waypoint. Transition Identifiers should be When an enroute airway crosses the boundary separating
derived from official government sources, where two geographical areas (Section 5.3), the airway fix lying
provided. on or closest to the boundary shall be coded twice, once for
each geographical area, and should be assigned the same
Used On: Airport and Heliport SID/STAR/ sequence number in each case. Record uniqueness in such
Approach, Flight Planning cases is maintained through the “Boundary Code” (Section
Arrival/Departure Data and Company 5.18). Enroute airway record sequence numbers should be
Route Records assigned in a manner which permits them to be arranged
Length: 5 characters max. into continuous airway routes in flight sequence order when
Character Type: Alpha/numeric sorted according to the Route Identifier and Sequence
Examples: 9TU, ETX, KEENE, DEN, RW08R, Number only, without regard to their applicable
Blank Geographical Area Code.

5.12 Sequence Number (SEQ NR) Used On: Enroute Airways, Airport and Heliport
MSA Records, Airport and Heliport
Definition/Description: For Route Type Records - A TAA Records, Airport and Heliport
route of flight is defined by a series of records taken in SID/STAR/Approach, Company Route,
order. The “Sequence Number” field defines the location Cruise Tables, FIR/UIR, Restrictive
of the record in the sequence defining the route of flight Airspace, Controlled Airspace,
identified in the route identifier field. For Boundary Type Preferred Routes, Flight Planning
Records - A boundary is defined by a series of records Arrival/Departure Data and VHF
taken in order. The “Sequence Number” field defines the Navaid Limitation Continuation
location of the record in the sequence defining a Records
boundary. For Record Types requiring more than one Length: 4 characters - Enroute Airways, Preferred
primary record to define the complete content – In a series Routes, FIR/UIR and Restrictive
of records used to define a complete condition, the Airspace
“Sequence Number” is used to define each primary record
in the sequence. For Airport and Heliport TAA Records – 3 characters - SID/STAR/Approach and
Sequence Number 1 will always be assigned to the record Company Routes
based on the Center Fix upon which the Straight-In Area
is predicated, Sequence Number 2 will always be assigned 2 characters - VHF Navaid Limitation
to the record based on the Center Fix upon which the Left Continuation Records
Base Area is predicated, and Sequence Number 3 will 1 character - MSA Table, TAA
always be assigned to the record based on the Center Fix Table, Cruise Table
upon which the Right Base Area is predicated. Therefore, Character Type: Numeric
if a TAA Record has a Straight-In Area and a Right Base Examples: 0010, 0135, 2076, 120, 030, 01, 84, 3
Area, but no Left Base Area, only Sequence Numbers 1
and 3 will be used. If a TAA Record has a Straight-In 5.13 Fix Identifier (FIX IDENT)
Area and a Left Base Area but no Right Base Area, only
Sequence Numbers 1 and 2 will be used. Definition/Description: The “Fix Identifier” field contains
the five-character-name-code, or other series of characters,
Source/Content: Sequence numbers are assigned during the with which the fix is identified. This includes Waypoint
route, boundary or sequence definition phase of the data file Identifiers, VHF NAVAID Identifiers, NDB NAVAID
assembly. Sequence numbers are assigned so as not be identifier, Airport Identifiers, and Runway Identifiers.
duplicated within the route, boundary or sequence assigned
a unique identification/designation. For three or four digit Source/Content: Officially published identifiers or
Sequence Numbers, initially, an increment of ten should be identifiers derived in accordance with Chapter 7, Naming
maintained between the sequence numbers assigned to Conventions, of this document.
consecutive records. For one or two digit Sequence
Numbers, the initial increment is one. In route or boundary Used On: Holding Patterns, Enroute Airways,
records, should subsequent maintenance of the file Airport and Heliport SID/STAR/
necessitate the addition of a record or records, the new Approach, Enroute Airway Restrictions,
record(s) should be located in the correct position in the and Enroute Waypoints, Airport and
sequence and assigned a sequence number whose most Heliport Terminal Waypoints
significant characters are identical to those in the sequence (Waypoint Ident) and Flight Planning
number of the preceding record in sequence. The unit Arrival/Departure Data Records.
character should be assigned a value midway between the Length: 5 characters max
units character values of the preceding and following record Character Type: Alpha/numeric (no embedded blanks)
sequence numbers. For example, if it is desired to add one Examples: SHARP, DEN43, BHM, RW27L,
record to the sequence and the units characters of both the KGRR
 ARINC SPECIFICATION 424 - Page 63
5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.14 ICAO Code (ICAO CODE) 5.17 Waypoint Description Code (DESC CODE)
Definition/Description: The “ICAO Code” field permits Definition/Description: Fixes are located at positions
records to be categorized geographically within the limits of significant to navigation in the Enroute, Terminal Area
the categorization performed by the “Area Code” field. and Approach Procedure path definitions. The “Waypoint
Description Code” field enables that significance or
Source/Content: The code is to be employed in the ICAO function of a fix at a specific location in a route to be
code field may be found in ICAO Document No. 7910, identified. The field provides information on the type of
“Location Indicators.” fix. As a single fix can be used in different route
structures and multiple times within a given structure, the
In order to permit sub-division of the United States into field provides the function for each occurrence of a fix.
more easily manageable regions, the ICAO code for the
USA (K) is followed by a numeric character obtained from Source/Content: Valid contents for the “Waypoint
Figure 5-5. Description Code” are contained in the table below. The
contents of Column 40 provide information on the fix
Used On: All records except Cruising Tables and type. Column 41 is used to define whether the fix is a
Grid MORA “fly-over” or “fly-by” fix and to indicate the charting
Length: 2 characters max status of some waypoints. Columns 42 and 43 provide the
Character Type: Alpha/numeric fix function information. Column 40, Code “G,” is valid
Examples: K1,K7,PA,MM,EG,UT for Runway as Waypoint and Helipad as Waypoint.

5.15 Intentionally Left Blank

5.16 Continuation Record Number (CONT NR)

Definition/Description: When it is not possible to store all

the information needed on a record within the 132 columns
of the record itself, the so-called Primary Record; one or
more continuation records may be used. The “Continuation
Record Number” identifies the position of a continuation
record in a sequence of such records.

Source/Content: Primary records contain the numeric “0”

when no Continuation Records are included in the file for
that Primary. The numeric “1” in this field of the Primary
Record indicates that one or more Continuation Records
follow the Primary Record. Continuation Records are
numbered sequentially starting with the numeric “2” in the
first continuation. If the information requirement goes
beyond a Continuation Record with the numeric “9,” the
sequence is continued with alpha characters, starting with
“A” and continuing through to “Z” as required.
Used On: All records except Company Route,
Airport Localizer Marker/Locator,
Enroute Markers, Cruising Tables,
FIR/UIR and Grid MORA
Length: 1 character
Character Type: Alpha/numeric
Examples: 0, 1, 2 (through 9) A, B, C
(through Z)
 ARINC SPECIFICATION 424 - Page 64

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Explanation of superscript notes and other details required

Waypoint Description Enroute, to understand this table:
STAR,APRCH for
COL COL COL COL
the line “Airport 1. Any waypoint (not Navaid, Airport or Runway) in
as Waypoint” Terminal Procedures or any waypoint (not Navaid or
Type/ Function Used On 40 41 42 43 airport) on Enroute Airways, required for navigation
Airport as Waypoint STAR, APCH A such as a change in bearing, intersection of two
1 Enroute, SID, airways, beginning or end of continuous segment. See
Essential Waypoint E Special Navigation Terms in Section 2.
STAR, APCH
Off Airway Waypoint2 Enroute F
2. Any waypoint published by government source but not
Runway as Waypoint, SID, STAR,
G part of any route structure.
Helipad as Waypoint APCH
Heliport as Waypoint STAR, APCH H
3. A waypoint established during procedure coding on the
Enroute, SID, nominal track.
NDB Navaid as Waypoint N
STAR, APCH
3 SID, STAR, 4. Any waypoint (not Navaid or airport) on Enroute
Phantom Waypoint P
APCH Airways that is not considered “Essential” or
Non-Essential Waypoint4 Enroute R “Transition Essential.” See Special Navigation Terms
Transition Essential
Enroute T
in Section 2.
Waypoint5
Enroute, SID, 5. Any waypoint (not Navaid or airport) on Enroute
VHF Navaid As Waypoint V
STAR, APCH Airways for the purpose of transitioning between the
Flyover Waypoint, End of Enroute and Terminal structures. See Special
SID, STAR Route Type, SID, STAR, Navigation Terms in Section 2.
B
APCH Transition or Final APCH
Approach6 6. A fly-over waypoint (including Navaid) specified by
End of Enroute Airway or the procedure: (a) at the end of a SID or STAR Route
Enroute, SID, Type; (b) at the end of an Approach Transition for
Terminal Procedure Route E
STAR, APCH FMS, GPS, or MLS/RNAV approach; or (c) at the
Type
Uncharted Airway missed approach point in an Approach Procedure.
Enroute U
Intersection7
SID, STAR, 7. Any waypoint (not Navaid and airport) on Enroute
Fly-Over Waypoint8 Y Airways that has not been established by government
APCH
Unnamed Stepdown Fix
source. Used only in conjunction with “E” in Column
After Final Approach Fix20
APCH A 40.
Unnamed Stepdown Fix
8. Any waypoint (including Navaid and airport) that must
Before Final Approach APCH B
be over flown before establishing on the following leg.
Fix20
ATC Compulsory 9. Any waypoint (including Navaid and airport) on
Enroute C
Waypoint 9 Enroute Airways at which a “position report” must be
Oceanic Gateway made to the appropriate Air Traffic Control unit. See
Enroute G
Waypoint10 Special Navigation Terms in Section 2.
First Leg of Missed
APCH M
Approach Procedure11 10. Any waypoint (including Navaid) designated as the
19
Path Point Fix APCH P start/end of an oceanic organized track system. See
Named Stepdown Fix18 APCH S Special Navigation Terms in Section 2.
Initial Approach Fix12 APCH A
Intermediate Approach 11. Coded on the first leg after a runway fix or missed
APCH B approach point fix dependent on approach procedure
Fix13
Initial Approach Fix with coding rules in Attachment 5. The leg may be the first
APCH C leg of a published missed approach procedure or a leg
Holding
Initial Approach Fix with to the published missed approach point.
APCH D
Final Approach Course Fix
Final End Point Fix16 APCH E 12. Any waypoint (including Navaid) established as an
Published Final Approach
Initial Approach Fix. See Special Navigation Terms in
Fix or Database Final APCH F
Section 2.
Approach Fix14
13. Any waypoint (including Navaid) established as an
Enroute SID,
Holding Fix H Intermediate Approach Fix and not coded as a Final
STAR, APCH
Approach Course Fix. See Special Navigation Terms
Final Approach Course in Section 2.
APCH I
Fix15
Published Missed 14. Any waypoint (including Navaid) established as a Final
M
Approach Point Fix17 Approach Fix. This may be a fix published as the Final
Approach Fix by government source or, when no such
Figure 5-4 Waypoint Description fix is published, one established by a data supplier
 ARINC SPECIFICATION 424 - Page 65
5.0 NAVIGATION DATA - FIELD DEFINITIONS

according to the rules in Attachment 5. See Special

Navigation Terms in Section 2.
15. Any waypoint (including Navaid) established as a Final
Approach Course Fix. This may be a fix published as
the Final Approach Course Fix by government source
or, when no such fix is published but yet required, one
established by a data supplier according to the rules in
Attachment 5. See Special Navigation Terms in
Section 2.

16. Any waypoint established as the Final End Point.

This may be a fix published as the FEP by the
government source or, when no such fix is published
but yet required, one established by the data supplier.
It is used in vertical coding of non-precision approach
procedures. See Special Navigation Terms in Section
2.
17. Any waypoint (including Navaid or Runway)
established as a Missed Approach Point by government
source, may follow a Runway Fix when such is
required by the rule in Attachment 5. The code is used
in conjunction with “G” in Column 40 when the
Runway is the published Missed Approach Point.

18. Any waypoint established and named by the

government source lying between the Final Approach
Fix and the Missed Approach Point or between a
published Final Approach Course Fix and a Final
Approach Fix.

19. Any waypoint established by the government source

in support of RNAV-GPS/GLS Approach
Procedures. Path Points are not part of the defined
procedure track but are provided in a separate record
where required. The points are not named and are
always referred to as Path Point 1 and Path Point 2.

20. Any published but unnamed waypoint lying between

the Final Approach Fix and the Missed Approach
Point (Code “A”) or between the Final Approach
Course Fix and the Final Approach Fix (Code “B”).
Note 1: Column 40, the fix type column, may be blank
when a particular leg of a procedure does not
include a fix, such as those legs ending in
intercepts or terminating altitudes. For more
information on such legs, refer to the Leg Data
Table in Attachment 5.
Note 2: With the rules provided for Columns 42 and 43,
as further explained by references 11 and 17, it is
possible to have the code “M” in both of the
columns for one leg in cases where a runway fix
which is not the designated missed approach
point has been inserted into the procedure
coding.

Used On Airport and Heliport

SID/STAR/Approach, Enroute
Airway Records
Length: 4 Characters
Character Type: Alpha
ARINC SPECIFICATION 424 - Page 66

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Figure 5-5
7 SUBDIVISIONS FOR UNITED STATES
 ARINC SPECIFICATION 424 - Page - 67

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.18 Boundary Code (BDY CODE) 5.21 Path and Termination (PATH TERM)
Definition/Description: Routes of flight frequently cross Definition/Description: The Path and Termination defines the
geographical boundaries. The “Boundary Code” field path geometry for a single record of an ATC terminal
identifies the area into, or from which a continuous route procedure.
passes when such a crossing occurs.
Source/Content: Attachment 5 to this document, “Path and
Source/Content: See Table 5-6. Terminator,” contains the various Path Term codes available
for coding an ATC terminal procedure.
Used On: Enroute Airways records
Length: 1 character Used On: Airport and Heliport
Character Type: Alpha/numeric SID/STAR/Approach records
Length: 2 characters
Area Area Code* Boundary Code Character Type: Alpha
USA USA U
Canada and Alaska CAN C 5.22 Turn Direction Valid (TDV)
Pacific PAC P
Latin America LAM L Definition/Description: This field is used in conjunction with
South America SAM S Turn direction to indicate that a turn is required prior to
South Pacific SPA 1 capturing the path defined in a terminal procedure.
Europe EUR E
Eastern Europe EEU 2 Source/Content: The field contains the alpha character “Y”
Middle East-South Asia MES M when a turn is required prior to beginning the leg defined by
Africa AFR A the Path Term. The direction of the turn is specified in
Section 5.20.
*From Figure 5-2
Used On: Airport and Heliport
Table 5-6 - Boundary Codes SID/STAR/Approach Records
Length: 1 character
5.19 Level (LEVEL) Character Type: Alpha

Definition/Description: The Level field defines the airway 5.23 Recommended NAVAID (RECD NAV)
structure of which the record is an element.
Definition/Description: The “Recommended Navaid” field
Source/Content: allows the reference facility for the waypoint in a given
record “Fix Ident” field or for an Airport or Heliport to be
specified. VHF, NDB (Enroute and Terminal), Localizer,
B All Altitudes TACAN, GLS and MLS Navaids may be referenced.
H High Level Airways
L Low Level Airways Source/Content: The 1, 2, 3 or 4 character identification of
the Navaid appears in this field. Navaids recommended for
Used On: Enroute Airway, Preferred Routes, waypoint reference in official government publications will
Restrictive Airspace, and Controlled be used when available. The following general rules on field
Airspace records content apply:
Length: 1 character
Character Type: Alpha a. A “VHF Navaid” may be any VOR, DME, VORDME,
VORTAC, TACAN or Un-Biased ILSDME available in
5.20 Turn Direction (TURN DIR) the database.
Definition/Description: The “Turn Direction” field b. A “NDB Navaid” may be any NDB or Locator
specifies the direction in which Terminal Procedure turns (Terminal NDB) available in the database.
are to be made. It is also used to indication direction on
course reversals, see Attachment 5 Path and Termination. c. Localizers, GLS Reference Path, and MLS Azimuth are
used as Recommended Navaids for procedures that
Source/Content: The field contains the alpha character reference those navaids.
“L” for Left turns, “R” for Right turns and “E” for turns
in either direction. d. The Recommended Navaid in final approach procedure
coding will be the procedure reference facility (when
Used On: Airport and Heliport Recommended Navaid is provided in coding).
SID/STAR/Approach records
Length: 1 character e. The Recommended Navaid in Airport and Heliport
Character Type: Alpha Records will be any VOR, VORDME, TACAN or
VORTAC available in the database.

f. The Recommended Navaid in any Enroute Airway

Record will be any VORDME or VORTAC available in
the database.
ARINC SPECIFICATION 424 - Page - 68

5.0 NAVIGATION DATA - FIELD DEFINITIONS

g. The Recommended Navaid in any Terminal

Procedure Record other than the final approach
coding will be the procedure reference facility of a
type from the Definition/Description paragraph
above and will be in accordance with the rules
governing Recommended Navaids for Path
Terminators and coding rule as defined in
Attachment 5 of this Specification.
h. The rules for Recommended Navaids for
Converging ILS Approach Procedures are the same
as for ILS Approach Procedures.

i. The Recommended Navaid used in a GLS

Approach Procedure will be the GLS Ref Path
identifier appropriate to the runway and approach.
Used On: Enroute Airway Record, Airport and
Heliport SID/STAR/Approach
Records, Airport and Heliport Record
Length: 4 characters max.
Character Type: Alpha/numeric
Examples: P, PP, DEN, LAX, ILAX, MJFK
 ARINC SPECIFICATION 424 - Page - 69

5.0 NAVIGATION DATA - FIELD DEFINITIONS

VOR Only Final Approach

NDB Only Final Approach

Localizer Final Approach

TACAN Final Approach

Transitions of course or

VORDME/VORTAC
Approach Transitions

Path Terminator - FD

heading to intercept

NDB + DME Final

Path Terminator –

Path Terminator –

Missed Approach

& Single Record

Final Approach
Procedure Use

Transitions
SID/STAR

Approach
localizer
CD, VD

Airports
CR, VR
Facility
Type

&
Co-located VOR X X X X X X X [3] X
DME/VORTAC
Theta-Rho X|X X|X X| | X|X X|X X|X | | |X | |

Non-Co-located X X X [3] X
VORDME/
VORTAC
|
Theta/Rho | X|X | | X|X | X|X | | |X | |
Localizer X X X X
Theta/Rho | | | | | | X | X | | | | | |
VOR X X X X X
Theta/Rho | | X| | | | | | X | | | | |
DME X X X [3]
Theta/Rho | | | | |X | | | | | | X | |
TACAN [4] X X X X X [3] X X
Theta/Rho X|X X|X | | |X X|X | | | | |X X|X |

NDB X X X [2]
Theta/Rho | | | | | | | | | | | | |

[2] On FACF and FAF Records

[3] On Runway/MAP Records Only

Figure 5-7 Procedure Use

ARINC SPECIFICATION 424 – Page 70
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.24 Theta (THETA) Used On: Airport and Heliport

SID/STAR/Approach, Enroute Airway
Definition/Description: “Theta” is defined as the magnetic and Flight Planning Arrival/ Departure
bearing to the waypoint identified in the record’s “FIX Data Records
Ident” field from the Navaid in the “Recommended Length: 4 characters
Navaid” field. Character Type: Alpha/numeric
Examples: 2760, 0231, 194T
Source/Content: Theta values are derived from official
government sources when available. They are provided in 5.27 Route Distance From, Holding Distance/Time
degrees and tenths of a degree, with the decimal point (RTE DIST FROM, HOLD DIST/TIME)
suppressed. The content is controlled through requirements
of the Path Terminator and coding rules contained in Definition/Description: In Enroute Airways, “Route
Attachment 5 of this specification. Distance From” is the distance in nautical miles from the
waypoint identified in the records “Fix Ident” field to the
next waypoint of the route. In SID, STAR and Approach
Used On: Airport and Heliport Procedure records, the field may contain segment
SID/STAR/Approach, Enroute Airway distances/along track distances/excursion distances/DME
Records distances. The actual content is dependent on the Path and
Length: 4 characters Termination. For more information on the content, refer to
Character Type: Alpha/numeric Table Three, Leg Data Fields, in Attachment 5 of this
Examples: 0000, 0756, 1217 1800 document.
Source/Content: The field contains distances, from official
5.25 Rho (RHO) government source where available, expressed in nautical
miles and tenths of nautical miles with the decimal point
Definition/Description: “RHO” is defined as the geodesic suppressed. For Holding Pattern Records and/or Path and
distance in nautical miles to the waypoint identified in the Terminations defining holdings patterns, content may be
record’s “Fix Ident” field from the NAVAID in the “holding time” expressed in minutes and tenths of minutes
“Recommended NAVAID” field. preceded by the character “T” with the decimal point
suppressed.
Source/Content: Rho values derived from official
government sources will be used when available. They are Used On: Airport and Heliport
entered into the field in nautical miles and tenths of a SID/STAR/Approach, Enroute Airway
nautical mile, with the decimal point suppressed. The Records
content is controlled through requirements of the Path Length: 4 characters
Terminator and coding rules contained in Attachment 5 of Character Type: Distance - Numeric;
this specification. Time - Alpha/numeric
Examples: 1076, 2822, T010, 0208, 0016

Used On: Airport and Heliport 5.28 Inbound Magnetic Course (IB MAG CRS)
SID/STAR/Approach, Enroute Airway
Records Definition/Description: “Inbound Magnetic Course” is
Length: 4 characters the published inbound magnetic course to the waypoint in
Character Type: Alpha/numeric the “Fix Ident” field of the records in which it is
Examples: 0000, 0216, 0142, 1074 employed.
The “HX” group of Path Terminator codes is used to
provide racetrack type course reversal flight paths.
5.26 Outbound Magnetic Course (OB MAG CRS) Government publications for these course reversal include
an “inbound magnetic bearing.” The
Definition/Description: “Outbound Magnetic Course” is SID/STAR/Approach Procedures records do not include a
the published outbound magnetic course from the waypoint dedicated field for this inbound course. Instead, the
identified in the record’s “Fix Ident” field. In addition, this information is included in the “Outbound Magnetic
field is used for Course/Heading/Radials on SID/STAR Course” field of such records.
Approach Records through requirements of the Path
Terminator and coding rules contained in Attachment 5 of Source/Content: Values from official government
this specification. sources will be used when available. The field contains
magnetic bearing in degrees and tenths of a degree, with
Source/Content: Values from official government sources the decimal point suppressed. For routes charted with true
will be used when available. The field contains magnetic courses, the last character of this field will contain a “T”
information expressed in degrees and tenths of a degree, in place of tenths of a degree.
with the decimal point suppressed. For route and procedure
segments charted in “degrees true,” the last character Used On: Enroute Airways records
(tenths position) of the field will contain the character “T”. Length: 4 characters
See Section 5.165 of this document for more information Character Type: Alpha/numeric
on “degrees true” information. Examples: 2760, 0231, 194T
 ARINC SPECIFICATION 424 – Page 71
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.29 Altitude Description (ALT DESC) In Approach Records, use is limited to

Approach Transitions with the exception of the
Definition/Description: The “Altitude Description” field last leg of a transition and to Missed Approach
will designate whether a waypoint should be crossed “at,” with the exception of the first leg of a missed
“at or above,” “at or below” or “at or above to at or approach.
below” specified altitudes. The field is also used to
designate recommended altitudes and cases where two Note: The “C” entry may only appear in SID records.
distinct altitudes are provided at a single fix. It is used to indicate that the leg has a
conditional altitude termination.
Source/Content: A code from the following table, selected
based on official government source or coding rules in Note: In Final Approach Route Coding for Precision
Attachment 5 to this document. Approach Procedures with electronic Glide
Slope the codes “@ (for blank),” “G,” “H,” “I,”
Field and “J,” are applied as indicated in the table
Waypoint Crossing Description
Content above. For more detail refer to procedure coding
“At or above” altitude specified in first “Altitude” rules in Attachment 5 of this Specification.
+ (plus) field. Also used with Localizer Only Altitude
field. Note Codes “I” and “J” are only used when the first
“At or below” altitude specified in first “Altitude” altitude for the FACF fix is not blank. If that
- (minus) field. Also used with Localizer Only Altitude altitude is blank, the Altitude Description is also
field. blank, even when the second altitude is not
@ “At” altitude specified in first “Altitude” field. blank.
(blank) Also used with Localizer Only Altitude field.
“At or above to at or below” altitudes specified in Note: The codes “V,” “X” and “Y” are used with all
B fixes defined in government source as step-down
the first and second “Altitude” fields.
“At or above” altitude specified in second fixes and from the FACF inbound on final
C approach coding. There can be two altitudes
“Altitude” field.
Glide Slope altitude (MSL) specified in the provided on every fix in final approach coding.
second “Altitude” field and “at” altitude specified Altitude 1 is the altitude and constraint specified
G in the first “Altitude” field on the FAF Waypoint at the fix, the so-called “procedure altitude.”
in Precision Approach Coding with electronic Altitude 2 is the “at” altitude on the coded
Glide Slope. vertical path at the fix. See rules for fix altitude
Glide Slope Altitude (MSL) specified in second coding in Attachment 5 of this Specification.
“Altitude” field and “at or above” altitude
H specified in first “Altitude” field on the FAF Note: Localizer Only Altitude information is provided
Waypoint in Precision Approach Coding with in the Approach Continuation Record for
electronic Glide Slope Precision Approach Procedures with electronic
Glide Slope Intercept Altitude specified in second Glide Slope using the codes for “At,” “At or
“Altitude” field and “at” altitude specified in first Above” and “At or Below” appropriately based
I “Altitude” field on the FACF Waypoint in on government source publications. This
Precision Approach Coding with electronic Glide Altitude is the non-precision altitude at the fix on
Slope which it is coded. Provided on FAF and step-
Glide Slope Intercept Altitude specified in second
down fix waypoints.
“Altitude” field and “at or above” altitude
J specified in first “Altitude” field on the FACF
Used On: Airport and Heliport
Waypoint in Precision Approach Coding with
SID/STAR/Approach, Primary and
electronic Glide Slope
Continuation Records, Airport,
Heliport and Enroute
“At” altitude on the coded vertical angle in the
Communications, VHF NAVAID
second “Altitude” field and “at or above” altitude
V Limitation Continuation, Preferred
specified in first “Altitude” field on step-down fix
Routes and Flight Planning
waypoints.
Arrival/Departure Data Records.
“At” altitude on the coded vertical angle in Length: 1 character
X the second “Altitude” field and “at” altitude Character Type: Alpha
specified in the first “Altitude” field on step-
down fix waypoints. 5.30 Altitude/Minimum Altitude
“At” altitude on the coded vertical angle in
Y the second “Altitude” field and “at or below” Definition/Description: The “Altitude/Minimum
altitude specified in the first “Altitude” field Altitude” field indicates the reference altitude associated
on step-down fix waypoints. with (1) Enroute Airways (MEA, MFA or other minimum
altitudes as defined by source), (2) holding pattern path of
Note: The “B” entry may only appear in Airport and Holding Pattern record, (3) altitudes at fixes in terminal
Heliport SID/STAR/Approach Route, procedures and terminal procedure path termination
Airport/Enroute/Heliport Communications, defined by the Path Terminator in the Airport or Heliport
VHF Navaid Limitation and Preferred Route SID/STAR/Approach Record and (4) lowest altitude of
Records. The higher value will always appear the “blocked altitudes” for a Preferred Route.
first in records with two altitude fields, or as the
first three digits of the Altitude Limitation field.
ARINC SPECIFICATION 424 – Page 72
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Source/Content: Reference altitudes are determined Used On: Airport and Heliport
during route definition. The values are derived from SID/STAR/Approach, Primary and
official government source when available. This Continuation Records, Holding
specification includes specific rules for altitude provision Pattern, Enroute Airway, Preferred
and when those altitudes are not provided by source Routes.
documents, they will be included by data suppliers Length: 5 characters
according to those rules. The field may contain altitudes Character Type: Alpha/numeric
(all numeric) or flight level (alpha/numeric). The all- Examples: 05000, FL050, 18000, FL180 00600,
numeric fields will contain altitudes in feet with a -0012, 29000, FL290, UNKNN or
resolution of one foot. The alpha/numeric fields will NESTB (the last two on Enroute
contain the alpha characters “FL” followed by the altitude Airways only)
expressed in hundreds of feet (three digits) or a code as
indicated below. 5.31 File Record Number (FRN)
On Airport and Heliport SID, STAR and Approach Route Definition/Description: The “File Record Number” is a
records, the first “Altitude” field will contain an altitude reference number assigned to the record for housekeeping
when “Altitude Description” field contains a plus (+), a purposes. Records are numbered consecutively, the first
minus (-), or one of the following characters: “B,” “G,” record on the file being assigned the number 00001, the
“H,” or “V.” The first “Altitude” field may contain an second the number 00002, and so on through the final
altitude when the “Altitude Description” field contains a record on the file. File record numbers are subject to
“I” or “J” or when it is blank. The second “Altitude” field change at each file update.
will contain an altitude when the “Altitude Description”
field contains one of the following characters: “B,” “C,” Source/Content: File record numbers are assigned to
“G,” “H,” “I,” “J,” or “V.” In approach procedure records during the assembly of the data file. If the file
coding, some fix “Altitudes” may be below sea level, reaches 99999, the next record number will start over with
specifically altitudes at runway fixes when the runway 00000.
threshold elevation is below sea level. In these cases, the
“Altitude” will be expressed in feet with a minus (-) sign Used On: All records
in the first character of the five-character field, see Length: 5 characters
examples. Character Type: Numeric
Examples: 10640, 00420, 31462
On Airport and Heliport SID/STAR/Approach
Continuation Records, the “Localizer Only Altitude” field 5.32 Cycle Date (CYCLE)
will contain an altitude when there is a non-precision
altitude at the fix that is associated with using the ILS Definition/Description: The “Cycle Date” field identifies
procedure as a Localizer Only (Glide Slope out) the calendar period in which the record was added to the
procedure. Such an altitude may be provided for the Final file or last revised. A change in any ARINC 424 field,
Approach Fix (FAF) or any step-down fix from the FACF except Dynamic Magnetic Variation, Frequency Protection,
inbound on the final approach course. Continuation Record Number and File Record Number,
requires a cycle date change. The cycle date will not
On Enroute Airway records, the first “Minimum Altitude” change if there is no change in the data.
field will contain the MEA or MFA if the altitude is the
same for both directions of flight and the second Source/Content: The first two digits of the field contain the
“minimum Altitude” will be blank. If the airway segment last two digits of the year in which the addition or revision
has directional MEAs/MFAs, the first “Minimum was made. The last two digits contain the numeric identity
Altitude” field will contain the value for the direction of of the 28-day data update cycle during which the change
flight in which the airway is coded and the second occurred. Each calendar year contains 13 such cycles,
“Minimum Altitude” field will contain the value for the however, on rare occasions 14 cycles will be encountered.
opposite direction of flight. The first “Minimum Altitude”
field may contain the alpha characters UNKNN when the Used On: All records
MEA/MFA is unknown or the alpha characters NESTB Length: 4 characters
when the MEA/MFA has not been established by the Character Type: Numeric
appropriate authority.
5.33 VOR/NDB Identifier (VOR IDENT/NDB IDENT)
On Preferred Routes, the “Minimum Altitude” and the
“Maximum Altitude” apply to the entire route and are a Definition/Description: The “VOR/NDB Identifier” field
minimum and maximum block. Altitude 1 and Altitude 2 identifies the VHF/MF/LF facility defined in the record.
are fix related apply only to the fix in the sequence in
which they occur and are defined by the Altitude Source/Content: The field contains the official government
Description field. 1-, 2-, 3- and 4-character facility identification code.
Used On: VHF NAVAIDs, NDB NAVAIDs,
Airport Localizer Marker records,
Airport and Heliport Localizer, and
Airport and Heliport MLS records.
Length: 4 characters max
Character Type: Alpha/numeric
Examples: DEN, 6YA, PPI, TIKX
 ARINC SPECIFICATION 424 – Page 73
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.34 VOR/NDB Frequency (VOR/NDB FREQ)

Col Col Col Col Col
Definition/Description: The “VOR/NDB Frequency” field 28 29 30 31 32
specifies the frequency of the NAVAID identified in the Facility
Navaid Navaid Range/ Add Col-
“VOR/NDB Identifier” field of the record. Type 1 Type 2 Power Info location
VOR V
Source/Content: Frequencies are derived from official DME D
government sources. VHF NAVAID frequencies contain TACAN
characters for hundreds, tens, units, tenths and hundredths (channels 17- T
of megahertz. NDB frequencies contain characters for 59 & 70-126)
thousands, hundreds, tens, units and tenths of kilohertz. MIL TACAN
(channels 1-16 M
The decimal point following the unit entry is suppressed in & 60-69)
both cases. ILS/DME I
ILS/TACAN I
Used On: VHF NAVAID, NDB NAVAID, MLS/DME/N N
Airport Localizer Marker records MLS/DME/P P
Length: 5 characters Range/Power
Character Type: Numeric Terminal T
Examples: VHF 11630, 11795 NDB 03620, Low Altitude L
17040 High Altitude H
U
5.35 NAVAID Class (CLASS) Undefined
Note 3
C
ILS/TACAN
Definition/Description: The “Navaid Class” field Note 4
provides information in coded format on the type of Additional
navaid, the useable range or assigned output power of the Information
navaid, information carried on the navaid signal and Biased
collocation of navaids in both an electronic and ILSDME or D
aeronautical sense. The field is made up of five columns ILSTACAN
of codes that define this information. Automatic
Transcribed
A
Weather
Source/Content: The information for the five columns is Broadcast
derived from official government source. The mapping of Scheduled
the information codes to the output record columns for the Weather B
various types of navaids is contained in the tables below. Broadcast
No Voice on
W
Used On: Navaid Records (VHF, NDB and Frequency
Airport/Heliport Voice on
Blank
Frequency
Localizer/Markers/Locators) Collocation
Length: 5 characters (including “blanks”) Collocated
Blank
Character Type: Alpha Navaids
Non-
N
VHF Navaid Record – Includes VOR, VORDME, Collocated
Note 1
VORTAC, TACAN, ILSDME and MLSDME type Navaids
navaids, Output Record Section/Subsection D
ARINC SPECIFICATION 424 – Page 74
5.0 NAVIGATION DATA – FIELD DEFINITIONS

NDB Navaid Record –NDBs and Terminal NDBs, Output Airport/Heliport Localizer Marker/Locator Record –NDB
Record Section/Subsection DB and PN Locator and Marker Navaids, Output Record
Section/Subsection PM
Col Col Col Col Col
28 29 30 31 32 Col. 75 Col. 76 Col. 77 Col. 78 Col. 79
Col- Navaid Navaid Range/ Col-
Navaid Navaid Range/ Add/ Facility Add Info
Facility locatio Type 1 Type 2 Power location
Type 1 Type 2 Power Info
n NDB H
NDB H SABH S
SABH S Marine Beacon M
Marine Beacon M Inner Marker I
Inner Marker I Middle Marker M
Middle Marker M Outer Marker O
Outer Marker O Back Marker C
Back Marker C Range/Power
Range Power 200 Watts or More H
200 Watts or More H 50 to 1999 Watts Blank
50 to 1999 Watts Blank 25 to Less Than 50 M
25 to Less Than 50 M Less Than 25 L
Less Than 25 L Additional
Additional Information
Information Automatic
Automatic Transcribed A
Transcribed A Weather Broadcast
Weather Broadcast Scheduled
B
Scheduled Weather Weather Broadcast
B
Broadcast No Voice on
W
No Voice on Frequency
W
Frequency Voice on
Blank
Voice on Frequency Blank Frequency
Collocation Collocation
B B
BFO Operation BFO Operation
Note 5 Note 5
Locator/Marker A
Collocated Note 2
Locator/Middle
N
Marker Not
Note 2
Collocated

Note 1: Collocations: For VHF Navaid records, the

character “N” in column 32 is entered if either
the latitude and/or the longitude of the VOR and
the Collocated DME or TACAN of a frequency
paired VORDME or VORTAC differ by 1/10
arc minutes or more. Column 32 is “blank” on
VHF Navaids where the difference in latitude or
longitude is less than the 1/10-arc minutes.
Column 32 of the VHF Navaid will also carry
the “N” or “blank” meaning listed above for
frequency paired ILSDMEs and ILSTACANs.
Note that in this later case, the character is
carried on the ILSDME or ILSTACAN record as
the Localizer record is not part of the VHF
Navaid Section.
Note 2: Collocation: For Airport/Heliport Localizer
Marker/Locator records, the character “N” in
column 79 is entered if either the latitude or
longitude of a Marker and it aeronautically
associated Locator differ by 1/10-arc minutes or
more. The character “A” in column 79 is entered
if the latitude or longitude of a Marker and its
aeronautically associated Locator differ by less
than 1/10-arc minutes. Column 79 is left “blank”
when the latitude and longitude of the Marker
and Locator are exactly the same.
 ARINC SPECIFICATION 424 – Page 75
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Note 3: VHF Navaid Records, Range/Power. The Used On: NAVAID, Waypoint, Airport and
character “U” is entered into column 30 on Heliport ILS, Airport, Gate, Runway,
VHF Navaid Records when the official Airport and Heliport Localizer Marker,
government source has not defined the use of Airport and Heliport MLS and GLS,
the facility or has not restricted such use by Airport and Heliport MLS Continuation,
range or altitude. Airway Marker, Airport and Heliport
Communications, Enroute
Note 4: VHF Navaid Records, Range Power. The Communications, Heliport, Restrictive
character “C” is entered into column 30 when Airspace, FIR/UIR, Controlled Airspace,
that records contains a TACAN Navaid that is Path Point and GLS Records.
frequency paired with an ILS Localizer with the Length: 9 characters
same identifier at the same location. The Character Type: Alpha/numeric
character is only used in combination with the Examples: N39513881
character “I” in column 29. If the “C” appears in
column 30, the Range is understood to be “T” = 5.37 Longitude (LONGITUDE)
Terminal use. Note that in some output files, this
TACAN Navaid may be listed twice, once as a Definition/Description: The Longitude field contains the
TACAN and once as an ILSTACAN, depending longitude of the geographic position of the navigational
on the individual government source publication. feature identified in the record.
Note 5: NDB Navaids, Airport/Heliport Localizer Source/Content: Geographic positions whose longitudes
Marker/Locator Navaids, BFO Operations. must be included in the data base are defined during route
While not a “collocation” indication, the design, many of them in official government publications.
character “B” is entered in the Collocation The field is constructed as follows: The first character
Columns (32 of NDB Navaids and 79 of position will contain the alpha character “E” or “W,”
Airport/Heliport Localizer Marker/Locator indicating whether the longitude is east or west of the
Navaids) to indicate the type of signal emitted prime (zero degree) meridian. For longitudes falling on the
by the Navaid requires the use of a Beat 0 or 180 degree meridians, “E” is entered. The following
Frequency Oscillator (BFO) to make the morse nine numeric characters define the longitude in degrees,
identifier transmission audible. Should both a minutes, seconds, tenths of seconds and hundredths of
collocation and a BFO condition exist for one seconds. Degree, minute and second symbols and the
and the same Navaid Record, preference is decimal point are suppressed.
given to the collocation characters.
Note: Some RNAV system users may elect to round off
5.36 Latitude (LATITUDE) longitude values to resolutions of less than one
hundredth of a second prior to the entry of these data
Definition/Description: The “Latitude” field contains the into the airborne computer.
latitude of the navigational feature identified in the record.
The navigation reference points to be defined by latitude
Source/Content: Geographic positions whose latitudes and longitude coordinates are listed in Figure 5-8.
must be included in the data base are defined during route
design, many of them in official government publications. Used On: NAVAID, Waypoint, Airport and
The field is constructed as follows. The first character Heliport ILS, Airport, Gate, Runway,
position contains the alpha character “N” or “S” indicating Airport and Heliport Localizer Marker,
whether the latitude is north or south of the equator. “N” is Airport and Heliport MLS, GLS
entered for latitudes falling on the equator. The following Airports and Heliport MLS
eight numeric characters define the latitude in degrees, Continuation, Airway Marker, Airport
minutes, seconds, tenths of seconds and hundredths of and Heliport Communications, Enroute
seconds. Degree, minute and second symbols and the Communications, Heliport, Restrictive
decimal point are suppressed. Airspace, FIR/UIR, Controlled
Airspace, Path Point and GLS Records.
Note: Some RNAV system users may elect to round off Length: 10 characters
latitude values to resolutions of less than one Character Type: Alpha/numeric
hundredth of a second prior to the entry of these data Examples: W104450794
into the airborne computer.
The navigation reference points to be defined by latitude
and longitude coordinates are listed in Figure 5-8.
ARINC SPECIFICATION 424 – Page 76
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Note 7: On Communications Records, the Latitude and

Record File Lat/Long Field Location Defined
Longitude always define the transmitter antenna
Airport Airport
Aerodrome Reference site, regardless if that site is a Remote
Point Communications Outlet or independent
Airport Comm Comm (Note 7) Transmitter Antenna transmitter position not associated with a Navaid.
Enroute Comm Comm (Note 7) Transmitter Antenna
Enroute Marker Marker Marker Antenna 5.38 DME Identifier (DME IDENT)
FIR/UIR FIR/UIR Boundary Position
FIR/UIR Arc Origin Center of Arc Definition/Description: The identification of a DME
Gate Gate Gate facility, a TACAN facility or the DME (or TACAN)
Heliport Heliport Helipad component of a VORDME or VORTAC facility.
Heliport Comm Comm Transmitter Antenna
Localizer Localizer Localizer Antenna
Source/Content: The “DME Identifier” field will contain
the officially published 2-, 3-, or 4-character DME facility
Localizer Glide Slope (Note 6) Glide Slope Antenna
identifier. For VOR/DME and VORTAC facilities, if the
Marker/Locator Marker Beacon Marker Antenna identification codes of the VOR and DME components of
Marker/Locator Locator Locator Antenna the NAVAID defined in the record are the same, the field
NDB Navaid NDB NDB Antenna will be blank. If they are not the same, the VOR
Restr. Airspace Restr. Airspace Boundary Position Identification will be as defined in Section 5.33 and the
Restr. Airspace Arc Origin Center of Arc DME Identifier field will carry the identification of the
VHF Navaid VOR (Note 1) VOR Antenna DME component. The field is blank when the VHF
DME or TACAN DME or TACAN Navaid facility in the reference record has no DME
VHF Navaid
(Note 2) Antenna component. The field will always contain the DME
Runway Landing Identifier for TACANs, DME Only NAVAIDS and
Runway Runway (Note 5) Localizer or MLS DME facilities.
Threshold
Waypoint Waypoint Waypoint
MLS Azimuth Azimuth Antenna Used On: VHF NAVAID records
MLS Elevation Elevation Antenna Length: 4 characters max
Back Azimuth Back Azimuth
Character Type: Alpha/numeric
MLS
(Note 3) Antenna
Examples: MCR, DEN, IDVR, DN, (Blank)
MLS Reference
MLS Datum (Note 4) 5.39 Magnetic Variation (MAG VAR, D MAG VAR)
Datum Point
Definition/Description: The “Magnetic Variation” field
Figure 5-8 specifies the angular difference between True North and
Magnetic North at the location defined in the record.
Note 1: The VOR latitude and longitude fields are filled “Dynamic Magnetic Variation” is a computer model
when the “NAVAID Class” field contains the derived value and takes location and date into
letter “V” in column 28 of the record. If column consideration. For the “Station Declination” used in some
28 is blank, these fields are blank also. record types, refer to Section 5.66.
Note 2: The DME or TACAN latitude and longitude Source/Content: Magnetic variations are obtained from
fields are filled when the “NAVAID Class” field official government data sources and other geographical
contains the letters “D,” “I” “M,” “N,” “P” or magnetic variation source. A number of different terms are
“T” in column 29 of the record. If column 29 is used in government documentation that have specific
blank, these fields are blank also. connotations for the information provided by that
government. The most common is “Epoch Year Variation.”
Note 3: The MLS Back Azimuth latitude and longitude In theory, this is a value determined by a government
fields are to be left blank where no such facility agency once every five years and published for general use.
exists. Along with Epoch Year Variation, some governments also
publish an annual drift value. Data suppliers do not include
Note 4: MLS Datum is the point on the runway center annual drift derived figures in their databases but rather
line closest to the phase center of the approach stay with the Epoch Year value. Another term encountered
elevation antenna. in source documentation is “Magnetic Variation of
Record.” This is generally an Epoch Year value. The
Note 5: The Runway latitude and longitude fields define difference here is that the government authority has
the Runway Landing Threshold. This threshold established the value as valid for everything associated
can be the beginning of the landing runway with a given location. For example, if a Magnetic Variation
pavement. It will be the displaced threshold of Record is established for an airport location, everything
(inward from the beginning of the landing referenced to that airport will use the same value. This is of
runway pavement) when such is published by interest as it means that Terminal Procedure design is also
official government documentation. based on that value. Obvious differences can occur
between a database supplied, semi-static value, and a value
Note 6: Localizer Glide Slope latitude and longitude may derived dynamically, either by the airborne systems or
be blank then detail not available through source supplier ground systems. Dynamic Magnetic Variation,
documentation. contained in the VHF Navaid Continuation Record and
 ARINC SPECIFICATION 424 – Page 77
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Enroute/Terminal Waypoint Primary Records, is a 5.42 Waypoint Type (TYPE)

computed, earth model derived figure, and is updated
dynamically on a schedule established by the data base Definition/Description: The “Waypoint Type” field
supplier. Position one of the field contains an alpha defines both the “type” and function of IFR waypoints
character taken from the table below followed by the value and also define a waypoint as being VFR.
of magnetic variation expressed in degrees and tenths of a
degree, with the decimal point suppressed. When the first Source/Content: The following tables define available
column is coded with the character “T,” the value will be “Waypoint Type” codes:
all zeros.
ENROUTE WAYPOINT
Field Description
Entry Waypoint Type Col Col Col
E Magnetic variation is East of TRUE North 27 28 29
W Magnetic variation is West of TRUE North Combined Named Intersection C
T The element defined in the current record is and RNAV
oriented to TRUE North in an area in which Unnamed, Charted Intersection I
the local variation is not zero. NDB Navaid as Waypoint N Note 1 Note 2
Named Intersection R
Used On: Airport, NDB Navaid, Airport Localizer Uncharted Airway Intersection U
Marker, MLS, GLS, Airway Marker, VFR Waypoint V Note 4
Enroute/ Airport/ Heliport RNAV Waypoint W
Communication, Heliport, Enroute Final Approach Fix A
Waypoint, Airport and Heliport Initial and Final Approach Fix B
Terminal Waypoint and GLS Primary Final Approach Course Fix C
Records and VHF Navaid Continuation Intermediate Approach Fix D
Records. Off-Route intersection in the
Length: 5 characters FAA National Reference System E
Character Type: Alpha/numeric Off-Route Intersection F
Examples: E0140, E0000, T0000
Initial Approach Fix I
5.40 DME Elevation (DME ELEV) Final Approach Course Fix at K
Initial Approach Fix
Definition/Description: The “DME Elevation” field defines Final Approach Course Fix at L
the elevation of the DME component of the NAVAID Intermediate Approach Fix
described in the record. Missed Approach Fix M
Initial Approach Fix and Missed N
Source/Content: DME elevations specified in official Approach Fix
government publications are entered into this field in feet Oceanic Entry/Exit Waypoint O
with respect to MSL. When the elevation is below MSL, Pitch and Catch Point in the FAA P
the first column of the field contains a minus (-) sign. High Altitude Redesign
AACAA and SUA Waypoints in S
Used On: VHF NAVAID records the FAA High Altitude Redesign
Length: 5 characters FIR/UIR or Controlled Airspace
Character Type: Alpha/numeric U
Intersection
Examples: 00530, -0140 Latitude/Longitude Intersection, V
Full Degree of Latitude
5.41 Region Code (REGN CODE) Latitude/Longitude Intersection, W
Half Degree of Latitude
Definition/Description: The “Region Code” permits the
categorization of waypoints and holding patterns as either
enroute or terminal area waypoints. In the latter case the
terminal area airport is identified in the field.
Source/Content: The field contains the alpha characters
ENRT for enroute waypoints and airport identification
code (Airport Ident) for terminal waypoints. In the holding
pattern file, the content will match that of the holding fix,
e.g. if the holding fix is an enroute waypoint or enroute
Navaid, the content with be ENRT; if the holding fix is a
terminal waypoint or terminal NDB, the content will be the
airport identification.
Used On: Waypoint and Holding Pattern records
Length: 4 characters
Character Type: Alpha/numeric
Examples: ENRT, KLAX, 9V9
ARINC SPECIFICATION 424 – Page 78
5.0 NAVIGATION DATA – FIELD DEFINITIONS
Note 4: The code V in column 27 for VFR Waypoints is
TERMINAL WAYPOINT not used in conjunction with any codes from
column 28 and 29.
Col Col Col
Waypoint Type
27 28 29 5.43 Waypoint Name/Description (NAME/DESC)
ARC Center Fix Waypoint A Note 3 Note 3
Combined Named Intersection Definition/Description: The “Waypoint Name/Description”
and RNAV Waypoint C
field sets the unabbreviated name of a named waypoint or a
Unnamed, Charted definition of an unnamed waypoint.
I
Intersection
Middle Marker as Waypoint M Source/Content: The name of a named waypoint is spelled
Terminal NDB Navaid as out in full. Definitions for unnamed waypoints are
N Note 1 Note 2 described in Chapter 7 of this specification.
Waypoint
Outer Marker as Waypoint O
Named Intersection R Used On: Enroute Waypoints, Airport and
VFR Waypoint V Note 4 Heliport Terminal Waypoints.
RNAV Waypoint W Length: 25 characters max
Final Approach Fix A
Character Type: Alpha/numeric
Examples: FORT SMITH, LAX04026,
Initial Approach Fix and Final
B LOS235/110, 6100N01234W (OCTA),
Approach Fix
OM RW26L ALTUR
Final Approach Course Fix C
Intermediate Approach Fix D 5.44 Localizer/MLS/GLS Identifier (LOC, MLS, GLS
Initial Approach Fix I IDENT)
Final Approach Course Fix at
K
Initial Approach Fix Definition/Description: The “Localizer/MLS/GLS
Final Approach Course Fix at
L
Identifier” field identifies the localizer, MLS facility or
Intermediate Approach Fix GLS Ref Path defined in the record. In the Runway
Missed Approach Fix M Record, two “Landing Systems” may be defined.
Initial Approach Fix and
Missed Approach Fix N Source/Content: The field contains the identification
Unnamed Stepdown Fix P code of the Localizer or MLS facility or GLS Reference
Named Stepdown Fix S Path derived from official government sources. In the
FIR/UIR or Controlled Runway Record, there are two fields labeled
Airspace Intersection U Localizer/MLS/GLS Reference Path identifier and second
Localizer/MLS/ GLS Reference Path identifier to encode
multiple Localizers, such as an ILS and a LDA associated
ENROUTE AND TERMINAL WAYPOINT with a single runway.
SID D
STAR E Used On: Runway, Localizer, Localizer Marker,
Approach F MLS, MLS Continuation and GLS
Multiple Z Record.
Length: 4 characters max
Character Type: Alpha/numeric
Used On: Enroute Waypoints, Airport and Examples: Localizer - IDEN, ISTX, IDU, PP MLS
Heliport Terminal Waypoints. - MDEN, MSTX, MLAX GLS - LFBL,
Length: 3 characters EGLC, KSAN
Character Type: Alpha
5.45 Localizer Frequency (FREQ)
Note 1: Column 28 of the Enroute and Terminal
Waypoint Types will always be blank when Definition/Description: The “Localizer Frequency” field
column 27 carries the “N” for NDB or Terminal specifies the VHF frequency of the facility identified in
NDB produced as Waypoints. the “Localizer Identifier” field.

Note 2: Possible codes for column 29 are identical for Source/Content: The official government-source localizer
both Enroute and Terminal Waypoints and are frequency is entered into the field with a resolution of 50
those carried in the third portion of the table. kHz. The decimal point following the unit MHz entry is
Column 29 will always be blank when column suppressed.
27 carries the “N” for NDB or Terminal NDB
produced as Waypoints. Used On: Airport and Heliport ILS Localizer
records
Note 3: When column 27 equals “A” for ARC Center Length: 5 characters
Fix Waypoint, columns 28 and 29 will always Character Type: Numeric
be blank. Examples: 11030, 11195
 ARINC SPECIFICATION 424 – Page 79
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.46 Runway Identifier (RUNWAY ID) 5.49 Localizer/Azimuth Position Reference (@,+,-)
Definition/Description: The “Runway Identifier” field Definition/Description: The “Localizer/Azimuth Position
identifies the runways described in runway records and Reference” field indicates whether the antenna is situated
runways served by the ILS/MLS described in ILS/MLS beyond the stop end of the runway, ahead of or beyond the
records. approach end of the runway. The “Back Azimuth Position
Reference” field indicates whether the antenna is situated
Source/Content: Runway identifiers are derived from ahead of the approach end of the runway, ahead of or
official government sources and are shown in the following beyond the stop end of the runway.
format:
Source/Content: For Localizer and Azimuth positions the
The two letters “RW” are followed by two numerics, 01 field is blank (@) when the antenna is situated beyond the
thru 36, and may contain a fifth character designation of stop end of the runway, it contains a plus (+) sign when the
one of the following: antenna is situated ahead of the approach end of the runway
or a minus (-) sign when it is located off to one side of the
C = Center (Runway of three parallel runways) runway. For Back Azimuth positions the field is blank (@)
L = Left (Runway of two or three parallel runways) when the antenna is situated ahead of the approach end of
R = Right (Run way of two or three parallel runways) the runway, it contains a plus (+) sign when the antenna is
T = (Runway and associated flight maneuvers situated beyond the stop end of the runway or a minus (-)
referenced only in degrees true) sign when it is located off to one side of the runway.

Any other designations (suffixes), such as North, South, Used On: ILS, MLS and MLS Continuation
East, West or STOL will not be included in the ARINC records
file. Length: 1 character
Character Type: Alpha
Used On: Airport and Heliport ILS and MLS,
GLS Runway, Airport and Heliport 5.50 Glide Slope Position (GS FR RW THRES)
Localizer Marker, Path Point and GLS Elevation Position (EL FR RW THRES)
Records.
Length: 5 characters max Definition/Description: The “Glide Slope/Elevation
Character Type: Alpha/numeric Position” field defines the location of the antenna with
Examples: RW26L, RW08R, RW26C, RW05, respect to the approach end of the runway.
RW17T
Source/Content: The field contains four numeric characters
5.47 Localizer Bearing (LOC BRG) indicating the distance in feet (to a resolution of one foot)
from a line drawn at right angles to the runway at the
Definition/Description: The “Localizer Bearing” field antenna position to the threshold of the runway.
defines the magnetic bearing of the localizer course of the
ILS facility/GLS approach described in the record. Used On: ILS and MLS records
Length: 4 characters max
Source/Content: Localizer courses, derived from official Character Type: Numeric
government sources, are entered into the field in degrees Examples: 0980, 1417
and tenths of a degree, with the decimal point suppressed.
For localizer courses charted with true courses, the last 5.51 Localizer Width (LOC WIDTH)
character of this field will contain a “T” in place of tenths
of a degree. Definition/Description: The “Localizer Width” field
specifies the localizer course width of the ILS facility
Used On: ILS, GLS records defined in the record.
Length: 4 characters
Character Type: Alpha/numeric Source/Content: Localizer course widths from official
Examples: 2570, 0147, 2910, 347T government sources are entered into the field in degrees,
tenths of a degree and hundredths of a degree with the
5.48 Localizer Position (LOC FR RW END) decimal point suppressed.
Azimuth/Back Azimuth Position (AZ/BAZ FR RW
END) Used On: ILS records
Length: 4 characters
Definition/Description: The “Localizer/Azimuth Position” Character Type: Numeric
field defines the location of the facility antenna relative to Examples: 0500, 0400, 0350
one end of the runway.

Source/Content: The field contains the official government

source distance, in feet, from the antenna to the runway
end. The resolution is one foot.
Used On: ILS, MLS and MLS Continuation records
Length: 4 characters
Character Type: Numeric
Examples: 0950, 1000
ARINC SPECIFICATION 424 – Page 80
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.52 Glide Slope Angle (GS ANGLE) Minimum hard-surfaced operational runway available without
Elevation Angle (MIN ELEV ANGLE) restriction at the airport. The value reflects overall
pavement length declared suitable and available for the
Definition/Description: The “Glide Slope Angle” field ground operations of aircraft. Where no hard-surfaced
defines the glide slope angle of an ILS facility/GLS runway is available or those available do not meet
approach. The “Minimum Elevation Angle” field defines criteria, the value will represent the longest operational
the lowest elevation angle authorized for the MLS runway at the airport.
procedure.
Used On: Airport Records
Source/Content: Glide Slope and Elevation angles from Length: 3 characters
official government sources are entered into the fields in Character Type: Numeric
degrees, tenths of a degree and hundredths of a degree Examples: 040, 055, 098, 111
with the decimal point suppressed.
5.55 Airport/Heliport Elevation (ELEV)
Used On: ILS, GLS and MLS records
Length: 3 characters Definition/Description: The elevation of the
Character Type: Numeric Airport/Heliport specified in the record is defined in the
Example: 275, 300 “Airport Elevation” and “Heliport Elevation” field.
Source/Content: Airport/Heliport elevations are to be
5.53 Transition Altitude/Level (TRANS derived from official government sources and entered into
ALTITUDE/LEVEL) the field in feet to a resolution of one foot. For elevations
above MSL, the field contains the numeric characters of the
Definition/Description: The “Transition Altitude” field elevation only. For below MSL elevations the first
defines the altitude in the vicinity of an airport or heliport character of the field is a minus (-) sign. In most cases,
at or below which the vertical position of an aircraft is airport elevation is defined as the highest elevation of any
controlled by reference to altitudes (MSL). The landing surface on the airport.
“Transition Level” field defines the lowest flight level
available for use above the transition altitude. Aircraft Used On: Airport and Heliport records
descending through the transition layer will use altimeters Length: 5 characters
set to local station pressure, while departing aircraft Character Type: Alpha/numeric
climbing through the layer will be using standard Examples: 02171, -0142, 05230
altimeter setting (QNE) of 29.92 inches of mercury,
1013.2 millibars or 1013.2 hectopascals. 5.56 Gate Identifier (GATE IDENT)
Source/Content: Transition Altitudes/Levels are derived Definition/Description: The airport gate defined in the
from official government sources. For STAR and record is identified in the “Gate Identifier” field.
Approach records, the field defines the level, expressed in
feet, at which the altimeter barometric setting is changed Source/Content: Coded gate identity information is derived
from standard to local values for the airport or heliport from official government sources and navigation system
identified in the record. For SID records, the field will users.
contain the Transition Altitude expressed in feet. The first
leg of each Airport and Heliport SID/ STAR/Approach Used On: Gate records
procedure shall contain the appropriate transition altitude Length: 5 characters max
with a resolution of one foot. If the transition altitude is Character Type Alpha/numeric
unknown “by ATC,” the field will be blank in procedure Examples: C134B, 23, 30A, B12A
records. For Airport and Heliport records, the Transition
Altitude and Transition Level will be entered into the 5.57 Runway Length (RUNWAY LENGTH)
appropriate fields, in feet with a resolution of one foot. If
the Transition Altitude or Level is unknown, “by ATC” or Definition/Description: The “Runway Length” field
has different values for varying procedures at the airport defines the total length of the runway surface declared
or heliport, the field will be blank. suitable and available for ground operations of aircraft for
the runway identified in the records’ Runway Identifier
Used On: Airport and Heliport field.
SID/STAR/Approach, Airport and
Heliport Records Source/Content: Runway lengths are derived from
Length: 5 characters official government sources and are entered in feet with a
Character Type: Numeric resolution of one foot. The value represents the overall
Examples: 05000, 23000, 18000 length of the runway, with no regard for displaced
thresholds. It does not include stopways, overruns or
5.54 Longest Runway (LONGEST RWY) clearways. Available landing lengths and take-off runs are
not necessarily identical to this runway length. Analysis
Definition/Description: The “Longest Runway” field of the content of Section 5.69, Displaced Threshold and
permits airport to be classified on the basis of the longest 5.79, Stopway is required to determine these operational
operational hard-surface runway. lengths. As the latitude/longitude information in the
runway record reflects the Landing Threshold Point of the
Source/Content: The longest runway will be derived runway identified in the record, which may or may not be
from official government sources and entered in the field displaced, there is no direct correlation between the
in hundreds of feet. This value will represent the longest Runway Length and a value calculated based on these
 ARINC SPECIFICATION 424 – Page 81
5.0 NAVIGATION DATA – FIELD DEFINITIONS

latitude/longitude values. For additional information on Used On: All except Company route records
runway length analysis and operational length Length: 70 characters max
calculations, see Figure 5-9. Character Type: Alpha/numeric
Examples: EASTBOUND PREFERRED
Used On: Runway Records 090/0Z/230/0Z
Length: 5 characters
Character Type: Numeric 5.62 Inbound Holding Course (IB HOLD CRS)
Examples: 05000, 07000, 11480
Definition/Description: The “Inbound Holding Course”
5.58 Runway Magnetic Bearing (RWY BRG) field defines the inbound course to the holding waypoint.
Definition/Description: The magnetic bearing of the Source/Content: Inbound holding courses derived from
runway identified in the “runway identifier” field of the official government sources are entered into the field in
record is specified in the “Runway Magnetic Bearing” degrees and tenths of a degree, with the decimal point
field. suppressed. For holding courses charted with true bearings,
the last character of this field contains a “T” in place of
Source/Content: Runway magnetic bearings derived from tenths of a degree.
official government sources are entered into the field in
degrees and tenths of a degree, with the decimal point Used On: Holding Pattern records
suppressed. For runway bearings charted with true Length: 4 characters
bearings, the last character of this field will contain a “T” in Character Type: Alpha/numeric
place of tenths of a degree. Examples: 0456, 1800, 3034, 347T

Used On: Runway records 5.63 Turn (TURN)

Length: 4 characters
Character Type: Alpha/numeric Definition/Description: The “Turn” field specifies the
Examples: 1800, 2302, 0605, 347T direction in which holding pattern turns are to be made.

5.59 Runway Description (RUNWAY DESCRIPTION) Source/Content: The “Turn” field will always contain
either L or R.
Definition/Description: If required, additional information
concerning a runway can be included in a record in the Used On: Holding Pattern records
“Runway Description” field. Length: 1 character
Character Type: Alpha
Source/Content: Appropriate contents for the field will be
determined when the record is assembled. 5.64 Leg Length (LEG LENGTH)
Definition/Description: The “Leg Length” field specifies
Used On: Runway records the distance between the point at which the aircraft rolls out
Length: 22 characters max on the inbound leg of the holding pattern and the fix at
Character Type: Alpha/numeric which the holding pattern is defined (Figure 5-10).
Examples: GROOVED, SINGLE ENG. ONLY
Source/Content: Leg length derived from official
5.60 Name (NAME) government sources is entered into the field in nautical
miles and tenths of a nautical mile, with the decimal point
Definition/Description: The “Name” field defines the suppressed.
name commonly applied to the navigation entity defined
in the record. Used On: Holding Pattern records
Length: 3 characters
Source/Content: Appropriate contents for the field will Character Type: Numeric
be determined from official government or customer Examples: 108, 055
sources.
5.65 Leg Time (LEG TIME)
Used On: Gate and Holding Pattern records
Length: 25 characters max Definition/Description: The “Leg Time” field specifies the
Character Type: Alpha/numeric length of the inbound leg of a holding pattern in units of
Examples: HOLDING JIMEE MIAMI time (Figure 5-10).
5.61 Notes (Continuation Records) (NOTES) Source/Content: Leg time, derived from official
government sources, is entered into this field in minutes
Definition/Description: The “Notes” field (continuation and tenths of a minute, with the decimal point suppressed.
record) is provided to accommodate any information that
cannot be entered in the primary record. Used On: Holding Pattern records
Length: 2 characters
Source/Content: Appropriate contents for the field will be Character Type: Numeric
determined at the time the primary record is assembled. Examples: 10, 15, 20
ARINC SPECIFICATION 424 – Page 82
5.0 NAVIGATION DATA – FIELD DEFINITIONS

5.66 Station Declination (STN DEC)

COMMENTARY
Definition/Description: For VHF NAVAIDS, the “Station
Declination” field contains the angular difference between Based on the information contained in the
true north and the zero degree radial of the NAVAID at the
time the NAVAID was last site checked. For ILS Source/Content paragraph, it should be noted that the
single TCH value provided on the Runway Record
localizers, the field contains the angular difference between may be different than the TCH value provided on the
true north and magnetic north at the localizer antenna site
at the time the magnetic bearing of the localizer course was Approach Continuation Record for a procedure to
that same runway. These differences may be
established. significant. A comparison of procedure altitude data
Source/Content: Station declinations are derived from to threshold elevation and threshold crossing heights
should only be made to the Approach Continuation
official government sources. The field contains one of the Record. It should also be noted that a TCH associated
alpha characters shown in the following table followed by
the value of the declination in degrees and tenths of a with the VGSI for the same runway may be different
than either value. Some government sources will
degree, with the decimal point suppressed. When the first provide information on these procedure to VGSI
column of the Station Declination field is coded T or G, the
remainder of the field should be coded all zeros. differences when they are three feet or greater
Used On: Airport and Heliport ILS and MLS
Column 1 Runway, Airport, and Heliport
Declination Description
Character Approach Continuation Records.
Length: 2 characters on Airport and Heliport
E Declination is East of True North ILS, MLS and Runway Records
W Declination is West of True North 3 characters on Airport and Heliport
Station is oriented to True North in an Approach Continuation Records
T area in which the local variation is not Character Type: Numeric
zero. Example 37, 50, 99 (ILS, MLS and Runway
G Station is oriented to Grid North 044, 055, 102, (Approach)

Used On: VHF NAVAID and ILS records 5.68 Landing Threshold Elevation (LANDING THRES
Length: 5 characters ELEV)
Character Type: Alpha/numeric
Examples: E0072, E0000, T0000, G0000 Definition/Description: The elevation of the landing
threshold of the runway described in a runway record is
COMMENTARY defined in the “Landing Threshold Elevation” field.

The appearance of the character “G” in column 1 of this Source/Content: Runway landing threshold elevations
field will alert users that although a NAVAID derived from official government sources are entered into
declination may not be zero, the fact that the grid this field in feet, to a resolution of 1 foot. For elevations
reference is unknown prevents a value from being above MSL, the field contains the numeric characters of the
defined. elevation only. For below MSL elevations, the first
character of the field is a minus (-) sign.
5.67 Threshold Crossing Height (TCH)
Used On: Runway records
Definition/Description: The “Threshold Crossing Height” Length: 5 characters
specifies the height above the landing threshold on a Character Type: Alpha/numeric
normal glide path. Examples: 01250, -0150

Source/Content: The Threshold Crossing Height will be

derived from official government sources when available.
As provided on Runway Records, the TCH value will be
the Glide Slope Height at the landing threshold for
runways with ILS or MLS approaches. If an ILS or MLS
is not available and an RNAV approach is available it will
be the published TCH for that procedure. When ILS/MLS
or RNAV values are not available but a published VGSI
with TCH is available, it will be used. If none of these
values are available, it will be 50 feet. When used on
Approach Continuation Records, the field will contain the
published TCH for that procedure. When used on ILS or
MLS Records, it will be the height of the glide slope at
the landing threshold.
 ARINC SPECIFICATION 424 – Page 83
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Figure 5-9
ARINC SPECIFICATION 424 – Page 84
5.0 NAVIGATION DATA – FIELD DEFINITIONS

Figure 5-10

HOLDING PATTERN LEG LENGTH

*Leg time diagram added by Supplement 1

 ARINC SPECIFICATION 424 - Page 85

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.69 Threshold Displacement Distance (DSPLCD THR) a terminal procedure or for an airport or heliport
terminal environment.
Definition/Description: The distance from the extremity of a
runway to a threshold not located at that extremity of that Source/Content: The speed limit will be derived from
runway. official government source documentation and shown
in Knots. When used on an Airport or Heliport Record,
Source/Content: Threshold displacement distances derived the field is an indication of the maximum allowed speed
from official government sources are entered into this field in and applies to all flight segments departing or arriving
feet. that airport’s or heliport’s terminal area, at and below
the specified Speed Limit Altitude (5.73). When used
Used On: Runway records on Airport and Heliport SID/STAR/Approach Records,
Length: 4 characters the field is an indication of a speed for a fix in the
Character Type: Numeric procedure description, used in conjunction with Speed
Examples: 0485, 1260 Limit Description (5.261).
5.70 Vertical Angle (VERT ANGLE) On SID Procedure Records, the speed limit will apply
to all legs up to and including the termination of the leg
Definition/Description: The “Vertical Angle” field defines the on which the speed is coded from the beginning of the
vertical navigation path prescribed for the procedure. The procedure or a previous speed limit. If a different speed
vertical angle should cause the aircraft to fly at the last coded is coded on a subsequent leg, the limit will be applied
altitude and then descend on the angle, projected back from the for that leg and from that leg backwards to the previous
fix and altitude code for that fix at which the angle is coded. terminator which contained a speed limit.
Vertical Angle information is provided only for descending
vertical navigation. The angle is preceded by a “–” (minus On STAR and Approach Procedure Records, the speed
sign) to indicate the descending flight. limit will be applied forward to the end of the arrival
(e.g. throughout the procedure until the end of the
Source/Content: Values from official government sources Flight Plan) or until superceded by another speed limit.
will be used when available. In coding of procedures with
navaids providing an electronic glide slope, the Vertical The intent in both SIDs and STARs is to exclude speed
Angle is the angle assigned to that glide slope. In coding of changes inconsistent with the procedure
procedures with a published VNAV Angle, it is that angle or
one calculated by the data supplier. In coding of procedures Used On: Airport and Heliport SID/STAR/
with no government source vertical angle data, it is always a Approach, Airport and Heliport,
data supplier calculated value; see Attachment Five, Flight Planning Arr/Dep Data
Procedure Coding Rules. The angles are expressed in Records
degrees, tenths and hundredths of a degree, with the decimal Length: 3 characters
point suppressed. The Localizer Only Vertical Angle is a Character Type: Numeric
value provided for non-precision use of an ILS procedure as Examples: 250
a Localizer Only (Glide Slope Out) procedure.
5.73 Speed Limit Altitude
Used On: Airport and Heliport STAR/Approach
Records Definition/Description: “Speed Limit Altitude” is the
Length: 4 characters altitude below which speed limits may be imposed.
Character Type: Alpha/numeric
Examples: -300, -375, -542, -969 (max angle is 9.99 Source/Content: The “Speed Limit Altitude” will be
degrees) derived from official government sources in feet MSL or
FL’s.
5.71 Name Field
Used On: Airport and Heliport records
Definition/Description: This field will be used to further define Length: 5 characters
the record by name. Character Type: Alpha/numeric
Examples: 10000, F125
Source/Content: Facility name will be derived from official
government sources. A parenthetical name following the 5.74 Component Elevation (GS ELEV, EL ELEV, AZ
official name may be used to identify the location of the ELEV, BAZ ELEV)
facility.
Definition/Description: The “Component Elevation”
Used On: Navaid, Airport, Heliport and Enroute field defines the elevation of a given component in the
Marker records Localizer, GLS and MLS records. The “Glide Slope
Length: 30 characters Elevation (GS ELEV)” defines the elevation of the Glide
Character Type: Alpha Slope component in the Localizer Records. The “EL
Elevation (EL ELEV)” defines the elevation of the
5.72 Speed Limit (SPEED LIMIT) Elevation component of the MLS Record, the “Azimuth
Elevation (AZ ELEV)” defines the elevation of the
Definition/Description: The “Speed Limit” field defines a Azimuth component of the MLS Record and the “Back
speed, expressed in Knots, Indicated (K.I.A.S.), for a fix in Azimuth Elevation (BAZ ELEV)” defines the elevation
of the Back Azimuth component of the MLS Record.
ARINC SPECIFICATION 424 - Page 86

5.0 NAVIGATION DATA - FIELD DEFINITIONS

The “GLS station elevation (GLS ELEV)” defines the Company Route Record (R)
elevation of the GLS ground station in the GLS record.
VIA Field Description
Source/Content: Elevations specified in official government ALT Alternate Airport
publications are entered in this field with respect to MSL. APP Approach Route
When the elevation is below MSL, the first column of the field AWY Designated Airway
contains a minus (-) sign. DIR Direct to Fix
INT Initial Fix
Used On: Localizer, MLS and GLS Records and MLS PRE Preferred Route
Continuation Records SID Standard Instrument Departure
Length: 5 characters SDE Standard Instrument Departure - Enroute
Character Type: Alpha/numeric Transition
Examples: 00235, 01265, -0011 SDY Standard Instrument Departure - Runway
Transition
5.75 From/To - Airport/Fix STR Standard Terminal Arrival and Profile Descent
STE Standard Terminal Arrival and Profile Descent
Definition/Description: When used on Company Routes, the - Enroute Transition
“From Airport/Fix” is the waypoint from which the company STY Standard Terminal Arrival and Profile Descent
route originates. The “To Airport/Fix” is the waypoint at - Runway Transition
which the company route terminates. When used on
Alternate Records, it is the Departure, Destination or Preferred Route Record (ET)
Enroute Airport/Fix for which the alternate information is
being provided.
VIA Field Description
Source/Content: The customer is responsible for defining AWY Designated Airway
points at which company routes originate and terminate and DIR Direct to Fix
for defining which departure, destination or enroute points INT Initial Fix
are to have alternate information. RVF Route via Fix
RNF Route via Fix not permitted
Used On: Company Route and Alternate Records SID Standard Instrument Departure
Length: 5 characters max. STR Standard Terminal Arrival and Profile Descent
Character Type: Alpha/numeric
Used On: Company Route and Preferred Route
5.76 Company Route Ident records
Length: 3 characters
Definition/Description: The “Company Route Ident” field Character Type: Alpha/numeric
identifies each unique route between origination and
destination. Note: Figure 5-11 illustrates how various fields are to
be completed in the Company Route Record
Source/Content: This field is determined by the customer. based on the various “VIA Codes” defined in
this paragraph.
Used On: Company Route records
Length: 10 characters
Character Type: Alpha/numeric
5.77 VIA Code

Definition/Description: The “VIA Code” field is used to

define the type of route used in the
SID/STAR/Approach/Airways field (Section 5.78) on
Company Route records and defines the type of route used in
the AWY Identifier on Preferred Route records. On the
Preferred Route records, some codes define the use, or
restriction to use, of a fix or routing.

Source/Content: The code to be entered must be selected

from the table below:
 ARINC SPECIFICATION 424 - Page 87

5.0 NAVIGATION DATA - FIELD DEFINITIONS

S/S/A RWY ENRT CRUISE TERM/ ALT

VIA AIRWAY AREA TO FIX TRANS TRANS ALT ALT DIST
ARPT
ALT or Arpt or Dist in
ALT Blank Area Blank Blank Blank Blank Heliport NM
Ident
Arpt or
Tml Rte Heliport
APP Apch Ident Area Optional Blank Ident or Blank Ident if TO Blank
Blank FIX
Ident is
Terminal
AWY Awy Ident Area Fix Ident Blank Blank ALT or Blank Blank
Blank
Airport or
Heliport
DIR, Blank Area Fix Ident Blank Blank ALT or Ident if Blank
INT Blank TO FIX
Ident is
Terminal
Rwy Trans Airport or
Ident/ Ident ALT or Heliport if
SID SID Ident Area Fix Ident All or or Blank TO FIX Blank
Blank Blank Ident is
Terminal
Airport or
Heliport
SDE SID Ident Area Fix Ident Blank Trans ALT or Ident if Blank
Ident Blank TO FIX
Ident is
Terminal
Airport or
Heliport
SDY SID Ident Area Fix Ident Rwy Blank ALT or Ident if Blank
Ident Blank TO FIX
Ident is
Terminal
Airport or
Trans Heliport
STR STAR Ident Area Fix Ident Rwy Ident or ALT or Ident if Blank
of Blank Ident/All Blank Blank TO FIX
Ident is
Terminal
Airport or
Heliport
STE STAR Ident Area Fix Ident Blank Trans ALT or Ident if Blank
Ident Blank TO FIX
Ident is
Terminal
Airport or
Heliport
STY STAR Ident Area Fix Ident Rwy Blank ALT or Ident if Blank
Ident Blank TO FIX
Ident is
Terminal
Airport or
Heliport
PRE Pref Rte Area Fix Ident Blank Blank ALT or Ident if Blank
Ident Blank TO FIX
Ident is
Terminal

Figure 5-11
Company Route Record (R)
Field Content
ARINC SPECIFICATION 424 - Page 88

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.78 SID/STAR/App/AWY (S/S/A/AWY)

SID/STAR/Awy (S/S/AWY) Category/
Definition
Classification
Definition/Description: This field is used to identify the ILS Localizer Only, No Glideslope 0
particular route to be flown as referenced by the “VIA” field ILS Localizer/MLS/GLS Category I 1
(Section 5.77). ILS Localizer/MLS/GLS Category II 2
ILS Localizer/MLS/GLS Category III 3
Source/Content: For Company Route records this field can IGS Facility I
contain the SID/STAR, Approach, Enroute Airway, or LDA Facility with Glideslope L
Preferred Route Identifier (Sections 5.8, 5.9, and 5.10). For LDA Facility, no Glideslope A
Preferred Route records this field can contain the SID/STAR SDF Facility with Glideslope S
or Enroute Airway Route Identifier (Section 5.8). This field SDF Facility, no Glideslope F
will be blank for certain records depending on the “VIA” field
content (Section 5.77). Used On: Runway, Localizer, MLS and MLS
Continuation Records, GLS Record.
Used On: Company Route and Preferred Route Length: 1 character
Records Character Type: Alpha/numeric
Length: 6 characters
Character Type: Alpha/numeric 5.81 ATC Indicator (ATC)
Examples: VIA S/S/A/AWY
SIDCUIT8 Definition/Description: The “ATC Indicator” field will
STRLOCKE9 be used to indicate that the altitudes shown in the altitude
APPI19L fields can be modified by ATC or the altitude will be
AWYJ501 assigned by ATC.
5.79 Stopway Source/Content: This field will contain the alpha
character “A” when the official government source states
Definition/Description: “Stopway” means the length of an area that the altitude can be modified or assigned by ATC.
beyond the take-off runway, no less wide than the runway and This field will contain the alpha character “S” when the
centered upon the extended centerline of the runway, and official government source states that the altitude will be
designated for use in decelerating the airplane during an assigned by ATC or if no altitude is supplied.
aborted takeoff.
Used On: Airport and Heliport SID/STAR/
Source/Content: The Stopway will be derived from official Approach Records
government sources and shown in feet (See Figure 5-3). Length: 1 character
Character Type: Alpha
Used On: Runway records
Length: 4 characters 5.82 Waypoint Usage
Character Type: Numeric
Examples: 0900, 1000 Definition/Description: The waypoint usage field is
employed to indicate the structure in which the
5.80 ILS/MLS/GLS Category (CAT) waypoint is utilized.
Definition/Description: The Localizer/MLS/GLS Source/Content:
Performance Categories have established operating
minimums and are listed as Category I, II, and III. The level Record Column
of Performance Category does not imply that permission Usage
exists to use the facility for landing guidance to that level Content
and does not limit minimal using designated classification. 30 31
This field is also used to define the classification, non- HI and LO Altitude B
ILS/MLS/GLS, and localizer installation such as IGS, LDA, HI Altitude H
or SDF. As used in the runway record, there are two fields, LO Altitude L
one labeled Localizer/MLS/GLS Category/Classification and
the other labeled Second Localizer/MLS/GLS Terminal Use Only Blank
Category/Classification. RNAV R

Source/Content: The Localizer/MLS/GLS Used On: Enroute (EA) waypoint records

Category/Classification will be derived from official Length: 2 characters
government sources and will be indicated by a value from Character Type: Alpha
the table below.
 ARINC SPECIFICATION 424 - Page 89

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.83 To FIX This field uniquely identifies the desired SID/STAR

enroute transition. If no enroute transition is desired, the
Definition/Description: The Company Route and Preferred field is blank.
Route “To Fix” field is used to terminate the route referenced
in the SID/STAR/APCH/AWY field (Section 5.78), or VIA field contains “SDE” or “STE”:
terminate a “Direct” segment or start an “Initial” segment
when no SID/STAR/APCH/AWY is referenced. In this situation the field contents are defined exactly as
stated above (VIA field - “SID” or “STR”) except that
Source/Content: For Company Route records the field will the field is always non-blank.
contain Enroute Waypoint, Terminal Waypoint, VHF
NAVAID, NDB NAVAID, Terminal NDB NAVAID, Airport VIA field contain “APP”:
or Runway Identifier. The customer will define where a
particular route segment is to terminate. For Preferred Route This field uniquely identifies the desired approach
records, the field will contain Enroute Waypoint, Terminal transition. If no approach transition is desired, the field is
Waypoint, VHF NAVAID, NDB NAVAID or Terminal NDB blank.
NAVID, Airport Identifier.
The field is blank for all other contents of the VIA field.
Used On: Company Route and Preferred Route
Records Used On: Company Route Records
Length: Company Route - 6 characters max. Length: 5 characters
Preferred Route - 5 characters max. Character Type: Alpha/numeric
Character Type: Alpha/numeric Examples: ETS, KEENE, DEN
Examples: SHARP, BHM, DEN43, KDEN,
RW35R 5.86 Cruise Altitude

5.84 RUNWAY TRANS Definition/Description: This field will be used to

establish an Enroute Cruise Altitude. It will be entered on
Definition/Description: This field is used to identify the Company Route records as specified by the customer.
desired runway transition of the applicable SID or STAR. It is
used to link directly to the SID/STAR procedure records Source/Content: The customer will supply the Cruise
depending on the Company Route record “VIA” field (Section Attitude in feet or flight level.
5.77) and whether or not the SID/STAR has explicit runway
transitions. Used On: Company Route Records
Length: 5 characters
Source/Content: If the applicable SID/STAR has explicit Character Type: Alpha/numeric
runway transitions then this field uniquely identifies the Examples: 10000, 15000, FL090, FL240
desired runway transition. If no runway transition is desired,
the field is blank. If the applicable SID/STAR does not have 5.87 Terminal/Alternate Airport (TERM/ALT ARPT)
explicit runway transitions this field is always non-blank and
exactly matches the “TRANS IDENT” field of the SID/STAR Definition/Description: This field has two uses
procedure records. depending on the “VIA” field and File Code for “To
Fix.” For “VIA” field content of “ALT” this field will
VIA field contains “SDY” or “STY”: contain the Alternate Airport Ident for this Company
Route. If the file code for “To Fix” contains “P,” this
In this situation the field contents are defined exactly as stated field will contain the Airport Ident for REGN CODE
above (VIA field = “SID” or “STR”) except that the field is (Section 5.41) of Terminal Waypoints (PC records) and
always non-blank. This field is blank for all other contents of Runway (PG records).
the VIA field.
Source/Content: See Section 5.6, Airport ICAO
VIA field contains “SID” or “STR”: Identifier.
Used On: Company Route Records Used On: Route Records
Length: 5 characters Length: 4 characters
Character Type: Alpha/numeric Character Type: Alpha/numeric
Examples: RW08L, ALL, Blank Examples: KDEN, EDDF

5.85 ENRT TRANS 5.88 Alternate Distance (ALT DIST)

Definition/Description: This field is used to identify the Definition/Description: This field is used to supply the
desired enroute transition of the applicable SID or STAR. It distance in nautical miles from the “To Airport/Fix” to
can also be used to identify the desired approach transition of the “ALT ARPT”.
an approach.
Source/Content: Values for this field will be supplied by
Source/Content: the customer and must be equal to or greater than the
great circle distance from the destination airport/fix to the
VIA field contains “SID” or STR”: alternate airport.
ARINC SPECIFICATION 424 - Page 90

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Company Route Records 5.92 Facility Elevation (FAC ELEV)
Length: 4 characters
Character Type: Numeric Definition/Description: This “Elevation” field defines the
Examples: 052, 0011, 0123 elevation of the VOR, NDB, ILS Marker, Airways
Marker and Airport Communications stations.
5.89 Cost Index
Source/Content: Facility elevations specified in official
Definition/Description: The Cost Index field is used to define government publications are entered into this field in feet
the relative value of fuel-related costs and time-related costs with respect to MSL. When the elevation is below MSL,
for a particular route. the first column of the field contains a minus (-) sign.

Source/Content: Source will be by customer airline. Used On: ILS Marker, Airways Marker,
Enroute/Airport Communications
Used On: Company Route Records primary records. VHF Navaids and
Length: 3 characters NDB Navaids continuation records.
Character Type: Numeric Length: 5 characters
Examples: 001, 011, 999 Character Type: Alpha/numeric
Examples: 00530, -0014
5.90 ILS/DME Bias
5.93 Facility Characteristics (FAC CHAR)
Definition/Description: This field is used to specify the DME
offset. Definition/Description: The “Facility Characteristics”
field identifies the characteristics of the NAVAID
Source/Content: The field contains a 2-digit bias term in facility.
nautical miles and tenths of a nautical mile with the decimal
point suppressed. Field is blank for unbiased DME’s.
Used On: VHF NAVAID Records containing
ILS/DME or MLS/DME Facilities
Length: 2 characters
Character Type: Numeric
Examples: 13, 91
5.91 Continuation Record Application Type (APPL)
Definition/Description: This field indicates specific application
of this continuation record.

Source/Content: The field will contain one of the following

type codes:

Field
Description
Content
A standard ARINC Continuation containing Notes
A
or other formatted data
C A Call Sign/Controlling Agency Continuation
E Primary Record Extension
L VHF Navaid Limitation Continuation
N A Sector Narrative Continuation
A Time of Operations Continuation with
T
“formatted time data”
A Time of Operations Continuation with
U
“narrative data”
A Time of Operations Continuation with
V
“narrative data”
A Flight Planning Application Continuation
P
Record
A Flight Planning Application Primary Data
Q
Continuation
S A Simulation Application Continuation Record

Used On: Continuation Records

Length: 1 character
Character Type: Alpha
 ARINC SPECIFICATION 424 - Page 91

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: Used On: ILS Marker Primary records, VHF

Navaid, NDB
Facility 28 29 30 31 32 Navaid and ILS/MLS continuation
records
VHF NAVAID, ILS & Length: 5 characters
MLS Character Type: Alpha/numeric
Synchronous S
Asynchronous A Note 1: 0=A0, 1=A1, 2=A2
Unknown U
Note 2: Enter number of occurrences per minute if
VHF NAVAID, NDB known. Leave blank if not known.
NAVAID and Locator
Note 3: Colocated means that the latitudes and
Voice Ident Y longitudes of the two facilities differ by no
No Voice Ident N more than 1 arc second.
Undefined U
NDB NAVAID Note 4: Where a high-rate approach azimuth
guidance is available, enter “H,” otherwise
Type of emission Note leave blank.
1
400H 4 COMMENTARY
1020H 1
Repetition Rate Note The NDB emission designators set forth in Note 1
2 above are being replaced with the new designators
shown in the equivalency table below as the result of
ILS DME Location action taken at the 1979 ITU World Administrative
Collocated with Localizer L Radio Conference.
Note 3
Collocated with Glide G Present New
Slope Designator Designator Description
Not cllocated with Blank
Localizer or Glide Slope
A0 NON Unmodulated Carrier
ILS Back Course A1 A1A Carrier keyed, bandwidth less
than 0.1 kHz
Usable Y A1 A1B Carrier keyed, bandwidth
Unusable N greater than 0.1 kHz
Restricted R A2 A2A Tone keyed modulation
Undefined U
MLS, DME or DME/P
Location 5.94 True Bearing (TRUE BRG)
Collocated with Azimuth A Definition/Description: The “Magnetic Bearing” for ILS
Collocated with Elevation E localizer, MLS Azimuth, MLS Back Azimuth and
Not Collocated with N Runway records is given in the primary record. This field
Azimuth or Elevation allows the true bearing to be entered independently of the
magnetic variation.
MLS Approach Azimuth Note
Scan Rate 4 Source/Content: True Bearings are entered into the field
in degrees, tenths of a degree and hundredths of a degree,
with the decimal point suppressed. See Section 5.95 for
source description.

Used On: ILS Continuation, MLS Continuation

and Runway Continuation records
Length: 5 characters
Character Type: Numeric
Examples: 19000, 23021, 06050
5.95 Government Source (SOURCE)
Definition/Description: The content of the source field
indicates whether the “True Bearing” is derived from
official government sources or from other sources.
ARINC SPECIFICATION 424 - Page 92

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: The field contains “Y” when the “True 5.99 Marker Type (MKR TYPE)
Bearing” is derived from official government sources and “N”
when it is derived from other sources. Definition/Description: The “Marker Type” field defines
the type of marker.
Used On: ILS, MLS, MLS continuation and
runway continuation records Source/Content: The field contains the following
Length: 1 character information.
Character Type: Alpha
Record Column Content
5.96 Glide Slope Beam Width (GS BEAM WIDTH) Type of Facility
18 19 20
Definition/Description: The “Glide Slope Beam Width” field Inner Marker I M
specifies the glide path beam width of the Glide Slope defined Middle Marker M M
in the record. Outer Marker O M
Back Marker B M
Source/Content: Glide Slope beam widths from official Locator at Marker L
government sources are entered into this field in degrees,
tenths of a degree and hundredths of a degree with the decimal Used On: Airport Localizer Marker records
point suppressed. Length: 3 characters
Character Type: Alpha
Used On: ILS continuation records
Length: 3 characters 5.100 Minor Axis Bearing (MINOR AXIS TRUE
Character Type: Numeric BRG)
Examples: 140, 180, 200
Definition/Description: The “Minor Axis Bearing” field
5.97 Touchdown Zone Elevation (TDZE) indicates the true bearing of the minor axis of marker
beacons.
Definition/Description: The “Touchdown Zone Elevation” is
the highest elevation in the first 3,000 feet of the landing Source/Content: This field will contain the true bearing
surface beginning at the threshold. in degrees and tenths of a degree, with the decimal point
suppressed.
Source/Content: Touchdown zone elevations from official
government sources will be used when available. If official Used On: Airport Localizer Marker records
source is not available, the runway threshold elevation will be Length: 4 characters
entered. If the runway threshold elevation is not available, the Character Type: Numeric
Airport reference point elevation will be entered. (See TDZE Examples: 0900, 2715
Location, Section 5.98) The elevation will be entered in feet,
to a resolution of 1 foot, with respect to MSL. For below MSL 5.101 Communications Type (COMM TYPE)
elevations, the first character of the field is a minus (-) sign.
Definition/Description: The “Communications Type”
Used On: Runway continuation records field specifies the type of communication unit
Length: 5 characters contained in the record.
Character Type: Alpha/numeric
Examples: 02171, 05230, -0142 Source/Content: The field will contain one of the
following entries:
5.98 TDZE Location (LOCATION)

Definition/Description: The content of the “TDZE Location”

field indicates whether the TDZ elevation was obtained from
official government sources or from other sources.
Source/Content: The field will contain a “T” for official source
or a “L” if the landing threshold elevation is used, or an “A” if
the airport elevation is used.

Used On: Runway continuation records

Length: 1 character
Character Type: Alpha
 ARINC SPECIFICATION 424 - Page 93

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Note 1: The Comm Type PAL is used only when the

Airport frequency(s) published are used exclusively
Enroute Both for the activation of airport lighting. If the
Field Heliport
Description Comm Comm pilot activation of airport lighting is
Content Comm
Only Type accomplished on a frequency that is also used
Only
ACC Area Control Center X for voice communications, the Pilot
ACP Airlift Command Post X Controlled Lighting parameter of the Service
AIR Air to Air X
Indicator is used.
APP Approach Control X
ARR Arrival Control X Used On: Enroute, Airport and Heliport
Communications
Automatic Surface
ASO X Length: 3 characters
Observing System (ASOS)
Character Type: Alpha
Automatic Terminal Info
ATI X
Service (ATIS) 5.102 Radar (RADAR)
Airport Weather
AWI Information Broadcast X Definition/Description: The “Radar” field indicates
(AWIB) whether or not the communications unit has access to
Automatic Weather information derived from primary or secondary radar and
AWO Observing Service X can use that information in fulfilling their assigned tasks.
(AWOS)
Aerodrome Weather Source/Content: The availability or radar capability will
AWS Information Services X be drived from official government source
(AWIS) documentation. If the communications unit has radar
CLD Clearance Delivery X capabilities, the field will contain the character “R”. If no
CPT Clearance, Pre-Taxi X capability exists, the field will contain the character “N”.
CTA Control Area (Terminal) X
CTL Control X Used On: Enroute, Airport and Heliport
DEP Departure Control X Communications records
Director (Approach Length: 1 character
DIR X Character Type: Alpha
Control Radar)
Enroute Flight Advisory
EFS X 5.103 Communications Frequency (COMM FREQ)
Service (EFAS)
EMR Emergency X
FSS Flight Service Station X Definition/Description: The “Communications
GCO Ground Comm Outlet X
Frequency” field specifies a frequency for the facility
identified in the “Communications Type” (5.101) field.
GND Ground Control X
GTE Gate Control X Source/Content: Content is derived from official
HEL Helicopter Frequency X government sources. The following details apply:
INF Information X
MIL Military Frequency X HF frequencies are provided as five significant
MUL Multicom X digits in kilohertz for 10 thousands, thousands,
OPS Operations X hundreds, tens and units. The remaining two
Pilot Activated Lighting positions of the seven-character field is zero filled.
PAL X
(Note 1)
RDO Radio X Example: The HF frequency of 17955 kHz
RDR Radar X would be expressed as 1795500. The HF
Remote Flight Service frequency of 8965 kHz would be expressed as
RFS X 0896500.
Station (RFSS)
RMP Ramp/Taxi Control X
Airport Radar Service Area VHF frequencies with 100, 50 or 25 kilohertz
RSA X spacing are provided as three significant digits and
(ARSA)
three decimals in megahertz for hundreds, tens,
Terminal Control Area
TCA X units, tenths, hundredths and thousandths. The
(TCA)
remainder of the seven-character field is zero
Terminal Control Area filled.
TMA X
(TMA)
TML Terminal X Example: The VHF frequency of 118.50
Terminal Radar Service MHz would be expressed as 0118500. The
TRS X
Area (TRSA) VHF frequency of 131.275 MHz would be
Transcriber Weather expressed as 0131275.
TWE X
Broadcast (TWEB)
TWR Tower, Air Traffic Control X UHF frequencies are provided as three significant
UAC Upper Area Control X digits and two decimals in megahertz for hundreds,
UNI Unicom X tens, units, tenths and hundredths. The remainder
VOL Volmet X of the seven-character field is zero filled.
ARINC SPECIFICATION 424 - Page 94

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Airport, Enroute Communications

Example: the UHF frequency of 267 MHz would records
be expressed as 0026700. The UHF frequency of Length: 25 characters
287.5 MHz would be expressed as 0028750. Character Type: Alpha/numeric
Examples: COMM TYPE CALL NAME
VHF frequencies with 8.33 kHz spacing are provided as APP LION (“APPROACH” is
four significant digits and three decimals for the omitted)
assigned channel number. The actual frequency (which TWR LION (“TOWER” is omitted)
would be three significant digits and four decimal DEP LONDON APPROACH
places) is not provided. ACC DENVER CENTER

Example: The VHF frequency of 132.0583 MHz 5.106 Service Indicator (SERV IND)
will be provided as the channel number 132.060,
expressed in seven digits as 0132060. Definition/Description: The “Service Indicator” field is
used to further define the use of the frequency for the
The decimal point is always suppressed. As all of these specified Communication Type (5.101).
numeric expressions look alike, the “Frequency Units” field
(Section 5.104) is provided to assist in actual frequency Source/Content: The field may contain the following
determination. information:

Used On: Enroute, Airport and Heliport AIRPORT COMMUNICATIONS RECORDS

Communications Records
Length: 7 characters Column Content
Character Type: Numeric Description
27 28 29
Airport Advisory Service (AAS) A
5.104 Frequency Units (FREQ UNIT) Community Aerodrome Radio Station C
(CARS)
Definition/Description: The “Frequency Units” field will Departure Service (Other than Departure D
designate the frequency spectrum area for the frequency in the Control Unit)
“Communications Frequency” (Section 5.103) field as Flight Information Service (FIS) F
indicated in the table or will designate the content of the Initial Contact (IC) I
“Communications Frequency” field as a channel. Arrival Service (Other than Arrival L
Control Unit)
Source/Content: This field contains the follow information. Pre-Departure Clearance (Data Link P
Service)
Field Description Aerodrome Flight Information Service S
Content (AFIS)
H High Frequency Terminal Area Control (Other than T
(3000 kHz - 30,000 kHz) dedicated Terminal Control Unit)
V Very High Frequency Aerodrome Traffic Frequency (ATF) A
(30,000 kHz - 200 MHz) Common Traffic Advisory Frequency C
U Ultra High Frequency (CTAF)
(200 MHz - 3000 MHz) Mandatory Frequency (MF) M
C Communication Channel for Air/Air R
8.33kHz spacing Secondary Frequency S
Air/Ground A
Used On: Enroute, Airport and Heliport VHF Direction Finding Service (VDF) D
Communications records Remote Communications Air to Ground G
Length: 1 character (RCAG)
Character Type: Alpha Language other than English L
Military Use Frequency M
5.105 Call Sign (CALL SIGN) Pilot Controlled Light (PCL) P
Remote Communications Outlet (RCO) R
Definition/Description: The “Call Sign” field specifies the
name of the facility being called.

Source/Content: Call Signs are derived from official

government sources. On airport Communications records, the
type of facility being called will be omitted when is it the same
as the communication type. On Enroute Communication
records, the Call Name will be shown with the first record only
of any Flight Information Region or Flight Service Station.
 ARINC SPECIFICATION 424 - Page 95

5.0 NAVIGATION DATA - FIELD DEFINITIONS

ENROUTE COMMUNICATIONS RECORDS Used On: Runway records

Length: 3 characters
Column Content Character Type: Numeric
Description Examples: 150, 300, 075
57 58 59
Aeronautical Enroute Information A
Service (AEIS) 5.110 Marker Ident (MARKER IDENT)
Flight Information Service (FIS) F
Air/Ground A Definition/Description: The “Marker Ident” field
Discrete Frequency D contains a unique computer ident assigned to each
Air/Air R enroute marker.
Mandatory Frequency M
Secondary Frequency S Source/Content: A unique identifier will be created for
VHF Direction Finding Service (VDF) D each enroute marker since such idents are not designated
Remote Communications Air to by official sources. Marker idents will be established
G using the 2-character ICAO code followed by two
Ground (RCAG)
Language other than English L numeric digits assigned to keep markers unique within a
Military Use Frequency M given ICAO region.
Remote Communications Outlet (RCO) R
Used On: Enroute marker records
Used On: Enroute, Airport and Helicopter Length: 4 characters
Communications records Character Type: Alpha/numeric
Length: 3 characters Examples: EG01, EG02, K101, K102
Character Type: Alpha
5.111 Marker Code (MARKER CODE)
5.107 ATA/IATA Designator (ATA/IATA)
Definition/Description: The “Marker Code” field
Definition/Description: The “ATA/IATA” field contains the contains the coded ident that provides an aural and visual
Airport/Heliport ATA/IATA designator code to which the data indication of station passage in the cockpit. The code
contained in the record relates. shall be keyed so as to transmit dots or dashes, or both, in
an appropriate sequence on a radio frequency of 75
Source/Content: The content of this field should be derived MHz. The frequency of the modulating tone is 3000 Hz.
from IATA Reservations Manual Part II, IATA Resolution
763/Location Identifiers. Source/Content: The field contains the morse code ident
(dots and dashes) derived from official government
Used On: Airport and Heliport records sources.
Length: 3 characters
Character Type: Alpha Used On: Enroute marker records
Examples: DEN, LHR, JFK Length: 4 characters
Character Type: Alpha
5.108 IFR Capability (IFR) Examples: -.-., . . . ., - - - -

Definition/Description: The “IFR Capability” field indicates if 5.112 Marker Shape (SHAPE)
the Airport/Heliport has any published Instrument Approach
Procedures. Definition/Description: The “Shape” field defines the
radiation pattern of an airways marker as being either
Source/Content: The field contains “Y” if there is an Official “bone” or “elliptical.”
Government Instrument Approach Procedure published,
otherwise the field will contain “N”. (Note: The presence of Source/Content: The field contains the shape of the
“Y” in this field does not necessarily imply that the published marker derived from official government sources when
instrument approach is coded in the data base.) available. The character “B” will designate the “bone”
shape and the character “E” will designate the elliptical
Used On: Airport and Heliport records shape. “E” will be entered when the source does not
Length: 1 character supply shape information.
Character Type: Alpha
Used On: Enroute airways marker records
5.109 Runway Width (WIDTH) Length: 1 character
Character Type: Alpha
Definition/Description: The width of the runway identified in
the “Runway Identifier” field is specified in the “Runway 5.113 High/Low (HIGH/LOW)
Width” field.
Definition/Description: The “High/Low” field indicates
Source/Content: Runway widths derived from Official the power of the enroute marker.
Government Sources are entered into the field in feet, with a
resolution of one foot. For runways of variable width, the Source/Content: The field contains the power derived
minimum width encountered over the runway length will be from official government sources. The character “L”
entered. indicates low power for use at low altitudes. The
character “H” indicates high power for general use.
ARINC SPECIFICATION 424 - Page 96

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Enroute marker records Used On: Holding Pattern Records
Length: 1 character Length: 2 characters
Character Type: Alpha Character Type: Numeric
Examples: 00, 10, 61, 32
5.114 Duplicate Indicator (DUP IND)
5.115 Directional Restriction
Definition/Description: The “Duplicate Identifier” field is
used to further define holding patterns when official Definition/Description: The “Direction Restriction”
government source has designated more than one Holding field, when used on Enroute Airway records, will
Pattern on a Navaid or Waypoint. indicate the direction an Enroute Airway is to be flown.
The “Direction Restriction” field, when used on
Source/Content: Holding Patterns are derived from official Preferred Route records, will indicate whether the
government sources documents. That documentation will routing is available only in the direction of “from initial
normally specify the airspace structure in which the holding is fix to terminus fix” or in both directions.
to be used. That documentation may also designate more than
one Holding Pattern for a single Navaid or Waypoint. This Source/Content: Direction Restrictions should be
field will contain details on airspace structure and multiple derived from official government sources. They will be
designations. More than one holding is designated on a single coded and supplied as follows:
“fix” when one or more of the following elements are different
for holdings within the same airspace structure.Inbound Enroute Airway Records
Holding Course, Turn Direction, Altitude, Leg Length or Leg
Time, and Holding Speed. F= One way in direction route is coded
(Forward).
If only one Holding Pattern is designated for a “fix” and the B= One way in opposite direction route is coded
airspace structure in which that holding is to be used is not (backward).
defined, the field will contain “00.” If only one Holding Blank = No restrictions on direction.
Pattern is designated for a “fix” and the airspace structure in Preferred Route Records
which that holding is to be used is defined or if the same
holding is designated for more than one airspace structure, the F= Uni-directional Preferred Route, usable only
first position of the “Duplicate Indicator” will contain a digit of from Initial Fix to Terminus Fix.
1 through 6 and the second position will contain a zero. If B= Bi-directional Preferred Route, usable from
more than one holding is designated for a single “fix” in one Initial Fix to Terminus Fix or from Terminus
type of airspace structure, the first position will contain a digit Fix to Initial Fix.
of 1 through 6 and the second position will contain a digit of 1
through 9, depending on the number of holdings on that “fix” Used On: Enroute Airway and Preferred Route
within that airspace structure. Records
Length: 1 character
If multiple holdings are designated in official source Character Type: Alpha
documents for a single “fix” and the airspace structure is not
defined for all holdings, those with “undefined airspace 5.116 FIR/UIR Identifier (FIR/UIR IDENT)
structure” will carry the digit 7 in position one and a digit of 0
through 9 in position two. Definition/Description: The “FIR/UIR Identifier” field
identifies the Flight Information Region and Upper
MULTIPLE HOLDING PATTERNS Information Region of airspace with defined dimensions
within which Flight Information Service and Alerting
Duplicate Indicator Service are provided. The Identifier is for the controlling
Holding Pattern Position One Position Two Area Control Center or Flight Information Center.
Airspace Multiple
Undefined (None Defined) 0 See Note 1 Source/Content: FIR/UIR Identifiers will be derived
High Altitude 1 See Note 1 from official government sources. This field contains the
Low Altitude 2 See Note 1 four character identifier assigned to the airspace. For
SID 3 See Note 1 those areas charted as “NO FIR,” the identifier field will
STAR 4 See Note 1 contain “XX plus a two digit numeric.”
Approach 5 See Note 1
Missed Approach 6 See Note 1 When used on Flight Planning Continuation records, the
Undefined (with other entry will be related to the altitude structure. For records
7 See Note 1 that are classed or designated as high altitude, the FIR
defined)
All Altitude 8 See Note 1 field will be blank. For areas assigned a FIR identifier
only that is valid for both the low altitude and the high
Note 1: If there is only one holding pattern on a given fix altitude structure, the UIR field will be blank. For detail
within an airspace structure, position 2 will contain records classed or designated as low altitude and high
a “0.” For additional (multiple) holdings on that altitude, both the FIR and the UIR identifier will be
same fix within the same airspace structure, position entered.
2 will be incremented by 1, e.g. “0” for the first “1”
for the second, etc.
 ARINC SPECIFICATION 424 - Page 97

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: FIR/UIR, VHF NAVAID, NDB 4. Other than for lines of latitude and longitude, the
NAVAID, Enroute, Terminal Waypoint, Boundary VIA of “H” shall only be used when
Airport Flight Planning Continuation and specifically stated in the official government source.
Heliport records If not stated as “Rhumb Line” or not along
Length: 4 characters latitude/longitude, all straight lines will be coded as
Character Type: Alpha “G”.
Examples: DAAG, SGAS, XX02
Note: Refer to Figure 5-12 for sample coding of
5.117 FIR/UIR Indicator (IND) Boundary VIA Codes.

Definition/Description: The “FIR/UIR Identifier” field may Used On: Controlled Airspace, FIR/UIR, and
contain the identifier of a FIR, UIR or combined FIR/UIR. Restrictive Airspace records
This field indicates which one of these records is an element. Length: 2 characters
Character Type: Alpha
Source/Content:
5.119 Arc Distance (ARC DIST)
Type Field Entry
Definition/Description: The “Arc Distance” field is used
FIR F to define the distance in nautical miles from the “Arc
UIR U Origin” position to the arc defining the lateral boundary
Combined FIR/UIR B of a FIR/UIR or Restrictive Airspace.

Source/Content: ARC distances should be derived from

Used On: FIR/UIR and Enroute official government sources when available, in nautical
Communications records miles and tenths of nautical mile, with the decimal point
Length: 1 character suppressed. The field will be entered only when
Character Type: Alpha “Boundary Via” is “A,” “C,” “L,” or “R”.
5.118 Boundary Via (BDRY VIA) Used On: FIR/UIR, Restrictive Airspace, and
Controlled Airspace records
Definition/Description: The “Boundary VIA” defines the path Length: 4 characters
of the boundary from the position identified in the record to Character Type: Numeric
the next defined position. Examples: 0080, 0150, 1000
Source/Content: The path of the boundary will be determined 5.120 Arc Bearing (ARC BRG)
from official government sources or the rule listed below and
the “Boundary VIA” will be selected from the table below. Definition/Description: The “Arc Bearing” field contains
the true bearing from the “Arc Origin” position to the
Field Content Description beginning of the arc.
Position 1 Position 2
A Arc by edge Source/Content: Arc bearings should be derived from
C Circle official government sources when available. The field
G Great Circle contains true bearing in degrees and tenths of degree,
H Rhumb Line with the decimal point suppressed. The field will only be
L Counter Clockwise ARC entered when Boundary Via is “A,” “C,” “L” or “R”.
R Clockwise ARC
E End of description, return to Used On: FIR/UIR, Restrictive Airspace, and
origin point Controlled Airspace records
Length: 4 characters
Application Rules: Character Type: Numeric
Examples: 0900, 1800, 3450
1. Special Use Airspace designated as following rivers,
country, state or other political boundaries will be 5.121 Lower/Upper Limit
averaged in coding by using a series of straight lines so
that no path will be greater than two miles from the actual Definition/Description: Special Use Airspace is
boundary. The Boundary VIA will be “G”. described by both lateral and vertical boundaries. The
“Lower/Upper Limit” fields contain the lower and upper
2. If there is a named waypoint on an airway which crossed limits of the FIR/UIR or Restrictive Airspace being
an irregular FIR/UIR boundary, the waypoint described.
coordinates will be used to define a point in the path
defining that FIR/UIR boundary. The Boundary VIA Source/Content: Limits for the special use airspace
will appropriate to the path definition. should be derived from official government sources. The
field may contain altitude (all numerics), flight levels
3. Paths that follow lines of latitude will be coded with a (alpha/numerics) or an all alpha entry (see examples).
Boundary Via of “H”. Paths that follow lines of The flight level entry will contain the alpha characters
longitude may be coded with a Boundary Via of “G” or “FL” followed by the altitude in hundreds of feet. These
“H”. Consistent use of one or the other with a single fields will be entered on the first record only of each
airspace is desired. FIR/UIR or Restrictive Airspace being described.
ARINC SPECIFICATION 424 - Page 98

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: FIR/UIR, Restrictive Airspace, and Source/Content: FIR/UIR Entry Report should be
Controlled Airspace records derived from official government publications. “Y” in
Length: 5 characters this field indicates Entry Report is required, “N” in this
Character Type: Alpha/numeric field indicates no Entry Report is required. The field will
be entered on the first record only for each FIR/UIR
Examples: identifier.
All numeric: 05000, 25000
Alpha/numeric: FL245, FL450 Used On : FIR/UIR records
All alpha: NOTSP (for Not Specified) Length: 1 character
UNLTD (for unlimited) Character Type: Alpha
GND (for Ground)
MSL (for Mean Sea Level)
NOTAM (for Restrictive Airspace 5.125 FIR/UIR Name
only)
Definition/Description: The “FIR/UIR Name” field
5.122 FIR/UIR ATC Reporting Units Speed (RUS) contains the official name of the controlling agency of
the FIR/UIR of which this record is an element.
Definition/Description: The “FIR/UIR ATC Reporting Units
Speed” is used to indicate the units of measurement concerning Source/Content: The FIR/UIR name will be derived from
True Air Speed used in the specific FIR/UIR to fulfill the official publications. The areas without a specific
requirements of ICAO flight plan. “FIR/UIR” designation will be labeled “NO FIR”.

Source/Content: FIR/UIR Reporting Units should be derived Used On: FIR/UIR records
from official government publications. The field will be Length: 25 characters
entered on the first record only for each FIR/UIR identifier. Character Type: Alpha/numeric
Examples: ACCRA, FIR, ASUNCION FIR/UIR,
Reporting Units Field Entry NO FIR
Not specified 0
TAS in Knots 1 5.126 Restrictive Airspace Name
TAS in Mach 2
TAS in Kilometers/hr 3 Definition/Description: The “Restrictive Airspace Name”
field will contain the name of the restrictive airspace
when assigned.
Used On: FIR/UIR records
Length: 1 character Source/Content: Names will be derived from official
Character Type: Numeric government sources. The name, if assigned, will be
entered in the first record only. If source does not assign
5.123 FIR/UIR ATC Reporting Units Altitude (RUA) a name, this field may be blank.
Definition/Description: The “FIR/UIR ATC Reporting Units Used On: Restrictive Airspace records
Altitude” field is used to indicate the units of measurement Length: 30 characters
concerning the altitude used in the specific FIR/UIR to fulfill Character Type: Alpha/numeric
the requirements of ICAO flight plan. Examples: RANDOLPH ONE MOA,
SAMBURU GAME RESERVE
Source/Content: FIR/UIR Reporting Units should be derived
from official government publications. The field will be
entered on the first record only for each FIR/UIR identifier.
5.127 Maximum Altitude (MAX ALT)
Reporting Units Field Entry
Definition/Description: The “Maximum Altitude” field is
Not specified 0 used to indicate the maximum altitude allowed.
ALT in Flight Level 1
ALT in Meters 2 Source/Content: Maximum altitudes should be derived
ALT in Feet 3 from official government publications describing the
upper limit of the airway in feet or flight level.
Used On: FIR/UIR records
Length: 1 character Used On: Enroute Airway, Holding Pattern
Character Type: Numeric and Preferred Route records
Length: 5 characters
5.124 FIR/UIR Entry Report (ENTRY) Character Type: Alpha/numeric
Examples:
Definition/Description: The “FIR/UIR Entry Report” field is All numeric: 17999, 08000
used to indicate whether an entry report on ICAO flight plan is Alpha/numeric: FL100, FL450
required for that specific FIR/UIR. All alpha: UNLTD (for unlimited)
 ARINC SPECIFICATION 424 - Page 99

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Seq Boundary Arc Arc Arc Arc

No. Via Latitude Longitude Origin Origin Dist Brg
Latitude Longitude
010 H N45-00-00 W060-00-00
020 G N45-00-00 W047-00-00
030 G N43-12-45 W048-05-00
040 G N41-18-24 W046-16-12
050 G N38-58-54 W048-30-36
060 H N37-20-15 W047-00-00
070 R N37-20-15 W049-31-00 N37-20-18 W052-30-30 115 090
080 H N37-20-15 W055-30-00
090 G N42-00-00 W055-30-00

Figure 5-12
Controlled and Restrictive Airspace and FIR/UIR Boundaries
ARINC SPECIFICATION 424 - Page 100

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.128 Restrictive Airspace Type (REST TYPE) Source/Content: This field will be used when official
government publications for Restrictive Airspace divides an
Definition/Description: The “Restrictive Airspace Type” area with the same designator into different areas of
field is used to indicate the type of Airspace in which the Activation, altitude or other defining characteristics. For
flight of aircraft is prohibited or restricted. The restriction MSA Centers, this provides different sectorication and
may be continuous or specified for certain times. altitudes for the MSA published with the same center. The
field will contain an alpha character uniquely identifying
Source/Content: The “Restrictive Airspace Type” should be each area or MSA. The first record affected could contain
derived from official government publications. the character “A” and multiple primary records could
contain the character “B,” “C,” “D,” etc., as required.
Type Field Entry Used On: Controlled Airspace, Restrictive
Airspace, Airport and Heliport MSA
Alert A Center, Airport and Heliport
Caution C SID/STAR/Approach, and Enroute
Danger D Airway Flight Planning Continuation
Military Operations Area M Records.
Prohibited P Length: 1 character
Restricted R Character Type: Alpha
Training T
Warning W
Unspecified or Unknown U 5.131 Time Code (TIME CD)

Definition/Description: When used on the Primary

Used On: Restrictive Airspace and Enroute Airway Record of the possible record types, with the exception of
Flight Planning Continuation records Enroute Airway Restriction Records, this field is used to
Length: 1 character identify that the record in question is continuous or the
Character Type: Alpha times are other than continuous and are shown in a
Continuation Record. When used on a Continuation
5.129 Restrictive Airspace Designation Record, other than the Enroute Airway Restriction
Records, this field is used to indicate how the “Time of
Definition/Description: The “Restrictive Airspace Operation Fields” are to be interpreted. When used on
Designation” field contains the number or name that Enroute Airway Restriction Primary and Continuation
uniquely identifies the restrictive airspace. Records, this field identifies either a continuous situation
or a non-continuous situation, the detail for which is
Source/Content: The identifiers will be derived from official contained in the same record as the Time Code.
government sources. The field will contain a numeric
number, or when designation is by name this field will Source/Content: Active times are derived from official
contain the name up to 10 characters. When name is longer government source. The field will contain an alpha
than 10 characters, the 10th position will contain an asterisk character for which an associated description has been
indicating the name field should be used for the full defined as indicated in the tables below.
designator.
Used On: Restrictive Airspace and Enroute Airway Used On: Restrictive Airspace, Restrictive Airspace
Flight Planning Continuation records Continuation, Preferred Route, Preferred
Length: 10 characters Route Continuation, Airport, Heliport and
Character Type: Alpha/numeric Enroute Communication Airport, Heliport
and Enroute Communication Continuation
Field Entry records

Charted Designator ICAO Type Rest. Desig. PRIMARY RECORDS

Field Entry Description
RJ(R)-116 RJ R 116 C Active Continuously, including holidays
R-2524 K2 R 2524 H Active Continuously, excluding holidays
N Active Non-Continuously, Refer to
Crystal MOA K4 M Crystal Continuation Record
Randolph MOA One B K4 M Randolph* Blank Active times announced by NOTAM
CONTINUATION RECORDS
H Active times are provided in Time of
5.130 Multiple Code (MULTI CD) Operation format and exclude holidays
Activation Times are too complex for Time
Definition/Description: The “Multiple Code” field will be N of Operation format and are provided in
used to indicate Restrictive Airspace Areas or MSA Centers Note Form
having the same designator but subdivided or differently
divided by lateral and/or vertical detail. T Active times are provided in Time of
Operation format and include holidays
 ARINC SPECIFICATION 424 - Page 101

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Enroute Airway Restriction Primary and field will contain the alpha characters “AA”. For those
Continuation Records countries not using the standard ICAO table and having a
modified table this field will contain the alpha characters
PRIMARY AND “BB,” “CC,” etc. If a country uses the standard ICAO table
CONTINUATION RECORDS or a Modified table but indicates that an airway or portion
Field of an airway is to be flown opposite of the cruise table, the
Description field will contain alpha/numeric characters that identify the
Content
C Active Continuously, including holidays table to be used.
H Active Continuously, excluding holidays
Active times are provided in Time of Used On: Enroute Airway, FIR/UIR, Cruise Table
S and Flight Planning Arrival/ Departure
Operation format and exclude holidays
Active times are provided in Time of Data Records
T Length: 2 characters
Operation format and include holidays
Character Type: Alpha/numeric
Example:
Length: 1 character
Character Type: Alpha
Field Entry Description
5.132 NOTAM AA ICAO standard cruise table
AO Exception to ICAO cruise table
Definition/Description: Restrictive Airspace areas may not BB - ZZ Modified cruise table
have established active times and are activated by NOTAM BO - ZO Exception to modified cruise table
or may be active by NOTAM in addition to established
times. 5.135 Course FROM/TO

Source/Content: Active times by NOTAM will be derived Definition/Description: The “Course From” field is used to
from official government source. When used on primary indicate the lowest course for which a block of cruising
records, the area is active only by NOTAM and there will be levels are prescribed. The “Course To” field is used to
no continuation record. When used on continuation records, indicate the highest course for which a block of cruising
the area is active by NOTAM in addition to the levels is prescribed.
established times. The field will contain the alpha character
“N” to indicate either condition, otherwise the field will be Source/Content: The Courses will be derived from official
blank. government sources in degrees and tenths of degree with the
decimal point suppressed. The Magnetic/True indicator
Used On: Controlled Airspace, Restrictive Airspace field will be used to indicate True (T) or Magnetic (M)
and Restrictive Airspace Continuation courses.
records
Length: 1 character Used On: Cruising Table records
Character Type: Alpha Length: 4 characters
Character Type: Numeric
5.133 Unit Indicator (UNIT IND) Examples: 0000, 1790, 3590

Definition/Description: Restrictive Airspace lower and upper 5.136 Cruise Level From/To
limits are specified as “above mean sea level” (MSL) or
“above ground level” (AGL). This field permits the unit of Definition/Description: The “Cruise Level From” field is
measurement to be indicated. used to indicate the lowest cruising level prescribed for use
within the Course From/To fields. The “Cruise Level To”
Source/Content: The units of lower and upper limits are field is used to indicate the highest cruising level prescribed
derived from official government source. The alpha for use within the Course From/To fields.
character “M” will indicate MSL and the alpha character “A”
will indicate AGL. Source/Content: Cruise Levels will be derived from official
government sources. When the level is entered in feet the
Used On: Controlled Airspace, Restrictive Airspace field will be all numeric. When the level is entered in
records meters, the first column will contain the alpha character
Length: 1 character “M” followed by all numeric. If the “Level To” is unlimited,
Character Type: Alpha the field will contain the alpha characters “UNLTD”.

5.134 Cruise Table Identifier (CRSE TBL IDENT) Used On: Cruising Table records
Length: 5 characters
Definition/Description: A standard cruising level table is Character Type: Alpha/numeric
established by ICAO and is to be observed except when, on Examples: 0200, M0600, M1585
the basis of regional air navigation agreements, a modified
table of cruising levels is prescribed for use. This field
permits the enroute airway record to identify the Cruise 5.137 Vertical Separation
Table record that is to be used for cruise levels.
Definition/Description: The “Vertical Separation” field is
Source/Content: Cruise Levels will be derived from official used to indicate the minimum separation prescribed to be
government sources. For the standard ICAO cruise table this maintained between the cruising levels.
ARINC SPECIFICATION 424 - Page 102

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: Vertical Separation Values will be derived 5.141 Starting Latitude

from official government sources and entered in feet or tens
of meters with “M” in the first column. Definition/Description: The Grid MORA Table will contain
records describing the MORA for each Latitude and
Used On: Cruising Table records Longitude block. Each record will contain thirty blocks and
Length: 5 characters the “Starting Latitude” field defines the lower left corner for
Character Type: Alpha/numeric the first block of each record.
Examples: 01000, 02000, M0030, M0060
Source/Content: The “Starting Latitude” will be determined
when the record is assembled.
5.138 Time Indicator (TIME IND)
Used On: Grid Mora record
Definition/Description: The “Time Indicator” field is used Length: 3 characters
to indicate whether the times shown in the “Time of Character Type: Alpha/numeric
Operations” field(s) are Local Time, Daylight Savings Examples: N00, N42, S20, S90
Time or Universal Coordinated Time.
5.142 Starting Longitude
Source/Content: Time contained in the affected record(s)
is derived from official government sources. The “Time Definition/Description: The Grid MORA table will contain
Indicator” will qualify those source derived times as records describing the MORA for each Latitude and
indicated in the following table: Longitude block. Each record will contain thirty blocks and
the “Starting Longitude” field defines the lower left corner
Field Entry Description for the first block of each record.
T Times codes are Local Time
Times codes are to be adjusted for Source/Content: The “Starting Longitude” will be
S determined when the record is assembled.
Daylight Savings Time
Blank Times shown are Universal Coordinated
Time (UTC) Used On: Grid Mora records
Length: 4 characters
Used On: Controlled Airspace, Restrictive Character Type: Alpha/numeric
Airspace Continuation, Referred Route Examples: E000, W150, E090, W180
Continuation, Enroute Airway
Restriction, Airport and Heliport 5.143 Grid MORA
Communication Continuation and
Enroute Communications Continuation Definition/Description: Grid MORA Minimum Off-route
Records Altitude (MORA) provides terrain and obstruction
Length: 1 character clearance within the section outlined by latitude and
Character Type: Alpha longitude blocks provided in the Starting Latitude and
Starting Longitude fields.

5.139 Intentionally Left Blank Source/Content: Grid MORA values clear all terrain and
obstructions by 1000 feet in areas where the highest
elevations are 5000 feet MSL or lower. MORA values
5.140 Controlling Agency clear all terrain by 2000 feet in areas where the highest
elevations are 5001 feet MSL or higher. The field will
Definition/Description: Some “Restrictive Airspace” areas contain values expressed in hundreds of feet, for example,
are designated joint use and IFR operations in the area may the value of 6000 feet is expressed as 060 and the value of
be authorized by the controlling agency when it is not being 7100 feet is expressed as 071. For geographical sections
utilized by the using agency. that are not surveyed, the field will contain the alpha
characters UNK for Unknown.
Source/Content: The name of the Controlling Agency should
be derived from official government sources and will be COMMENTARY
shown on the first record only. If no Controlling Agency is
specified the field may be blank. MORA values are generally not provided in
government source and are calculated by the data
Used On: Controlled Airspace, Restrictive Airspace supplier using the formula indicated in the
Continuation record Source/Content paragraph. There are, however, some
Length: 25 characters governments that do provide off route altitude data
Character Type: Alpha/numeric and a data supplier may elect to use the government
Examples: LAX, ARTCC, Lumpur ACC, source values in their data services.
Butterworth APP
Used On: Grid MORA Records
Length: 3 characters
Character Type: Alpha/numeric
Examples: 010, 071, 100, 123, UNK
 ARINC SPECIFICATION 424 - Page 103

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.144 Center Fix (CENTER FIX)

Definition/Description: When used on Airport and

Heliport MSA Records and specific terminal procedure
records, the “Center Fix” field represents the MSA Center,
that point (Navaid or Waypoint) on which the MSA is
predicated. When used on Terminal Procedure Records
incorporating an “RF” Path and Termination, the field
represents the point (Terminal Waypoint) which defines
the center of the arc flight path.
Source/Content: When used as “MSA Center,” the field
will contain the identification of the navigation facility,
Enroute Waypoint, Terminal Waypoint, Runway or Airport
Reference Point upon which the MSA coverage radius is
predicated. Such content will be derived from official
government sources. When use as “ARC Center,” the field
will contain the identification of the Terminal Waypoint
used to define the arc. ARC Center waypoints can only
appear in the Airport Terminal Waypoint or Heliport
Terminal Waypoint Section/Subsections.
Used On: Airport and Heliport MSA Records,
Airport and Heliport
SID/STAR/Approach Records
Length: 5 characters max.
Character Type: Alpha/numeric
Examples: HOM, YXRNB, MM18, ARC02
ARINC SPECIFICATION 424 - Page 104

5.0 NAVIGATION DATA - FIELD DEFINITIONS

SEC SUB START START

MORA MORA MORA MORA MORA MORA MORA MORA
CODE CODE LAT LONG
A S N00 E000 010 010 010 010 010 010 090 191
A S N01 E000 010 010 010 010 010 010 010 082
A S N02 E000 010 010 010 010 010 010 010 073
A S N03 E000 010 010 010 010 010 010 010 073
A S N04 E000 010 010 010 010 010 015 UNK 049
A S N05 E000 026 014 010 010 014 020 UNK 042
A S N06 E000 049 024 020 019 026 029 029 042
A S N07 E000 UNK 040 033 031 038 043 035 040
A S N08 E000 041 037 033 035 035 034 035 UNK
A S N09 E000 029 045 030 035 027 032 033 UNK
A S N10 E000 030 034 029 028 028 032 043 UNK
A S N11 E000 030 034 031 032 025 041 046 UNK
A S N12 E000 026 029 029 022 024 028 043 UNK
A S N13 E000 026 030 030 030 026 026 030 UNK
A S N14 E000 031 031 024 030 023 040 034 UNK

E000 E001 E002 E003 E004 E005 E006 E029

Figure 5-13 GRID MORA Sample

The table shows a sample of the Grid Mora Table as it would appear in the file. The table starts at N00/E000 and ends at
N14/E029, and is blocked at intervals of sixty minutes. The values shown in the Start Lat and Start Long fields are the lower
left corner of a one degree Lat/Long box. The values shown at the bottom of the table are for illustration purpose only and
show the Longitude of the lower corner for the MORA values in the table. The values from longitude E007 thru E028 have
been omitted from this illustration.
 ARINC SPECIFICATION 424 - Page 105

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.145 Radius Limit Used On: Airport and Heliport MSA Records and
TAA Primary Records
Definition/Description: The altitude shown in the “Sector Length: 3 characters
Altitude” field provides a 1000 foot obstacle clearance with Character Type: Numeric
a specified radius from the navigational facility/fix. The Examples: 010 = 1000ft, 025 = 2500, 100= 10,000
“Radius Limit,” field allows the radius to be specified.

Source/Content: Radius limits will be derived from official 5.148 Enroute Alternate Airport (EAA)
government sources. Values will be shown in whole
nautical miles. Definition/Description: The “Enroute Alternate Airport”
field identifies the most suitable emergency airport along a
Used On: Airport and Heliport MSA Records Company Route.
Length: 2 characters Source/Content: This field is determined by the user airline
Character Type: Numeric and will contain the Airport ICAO Ident.
Examples: 25, 30
Used On: Company Route records
5.146 Sector Bearing (SEC BRG) Length: 4 characters
Character Type: Alpha/numeric
Definition/Description: When the MSA is provided as Examples: KDEN, EGKK, EDFF
sectors of a circle, the field defines the beginning and end
bearings of the sectors. The bearings are to the MSA 5.149 Figure of Merit (MERIT)
Center Fix. When used on TAA records – The sector
bearings in TAA records are the start and end bearings that Definition/Description: The “Figure of Merit” field is used
define a TAA area and are to the TAA IAF Waypoint to specify VHF Navaid facility usable ranges beyond that
defined in that TAA identified as the straight-in or center specified in the Class field. It is also used to specify when a
sector record (Section 5.272). For both the MSA and the VHF Navaid contained in the database is not available for
TAA record use, the bearings are entered clockwise. They operational use, i.e., is out of service and is used to flag a
enclose the sector defined in the record. The values are VHF Navaid that is not included in a civilian international
inclusive. NOTAM system.

Source/Content: The Sector Bearing information will be Source/Content: Actual Field Entry Values are not
derived from official government sources. Each sector is contained in official government source but rather are
made up of the start of sector bearing and the end of derived values based on usage, class, availability etc. These
sector bearing. The values are provided in whole degrees. may be further adjusted by input from actual users. The
The first three characters identify the start sector bearing. content will be as defined in the table below.
The second three characters identify the end sector
bearing. For a MSA that is a circle, no sectors both the Field
start and the end bearing set to 180. Entry Description

Used On: Airport and Heliport MSA and TAA 0 Terminal Use (generally within 25NM)
Primary Records 1 Low Altitude Use (generally within 40NM)
Length: 6 characters
Character Type: Numeric 2 High Altitude Use (generally within 130NM)
Examples: 060140, a Sector that starts at 060
degrees and continues clockwise to end 3 Extended High Altitude Use (generally beyond
at 140 degrees. 130NM)
140060, a Sector that starts at 140 7 Navaid not included in a civil international
degrees and continues clockwise to end NOTAM system
at 060 degrees
180180, a full circle MSA Sector 9 Navaid Out of Service

5.147 Sector Altitude (SEC ALT) Used On: VHF Navaid Records
Length: 1 character
Definition/Description: When used on MSA records, the Character Type: Numeric
“Sector Altitude” provides a 1000 foot obstacle clearance
within the specified sector. When used on TAA records, 5.150 Frequency Protection Distance (FREQ PRD)
the “Sector Minimum Altitude” is the minimum altitude
for that sector, providing obstacle clearance compatible Definition/Description: The “Frequency Protection
with the instrument procedures with which the TAA is Distance” field provides an indication of the distance to the
associated, generally 1000 feet or more as necessary in next nearest NAVAID on the same frequency.
mountainous areas. Flight crews are expected to fly direct
to the initial approach fix in the record at the appropriate Source/Content: The distance to the next NAVAID will be
sector altitude unless otherwise instructed by ATC. computer generated values. Values will be entered on
NAVAID with DME or TACAN equipped facilities only
Source/Content: Sector Altitude values are derived from and will indicate the distance, in nautical miles, to the next
official government source and are provided in hundreds nearest DME or TACAN equipped facility. Maximum
of feet. relevant value will be 600 nautical miles.
ARINC SPECIFICATION 424 - Page 106

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On : VHF Navaid records 5.153 Start/End Date

Length: 3 characters
Character Type: Alpha/numeric Definition/Description: The “Start/End Date” when used on
Examples: 030, 150, 600 Continuation records specifies the effective Start/End date
for a specific primary record when the effective date does
5.151 FIR/UIR Address (ADDRESS) not correspond with the AIRAC date. When used on
Restriction records the Start and End dates specifies when
Definition/Description: The “FIR/UIR Address” field the restrictions are in effect.
contains the four character communications address of the
FIR/UIR to supplement the FIR/UIR Ident. Source/Content: Effective dates will be derived from
official government sources indicating the date/time in
Source/Content: When addressing ATS messages to the GMT of the effective date of the record or the effective
ATS Center in charge of a FIR or UIR, a three-letter times of the restriction. Default of the Start date is the
designator followed by a filler of “X” or by a letter current GMT date and default of the End date is forever.
representing a department or division within the
organization addressed should be used. The three-letter Used On: Restrictive Airspace, VHF NAVAID,
designators are to be those defined in ICAO Document NDB NAVAID, Enroute, Terminal
8585, Designators for Aircraft Operating Agencies, Waypoint, Airport Flight Planning
Aeronautical Authorities 2 and Services. ICAO Document Continuation and Heliport records
7910, Location Indicators, Address of Centers in charge of Length: 11 characters
FIR/UIR, states that when addressing ATS messages to the Character Type: Alpha/numeric
ATS Center in change of a FIR or a UIR, one of the Examples: 12JAN840000, 28SEP841200
following designators should be added to the location
indicator to complete the addressee indicator: 5.154 Restriction Identifier (REST IDENT)
If the message is related to an IFR Flight -- ZQZX Definition/Description: The “Restriction Identifier” is used
If the message is related to a VFR Flight -- ZFZX to assign a unique identifier to a restriction record and to
multiple restrictions records for a particular route or route
To satisfy this requirement, unless otherwise stipulated by segment.
the user, the following address codes will be used:
Source/Content: Restriction Identifiers are assigned during
ZOZX if related to an Oceanic FIR/UIR. the data file assembly. Initially the identifier will be
ZRZX if related to all other FIR/UIRs. assigned in sequence with the first restriction assigned the
numeric value “001,” the second “002,” the third “003,” etc.
Used On: FIR/UIR and Enroute Communications If a restriction record is removed, only that record is deleted
records and there will be no effect on the other identifiers for that
Length: 4 characters airway; i.e., if record “002” is deleted, records “001” and
Character Type: Alpha “003” will retain their identifiers. If a new restriction is
Examples: ZOZX, ZRZX added, within a few cycles of the deletion of “002,” it will
use the next higher number even if there are gaps in the
5.152 Start/End Indicator (S/E IND) sequence of identifiers.

Definition/Description: The “Start/End Indicator” field is Used On: Airway Restriction and Airway
used to indicate if the “Start/End Date” field is the effective Restriction Continuation records
start date, effective end date or the effective date for a Length: 3 characters
change of the Primary record. Character Type: Numeric
Examples: 001, 002, 003
Source/Content:
5.155 Intentionally Left Blank
Field Entry Description
5.156 Intentionally Left Blank
C Change Date
E End Date 5.157 Airway Restriction Start/End Date (START/END
S Start Date DATE)

Note: If the Start/End Indicator field contains the alpha Definition/Description: The “Airway Restriction Start Date”
character “C” then the following continuation record field is used to indicate the earliest GMT date at which the
is paired with it and the record will contain only the restriction takes effect. The “Airway Restriction End Date”
new values in the changed fields. All other fields will is used to indicate the latest GMT date at which the
be blank. restriction is still in effect. This date information may be
supplemented by “Time of Operation” information
Used On: Restrictive Airspace, VHF NAVAID, contained in an Airway Restriction Record, Type “AE” or
NDB NAVAID, Enroute, Terminal “TC”. When no “AE” or “TC” record exists for the
Waypoint, Airport Flight Planning Restriction Identifier, the Start time is 0000 GMT and the
Continuation and Heliport records end time is 2359 GMT of the dates indicated.
Length: 1 character
Character Type: Alpha Source/Content: When entered, start dates and end dates
will be in the format DDMMMYY. If the YY portion is
 ARINC SPECIFICATION 424 - Page 107

5.0 NAVIGATION DATA - FIELD DEFINITIONS

equal to blanks, the restriction is valid every year. When the Source/Content:
start date is equal to blanks, the restriction is valid with
immediate affect. When the end date is equal to blanks, the Field
restriction is valid until further notice. Description
Entry
Used On: Enroute Airway Restriction records B Step climb up or down is permitted
Length: 7 characters D Only step climb down is permitted
Character Type: Alpha/numeric N No step climb is permitted
Examples: 15JAN92, 15 JAN (blank) U Only step climb up is permitted

5.158 Intentionally Left Blank Used On: Airway Restriction and Airway
Restriction Continuation records
5.159 Intentionally Left Blank Length: 1 character
Character Type: Alpha
5.160 Units of Altitude (UNIT IND)
5.163 Restriction Notes
Definition/Description: The “Units of Altitude” field is used
to indicate the units of measurement for the values in the Definition/Description: The “Restriction Notes” field may
“Restriction Altitude” fields. contain any restriction not otherwise covered by the altitude
or time restriction.
Source/Content: The actual values are derived from official
government sources and expressed as one of the following Source/Content: Restriction notes will be derived from
codes. official government sources.

Field Used On: Airway Restriction continuation records

Entry Description Length: 104 characters
Character Type: Alpha/numeric
F Restriction Altitudes are expressed in Examples: AVAILABLE FOR WESTBOUND
hundreds of feet DEPARTURES FROM GATWICK.
K Restriction Altitudes are expressed in metric EASTBOUND AND OVER-FLIGHTS
Flight Levels BY ATC ONLY. REROUTING MUST
L Restriction Altitudes are expressed in feet BE EXPECTED MON-FRI 1800-2400
Flight Levels DUE TO MILITARY TRAFFIC.
M Restriction Altitudes are expressed in tens of
meters 5.164 EU Indicator (EU IND)
Definition/Description: The “EU Indicator” field is used to
Used On: Airway Restriction records and Airway identify those Enroute Airway records that have an Airway
Restriction Continuation Records Restriction record without identifying the restriction.
Length: 1 character
Character Type: Alpha Source/Content: The field will contain the alpha character
“Y” when a restriction for the segment is contained in the
5.161 Restriction Altitude (RSTR ALT) restriction file or a blank when no restriction record exists.

Definition/Description: The “Restriction Altitude” fields Used On: Enroute Airways records
are used to specify the altitude profile for a specific Length: 1 character
restriction. Character Type: Alpha
Source/Content: Altitudes will be derived from official 5.165 Magnetic/True Indicator (M/T IND)
government sources and entered in hundreds of feet, tens of
meters, standard or metric Flight Levels. The units used are Definition/Description: The “Magnetic/True Indicator”
determined through the “Units of Altitude” field. Altitudes field is used to indicate if the “Course From” and “Course
are expressed in ascending order. All altitude fields after a To” fields of the Cruise Table record and the “Sector
“blank” altitude will also be blank. Bearing” fields of the MSA and TAA record are in
magnetic or true degrees. It is also used in the Airport
Used On: Airway Restriction, Airway Restriction Record to indicate that all detail and procedures for that
Continuation records airport are included in the data base with a reference to
Length: 3 characters either Magnetic North or True North. The field is blank in
Character Type: Numeric Airport Record when the data base contains a mix of
Examples: 310 (standard FL310 or metric FL3199m magnetic and true information for the airport.
or 31000 feet or 3100 meters)
090 (standard FL90 or metric FL900m or Source/Content: Cruise Table Courses, MSA, and TAA
9000 feet or 900 meters) Sector Bearings will be derived from official government
source. The field will contain the alpha character “M” if the
5.162 Step Climb Indicator (STEP) Course From/To or Sector Bearings are magnetic. It will
contain the alpha character “T” if the courses/bearings are
Definition/Description: The “Step Climb Indicator” field is true. In Airport Records, the field will contain the alpha
used to indicate if step climb up or down is permitted. character “M” if all detail and procedure for the airport are
ARINC SPECIFICATION 424 - Page 108

5.0 NAVIGATION DATA - FIELD DEFINITIONS

reported in magnetic bearing, the alpha character “T” if all Used On: MLS and MLS Continuation records
detail and procedure for the airport are reported in true Length: 3 characters
bearing. The field will be “blank” if details and procedures Character Type: Numeric
are provided in both magnetic and true for the airport. In Examples: 040, 025, 015
such cases the individual detail or procedure records will
contain the “magnetic” or “true” information. 5.169 Elevation Angle Span (EL ANGLE SPAN)

Used On: Airport, Heliport, Cruise Table and Definition/Description: The “Elevation Angle Span” field
Airport and Heliport MSA Records, and defines the scan of the elevation transmitter signal between
Airport and Heliport TAA Record the lower and upper limits.
Length: 1 character
Character Type: Alpha Source/Content: Elevation angle span limits will be derived
from official government publications and entered in
5.166 Channel degrees and tenths of degrees with the decimal point
suppressed.
Definition/Description: The “Channel” field specifies the
channel of the Azimuth, Elevation and Data transmissions Used On: MLS records
for the MLS identified in the “MLS Identifier” field of the Length: 3 characters
record. Character Type: Numeric
Examples: 300, 150
Source/Content: Channels are derived from official
government sources and range from 500 to 699. 5.170 Decision Height (DH)
Used On: MLS records Definition/Description: The “Decision Height” fields are
Length: 3 characters used to specify a specific height in the precision approach at
Character Type: Numeric which a missed approach must be initiated if the required
visual reference to continue the approach has not been
5.167 MLS Azimuth Bearing (MLS AZ BRG) established.
MLS Back Azimuth Bearing (MLS BAZ BRG)
Source/Content: Decision Height information is obtained
Definition/Description: The “MLS Azimuth Bearing” and from official government publications and will be the ILS
the “MLS Back Azimuth Bearing” fields define the inbound CAT I barometric related value. The field will contain a
magnetic final approach course of the MLS Azimuth and numeric value expressed in feet above touchdown, with a
the MLS Back Azimuth facility described in the record. resolution of one foot. This value is also referred to as
“Height Above Touchdown” (HAT), a figure which, when
Source/Content: MLS bearings derived from official added to the touchdown zone, runway end or threshold
government sources are entered into the field in degrees and elevation, will give the Decision Altitude in feet above
tenths of degrees with the decimal point suppressed. For mean sea level. These fields will be shown on the first
MLS Azimuth or Back Azimuth charted with true courses, record of the final approach only and may be blank if
the last character of this field will contain a “T” in place of Minimum Descent Altitude fields are entered.
tenths of a degree.
Used On: Airport and Heliport Approach
Used On: MLS and MLS Continuation records Continuation Records.
Length: 4 characters Length: 4 characters
Character Type: Numeric Character Type: Alpha/numeric
Examples: 0550, 0155, 015T Examples: 0200
5.168 Azimuth Proportional Angle Right/Left 5.171 Minimum Descent Height (MDH)
(AZ PRO RIGHT/LEFT)
Definition/Description: The “Minimum Descent Height”
Back Azimuth Proportional Angle Right/Left fields specify the lowest height, expressed in feet, to which
(BAZ PRO RIGHT/LEFT) descent is authorized on final approach or during circle-to-
land maneuvering in execution of a standard instrument
Definition/Description: The “Azimuth Proportional Angle” approach procedure where no electric glide slope is
fields define the limits of proportional guidance of the provided.
azimuth transmitter signal on the right and left side of the
final approach course flight track. The BAZ is identical to Source/Content: Minimum Descent Height information is
the AZ and also provides guidance for missed approaches obtained from official government publications. The field
and departures. See figure under Section 5.172. will actually contain a figure expressed in feet above the
airport elevation, with a resolution of one foot. This value is
Source/Content: Azimuth Proportional angles will be also referred to as “Height Above Airport” (HAA), a figure
derived from official government publications and entered which, when added to the airport elevation, will give the
in whole degrees. Minimum Descent Altitude in feet above mean sea level.
These fields will be shown on the first record of the final
approach only and may be blank if Decision Height fields
are entered.
 ARINC SPECIFICATION 424 - Page 109

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Airport and Heliport Approach Links in the Flight Planning Continuation Record defined in
Continuation records 4.6.3 (more than four area links required).
Length: 4 characters
Character Type: Alpha/numeric Source/Content: When an additional Continuation Record
Examples: 0314, 0514 (as defined in Section 4.1.6.4) is required to provide further
Enroute Airway to Restrictive Airspace Links, this field will
5.172 Azimuth Coverage Sector Right/Left contain the alpha character “Y” to indicate that status.
(AZ COV RIGHT/LEFT)
Used On: Enroute Airway Flight Planning
Back Azimuth Coverage Sector Right/Left Continuation records
(BAZ COV RIGHT/LEFT) Length: 1 character
Definition/Description: The “Azimuth Coverage Sector” Character Type: Alpha
fields define the limit of the azimuth transmitter signal on
the right and left side of the final approach course flight 5.175 Holding Speed (HOLD SPEED)
track. The Back Azimuth Coverage Sector is identical to the
Azimuth Coverage Sector and also provides guidance for Definition/Description: The “Holding Speed” will be the
missed approaches and departures. maximum speed in a holding pattern.

Source/Content: Azimuth Coverage Sectors will be derived Source/Content: The speed limit will be derived from
from official government publications and entered in whole official government sources. If the value is different from
degrees. the limit given with ICAO rules, it will be shown in knots,
else the field will be blank.
Used On: MLS and MLS Continuation records
Length: 3 characters Used On: Holding Pattern record
Character Type: Numeric Length: 3 characters
Examples: 040, 062, 110 Character Type: Numeric
Examples: 250, 015
COMMENTARY
5.176 Pad Dimensions
The Azimuth Coverage Sector includes the
Proportional Guidance Sector and the Clearance Definition/Description: The “Pad Dimensions” field
Guidance Sector as illustrated in below. defines the landing surface dimensions of the helicopter
landing pad. The pad may be described as a rectangle or as
a circle.

Source/Content: Pad dimensions will be derived from

official government sources and entered into the field in feet
with a resolution of one foot. When the pad is rectangular,
the first three digits define one side of the landing pad and
the last three digits the other side of the pad, e.g. “060120”
indicates the pad is 60 feet by 120 feet. When the pad is
circular, the first three digits define the diameter of the pad
and the last three digits will be zeros, e.g., “080000”
indicates a pad that is 80 feet in diameter.

5.173 Nominal Elevation Angle (NOM ELEV ANGLE) Used On: Heliport record
Length: 6 characters
Definition/Description: The “Nominal Elevation Angle” Character Type: Numeric
field defines the normal glide path angle for the MLS Examples: 060060, 100050, 040040
installation.
5.177 Public/Military Indicator (PUB/MIL)
Source/Content: Glide Path angles from official government
sources are entered into the field in tens of degrees, Definition/Description: Airports can be classified into three
tenths of a degree, and hundredths of a degree with the categories, airports open to the general public, military
decimal point suppressed. airports, and airport closed to the public. This field permits
these airports to be categorized by their use.
Used On: MLS records
Length: 4 characters Source/Content: Airport data is obtained from official
Character Type: Numeric government sources and their use is defined in these civil
Examples: 1000, 0275 and or military publications. Airports that are considered
joint use, both civil and military, will be shown as a civil
5.174 Restrictive Airspace Link Continuation (LC) airport.

Definition/Description: The “Restrictive Airspace Link

Continuation” field is used to indicate cases where it is not
possible to store all Enroute Airway to Restrictive Airspace
ARINC SPECIFICATION 424 - Page 110

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Summer time when such time changes are in effect for the
Field country or state the airport resides in.
Description
Content
C Airport/Heliport is open to the public (civil) Source/Content: Countries and states that observe Daylight
M Airport/Heliport is military airport time will be obtained from official publications and the field
P Airport/Heliport is not open to the public will contain the alpha character “Y” if airport observes
(private) Daylight or Summer time. The field will contain the alpha
character “N” if the airport does not observe Daylight time
Used On: Airport and Heliport records or if it is unknown.
Length: 1 character
Character Type: Alpha Used On: Airport and Heliport records
Length: 1 character
5.178 Time Zone Character Type: Alpha

Definition/Description: The standard time zone system is 5.180 Pad Identifier (PAD IDENT)
based on the division of world into 24 zones, each of 15
degrees longitude. The “zero” time zone is entered at Definition/Description: The “PAD Identifier” field
Greenwich meridian with longitudes 7 degrees, 30 minutes identifies the helipad described in the heliport records,
West and 7 degrees, 30 minutes east, and there is no helipad field, or that pad served by ILS/MLS described in
difference in the standard time of this time zone and the Airport and Heliport ILS/MLS records. There is a
Greenwich Mean Time. Time zones are designated by unique Heliport Record for each Helipad at a given
letters of the alphabet by which the standard time of each location.
zone differs from that at Greenwich.
Source/Content: PAD Identifiers will be derived from
Source/Content: Time zones will be derived from official official government publications when available. If not
Time Zone Charts of the World. The first character of the available from source, unique identifiers will be assigned
field indicates the time zone observed by the airport. Time by the data supplier.
zones are indicated by a letter of the alphabet according to
the following table: Used On: Heliport, Airport and Heliport ILS and
MLS Records
Field
Diff to
Field Diff to Zulu Length: 5 characters max
Zulu Lat/long Boundaries Lat/Long Boundaries
Cont
time
Cont time Character Type: Alpha/numeric
Examples: Source Supplied - PADA1, NWPAD,
Z 0 W007 30/E007 30 ALPHA, A1
A -1 E007 30/E022 30 N +1 W007 30/W022 30
B -2 E022 30/E037 30 O +2 W022 30/W037 30
Data Supplier - HELO1, HELO2,
C -3 E037 30/E052 30 P +3 W037 30/W052 30 HELO3
D -4 E052 30/E067 30 Q +4 W052 30/W067 30
E -5 E067 30/E082 30 R +5 W067 30/W082 30 5.181 H24 Indicator (H24)
F -6 E082 30/E097 30 S +6 W082 30/W097 30
G -7 E097 30/E112 30 T +7 W097 30/W112 30
H -8 E112 30/E127 30 U +8 W112 30/W127 30
Definition/Description: The “24H Indicator” field is used
I -9 E127 30/E142 30 V +9 W127 30/W142 30 to indicate if the frequency is available on a 24 hour basis or
K -10 E142 30/E157 30 W +10 W142 30/W157 30 only on a part time base.
L -11 E157 30/E172 30 X +11 W157 30/W172 30
M -12 E172 30/180 00 Y +12 W172 30/180 00 Source/Content: Hours of operation are derived from
official government publications. The field will contain the
The second and third characters indicate, in minutes, that alpha character “Y” if the frequency is available 24 hours or
the time observed by the airport/heliport must be adjusted the alpha character “N” if it is available part time.
from the hour by the number of minutes indicated.
Used On: Enroute/Airport Communications records
Used On: Airport and Heliport records Length: 1 character
Length: 3 characters Character Type: Alpha
Character Type: Alpha/numeric
Examples: India falls in the “E” (-5) and “F” (-6) 5.182 Guard/Transmit (G/T)
time zones, however, the time zone
observed in all of India is “E30” (-5 Definition/Description: The “Guard/Transmit” field is used
hours and 30 minutes). For any country to indicate if the frequency shown in the Communication
falling into the “M” or “Y” time zone and Frequency field is used, by the station, to receive voice
observing a time equal to the next greater communications or to transmit voice on.
time zone, the adjustment of 1 hour will
be indicated by “60” in the second and Source/Content: The field will be derived from official
third positions. government publications. The field will contain the alpha
character “G” if the radio guards (receives), or the alpha
5.179 Daylight Time Indicator (DAY TIME) character “T” if the radio transmits, on the respective
frequency. The field will be blank if the radio receives and
Definition/Description: The “Daylight” Time Indicator” transmits on the same frequency.
field is used to indicate if the airport observes Daylight or
 ARINC SPECIFICATION 424 - Page 111

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Enroute/Airport 5.186 Narrative

Communications records
Length: 1 characters Definition/Description: The “Narrative” field is used to
Character Type: Alpha define communication sectors in a narrative form when the
Sectorization field cannot be used, or to further define the
5.183 Sectorization (SECTOR) sector when the Sectorization field is used.
Definition/Description: The “Sectorization” field is used to Source/Content: Sectors are derived from official
define the airspace sector a communication frequency is government publications. The field will contain a free form
applicable for when an airport defines sectors by bearing description of the sectorization for the frequency being
from the same point. defined.
Source/Content: Sectors are derived from official Used On: Airport Communications Continuation
government publication. Each sector will contain two records
bearings, indicated in whole degrees, of the sector being Length: 60 characters
defined. The first three numeric characters define the Character Type: Alpha/numeric
beginning bearing from the station, and the last three Examples: NORTH COMPLEX, RWYS 9/27
characters define the ending bearing from the station. If the 15/33
sectors are not defined by bearings, then the sectorization
will be shown in narrative form in an Airport 5.187 Distance Description (DIST DESC)
Communications Continuation record.
Definition/Description: The “Distance Description” field
Used On: Airport Communication records will designate whether a Communications frequency is to be
Length: 6 characters used from the facility out to a specified distance or from a
Character Type: Alpha/numeric specified distance and beyond in the Airport
Examples: 010189, 190009 Communications Record. In the VHF Navaid Limitation
Continuation Record, the field is used to define whether the
5.184 Communication Altitude (COMM ALTITUDE) limitation applies from the navaid out to a specified distance
or from a specified distance and beyond.
Definition/Description: The “Communication Altitude”
fields are used to define the altitude restrictions that the Source/Content: The field will contain the character “-”
frequency is to be used within. On Airport Communications when the communications frequency or navaid limitation is
records, this field is normally used in conjunction with “out to a specified distance.” When the field content is “+”,
sectorization. then the communications frequency is used or the navaid
limitation applies “beyond” a specified distance. When the
Source/Content: Altitude constraints will be derived from field is blank, no restrictions/limitations apply.
official government publications. The field may contain
altitudes (all numerics) or flight levels (alpha/numerics). Used On: Airport Communications Records, VHF
The all numeric fields will contain altitudes, in feet, with a Navaid Limitation Continuation Records
resolution of one foot. The alpha/numeric fields will contain Length: 1 character
the alpha characters “FL” followed by the altitude in Character Type: Alpha
hundreds of feet. The first altitude field will contain an
altitude when the Altitude Descript field contains a plus (+), 5.188 Communications Distance (COMM DIST)
minus (-) or B. The second altitude field will contain an
altitude when the Altitude Descript field contains a B. Definition/Description: The “Communications Distance”
field is used to define the distance restriction a
Used On: Enroute/Airport Communications records communication frequency is to be used within or beyond
Length: 5 characters when such restrictions apply. This field is used in
Character Type: Alpha/numeric conjunction with the Distance Description field.
Examples: 12000, 06000, FL050
Source/Content: Distances restrictions are derived from
5.185 Sector Facility (SEC FAC) official government publications and will contain a value in
nautical miles from the communications facility. If the
Definition/Description: The “Sector Facility” field is used Distance Description field contains the character “-”, then
to define the Navaid or Airport upon which the information the frequency is to be used from the facility to the distance
in the “Sector” (5.183) field is based. specified. If the Distance Description field contains the
character “+” then the frequency is to be used from the
Source/Content: Sector related facility information will be distance specified and beyond. The field will be blank if no
derived from official government sources. The field will restrictions apply.
contain the official Navaid or Airport identifier.
Used On: Airport Communications records
Used On: Airport and Heliport Communications Length: 2 characters
Records Character Type: Numeric
Length: 4 characters Examples: 05, 10, 15
Character Type: Alpha/numeric
Examples: IOC, COS, DEN, KJFK
ARINC SPECIFICATION 424 - Page 112

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.189 Remote Site Name Used On: Preferred Route record

Length: 5 characters
Definition/Description: The “Remote Name” contains the Character Type: Alpha/numeric
name assigned to a Remote Communications Air/Ground
and Remote Communications Outlet facilities. These Examples: KDEN, CYUL, DEN, YUL, COLOR
remote facilities are unmanned air/ground communication
stations with transmit and receive capability, used to extend Entries for Metro Area “New York to
the service range of ARTCC and FSS stations. Atlanta”
Seq 010 KJFK K6 KATL K7
Source/Content: Remote Names are derived from official Seq 020 KLGA K6
government publications. The field may be blank if names Seq 030KEWR K6
are not assigned.
Entries for Atlanta to Metro Area “New
Used On: Enroute Communications records York”
Length: 25 characters Seq 010KATL K7 KJFK K6
Character Type: Alpha/numeric Seq 020LGA K6
Examples: CHEYENNE, ABBEVILLE Seq 030KEWR K6

5.190 FIR/RDO Identifier (FIR/RDO) 5.195 Time of Operation

Definition/Description: The “FIR/RDO Identifier” field for Definition/Description: The “Time of Operation” field is
Enroute Center records identifies the Flight Information used to indicate the times of operation of a Facility or
Region or Upper Information Region. For FSS records the Restriction.
field identifies the Flight Service Station.
Source/Content: The times of operation are derived from
Source/Content: Identifiers are obtained from official official government source. Each “Time of Operation”
government publications. For FIR/UIR the field will contain group contains the definition of a daily period of operations
the four characters FIR or UIR ident. For other record type within a calendar week.
the field will contain a three or four character identifier.
The first two positions identify days of the week, with
Used: Enroute Communications records Monday equal to 1 and Sunday equal to 7. A single day, for
Length: 4 characters example, Monday, is depicted as “01”. A consecutive series
Character Type: Alpha/numeric of days, for example Monday through Friday, is depicted as
Examples: KZDN, DEN “15”. Non-consecutive days require multiple Time of
Operation entries. The remaining 8 characters define a
5.191 Triad Stations (TRIAD STA) starting time of four characters and an ending time of four
characters. These times are in the format HHMM (H=
Deleted by Supplement 14. hours, M= minutes) using a 24 hour time system. For
example, 00012350 starts at one minute after midnight and
5.192 Group Repetition Interval (GRI) ends at 10 minutes before midnight. 07152000 starts at
07:15 hours and ends at 20:00 hours.
Deleted by Supplement 14.
Times of Operation can also be expressed in terms of
5.193 Additional Secondary Phase Factor (ASF) Sunrise (SR) and Sunset (SS). When a “Time of Operation”
is defined as starting at or ending at Sunrise, that time is
Deleted by Supplement 14. specified as “000R”. When a “Time of Operation” is
defined as starting at or ending at Sunset, that time is
5.194 Initial/Terminus Airport/Fix specified as “000S”. When a “Time of Operation” is
defined as starting at or ending at a certain number of
Definition/Description: The “Initial Fix” and the “Terminus hours/minutes before or after Sunrise or Sunset, those times
Fix” fields are used to define the departure airport or initial are specified as in the following examples:
fix and the destination airport or terminus fix of a preferred
route. 030R for 30 minutes before Sunrise or R030 for 30
minutes after Sunrise.
Source/Content: For preferred and preferential routes these 100R for 1 hour before Sunrise or R100 for 1 hour
fields will normally contain an airport identifier. For North after Sunrise.
America Routes for North Atlantic Traffic - Common 030S for 30 minutes before Sunset or S030 for 30
portion routes, these fields may contain NAVAID or minutes after Sunset.
waypoint identifiers. For North America routes for North 100S for 1 hour before Sunset or S100 for 1 hour after
Atlantic Traffic - Non-common portion routes, these fields Sunset
may contain airport, NAVAID or waypoint identifiers.
These fields will be entered on the first sequence of a route Of the three digits associated with “R” or “S,” the first
only, except when the route serves more than one airport, in is an expression of hours, the second and third an
which case the additional airports are shown on succeeding expression of minutes. 1 hour, 30 minutes would be
sequences. 130, 2 hours, 15 minutes would be 215, etc.
 ARINC SPECIFICATION 424 - Page 113

5.0 NAVIGATION DATA - FIELD DEFINITIONS

When multiple definitions are required to fully define the Note 1: Column 98 is reserved for future expansion of
“Time of Operation” for a given calendar week, these are the Name-Format-Indicator concept.
coded as second and subsequent “Time of Operation”
fields. Note 2: The “T” indicator will be used with all fixes
established in accordance with Chapter 7,
Examples: Section 7.2.6, Terminal Waypoints, in this
document.
A restriction valid on Mondays, Wednesdays and
Fridays only, 0700 to 1700, would require three “Time Used On: Enroute Waypoints, Airport and
of Operation” entries, one for 01 (Monday), one for 03 Heliport Terminal Waypoints
(Wednesday), one for 05 (Friday) and would be Length: 3 characters
expressed as 0107001700 0307001700 0507001700. Character Type: Alpha
A continuous restriction, starting on Monday at 0700
and ending on Friday at 1700 would require three
“Time of Operation” entries, one for Monday of 5.197 Datum Code (DATUM)
0107002359, one for Tuesday through Thursday of
2400002359 and one for Friday of 0500001700. Definition/Description: The “Datum Code” field defines
the Local Horizontal Reference Datum to which a
When the times to be defined go over midnight, the second geographical position, expressed in latitude and longitude,
four characters of time information are valid on the actual is associated.
ending day. For example, a “Time of Operation” of Monday
through Friday, 1700 to 0300 actually ends on Saturday and Source/Content: Local Horizontal Reference Datums will
would be shown as 1617000300, not 1517000300. be derived from official government documentation. The
“Datum Code” field will contain a three letter code
Used On: Enroute Airway Restriction Primary and corresponding to that government publication. A listing of
the following Continuation Records - valid three letter codes is contained in Attachment 2 to this
Airport/Heliport/Enroute Specification.
Communications, Restrictive Airspace,
Preferred Route, Enroute Airway Used On: VHF Navaid, NDB Navaid, Terminal
Restrictions and Controlled Airspace NDB, Enroute Waypoint, Airport, Fan
Length: 10 characters Marker, Heliport and GLS Transmitter
Character Type: Alpha/numeric Records
Length: 3 characters
5.196 Name Format Indicator (NAME IND) Character Type: Alpha
Examples: AGD, NAS, WGA
Definition/Description: The “Name Format Indicator”
field is used to describe the format of the “Waypoint
Name/Description” field (5.43). This field will be 5.198 Modulation (MODULN)
formatted according to the rules described in Chapter 7 of
this Specification, Waypoint Naming Conventions. Definition/Description: The “Modulation” field will design
the type of modulation for the frequency in the
Source/Content: Values for this field have no official “Communication Frequency” (5.103) field.
government source and are adjusted by input from the
following table. Code may not be used in combination Source/Content: The field contains the following
between columns. information:
Record Column Content
Description
96 97 98 Field
A Abeam Fix Content Description
B Bearing and Distance Fix
D Airport Name as Fix A Amplitude Modulated frequency
F FIR Fix F Frequency Modulated frequency
H NOTE 1 Phonetic Letter Name Fix
I Airport Ident as Fix
L Latitude/Longitude Fix
M Multiple Word Name Fix Used On: Enroute, Airport and Heliport
N Navaid Ident as Fix Communication Records
P Published Five - Letter - Name - Fix Length: 1 character
Q Published Name Fix, less than five Character Type: Alpha
letters
R Published Name Fix, more than five
letters
T Airport/Rwy Related Fix (Note 2)
U UIR Fix
O Localizer Marker with officially
published five - letter identifier
M Localizer Marker without officially
published five - letter identifier
ARINC SPECIFICATION 424 - Page 114

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.199 Signal Emission (SIG EM) SC = Seasonal Restriction. Record is used to close
an Airway or portion of an Airway on a
Definition/Description: High Frequency (HF) signals used seasonal basis.
in aeronautical communications can be the complete signal
or a portion of the signal, called a sideband. The “Signal NR = Note Restrictions. The record contains
Emission” field will designate for each HF Frequency what restrictions that do not fit the pattern of
emission is used. “formatted” information allowed by other
“Restriction Record Types.”
Source/Content: This field contains the following
information: Used On: Enroute Airway Restriction Records
Length: 2 characters
Note: The field is blank on records with frequencies that Character Type: Alpha
are not HF, see Section 5.104.
5.202 Exclusion Indicator (EXC IND)
Field
Content Description Definition/Description: The “Exclusion Indicator” field is
an indication of how the altitudes contained in the Cruising
3 Double Sideband (A3) Table record referenced by the Airway segment(s) are
A Single sideband, reduced carrier (A3A) restricted. This is an “all altitude” restriction, further
B Two Independent sidebands (A3B) defined by direction of flight. These codes will not be used
H Single sideband, full carrier (A3H) when certain altitudes remain available in a direction of
J Single sideband, suppressed carrier (A3J) flight.
L Lower (single) sideband, carrier unknown
U Upper (single) sideband, carrier unknown Source/Content: The content of the field will be one of the
codes from the following listing:
Used On: Enroute, Airport and Heliport “A” = All altitudes in both directions of flight are
Communications Records restricted. This effectively closes the airway in
Length: 1 character both direction of flight.
Character Type: Alpha/numeric
5.200 Remote Facility (REM FAC) “B” = All altitudes in the opposite direction in which
the Enroute Airway is coded are restricted.
Definition/Description: The “Remote Facility” field is used This effectively closes the airway in one
to define the Navaid or airports that a Remote direction of flight i.e., the opposite direction
Communications Outlet (RCO) will be transmitting through. from that in which the airway is coded.
Source/Content: Navaids or airports used as RCOs will be “F” = All altitudes in the direction in which the
derived from official government publications and the field Enroute Airway is coded are restricted. This
will contain the official 2, 3 or 4 character Navaid Identifier. effectively closes the airway in one direction
of flight i.e., the direction in which the airway
Used On: Enroute, Airport and Heliport is coded.
Communications Records.
Length: 4 characters (blank) = The restriction is not an “all altitude”
Character Type: Alpha/numeric restriction.
5.201 Restriction Record Type (REST TYPE)
Used On: Enroute Airway Restriction Records
Definition/Description: The “Restriction Record Type” Length: 1 character
field is used to define what type of a restriction is contained Character Type: Alpha
in the Enroute Airway Restriction Record in question.
Source/Content: The content of this field should be selected 5.203 Block Indicator (BLOCK IND)
from the following listing of possible codes:
Definition/Description: The “Block Indicator” field is used
AE = Altitude Exclusion. The record contains to specify that the altitudes that follow in the restriction
altitudes, normally available, that are record are either “block” of altitudes that are restricted (not
excluded from use for the Enroute Airway available for flight) or are individual altitudes that are
Segment. May be further restricted by “Time restricted.
of Operation” information.

TC = Cruising Table Replacement. The record Source/Content: The field will either be set to “B”
contains only a reference to a Cruising Table indicating an altitude block or “I” indicating individual
Identifier. That Cruise Table will be in force, altitudes. One or the other or both codes will appear in
replacing the Cruise Table Identifier in the restriction records that are not “Exclusive” restrictions (see
Enroute Airway segment records defined in Section 5.201).
the “Start Fix/End Fix” fields.
 ARINC SPECIFICATION 424 - Page 115

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Enroute Airway Restriction, Enroute Used On: VHF Navaid Limitation Continuation
Airway Restriction Continuation Records Records
Length: 1 character Length: 1 character
Character Type: Alpha Character Type: Alpha
Examples: (using multiple columns of the record)
5.206 Component Affected Indicator (COMP AFFTD
030B090 = all altitudes from 3000 feet to 9000 feet IND)
(inclusive) are not available
030I090 = the individual altitudes of 3000 feet and
9000 feet are not available Definition/Description: The VHF Navaid File contains
030I070B130 = the individual altitude of 3000 feet and navaids that have one or two components - azimuth and/or
all altitudes from 7000 feet to 13000 feet distance. Published limitations may apply to one or both of
(inclusive) are not available the components. The “Component Affected Indicator”
defines which component(s) are affected by the limitation.
5.204 ARC Radius (ARC RAD)

Definition/Description: The “ARC Radius” field is used to Source/Content: The field content will be entered as
define the radius of a precision turn. In Terminal indicated in the table based on official government
Procedures, this is the “Constant Radius To A Fix” Path and publications. When different limitations apply to different
Termination, for “RF” Leg. In Holding Patterns, this is the components or components pairs, this will result in multiple
turning radius, inbound to outbound leg, for RNP Holding. Component Affected Indicators for a single navaid to cover
The ARC Radius field is also used to specify the turn radius the complete limitation. In these cases, the Sequence
of RNP holding patterns included in SID, STAR, and Number (Section 5.12) will start again with one (01) with
Approach Records as HA, HF, and HM legs. each new Component Affected Indicator.
Source/Content: The content of the field will be derived
Content Component Description
from official source publications. It will be expressed in
nautical miles, tenths, hundredths and thousandths of a TACAN or VORTAC, TACAN azimuth
A
nautical mile, with the decimal point suppressed. A component only affected.
conversion to feet of the resolution in nautical miles is equal VORDME, or VORTAC, both azimuth and
B
to an accuracy of 6 feet. distance component affected.
VORDME or DME, distance component only
D
Used On: SID, STAR and Approach Records, affected.
Holding Pattern Records VORTAC or TACAN, TACAN azimuth and
M
Length: 6 characters distance component affected.
Character Type: Numeric TACAN or VORTAC, distance component
T
Examples: 246868, 460820, 691231 affected.
VOR, VORDME or VORDME, VOR azimuth
V
5.205 Navaid Limitation Code (NLC) component affected.
VORDME, VORTAC or TACAN, VOR and
Definition/Description: The “Navaid Limitation Codes” Z TACAN azimuth and distance component
field is used to define the type of limitation to be expected affected.
with a VHF Navaid.
Source/Content: The type of limitation will be derived from Used On: VHF Navaid Limitation Continuation
official government publications and entered using one of Records
the codes defined in the table. Length: 1 character
Character Type: Alpha
Content Limitation Description
Coverage, the limitations are expressed as
C
maximum reception reliability 5.207 Sector From/Sector To (SECTR)
Fluctuations, radial(s) are affected by course
F Definition/Description: The “Sector From/Sector To” field
fluctuations.
Roughness, signal roughness experienced in the defines sectorization applicable to the range limited sectors
G of VOR/DME, VORTAC or TACAN facilities, using the
sector(s) defined.
Unreliable in the sector(s), at the altitude(s), at the sector letters from the table. Each sector is described by two
N characters and is to be interpreted as “from” the first
distance(s) defined.
Restricted in the sector(s), at the altitude(s), at the character, clockwise “to” the second character.
R
distance(s) defined.
Unusable in the sector(s), at the altitude(s), at the
T Source/Content: Field content is derived through
distance(s) defined. interpretation of official government publication
Out of Tolerance in the sector(s), at the altitude(s), information which may be in a variety of formats.
U
at the distance(s) defined.
ARINC SPECIFICATION 424 - Page 116

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Sector Character From (degrees true) To (degrees true) Ditance

Distance
A 000 015 Limit –
Distance Limit –
B 015 030 Second Description of Content
Description First Three
C 030 045 Three
Digits
D 045 060 Digits
E 060 075
_ 040 000 Limitation valid out to
F 075 090
40NM from the facility.
G 090 105
Limitation valid beyond
H 105 120 + 040 000
40NM from the facility.
I 120 135
Limitation valid between
J 135 150 B 100 040
40NM and 100NM.
K 150 165
Blank 040 000 Limitation valid at 40NM
L 165 180
from the facility.
M 180 195
N 195 210
O 210 225 5.209 Altitude Limitation (ALT LIMIT)
P 225 240
Q 240 255 Definition/Description: The “Altitude Limitation” field is
R 255 270 used to define the altitude(s) at which the limitation applies.
S 270 285
T 285 300 Source/Content: “Altitude Limitations” are derived from
U 300 315 official government publications. The field will contain one
V 315 330 to two altitudes, expressed in hundreds of feet MSL. Used
W 330 345 together with the “Altitude Description” field, the altitudes
X 345 000 can be provided as indicated in the table of examples. The
field will be blank if there are no altitudes associated with
Used On: VHF Navaid Limitation Continuation the limitation.
Records
Length: 2 characters Used On: VHF Navaid Limitation Continuation
Character Type: Alpha Records
Examples: AB, TA, LW Length: 6 characters
Character Type: Alpha/numeric
Examples:
5.208 Distance Limitation (DIST LIMIT)
Altitude Altitude
Definition/Description: The “Distance Limitation” field is Limit -
used to define the distance(s) from the navaid at which the Altitude Limit - Description of
Description First Second Content
limitation applies. Three Three Digits
Digits
Source/Content: “Distance Limitations” are derived from
official government publications. The field will contain one - 040 000 Limitation valid
or two distances expressed in nautical miles from the at or below
facility. Used together with the “Distance Description” 4000'/FL040.
field, the distances can be provided as indicated in the table + 040 000 Limitation valid
of examples. The field will be blank if there are no distances at or above
associated with the limitation. 4000'/Fl040.
B 100 040 Limitation valid
Used On: VHF Navaid Limitation Continuation from 4000'/FL040
Records to 10000'/FL100.
Length: 6 characters Limitation valid
Character Type: Alpha/numeric blank 040 000 at 4000'/FL040.
Examples:
 ARINC SPECIFICATION 424 - Page 117

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.210 Sequence End Indicator (SEQ END) 5.212 Runway Gradient (RWY GRAD)

Definition/Description: The “Sequence End Indicator” field Definition/Description: The Runway Gradient field
is used to define the end of a set of sequences defining a indicates an overall gradient in percent, measured from the
given limitation to a given VHF Navaid Component or start of take-off roll end of the runway designated in the
Component pair. record. The gradient is expressed as a positive or negative
gradient; positive being an upward and negative being a
Source/Content: “Limitations” are derived from official downward gradient.
government publications. The field will contain the
character “E” in that sequence which is the end of a given Source/Content: The values will be derived from official
limitation. government source. The first position will be either a “+” or
a “-” sign indicating upward or downward gradient.
Used On: VHF Navaid Limitation Continuation Positions 2 through 5 indicate the gradient with the decimal
Records point suppressed. The Maximum Gradient that can be
Length: 1 character expressed in this field is (+9.000 or -9.000).
Character Type: Alpha
Used On: Runway Records
5.211 Required Navigation Performance (RNP) Length: 5 characters
Character Type: Alpha/numeric
Definition/Description: Required Navigation Examples: +0450, -0300
Performance (RNP) is a statement of the Navigation
Performance necessary for operation within a defined 5.213 Controlled Airspace Type (ARSP TYPE)
airspace in accordance with ICAO Annex 15 and/or State
published rules. Definition/Description: The “Controlled Airspace Type”
field is used to indicate the type of controlled airspace,
Source/Content: RNP values derived from official using codes from the table below.
government source will be used when available. They are
entered into the field in nautical miles (two digits) with a Source/Content: The airspace type should be derived from
zero or negative exponent (one digit). The contents can official government publications. The table below shows the
be: indicators used for the various types. For the USA, the
previous applied designations such as TCA are supplied for
When used on Enroute Airway segments, RNP ease of reference, they are longer officially published.
shall apply inbound to the fix when viewed in
increasing sequence number order. The RNP
Field Description
applies only to the airway leg on which it is
Content
specified. If no RNP values is coded on a
segment, there is not a database specified RNP A Class C Airspace (Was ARSA within the USA).
for that segment. C Control Area, ICAO Designation (CTA).
M Terminal Control Area, ICAO Designation (TMA or
When used on a SID, STAR and Approach TCA).
Procedure records, the RNP shall apply to the R Radar Zone or Radar Area (Was TRSA within the
segment on which it is coded. RNP will be coded USA).
on every segment where it is specified by source. T Class B Airspace (Was TCA with the USA).
Lack of a RNP value on a segment indicates no Z Class D Airspace within the USA, Control Zone,
source supplied RNP value was available for that ICAO Designation (CTR).
segment.

When used on Holding Patterns, the RNP applies Used On: Controlled Airspace Records
to the holding pattern as defined in the record. Length: 1 character
Character Type: Alpha
Note 1: The RNP concept will also be applied to defined
airspaces, in addition to the specific flight paths
as defined above. ARINC 424-13 addresses an 5.214 Controlled Airspace Center (ARSP CNTR)
“airspace record” that includes a reservation for
RNP until actual content can be defined. Definition/Description: The “Controlled Airspace Center”
field is used to define the navigation element upon which
Note 2: There are no provisions for “Vertical RNP” in the controlled airspace being defined is predicated, but not
ARINC 424 at this time. necessarily centered. Where the Airspace is not defined then
the “Region Identifier” should be used. In this case, the
Used On: Enroute Airways, Airport and Heliport Controlled Airspace Center will contain the ICAO
SID, STAR and Approach Route, Identification code for the Controlled Airspace to which the
Controlled Airspace and Holding data contained in the record relates.
Pattern Records
Length: 3 characters (see Content paragraph) Source/Content: The Controlled Airspace Center will be
Character Type: Numeric (see Content paragraph) determined during the construction of the records. As an
Examples: 990 (equal to 99.0NM), example the New York Class B Airspace (formerly TCA) is
120 (equal to 12.0NM), 013 centered on the JFK VOR, the LGA VOR and the Newark
(equal to 0.001NM)
ARINC SPECIFICATION 424 - Page 118

5.0 NAVIGATION DATA - FIELD DEFINITIONS

airport. The Controlled Airspace Center field could contain Source/Content: Airports lying within or below terminal
the Kennedy Airport identifier “KJFK” as the key for all controlled airspace will be determined through the use of
records describing the New York Class B Airspace. The official government publications describing the lateral limits
field may contain a Navaid, Enroute Waypoint or Airport of such airspace. The Controlled Airspace Airport/ICAO
Identifier. A “Region Identifier” content should be derived fields identify the airport for which terminal controlled
from official government source where the controlling airspace has been included in the Controlled Airspace
authority is published or from ICAO Document 7910, Section of the file. The Controlled Airspace Indicator field
Location Indicators. In cases where no official identifier is will contain one of the codes from the table below. If an
published that can be used as the “Airspace Center” where airport is not associated with any terminal controlled
the controlled airspace is used for more than one airport, the airspace of the types in this table, the Controlled Airspace
Region Identifier can be used. Indicator field will be blank. The Controlled Airspace
Airport/ICAO may be identical to or different than the
COMMENTARY record airport. Although Control Zones (CTR) are provided
as Controlled Airspace, no reference to them is made in this
It should be noted that during construction of a manner in the Airport Flight Planning Continuation Record.
Controlled Airspace Center, no published Navaid,
Enroute Waypoint, Airport Identifier or Region
Identifier may be found to be suitable. Data suppliers Field Description
may create a “center waypoint” for use in the “Airspace Content
Center” field in such cases. A The Airport is within or below the lateral
limits of Class C Airspace.
Used On: Controlled Airspace records C The Airport is within or below the lateral
Length: 5 characters limits of a CTA.
Character Type: Alpha/numeric M The Airport is within or below the lateral
Examples: OTR, FISHS, KJFK, EGTT limits of a TMA or TCA.
R The Airport is within or below the lateral
5.215 Controlled Airspace Classification (ARSP limits Radar Zone.
CLASS) T The Airport is within or below the lateral
limits of Class B Airspace.
Definition/Description: The “Controlled Airspace
Classification” field will contain an alpha character
indicating the published classification of the controlled Used On: Airport Flight Planning Continuation
airspace, when assigned. Records
Length: 1 character
Source/Content: Classification codes will be derived from Character Type: Alpha
official government sources. If source does not provide a
classification, the field will be blank. 5.218 Geographical Reference Table Identifier (GEO
REF TBL ID)
Used On: Controlled Airspace records
Length: 1 character Definition/Description: The “Geographical Reference
Character Type: Alpha Table Identifier” will be used to provide a unique
Examples: A through G identification for each Geographical Entity. As the
“Geographical Entity” field is a large field with no
5.216 Controlled Airspace Name (ARSP NAME) established content, this two character code will act as a
pseudo key for the record.
Definition/Description: The “Controlled Airspace Name”
field will contain the name of the controlled airspace when Source/Content: The content of this field will be determined
assigned. by the data supplier using the rules below.

Source/Content: Names will be derived from official Position One - The first letter or other significant letter
government sources. The name, if assigned, will be entered of the Geographical Entity.
in the first record only. If source does not assign a name, the Position Two - A numeric of 0 thru 9 for each multiple
field may be blank. of the character in position one.

Used On: Controlled Airspace records Used On: Geographical Reference Table records
Length: 30 characters Length: 2 characters
Character Type: Alpha/numeric Character Type: Alpha/numeric
Examples: DENVER CLASS B, OAKLAND Examples: Scandinavia S1
OCTA Southern United Kingdom S2
Baleric Islands B0
5.217 Controlled Airspace Indicator (CTLD ARSP IND)
5.219 Geographical Entity (GEO ENT)
Definition/Description: The “Controlled Airspace
Indicator” field is used to indicate if an airport is associated Definition/Description: The Geographical Reference Table
with controlled airspace of a terminal type such as a will be used to identify “Geographical Entities” not
Terminal Control Area (TMA or TCA) Radar Area or Class definable by other established encoding systems. For
B or C Airspace within the USA. established systems refer to Section 7 of this document.
 ARINC SPECIFICATION 424 - Page 119

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: The content of the field will be derived Note 1: When two routings have been defined between
from official government source documentation for end fixes/areas for the sole purpose of separating
preferred route systems of any kind. aircraft groups of use, the first column will
contain the code for the group that may use the
Used On: Geographical Reference Table Records routing and the second column will contain the
Length: 29 characters code for the group that must use the alternative
Character Type: Alpha/numeric routing. If there is no alternative routing for
aircraft group separation, the second column will
5.220 Preferred Route Use Indicator (ET IND) be blank.
Definition/Description: The “Preferred Route Use Used On: Preferred Route Records
Indicator” provides information on whether the route in Length: 2 characters
question is point-to-point and therefore usable for Character Type: Alpha
navigation, or area-to-area and usable only as advisory Examples: For a pair of routings established for
information which requires further processing. The field aircraft group separation between Single
will also provide information on whether or not RNAV Engine and Twin Engine, the Single
equipment is required to use the route. Engine would carry the code of ST and
the Twin Engine Route would be TS.
Source/Content: The content of this field will be
determined by the data supplier at the time the route is 5.222 GPS/FMS Indicator (GPS/FMS IND)
established. The two character field will be used to denote
both the definition of the route initial/terminus nature and Definition/Description: The “GPS/FMS Indicator” field
the RNAV equipment requirement. In position one, the field provides an indication of whether or not the responsible
will contain the alpha character “P” if the route is point-to- government agency has authorized the overlay of a
point or “A” if the route is area-to-area. In position two, the conventional, ground-based aid approach procedure with
field will contain the alpha character “R” if RNAV the use of a GPS sensor or if the procedure may be flown
equipment is required and the alpha character “N” if RNAV with FMS as the primary navigation equipment.
equipment is not required.
Source/Content: The Indicator will be selected from the
Used On: Preferred Route and Geographical table below.
Reference Table Records
Length: 2 characters Field
Character Type: Alpha Indicator Definition
Content
Procedure Not Authorized for GPS or 0
5.221 Aircraft Use Group (ACFT USE GP) FMS Overlay
Procedure Authorized for GPS Overlay,
Definition/Description: The “Aircraft Use Group” field primary Navaids operating and 1
provides information on what aircraft or groups of aircraft monitored
are permitted to use a certain route. Procedure Authorized for GPS Overlay,
primary Navaids installed, not 2
Source/Content: The raw information for this field will be monitored
derived from government sources and encoded according to Procedure Authorized for GPS Overlay,
the table below. The first column will contain the code valid 3
Procedure Title includes “GPS”
for the routing. See Note One for the second column Procedure Authorized for FMS Overlay 4
content.
Procedure Authorized for FMS and 5
GPS Overlay
Aircraft or Aircraft Group Field Field RNAV (GPS) Procedure, can be flown A
Content Content with SBAS (WAAS)
RNAV (GPS) Procedure, cannot be B
All Aircraft A flown with SBAS (WAAS)
All Aircraft, Cruise speed 250 kts or less C RNAV (GPS) Procedure, use of SBAS
Non-Jet and Turbo Prop D C
(WAAS) not specified
Multi-Engine Props Only E
Stand Alone GPS Procedure P
Jets and Turbo Props/Special, Cruise Speed 190 kts F
or greater
Procedure Overlay Authorization U
Helicopter Only H
unspecified
Jet Power J See
Turbo-Prop/Special, Cruise Speed 190 kts or greater M Note 1 Note: RNAV (GPS) is part of the new ICAO Procedure
Non-Jet, Non-Turbo Prop N naming convention. WAAS is the only SBAS
Non-Jet, Cruise speed 190 kts or greater P system approved at this time.
Non-Jet, Cruise speed 189 kts or less Q
Aircraft as defined in a Notes Continuation Record R Used On: Airport and Heliport Approach
Single Engine S Procedure Records
Twin Engine T Length: 1 character
Character Type: Alpha/numeric
ARINC SPECIFICATION 424 – Page 120

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.223 Operation Type (OPS TYPE) Source/Content: The values will be derived from official
government source.
Definition/Description: The “Operation Type” field
contains information on the type of final approach Used On: Path Point Record
segment. Length: 4 characters
Character Type: Numeric
Source/Content: A number from 00 to 15 derived from Examples: 0275 (is equal to 2.75°), 1015 (is equal
the type of approach to which the Path Point record is to to 10.15°), 0300 (is equal to 3.00°)
be associated. A straight-in-procedure is indicated by 00.
All other values are reserved for future definition.

Used On: Path Point Record

Length: 2 characters
Character Type: Numeric
5.224 Route Indicator (RTE IND)
Definition/Description: The “Route Indicator” field is a
single alpha character used to differentiate between
multiple final approach segments to the same runway or
helipad.

Source/Content: A code of “A” through “Z,” (omitting

“I” and “O”).

Note: This single character is consistent with the

“Multiple Approach Indicator” included as the
fifth character of an Approach Procedure
Identifier.
Used On: Path Point Record
Length: 1 character
Character Type: Alpha Figure 5-14 Precision Approach Path Points

5.225 Ellipsoidal Height 5.227 Orthometric Height (ORTH HGT)

Definition/Description: The “Ellipsoidal Height” field is Definition/Description: The “Orthometric Height” field is
the height of a surveyed point in reference to the WGS-84 the height of a surveyed point in reference to Mean Sea
ellipsoid. Level (MSL).
Source/Content: The Ellipsoidal Height will be derived Source/Content: The Orthometric Height will be derived
from official government source and entered with a from official government source and entered with a
resolution of a tenth of a meter, with the decimal point resolution of a tenth a meter, with the decimal point
suppressed. When the height is below the ellipsoid, the suppressed. When the height is below MSL, the first
first position will carry a minus (-) sign, otherwise this position will carry a minus (-) sign, otherwise this position
position will be a plus (+) sign. will be a plus (+) sign.
Used On: Path Point Record Used On: Path Point Record
Length: 6 characters Length: 6 characters
Character Type: Alpha/numeric Character Type: Alpha/numeric
Examples: +00356, +00051, +015 -00022, Examples: +00356, +00051, +01566, -00022,
-01566 -01566
5.226 Glide Path Angle (GPA) 5.228 Course Width At Threshold (CRS WDTH)
Definition/Description: The “Glide Path Angle” field is Definition/Description: The “Course Width At
an angle, expressed in degrees, tenths and hundredths of Threshold” field defines the width of the lateral course at
degrees, measured at the Flight Path Control Point (FPCP) the Landing Threshold Point (LTP). This width, in
of those approach procedures that require the coding of a conjunction with the location of the Flight Path Alignment
Path Point record. It establishes the intended descent Point (FPAP) defines the sensitivity of the lateral
gradient for the final approach flight path. For an deviations throughout the approach.
illustration of the GPA and related points, see
Figure 5-13.
 ARINC SPECIFICATION 424 – Page 121

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: The width will be derived from official

government sources and entered in meters in the hundreds, Used On: Flight Planning Arrival/Departure Data
tens, units, tenths and hundredths format with the decimal Records
point suppressed. The value requires a data resolution of Length: 1 character
0.25 meters and acceptable values will end in 00, 25, 50, Character Type: Alpha
and 75. When the procedure is to a helicopter alighting
point, the value is 38 meters. 5.231 Along Track Distance (ATD)

Used On: Path Point Records Definition/Description: The “Along Track Distance” field
Length: 5 characters used on Flight Planning Arrival/Departure Data Records
Character Type: Numeric is the total distance for a given transition, from the initial
Examples: 08025, 14375, 03800 fix to the ending fix in the transition. A single occurrence
of a Flight Planning Arrival/Departure Data record can
5.229 Final Approach Segment Data CRC Remainder contain up to three Along Track Distance fields, one for
(FAS CRC) each of the transition types that can make up a single
terminal route in the Primary Record and up to four
Definition/Description: The “Final Approach Segment possible intermediate fix points in each Continuation
Data CRC Remainder” field is an eight (8) character Record. Collectively, the values equal the along track
hexadecimal representation of the 32-bit CRC value distance from the first fix in the first transition to the last
provided by the source for the information contained in fix in the last transition.
the aeronautical data fields being monitored for integrity.
The value is calculated by a specific mathematical Source/Content: The along track distances will be
algorithm, which is both machine and man processible. calculated by data suppliers using coded terminal
procedures or uncoded terminal procedures derived from
Source/Content: The CRC calculation information is official government source and expressed in nautical miles
available as Chapter Six of this Specification. with a 1NM resolution.
Used On: Path Point Record Used On: Flight Planning Arrival /Departure Data
Length: 8 characters Records
Character Type: Alpha/numeric Length: 3 characters
Examples: 243BC649, A6934B72 Character Type: Numeric
5.230 Procedure Type (PROC TYPE) 5.232 Number of Engines Restriction (NOE)
Definition/Description: The “Procedure Type” field used Definition/Description: The “Number of Engines
on Flight Planning Arrival/Departure Data Record is a Restriction” field used on Flight Planning
single character code indication the type of procedure in Arrival/Departure Data Records is derived from
the record, such as Arrival, Standard Instrument Arrival government source and is included whenever a given
Route, Approach. procedure, normally departure, is restricted to, or
designed for, aircraft with a specific number of engines.
Source/Content: The Procedure Type code must be one
of the following codes: Source/Content: The number of engines will be taken
from official government source. The field will contain
Procedure the character Y for each engine configuration position, 1,
Procedure Type Description 2, 3 and 4, for which the procedure is authorized. Non-
Type Code
Arrival Procedure, Available in A authorized configuration positions will contain the
Database character N.
Arrival Procedure, Not Available in B
Database Used On: Flight Planning Arrival /Departure Data
Departure Procedure, Available in C Records
Database Length: 4 characters
Departure Procedure, Not Available in D Character Type: Alpha
Database Examples: YYYY (1, 2 3 or 4 Engine aircraft may
Standard Terminal Arrival Route E use procedure)
(STAR), Available in Database NNYY (3 and 4 Engine aircraft may use
Standard Terminal Arrival Route F procedure)
(STAR), Not Available in Database
Standard Instrument Departure (SID), G 5.233 Turboprop/Jet Indicator (TURBO)
Available in Database
Standard Instrument Departure (SID), H Definition/Description: The “Turboprop/Jet Indicator”
Not Available in Database field used on Flight Planning Arrival/Departure Data
Vector SID, Available in Database I Records is derived from government source and is
Vector SID, Not Available in Database J included whenever a given procedure, normally departure,
Approach Procedure, Available in K is restricted to, or designed for, aircraft with a specific
Database kind of engines.
Approach Procedure, Not Available in L
Database
ARINC SPECIFICATION 424 – Page 122

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: The indication of Turboprop, Jet or Both 5.236 ATC Identifier (ATC ID)
on the use restriction of given procedure will be taken
from official government source. The field will indicate Definition/Description: The “ATC Identifier” field used
the use restriction with a character from the table below. on Flight Planning Arrival/Departure Data Records is the
indication of the officially published procedure
Field designation which is required for Flight Planning.
Aircraft or Aircraft Group
Content
Source/Content: The ATC Identifier will be derived from
All Aircraft A official government source. This seven character field is
Jets and Turbo Props B required in addition to the six character identifier, the
All Aircraft, Cruise speed 250 kts or less C former is used in Flight Planning, the latter in accessing
Non-jet and Turbo Prop D the database.
Multi-Engine Props Only E
Jets J Used On: Flight Planning Arrival /Departure Data
Non-Jet, Non-Turbo Prop N Records
Turbo Props P Length: 7 characters
Character Type: Alpha/numeric
Used On: Flight Planning Arrival /Departure Data
Records 5.237 Procedure Description (PROC DESC)
Length: 1 character
Character Type: Alpha Definition/Description: The “Procedure Description”
field used on Flight Planning Arrival/Departure Data
5.234 RNAV Flag (RNAV) Records is the textual representation of the procedure
name.
Definition/Description: The “RNAV Flag” field used on
Flight Planning Arrival/Departure Data Records is derived Source/Content: The Procedure Description will be
from government source and is included whenever a given derived from official government source. It will assist in
procedure included in the record is restricted to, or matching flight plan content to charted procedures.
designed for, aircraft capable of flying RNAV Procedures.
Used On: Flight Planning Arrival /Departure Data
Source/Content: The indication of RNAV, Yes or No, on Records
a given procedure will be taken from official government Length: 15 characters
source. The field will indicate Y for “Yes,” the procedure Character Type: Alpha/numeric
is an RNAV procedure or N for “No,” the procedure is
not RNAV. 5.238 Leg Type Code (LTC)
Used On: Flight Planning Arrival /Departure Data Definition/Description: The “Leg Type Code” field used
Records on Flight Planning Arrival/Departure Data Records is a
Length: 1 character simplification of the Path Terminator concept. It will
Character Type: Alpha provide the information on the path between intermediate
waypoints as straight or curved and provide an indication
5.235 ATC Weight Category (ATC WC) of the change in direction of flight, expressed as left or
right, at an intermediate waypoint.
Definition/Description: The “ATC Weight Category”
field used on Flight Planning Arrival/Departure Data Source/Content: The Leg Type Code will be derived from
Records is derived from government source and is official government source. In this two character field, the
included whenever a given procedure included in the first position will indicate with the character S, straight
record is restricted to, or designed for, a specific aircraft line point to point and with the character C, curved line
weight grouping. flight track. The second position will be used as a turn
indication, L for Left and R for Right when there is a turn
Source/Content: The indication of Heavy, Medium or requirement at an intermediate waypoint.
Light aircraft on a given procedure will be taken from
official government source. The field will be derived from Used On: Flight Planning Arrival /Departure Data
that source to indicate: Records
Length: 2 characters
H for Heavy, all aircraft types of 136,000kg (300000LB) Character Type: Alpha
or more.
5.239 Reporting Code (RPT)
M for Medium, aircraft types less than 136,000kg
(300,000LB) and more than 7,000kg (155,000LB). Definition/Description: The “Reporting Code” field used
on Flight Planning Arrival/Departure Data Records is a
L for Light, aircraft types of 7,000kg (155,000LB) or less. simplification of the Waypoint Description concept. It will
provide the information on intermediate waypoints as
Used On: Flight Planning Arrival /Departure Data either Position Report Required (Compulsory Report) or
Records Position Report Not Required (On-Request Report).
Length: 1 character
Character Type: Alpha
 ARINC SPECIFICATION 424 – Page 123

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Source/Content: The Reporting Code will be derived Source Content: The field will contain a coded category
from official government source. In this single character from the following table:
field, the code “C” will indicate Position Report Required
and the code “X” Position Report Not Required. Content Procedure Category
Used On: Flight Planning Arrival /Departure Data LAAS Local Area Differential Augmentation
Records System
Length: 1 character WAAS Wide Area Differential Augmentation
Character Type: Alpha System
FMS Flight Management System
5.240 Altitude (ALT) GPS Global Positioning System, no
Augmentation
Definition/Description: The “Altitude” field used on VDME VORDME, VORTAC
Flight Planning Arrival/Departure Data Records is a CIRC Circle-To-Land
simplification of the altitude concept used in the full
procedure records. It will provide an altitude indication in Used On: Airport and Heliport
hundreds of feet, no AGL, MSL, FL etc indication SID/STAR/Approach Procedure
provided. Continuation Records
Length: 4 characters
Source/Content: The Altitude will be derived from Character Type: Alpha
official government source and reduced to this flight
planning resolution requirement. 5.243 GLS Station Identifier
Used On: Flight Planning Arrival /Departure Data Definition/Description: The “GLS Identifier” field
Records defines the identification code for retrieval of such a
Length: 3 characters transmitter from a database. This is not a transmitted
Character Type: Numeric identifier.
Examples: FL100 = 100
10000 feet = 100 Source/Content: The content of this field will be the
03500 feet = 035 Airport or Heliport ICAO Location Identifier Code at
which the transmitter is installed.
5.241 Fix Related Transition Code (FRT Code)
Used On: GLS Records
Definition/Description: The “Fix Related Transition Length: 4 characters max
Code” is used on Flight Planning Arrival/Departure Data Character Type: Alpha/numeric
Continuation Records containing Intermediate Fix
information and provides an indication, through use of the 5.244 GLS Channel
standard coding practices of separating the procedure into
transitions, as to where in the procedure the intermediate Definition/Description: The “GNSS Channel Number”
fix is located. field identifies the channel that will be decoded to identify
the augmentation system used.
Source/Content: The field will contain a code an meaning
as indicated in the table below. Source/Content: The Channel Number is derived from
official government sources. It consists of 5 numeric
Intermediate Fix is Field characters in the range 20001 to 99999 (numbers less then
Located in Transition Type Content 20000 are reserved for ILS and MLS). Channel Numbers
between 20001 and 39999 are reserved for GBAS (and
Fix Located in SID Runway Transition 1 SBAS if applicable) and 40000 to 99999 are reserved for
Fix Located in SID Common Portion 2 SBAS.
Fix Located in SID Enroute Transition 3
Fix Located in STAR Enroute Transition 4 Used On: GLS and Path Point Continuation
Fix Located in STAR Common Portion 5 Records
Fix Located in STAR Runway Transition 6 Length: 5 character
Character Type: Numeric
Used On: Flight Planning Arrival/Departure Data Examples: 20010, 56234
Records
Length: 1 character
Character Type: Numeric 5.245 Service Volume Radius
5.242 Procedure Category (PROC CAT) Definition/Description: The service volume radius
identifies the radius of the service volume around the
Definition/Description: The Airport and Heliport transmitter in Nautical miles.
SID/STAR/Approach Procedure Route Type supports the
“All Sensor RNAV” Approach procedure. This kind of Source/Content: The value for this field will be derived
approach will have multiple sets of weather minimums from official government sources. If no source is
(DH and NDA) associated with it. This field identifies the provided, the default value will be blanked.
Procedure Categories for which these minimums apply.
ARINC SPECIFICATION 424 – Page 124

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: GLS Record surface runway at the airport, the length of which is
Length: 2 characters indicated in the Longest Runway field.
Character Type Numeric
Examples: 05, 19 Source/Content: The content will be selected from the
table below.
5.246 TDMA Slots
Field Description
Definition/Description: The TDMA identifies the time Content
slot(s) in which the ground station transmits the related H Hard Surface, for example, asphalt or
approach. The high precision time source available concrete
through GPS permits utilization of Time division S Soft Surface, for example, gravel, grass or
multiplexing or TDMA (Time Division Multiple Access), soil
allowing multiple ground stations to share a common W Water Runway
frequency by dividing it into eight time slots. An U Undefined, surface material not provided in
individual station may broadcast in one or more of eight source
slots.
Used On: Airport Records
Source/Content: The value for this field will be derived Length: 1 character
from official government sources. The range is 01 to FF. Character Type: Alpha
If no source is provided, the default value will be blank.
5.250 Alternate Record Type (ART)
Used On: GLS Record
Length: 2 characters Definition/Description: The “Alternate Record Type”
Character Type: Alpha/numeric field identifiers the record as being applicable to the
Examples A2, 01, FF departure airport (take-off alternate), destination airport
(arrival alternate) or a fix along the route (enroute
5.247 Station Type alternate).
Definition/Description: The station type identifies the type Source/Content: The “Alternate Record Type” will be
of the differential ground station. The first character will selected from the following table:
be L for LAAS/GLS ground station, C for SCAT-1
station. The second and third character will be blank for
the moment. They will indicate the interoperability Content Description
standard to which the station conforms. AA The Airport identifier in Columns 7 through 11
of the Primary Record are the identifier of the
Source/Content: The value for this field will be derived Arrival Airport.
from official government sources. If LAAS/GLS or DA The Airport identifier in Columns 7 through 11
SCAT-1 is not specified in source, the default value will of the Primary Record are the identifier of the
be blank. Departure Airport.
EA The end fix of a Company Route is identified in
Used on: GLS Record Columns 7 through 15 of the Primary Record.
Length: 3 characters
Character Type: Alpha/numeric Used On: Alternate Records
Examples: L, C Length: 2 characters
Character Type: Alpha
5.248 Station Elevation WGS84
5.251 Distance To Alternate (DTA)
Description/Definition: This field identifies the WGS84
elevation of the GLS ground station described in the Definition/Description: The “Distance To Alternate” field
record. defines either the direct (geodesic) distance from the
Destination Airport or Fix to the Alternate Airport or the
Source/Content: The value for this field will be derived along track distance of an alternate Company Route.
from official government sources or entered into this field
in feet with respect to the WGS84 ellipsoid. When Source/Content: When the Alternate Type field carries
elevation is below the WGS 84 ellipsoid, the first column the character “A,” the Distance to Alternate field carries
of the field contains a minus (-) sign. the straight line (geodesic) distance in nautical miles
between the Destination Airport or Fix and the Alternate
Used on: GLS Record Airport as listed in Alternate Identifier fields. When the
Length: 5 characters Alternate Type field carries the character “C,” the
Character Type: Alpha/numeric Distance to Alternate field carries the cumulative along
Examples: 00530, -0140 track distance for the Alternate Company Route as listed
in the Alternate Identifier fields.
5.249 Longest Runway Surface Code (LRSC)
Used On: Alternate Records
Definition/Description: The “Longest Runway Surface Length: 3 characters max.
Code” field is used to define whether or not there is a hard Character Type: Numeric
 ARINC SPECIFICATION 424 – Page 125

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.252 Alternate Type (ALT TYPE) Used On: Path Point Records
Length: 2 characters
Definition/Description: The “Alternate Type” field is an Character Type: Numeric
information processing indicator. The Alternate
Destination can be defined as an airport or an airport and 5.256 Reference Path Data Selector (REF PDS)
route to an airport. This field defines that an alternate
airport or, an company route is defined in the Alternate Definition/Description: The “Reference Path Data
Identifier fields. Selector” field enables the automatic tuning of a
procedure by Ground Based Augmentation Systems
Source/Content: The field will contain either the (GBAS) avionics.
character “A” when an Airport is provided or the
character “C” when a Company Route is provided. Source/Content: A number from 00 to 48, the exact
definition of which is currently under development by
Used On: Alternate Records ICAO GBAS SARPS working groups.
Length: 1 character
Character Type: Alpha Used On: Path Point Records
Length: 2 characters
5.253 Primary and Additional Alternate Identifier Character Type: Numeric
(ALT IDENT)
5.257 Reference Path Identifier (REF ID)
Definition/Description: The Primary Alternate Identifier
and the Additional Alternate Identifiers (two through five) Definition/Description: The “Reference Path Identifier”
uniquely identify either an Alternate Airport or an field is used to provide an identifier that can be used to
Alternate Company Route. The determination of whether confirm selection of the correct approach procedure.
the content is an Airport Identifier or a Company Route
Identifier is accomplished through the Alternate Type Source/Content: The content will be derived from official
field. government sources and analogous to the Morse code
identifier on existing ILS approach Procedures.
Source/Content: The content of this field is determined
by the customer. (Editor comment: See Section 5.243, GLS Station
Identifier.)
Used On: Alternate Records
Length: 10 characters max Used On: Path Point Records
Character Type: Alpha/numeric Length: 4 characters
Character Type: Alpha/numeric
5.254 Fixed Radius Transition Indicator (FIXED RAD Examples: GDCA, SJK2
IND)
5.258 Approach Performance Designator (APD)
Definition/Description: Indicates that a specific turn
radius from the inbound course to the outbound course is Definition/Description: The “Approach Performance
required by the airspace controlling agency. Designator” field is used to indicate the type or category
of approach.
Source/Content: When a fix radius turn is required a 3
digit numeric value will be entered in this field Source/Content: A number between 0 and 7. The
representing the radius of the turn to 1 decimal place content will be derived from official government source
(tenths, decimal point suppressed) in nautical miles. A documents. The ICAO GBAS SARPS working groups
blank entry in this field indicates that no fixed radius will provide the complete assignment.
transition is required.
Used On: Path Point Records
Used On: Enroute Airway Records Length: 1 character
Length: 3 characters Character Type: Alpha
Character Type: Numeric Example: 1 (Category I Approach)
Examples: 225=22.5nm, 150=15.0 nm
5.259 Length Offset (OFFSET)
5.255 SBAS Service Provider Identifier (SBAS ID) Definition/Description: The “Length Offset” field is
the distance from the stop end of the runway (SER) to the
Definition/Description: The “SBAS Service Provider FPAP. This distance defines the location where lateral
Identifier” field is used to associate the approach sensitivity changes to the missed approach sensitivity. If
procedure to a particular satellite based approach system the FPAP is located at the designated center of the
service provider. opposite runway end, the distance is zero.
Source/Content: A number from 00 to 15, the exact Source/Content: A value, expressed in meters, derived
definition of which is currently under development by from official government sources (Explanation and details
ICAO SBAS SARPS working groups. will appear in appropriate FAA and ICAO documents).
The actual resolution is 8 meters.
ARINC SPECIFICATION 424 – Page 126

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Used On: Path Point Records Used On: Path Point Continuation Records
Length: 4 characters Length: 10 Characters
Character Type: Numeric Character Type: Alpha/numeric
Examples: 0000, 0432 Examples: GLS, LPV, APV-II

5.260 Terminal Procedure Flight Planning Leg 5.263 HAL

Distance (LEG DIST)
Definition/Description: The Horizontal Alert Limit (HAL)
is the radius of a circle in the horizontal plane (the local
Definition/Description: The Terminal Procedure Flight plane tangent to the WGS-84 ellipsoid), with its center
Planning Leg distance is the along track distance required being at the true position, which describes the region
to complete any given leg. It is used to determine a which is required to contain the indicated horizontal
cumulative track distance for a given terminal procedure position with the required probability for a particular
for flight planning purposes, from the beginning of the navigation mode assuming the probability of a GPS
take-off or arrival point to the termination point of the satellite integrity failure being included in the position
procedure. solution is less than or equal to 10-4 per hour.
Source/Content: The values will be determined during Source/Content: A value, expressed in meters to a
route definition of the procedure records. The content is resolution of tenths of meters with the decimal point
controlled through requirements of the Path and suppressed, derived from official government sources.
Termination and coding rules in force with the data
supplier. The values are expressed in nautical miles and Used On: Path Point Records
tenths of nautical miles, with the decimal point Length: 3 Characters
suppressed. Character Type: Numeric
Examples: 400, 200
Used On: Airport and Heliport SID, STAR and
Approach Procedure Flight Planning 5.264 VAL
Continuation Records
Length: 4 characters Definition/Description: The Vertical Alert Limit (VAL) is
Character Type: Numeric half the length of a segment on the vertical axis
Examples: 0176, 0822, 0208 0016, 0100 (perpendicular to the horizontal plane of WGS-84
ellipsoid), with its center being at the true position, which
5.261 Speed Limit Description (SLD) describes the region which is required to contain the
indicated vertical position with a probability of 1-10-7 per
Definition/Description: The “Speed Limit Description” approach, assuming the probability of a GPS satellite
field will designate whether the speed limit coded at a fix integrity failure being included in the position solution is
in a terminal procedure description is a mandatory, less than or equal to 10-4 per hour.
minimum or maximum speed.
Source/Content: A value, expressed in meters to a
Source/Content: The content will be as defined in the resolution of tenths of meters with the decimal point
table below. suppressed, derived from official government sources.
Field Entry Description Used On: Path Point Records
Value Length: 3 Characters
@ (blank) Mandatory Speed, Cross Fix AT speed Character Type: Numeric
specified in Speed Limit Examples: 120, 500
+ (plus) Minimum Speed, Cross Fix AT or
ABOVE speed specified in Speed Limit 5.265 Path Point TCH
- (minus) Maximum Speed, Cross Fix AT or
BELOW speed specified in Speed Limit Definition/Description: The Path Point TCH is the height
above the runway threshold (LTP) or the helicopter
Used On: Airport/Heliport alighting point. It is the same as the TCH defined in
SID/STAR/Approach Records Section 5.67, but has greater resolution due to the required
Length: 1 character precision.
Character Type: Alpha
Source/Content: The value is derived from official
5.262 Approach Type Identifier (ATI) government sources. The value may be expressed in feet
to a resolution of tenths of feet, decimal point suppressed
Definition/Description: Identifies the approach types or expressed in meters to a resolution of hundredths of
published on a given approach procedure which require meters, decimal point suppressed. Whether or the value is
path points. in feet or meters can be determined from the TCH Units
Indicator.
Source/Content: Up to 10 characters representing the
literal name of an approach with vertical guidance Used On: Path Point Records
requiring path points, Horizontal Alert Limit (HAL) and Length: 6 characters
Vertical Alert Limit (VAL). The name is derived from Character Type: Numeric
government source material. Examples: 566777, 356799
 ARINC SPECIFICATION 424 – Page 127

5.0 NAVIGATION DATA - FIELD DEFINITIONS

5.266 TCH Units Indicator Used On: Path Point Continuation Records
Length: 3 Characters
Definition/Description: The “TCH Units Indicator” field Character Type: Numeric
is used in Path Point Records to define the units, Feet or Examples: 003, 013, 103, 310, 333
Meters for the Path Point TCH. This element is included
in the “CRC Wrap” a possible metric source value cannot 5.270 TCH Value Indicator (TCHVI)
be converted to feet.
Definition/Description: The “TCH Value Indicator” field
Source/Content: The field will contain the character “F” will define which TCH value is provided in the runway
if the Path Point TCH is provided in source record.
documentation in feet or the character “M” if that value is
provided in meters. Source/Content: The field will contain a value from the
following table:
Used On: Path Point Records
Length: 1 character Field Description
Character Type: Alpha Content
I TCH Provided in Runway Record is
5.267 High Precision Latitude (HPLAT) that of the ILS or MLS Glide Slope
TCH Provided in Runway Record is
Definition/Description: The “High Precision Latitude” R that of an RNAV procedure to the
field contains the latitude of the navigation feature runway
identified in the record. TCH Provided in the Runway Record
V
is that of the VGSI for the runway
Source/Content: The content of field is an expansion of TCH Provided in the Runway Record
the latitude defined in Section 5.36 to include degrees, D
is the default value of 50 feet.
minutes, tenths, hundredths, thousandths and tenths of
thousandths of seconds to accommodate the high Used On: Runway Records
precision resolution of 0.0005 arc seconds. Length: 1 character
Character Type: Alpha
Used On: Path Point Records
Length: 11 characters 5.271 Procedure Turn (PROC TURN)
Character Type: Alpha/numeric
Example: N3028422400 Definition/Description: The “TAA Procedure Turn” field
is used to indicate whether or a course reversal is
5.268 High Precision Longitude (HPLONG) necessary when flying within a particular TAA Area.
Definition/Description: The “High Precision Longitude” Source/Content: Official government source will carry an
field contains the latitude of the navigation feature indication when the course reversal is not necessary.
identified in the record. Generally, that indication is “NOPT”. Otherwise, the
execution of a course reversal is expected. When the
Source/Content: The content of field is an expansion of course reversal is not necessary, this field will carry the
the latitude defined in Section 5.36 to include degrees, alpha characters NOPT. When the course reversal is
minutes, tenths, hundredths, thousandths and tenths of necessary, the field will be blank. The indication is
thousandths of seconds to accommodate the high provided once for a given TAA Sector Identifier.
precision resolution of 0.0005 arc seconds.
Used on: Airport or Heliport TAA Primary
Used On: Path Point Records Record
Length: 12 characters Length: 4 characters
Character Type: Alpha/numeric Character Type: Alpha
Example: W081420301000
5.272 TAA Sector Identifier
5.269 Helicopter Procedure Course (HPC)
Definition/Description: The “TAA Sector Identifier”
Definition/Description: The “Helicopter Procedure contains an indication as to which sector data is contained
Course” field is used on Path Point Continuation Records in the record.
to define the final approach course of procedures designed
to helipads and points in space. Source/Content: Airport and Heliport Terminal Area
Altitudes (TAA) are published for each Initial Approach
Source/Content: The field will contain the full degree Fix (IAF) for RNAV and GPS Approach procedures. The
final approach course of a procedure designed to a helipad field identifies for which sector the data applies. The
or point in space and be derived from official government content is derived from official government source and
source. It will be used in conjunction with the Approach entered as indicated in the table below. The terminology
Procedure Identifier and Runway/Helipad Identifier data “left” and “right” is in reference to the final approach
in the Path Point Primary record to uniquely identify an course, i.e., left of final or right of final, regardless of the
approach procedure. magnetic alignment of the procedure.
ARINC SPECIFICATION 424 – Page 128

5.0 NAVIGATION DATA - FIELD DEFINITIONS

Field Content Sector Identifier Description

C Straight-In Area or Center Sector
L Left Base Area
T Right Base Area

Used On: Airport and Heliport TAA Primary

Records
Length: 1 character
Character Type: Alpha
5.273 TAA IAF Waypoint
Definition/Description: The “TAA IAF Waypoint” field
contains the identifier of the Initial Approach Fix (IAF)
associated with a given Terminal Area Altitude sector.
There may be one, two or three such IAF waypoints
defined for a single approach procedure. The TAA IAF
Waypoint identified in the TAA Sector with the identifier
of “C” (Section 5.272) is the fix to which all sector
bearing information for the procedure TAA is defined.
The TAA IAF Waypoint in the individual TAA Sector
records is the fix from which radius distances are defined.

Source/Content: The field contains the official identifier

of the waypoint for which the TAA Sector is defined.
They will be derived from official government sources.

Used On: Airport and Heliport TAA Records

Length: 5 character max
Character Type: Alpha/numeric

5.274 TAA Sector Radius

Definition/Description: The “Sector Radius” field in TAA

records defines the start and end distances that define a
TAA area. They are referenced to the TAA IAF Waypoint
defined in that record. As TAA information is used
towards that waypoint, the radius information is provided
towards that waypoint. They enclose the sector defined in
the record. The values are inclusive.

Source/Content: The Sector Radius information will be

derived from official government source. Each TAA
sector is made up of the start of sector radius and the end
of sector radius. The values are provided in nautical miles.
The first three digits define the radius for start of the
sector, the second three digits the end of the sector, when
flying towards the IAF Waypoint.
Used On: Airport and Heliport TAA Primary
Records
Length: 4 characters
Character Type: Numeric
Examples: 3011, a Sector that starts at 30
nautical miles to the IAF Waypoint
and ends at 11 nautical miles to the
IAF Waypoint.
0500, a Sector that starts at 5
nautical miles to the IAF Waypoints
and ends at that IAF Waypoint
 ARINC SPECIFICATION 424 - Page 129
6.0 ENCODING STANDARDS

6.1 General
This chapter sets forth the encoding standards to be employed for ARINC 424 and other master user data files. The data will
be encoded with ASCII characters.
6.2 Header Records

There will be at least one 132-character header record for each data file. The header records contain information to
uniquely identify each data file. Header record fields are considered required unless specified otherwise. Header records
are identified by HDR in columns 1 through 3 of the record.
6.2.1 Header Record 1

Column Field Name Field Reference

Length
1 thru 3 Header Ident 3 Contains “HDR”
4 thru 5 Header Number 2 Contains decimal 01 to indicate this is the first Header Record.
6 thru 20 File Name 15 Contains the file name.
21 thru 23 Version Number 3 Contains 3 decimal numbers to uniquely identify revision of this file.
Initially set to 001, but will be incremented if the file is created more
than once in the same cycle.
24 Production/Test Flag 1 Contains “P” if this is a production data file. Contains “T” if this is a
file created for test purposes.
25 thru 28 Record Length 4 Contains the decimal number 0132, i.e., the number of characters in
each data record.
29 thru 35 Record Count 7 Contains the decimal count of the number of data records in the file.
36 thru 39 Cycle Date 4 Contains Cycle Date (5.32)
40 thru 41 Blank (spacing) 2 Contains blanks.
42 thru 52 Creation Date 11 Contains the date when the file was created. Format is DD-MMM-
YYYY. Where DD is the two-digit decimal day of month, MMM is
a three-character month abbreviation, and YYYY is the four-digit
decimal year. (Example: 12-APR-2002)
53 thru 60 Creation Time 8 Contains the UTC time when the file was created. The format is two
decimal digits each for hours, minutes, and seconds, separated by
colons. (Example: 13:12:02 = 1:12:02 p.m.)
61 Blank (spacing) 1 Contains blank.
62 thru 77 Data Supplier Ident 16 Contains information to identify the data supplier. Content defined
by the data supplier.
78 thru 93 Target Customer Ident 16 Contains information to identify the data user/customer (for
example, the customer name(s), file codes). Content defined by the
data supplier and/or customer. (Optional)
94 thru 113 Database Part Number 20 Unique part number for database. (Optional - Content TBD)
114 thru 124 Reserved 11 Contains blanks.
125 thru 132 File CRC 8 File CRC: CRC Polynomial TBD. Size of data blocks to be CRCed
also TDB. Note: if it is determined that multiple CRCs are required
this field will become multiple fields and have to be moved to
another record(s).
CRC value for the ARINC data file (including data and header
records). For purposes of calculating a CRC value, Header record 1,
Columns 125 through 132, shall be considered to contain zeros.
ARINC SPECIFICATION 424 - Page 130
6.0 ENCODING STANDARDS

6.2.2 Header Record 2

Column Field Name Field Reference

Length
1 thru 3 Header Ident 3 Contains “HDR”
4 thru 5 Header Number 2 Contains decimal 02 to indicate this is the second Header Record.
6 thru 16 Effective Date 11 If the Effective Date is the date associated with the Cycle Date,
this field will contain blanks. If the file is created outside of
standard cycles, this field will provide the effective date. The
format is the same as the Creation Date. (Optional)
17 thru 27 Expiration Date 11 If the Expiration Date is the date associated with the Cycle Date,
this field will contain blanks. If the file is created outside of
standard cycles, this field will provide the expiration date. The
format is the same as the Creation Date. (Optional)
28 Blank (spacing) 1 Contains blank.
29 thru 58 Supplier Text Field 30 Contains information specific to data supplier, contents to be
defined by data supplier (For example, extract program version)
(Optional)
59 thru 88 Descriptive Text 30 Contains description of file contents, or other information agreed
upon by data supplier and customer. (For example, description of
file content, test file notes, etc). (Optional)
89 thru 132 Reserved 43 Contains blanks.

6.2.3 Additional Header Records 6.7.4 End-of-File Trailer Label (EOF)

Additional Header Records may be added. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.3 Bit Density
6.7.5 End-of-Volume Trailer Label (EOV)
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.4 Coding
6.8 Tape Marks
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.5 Parity Convention
6.9 Summary of Tape Data Layout
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.6 Reel-File Relationship
6.9.1 One File, One Reel
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.7 Labels
6.9.2 One File, Multiple Reels
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.7.1 Volume Header Label (VOL)
6.9.3 Multiple Files, One Reel
This section was deleted and replaced by Section 6.2.1 and
6.2.2. This section was deleted and replaced by Section 6.2.1
and 6.2.2.
6.7.2 Header 1 Label (HDR 1)
6.10 CRC Calculations
This section was deleted and replaced by Section 6.2.1 and
6.2.2. 6.10.1 Precision Approach Path Point Cyclic
Redundancy Check (CRC) Overview
6.7.3 Header 2 Label (HDR 2)
A CRC is an error detection algorithm capable of
This section was deleted and replaced by Section 6.2.1 and detecting small changes in a block of data. Data, which
6.2.2. require high integrity often, utilize CRCs to detect
changes at the “bit” level. A high integrity requirement is
 ARINC SPECIFICATION 424 - Page 131
6.0 ENCODING STANDARDS

called for when a small change in a data block can cause generator polynomial, as shown in the previous section,
programs to fail, or produce erroneous results. Such is the was being used in a CRC calculation the divisor would be:
case for straight and advanced landing approach operations
conducted using information contained in a Precision RNP 110000001010000010100000110101011
RNAV Approach Procedure Path Point Record.
The equation for calculating a 32 bit CRC is where:
A CRC algorithm treats a data block as a single (large) x32 is a multiplier which appends 32 zero bits
numerical value. The data block is divided by a fixed to the end of M(x)
number (called a “generator polynomial”) whose value and M(x) is the data block bit stream
magnitude is determined based on the level of integrity G(x) is the predetermined generator
desired. The remainder of the division is the CRC value for polynomial of the 32nd order
the data block. CRC values are stored or transmitted with Q(x) is the quotient of the modulo 2 division
their corresponding data blocks. Integrity of a data block R(x) is the remainder of the modulo 2 division
can be confirmed when necessary by reapplying the CRC and is coded with the coefficient of x31 as
algorithm and comparing the result with the stored or the most significant (leftmost) bit.
transmitted CRC value. If the data is corrupt, it is highly
probable that the two CRC values will differ. When using a CRC to protect the integrity of a data block,
the data contained in the block is said to be “wrapped” by
The preceding paragraph oversimplifies the CRC process. a CRC. When checking the integrity of the wrapped data
The real ability for a CRC to ensure high levels of integrity there are two different methods that can be employed. The
is provided by polynomial modulo two arithmetic and a two methods are:
sufficiently large generator polynomial. Polynomial
arithmetic mod2 is a form of division that is fast, efficient, 1. Recalculate the data block’s CRC value using the
and sufficient for the purpose of integrity protection. The same generator polynomial. Then compare the
generator polynomial of a CRC algorithm is measured in resultant CRC value to the stored or transmitted
bit size where the polynomial coefficients are binary values CRC value. If the values are equivalent, then the
equal to 0 or 1. The level of integrity protection provided data has integrity.
by a specific generator polynomial is a function of the
highest order term in the polynomial. The higher the term, 2. Perform a modulo 2 division with the stored or
the higher the level of protection. transmitted CRC value appended to the end of
the data block bit stream as the dividend and the
6.10.2 Generator Polynomials: generator polynomial as the divisor. If the
remainder, R(x), is equal to zero, then the data
G[x] =x16+x12+x5+1 (CRC-CCITT algorithm) has integrity.

G(x) = Note 1: G(x) is of the form (1+x)P(x), where P(x) is a

x32 + x 31 + x24 + x22 + x16 + x14 + x8 + x7 + x5 + x3 + x + 1 primitive and irreducible polynomial of order r-
1 = n-k-1.
(CRC-32Q algorithm)
Note 2: All arithmetic operations are performed modulo
The CRC-CCITT algorithm is a 16 bit algorithm and 2.
provides less protection than the CRC-32Q algorithm,
which is a 32 bit algorithm. Generator polynomial Note 3: This explanation is based on a 32 bit CRC. CRCs
coefficients are binary, meaning equal to 0 or 1. Therefore, based on other bit register sizes work on the
only terms with a coefficient of 1 are shown in a generator same principal.
polynomial. A rule of thumb for determining the upper
bound of the probability, e, of an error escaping undetected 6.11 Application of CRC for Integrity Protection of
is 2-r, where r is the magnitude (bit value) of the generator Straight & Advanced Landing Approach
polynomial. Operations
For CRC-CCITT, e = 2-16 = 1.5259 x 10-5. For CRC-32Q, e Refer to RTCA/DO-229C “Minimum Operational
= 2-32 = 2.3283 x 10-10. Performance Standards for Global Positioning
System/Wide Area Augmentation System Airborne
6.10.3 32 Bit CRC Calculation Equipment” for Final Approach Segment (FAS) Data
Block and CRC standards.
CRC are calculated on a “bit-wise” basis. This means that
the data elements of a data block are concatenated into a 6.11.1 Data Block Structure, M(x)
single string of values, which, when converted to their
binary equivalents, comprise a string of binary “bits.” This section was deleted by Supplement 17 when Section
6.11 was revised to refer to RTCA DO-229C.
Each bit is either a 0 or 1. A CRC value represents the
remainder of a modulo 2 division of two bit streams. M(x), 6.11.2 RNAV - GPS/GLS Approach Procedure Path
the data block bit stream, is the dividend in the modulo 2 Point Data Field Bits
division and a predefined generator polynomial is the
divisor. The remainder is commonly and hereafter referred This section was deleted by Supplement 17 when Section
to as R(x). As an example of a bit stream, if the CRC-32Q 6.11 was revised to refer to RTCA DO-229C.
ARINC SPECIFICATION 424 - Page 132
6.0 ENCODING STANDARDS

6.11.3 CRC - Generator Polynomial, G(x)

This section was deleted by Supplement 17 when Section
6.11 was revised to refer to RTCA DO-229C.
 ARINC SPECIFICATION 424 – Page 133
7.0 NAMING CONVENTIONS
7.1 General would used the airport identifier JHKD as the waypoint
identifier. A waypoint established at the position of an
This chapter establishes the coding rules for Identifiers and airport without an identifier but with a name of Rondaville
Name fields when government source does not provide Airport would have an identifier of RONDE.
these Identifiers or Names within the rules established by
ICAO Annex 11. 7.2.3 Named RNAV Waypoints, Intersections, and
Reporting Points
ICAO Annex 11 defines the international standards for
coded designators of NAVAIDS, Waypoints, Airways, In many countries these waypoints are assigned unique
Standard Instrument Arrivals Routes, and Standard five-character names, and the identifier is the same as the
Instrument Departures. name. For waypoints not so named, identifiers are
developed using the following rules sequentially until
7.2 Fix Identifiers five, or fewer, character groups remain.
Fix identifiers will be assigned to all waypoints with the ONE-WORD NAMES
ground rules set forth in this chapter. Section 5.13
establishes the use and limits the field to five characters A. If five or less characters are involved, use the full
maximum. name.

7.2.1 VOR, VORDME, VORTAC, TACAN, and Non- Examples:

Directional Beacons (NDB)
Facility Fix Field Entry
Waypoints located at any of the above types of facilities DOT becomes DOT
will take on the official 1-, 2-, 3-, or 4-character identifier of ACRA becomes ACRA
the facility in question. LOGAN becomes LOGAN

Examples: B. If the name is more than five characters, reduce to five

characters with one or more of the following methods.
Facility Fix Field Entry
Los Angeles VORTAC becomes AX 1. Eliminate double letters
Tyndall TACAN becomes PAM
Ft. Nelson NDB becomes YE Examples:
7.2.2 Non-Directional Beacons (NDB) Waypoint Name Fix Field Entry
KIMMEL becomes KIMEL
For systems employing the “NDB as Waypoint” concept, COTTON becomes COTON
waypoints located at NDB’s should be identified by the use RABBITT becomes RABIT
of the station identifier followed by the alpha characters
“NB.” 2. Keep the first letter, first vowel, and last letter. Drop
other vowels starting from right to left.
Examples:
Examples:
Facility Fix Field Entry
Fort Nelson, Can becomes YENB Waypoint Name Fix Field Entry
Newark, NJ becomes EWRNB ADOLPH becomes ADLPH
BAILEY becomes BAILY
7.2.2.1 Navaid Waypoint BURWELL becomes BURWL

When the position of a navaid is used to create a waypoint 3. Drop consonants, starting from right to left
such as during navaid outage or lack of complete navaid
information, the waypoint identifier will be created using Examples:
the navaid name, following the conventions of Section
7.2.3 for One Word Names and Multiple Word Names. Waypoint Name Fix Field Entry
For example, a waypoint established at the position of a ANDREWS becomes ANDRS
navaid with the name “Uzgorod” would have an identifier BRIDGEPORT becomes BRIDT
of UZGOD. A waypoint established at the position of a
navaid with the name of “Camp Henry” would have an MULTIPLE WORD NAMES
identifier of CHENY.
Use the first letter of the first word and shorten the last word
7.2.2.2 Airport Waypoint using the rules for One-Word names to reduce it four
characters, for a total of five characters.
When the position of an airport is used to create a
waypoint, the waypoint identifier will be created either Examples:
from the airport identifier, if known, or from the airport
name, following the conventions of Section 7.2.3 for One Waypoint Name Fix Field Entry
Word Names and Multiple Word Names. For example, a CLEAR LAKE becomes CLAKE
waypoint established at the position of an airport with the ROUGH AND READY becomes RREDY
identifier of JHKD and a name of Juhankerd Airfield
ARINC SPECIFICATION 424 – Page 134
7.0 NAMING CONVENTIONS
PHONETIC LETTER NAMES NAVAID DISTANCE CODE
INW 18 INW18
When an ICAO phonetic alpha character is used as a CSN 106 06CSN
waypoint name (Alpha, Bravo, Charlie, etc.), use the rules TCS 89 TCS89
established in One-Word Names. When more than one
waypoint in a country has the same phonetic name, obtain B. FIR, UIR, and Controlled Airspace Reporting Positions
uniqueness by applying Duplicate Identifier rules below.
In cases where the government authority does not provide
Examples: unique, five-letter or less waypoint names and in cases
where the government supplied name cannot be converted
Waypoint Name Fix Field Entry to a unique five-letter identifier using previous rules, the
ALPHA becomes ALPHA following rules should be applied in developing an
NOVEMBER becomes NOVMR identifier for such waypoints.
CHARLIE becomes CHARE
1. FIR - use the three characters “FIR” plus a numeric
Two waypoints having the same Waypoint Identifiers from 02 to 99. An identifier so developed is to
within the same country two-letter ICAO, for example, be unique within the geographical area code.
CHARLIE, would become CHAR1 and CHAR2.
2. UIR - use the three characters “UIR” plus a numeric
When a double phonetic, such as TANGO INDIA, is used from 02 to 99. An identifier so developed is to
as the waypoint name, use the rules established under be unique within the geographical area code.
Multiple Word Names. For example, TANGO INDIA
becomes TINDA. 3. FIR/UIR -use “FIR” and a numeric as indicated above.

When a phonetic alpha character followed by a numeric 4. Controlled - use the three- letter characters for the
and/or other alpha character (A1, A1N, B2, etc.), is used Airspace type of controlled airspace plus a
as the waypoint name, it will be coded in the data base the numeric from 02 to 99. If these are
same as shown on aeronautical charts. Terminal Waypoints, they are to be unique
within the Terminal Area. If these are
7.2.4 Unnamed Waypoints Enroute Waypoints, they are to be unique
within the geographic area code. Examples
Waypoints not assigned unique five-character names, but of controlled airspace types are:
where a defined fix is required for charting and is to be
included in navigation data bases, will have identifiers TMA Terminal Area
developed using the following guidelines: CTR Controlled Zone
ATZ Aerodrome Traffic Zone
A. Unnamed turn points, intersections, and CTA Controlled Area
bearing/distance waypoints TIZ Traffic Information Zone

If the unnamed turn point, intersection, or bearing/distance 7.2.5 Reporting Positions Defined by Coordinates
is collocated with a named waypoint or NAVAID station on
a different route structure (e.g., low level or approach), the Entry, Exit and intermediate points within Oceanic
name or identifier of the collocated waypoint should be Control Areas are often defined by waypoints which are
used. “undesignated,” meaning there is no published five-letter-
name-code. These points are quite often made available in
Example: Unnamed turn point on J2 between Lake Charles source documentation as geographical coordinates,
(LCH) and New Orleans (MSY) VORTACs is coincidental expressed in full degrees or half degrees of Latitude and
with the Lafayette (LFT) low level VORTAC. LFT should full degrees of Longitude. When such waypoints are to be
be used as the identifier code for the turn point. entered into a database, the following rules are to be
applied:
Identifier codes for unnamed turn points, intersection, or
bearing/distance waypoints that are not coincidental with A. Full Degree of Latitude
named waypoints should be constructed by taking the
identifier code of the reference NAVAID for the turn 1. Positions in the northern hemisphere use the
point/intersection/(bearing/ distance waypoint) (expected to letters “N” and “E,” the southern hemisphere
be the nearest NAVAID serving the airway structure in uses the letters “S” and “W.”
which it is located) and the distance from the NAVAID to
the turn point/intersection/(bearing/distance waypoint). If 2. Latitude will always precede Longitude.
the distance is 99 nautical miles or less, the NAVAID
identifier should be placed first, followed by the distance. If 3. Both will use numerics for latitude and longitude
the distance is 100 nautical miles or more, the last two digits as follows:
only should be used and placed ahead of the NAVAID
identifier. a. Latitude - use values provided by source.

b. Longitude - use only the last two digits of the

three digit longitude. Placement of the longitude
value in reference to the identifier character (of
“N,” “S,” “W” or “E,” see below) will provide
 ARINC SPECIFICATION 424 – Page 135
7.0 NAMING CONVENTIONS
the information as to whether the longitude digit S7500/E15000 - 75S50
dropped was “0” or “1.” That character will S0600/E11000 - 06S10
follow the longitude digits if the longitude is less
than 100 degrees and precede the longitude digits B. Half Degree of Latitude
if the longitude is equal to or greater than 100.
1. Positions in the northern hemisphere use the
c. Use of a single character to provide both latitude letters “N” and “E,” the southern hemisphere
and longitude information: uses the letters “S” and “W.”
“N” = North Latitude and West Longitude 2. Latitude will always precede Longitude.
“E” = North Latitude and East Longitude
“S” = South Latitude and East Longitude 3. Both will use numerics for latitude and longitude
“W” = South Latitude and West Longitude as follows:
d. Examples: a. Latitude - use the full degree values provided by
source. Placement of the latitude value in
North Latitude/West Longitude, longitude less reference to the identifier character (of “N,” “S,”
than 100 degrees “W” or “E,” see below) will provide the
information as to whether the latitude is full
N5200/W07500 - 5275N degree or half degree.
N5000/W04000 - 5040N
N0700/W00800 - 0708N b. Longitude - use only the last two digits of the
three digit longitude. Placement of the longitude
North Latitude/West Longitude, longitude equal value in reference to the identifier character (of
to or greater than 100 degrees “N,” “S,” “W” or “E,” see below) will provide
the information as to whether the longitude digit
N7500/W17000 - 75N70 dropped was “0” or “1.” That character will
N0700/W12000 - 07N20 follow the longitude digits if the longitude is less
than 100 degrees and precede the longitude digits
North Latitude/ East Longitude, longitude less if the longitude is equal to or greater than 100.
than 100 degrees
c. Use of a single character to provide both latitude
N5000/E02000 - 5020E and longitude information:
N7500/E05000 - 7550E
N0600/E00800 - 0608E “N” = North Latitude and West Longitude
“E” = North Latitude and East Longitude
North Latitude/East Longitude, longitude equal “S” = South Latitude and East Longitude
to or greater than 100 degrees “W” = South Latitude and West Longitude
N7500/E15000 - 75E50
N0600/E11000 - 06E10 d. Examples:
South Latitude/West Longitude, longitude less North Latitude/West Longitude, longitude less
than 100 degrees than 100 degrees

S5200/W07500 - 5275W N5630/W02000 - N5620

S5000/W04000 - 5040W N5030/W04000 - N5040
S0700/W00800 - 0708W N0730/W00800 - N0708

South Latitude/West Longitude, longitude equal North Latitude/West Longitude, longitude equal
to or greater than 100 degrees to or greater than 100 degrees
S7500/W17000 - 75W70 N7530/W17000 - 7N570
S0700/W12000 - 07W20 N0730/W12000 - 0N720
North Latitude/ East Longitude, longitude less
South Latitude/East Longitude, longitude less than 100 degrees
than 100 degrees
N5030/E02000 - E5020
S5000/E02000 - 5020S N7530/E05000 - E7550
S7500/E05000 - 7550S N0630/E00800 - E0608
S0600/E00800 - 0608S
North Latitude/East Longitude, longitude equal
South Latitude/East Longitude, longitude equal to or greater than 100 degrees
to or greater than 100 degrees
N7530/E15000 - 7E550
N0630/E11000 - 0E610
ARINC SPECIFICATION 424 – Page 136
7.0 NAMING CONVENTIONS
South Latitude/West Longitude, longitude less TD = Touchdown Fix inboard of runway threshold
than 100 degrees HC = Helipad Fix
EP = Final End Point
S5230/W07500 - W5275
S5030/W04000 - W5040 Multiple Approach Procedures for a given runway or
S0730/W00800 - W0708 helipad coded for which common waypoints cannot be
established:
South Latitude/West Longitude, longitude equal
to or greater than 100 degrees The following two-character codes are to be added to the
runway identifier to create an airport-related waypoint
S7530/W17000 - 7W570 identifier when no named waypoint has been established by
S0730/W12000 - 0W720 the government source for the fix type:

South Latitude/ East Longitude, longitude less Fx = Final Approach Fix, where “x” equals the “Route
than 100 degrees Type” (Section 5.7) for the procedure in question
Ax = Initial Approach Fix, where “x” equals the “Route
S5030/E02000 - S5020 Type” (Section 5.7) for the procedure in question
S7530/E05000 - S7550 Ix = Intermediate Approach Fix, where “x” equals the
S0630/E00800 - S0608 “Route Type” (Section 5.7) for the procedure in
question
South Latitude/East Longitude, longitude equal Cx = Final Approach Course Fix, where “x” equals the
to or greater than 100 degrees “Route Type” (Section 5.7) for the procedure in
question
S7530/E15000 - 7S550 Mx = Missed Approach Point Fix, where “x” equals the
S0630/E11000 - 0S610 “Route Type” (Section 5.7) for the procedure in
question
7.2.6 Terminal Waypoints Sx = Step-Down Fix Note: if multiple step-down fix
waypoints need to be created, replace “D” with
The following rules should be applied in developing another character, retain the “S.”
identifiers for waypoints used solely in terminal area Rx = Runway Centerline Fix, where “x” equals the
procedures. Such waypoint identifiers will be unique only “Route Type” (Section 5.7) for the procedure in
for the airport specified; a waypoint identifier used in a question
terminal area cannot be repeated in that terminal area but Tx = Touchdown Fix inboard of runway threshold,
can be used in an enroute area encompassed by the same where “x” equals the “Route Type” (Section 5.7)
geographical area code. Terminal waypoint identifiers can for the procedure in question
be repeated in areas covered by different geographical
codes. These identifier developing rules should only be The convention for Multiple Approaches/Multiple
applied when the waypoints in question have not been Waypoints is contained in Table 7-1.
assigned official names/identifier by the government
authority. Note: “C-T-L” is “Circle-To-Land” Approach

A. Airport/Heliport or Runway/Helipad related Terminal The prefixes indicated in the table above assume that a
Waypoints unique geographical position (Latitude/Longitude) is
required for each Waypoint and the “common waypoint”
Single Approach Procedure for a given runway or helipad idea cannot be used. Should a single waypoints'
coded and Waypoints common to more than one geographical position be such that it will serve as the same
approach. waypoint type for more than one coded approach
The following two-character codes are to be added to the procedure, a “common waypoint”; the Single
runway identifier or helicopter approach alignment Approach/Common Waypoint convention should be used.
bearing to create an airport related waypoint identifier
when no named waypoint has been established by the Note on prefixes for FMS(F) Approach Waypoints:
government source for the fix type:
As the majority of the prefixes generated using the standard
FF = Final Approach Fix convention and the Route Type “F” produced duplicates or
AF = Initial Approach Fix two character codes that would be easily confused with
IF = Intermediate Approach Fix other coded, the numeric/alpha/runway identifier concept is
CF = Final Approach Course Fix used.
MA = Missed Approach Point Fix
SD = Stepdown Fix (when not using convention in B. Bearing and Distance Waypoints
paragraph “E”)
RW = Runway Fix Identifiers should be developed by the application of the
OM = Outer Marker Fix following rules:
MM= Middle Marker Fix
IM = Inner Marker Fix 1. The first character of the fix identifier should be “D.”
BM = Backcourse Marker Fix
2. Character 2 through four should simplify the Navaid
course on which the waypoint lies.
 ARINC SPECIFICATION 424 – Page 137
7.0 NAMING CONVENTIONS
3. The last character should be the distance of the
radius defining the position of the waypoint. This
radius should be expressed as the equivalent letter of
the alphabet, i.e., A = 1nm, G = 7nm, O = 15nm, etc.

4. If the arc radius is greater than 26 NM, then use the

convention for unnamed Turn Points, Intersections,
and Bearing/Distance Waypoints.

5. If the arc radius is provided in official government

source as nautical miles and tenths of nautical miles,
the letter of the alphabet will reflect values rounded
to full nautical miles, i.e., 10.5nm = 11nm or “K,”
10.4nm = 10nm or “J.” All values between 0.1 and
1.4 will be character “A.”

C. Along Track Distance Waypoints

Along Track Distance Waypoints are expressed in

government source documentation as being “x” number of
nautical miles from a named waypoint/fix. On
aeronautical charts, they are normally identified as “xx.x
NM from Named Waypoint.”

When not provided by the source document, identifiers

for such waypoints should be developed from the along
track distance portion of the source information, in two
parts:

Part One - the distance in nautical miles and tenths of

nautical miles when the tenths is greater than zero, with
the decimal point suppressed. Tenths values equal to zero
are dropped.

Part Two - the suffix “NM” if the value is equal to or less

than 9.9 or a prefix of “NM” if the value is greater than
9.9.
Examples:

3.0 NM from DOOTY should be expressed as 3NM.

2.8 NM from CHASS should be expressed as 28NM.
11.0 NM from BACUP should be expressed as NM11.
13.8 NM from KITTY should be expressed as NM138.
ARINC SPECIFICATION 424 – Page 138
7.0 NAMING CONVENTIONS

Waypoint Waypoint codes based on the procedure type.

Type

ILS (I) ILS (L) ILS (B) VOR (V) NDB (N) MLS (M)
IAF AI AL AB AV AN AM
IF II IL IB IV IN IM
FACF CI CL CB CV CN CM
FAF FI FF FB FV FN FM
MAP MI ML MB MV MN MM
TDP TI TL TB TV TN TM
Step-down SI SL SB SV SN SM
FEP EI EL EB EV EN EM

RNAV (R) TACAN (T) IGS (G) LDA (X) SDF (U) GPS (P)
IAF AR AT AG AX AU AP
IF IR IT IG IX IU IP
FACF CR CT CG CX CU CP
FAF FR FT FG FX FU FP
MAP MR MT MG MX MU MP
TDP TR TT TG TX TU TP
Step-down SR ST SG SX SU SP
FEP ER ET EG EX EU EP

RNAV GPS LAAS-

MLS (W) MLS (Y) Required (E) FMS (F) GPS/GLS (J) WAAS-GPS (K)
IAF AW AY AE 1F AJ AK
IF IW IY IE 2F IJ IK
FACF CW CY CE 3F CJ CK
FAF FW FY FE 4F FJ FK
MAP MW MY ME 5F MJ MK
TDP TW TY TE 6F TJ TK
Step-down SW SY SE 7F SJ SK
FEP EW EY EE 8F EJ EK

Table 7-1 Multiple Approaches/Multiple Waypoints

D. Constant Radius to a Fix Waypoint E. Unnamed Step-down Fix Waypoints

The “Constant Radius to a Fix” Path Terminator (RF The majority of published, unnamed step-down fix
LEG) has available a constellation of three fixes to assist waypoints are defined by DME distances from a DME
in defining the arc. These are the ARC Center Fix, the associated with procedure reference facility. The naming
Initial Fix, and the Ending Fix. As the waypoints in convention for these points makes use of that general
question will be related to a specific terminal procedure or standard. The convention will still be used for unnamed
set of procedures for an airport, these waypoints are step-down fix waypoints even if they are not DME
defined as Terminal Waypoints. defined.

When not provided by the source document, identifiers for 1. Two digits to identify the distance)
such waypoints should be developed from their use in the 2. Three characters to identify the procedure type.
arc definition, in two parts: 3. Position digits to identify decimal or full
nautical miles.
Part One - a three character alpha code indicating position
within the constellation: Examples. An unnamed step-down fix at 0.5 DME from
an ILS DME = 05ILS
ARC = ARC Center Waypoint
AIF = ARC Initial Waypoint An unnamed step-down fix at 1.7 DME from
AEF = ARC Ending Waypoint a LOC DME = 17LOC
Part Two - a two character numeric that ensures a unique An unnamed step-down fix at 3.5 GPS =
waypoint within the set of terminal waypoints for a given 35GPS
airport.
An unnamed step-down fix at 12 DME from
Examples: ARC01, AIF01, AEF01 a VORDME = DME12
 ARINC SPECIFICATION 424 - Page 139

7.0 NAMING CONVENTIONS

An unnamed step-down fix at 7 DME from a Examples:

TACAN = TAC07
Fix Ident Fix Name
An unnamed step-down fix at 3.5NM from the threshold SPH SEA PERCH (SPH)
= 35THR CRP CARP (CRP)
If duplications result within an airport from this 7.3.2 Unnamed Waypoints
convention, the duplicate and subsequent waypoint idents
will carry a number replacing the last of the three UNNAMED TURN POINTS, INTERSECTIONS,
characters. AND BEARING/DISTANCE WAYPOINTS

Examples: The first unnamed step-down fix at 3.5NM The name field for unnamed waypoints whose identifiers
from the threshold = 35THR are established under rule 7.2.4 will have a description of
the waypoint to assist in finding the location on
The second unnamed step-down fix at aeronautical charts. This description will use the forming
3.5NM from the threshold = 35TH2 NAVAID identifier and bearing/distance information.

F. Navaid/Distance Convention. Examples:

Although the convention for waypoint identifiers using a Fix Ident Fix Name
navaid identifier and the distance from the navaid at ABC12 ABC090012 ABC 090 degrees, 12 nm
which the waypoint is located, (see Section 7.2.4 A, 81ABC ABC090181 ABC 090 degrees, 181 nm
Unnamed Waypoints) is permissible for Terminal AB13 AB180013 AB 180.3 degrees 12.8
Waypoints, preference should be given to using the Decimal values, round up
conventions of this Section (7.2.6), resorting to the rules for .5 or greater and round
of 7.2.4 only when distances are greater than 26NM. The down for .4 or less
conventions of Section 7.2.4 A should never be used for D185J ABC185010 ABC 185 degrees, 10 nm
waypoints where the distances is 10NM or less.
FIR/UIR AND CONTROLLED AIRSPACE
7.3 Waypoint Name/Description REPORTING POSITIONS

The waypoint Name field is assigned to all waypoints in The name field will be developed under the same
accordance with the ground rules set forth in this section. guidelines as for the rules above with the addition of a
ICAO Document 4444 defines an international standard for boundary description in parenthesis. Any additional data
the name of both officially assigned and non-assigned added must start in position 13 of the name field.
designators at significant points along a route of flight.
These rules are in accordance with that standard. Examples:

7.3.1 Named Waypoints Fix Ident Fix Name

FIR05 ABC090012 (FIR)
UNIQUE FIVE-LETTER FIR06 ABC090105 (FIR/UIR)
FIR08 AB180013 (FIR/UIR/UTA)
The name field will contain the same five-letter name as the
Waypoint Identifier field. Use the NAVAID/Bearing/Distance name whenever
possible rather than the Latitude and Longitude method.
Examples:
For those fixes that cannot be described using
Fix Ident Fix Name NAVAID/Bearing/Distance description, the name field
LOGAN LOGAN may contain the latitude/longitude of the fix followed by a
boundary description.
NAME WITH MORE THAN FIVE LETTERS
Examples:
The name field will contain the full name of the fix.
Fix Ident Fix Name Actual Position
Examples: UIR05 6100N01234W (OCTA) N6100.0 W012 34.0
UIR06 4028N01500W (OCTA) N40 27.5 W015 00.0
Fix Ident Fix Name
RABIT RABBITT REPORTING POSITIONS DEFINED BY
RREDY ROUGH AND READY COORDINATES
NAMES WITH MORE THAN FIVE LETTERS Identifiers for waypoints that are defined on aeronautical
AND AN ASSIGNED FIX IDENTIFIER charts by latitude and longitude are outlined in paragraph
7.2.5. The name field for these waypoints will be coded
The name field will contain the full name of the fix with the according to the following rules:
assigned identifier in parenthesis.
Latitude will be shown before longitude:
ARINC SPECIFICATION 424 - Page 140

7.0 NAMING CONVENTIONS

If either value contains minutes greater than zero, both Positions 1 and 2 = use the characters VP or VC,
values will show minutes (11 character rules). alternatively VF or VS
Positions 3 thru 5 = numeric.
If both values contain minutes of zero (degrees only), both The identifiers so created are to be unique within a given
values will omit the minutes (7 character rules). ARINC Area Code.
Other descriptive information, in parenthesis, may be added Examples: VP001
but must start in position 13 of the fix name field. VC101
Examples:
“VP” or “VC” are the preferred position 1 and 2 codes. VF
Fix Ident Fix Name Actual Position and VS are to be used after all numeric, 001 to 999, for
4708N 47N008W N4700.0 W008 00.0 given ARINC Area Code have been used.
6010N 60N010W (OCTA) N60 00.0 W010 00.0
7.4 SID/STAR Procedure Identifiers
7.3.3 Airport-Related Waypoints
Naming Rules
MARKERS AS TERMINAL WAYPOINTS
When source documents for procedure identifiers published
For Markers that are shown as Terminal Waypoints, the by the controlling agency include computer abbreviations,
runway with which the marker is associated will be they will be used in the appropriate fields. When the source
included in the name field. provide codes designations are not compatible with the
requirements of an aeronautical database, modifications are
Pos 1 and 2: OM, IM, MM or BM required. In such cases, SID/STAR identifiers are assigned
Pos 3: blank to all procedures in accordance with the ground rules set
Pos 4 thru 8: runway identifier forth in this Chapter. The SID/STAR identifier must be
Pos 9: blank limited to a maximum of 6 characters in length. Current
Pos 10 thru 25: additional name when required international standards for assigning coded designators
permit up to 7 characters (ICAO Annex 11, Appendix 3).
Examples: These seven characters normally consist of a basic
indicator, validity indicator, and, when required, a route
Fix Ident Fix Name indicator. The basic indicator names the significant point
OM18 OM RW18 where the departure terminates or the arrival begins. The
ALTUR OM RW26L ALTUR ICAO validity indicator publicizes the current edition of the
arrival or departure. This is a numeric character from one to
7.3.4 Navaid Waypoint nine. The ICAO route indicator is an alpha character which
is added, as necessary, to distinguish between more than
The Name/Description field of a waypoint established at one departure terminating at the same significant point or
the position of a navaid will contain the full navaid name, arrival beginning at the same point.
and navaid type when known.
A. For a published SID or STAR identifier not derived
Examples: Fix Ident Fix Name from the ending/beginning NAVAID or waypoint
UZGOD Uzgorod NDB follow these rules:

CHENY Camp Henry If the identifier is:

VORTAC
1. Alphanumeric, then shorten the published name down
7.3.5 Airport Waypoint to six characters by simply dropping characters from
the name from right to left. If such a SID or STAR
The Name/ Description field of a waypoint established at uses numeric or alpha detail, always retain that suffix
the position of an airport will contain the full airport name (validity/route indicator) detail, dropping an additional
and the published “airport term.” number of characters from the name as required.

Examples: Fix Ident Fix Name Examples:

JHKD Juhankerd Airfield
POGO Departure, no waypoint named POGO, would
RONDE Rondaville Airport be POGO
North Departure (or Departure to North), would be
7.3.6 VFR Waypoints NORTH
Military One Arrival would be MILIT1
If a VFR Waypoint is to be included in the Enroute (EA), Noise Abatement Six Departure would be NOISE6
Airport Terminal (PC) or Heliport Terminal (HC) Arrival Seven would be ARRIV7
Waypoint files for which the government authority has
not provided a five-letter-name-code, one is to be created 2. Either all numeric or a runway identifier, then add the
using the following conventions: characters DEP for Departure or ARR for Arrival to
the identifier, dropping letters (on DEP or ARR) from
right to left where required.
 ARINC SPECIFICATION 424 - Page 141

7.0 NAMING CONVENTIONS

Examples: e. The Waypoint name contains double letters and both

validity indicator and route indicator are published,
One Departure would DEP1 then drop the first double letter (instead of the 5th
31 Arrival would be ARR31 character of the waypoint name) and retain the
131 Departure would be DEP131 validity indicator and route indicator.
311 Arrival would be ARR311 Examples:
1001 Departure would be DE1001
2000 Arrival would be AR2000 WITTY One Alpha Departure to WITTY waypoint
would be WITY1A
Runway 07 Departure would be DEP07
Runway 25 Arrival would be ARR25 MASSA Two Charlie Arrival from MASSA
Runway 01L Departure would be DEP01L waypoint would be MASA2C

B. For a published SID or STAR identifier derived from a 3. Published Waypoint with more than 5 characters,
NAVAID or Waypoint follows these rules: then reduce the name to 5 characters using the
established waypoint rules from this chapter and
If the SID (departure) terminates or STAR (arrival) begins then apply rule B.2 above.
with a
Examples:
1. NAVAID, then use the ident of the NAVAID in all
cases, even when the NAVAID “name” is five COTTON One Departure to COTTON waypoint
characters or less. would be
COTON1
Examples: BURWELL Bravo Arrival from BURWELL
waypoint would be BURWLB
Bucks Seven Arrival from Bucks VOR “BKS” would CLEAR LAKE Three Golf Departure to CLEAR
be BKS7 LAKE waypoint would be CLAK3G
Kellogg Five Alpha Departure to Kellogg VOR
“WDK” would be WDK5A 4. Published Duplicate Waypoint (as identified by
Fink Two Delta Arrival from Fink VOR “FNK” would WAYPOINT IDENTIFIERS - paragraph 7.2.3) then,
be FNK2D drop the digit added to provide uniqueness (unless the
digit is necessary because of the procedures existing at
2. Published Waypoint with 5-character name, then if: the same airport).

a. No validity indicator or route indicator has been Examples:

published, then retain the basic name as published.
CHARLIE Departure to a waypoint in the data base as
b. Only a validity indicator has been published, then CHAR1 or CHAR2 would be CHAR (retain only these
retain the basic name and the validity indicator as four characters)
published. CHARLIE One Departure to a waypoint in the data
base as CHAR1 or CHAR2 would be CHAR1
c. Only a route indicator has been published, then CHARLIE One Alpha Departure to a waypoint in the
retain the basic name and the route indicator as data base as CHAR1 or CHAR2 would be CHAR1A
published.
SHAWNEE Departure to a waypoint in the data base
Examples: as SHA1E as there are more than nine points named
SHAWNEE within the ICAO would be SHAE (as
ALLAN Departure to ALLAN waypoint would be SHAE1 through SHAE9 came before SHA1E)
ALLAN SHAWNEE One BRAVO Departure to a waypoint in
CAROL One Departure to CAROL waypoint would the data base as SHA1E as there are more than nine
be CAROL1 points named SHAWNEE within the ICAO would be
STEVE Alpha Arrival from STEVE waypoint SHAE1B.
would be STEVEA
5. Unpublished Waypoint name, then use the rule for the
d. Both a validity indicator and a route indicator have points as described in WAYPOINT IDENTIFIERS -
been published, then drop the last (5th) character of paragraph 7.2.4 (unnamed waypoints), and apply the
the basic name and retain the validity indicator and rule in B.2 above.
route indicator.
C. Unpublished SIDs or STARs without any name or
Examples: identifier are currently not included in the aeronautical
navigation data base and, hence, are not currently
DAVIS Five Bravo Departure to DAVIS waypoint provided for in these naming rules for SID/STAR
would be DAVI5B identifiers.
ANITA Six Delta Arrival from ANITA waypoint
would be ANIT6D
ARINC SPECIFICATION 424 - Page 142

7.0 NAMING CONVENTIONS

For “Engine Out SIDs,” use an identifier provided by Examples: From Terminal Area to Airport -
source documentation when such is available. If an Engine CYULCYYC
Out SID is to be coded that does not have a source From FIR to FIR - ENBOGCCC
provided identifier, an identifier will be created by adding From Center to Airport - KZTLKRDM
the prefix “EO” to the Runway Designator. For example, From Geographical Entity to Terminal Area
an Engine Out SID for Runway 07L would be designated SCANDIGCCC
“EO07L.” Note that with this convention, only one Engine
Out SID per runway can be included in a master airline 7.5.4 Multiple Routes - Same Points/Areas/Regions
user file.
If there is more than one routing without a published
7.5 Preferred Route Identifiers identifier between the same two points/areas/regions and
the rules in Section 7.5.3 is being used to create the route
7.5.1 North American Routes identifier, add numerics to indicate the multiples.

Examples: For two routes between KZTL and KRDM

For North American Routes for North Atlantic Traffic, KZTLKRDM1 and KZTLKRDM2
“Non-Common” portion and other Preferred or Preferential
Routes without published identifiers but with unique initial 7.5.5 Preferred or Preferential Overfly Routings
and terminus fix points, the route identifier will be
developed using the initial and terminus fix identifiers, as For Preferred or Preferential Overfly Routings, routings
indicated in the table below. that are not designed to serve a initial departing
airport/terminal area or terminus arriving airport/terminal
area, the route identifier will be derived from the fix, area
Fix Type Create Identifier Using or region to be overflown and a direction of overflight
Airport Three or Four Character Airport Identifier prefix or a direction of origin in reference to the direction
Navaid Navaid Identifier of overflight suffix, according to the table below. If the
Waypoint Waypoint Identifier (five character max) route is an overflight route and no directional restrictions
apply, the character “O” for “overfly” is used instead of the
directional indication.
Examples: From Airport to Airport - CYYLCYYC
From Airport to Navaid - CYYLART Fix/Area/
From Navaid to Waypoint - ARTCOLAR Region
Direction Create Identifier Using

7.5.2 Multiple Routes - Same Fix Airport Three or 4-character Airport

Navaid Identifier
If there is more than one routing without a published Waypoint Navaid Identifier
identifier between the same to fixes and the rules in Section FIR, ARTCC Waypoint Identifier
7.5.1 is being used to create the route identifier, then add Terminal Area Four Character FIR/Center ICAO
numerics to indicate the multiple routings. Geographical Identifier
Entity Identifier of owning Airport
Examples: For two routes between the airports CYYL ICAO Region North Commonly used abbreviations
and CYYC, South Two character ICAO Region Code
CYYLCYYC1 and CYYLCYYC2 East The character “N”
West The character “S”
7.5.3 Preferred or Preferential Routes Overfly The character “E”
The character “W”
For Preferred or Preferential Routes without a published The character “O”
identifier and not between unique initial and terminus fix
points but rather from areas or regions such as Terminal Note: The direction codes shown in the table are provided
Control Areas, FIRs or Geographical Entities, the route for guidance only. Any published direction may be
identifier will be derived from commonly understood indicated by the use of a 1, 2 or three character
elements such as communications center identifiers, prefix/suffix.
country or region abbreviations and the like. Note that if
one end of the routing is a unique fix, the rules in Section Examples:
7.5.1 apply for that fix.
Overflying Terminal Area Eastbound - ECYUL
Area or Region Create Identifier Using Overflying FIR Southbound - SENBO
Overflying from West of a Center - KZTLW
FIR, ARTCC Four Character ICAO Identifier of FIR or Overflying Center Southwestbound - SWKZDV
Center Overflying Terminal Area (no direction specified) OEGLL
Terminal Area Three or Four Character Identifier of
owning airport 7.5.6 Multiple Routes - Overfly
Geographical Commonly used abbreviations
Entity If there is more than one routing without a published
ICAO Region Two character ICAO Region Code identifier between the fix/area/region and the rules in
Section 7.5.5 are being used to create the identifier, add a
numeric to indicate the multiples.
 ARINC SPECIFICATION 424 - Page 143

7.0 NAMING CONVENTIONS

Examples: SENBO1 and SENBO2 7.5.12 Multiple Routes - Off Load

OEGLL1,OEGLL2,0EGLL3
If there is more than one routing published as “off load
7.5.7 Preferred Weekday/Weekend route” and the rules in Section 7.5.11 are being used to
create the identifier, add a numeric to indicate the
For Preferred or Preferential Routings that are published multiples.
with a “weekday” and a “weekend” version, the rules for
“multiples” are replaced with a two character suffix Examples: SENBOOLR1 and SENBOOLR2
(replacing the numerics). “WK” is used for “weekday” and
“WE” is used for “weekend.” This rule applies to routes 7.6 Transition Identifiers
both with and without published identifiers.
SID/STAR Runway Transition Identifiers will be
Examples: Published Identifiers - established using the characters RW (for runway) followed
TOS1WK and TOS1WE by the runway number. If a transition applies identically to
parallel runways, the transition need only be coded once for
Unpublished Identifiers - the parallel runways. In those cases, it should be identified
SENBOWK and SENBOWE with a suffix of “B” after the runway number.
7.5.8 Weekday/Weekend Example: Transitions for Runway 08L and 08R are
identical. They can be coded once as RW08B
If there is more than one routing published as “weekday” or rather than twice as RW08L and RW08R.
“weekend” and the rules in Section 7.5.7 are being used to
create the identifier, add a numeric to indicate the Approach Transition Identifiers are normally the identifier
multiples. of the NAVAID or Waypoint at which the transition starts
or as published in official government source. These
Examples: TOS1WK1 and TOS1WK2 identifiers may be modified to ensure a unique identifier is
available for each transition.
7.5.9 Geographical Routings

For Preferred or Preferential Routings that are published as

being between large areas not definable with aeronautical
terms, a convention of Geographical Entity abbreviations is
used to create Route Idents. As these Route Idents will
have reduced the entity name down considerably, the
Geographical Entity Reference Table is used to provide a
link between the Route Ident and the full entity name.
While the Route Ident is 10 characters long and normal
split five and five between the initial and terminus points of
the route, that split does not have to be applied when
creating Route Idents based on Geographical Entities.

Examples: Routing between UK North and Greece West

- UKNOGRECW or NOUKWGRECE

7.5.10 Multiple Routes - Geographical

If there is more than one routing without a published

identifier between geographical entities and the rules in
Sections 7.5.8 are being used to create the identifier, add a
numeric to indicate the multiples.
Examples: UKNOGRECW1 and UKNOGRECW2

7.5.11 Off Load Route

For Preferred or Preferential Routings that are published

with an “off load route,” the rules for “multiples” are
replaced with a three character suffix (replacing the
numerics). “OLR” is used for the “off load route.” The
standard route would not use a suffix. This rule applies to
routes both with and without published identifiers.

Examples: Published Identifiers -

TOS1 and TOS1OLR

Unpublished Identifiers -
SENBO and SENBOOLR
 WORLD-WIDE DATA (All Applications)

MASTER AIRLINE USER FILE A/L#1 A/L#2 A/L#3 A/L#4 [2]

STEP 1 T/TCR T/TCR T/TCR
ARINC 424 FORMAT, RECORD & FILE CONTENT T

A/L#1 A/L#2 A/L#3 A/L#4

ARINC SPECIFICATION 424 – Page 144

TCR TCR TCR TCR

STEP 2 A/L #1 A/L #2 A/L # 3 A/L #4

NAV DATA FILE NAV DATA FILE NAV DATA FILE NAV DATA FILE
ATTACHMENT 1
FLOW DIAGRAM

AIRBORNE
NAVIGATION
SYSTEM [1]
OPERATIONAL
SOFTWARE

A/L #1 A/L #2 A/L #3 A/L #4

STEP 3 NAV SYS MASTER NAV SYS MASTER NAV SYS MASTER NAV SYS MASTER
FILE FILE FILE FILE

STEP4 A/L #1 [3] A/L #2 A/L #3 A/L #4

NAV SYS MEDIA NAV SYS MEDIA NAV SYS MEDIA NAV SYS MEDIA

See next page for notes [1] thru [3]

 ARINC SPECIFICATION 424 – Page 145

ATTACHMENT 1
FLOW DIAGRAM

Notes Concerning the Flow Diagram

1. The flow diagram shows alternate paths to individual airline master files for tailored company route (TCR) data in the
individual airline boxes of step 1 level.

2. Airline tailored records (denoted by the letter T in the individual airline boxes of the Step 1 level) will be formatted
according to the standards set forth in this document.
ARINC SPECIFICATION 424 – Page 146

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Adindan ADI Clarke 1880 CD Burkina Faso, Cameroon,

Ethiopia, Mali, Senegal,
Sudan

Afgooye AFG Krassovsky 1940 KA Somalia

Ain El Abd 1970 AIN International 1924 IN Bahrain Island, Saudi Arabia

American Samoa 1962 AMA Clarke 1866 CC American Samoa Islands

Anna 1 Astro 1965 ANO Australian National AN Cocos Islands

Antigua Island Astro 1943 AIA Clarke 1880 CD Antigua, Leeward Islands

Arc 1950 ARF Clarke 1880 CD Botswana, Burundi, Lesotho,

Malawi, Swaziland, Zaire,
Zambia, Zimbabwe

Arc 1960 ARS Clarke 1880 CD Kenya, Tanzania

Ascension Island 1958 ASC International 1924 IN Ascension Island

Astro Beacon “E” 1945 ATF International 1924 IN Iwo Jima

Astro DOS 71/4 SHB International 1924 IN St. Helena Island

Astro Tern Island (Frig) 1961 TRN International 1924 IN Tern Island

Astronomical Station 1952 ASQ International 1924 IN Marcus Island

Australian Geodetic 1966 AUA Australian National AN Australia and Tasmania

Australian Geodetic 1984 AUG Australian National AN Australia and Tasmania

Ayabelle Lighthouse PHA Clarke 1880 CD Djibouti

Bellevue (IGN) IBE International 1924 IN Efate and Erromango Islands

Bermuda 1957 BER Clarke 1866 CC Bermuda Islands

Bissau BID International 1924 IN Guinea-Bissau

Bogota Observatory BOO International 1924 IN Colombia

Bukit Rimpah BUR Bessel 1841 BR Bangka and Belitung Islands

(Indonesia)

Camp Area Astro CAZ International 1924 IN Camp McMurdo Area,

Antarctica

Campo Inchauspe 1969 CAI International 1924 IN Argentina

Canton Astro 1966 CAO International 1924 IN Phoenix Islands

Cape CAP Clarke 1880 CD South Africa

Cape Canaveral CAC Clarke 1866 CC Florida and Bahamas

Carthage CGE Clarke 1880 CD Tunisia

 ARINC SPECIFICATION 424 – Page 147

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Chatham Island Astro 1971 CHI International 1924 IN Chatham Island (New
Zealand)

Chua Astro CHU International 1924 IN Paraguay

Co-Ordinate System 1937 of Estonia EST Bessel 1841 BR Estonia

Corrego Alegre COA International 1924 IN Brazil

Dabola DAL Clarke 1880 CD Guinea

Danish Geodetic Institute 1934 DAN Danish 1876 DA Denmark

System

Deception Island DID Clarke 1880 CD Deception Island, Antarctica

Djakarta (Batavia) BAT Bessel 1841 BR Sumatra (Indonesia)

DOS 1968 GIZ International 1924 IN Gizo Island (New Georgia

Islands)

Easter Island 1967 EAS International 1924 IN Easter Island

European 1950 EUR International 1924 IN Austria, Belgium, Channel

Islands, Cyprus, Denmark,
Egypt, England, Finland,
France, Federal Republic of
Germany (West Germany),
Gibraltar, Greece, Iran, Iraq,
Ireland, Israel, Italy, Jordan,
Kuwait, Lebanon,
Luxembourg, Malta,
Netherlands, Norway,
Portugal, Sardinia, Saudi
Arabia, Scotland, Shetland
Islands, Sicily, Spain,
Sweden, Switzerland, Syria,
Tunisia

European 1979 EUS International 1924 IN Austria, Finland,

Netherlands, Norway, Spain,
Sweden, Switzerland

Fort Thomas 1955 FOT Clarke 1880 CD Nevis, St. Kitts, Leeward
Islands

Gan 1970 GAA International 1924 IN Republic of Maldives

Gandajika Base GAN International 1924 IN Zaire

Geodetic Datum 1949 GEO International 1924 IN New Zealand

Graciosa Base SW 1948 GRA International 1924 IN Faial, Graciosa, Pico, Sao
Jorge and Terceira Islands
(Azores)

Greek Geodetic Reference System GRX GRS 80 RF Greece

1987
Guam 1963 GUA Clarke 1866 CC Guam
ARINC SPECIFICATION 424 – Page 148

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Gunuung Segara GSE Bessel 1841 BR Kalimantan (Indonesia)

GUX 1 Astro DOB International 1924 IN Guadalcanal Island

Herat North HEN International 1924 IN Afghanistan

Hermannskogel HER Bessel 1841 BR Yugoslavia (Prior to 1990),

Slovenia, Croatia, Bosnia
and Herzegovina, and Serbia

Hjorsey 1955 HJO International 1924 IN Iceland

Hong Kong 1963 HKD International 1924 IN Hong Kong

Hu-Tzu-Shan HTN International 1924 IN Taiwan

Indian IND Everest EA Bangladesh

EC India, Nepal
EF Pakistan

Indian 1954 INF Everest EA Thailand

Indian 1960 ING Everest EA Vietnam

Indian 1975 INH Everest EA Thailand

Indonesian 1974 IDN Indonesian 1974 ID Indonesia

Ireland 1965 IRL Modified Airy AM Ireland

ISTS 061 Astro 1968 ISG International 1924 IN South Georgia Island

ISTS 073 Astro 1969 IST International 1924 IN Diego Garcia

Johnston Island 1961 JOH International 1924 IN Johnston Island

Kandawala KAN Everest EA Sri Lanka

Kerguelen Island 1949 KEG International 1924 IN Kerguelen Island

Kertau 1948 KEA Everest EE West Malaysia, Singapore

Kusaie Astro 1951 KUS International 1924 IN Caroline Islands, Fed. States
of Micronesia

L.C. 5 Astro 1961 LCF Clarke 1866 CC Cayman Brac Island

Leigon LEH Clarke 1880 CD Ghana

Liberia 1964 LIB Clarke 1880 CD Liberia

Luzon LUZ Clarke 1866 CC Philippines

M’Poraloko MPO Clarke 1880 CD Gabon

Mahe 1971 MIK Clarke 1880 CD Mahe Island

Manchurian Principal System MCN Bessel 1841 BR Manchuria

 ARINC SPECIFICATION 424 – Page 149

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Massawa MAS Bessel 1841 BR Eritrea (Ethiopia)

Merchich MER Clarke 1880 CD Morocco

Midway Astro 1961 MID International 1924 IN Midway Islands

Minna MIN Clarke 1880 CD Cameroon, Nigeria

Montjong Lowe MOL Bessel 1841 BR Sulawesi (Indonesia)

Montserrat Island Astro 1958 ASM Clarke 1880 CD Montserrat, Leeward Islands

Nahrwan NAH Clarke 1880 CD Masirah Island (Omna),

United Arab Emirates, Saudi
Arabia

Nanking 1960 NAN International 1924 IN China

Naparima, BWI NAP International 1924 IN Trinidad and Tobago

North American 1927 NAS Clarke 1866 CC Bahamas, Canada, Canal

Zone, Caribbean, Central
America, Greenland,
Mexico, United States

North American 1983 NAR GRS 80 RF Canada, Central America,

Mexico, United States

North Sahara 1959 NSD Clarke 1880 CD Algeria

Observatorio Meteorologico 1939 FLO International 1924 IN Corvo and Flores Islands
(Azores)

Old Egyptian 1907 OEG Helmert 1906 HE Egypt

Old Hawaiian OHA Clarke 1866 CC Hawaiian Islands

Oman FAH Clarke 1880 CD Oman

Ordnance Survey of Great Britain OGB Airy 1830 AA England, Isle of Man,
1936 Scotland, Shetland Islands,
Wales

Palmer Astro PAM International 1924 IN Antarctica

Pico de las Nieves PLN International 1924 IN Canary Islands

Pitcairn Astro 1967 PIT International 1924 IN Pitcairn Island

Point 58 PTB Clarke 1880 CD Burkina Faso, Niger

Point Noire 1948 PTN Clarke 1880 CD Congo

Porto Santo 1936 POS International 1924 IN Porto Santo and Madeira
Islands
Potsdam PDM International 1924 IN Germany
ARINC SPECIFICATION 424 – Page 150

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Provisional South American 1956 PRP International 1924 IN Bolivia, Chile, Colombia,
Ecuador, Guyana, Peru,
Venezuela
Provisional South Chilean 1963 (also HIT International 1924 IN Southern Chile (near 53°S)
known as Hito XVIII 1963)

Puerto Rico PUR Clarke 1866 CC Puerto Rico and Virgin

Islands

Pulkovo 1942 PUK Krassovsky 1940 KA Russia

Qatar National QAT International 1924 IN Qatar

Qornoq QUO International 1924 IN South Greenland

Reunion REU International 1924 IN Mascarene Islands

Rome 1940 MOD International 1924 IN Sardinia

RT90 RTS Bessel 1841 BR Stockholm

S-42 (Pulkovo 1942) SPK Krassovsky 1940 KA Albania, Czechoslovakia

(prior to 1 January 1993),
Hungary, Kazakhstan,
Latvia, Poland, Romania

Santo (DOS) 1965 SAE International 1924 IN Espirito Santo Island

Sao Braz SAO International 1924 IN Sao Miguel, Santa Maria

Islands (Azores)

Sapper Hill 1943 SAP International 1924 IN East Falkland Island

Schwarzeck SCK Bessel 1841 BN Namibia

Selvagem Grande 1938 SGM International 1924 IN Salvage Islands

Sierra Leone 1960 SRL Clarke 1880 CD Sierra Leone

S-JTSK CCD Bessel 1841 BR Czechoslovakia (prior to 1

January 1993)

South American 1969 SAN South American 1969 SA Argentina, Bolivia, Brazil,
Chile, Colombia, Ecuador,
Baltra and Galapagos
Islands, Guyana, Paraguay,
Peru, Trinidad and Tobago,
Venezuela

South Asia SOA Modified Fischer FA Singapore

1960

Stockholm 1938 STO Bessel 1841 BR Sweden

Sydney Observatory SYO Clarke 1858 New South Wales, Australia

Tananarive Observatory 1925 TAN International 1924 IN Madagascar

 ARINC SPECIFICATION 424 – Page 151

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum Ell.
Datum Code Ellipsoid Code Location

Timbalai 1948 TIL Everest EB Brunei and East Malaysia

(Sarawak and Sabah)

Tokyo TOY Bessel 1841 BR Japan, Okinawa, South

Korea

Trinidad Trigonometrical Survey TRI Clarke 1858 Trinidad

Tristan Astro 1968 TDC International 1924 IN Tristan da Cunha

Unknown U
Viti Levu 1916 MVS Clarke 1880 CD Viti Levu Island (Fiji
Islands)

Voirol 1874 VOI Clarke 1880 CD Tunisia, Algeria

Voirol 1960 VOR Clarke 1880 CD Algeria

Wake Island Astro 1952 WAK International 1924 IN Wake Atoll

Wake-Eniwetok, 1960 ENW Hough 1960 HO Marshall Islands

World Geodetic System 1960 WGA WGS-60 WS Global

World Geodetic System 1966 WGB WGS-66 WC Global

World Geodetic System 1972 WGC WGS-72 WD Global

World Geodetic System 1984 WGE WGS-84 WE Global

Yacare YAC International 1924 IN Uruguay

Zanderij ZAN International 1924 IN Suriname

ARINC SPECIFICATION 424 – Page 152

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Datum
Datum Code Location

NOTE: This listing does not include the name of the ellipsoid used with the local datum as that information is not
currently available.

Lemuta LEM Samoa Islands

Manira MAQ Maldives

Marcus Astro 1961 MCS Japan

Marcus Astro 1965 MAX Japan

Masira Island Astro 1958 MAZ Oman

Mercury MET Global

Modified Mercury MOT Global

Mozambique MOZ Mozambique

Nikolskoe Astro 1929 NIL

NMA/S39 Wilkes Station NMW Antarctica

North Astro 1947 NOT

Paga Hill 1939 PAH West Irian, Papua New

Guinea (Indonesia)

Pete Astro 1969 PET Pitcairn Island

Pico de Sao Tome PST Sao Tome and Principe

Pico Norte PIC

Ponape Astro 1962 PON Fed. States of Micronesia

Port Lockroy POR

Pronto Socorro PRS Brazil

Pulkovo 1932 System PKO U.S.S.R.

Reykjavik REY Iceland

Spitzbergen SPZ Svalbard

Table Hill TAH New Zealand

Taongi Astro 1952 TAO Marshall Islands

Tsingtao Observatory TSO China

 ARINC SPECIFICATION 424 – Page 153

ATTACHMENT 2
LOCAL HORIZONTAL REFERENCE DATUM NAME, DATUM CODE, AND ELLIPSOID LIST

Ellipsoid
Ellipsoid Code

The following is a listing of ellipsoids that have been identified as being used with local horizontal datums.

Airy 1830 AA
Australian National AN
Bessel 1841
Ethiopia, Indonesia, Japan, and Korea BR
Namibia BN
Clarke 1858
Clarke 1866 CC
Clarke 1880 CD
Danish 1876 DA
Everest
Brunei and E. Malaysia
(Sabah and Sarawak) EB
India 1830 EA
India 1956 EC
Pakistan EF
W. Malaysia and Singapore 1948 EE
W. Malaysia 1969 ED
Geodetic Reference System 1980 RF
Helmert 1906 HE
Hough 1960 HO
Indonesian 1974 ID
International 1924 IN
Krassovsky 1940 KA
Modified Airy AM
Modified Fischer 1960 FA
South American 1969 SA
WGS 1960 WS
WGS 1966 WC
WGS 1972 WD
WGS 1984 WE
ARINC SPECIFICATION 424 - Page 154
ATTACHMENT 3
NAVIGATION DATA FILE RELATIONSHIPS

The following pages show a sample computer printout of an ARINC 424 data file. Each record in an ARINC 424 file is
included. Relationships between various record types within the data file has been maintained, e.g., the Navaids and
Waypoints used on the Enroute Airways are available in the appropriate Sections/Subsections.
 ARINC SPECIFICATION 424 - Page 155

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 156

The following ARINC 424 ATTACHMENT 3

NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 157

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 158

The following ARINC 424 ATTACHMENT 3

NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 159

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 160
ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 161

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 162

The following ARINC 424 ATTACHMENT 3

NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 163

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 164
The following ARINC 424 ATTACHMENT 3
data file is for example only. NAVIGATION DATA FILE RELATIONSHIPS
 ARINC SPECIFICATION 424 - Page 165

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 166

The following ARINC 424 ATTACHMENT 3

NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 167

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 168

The following ARINC 424 ATTACHMENT 3

NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
 ARINC SPECIFICATION 424 - Page 169

ATTACHMENT 3
The following ARINC 424 NAVIGATION DATA FILE RELATIONSHIPS
data file is for example only.
ARINC SPECIFICATION 424 - Page 170
ATTACHMENT 4
AIRWAY MINIMUM ALTITUDES AND REQUIRED NAVIGATION PERFORMANCE (RNP)

Airway Minimum Altitude Coding

A. An ARINC 424 Data Base may contain three “levels” of Enroute Airways. These are “High,” “Low” and “Both” Level
routes. The following descriptions apply:
1. High Altitude Airways, Airway Level code of “H,” shall contain:

a. Routes that exist only in the upper airspace as officially designated by the appropriate authority.
b. Routes that are officially designated as “Upper” or “High” even though the structure in which they
exist has not been officially established as “Upper Airspace.”
c. Routes that, by virtue of the assigned MEA or MFA, must be charted as high level routes.

2. Both Altitude Airways. Airway Level code of “B,” shall contain:

a. Routes that are not specifically defined into either the upper or lower airspace in a structure that does
recognize these airspace divisions, for example the “Control Routes” in the USA and CAN coverages.
b. Routes that exist without a “level designator” that are in a structure that does recognize the division of
Upper and Lower Airspace.
c. Routes that exist in a structure that has Upper and Lower Airspace when such routes have a MEA or
MFA assigned lower than the upper limit of Lower Airspace and a MAA above the upper limit of
Lower Airspace.

3. Low Altitude Airways. Airway Level code of “L,” shall contain:

a. Routes that exist only the lower airspace as officially established by the appropriate authority.

b. Routes that, by virtue of the published MAA, must be charted in lower airspace only.

4. Enroute Airway Sequencing.

Airways changing from one level to another level will be sequenced in order as any airway in the same
level. The Airway Level Code is not used to sort airways in an ARINC 424 data base.

When an airway changes from Airway Level Code “B” to two separate airways that are coded as “L” and
“H,” the point of change will carry the “B” in the level field.

B. High Altitude Airways.

The altitude information shown on “High Level” records will be established with the following criteria:
1. The altitude information included for High Altitude Airways will be derived from official government source.
The values entered for “Minimum Altitude” will be published MEAs (Minimum Enroute Altitude) or MFAs
(Minimum Flight Altitude). If neither of those two values are available through source documentation, the
lower limit of the designated upper airspace will be entered.
2. There are two Minimum Altitude fields. The second of these is only used when an Enroute Airway has been
published with “Directional MEAs” or “Directional MFAs.” “Directional” information is considered to exist
when the difference in altitude in opposing flight directions is higher than would be indicated by normal
separation standards.
3. For Enroute Airways published with non-standard separation or blocked altitudes, the first Minimum Altitude
field will contain the lowest altitude available. The non-standard separation and/or blocked altitude
information will be available in the “Cruise Table” referenced in the Enroute Airway Record.

4. The Maximum Altitude field will contain the highest useable altitude for the Enroute Airway Segment. This
will be equal to the Upper Limit of the Designated Upper Airspace unless a lower altitude, a “MAA” or
Maximum Authorized Altitude, has been published in the official government source.
 ARINC SPECIFICATION 424 - Page 171
ATTACHMENT 4
AIRWAY MINIMUM ALTITUDES AND REQUIRED NAVIGATION PERFORMANCE (RNP)

C. Low Level and “Both” Level Airways.

The altitude information shown on “Both Level” and “Low Level” records will be established with the following
criteria:

1. The altitude information included for “Both” Altitude and “Low” Altitude Airways will be derived from
official government source. The values entered for “Minimum Altitude” will be published MEAs (Minimum
Enroute Altitude) or MFAs (Minimum Flight Altitude) when such are available. If neither of those two values
are available through source documentation, a code indicating one of the following two conditions will be
used:
NESTB - MEA/MFA not established in source documentation. Used when the source does not establish minimum
altitudes as a general rule. Also used when source documentation does provide minimum altitude
information as a general rule and has explicitly not established a value for a specific route segment or
segments.

UNKNN - MEA/MFA Minimum Altitude was unknown at the time the data base was produced but the source
documentation does provide MEA or MFA as a general rule. The data base supplier expects that future
source documentation will provide some minimum altitude information.
2. There are two Minimum Altitude fields. The second of these is only used when an Enroute Airway has been
published with “Directional MEAs” or “Directional MFAs.” “Directional” information is considered to exist
when the difference in altitude in opposing flight directions is higher than would be indicated by normal
separation standards. “Directional” altitudes will not be provided for “NESTB” and “UNKNN.”

3. For Enroute Airways published with non-standard separation or blocked altitudes, the first Minimum Altitude
field will contain the lowest altitude available. The non-standard separation and/or blocked altitude
information will be available in the “Cruise Table” referenced in the Enroute Airway Record.

4. The Maximum Altitude field will contain the highest useable altitude for the Enroute Airway Segment. This
will be equal to the highest available Flight Level in the Designated Airspace in which the route is available
(Low Altitude Structure or “Both” Altitude Structure) unless a lower altitude, a “MAA” or Maximum
Authorized Altitude, has been published in the official government source.

RNP Coding
RNP values are supplied inbound to the fix in the airway sequence record, when viewed in increasing sequence
number order. The RNP applies only to the airway leg on which it is supplied. Like-values in subsequent sequences
will be repeated in the airway record. If no RNP values is supplied on a segment, there is not a database specified
RNP for that segment.

Examples of coding:

Airway Sequence Number Airway Fix Ident Airway Segment RNP

010 ALPHA Blank
020 BRAVO 050
030 CARLY 040
040 DELTA 100
050 ECHHO Blank
060 FOXTR 050
ARINC SPECIFICATION 424 - Page 172
ATTACHMENT 4
AIRWAY MINIMUM ALTITUDES AND REQUIRED NAVIGATION PERFORMANCE (RNP)

RNP 5 RNP 4 RNP 10 No RNP RNP 5

Alpha Bravo Carly Delta Echho Foxtr

Explanation:

Sequence 010 has a “blank” RNP field. In the example, sequence 010 is the first sequence of the airway and there is no
“inbound to the fix” data

Sequence 020 has a coded RNP value of 050, meaning that a RNP of 5.0NM applies to the segment defined by the
waypoints ALPHA and BRAVO, regardless of the direction flown.

Sequence 030 has a coded RNP value of 040, meaning that a RNP of 4.0NM applies to the segment defined by the
waypoints BRAVO and CARLY, regardless of the direction flown

Sequence 040 has a coded RNP value of 100, meaning that a RNP of 10.0NM applies to the segment defined by the
waypoints CARLY and DELTA, regardless of the direction flown

Sequence 050 has a “blank” RNP field, meaning there is no published RNP for the segment defined by the waypoints
DELTA and ECHHO, regardless of the direction flown

Sequence 060 has a coded RNP value of 050, meaning that a RNP of 5.0NM applies to the segment defined by the
waypoints ECHHO and FOXTR, regardless of the direction flown. In this example, sequence 060 is the last sequence of
the airway.
 ARINC SPECIFICATION 424 - Page 173

ATTACHMENT 5
PATH AND TERMINATOR

Throughout this Attachment many rules and standards for the preparation of coding for Terminal Procedures
(SIDs/STARs/Approaches) from official government source documentation into the ARINC Navigation Database format have
been documented. These rules and standards use the words “must” and “will” as defined below:
“MUST” = Obligation, no other choice.
“WILL” = Desired, decision by data authority implied.
The Path and Terminator concept is a means to permit coding of Terminal Area Procedures, SIDs, STARs and Approach
Procedures, without proliferating the number of named waypoints required to support such procedures. Although it is the
intent of this attachment to provide consistent rules, where a contradiction exists between a general rule and a specific rule,
the specific rule must be used. The Path and Terminator concept includes a set of defined codes referred to as Path
Terminators. Each Code defines a specific type of flight path and a specific type of termination of that flight path. Path
Terminators are assigned to all SIDs, STARs and Approach Procedure segments in accordance with the rules set forth in this
Attachment. This Attachment also includes rules regarding leg data fields associated with each Path Terminator.
It is desirable that all navigation systems be designed to accept all leg types defined in this Attachment. However, as this
Attachment has been dynamic, with new leg types being added, it may be required or desirable not to implement all leg types
in any given navigation airborne system. An example of this is the heading (VX) legs versus the course (CX) legs, which were
added later. A given system may not have the CX legs (with the exception of the CF leg) implemented. Coding by database
suppliers must be accomplished using Path Terminators most appropriately reflecting the official government source
documentation.

COMMENTARY

The use of XA legs is required to maintain consistency with published instrument procedure instructions. It is
recognized that the length of XA legs (CA, FA, or VA) is highly dependent upon the aircraft performance and the
altitude situation and therefore may cause unusual path generation cases.

Unless otherwise specifically stated, all of the rules, information and guidelines in this Attachment apply equally to fixed-
wing and rotor-wing terminal procedures.

The RF Leg type, added with Supplement 11, was introduced with the guidelines listed below.
The RF Leg is to be used only in the following cases:

1. When coding procedure types which were designed with the RF Constant Radius Turn capability as a design criteria.

2. When coding procedure types which were not designed with the RF Leg capability as a criteria as long as both the
original coding and the RF Leg specific coding are available and uniquely identified.
3. When coding procedure types which were not designed with the RF Leg capability as a criteria but which cannot be
coded using other path terminators.
In order to achieve these coding rule goals, and to ultimately simplify the path terminator matrix currently required to define
present-day terminal area procedures, it is in the interest of all user airlines to prevail upon their government agencies and
ATC authorities to:
A. Permit FMS-equipped airplanes to fly tracks instead of procedural headings and,
B. Design Terminal area procedures to be compatible with the capabilities of the increasing number of FMS-Equipped
airplanes entering service.

The Path and Terminator concept is to accommodate the performance capabilities of various fixed-wing aircraft types.
Airmass Path and Terminator constraints are generally for fixed-wing aircraft only. In order to accomplish this requirement,
certain values are established for coding the Path and Termination for fixed-wing aircraft. These values have been established
to allow data base suppliers to code turn and distance fields to a single set of rules. If official government source specifies
values other than these established values, source data will be used.

1. Distance to Calculation
A speed of 210 knots, ground speed, will be used to compute distance based on time (3.5 NM per minute). On “Course
Reversal” Path Terminators, if no time or distance is specified, a minimum distance of 4.3 NM will be used prior to
turning inbound.
ARINC SPECIFICATION 424 - Page 174

ATTACHMENT 5
PATH AND TERMINATOR

2. Bank Angle

A maximum bank angle of 25 degrees will be used to compute turn radius. A full 180 degree turn would require a
minimum of 4 nautical miles in diameter at 250 kt. ground speed.

3. Climb Rate
A climb rate of 500 feet per nautical mile will be used for computations. For missed approach, the climb rate must begin
at the Missed Approach Point. For departure procedures, the climb rate must begin at the take-off end of the runway
unless otherwise specified by source.

4. Outbound Leg Length for Teardrop Procedures

If no distance limit is given, or if a time is given, use the following table to determine the length of the outbound leg.

Angle of Nautical Outbound

Divergence Miles Time
18 10.5 2:45
20 9.5 2:30
22 8.6 2:15
24 7.9 2:00
26 7.3 1:55
28 6.8 1:45
30 6.3 1:40
32 5.9 1:30
34 5.6 1:28
36 5.3 1:23
38 5.0 1:18
40 4.7 1:14
42 4.5 1:10
44 4.3 1:07

This table is based on a speed of 210 knots and a Density Altitude of 5000 Feet. Any procedure that does not fall within
this table would not be coded.

5. Intercept Angles

When the government source does not specify the intercept angle, the following angles must be used:
A. Use the angle determined in accordance with Rule 6.3.6 of this attachment on approach transitions to intercept the
localizer approach path.
B. Use 30 to 45 degrees on all other procedures.
C. For procedures other than approach transitions to intercept the localizer approach path, use a VI Path Terminator
and 30 to 45 degrees intercept if there is a fix termination in the current leg followed by a 3NM or greater gap
between start of turn and the track in the leg to be intercepted.
1.0 General Rules

1.1 NAVAID related Leg Types

Specific leg types require a reference Navaid. The details of which leg types and which Navaid types are to be used can be
seen in Section 5.23 of the main document and Table 3 of this Attachment.
 ARINC SPECIFICATION 424 - Page 175

ATTACHMENT 5
PATH AND TERMINATOR

1.2 Beginning and Ending Leg Types

The Beginning and Ending Leg of a SID, STAR or Approach Route will be selected from the following table. Note that
Profile Descents and their transitions are coded in the same manner as STARs and STAR Transitions.
Note: In general, the same Beginning and Ending Leg types will be used for Helicopter SIDs, STARs and Approaches as
listed for fixed-wing aircraft. No additional types are authorized and use of the authorized types should be consistent
with helicopter flight capabilities.

Procedure Beginning Leg Ending Leg

SID Runway Transition CA, CD, CF, CI, CR, DF, FA, FC, FD AF, CF, DF, FM, HA, HM2, RF, TF,
Route Type 0, 1, 4, F and T FM, IF, VA, VD, VI, VM, VR VM,
CA3, CD3, CF3, CI3, CR3, DF3, FA, FC, AF, CF, DF, FM, HA, IF4, TF, RF,
SID
FD, FM, IF4 , VA3, VD3, VI3, VM
Route Type 2, 5, or M
VM8, VR3 ,
SID Enroute Transition
FA, FC, FD, IF AF, CF, DF, HA, RF, TF,
Route Type 3, 6, S or V
STAR Enroute Transition
FC, FD, IF AF, CF, DF, HM, RF, TF
Route Type 1, 4, 7 or F
STAR
FC, FD, IF AF, CF, DF, FM, IF4, RF, TF, VM
Route Type 2, 5, 8 or M
STAR Runway Transition
FC, FD, HF, IF AF, CF, FM, HF, HM, RF, TF, VM
Route Type 3, 6, 9 or S
Approach Transition
FC, FD, HF, IF, PI AF, CF, CI5, HF, HM, PI, RF, TF, VI5
Route Type A
Approach
IF CF, RF, TF6,
Route Types in Section 5.7
AF7, CA, CD, CF, CI, CR7 DF, FA, FC,
Missed Approach AF, CA, CF, DF, FM, HM, RF, TF,
FD, FM, HA, HM, RF7, TF, VA, VD, VI,
Route Type Z VA, VM,
VM, VR

Explanation of Notes in Table

1
When followed by a CF or DF leg or when Route Type is “T,” Vector SID.
2
When Route Type is “0,” Engine Out SID.
3
When SID Procedure has NO Runway Transitions
4
When “IF” leg is the one and only record in the SID/STAR route.
5
When Approach Transition is localizer based.
6
When Final Approach is GPS or some types of MLS Approach or other specific cases where it has been determined that
a “TF” is more satisfactory than a “CF.”
7
When “AF” or “RF” are published to begin at the published Missed Approach Point.
8
When preceded by runway coded as an IF leg for SID runway transition.
ARINC SPECIFICATION 424 - Page 176

ATTACHMENT 5
PATH AND TERMINATOR

1.3 Leg Sequencing

The following table defines the permitted leg sequences within the individual procedures. A shaded space indicates that the
“current leg/next leg” sequence is not permitted within individual procedure routes.

N E X T L E G
AF CA CD CF CI CR DF FA FC FD FM HA HF HM IF PI RF TF VA VD VI VM VR
AF
CA
CD
CF &
CI
CR
DF &
L E G

FA
FC &
FD
C U R R E N T

FM
HA
HF
HM
IF * * * * * * * *
PI
RF
TF &
VA
VD
VI
VM
VR

* = The IF leg is coded only when the altitude constraints at each end of the “FX,” “HX” or “PI” leg are different.
& = A CF/DF, DF/DF, TF/DF, or FC/DF sequence should only be used when the termination of the first leg must be
overflown, otherwise alternative coding should be used. See Rule 3.1 in this attachment.
 ARINC SPECIFICATION 424 - Page 177

ATTACHMENT 5
PATH AND TERMINATOR

1.4 Leg Type Descriptions

The following illustrations on the various Leg Types are provided to assist coding and decoding of the Path and
Terminator concept.

Leg Code Example Path Description

Figure 1: Initial Fix or IF Leg.

Defines a database fix as a point
IF in space.
IF

Figure 2: Track to a Fix or TF

Leg. Defines a great circle track
over ground between two known
TF databases fixes.

Figure 3: Course to a Fix or CF

Leg. Defines a specified course to
a specific database fix.
CF

Figure 4: Direct to a Fix or DF

Leg. Defines an unspecified track
starting from an undefined
position to a specific database fix.
DF Note: See also Table 1.3, Leg
Sequencing, for other uses of the
DF Leg.

Figure 5: Fix to an Altitude or FA

Leg. Defines a specified track
over ground from a database fix to
a specified altitude at an
FA
unspecified position.
ARINC SPECIFICATION 424 - Page 178

ATTACHMENT 5
PATH AND TERMINATOR

Figure 6: Track from a Fix for a

Distance or FC Leg. Defines a
FC specified track over ground from a
database fix for a specific
distance.

Figure 7: Track from a Fix to a

DME Distance or FD Leg.
Defines a specified track over
FD ground from a database fix to a
specific DME Distance which is
from a specific database DME
Navaid.

Figure 8: From a Fix to a Manual

termination or FM Leg. Defines a
FM specified track over ground from a
database fix until Manual
termination of the leg.

Figure 9: Course to an Altitude or

CA Leg. Defines a specified
course to a specific altitude at an
unspecified position.
CA

Figure 10: Course to a DME

Distance or CD Leg. Defines a
specified course to a specific
DME Distance which is from a
CD specific database DME Navaid.

Figure 11: Course to an Intercept

or CI Leg. Defines a specified
course to intercept a subsequent
CI leg.
 ARINC SPECIFICATION 424 - Page 179

ATTACHMENT 5
PATH AND TERMINATOR

Figure 12: Course to a Radial

termination or CR Leg. Defines a
course to a specified Radial from
a specific database VOR Navaid.

CR

Figure 13: Constant Radius Arc

or RF Leg. Defines a constant
radius turn between two database
fixes, lines tangent to the arc and a
center fix.
Note: While the arc initial point,
arc ending point and arc
centerpoint are all available as
RF database fixes, implementation of
this leg type may not require them
to be available as fixes.

Figure 14: Arc to a Fix or AF

Leg. Defines a track over ground
at specified constant distance from
a database DME Navaid.

AF

Figure 15: Heading to an Altitude

termination or VA Leg. Defines a
specified heading to a specific
VA Altitude termination at an
unspecified position.
ARINC SPECIFICATION 424 - Page 180

ATTACHMENT 5
PATH AND TERMINATOR

Figure 16: Heading to a DME

Distance termination or VD Leg.
Defines a specified heading
terminating at a specified DME
VD Distance from a specific database
DME Navaid.

Figure 17: Heading to an

Intercept or VI Leg. Defines a
specified heading to intercept the
subsequent leg at an unspecified
VI
position.

Figure 18: Heading to a Manual

termination or VM Leg. Defines a
specified heading until a Manual
termination.
VM

Figure 19: Heading to a Radial

termination or VR Leg. Defines a
specified heading to a specified
radial from a specific database
VOR Navaid.
VR
 ARINC SPECIFICATION 424 - Page 181

ATTACHMENT 5
PATH AND TERMINATOR

Figure 20: 045/180 Procedure

Turn or PI Leg. Defines a course
reversal starting at a specific
database fix, includes Outbound
Leg followed by a left or right
turn and 180 degree course
PI reversal to intercept the next leg.
A Maximum excursion Time or
Distance is included as a data
field.

Figure 21: Holding in lieu of

Procedure Turn (HF) for
Approach Procedures and
Mandatory Holds (HA, HM) in
SID/STAR and Missed Approach
coding. The HA, HF, and HM Leg
Types define a holding pattern in
lieu of procedure turn course
reversal or a terminal procedure
referenced mandatory holding
pattern at a specified database fix.
HA, HF, HM Leg time or distance is included
as a data field.
The three codes indicate different
path termination types:
HA = Altitude Termination

HF = Single circuit terminating at

the fix.

HM = Manual Termination.
ARINC SPECIFICATION 424 - Page 182

ATTACHMENT 5
PATH AND TERMINATOR

1.5 Leg Data Fields

The following table provides detail on “Required” and “Optional” parameters used to define each leg type. An “O” in the
table indicates that the parameter is considered optional and may be omitted as required in individual cases. All other entries
indicate some type of a “required” situation for leg definition.
Leg Data Fields Table 3
OBD
W/P OVR RMD THET TM/ ALT ALT SPD VRT ARC
PT MAP HLD TD TDV RHO MAG COMMENTS
ID FLY NAV A DST ONE TWO LMT ANG CTR
CRS
OB MAG CRS=BNDY RDL,
AF X O O X X X X R O O O
THETA=FIX RDL
ALT TERM WILL BE “AT
CA O O O C + O
OR ABOVE”

CD O O O X C D O O O
OB MAG CRS IS CRS TO
CF X B O O O O X X X C P O O O O
SPECIFIED FIX
CI O O O O O C O O O

CR O O O O X X C O O O

DF X B O O O O O O O O

FA X O O O X X X C + O ALT TERM WILL BE “AT

OR ABOVE”
FC X B O O O X X X C P O O O

FD X O O O O X X X C D O O O

FM X O O O X X X C O O
HA ALT TERM WILL BE “AT
X O X O O O C X + O
OR ABOVE”
HF X O X O O O C X O O

HM X O X O O O C X O O

IF X O O O O O O O

PI X X X X X C P X O DIST IS EXCURSION DIST

FROM FIX

RF X O O X O I T A O O O O X

TF X B O O O O O O O O O O O O

O O O H + O ALT TERM WILL BE “AT

VA OR ABOVE”
VD O O O X H D O O O

VI O O O O O H O O O
FOR W/P ID SEE STAR
VM O O O O H O O
CODING RULES
VR O O O O X X H O O O

LEGEND:

X = REQUIRED FIELD R = BOUNDARY RADIAL D = DME DISTANCE

A = ALONG TRACK DISTANCE C = COURSE + = “AT OR ABOVE” ONLY
O = OPTIONAL FIELD H = HEADING SHADED = NOT APPLICABLE FIELD
P = PATH LENGTH
B = “REQUIRED” FOR CF/DF, DF/DF, TF/DF OR FC/DF COMBINATIONS, OTHERWISE “OPTIONAL”
T= Provided for the leg combinations of IF/RF, RF/RF or RF/Hx, and when the RF is the last leg of the procedure, otherwise, the outbound tangential track is
contain in the next leg.
I = The inbound tangential track is provided for leg combinations IF/RF, RF/RF, or RF/HX, otherwise in the inbound tangential track is contained in the
previous leg.
 ARINC SPECIFICATION 424 – Page 183

ATTACHMENT 5
PATH AND TERMINATOR

2.0 Coding Rules Applicable To All Procedures

2.1 All Procedures must be coded to provide guidance specified by source documentation.

2.2 Vertical angles are referenced to the terminating fix.

2.3 Use of a “C” in the Altitude Description field (5.29) may only be used in SID records and there only with the
following leg types:

CD, CF, CR, FC, FD, TF, VD, VR

The conditional termination altitude can be coded in columns 90 through 94 of the SID record. If a “+,” “-” or
“blank” is coded in the Altitude Description field, input of a second altitude must imply a condition altitude
termination.

2.4 Altitude terminations must not be used in descent procedures.

2.5 Lost Communication Procedures may be coded in place of “Vector Legs” if the procedure defines a complete
route of flight to the end of a SID or STAR.

2.6 The “Turn Direction” and “Turn Direction Valid” leg data fields are used in combination to force a particular
turn direction whenever the track/heading change exceeds 135 degrees. If the turn direction is indicated with the
“L” or “R,” then the turn direction valid character must be set to “Y.” If the turn direction is indicated with “E,”
then the turn direction valid field must always be blank.
The Turn Direction/Turn Direction Valid combination is used to indicate that turn in the specified direction
must be executed prior to intercepting the path defined in the record. Turn Direction must always be indicated
whenever the turn is 90 degrees or more.

2.7 The first leg of each procedure will contain the appropriate transition “altitude.” If the transition altitude is
18,000 feet, it may be omitted. See Section 5.53 for specifics on the appropriate altitude for each type of
Terminal Procedure.

2.8 Non essential and transition essential waypoint codes are not used in the waypoint description field on terminal
procedures. All waypoints must be considered as essential in these procedures.

2.9 Required Navigation Performance (RNP) must be applied to segment on which the value is coded. RNP will be
coded on every segment where it is specified by source. Lack of a RNP value on a segment indicated that no
source RNP value is available for the segment.

Examples of RNP Coding:

Standard Instrument Departure (SID)

Trans Sequence Path Fix

Route Type Segment RNP
Ident Number Terminator Ident
1 RW08 010 CA Blank
1 RW08 020 DF ALPHA Blank
1 RW26 010 CA Blank
1 RW26 020 DF ALPHA Blank
2 Blank 010 IF ALPHA Blank
2 Blank 020 TF CARLY 010
3 BRAVO 010 IF CARLY Blank
3 BRAVO 020 TF BRAVO 010
3 DELTA 010 IF CARLY Blank
3 DELTA 020 TF INTER 010
3 DELTA 030 TF DELTA 050
3 ECHHO 010 IF CARLY Blank
3 ECHHO 020 TF ECHHO 040
ARINC SPECIFICATION 424 – Page 184

ATTACHMENT 5
PATH AND TERMINATOR

Explanation:

There is no defined RNP for the Runway Transitions. The common segment has a RNP of 010 or 1.0NM from
ALPHA to CARLY. The Enroute Transition from CARLY to BRAVO is RNP 010 or 1.0NM. The Enroute
Transition to DELTA is RNP 010 or 1.0NM from CARLY to INTER and 050 or 5.0NM from INTER to
DELTA. The Enroute Transition from CARLY to ECHHO is RNP 040 or 4.0NM. The “initial fix” segments
carry no RNP values.

Instrument Approach Procedure

Trans Sequence Path

Route Type Fix Ident Segment RNP
Ident Number Terminator
A EAST 010 IF EAST Blank
A EAST 020 TF ALPHA Blank
A WEST 010 IF WEST Blank
A WEST 020 TF ALPHA 010
R Blank 010 IF ALPHA Blank
R Blank 020 TF BRAVO (FAF) 031
R Blank 030 TF RW18 (MAP) 031
Z Blank 040 DF CARLY 010
Z Blank 050 TF DELTA 010
Z Blank 060 TF ECHHO 010
Z Blank 070 HF ECHHO 010

Explanation:

There is no defined RNP for the EAST transition. The WEST transition has a RNP of 010 or 1.0NM from
WEST to ALPHA. The Final Approach Segment from ALPHA to Runway 18 (RW18) has a RNP of 031 or 0.3
NM. The Missed Approach Segment from the runway through the holding pattern at ECHHO has a RNP of
010 or 1.0 NM.

3.0 Path and Termination Related Rules Valid For All Procedure Types

3.1 DF legs must be used to start from an unknown position such as an altitude or from DME or Distance
terminations. A DF leg may follow a CF leg only when the CF leg fix must be overflown, otherwise a TF leg
should be used. A DF may also be followed by another DF leg. In these cases, the fix at the end of the first DF
leg must be overflown. When DF legs follow DME or Distance Terminations, that termination must be
overflown. For distance terminations, the overfly parameter must be set, otherwise the combination is not
permitted.

3.2 The distance leg data field must be completed on all CF legs. When the CF is preceded by an intercept, the no
wind intercept distance will be provided. If the CF leg is the first leg of a missed approach, the distance entered
will be from the approach runway fix or missed approach fix, whichever applies.

3.3 When a leg terminating at a fix (“XF” leg) is followed by a PI leg, the PI fix must be the same fix as the
terminating fix on the preceding leg.

3.4 Rules specific to “arc” legs, leg type AF:

3.4.1 When an AF-AF leg sequence is coded, both legs must use the same “Recommended VHF Navaid” facility and
the DME distance must be the same for both legs.

3.4.2 When any holding leg (“HX”) or fix termination (“XF”) is followed by an AF leg, the preceding termination fix
must lie on the arc defined in the AF leg.

3.4.3 When a FD leg is followed by an AF leg type, the fix in the FD leg must have the same “Recommend VHF
Navaid” as that defining the AF leg.

3.4.4 When a CD or VD leg type is followed by an AF leg type, both legs must have the same Recommended VHF
Navaid. The DME distance must be the same for both legs.
 ARINC SPECIFICATION 424 – Page 185

ATTACHMENT 5
PATH AND TERMINATOR

3.4.5 When a CI leg type is followed by an AF leg type, the “course to” must be to the “Recommended VHF Navaid”
which defines the AF arc.

3.5 When an AF, CF, DF, RF, TF or “HX” leg is followed by any course-from leg type (“FX” legs), the “FX” leg
must be from the same point as the preceding termination.
3.6 Leg types of CD, CR, FD, RF, VD and VR “overfly” the terminator point. If “turn anticipation” is required to
reflect the source, alternate leg types must be used.

3.7 When the leg data type “Recommended Navaid” is coded in a CI or VI leg, it must be the same as the
Recommended Navaid in the leg to be intercepted.
3.8 The TF leg type will be coded in preference to the CF leg type in all cases where the resulting path will be the
same, except when coding some types of final approach procedure legs, see Rules in Section 6.0, 7.0 and 8.0 of
this Attachment.

3.9 The FC leg type must be used when the distance in the “Time/Distance” field is the path length and is measured
from the fix entered in the Waypoint Identifier field.

The FD leg type must be used when the distance in the “Time/Distance” field is the “DME” distance from the
Navaid entered in the Recommended Navaid field.

3.10 FC or FD legs will not be used if the distance is greater than 60NM and are followed by a CF leg.

3.11 A PI leg is used to make a 180 degree course reversal when a holding or a tear drop turn is not specified. The
course must be coded as 45 degrees from the reciprocal of the inbound course, unless otherwise specified by
government sources. The turn direction is the direction made during the 180 reversal within the PI leg. A one
minute outbound leg is implied from the fix to the initial 45 degree turn.

3.12 The IF leg type will normally be used in an initial sequence of a procedure. The IF leg type, followed by a TF
leg type will be used in other than the first sequence if such is required to correctly code the procedure as
published by the source documentation when one or more of the following criteria are met -
- there is no VHF Navaid available for use as the Recommended Navaid that would permit coding with other
leg types.

- the leg to be intercepted will have a distance of more than 60 NM between the point of intercept and the
terminating fix.

This will allow a segment to be constructed, from one fix to the next fix, using an “intercept” where coding
would otherwise not be possible. See the sample use of this rule below.

3.13 When coding “arc paths,” when the source defined ARC Center is a VHF Navaid of the types VORDME or
VORTAC and the path is defined as a “DME ARC,” the AF leg must be used instead of the RF leg.

3.14 The previous leg and next leg associated with an RF leg should have a course or track which is tangent to the RF
leg except when the leg combination is IF/RF, RF/RF or HX.

3.15 Use of a single RF leg is limited to turns of equal to or greater than 2 degrees and equal to or less than
300 degrees.

3.16 Phantom Waypoints. These database waypoints are established during procedure coding. Used to facilitate more
accurate navigation under certain circumstances.
ARINC SPECIFICATION 424 – Page 186

ATTACHMENT 5
PATH AND TERMINATOR

The copyrighted material in this VI/IF/TF Not for navigational or other operational
Coding diagram is reproduced with the use. For example only. Please consult
permission of the copyright holder Jeppesen current navigation charts.
Sanderson, Inc., Englewood, Colorado.

Normal SID Coding if IRN were a VORDME

SID ROUTE TRANS WAYPOINT DESC PATH

IDENT TYPE IDENT IDENT CODE TERM

SID 1 2 RW29 VA
SID 1 2 RW29 VI
SID 1 2 RW29 CAMEL EE CF

SID Coding required when IRN is VOR only

SID ROUTE TRANS WAYPOINT DESC PATH

IDENT TYPE IDENT IDENT CODE TERM

SID 1 2 RW29 VA
SID 1 2 RW29 VI
SID 1 2 RW29 IRN V IF
SID 1 2 RW29 CAMEL EE TF

©Jeppesen Sanderson, Inc., 1987. All rights reserved.

 ARINC SPECIFICATION 424 – Page 187

ATTACHMENT 5
PATH AND TERMINATOR

Phantom waypoints serve two purposes:

1. Used to end speed restriction in AIP
PH (max 210 until intercepting radial).
2. Allows accurate TF leg to next point
i.s.o. CF leg.

PH PH

AIP specifies to m ake good a track of 090 to

avoid a town North of the airport. Two
Phantom waypoints allow accurate
navigation along the SID.
ARINC SPECIFICATION 424 – Page 188

ATTACHMENT 5
PATH AND TERMINATOR

4.0 STANDARD INSTRUMENT DEPARTURE (SID) CODING RULES

4.1 The following rules cover the altitude coding requirements of the initial leg of a departure:
If a published take-off requires a turn of greater than 15 degrees from the runway bearing, code a CA, VA
or FA leg on the runway bearing/heading to an altitude of 400 feet above the airport elevation (AFE).

If a published take-off is straight ahead or requires a turn of less than 15 degrees and is to a fix such as a
waypoint, Navaid, or DME distance termination, code an altitude on that fix when included in the
government source, otherwise no altitude is coded.

If a published take-off is straight ahead or requires a turn of less than 15 degree and is to a specified
altitude termination, code the appropriate leg type (VA, FA, CA) to that altitude.

The altitude description on a coded altitude, either a termination or at a fix, may be “at,” “at or above,” “at
or below” and “at or below to at or above.”

4.2 For the first leg of a SID, course legs (“CX” or “FX”) are preferred over heading legs unless the source requires
that heading legs be coded.

4.3 The use of FM or VM leg types in the first leg of a SID Runway Transition for Route Types of 0, 1 and 4 or F
is permitted when the initial heading is defined in the source.

4.4 If a SID ends in vectors, the heading for the FM or VM leg must be based on source documentation.

4.5 If the last fix of a SID sequence or SID Enroute Transition sequence is a fix on an Enroute Airway, the
Waypoint Description Code in the Enroute Airway record for that fix must designate that fix as “Essential” or
“Transition Essential.”

4.6 SID Enroute Transition legs will be coded using TF legs where possible to simplify coding. This rule does not
apply if the use of TF legs would require the creation of additional waypoints.
4.7 SID Enroute Transitions published in source documentation but wholly contained in other SID Enroute
Transitions will not be coded separately.

4.8 All waypoints used in SID common or Vector SIDs must be in the Enroute Waypoint File as an Off-Route
Intersection unless the waypoint is also used for Enroute Airway Coding.

4.9 A SID which consists of a single path from an origination fix to a termination fix will be coded as a Route Type
2 or 5 or M.

4.10 A SID which consists of Enroute Transitions only can be coded with a single IF leg as a Route Type 2 or 5 or
M, followed by the required Route Type 3 or 6 or S coding. The fix on which the IF leg is coded must be the
first fix in all of the Enroute Transitions. The Transition Identifier must be coded in accordance with Chapter
Five, Section 5.11.

4.11 For Vector SIDs which consist of Enroute Transitions only, the coding must be a Runway Transition Route
Type “V,” followed by the Enroute Transition(s), Route Type “T.” The Enroute Transition(s) must be an IF/DF
leg combination with the Airport as the fix in the IF leg and the first fix of the Enroute Transition as the fix in
the DF leg. The DF leg must carry a distance value equal to the total distance between the Airport and the fix
along the approximated path.

4.12 When a SID Route or portion of a SID Route is repeated with different Runway Identifiers in the Transition
Identifier, it must be coded as a Runway Transition Route Type of 1 or 4 or F or V (Vector SID). When a SID
Route is repeated with different fix identifiers in the Transition Identifier, it must be coded as an Enroute
Transition, Route Type of 3 or 6 or S or T (Vector SID).

4.13 “Engine Out” SIDs must be coded as Route Type “0” only. Route Type “0” is not used in combination with
other SID Route Types. The Runway Transition Identifier must contain a specific Runway Identification or
Helipad Identification. All other rules for Route Type 1 and 4 apply in the coding of Route Type “0.”
 ARINC SPECIFICATION 424 – Page 189

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 1

The copyrighted material in the following SID Not for navigational or other operational
coding examples is reproduced with the use. For example only. Please consult
permission of the copyright holder Jeppesen current navigation charts.
Sanderson, Inc, Englewood, Colorado.
ARINC SPECIFICATION 424 – Page 190

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 2

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
 ARINC SPECIFICATION 424 – Page 191

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 3

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
ARINC SPECIFICATION 424 – Page 192

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 4

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
 ARINC SPECIFICATION 424 – Page 193

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 5

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
ARINC SPECIFICATION 424 – Page 194

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 6

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
 ARINC SPECIFICATION 424 – Page 195

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 7

Not for navigational or other operational
use. For example only. Please consult
current navigation charts.
 ARINC SPECIFICATION 424 – Page 196

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 8

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
 ARINC SPECIFICATION 424 – Page 197

ATTACHMENT 5
PATH AND TERMINATOR

SID CODING EXAMPLE 9

Not for navigational or other operational

use. For example only. Please consult
current navigation charts.
ARINC SPECIFICATION 424 – Page 198

ATTACHMENT 5
PATH AND TERMINATOR

5.0 Standard Terminal Arrival Route (STAR) Coding Rules

5.1 If a STAR ends in vectors to a final approach (VM leg), the Airport Reference Point Record will be coded in the
Waypoint Ident field of the STAR Record.
5.2 If a STAR ends in a sequence which aligns the aircraft inbound on the localizer course, the termination of the
STAR sequence must be the Waypoint defined as the FACF for the localizer based Approach Procedure.
5.3 If a STAR or Profile Descent does not begin at a fix in the source documentation, the closest named fix along
the STAR or Profile Descent track must be assigned as the initial fix (IF leg) for the STAR or Profile Descent.
5.4 If no crossing altitudes are specified on intermediate fixes of a STAR or Profile Descent, a “vertical angle” will
be coded in the last leg of the procedure. This angle will be computed, based on the altitudes specified at the
end fixes, to provide a constant descent path through all intermediate fixes. The angle provided will ensure
compliance with minimum enroute altitudes for those segments without assigned altitudes.

5.5 A STAR or Profile Descent which consists of a single path from an origination fix to a termination fix will be
coded as a Route Type 2 or 5 or 8 or M.

5.6 When a STAR Route/Profile Descent Route or portion of a STAR Route/Profile Descent Route is repeated with
different Runway Identifiers or different Helipad Identifiers in the Transition Identifier it must be coded as a
Runway Transition Route Type 3 or 6 or 9 or S. When a STAR Route/Profile Descent Route or portion of a
STAR Route/Profile Descent Route is repeated with different Fix Identifiers in the Transition Identifier, it must
be coded as an Enroute Transition Route Type 1 or 4 or 7 or F.

5.7 When an Arrival Route serves the same runway or helipad as an Approach Route and the Arrival Route
overlaps an Approach Transition, both the Arrival Route and the Approach Transition will be coded in their
entirety in accordance with source documentation.
 ARINC SPECIFICATION 424 – Page 199

ATTACHMENT 5
PATH AND TERMINATOR

STAR CODING EXAMPLE 1

The copyrighted material in the following Not for navigational or other operational
STAR coding example is reproduced with the use. For example only. Please consult
permission of the copyright holder Jeppesen current navigation charts.
Sanderson, Inc, Englewood, Colorado.
ARINC SPECIFICATION 424 – Page 200

ATTACHMENT 5
PATH AND TERMINATOR

STAR CDOING EXAMPLE 2

The copyrighted material in the following Not for navigational or other operational
STAR coding example is reproduced with use. For example only. Please consult
the permission of the copyright holder current navigation charts.
Jeppesen Sanderson, Inc, Englewood,
Colorado.
 ARINC SPECIFICATION 424 – Page 201

ATTACHMENT 5
PATH AND TERMINATOR

STAR CODING EXAMPLE 3

The copyrighted material in the following Not for navigational or other operational
STAR coding example is reproduced with use. For example only. Please consult
the permission of the copyright holder current navigation charts.
Jeppesen Sanderson, Inc, Englewood,
Colorado.
ARINC SPECIFICATION 424 – Page 202

ATTACHMENT 5
PATH AND TERMINATOR

STAR CODING EXAMPLE 4

The copyrighted material in the following

STAR coding example is reproduced with Not for navigational or other operational
the permission of the copyright holder use. For example only. Please consult
Jeppesen Sanderson, Inc, Englewood, current navigation charts.
Colorado.
 ARINC SPECIFICATION 424 – Page 203

ATTACHMENT 5
PATH AND TERMINATOR

6.0 Approach Procedure Rules Valid For All Procedure Types

6.1 Multiple Approach Procedure Coding

6.1.1 Multiple Approach Procedure Definition

1. ILS Localizer 8. RNAV 15. RNAV, GPS Required
2. IGS Localizer 9. VORDME 16. FMS
3. LDA Localizer 10. VORTAC 17. GPS
4. SDF Localizer 11. VOR (no DME) 18. LAAS-GPS/GLS
5. Localizer (Only) 12. TACAN 19. WAAS-GPS
6. Localizer Backcourse 13. NDB + DME
7. MLS (all types) 14. NDB

Notes: GPS, GLS, RNAV, LAAS, and WAAS are not facility types but rather an equipment classification. RNAV
procedures use VORDME or VORTAC navaids along with the RNAV equipment. For the purpose of these
rules, RNAV is to be considered a facility type. This will allow coding of a RNAV and VORDME or VORTAC
procedure to the same runway or helipad. For GPS, GLS, WAAS, and LAAS a GPS or GLS sensor input to the
equipment is required.

Circle to Land minimum version of the various approach sensors are covered through the Approach Route
Qualifier (see Section 5.7). Circle-To-Land is not a facility type but rather a weather minimum criteria. For the
purpose of these rules, Circle-To-Land is to be considered an equal to the procedure reference facility. This will
normally rule out coding of “straight-in” and “circling” procedures using the same reference facility to one and
the same runway or helipad, even though different “Route Types” are involved.

There are three types of MLS Approach, each with a unique Route Type. Normally, there will only be one
approach referencing MLS to any given runway or helipad.

6.1.2 Multiple Approach Procedure Identifiers

Multiple approach procedures are identified by unique procedure identifiers and unique route types (refer to
Sections 5.7 and 5.10 of this specification).

6.1.3 Multiple Approach Procedure Waypoints

Multiple approach procedures to one and the same runway or helipad may require multiple final approach
segment waypoints of the same category such as FACF, FAF and missed approach point. Where such
waypoints are not established with unique identifiers through source documentation, the data base supplier must
create the required waypoints and assign unique identifiers, using Section 7.2.6 of this specification.

6.1.4 Multiple Approach Procedure Detail

Specific details of approach procedures such as speed, altitudes and vertical angles are considered unique for
the procedure and must be coded in those records where they apply, including duplication of such detail where
appropriate.

6.1.5 Transitions in Multiple Approach Procedure Coding

6.1.5.1 Approach transitions are coded to be used together with specific approach procedures. As such, a transition
route must be unique to a given approach, “multiple use” with more than one approach cannot be coded.
Transition routes required for more than one approach must be coded multiple times.

6.1.5.2 If an approach transition route is be coded multiple times, it must be coded with an identifier that is unique to
the approach procedure for which it is to be used.
ARINC SPECIFICATION 424 – Page 204

ATTACHMENT 5
PATH AND TERMINATOR

6.2 General Rules, applicable to all Approach Route coding.

6.2.1 “Altitudes” used in approach route coding between the final approach course fix (FACF) and the runway or
helipad or missed approach point will be coded in combination with Altitude Description Codes as detailed in
Section 5.29 of this specification and in accordance with government source documents. This coding rule is
intended to match the altitude publishing methods in official government sources, which may specify altitudes
as minimum, maximum, mandatory, recommended, or between altitudes, defined with a minimum and a
maximum altitude.

These definitions include two kinds of altitudes. One is “procedural altitudes” information on mandatory or
minimum altitudes at designated fixes along the final approach path. The other is the altitude related to the
electronic Glide Slope or published vertical angle with recommended altitudes. The ordering of Procedural and
Glide slope altitudes in the first and second altitude fields is accomplished in accordance with Section 5.29.

6.2.2 All fixes associated with the lateral and vertical path of approach procedures must be coded, including step-
down fixes, both before and after the Final Approach Fix.

6.2.3 With the exception of the NDB + DME Approach or a Helicopter version of a NDB + DME Approach, the
recommended Navaid must be the same facility for all legs of a final approach (missed approach sequences not
included) that require a recommended facility. The recommended Navaid must be the procedure reference
facility. For Approach Transition Routes, the recommended Navaid will be the procedure reference facility or a
VORDME or VORTAC facility. When a VORDME or VORTAC is coded as the recommended Navaid in
approach procedure coding, the Navaid will be within 40 NM of the fix in which it is coded. GPS approach
procedures do not include a recommended Navaid. GLS approach procedures will reference the GLS facility.
For specific rules on recommended Navaid for NDB + DME Approach Procedures, see Rule 6.8.1.4.b of this
Attachment.

6.2.4 If a PI leg is from the FAF waypoint and the distance between the FACF and the FAF is less than 6.0 NM, code
a CF leg after the PI, with the FACF as the fix in the CF. The route distance leg data field on the CF leg will be
the difference between the distance coded on the PI leg and the distance between the FACF and FAF
waypoints.

6.2.5 Approach Procedure Fix Requirements:

- All approach procedure coding requires a Final Approach Fix (FAF) and a Missed Approach Point Fix
(MAP).
- The coding of Final Approach Course Fix (FACF) must be accomplished using the following rules:
- A FACF Waypoint is required on all localizer based approaches, including, ILS, LOC, SDF, LDA,
IGS and LOC Backcourse.
- A FACF Waypoint is required on all other Approach Procedure coding:
- At a published Intermediate Fix
- When published by source
- When a named fix at common ending point for transitions exists
- When transitions end in the intercept of a track rather than to a fix.
When the course or track inbound to the FAF is different than the course or track from the FAF to
the MAP. This requirement will be met by the addition of data supplier created FACF waypoints
as indicated in Rule 6.2.5.2.

6.2.5.1 Transitions may end at a FAF fix regardless of whether a FACF is coded for the procedure or not.

6.2.5.2 If no waypoint is established by source documentation for the final approach course fix and one is required by
the requirements in Rule 6.2.5, one must be computed by the data supplier. For Localizer based approach
procedures, the computer FACF will be on the localizer course at a distance of 2 to 8NM from the Final

Approach Fix (FAF). For all other approach types, the FACF will be computed on the published course to the
FAF at a distance not less than 2NM to the FAF. See Section 2, Subsection 2.3, Special Navigation Terms.
Altitude coding for this fix is defined in Rule 6.2.10.
 ARINC SPECIFICATION 424 – Page 205

ATTACHMENT 5
PATH AND TERMINATOR

6.2.5.3 If no waypoint is established by source documentation for the Final Approach Fix (FAF), one must be computed
on the final approach course, using the initial approach altitude and the vertical descent angle (source or
computed). For non-precision approach procedures such as VOR or NDB, the minimum distance between the FAF
and the runway threshold or helipad alighting point (or MAP) will be 4 nautical miles. For Localizer and GLS
based approach procedures, establish the FAF, when none is provided by source, at the nominal outer marker
position.

6.2.5.4 Except as indicated below, the published Missed Approach Point (MAP) is always coded as part of the approach
procedure. This fix may be a runway threshold, helipad alighting point or a dedicated missed approach point fix
waypoint. The published missed approach point may be replaced by a database supplier fix when it can be
determined that the published fix is within 0.14NM of the landing threshold or helipad alighting point on the
centerline or extended centerline. If the published MAP is a Navaid and is within 0.14NM of the threshold or
helipad alighting point, the MAP will remain at the Navaid position. In these cases, the altitude assigned to the
MAP will be a calculated altitude that is on a path that continues over the threshold at 50 feet. Such an altitude
constraint must not be below the threshold/alighting point elevation.

6.2.6 Straight-in Criteria, FAA type procedures

Refer to Appendix 2

6.2.7 Straight-in Criteria, ICAO type procedures

Refer to Appendix 2

6.2.8 Intentionally left blank

6.2.9 Lateral Coding Rules

All approach procedure coding must be to the published Missed Approach Point, as indicated below. Missed
Approach Procedure coding must begin at that point. For missed approach procedure coding, refer to Section
Nine of this Attachment. For the rules that follow, the term “runway threshold” is meant to refer either to the
landing threshold point (LTP) of an actual runway or to a helipad alighting point (HAP), when the procedure is
coded to a helipad.

6.2.9.1 If the published Missed Approach Point is a fix prior to the runway threshold, lateral coding is to that published
Missed Approach Point.

6.2.9.2 If the published Missed Approach Point is the runway threshold, lateral coding is to the runway threshold as the
published Missed Approach Point.

6.2.9.3 If the published missed approach point is beyond the runway threshold and the runway threshold will be coded
as a fix in the lateral path that fix will be on the established path, with no course changes.

6.2.9.4 If the published Missed Approach Point is beyond the runway threshold and no runway threshold fix has been
inserted into the lateral path, code a “Final End Point,” which is calculated at a location on the final approach
track where a line from the runway threshold intersects the track at a 90 degree angle. Lateral coding will still
be to the published missed approach point.
6.2.9.5 If the published Missed Approach Point is abeam the runway threshold, lateral coding must be to the published
Missed Approach Point.

Refer to the Examples 1 through 15 at the end of this section for a visual depiction of these rules.

6.2.10 Vertical Coding Rules, Procedure Fix Altitudes

Vertical Approach Procedure Coding is provided through two elements, Procedure Fix Altitudes and a Vertical
Angle. This section covers the Fix Altitude. Sections 7 and 8 cover the Vertical Angle for Precision and Non-
Precision Approach Procedures.
ARINC SPECIFICATION 424 – Page 206

ATTACHMENT 5
PATH AND TERMINATOR

6.2.10.1 Procedure Fix Altitudes, Final Approach Course Fix and Final Approach Fix.

Procedure Fix Altitudes for the Final Approach Course Fix will be coded according to official government
sources and will be left blank when no altitude data is provided by the source. When coded, these altitudes
will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or recommended
(see Section 5.29 of this Specification). When the coded Final Approach Fix is established by the government
source procedure data, the altitudes for this fix will also be coded according to official government sources.
These altitudes will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or
recommended (see Section 5.29 of this Specification). For government supplied altitude data, both Altitude 1
and Altitude 2 may be provided. If the Final Approach Fix is as an established fix rather than a published fix,
the altitude for this fix must be computed using the procedures detailed in Sections 7 and 8 of this
Attachment. For calculated altitude data, only Altitude 1 will be provided.

6.2.10.2 Procedure Fix Altitudes for the published Missed Approach Point, a runway threshold fix prior to the
published Missed Approach Point or a Final End Point prior to the Missed Approach Point must be as
indicated below.

6.2.10.2.a For a published Missed Approach Point prior to the runway threshold, an “at” altitude equal to the computed
altitude at the published Missed Approach Point must be coded in Altitude 1. (See example 7)

6.2.10.2.b For a published Missed Approach Point at the runway threshold, an “at” altitude equal to the runway
threshold elevation plus the published TCH must be coded in Altitude 1. If TCH is not specified by source
then use 50 feet.

6.2.10.2.c For a Missed Approach Point beyond the runway threshold and where the runway threshold has been
included in the lateral path, code an”at” altitude equal to the runway threshold elevation plus the published
TCH. If TCH is not specified by source then use 50 feet in Altitude 1 of the runway threshold fix record. Do
not code an altitude on the MAP for this case.

6.2.10.2.d For the Missed Approach Point beyond the runway threshold and if a Final End Point is coded, then code an
“at” altitude for the Final End Point equal to the runway threshold elevation plus the published TCH in
Altitude 1 of the Final End Point Record. If TCH is not specified by source, then use 50 feet. Code an “at or
above” altitude on the MAP record equal to the airport elevation plus 400 feet or a value specified by source.

6.2.10.2.e For a published Missed Approach Point abeam the runway threshold, code the altitude equal to the runway
threshold elevation plus the published TCH. If TCH is not specified by source then use 50 feet.

6.2.10.3 Step down fixes will have altitude codes according to the government source documentation. These altitudes
will be assigned altitude descriptions codes indicating the altitude as mandatory, minimum or recommended
and altitudes on the vertical path (see Section 5.29 of this Specification). Both Altitude 1 and Altitude 2 will
be used on step-down fixes.

6.2.11 Vertical angle information is in Section 7 and 8 of Attachment 5 in this document.

6.2.12 Missed Approach Point

In general, the design of missed approach procedures require that the runway, helipad or missed approach
point be overflown prior to commencing any turn. In these cases, to ensure procedure coding reflects design
specific intentions, the Overfly Indication must be coded into the Waypoint Description field. However,
certain types of approach procedures design do require a turn prior to the runway, helipad or missed approach
point. In these cases, to ensure procedure coding reflects design specific intentions, the Overfly Indication
will not be set in the Waypoint Description field of the appropriate record.

6.3 Approach Transition Route Coding Rules

6.3.1 Recommended coding on approach transitions that end in leg to fix (“XF”) is that the fix in the ending leg
must be either the Final Approach Course Fix or the Final Approach Fix. If this is not the case, for example
HF leg type transitions on fixes off-set from the final approach 1
path, a series of legs must be substituted
representing the original flight path, but ending with a CF or TF leg type to one of these two fixes. If neither
of these two coding recommendations can be followed, such as in cases where the “XF” would terminate at

1
In general “CF” legs are used in final approach coding. “TF” legs are used in FMS and GPS Approach Procedures,
some types of MLS Procedures and in other procedure types where the determination has been made that a TF will
work better than a CF.
 ARINC SPECIFICATION 424 – Page 207

ATTACHMENT 5
PATH AND TERMINATOR

the missed approach waypoint or a step-down fix not associated with the lateral guidance of the final
approach, the transition must be omitted.

6.3.2 When a holding pattern used for course reversal or a procedure turn is part of an approach route, it will be
included in an approach transition route.

6.3.3 If an approach transition for a specific runway or helipad is common to more than one approach, that
transition must be coded for each approach, with a transition identifier that must correspond to the approach
procedure identifier.

6.3.4 Rule Deleted by Supplement 16

6.3.5 Transitions of VOR based approach procedures, TACAN based approach procedures, and RNAV approach
procedures.

6.3.5.1 Any recommended navaid used in coding must be a VOR, VORDME, VORTAC, TACAN, DME, NDB or
Un-Biased ILS DME, see Section 5.23 of this document.

6.3.6 Transitions for Localizer Based Approach Procedures

6.3.6.1 The ending leg of all localizer-based transitions will either –

- end at the FACF (AF, CF, RF, TF, HF, HM)

- end in an intercept of the localizer inside the FACF (PI, CI or VI)
- end in a course reversal, normally at the FAF (HF, HM)

6.3.6.2 The ending leg of all localizer-based transitions will contain a recommended Navaid –

- if CF, RF, TF, CI or VI, the recommended Navaid will be the procedure reference localizer
- if AF, HF, HM or PI, the recommended Navaid will be a VORDME or VORTAC or TACAN
- the HF, HM and PI leg may use the procedure reference localizer when a VORDME, VORTAC or
TACAN is not available.
6.3.6.3 Deleted by Supplement 17.

6.3.6.4 Legs ending in an intercept will ideally be at angles of 30 degrees to the track intercepted. Angles between 10
and 90 degrees may be coded as required by source documentation, provided the resulting intercept is within
the reception area of the localizer.
ARINC SPECIFICATION 424 – Page 208

ATTACHMENT 5
PATH AND TERMINATOR

6.3.6.5 When a CF leg is used as the ending leg of a transition to a localizer-based procedure, the maximum leg
distance will be within 8NM of the FACF or within the reception area of the localizer as depicted in Figure A5-
6-1.
Note: An FC/CF is preferred over a TF as illustrated in Figure A5-6-1 for those legs ending at a fix.

CF LEG
8 MILES OR LESS
FACF

4 MILES
OR

Figure A5-6-1

6.3.6.6 When a CI or VI leg is used as the ending leg of a transition to a localizer-based procedure, the intercept will be
between the FACF and the FAF, at no less than 2 NM to the FAF.

6.3.7 Transitions for NDB Based Approach Procedures:

6.3.7.1 Transitions for NDB based approach procedures may use a NDB Navaid as the recommended Navaid, except
for transitions that are DME Arcs.

6.3.8 Transitions for MLS/GLS Approach Procedures:

6.3.8.1 MLS/GLS approach procedure coding is such that the rules can be identical to those used for Localizer based
procedure coding.

6.3.9 Transitions for Circle-To-Landing Approach Procedures

6.3.9.1 If the Circle-To-Land approach procedure is runway or helipad dependent, the rules on transition route coding
are identical to those of the reference facility procedure type, e.g. for a VOR Circle-To-Land that is runway
dependent, follow the VOR based approach procedure rules for approach transition route coding.

6.3.9.2 If the Circle-To-Land approach procedure is not runway or helipad dependent, being valid for more than one
landing direction, the rules for coding approach transitions routes are as follows.

6.3.9.3 Recommended navaids used in coding all legs except ending legs must be a VOR, VORDME, VORTAC, DME
or Un-Biased ILSDME. For the ending leg sequences, the recommended navaid, where required, must be the
procedure reference facility, see Section 5.23 of this document.
6.4 Localizer Based Approach Procedure Coding

6.4.1 The following rules apply to the coding of the “final approach segment” of all Localizer based approach
procedures. Localizer based approach procedures include Full ILS (Localizer and GS), Localizer only, IGS
(Instrument Guidance System), LDA (Localizer type Directional Aid) and SDF (Simplified Directional Aid)
procedures.

6.4.1.1 All Localizer based approach procedures must begin at the FACF. They must consist of a FACF, FAF and
runway Fix (precision approach) or missed approach point fix (non-precision approach). A Runway Centerline
Intercept (RCI) point may be coded in some non-precision, Localizer based procedures.

6.4.1.2 The FACF is defined as a fix located on the localizer beam center, 8NM or less from the FAF or within the
reception range of the Localizer. This may be a source document provided fix or a fix created using these
positioning rules.
 ARINC SPECIFICATION 424 – Page 209

ATTACHMENT 5
PATH AND TERMINATOR

6.4.1.3 The FACF is coded as an IF leg with an altitude assigned, based on the source document or equal to the altitude
of a procedure turn or the altitude of the last transition leg.

6.4.1.4 The track from the FACF to the FAF is coded as a CF or a TF leg with altitude constraints as indicated for the
specific procedure types below.

6.4.1.5 The recommended navaid will be the procedure reference localizer. Theta and Rho will be provided from the
localizer for each sequence of the final approach, including the runway fix and/or missed approach point.

6.4.1.6 The “Outbound Magnetic Course” field in all sequences will be equal to the localizer magnetic bearing,
rounded to the nearest whole degree, derived from official government source.

6.4.2 Full ILS (Localizer and Glide Slope) Precision Approach Procedure

6.4.2.1 For full ILS procedures, code the glide slope intercept altitude in the altitude 2 field of the FACF record, if an
intercept altitude is required. If the procedure requires a constant descent from the FACF to the runway, then
altitude 2 will be blank.

6.4.2.2 For full ILS procedures, a missed approach point beyond the runway is not allowed, therefore rules 6.2.9.3,
6.2.9.4, 6.2.9.5, 6.2.10.2.c, 6.2.10.2.d, and 6.2.10.2.e do not apply.

6.5 MLS Approach Procedure Coding

MLS Approach Procedure Code utilizing raw azimuth and elevation data is limited to those procedures which
are designed as a localizer equivalent. If such a procedures is coded, the rules for the “final approach
segments” are to be identical with those stated in Section 6.4 above. The Route Type of such approaches will be
coded as “M” in column 20 of the primary approach record. Approach procedures predicated on the use of MLS
Area Navigation (MLS/RNAV) will be coded with a “W” or “Y” in column 20 of the primary approach record.
MLS/RNAV approaches are coded as described below.

There are three types of MLS/RNAV approaches, listed in increasing level of complexity, computed lateral/raw
vertical guidance, computer lateral and vertical guidance and curved path.

6.5.1 Approaches using computed lateral path and raw vertical path guidance, also referred to as Type “A,” will be used
primarily where the MLS azimuth transmitter cannot be located on the extended runway centerline, but the
elevation transmitter is sited normally abeam the touchdown point. All legs will be straight and aligned with the
inbound course. The will be codes with Route Type “W” in column 20 of the primary approach record. Path
definition will be the equivalent of a full ILS approach (Rule 6.4.2) with the exception that the leg from the PFAF
inbound will be a “TF” leg, terminating at the runway waypoint, with the published final approach source in the
Outbound Magnetic Course field. The PFAF will be coded as the Final Approach Fix in the Waypoint Description
field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.

6.5.2 Approach using computed lateral and vertical guidance by no curved legs, also referred to as Type “B,” will be
coded as Route Type “Y” in column 20 of the primary approach record. All legs will be straight and aligned with
the inbound course. Path definition will be the equivalent of the full ILS approach (Rule 6.4.2) with the exception
that the leg from the PFAF inbound will be a “TF” leg, with the published final approach course in the Outbound
Magnetic Course field. The altitude of the PFAF and all waypoints inbound from it will be the glide path altitude
at that point. The PFAF will be coded as the Final Approach Fix in Waypoint Description field and the first fix
prior to the PFAF will be coded as the Final Approach Course Fix.

6.5.3 MLS/RNAV approaches using curved legs, also referred to as Type “C,” will be used for a variety of reasons,
including parallel sidestep approaches, separation of different categories of aircraft, noise abatement, etc. These
will always be precision approaches. They will be coded a with a Route type of “Y” in column 20 of the primary
approach record. The following rules apply:
ARINC SPECIFICATION 424 – Page 210

ATTACHMENT 5
PATH AND TERMINATOR

6.5.3.1 The first leg of an MLS/RNAV approach with curved legs will be an “IF/TF” leg combination. All other straight
legs will be coded as “TF” legs. All “TF” legs in an MLS/RNAV with curved legs procedure will have the
published course included in the Outbound Magnetic Course field.

6.5.3.2 All curved legs will be coded as “RF” legs. Every leg preceding or following an “RF” leg will be tangent to the
“RF” leg at that point.

6.5.3.3 The initial portion of a MLS/RNAV approach with curved legs may be an “IF/RF” combination provided a
straight leg approach transition is coded to the point in the “IF” and the rules in Section 6.5.2 are complied with.

6.5.3.4 The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to the
PFAF will be coded as the Final Approach Course Fix. If there is not a fix at the glide path intercept, then the first
fix after the intercept will be the PFAF. There must be one and only one PFAF for each MLS/RNAV approach
with curved legs.

6.5.3.5 The last leg of an approach transition prior to an MLS/RNAV approach will be one of the following types CF, CI,
HF, PI, RF or TF, except as indicated in Section 6.5.3.3. If the leg type is CF, CI, RF or TF, then the
Recommended Navaid will contain the identifier of the MLS used for the approach. If the leg type is PI or HF,
then the Recommended Navaid will contain the VHF Navaid the defines the PI or HF leg.
6.5.3.6 If the last leg prior to the approach is a “CI” leg, the intercept angle will be 300 or less, and the intercept point will
be between the first and second terminator fixes in the approach, but no closer that 2NM to the second fix.

6.5.3.7 The PFAF and the FACF altitudes will be coded according to the rules outlined for Precision Approach
Procedures in Rule 6.4.2.

6.5.4 The PFAF will be used in precision MLS/RNAV approaches. It is defined as that fix along the lateral path where
the published barometric altitude intercepts the glide slope. Prior to the PFAF, the aircraft is expected to fly
barometric altitude to intercept the glide path. All waypoints up to the PFAF should be coded using the published
barometric crossing altitude. The PFAF and all waypoints after it should be coded using the true altitude of the
glide path at those points.

6.6 VOR, VORDME, VORTAC and RNAV Approach Procedure Coding

The following rules apply to the coding of the “final approach segment” of all VOR based approach procedures,
regardless of the reference facility type, and to RNAV Procedures.

6.6.1 Reference Facility Specific Rules

The following rules apply to the coding of the “final approach segment” of specific reference facility VOR
based approach procedures.

6.6.1.1 When the reference facility is VOR only or there is no DME collocated with VOR (see VOR coding examples
1, 3 and 8), the following applies:

6.6.1.1.a Final approach segments will be coded using IF and CF or TF legs only.
6.6.1.1.b Final approach must include either a FAF and a runway fix or FAF and missed approach point fix.

6.6.1.1.c The recommended navaid will be the procedure reference VOR. Theta values will be provided from that facility
in all final approach sequences.

6.6.1.2 When the reference facility is VORDME or VORTAC (see VOR coding examples 2 and 6), the following
applies:

6.6.1.2.a Final approach segments will be coded using IF and CF or TF legs only.

6.6.1.2.b Final approach must include FACF, FAF and either a runway fix or missed approach point fix. The final
approach will include a FACF when one is required by Rule 6.2.5.

6.6.1.2.c The recommended navaid will be the procedure reference VORDME or VORTAC. Theta and Rho values will
be provided from that facility in all final approach sequences.

6.6.2 Examples of VOR Coding

6.6.2.1 Example of missed approach point before the runway threshold, refer to VOR coding examples 7 and 8.
 ARINC SPECIFICATION 424 – Page 211

ATTACHMENT 5
PATH AND TERMINATOR

6.6.2.2 Example of missed approach point at the runway threshold, refer to VOR coding example 1 and 2.
6.6.2.3 Example of missed approach point beyond the runway threshold and the final course passes over the runway
threshold, refer to VOR coding examples 3 and 4.

6.6.2.4 Example of missed approach point beyond the runway threshold and the final approach course does not cross
runway threshold, refer to VOR coding examples 5 and 6.
6.6.3 RNAV Procedures

6.6.3.1 All RNAV approach procedures will be coded to a runway threshold or missed approach point as the last leg in
the final approach.

6.6.3.2 The recommended navaid for VORDME RNAV approaches will be the procedure VORDME or VORTAC.
Theta and Rho values will be provided from that facility in all final approach sequences.

6.6.3.3 Final approach segments will be coded using IF and CF or TF legs only. RF legs may be used in the final
approach segment of RNAV approaches.

6.6.3.4 Final approach must include either a FAF and a runway fix or FAF and missed approach point fix.

6.7 TACAN Approach Procedure Coding

When the reference facility is TACAN (see VOR coding example 9), the following applies.

6.7.1 Final approach segments will be coded using IF and CF or TF legs only.

6.7.2 Final approach must include FACF, FAF and either a Runway Fix or Missed Approach Point Fix.

6.7.2.1 Final approach segments will be coded using IF and CF or TF legs only.

6.7.2.2 Final approach must include FAF and either a Runway Fix or Missed Approach Point Fix. The final approach
will include a FACF when one is required by Rule 6.2.5.

6.7.3 The Recommended Navaid will be the procedure reference TACAN. Theta and Rho values will be provided
from that facility in all final approach sequences.

6.7.4 Vertical Angle Rules

Vertical angle will be coded per the rules in Section 6.2.11.

6.8 NDB Approach Procedure Coding

The following rules apply to the coding of the “final approach segment” of all NDB based approach procedures.
NDB based approach procedures include procedures using a NDB or Locator as the reference facility and
procedures using a NDB or Locator and a DME (NDB + DME) as reference facilities. NDB approach
procedures not requiring DME but using the DME for reduced minimums will be coded as NDB + DME
procedures.

6.8.1 Specific Reference Facility Rules

The following rules apply to the coding of the “final approach segment” of specific reference facility NDB
based approach procedures.

6.8.1.1 NDB approach procedures must include at least FAF and a runway fix or missed approach point fix.
6.8.1.1.a Rule deleted by Supplement 17.

6.8.1.2 NDB + DME approach procedures must include a FAF and runway fix or missed approach point fix. The final
approach will include a FACF when one is required by Rule 6.2.5.

6.8.1.3 Coding will use IF and CF or TF legs only through to the runway fix or missed approach point fix. The IF leg
will be at the FAF or FACF when coded.
ARINC SPECIFICATION 424 – Page 212

ATTACHMENT 5
PATH AND TERMINATOR

6.8.1.4 Recommended Navaid Requirements

6.8.1.4.a On NDB procedures, the recommended navaid information will be provided on the FACF (where coded), the
FAF and the Missed Approach Fix record. It will be the procedure reference NDB or Locator. Theta and Rho
information will not be provided on any sequence.

6.8.1.4.b On NDB + DME procedures, the recommended navaid information will be provided on all sequences. On the
FACF (when coded) and FAF, this navaid will be the procedure reference NDB or Locator. On the runway fix
or missed approach point fix, the recommended navaid will be the procedure reference DME. A procedure
reference DME may be any navaid with DME, including ILSDMEs. The Theta and Rho information will not be
provided in any sequence of the NDB + DME final approach except in the runway fix or missed approach point
fix sequence. That sequence will include Rho information from the procedure reference DME Navaid.

6.8.2 Examples of NDB Coding

6.8.2.1 Example of missed approach point before the runway threshold, refer to NDB coding example 4.

6.8.2.2 Example of missed approach point at the runway threshold, refer to NDB coding example 1.

6.8.2.3 Example of missed approach point beyond the runway threshold and the final course passes over the runway
threshold, refer to NDB coding example 2.

6.8.2.4 Example of missed approach point beyond the runway threshold and the final approach course does not cross
runway threshold, refer to NDB coding example 3.

6.9 Loran Coding rules Deleted by Supplement 14

6.10 Circle-To-Land Approach Procedure Coding

6.10.1 Circle-To-Land approach procedures may be coded for the following types of specific reference facilities:

a. Localizer Only
b. Localizer Backcourse
c. IGS Procedure
d. LDA Procedure
e. SDF Procedure
f. VOR Procedure
g. NDB Procedure

6.10.2 Circle-To-Land approach procedures may be coded referencing a specific runway or not referencing a specific
runway. Coding rules to be followed are:

6.10.2.1 Use the coding rules for the reference facility type if the circle-to land is runway dependent.

6.10.2.2 The Circle-To-Land coding rules if the circle-to-land is not runway dependent.

6.10.3 The following are the Circle-To-Land coding rules for all types of valid reference facilities:

6.10.3.1 The last segment in the final approach sequence will be the missed approach point fix.
6.10.3.2 The Altitude 1 value in the missed approach point fix segment will be the highest published OCH(A) or MDA
for the procedure.

6.10.3.3 The vertical angle information will be in the missed approach point fix segment and will be coded as “0.00.”

6.11 FMS and GPS Procedure Coding

The following rules apply to the coding of the “final approach segments” of all FMS and GPS Approach
Procedure Coding.

6.11.1 Lateral Guidance Rules

For FMS and GPS procedures, a missed approach point beyond the runway is not allowed, therefore Rules
6.2.9.3, 6.2.9.4, 6.2.9.5, 6.2.10.2.c, 6.2.10.2.d, and 6.2.10.2.e do not apply.
 ARINC SPECIFICATION 424 – Page 213

ATTACHMENT 5
PATH AND TERMINATOR

6.11.2 The track from the FACF to the FAF, where an FACF exists, is coded with TF or RF legs. The RF leg is not
allowed as the first leg of the approach coding according to the Beginning/Ending Leg Table. The preferred
coding when an approach starts with a precision arc is “IF” at the FACF, followed by “RF” to the FAF.
According to the rules on “RF” legs, this will require that a straight line, fix terminated approach transition to
the FACF has been included. The track in the transition must be tangent to the arc and the fix at the end of the
transition must be overflown. The rule also does not exclude the use of an RF leg in between FAF and the final
TF leg of the approach. Such RF legs will be coded with the 4th character of the Waypoint Description field
blank.

6.12 Helicopter Procedure Coding

The following rules apply to the coding of the “final approach segment” of all Helicopter Approach Procedure
Coding. These rules cover Helicopter Approach Procedures which may be coded to Airports and Runways
included in Sub-sections PA and PG only.

6.12.1 Helicopter Approach Procedures will be coding using the rules in Section 6 of this Attachment, appropriate to
the type of sensor required for the procedure, such as VORDME or ILS or RNAV. This includes rules for
Recommended Navaid, FACF requirements and leg types.

6.12.2 The Lateral Path Rules for the sensor related procedure coding reference a “runway fix” as a missed approach
point or a missed approach point. Those same rules apply to helicopter procedures. For procedures designed
with a dedicated helipad as the missed approach point, a Terminal Waypoint will be established and used as the
missed approach point fix.

6.12.3 The Vertical Path Rules in Section 6 apply without exception, using the rules appropriate for the sensor type.

6.12.4 Missed Approach code will be accomplished according to the rule in Section 7 of this Attachment, appropriate
for the sensor type.
ARINC SPECIFICATION 424 – Page 214

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 1

Excerpted from Jeppesen Chart Adrar, Not for navigational or other operational
Algeria, VOR Rwy 04 Approach Chart by use. For example only. Please consult
permission of Jeppesen Sanderson, Inc. current navigation charts.
 ARINC SPECIFICATION 424 – Page 215

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 2

Excerpted from Jeppesen Chart Agadir, Not for navigational or other operational
Morocco, VOR Rwy 28 Approach Chart by use. For example only. Please consult
permission of Jeppesen Sanderson, Inc. current navigation charts.
ARINC SPECIFICATION 424 – Page 216

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 3

Excerpted from Jeppesen Chart Annaba, Not for navigational or other operational
Algeria, VOR Rwy 28 Approach Chart by use. For example only. Please consult
permission of Jeppesen Sanderson, Inc. current navigation charts.
 ARINC SPECIFICATION 424 – Page 217

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 4

Excerpted from Jeppesen Chart Annaba, For illustration only. Not intended for
Algeria, VOR Rwy 19 Approach Chart by use in navigation.
permission of Jeppesen Sanderson, Inc.
ARINC SPECIFICATION 424 – Page 218

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 5

Excerpted from Jeppesen Chart Alicante, Not for navigational or other operational
Spain, VOR Rwy 29 Approach Chart by use. For example only. Please consult
permission of Jeppesen Sanderson, Inc. current navigation. charts.
 ARINC SPECIFICATION 424 – Page 219

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 6

Excerpted from Jeppesen Chart Baldonnel, Not for navigational or other operational
Ireland, VORDME Rwy 11 Approach use. For example only. Please consult
Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
ARINC SPECIFICATION 424 – Page 220

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 7

Excerpted from Jeppesen Chart Aleppo, Not for navigational or other operational
Syria, A. R. VORDME Rwy 27 Approach use. For example only. Please consult
Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
 ARINC SPECIFICATION 424 – Page 221

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 8

Excerpted from Jeppesen Chart Al Not for navigational or other operational

Hoceima, Morocco, VOR Rwy 18 use. For example only. Please consult
Approach Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
ARINC SPECIFICATION 424 – Page 222

ATTACHMENT 5
PATH AND TERMINATOR

VOR CODING EXAMPLE 9

Not for navigational or other operational

Excerpted from Jeppesen Chart Elgin AFB, use. For example only. Please consult
Illinois, USA, TACAN Rwy 01 Approach current navigation. charts.
Chart by permission of Jeppesen
Sanderson, Inc.
 ARINC SPECIFICATION 424 – Page 223

ATTACHMENT 5
PATH AND TERMINATOR

NDB CODING EXAMPLE 1

Excerpted from Jeppesen Chart Majuro Not for navigational or other operational
Intl, Marshall Island, NDB Rwy 25 use. For example only. Please consult
Approach Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
ARINC SPECIFICATION 424 – Page 224

ATTACHMENT 5
PATH AND TERMINATOR

NDB CODING EXAMPLE 2

Excerpted from Jeppesen Chart Edmonton, Not for navigational or other operational
Alberta, Canada, NDB Rwy 11 Approach use. For example only. Please consult
Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
 ARINC SPECIFICATION 424 – Page 225

ATTACHMENT 5
PATH AND TERMINATOR

NDB CODING EXAMPLE 3

Excerpted from Jeppesen Chart Sioux Not for navigational or other operational
Lookout, Ontario, Canada, NDB Rwy 34 use. For example only. Please consult
Approach Chart by permission of Jeppesen current navigation. charts.
Sanderson, Inc.
ARINC SPECIFICATION 424 – Page 226

ATTACHMENT 5
PATH AND TERMINATOR

NDB CODING EXAMPLE 4

Not for navigational or other operational

Excerpted from Jeppesen Chart Blano- use. For example only. Please consult
Sablon, Quebec, Canada, NDB Rwy 05 current navigation. charts.
Approach Chart by permission of Jeppesen
Sanderson, Inc.
 ARINC SPECIFICATION 424 – Page 227

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

7.0 Precision Approach Procedure Coding

7.1 Final Approach Segment

The following rules apply to the coding of “final approach segments” of full ILS Localizer based approach
procedures. These procedures may include full ILS (localizer and GS), converging ILS, and those IGS
(Instrument Guidance System) that are full ILS equivalent. These rules also apply to all type of MLS Approach
Procedures and to GLS Approach Procedures.

7.1.1 All such approach procedures must begin at the FACF. They must consist of a FACF, FAF and missed approach
point fix and all step-down fixes published in the vertical path.

7.1.2 For localizer based procedures, the FACF is defined as a fix located on the localizer beam center, 8NM or less
from the FAF or within the reception range of the Localizer. This may be a source document provided fix or a fix
created using these positioning rules.

7.1.3 The FACF is coded as an IF leg. An altitude will not be assigned to the FACF unless specified in government
source documents.

7.1.4 The track from the FACF to the FAF is coded as a CF or TF leg with altitude constraints as indicated for the
specific procedure types below.

7.1.5 The recommended navaid must be the procedure reference localizer. Theta and Rho must be provided from that
navaid for each sequence of the final approach, including any step-down fixes, the runway or helipad fix and/or
missed approach point.

7.1.6 The “Outbound Magnetic Course” field in all sequences must be equal to the localizer magnetic bearing or MLS
course, derived from official government source.
7.1.7 For approach procedures with an electronic glide slope, the vertical angle must be coded in both the Final
Approach Fix and the fix, which carries the missed approach point coding. The FAF record carries the Final
Approach Fix waypoint description code of “F” in position four of that field. The missed approach point fix
carries the waypoint description code of “M” in this position four. The vertical angle will be the published glide
slope angle for the installation or procedure. If the altitude 1 and 2 constraints for the FAF are “at” (G) and equal
to the FACF altitude with an altitude description of “I,” the vertical angle is omitted from the FAF record.

7.1.8 The Coding of FAF and FACF Altitude description fields are as follows:

FACF FAF
G Glide Slope Crossing G

Glide Slope Intercept

Altitude 1 Altitude 2 Alt Desc [2]

FAF G/S Intercept Altitude is “at” Glide Slope Crossing Altitude is “at” G
G/S Intercept Altitude is “at or above” Glide Slope Crossing Altitude is “at” H
FACF State Defined Altitude is “at” [3] Glide Slope Intercept [1] I
State Defined Altitude is “at or above” [3] Glide Slope Intercept [1] J

NOTES:

[1] Glide Slope intercept altitudes are not specified as either “at” or “at or above.”
[2] Reference Section 5.29
[3] FACF Altitude 1 may be blank. When it is blank, the Altitude Description is also blank, even when Altitude 2 is
not blank.
ARINC SPECIFICATION 424 – Page 228

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

7.3 GLS Precision Approach Procedure Coding

7.3.1 The rules for coding GLS Approach Procedures are understood to be identical to those of Localizer coding as
found in Section 7.1 of this Attachment.

7.4 MLS Approach Procedure Coding

MLS Approach Procedure Code utilizing raw azimuth and elevation data is limited to those procedures that are
designed as a localizer equivalent. If such a procedures is coded, the rules for the “final approach segments” are
to be identical with those stated in Rule 7.1 above. The Route Type of such approaches must be coded as “M”
in column 20 of the primary approach record. Approach procedures predicated on the use of MLS Area
Navigation (MLS/RNAV) must be coded with a “W” or “Y” in column 20 of the primary approach record.
MLS/RNAV approaches are coded as described below.

There are three types of MLS/RNAV approach, listed in increasing levels of complexity, computed lateral/raw
vertical guidance, computed lateral and vertical guidance and curved path.

7.4.1 Approaches using computed lateral path and raw vertical path guidance, also referred to as Type “A,” will be
used primarily where the MLS azimuth transmitter cannot be located on the extended runway centerline, but the
elevation transmitter is sited normally abeam the touchdown point. All legs will be straight and aligned with the
inbound course. They must be codes with Route Type “W” in column 20 of the primary approach record. Path
definition will be the equivalent of a full ILS approach (Rule 6.4.2) with the exception that the leg from the
PFAF inbound will be a “TF” leg, terminating at the runway or helipad waypoint, with the published final
approach source in the Outbound Magnetic Course field. The PFAF will be coded as the Final Approach Fix in
the Waypoint Description field and the first fix prior to the PFAF will be coded as the Final Approach Course
Fix.

7.4.2 Approach using computed lateral and vertical guidance but no curved legs, also referred to as Type “B,” must
be coded as Route Type “Y” in column 20 of the primary approach record. All legs will be straight and aligned
with the inbound course. Path definition will be the equivalent of the full ILS approach (Rule 6.4.2) with the
exception that the leg from the PFAF inbound will be a “TF” leg, with the published final approach course in
the Outbound Magnetic Course field. The altitude of the PFAF and all waypoints inbound from it must be the
glide path altitude at that point. The PFAF will be coded as the Final Approach Fix in Waypoint Description
field and the first fix prior to the PFAF will be coded as the Final Approach Course Fix.

7.4.3 MLS/RNAV approaches using curved legs, also referred to as Type “C,” will be used for a variety of reasons,
including parallel sidestep approaches, separation of different categories of aircraft, noise abatement, etc. These
must always be precision approaches. They must be coded a with a Route type of “Y” in column 20 of the
primary approach record. The following rules apply:

7.4.3.1 The first leg of an MLS/RNAV approach with curved legs must be an “IF/TF” leg combination. All other
straight legs must be coded as “TF” legs. All “TF” legs in an MLS/RNAV with curved legs procedure must
have the published course included in the Outbound Magnetic Course field.

7.4.3.2 All curved legs will be code as “RF” legs. Every leg preceding or following the “RF” leg will be tangent to the
“RF” leg at that point.

7.4.3.3 The initial portion of a MLS/RNAV approach with curved legs may be an “IF/RF” combination, provided a
straight leg approach transition is coded to the point in the “IF” and Rule 7.4.2 are complied with.

7.4.3.4 The PFAF will be coded as the Final Approach Fix in the Waypoint Description field and the first fix prior to
the PFAF will be coded as the Final Approach Course Fix. If there is not a fix at the glide path intercept, then
the first fix after the intercept will be the PFAF. There must be one and only one PFAF for each MLS/RNAV
approach with curved legs.

7.4.3.5 The last leg of an approach transition prior to an MLS/RNAV approach must be one of the following types CF,
CI, HF, PI, RF or TF, except as indicated in Rule 6.5.3.3. If the leg type is CF, CI, RF or TF, then the
Recommended Navaid must contain the identifier of the MLS used for the approach. If the leg type is PI or HF,
then the Recommended Navaid must contain the VHF Navaid that defines the PI or HF leg.
7.4.3.6 If the last leg prior to the approach is a “CI” leg, the intercept angle will be 30° or less, and the intercept point
must be between the first and second terminator fixes in the approach, but no closer that 2NM to the second fix.

7.4.3.7 The PFAF and the FACF altitudes must be coded according to Precision Approach Procedures Rule 6.4.2.
 ARINC SPECIFICATION 424 – Page 229

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

7.4.4 The PFAF will be used in precision MLS/RNAV approaches. It is defined as that fix along the lateral path where
the published barometric altitude intercepts the glide slope. Prior to the PFAF, the aircraft is expected to fly
barometric altitude to intercept the glide path. All waypoints up to the PFAF should be coded using the published
barometric crossing altitude. The PFAF and all waypoints after it should be coded using the true altitude of the
glide path at those points.
8.0 Non-precision Approach Procedure Coding

8.1 General

8.1.1 For approach procedures without an electronic glide slope, the Final Approach Fix will be that designated by
government source. If no FAF is established in the government source, one will be computed according to Rule
6.2.5.2 of this Attachment. The fix, whether published or established, must carry the Final Approach Fix
Waypoint Description code of “F” in position four of that code field. Note that only one record in a coded
approach procedure can carry the “F” in position four of the Waypoint Description. Altitudes for this fix are
coded in accordance with Rule 6.2.10.1 of this Attachment.

8.1.2 A Vertical Angle must be coded in the Missed Approach Point, Runway Threshold or the Final End Point, which
ever occurs first, for each approach procedure. Vertical Angles must be derived from the official government
source or computed. This vertical angle will only be repeated on all step-down fixes after the FAF.

8.1.3 Missed Approach Point (MAP) Location - The MAP will be the MAP as shown on the non-precision approach
procedure by the civil aviation authority. If the intent of the procedure designer is to locate the MAP at the LTP
and it is within 0.1 NM radius of the landing threshold point, the MAP will be defined at the LTP.

Note: If the source document states that the MAP and the LTP are not at the same location even if the distance is
0.1 mile or less, the MAP will not be placed at the LTP.

8.2 Final Approach Path Coding - Localizer-based Procedures

The following rules apply to the coding of “final approach segments” of non-precision Localizer-based approach
procedures. These procedures may include Localizer Only, IGS (Instrument Guidance System) LDA, Localizer
type Directional Aid) and SDF (Simplified Directional Aid) procedures.

8.2.1 All such approach procedures must begin at the FACF. They must consist of a FACF, FAF and missed approach
point fix and all step-down fixes published in the vertical path.

8.2.2 The FACF is defined as a fix located on the localizer beam center, 8NM or less from the FAF or within the
reception range of the Localizer. This may be a source document provided fix or a fix created using these
positioning rules.

8.2.3 The FACF is coded as an IF leg with an altitude only when assigned by government source.

8.2.4 The track from the FACF to the FAF is coded as a CF or TF leg with altitude constraints as indicated for the
specific procedure types below.

8.2.5 The recommended navaid must be the procedure reference localizer. Theta and Rho must be provided from the
localizer for each sequence of the final approach, including any step-down fixes, the runway or helipad fix and/or
missed approach point.

8.2.6 The “Outbound Magnetic Course” field in all sequences must be equal to the localizer magnetic bearing, derived
from official government source.

8.3 Final Approach Path Coding - VOR-based Procedures

The following rules apply to the coding of the “final approach segments” of non-precision VOR-based approach
procedures. These procedures may include VOR, VORDME, VORTAC, RNAV and TACAN procedures.
1
8.3.1 Final approach segments must be coded using IF and CF or TF legs only.

1
In general “CF” legs are used in final approach coding. “TF” legs are used in FMS and GPS Approach Procedures,
some types of MLS Procedures and in other procedure types where the determination has been made that a TF will
work better than a CF.
ARINC SPECIFICATION 424 – Page 230

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

8.3.2 Final approach must include both a FAF and missed approach fix. The missed approach fix may be a runway or
helipad fix or a designated missed approach point. Coding of a FACF is defined in Rule 6.2.5.

8.3.3 The recommended navaid must be the procedure reference VOR or TACAN. Theta values must be provided
from that facility in all final approach sequences, including any step-down fixes that are included.
8.3.4 When the reference facility is VORDME or VORTAC or TACAN, the following applies:

8.3.4.1 Final approach segments must be coded using IF and CF or TF1 legs only.

8.3.4.2 Final approach must include FACF, FAF and a missed approach point which may be a missed approach point
fix, a runway fix or a helipad fix, and all step-down fixes published in the vertical path. The final approach will
include an FACF when one is required by Rule 6.2.5.

8.3.4.3 The recommended navaid must be the procedure reference VORDME or VORTAC or TACAN. Theta and Rho
values must be provided from that facility in all final approach sequences, including any step-down fixes that
are included.
8.3.5 When the procedure reference is RNAV, the following applies:

8.3.5.1 Final approach segments must be coded using IF and CF or TF1 legs only.

8.3.5.2 All RNAV approach procedure missed approach points must be at or prior to a runway threshold or helipad
alighting point. These points may be a source defined named waypoint.

8.3.5.3 The recommended navaid is not required unless specified by the state, or if required by leg type. The
recommended navaid must be procedure reference VORDME or VORTAC. Theta and Rho values must be
provided from that facility in all final approach sequences, including any step-down fixes that are included.

8.3.6 Rule deleted by Supplement 17.

8.3.6.1 Rule deleted by Supplement 17.

8.3.6.2 Rule deleted by Supplement 17.

8.3.6.3 Rule deleted by Supplement 17.

8.4 Final Approach Path Coding - NDB-Based Procedures

The following rules apply to the coding of the “final approach segment” of all NDB based approach procedures.
NDB based approach procedures include procedures using a NDB or Locator as the reference facility and
procedures using a NDB or Locator and a DME (NDB + DME) as reference facilities. NDB approach
procedures not requiring DME but using the DME for reduced minimums will be coded as NDB + DME
procedures.
8.4.1 NDB approach procedures must include a FAF and a runway or helipad fix or missed approach point fix and all
step-down fixes published in the vertical path. They may also include a FACF fix.
8.4.2 Rule deleted by Supplement 17.

8.4.3 NDB + DME approach procedures must include a FAF and runway or helipad fix or missed approach point fix
and all step-down fixes published in the vertical path. The final approach will include a FACF when one is
required by Rule 6.2.5.
1
8.4.4 Coding must use IF and CF or TF legs only through to the runway or helipad fix or missed approach point fix.
The IF leg must be at the FAF (or at the optional FACF) for NDB procedures or at the FACF for NDB + DME
procedures.

1
In general “CF” legs are used in final approach coding. “TF” legs are used in FMS and GPS Approach Procedures,
some types of MLS Procedures and in other procedure types where the determination has been made that a TF will
work better than a CF.
 ARINC SPECIFICATION 424 – Page 231

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

8.5 Intentionally Left Blank

8.6 Final Approach Path Coding - Circle-to-Land Procedures

Procedures which are Circle-To-Land may be included in the database. When they are included, they are
identified with the route type appropriate to the sensor involved and the “Circle-To-Land” Approach Procedure
Route Qualifier of “C.” These rules applies to approach routes so identified:

8.6.1 The last segment in the final approach sequence must be the missed approach point fix.

8.6.2 For Circle-To-Land Procedures that are to a runway or helipad, all the rules listed above in Sections 6, 7 and 8
apply, as well as the rules for Missed Approach Procedure coding in Section 9.

8.6.3 For Circle-To-Land Procedures that are not to a runway or helipad, the missed Approach Point will be the
center of the airport or heliport.

8.6.4 The vertical angle information must be in the missed approach point fix segment, or in the Final End Point
segment if a Final End Point is designated for the approach. Vertical angle information must be in accordance
with the rules in Section 6, 7 and 8 of this Attachment for the type of reference facility on which the procedure
is based.
8.7 Final Approach Path Coding – GNSS-Based Procedure

The rules for final approach path GNSS-based procedures are currently under development.

8.7.1 The track from the FACF (when coded) to the FAF is coded with TF or RF legs. The RF leg is not allowed as
the first leg of the approach coding according to the Beginning/Ending Leg Table. The preferred coding when
an approach starts with a precision arc is the use of an “IF” leg at the FACF or FAF, followed by “RF” to the
FAF or MAP. According to the rules on “RF” legs, this must require that a straight line, fix terminated,
approach transition to the FACF or FAF has been included. The track in the transition must be tangent to the arc
and the fix at the end of the transition must be overflown. The rule also does not exclude the use of an RF leg in
between FAF and the final TF leg to the missed approach point. Such RF legs must be coded with the 4th
character of the Waypoint Description field blank.

8.8 Final Approach Path Coding - Helicopter Approach Procedures

Helicopter Approach Procedures will be coding using the rules in Sections 6, 7 and 8 and 9 of this Attachment,
appropriate to the type of sensor required for the procedure, such as VORDME or ILS or RNAV or GNSS. This
includes rules for Recommended Navaid, FACF requirements, beginning and ending leg types, etc.

The Lateral Path Rules for the sensor related procedure coding reference a “missed approach point fix,” a
“runway fix” or a “helipad fix” as the missed approach point. Those same rules apply to the coding of
helicopter procedure.

8.9 Vertical Navigation Path (VNAV Path) or Descent Gradient Considerations

If the government source provides a vertical angle and/or TCH, it will be used. The only exception is when the
source provides more than one angle for the final approach segment. If more than one angle is provided for the
final approach segment, the highest angle will be used.

The following guidelines have been developed for the coding of the vertical angles on the final approach course
when the vertical angle is not provided by the government sources.

8.9.1 The descent angle is to be calculated from published TCH or a point 50 feet above the Landing Threshold Point
(LTP) to the altitude at the final approach fix (FAF). The curvature of the earth should not be used in the
calculations of the descent angle. Refer to examples 1, 7, and 8. The descent angle will always be rounded up to
the nearest one hundredth of a degree.

Examples of Rounding:

3.111 = 3.12
3.346 = 3.35
ARINC SPECIFICATION 424 – Page 232

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

8.9.1.1 The published TCH for a procedure used in these calculations is the procedure TCH or 50 feet when no TCH is
published. TCH is further defined in Chapter Five, Sections 5.67 and 5.265 of this document.

8.9.2 If the calculated angle is less than three degrees, it will be raised to a minimum of three degrees.

8.9.3 If a step-down fix is included in the final approach segment and it is determined that the calculated descent
angle will be above the step-down fix altitude, that calculated descent angle will be used. If it is determined that
the step-down fix altitude is above the descent path, the descent angle will be calculated from the LTP plus 50
feet to the altitude at the step-down fix. Refer to Examples 3 and 4.

8.9.4 The descent angle should not be less than the Visual Glide Slope Indicator (VGSI) associated with the landing
runway. If the calculated descent angle is less than the VGSI, the descent angle should be raised to match the
VGSI or to 3.77 degrees whichever is lower.

8.9.5 If the final approach course does not pass over the runway threshold, a position abeam the runway threshold on
the final approach course will be calculated and coded as a Final End Point. The descent angle will be computed
from the abeam position to the altitude at the FAF. The altitude to be used at the Final End Point is the LTP
plus 50 feet. Refer to Examples 6, 9, and 10.

8.9.6 If the missed approach point is prior to the runway threshold, the descent angle will be computed from the LTP
plus 50 feet to the altitude at the FAF. An altitude will be specified at the MAP and will be the altitude where
the descent angle passes through the MAP. Refer to Examples 7 and 8.

8.9.7 When circling-to-land minimums are the only landing minimums and the runway is in alignment with the final
approach segment, a descent angle will be provided. The descent angle will be calculated from the LTP plus 50
feet to the altitude at the FAF. Refer to Examples 11 and 12.
8.9.8 When circling-to-land minimums are the only landing minimums and the runway is not in alignment with the
final approach segment, a descent angle will be provided. The descent angle will be calculated from a point on
the final approach track Abeam the LTP of the nearest landing runway to the altitude at the FAF. The altitude to
be used at the abeam position is the airport elevation. Refer to Example 13.

8.9.9 If step-down fix is published in government source in the initial or intermediate segment, the fix and the
appropriate altitude will be coded as part of the procedure. A vertical angle will be coded on the FAF waypoint
that will ensure any step-down fix altitude in the intermediate segment FACF to FAF is cleared. Vertical angle
information is not provided in the initial segment IAF to FACF. All step-down fixes will be coded with the
appropriate altitude.

8.10 VNAV Coding of Non-Precision Approach Procedures With Missed Approach Points - Other Than Landing
Threshold

Coding standards for Non-Precision Approach Procedures that have a published missed approach point other
than the Landing Threshold Point (LTP) have been developed. Examples of coding three VNAV coding
scenarios have been developed. The three examples are:

8.10.1 Missed Approach Point beyond the landing threshold, more than 0.14NM from the landing threshold and the
published Final Approach Course crosses the landing threshold. The ARINC 424 rules for this case call for
inserting the Landing Threshold Point as a fix in the procedure coding. See VNAV Coding Example A.

8.10.2 Missed Approach Point beyond the landing threshold, more than 0.14NM from the landing threshold and the
published Final Approach Course does not cross the landing threshold, the Final Approach Course is no closer
than 0.14NM to the landing threshold at any given point. ARINC 424 rules for this case call for inserting a
Final End Point as a fix in the procedure coding. See Coding Example B.

8.10.3 Missed Approach Point is a Navaid beyond the landing threshold. The Navaid is within 0.14NM of the landing
threshold. According to ARINC 424 rules, this Navaid will be coded as the missed approach point. No fixes
will be inserted into the procedure coding. VNAV information will be provided on the Missed Approach Point
sequence. See Coding Example C.
 ARINC SPECIFICATION 424 – Page 233

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 1

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) at Landing Threshold Point (LTP)
final approach path with Straight-In landing alignment. The VNAV angle, when not provided in official government
source, is calculated from LTP + 50 feet to the FAF altitude and coded in the MAP sequence.
ARINC SPECIFICATION 424 – Page 234

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 2

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) at Landing Threshold Point (LTP)
final approach path with Straight-In landing alignment. The VNAV angle is calculated from LTP + 50 feet to the FAF
altitude, and raised to an optimum angle of 3.00 degrees or to an angle matching the VASI/PAPI angle. This adjusted
angle is coded in the MAP sequence
 ARINC SPECIFICATION 424 – Page 235

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 3

This example shows Final Approach Fix (FAF) to Missed Approach Point (MAP) at Landing Threshold Point (LTP) via
Step-down Fix final approach path with Straight-In landing alignment. The VNAV angle is calculated from LTP + 50
feet to the FAF altitude and coded in the MAP sequence. If the Step-down penetrates VNAV path of LTP + 50 feet to
FAF altitude, as shown in this example, the VNAV angle is raised to clear step-down and this revised VNAV angle is
used for entire final approach.
ARINC SPECIFICATION 424 – Page 236

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 4

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) at Landing Threshold Point (LTP)
via Step-down Fix final approach path with Straight-In landing alignment. The VNAV angle is calculated from LTP +
50 feet to the FAF altitude and coded in the MAP sequence. When the Step-down does not penetrate VNAV path of LTP
+ 50 feet to FAF altitude, there is no requirement to raise angle.
 ARINC SPECIFICATION 424 – Page 237

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 5

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) beyond Landing Threshold Point
(LTP) final approach path with Straight-In landing alignment. The MAP position is the officially published government
source position and is beyond the LTP. A “LTP Fix” waypoint (runway) is required in the correct coding of this
example. The VNAV angle is calculated from LTP + 50 feet, not the MAP, to the FAF altitude, and coded in the LTP
sequence.
ARINC SPECIFICATION 424 – Page 238

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 6

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) beyond Landing Threshold Point
(LTP) final approach path. The MAP is located more than 0.1NM from LTP. The MAP position is the officially
published government source position. A Final End Point (FEP) “ LTP” waypoint required. The procedure does meet
Straight-in landing alignment criteria. The VNAV angle is calculated from a LTP + 50 feet elevation to the FAF altitude,
using the Final End Point waypoint position and coded in the FEP sequence.
 ARINC SPECIFICATION 424 – Page 239

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 7

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) before Landing Threshold (LTP)
final approach path with Straight-in landing alignment. The MAP position is the officially published government source
position. The VNAV angle is calculated from the LTP +50 feet to the FAF altitude, and coded in the MAP sequence.
The Altitude in the MAP sequence is assigned based on computation, using the calculated VNAV angle. The LTP is not
included in the coding as a waypoint. The Missed Approach Procedure is coded as straight ahead over runway.
ARINC SPECIFICATION 424 – Page 240

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 8

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path meeting
Straight-in landing alignment criteria with the MAP before Landing Threshold Point (LTP). The MAP position is the
officially published government source position. The VNAV angle is calculated from the LTP +50 feet to the FAF
altitude, and coded in the MAP sequence. The Altitude in the MAP is assigned based on computation, using the
calculated VNAV angle. The LTP is not included in the coding as a waypoint. The Missed Approach Procedure includes
immediate turn at the MAP.
 ARINC SPECIFICATION 424 – Page 241

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 9

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path with the MAP
beyond Landing Threshold Point (LTP), and located more than 0.1NM from the LTP. The MAP position is the officially
published government source position. A “Final End Point” (FEP) waypoint is required. The procedure meets Straight-in
landing alignment criteria. The VNAV angle is calculated from a LTP+50 feet elevation to the FAF altitude, using the FEP
fix position and coded in the FEP sequence.
ARINC SPECIFICATION 424 – Page 242

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 10

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path with the MAP
located beyond Landing Threshold Point (LTP). The Final Approach segment is parallel/near parallel to the runway
alignment. The MAP is located more than 0.1NM from LTP. The MAP position is the officially published government
source position. A “Final End Point (FEP)” waypoint is required. The VNAV angle is calculated from a LTP +50 feet
elevation to the FAF altitude, using the Final End Point position and coded in the FEP sequence.
 ARINC SPECIFICATION 424 – Page 243

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 11

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) at Landing Threshold Point (LTP)
final approach path. The procedure is published with Circle-To-Land weather minimums although the straight-in landing
alignment criteria are met. The MAP position is the officially published government source position. The MAP is a
published waypoint at the LTP. The VNAV angle is calculated from the LTP +50 feet to the FAF altitude, and coded in
the MAP sequence.
ARINC SPECIFICATION 424 – Page 244

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 12

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path where the MAP
is before the Landing Threshold Point (LTP).

The procedure is Circle-To-Land weather minimums although Straight-in landing alignment criteria are met. The MAP
position is the officially published government source position. The LTP is not included in the coding. The VNAV angle
is calculated from the LTP +50 feet to the FAF altitude and coded in the MAP sequence.
 ARINC SPECIFICATION 424 – Page 245

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 13

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) that is other than the Landing
Threshold Point (LTP), and is not before, beyond or abeam the Landing Threshold Point. The procedure is published
with Circle-To-Land weather minimums. Straight-in landing alignment criteria are not met.

The MAP position is the officially government source position or, if not published, established as a point abeam the
nearest landing threshold. The VNAV angle is calculated from the airport elevation to the FAF altitude and coded in the
MAP sequence.
ARINC SPECIFICATION 424 – Page 246

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 14

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path with the MAP
before Landing Threshold (LTP). The MAP is located more than 0.1NM from LTP. The MAP position is the officially
published government source position and coded in the MAP sequence. The procedure does not meet Straight-in landing
requirement. The VNAV angle is calculated from a LTP + TCH elevation (or LTP + 50 feet if no TCH coded) to the FAF
altitude considering the along track distance between LTP and FAF as shown below in dimensional lines. The altitude at the
MAP is assigned based on computation, using the calculated VNAV angle.

[RWY13L]

DMYHL
3.8

2.6

DMYHL VOR
1500’
VNAV 2.12°

13’ 3.8 2.6

[RWY13L]
 ARINC SPECIFICATION 424 – Page 247

ATTACHMENT 5
PATH AND TERMINATOR

NON-PRECISION APPROACH CODING EXAMPLE 15

This example shows a Final Approach Fix (FAF) to Missed Approach Point (MAP) final approach path with the MAP
before Landing Threshold (LTP) and runway parallel to last leg. The MAP is located more than 0.1NM from LTP. The
MAP position is the officially published government source position and coded in the MAP sequence. The VNAV angle is
calculated from a LTP + TCH elevation (or LTP + 50 feet if no TCH coded) to the FAF altitude and coded considering the
along track distance between the abeam of the LTP on the final leg (noticed EP below) and the FAF as shown below in
dimensional lines. The altitude at the MAP is assigned based on computation, using the calculated VNAV angle.

D2.3 D7.0
1.4 4.7

[RWY19]

VOR D7.0
D2.3 2500’

VNAV 2.84°
M

610’ 1.4 4.7

[RWY19]
ARINC SPECIFICATION 424 – Page 248

ATTACHMENT 5
PATH AND TERMINATOR

CODING EXAMPLE A
VNAV APPROACH CODING EXAMPLE

Inserted Runway Fix

This example shows a procedure published as Final Approach Fix (FAF) to a Missed Approach Point (MAP) beyond
Landing Threshold Point (LTP). The final approach path crosses the LTP. The landing alignment is Straight-In. As the
officially published MAP position is beyond the LTP, a “LTP Fix” waypoint (RW30) is inserted as an additional
waypoint into the coding for this example. The VNAV angle is calculated from LTP + TCH or 50 feet, not the MAP, to
the FAF altitude, and is coded in the “LTP Fix” sequence. The missed approach path is not included in the graphic. It is
included in the coding sequence example. The inserted “LTP Fix” is coded as the MAP. The coded first leg of the
missed approach path is a continuation of the Final Approach Course (FAC) to the officially published MAP. The first
leg of the published missed approach path is a climb on the FAC to an altitude of airport elevation plus 400 feet,
followed by a direct to fix at the FAF.

Inserted Runway Fix Coding:

APP SEQ WAYPOINT MAG ALT VERT

FIX ID P/T DIST ARINC REF.
ID NR DESCRIPTION COURSE DESC/ALT ANGLE
D30 020 STAHL IF E F 0.0 0.0 At or Above Attachment
Procedure Five,
Altitude Rule 8.1.1
D30 030 RW30 CF G Y M Published 4.7 At LTP + -3.00 Attachment
FAC TCH or 50' Five,
Rule 8.1.2
Rule 6.2.9.3
Rule 6.2.10.2.c
D30 040 VOR CF V M Published 0.8 Attachment
FAC Five,
Rule 6.2.10.2.c
D30 050 CA Published At or Above Attachment
FAC Airport Plus Five,
400' Rule 9.4.1.4
D30 050 STAHL DF E E At or Above
Procedure
Altitude

Waypoint Description:
Column One - Fix Type: E = Waypoint, G = Runway, V = VHF Navaid
Column Two - E = End of Final Approach Coding, Y = Flyover waypoint
Column Three - M = First Leg of Missed Approach Procedure
Column Four - Fix Function in Coding: F = FAF, M = Missed Approach Fix
Note: FAF Altitude Description may be “at” when this is prescribed by source documentation. The altitude in sequence
050 may be a source provided value for the first leg of a missed approach or may be regionally adjusted to 500 feet
above the airport. The At or Above Airport Plus 400' is the minimum requirement.
 ARINC SPECIFICATION 424 – Page 249

ATTACHMENT 5
PATH AND TERMINATOR

CODING EXAMPLE B
VNAV APPROACH CODING EXAMPLE

Inserted Final End Point Fix

This example shows a procedure published as Final Approach Fix (FAF) to a Missed Approach Point (MAP) beyond
Landing Threshold Point (LTP). The final approach path does not cross the LTP. The landing alignment is Straight-in.
As the MAP is located more than 0.14NM from LTP, a Final End Point Fix (FEP) waypoint is inserted as an additional
waypoint into the coding for this example. The VNAV angle is calculated from a LTP + TCH or 50 feet elevation to the
FAF altitude, references the FEP position and is coded in the FEP sequence. The missed approach path is not included in
the graphic. It is included in the coding sequence example. The inserted “FEP Fix” is coded with its unique code. The
coded first leg of the missed approach path is a continuation of the Final Approach Course (FAC) to the officially
published MAP. The first leg of the published missed approach path is a climb on the FAC to an altitude of airport
elevation plus 400 feet, followed by a direct to fix at the FAF.

Inserted Final End Point Fix Coding:

APP SEQ WAYPOINT MAG ALT VERT

ID NR FIX ID P/T DESCRIPTION COURSE DIST DESC/ALT ANGLE ARINC REF.
D30 020 BANCH IF E F 0.0 0.0 At or Above Attachment Five
Procedure Rule 8.1.1
Altitude
D30 030 EP30 CF E Y E Published 4.1 At LTP + TCH -3.00 Attachment Five
FAC or 50' Rule 8.1.2
Rule 6.2.9.4
Rule 6.2.10.2.d
D30 040 VOR CF V M Published 0.9 At or Above Attachment Five,
FAC Airport Plus Rule 6.2.10.2.d
400'
D30 050 CA M Published At or Above Attachment Five,
FAC Airport Plus Rule 9.4.1.4
400'
D30 060 BANCH DF E E At or Above
Procedure
Altitude

Waypoint Description:
Column One - Fix Type: E = Waypoint, V = VHF Navaid
Column Two - E = End of Final Approach Coding, Y = Flyover Waypoint
Column Three - M = First Leg of Missed Approach Procedure
Column Four - Fix Function in Coding: F = FAF, E, M; E = Final End Point
Note: FAF Altitude Description may be “at” when this is prescribed by source documentation. The altitude in sequence
040 and 050 may be a source provided value for the first leg of a missed approach or may be regionally adjusted to 500
feet above the airport. The At or Above Airport Plus 400' is the minimum requirement.
ARINC SPECIFICATION 424 – Page 250

ATTACHMENT 5
PATH AND TERMINATOR

CODING EXAMPLE C
VNAV APPROACH CODING EXAMPLE

MAP is Navaid within 0.14NM of Landing Threshold

This example shows a procedure published as Final Approach Fix (FAF) to Missed Approach Point (MAP) beyond
Landing Threshold Point (LTP). The final approach path does not cross the LTP. The landing alignment is Straight-in.
As the officially published MAP is a Navaid located less than 0.14NM from LTP coding is to that fix and no waypoints
are inserted. The VNAV angle is calculated from the MAP to the FAF altitude so as to ensure LTP + 50 feet elevation
over the threshold, referencing the MAP position and is coded in the MAP sequence. The missed approach path is not
included in the graphic. It is included in the coding sequence example. Coding is to the officially published MAP. The
coded first leg of the missed approach path is a continuation of the Final Approach Course (FAC) and is a climb on the
FAC to an altitude of airport elevation plus 400 feet, followed by a direct to fix at the FAF.

No inserted fixes, MAP is Navaid, beyond threshold but within 0.14NM Coding:

APP SEQ WAYPOINT MAG ALT VERT ARINC

ID NR FIX ID P/T DESCRIPTION COURSE DIST DESC/ALT ANGLE REF.
S29 020 BANCH IF E F 0.0 0.0 At or Above Attachment
Procedure Five, Rule
Altitude 8.1.1
S29 030 VOR CF V Y M Published 5.0 See Note -3.00 Attachment
FAC Below Five, Rule
8.1.2,
6.2.5.3
S29 040 CA M Published At or Above Attachment
FAC Airport Plus Five, Rule
400' 9.4.1.4
S29 050 BANCH DF E E At or Above
Procedure
Altitude

Waypoint Description:
Column One - Fix Type: E = Waypoint, V = VHF Navaid
Column Two - E = End of Final Approach Coding, Y = Flyover Waypoint
Column Three - M = First Leg of Missed Approach Procedure
Column Four - Fix Function in Coding: F = FAF, M = Missed Approach Fix

Altitude/Altitude Description of MAP Sequence: Will be an At Altitude, calculated on the path that continues over the
threshold at 50 feet. The altitude for the MAP Navaid will not be less than the threshold elevation. The FAF Altitude
Description may be “at” when this is prescribed by source documentation. The altitude in sequence 040 may be a source
provided value for the first leg of a missed approach or may be regionally adjusted to 500 feet above the airport. The At
or Above Airport Plus 400' is the minimum requirement.
 ARINC SPECIFICATION 424 – Page 251

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

9.0 Missed Approach Procedure Rules Valid For All Procedure Types

Missed Approach Procedure coding must be accomplished as an integral part of the Approach Procedure
Coding and will be provided for each approach procedure contained in the data base. Specific coding must be
incorporated to facilitate identification of where the Missed Approach Coding starts within any given approach
procedure.

The structure of the procedure records included in this Specification as defined in this Attachment is such that
multiple missed approach procedure paths may be coded for a single approach procedure. This will
accommodate those procedures with alternative missed approach paths based on aircraft climb performance.
Coding for multiple missed approach paths for a single approach procedure must commence at the same missed
approach point. Identification of multiple missed approach procedures, when coded, will be accomplished
through the coding of a specific Transition Identifier which closely aligns with published information.

9.1 Missed Approach Point

9.1.1 All Approach Procedure coding must have a segment that identifies the Missed Approach Point Fix. Such a fix
must be the published Missed Approach Point, either a IFR Landing Threshold or a Helipad Alighting Point or
a dedicated Missed Approach Point (MAP Fix).

9.1.2 Identification of the fix within a sequence of procedure records and the type of fix, must be accomplished
through code in the “Waypoint Description” field (see Section 5.17).

9.1.2.1 When the Missed Approach Point Fix is a Runway or Helipad Fix, Waypoint Description Position One, must
carry a character “G” and the “M” in Position Four.

9.1.2.2 When the Missed Approach Point Fix is MAP Fix, Waypoint Description Position One will carry a code equal
to the type of fix such a Navaid or waypoint and must carry a character “M” in Position Four.

9.2 First Leg of Missed Approach Procedure

9.2.1 The first sequence of the Missed Approach Procedure must always be coded with the character “M” in Position
Three of the “Waypoint Description” field.

9.2.2 Coding of the Missed Approach Procedure assumes that the procedure will be flown commencing at the Missed
Approach Point Fix.

9.3 Vertical Path of Missed Approach Procedure

9.3.1 If the published Missed Approach Point Fix is a Runway fix or a Helipad Fix, then the following rules apply:

9.3.1.1 The Altitude 1 value in the Missed Approach Point sequence must be equal to Runway Threshold or Helipad
Alighting Point Elevation plus the published TCH. If TCH is not specified by source then use 50 feet.

9.3.1.2 The first leg of a Missed Approach Procedure will contain any government source provided altitude constraints.
These altitudes may be provided as “At,” “At or Above,” “At or Below,” “At or Below to At or Above,”
dependent on the government source documentation and coded in accordance with Section Five, Subsection
5.29 of this Specification. Except as indicated below, if the government source does not provide an altitude
constraint for the first leg of the Missed Approach Procedure, none will be coded

9.3.1.3 In precision approach procedures or “Full ILS” (Localizer and Glide Slope) or GLS, the Altitude 1 value in the
Missed Approach Point Fix sequence must be equal to runway threshold or the helipad alighting point elevation
plus the published TCH. If TCH is not specified by source then use 50 feet. The “Decision Height” value at
which the Missed Approach Procedure would normally be commenced is not coded as part of the Approach
Procedure. The Altitude values in the first leg of the Missed Approach Procedure, when coded, will be the
source provided values.

9.3.1.4 In non-precision approach procedure coding, the Altitude 1 value in the Missed Approach Point Fix sequence
must be equal to the runway threshold or helipad aligning point elevation plus the published TCH, or 50 feet if
not specified by source. The “Minimum Descent Altitude” value at which the missed approach decision would
normally be made is not coded as part of the Approach Procedure. The Altitude values in the first leg of the
Missed Approach Procedure, when provided, will be the source provided values.
ARINC SPECIFICATION 424 – Page 252

ATTACHMENT 5
PATH AND TERMINATOR

APPROACH AND APPROACH TRANSITION CODING RULES

9.3.1.5 When an immediate turn is specified in an ILS, MLS, or GLS missed approach, or if the source describes a turn
greater than 15 degrees from the final approach path, without an altitude specified before the turn, as the first
leg of a missed approach a course from or heading to an altitude (CA, FA, VA) leg must be coded as the first
leg of the missed approach, using the approach course for the leg heading or course. The altitude will be coded
as a minimum altitude, at least 400 feet above the airport elevation and the leg will terminate at that altitude.
9.4. Rule deleted by Supplement 17.

9.4.1 Rule deleted by Supplement 17.

9.4.1.1 Rule deleted by Supplement 17.

9.4.1.2 Rule deleted by Supplement 17.

9.4.1.3 Rule deleted by Supplement 17.

9.4.1.4 Rule deleted by Supplement 17.

9.4.1.5 Rule deleted by Supplement 17.

9.5 Other Missed Approach Procedure Considerations.

9.5.1 Opposite end runway or helipad fixes must not be used in the coding of missed approach procedures.
9.5.2 The procedure reference Navaid must be used as the Recommended Navaid when required, with the following
exceptions:
9.5.2.1 The first leg of a Missed Approach Procedure may be a CD, FD or VD leg. For these legs a DME may be used
as the Recommended Navaid, with the Theta field left blank and the DME distance entered in the Rho field.
9.5.2.2 Rule deleted by Supplement 17.

9.5.2.3 The first leg of the Missed Approach Procedure may be a CR or a VR leg. For these legs, a VOR facility
(without or without DME) may be used as the Recommended Navaid. When the facility has no DME, the Rho
field is left blank and the VOR radial is entered in the Theta field.

9.5.2.4 When the first leg of a Missed Approach Procedure is coded as a “HA or HM” leg, the coding will also include
a government source provided altitude.
 ARINC SPECIFICATION 424 – Page 253

ATTACHMENT 5
PATH AND TERMINATOR

MISSED APPROACH CODING EXAMPLE 1

The copyrighted material in the following Not for navigational or other operational
Missed Approach Coding Examples is use. For example only. Please consult
reproduced with the permission of the current navigation charts.
copyright holder Jeppesen Sanderson, Inc,
Englewood, Colorado.
 ARINC SPECIFICATION 424 – Page 254

ATTACHMENT 5
PATH AND TERMINATOR

MISSED APPROACH CODING EXAMPLE 2

The copyrighted material in the following Not for navigational or other operational
Missed Approach Coding Examples is use. For example only. Please consult
reproduced with the permission of the copyright current navigation charts.
holder Jeppesen Sanderson, Inc, Englewood,
Colorado.
 ARINC SPECIFICATION 424 - Page 255
APPENDIX 1
CHRONOLOGY AND BIBLIOGRAPHY

1. Chronology
The AEEC Area Navigation Subcommittee established a working group at its September 1973 meeting in Los Angeles to look into
the possibilities of standardizing RNAV system reference data format and encoding characteristics. The Subcommittee had
observed that different RNAV system manufacturers were taking divergent paths with respect to reference data organization, and
believed that, unless this trend was halted, the airline industry would be faced with the very high costs of supporting the production
of data files in several different formats. Obvious economic benefits would result if this could be avoided.
The working group met for the first time in January 1974. It examined the approaches to reference data organization being taken by
RNAV system manufacturers and, with the help of Jeppesen and Co., looked at the data whose characteristics needed definition. It
established the philosophy concerning standardization stated in Section 1.2 of this Specification, and determined the path to follow
to implement it. This was the vital first step in this activity, as it established where in the overall process of producing FDSU
cassettes and ADEU cards the application of standardization would and would not yield cost benefits.
At its second and third meetings, held in March and May of 1974 respectively, the working group concentrated on defining
characteristics for data elements. These included field content, record structure and file organization. Sufficient progress was made
for a first draft of this Specification to be prepared for presentation to the RNAV Subcommittee for review.

The Subcommittee considered this first draft at its September 1974 meeting in Washington, D.C. It endorsed the principles
established by the working group for the preparation of the draft. The Subcommittee concluded, however, that it should take on the
rest of the specification-writing itself, building on the foundation represented by the draft. The working group was, therefore,
disbanded. The Subcommittee’s in-depth review of the draft produced numerous amendments and proposals for addition which,
following the meeting, were incorporated into the document to produce the second draft.

The Subcommittee reviewed the second draft at its January 1975 meeting in Washington, D.C. Incorporation of the amendments
developed at this meeting was felt by the Subcommittee to be all that was necessary to complete the Specification. The third draft,
incorporating them, was approved by AEEC for publication at the General Session held in Washington, D.C. in the Spring of 1975.
2. Bibliography

The following is a list of AEEC letters associated with the preparation of ARINC Specification 424. A list of letters related to the
RNAV Subcommittee’s activities as a whole may be found in ARINC Report 299, “AEEC Letter Index.”

AEEC LETTER NO. DATE SUBJECT

73-124/RNAV-87 Oct 8, 1973 Report of the Area Navigation Subcommittee Meeting

held in Los Angeles, California, September 11th, 12th
and 13th, 1973.
74-017/RNAV-89 Apr 2, 1974 Progress Report on the Activities of the RNAV
Subcommittee’s Data Format Standardization
Working Group.
74-029/RNAV-90 Jun 17, 1974 Circulation of Draft No. 1 of Project Paper 424, “Area
Navigation System Data Base Specification.”
74-046/RNAV-94 Aug 7, 1974 Thomson CSF Comments on ARINC Characteristics
583 Synchro Excitation Provisions and on RNAV
Data Format Standardization.
74-058/RNAV-95 Sep 26, 1974 Report of the Area Navigation Subcommittee Meeting
Held September 17th, 18th and 19th, 1974 in
Washington, D.C.
74-071/RNAV-97 Nov 14, 1974 Circulation of Draft No. 2 of Project Paper 424, “Area
Navigation System Data Base Specification.”
75-013/RNAV-99 Feb 27, 1975 Circulation of Draft No. 3 of Project Paper 424, “Area
Navigation System Data Base Specification.”
75-014/RNAV-100 Mar 7, 1975 Report of the Area Navigation Subcommittee Meeting
held in Washington, D.C., January 21st, 22nd and
23rd, 1975.
75-018/RNAV-101 Mar 25, 1975 Additions to Project Paper 424 proposed by Jeppesen.

3. Meeting Attendees
The following people constituted the RNAV Subcommittee’s Data Format Standardization Working Group and attended
Subcommittee meetings held in September 1974 and January 1975.
ARINC SPECIFICATION 424 - Page 256
APPENDIX 1
CHRONOLOGY AND BIBLIOGRAPHY

AREA NAVIGATION SUBCOMMITTEE

AEEC Members and Airlines
F. W. Ungry, Chairman UNITED AIRLINES Chicago, Illinois
J. D. Wheeler AMERICAN AIRLINES Tulsa, Oklahoma
David Meredith BRITISH AIRWAYS London, England
H. F. McSweyn NATIONAL AIRLINES Miami, Florida
J. R. Reagan PIEDMONT AIRLINES Winston-Salem, North Carolina
Karl H. Riesen SWISSAIR Jamaica, New York
Phil Wirthlin SWISSAIR Zurich, Switzerland
T. G. Angelos UNITED AIRLINES Chicago, Illinois
T. A. Ellison UNITED AIRLINES San Francisco, California
Curt Humphrey UNITED AIRLINES San Francisco, California
D. H. Featherstone AERONAUTICAL RADIO, INC. Annapolis, Maryland
Manufacturers and Others

Francois Mourareau AEROSPATIALE Toulouse, France

Stanley W. Munson AIR FORCE Wright-Patterson AFB, Ohio
Morton Ross ARMA/AMBAC Garden City, New York
Philip T. Martin BATTELLE Columbus, Ohio
J. C. Lumsden BENDIX AVIONICS Ft. Lauderdale, Florida
J. G. Berzin BOEING COMPANY Seattle, Washington
Edward P. Donnelly BOEING COMPANY Edmonds, Washington
Phillip Fenner BOEING COMPANY Seattle, Washington
Gerald L. Moore BOEING COMPANY Seattle, Washington
Frank A. Rasmussen BOEING COMPANY Seattle, Washington
J. Nelson Seto BOEING COMPANY Seattle, Washington
Tony Smith BOEING COMPANY Seattle, Washington
Michael Gordon-Smith CANADIAN MARCONI COMPANY Montreal, Quebec, Canada
Donald Gussin CANADIAN MARCONI COMPANY Montreal, Quebec, Canada
J. F. Haberl CANADIAN MARCONI COMPANY Montreal, Quebec, Canada
R. K. Paull CANADIAN MARCONI COMPANY Montreal, Quebec, Canada
R. L. Kittrell COLLINS RADIO COMPANY Cedar Rapids, Iowa
Dave Lammers COLLINS RADIO COMPANY Cedar Rapids, Iowa
Roy L. Neff COLLINS RADIO COMPANY Cedar Rapids, Iowa
Jack Ringland COLLINS RADIO COMPANY Cedar Rapids, Iowa
Marvin H. Schmidt COLLINS RADIO COMPANY Cedar Rapids, Iowa
George F. King DECCA NAVIGATOR COMPANY LTD. Surrey, England
Ronald M. Fry DELCO ELECTRONICS Milwaukee, Wisconsin
L. David Lewis DELCO ELECTRONICS Milwaukee, Wisconsin
Robert E. Oliver DELCO ELECTRONICS Goleta, California
Rudy Poklar DELCO ELECTRONICS Milwaukee, Wisconsin
B. W. Singleton DOUGLAS AIRCRAFT COMPANY Long Beach, California
George F. Morris EDMAC ASSOCIATES, INC. East Rochester, New York
Roderic Nevin EDMAC ASSOCIATES, INC. East Rochester, New York
Adrian M. Zeffert EDO COMMERCIAL CORPORATION Melville, New York
Edgar A. Post FEDERAL AVIATION ADMINISTRATION Washington, D.C.
A. W. Randall FEDERAL AVIATION ADMINISTRATION Washington, D.C.
G. Tomsic FEDERAL AVIATION ADMINISTRATION Washington, D.C.
Tony Plattner GARRETT CORPORATION Los Angeles, California
Glen A. Gilbert GILBERT ASSOCIATES Washington, D.C.
Ira D. Ross ITT AVIONICS Nutley, New Jersey
Jack Davis JEPPESEN & COMPANY Denver, Colorado
M. J. Sommovigo JEPPESEN & COMPANY Washington, D.C.
James E. Terpstra JEPPESEN & COMPANY Denver, Colorado
John Cotton LITTON AERO PRODUCTS DIV. Woodland Hills, California
W. H. Harrison LITTON AERO PRODUCTS DIV. Woodland Hills, California
Wayne Kittner LITTON AERO PRODUCTS DIV. Woodland Hills, California
J. Van Der Bliek LOCKHEED CALIFORNIA COMPANY Burbank, California
Fred Ciechowski RAYMOND ENGINEERING, INC. Middletown, Connecticut
James H. Hill RAYMOND ENGINEERING, INC. Middletown, Connecticut
Martin R. Bates SIERRA RESEARCH CORP. Buffalo, New York
Frederick P. Allgower SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Donald Baker SPERRY FLIGHT SYSTEMS Phoenix, Arizona
 ARINC SPECIFICATION 424 - Page 257
APPENDIX 1
CHRONOLOGY AND BIBLIOGRAPHY

Larry Bowe SPERRY FLIGHT SYSTEMS Phoenix, Arizona

C. A. Hall SPERRY FLIGHT SYSTEMS Phoenix, Arizona
William Post SPERRY FLIGHT SYSTEMS Phoenix, Arizona
Daniel A. Giroux THOMSON-CSF, INC. Paris, France
J. Lane Ware THOMSON-CSF, INC. New York, New York
ARINC SPECIFICATION 424 - Page 258
APPENDIX 2
STRAIGHT-IN CRITERIA

Straight-in Criteria, FAA Type Procedures

Off-Airport Facility

The angle of convergence of the final approach course and extended runway centerline shall not exceed 30 degrees. The
final approach course should be aligned to intersect the runway centerline at the runway threshold. However, when an
operational advantage can be achieved, the point of intersection may be established as much as 3000 feet outward from the
runway threshold. See Figure AP2-1.

On-Airport Facility

The angle of convergence of the final approach course and extended runway centerline shall not exceed 30 degrees. The
final approach course should be aligned to intersect the runway centerline at a point 3000 feet outward from the runway
threshold. When an operational advantage can be achieved, this point of intersection may be established at any point
between the threshold and a point 5200 feet outward from the threshold. Also, where an operational advantage can be
achieved, a final approach course which does not intersect the runway centerline, or which intersects it at a distance greater
than 5200 feet from the threshold, may be established, provided that such a course lies within 500 feet laterally of the
extended runway centerline at a point 3000 feet outward from the runway threshold. See Figure AP2-2.

Figure AP2-1
Alignment Options for Final Approach Course Off-Airport VOR with FAF, Straight-In Approach

Figure AP2-2
Alignment Options for Final Approach Course On-Airport with FAF, Straight-In Approach
 ARINC SPECIFICATION 424 - Page 259
APPENDIX 2
STRAIGHT-IN CRITERIA

Straight-in Criteria, ICAO Type Procedures

The alignment of the final approach track with the runway centerline determines whether a straight-in or circling approach
may be established.

For a straight-in approach, the angle formed by the final approach track and the runway centerline shall not exceed 30
degrees and the distance between the runway threshold and the point oat which the final approach track intersects the runway
centerline shall not be less than 900 meters. A final approach track which does not intersect the extended centerline of the
runway may also be established, provided such a track lies within 150 meters laterally of the extended runway centerline at a
point 900 meters outward from the runway threshold. See Figure AP2-3.

Missed Approach Point (MAP)

Off-Airport Facility - Straight-in Approach

The MAP is located at a point on the final approach track which is not farther from the FAF or facility than the threshold.

Off-Airport Facility - Circling Approach

The MAP is located at a point on the final approach track which is not farther from the FAF than the first usable portion of
the landing surface.

On-Airport Facility

The MAP is located at a point on final approach track which is not farther from the FAF than the facility.

Figure AP2-3
Alignment Options for Final Approach Course Off-Airport VOR with FAF, Straight-In Approach
ARINC SPECIFICATION 424 – Page 260
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

32 Bit CRC Calculation 131

Additional Header Records 130
Additional Secondary Phase Factor (ASF) 112
Aircraft Use Group (ACFT USE GP) 119
Airport and Heliport Localizer and Glide Slope Continuation Records 21
Airport and Heliport Localizer and Glide Slope Primary Records 21
Airport and Heliport Localizer and Glide Slope Records (PI) 21
Airport and Heliport Localizer and Glide Slope Simulation Continuation Records 21
Airport and Heliport Localizer Continuation Records 22
Airport and Heliport Localizer Marker Records (PM) 22
Airport and Heliport Localizer Primary Records 22
Airport and Heliport Localizer/Glide Slope Section (P), Subsection (I) 9
Airport and Heliport Marker/Locator Marker Section (P), Subsection (M) 9
Airport and Heliport MLS (Azimuth, Elevation and Back Azimuth) Records 28
Airport and Heliport MLS Continuation Records 29
Airport and Heliport MLS Primary Records 29
Airport and Heliport MLS Section (P), Subsection (L) 9
Airport and Heliport Path Point Section (P), Subsection (P) 9
Airport and Heliport Terminal NDB Section (P), Subsection (N) 9
Airport Approaches Section (P), Subsection (F) 7
Airport Communications Continuation Records 23
Airport Communications Continuation Records 23
Airport Communications Primary Records 23
Airport Communications Records (PV) 23
Airport Communications Section (P), Subsection (V) 9
Airport Continuation Records 18
Airport Flight Planning Continuation Records 18
Airport Flight Planning Continuation Records 18
Airport Gate Continuation Records 18
Airport Gate Primary Records 18
Airport Gate Records (PB) 18
Airport Gates Section (P), Subsection (B) 6
Airport MSA (Minimum Sector Altitude) Records (PS) 26
Airport MSA Continuation Records 26
Airport MSA Primary Records 26
Airport Primary Records 17
Airport Records (PA) 17
Airport Reference Points Section (P), Subsection (A) 6
Airport Runway Section (P), Subsection (G) 9
Airport Section (P) 6
Airport SID/STAR Flight Planning Continuation Records 20
Airport SID/STAR/Approach (PD, PE and PF) 18
Airport SID/STAR/Approach Continuation Records 19
Airport SID/STAR/Approach Flight Planning Continuation Records 20
Airport SID/STAR/Approach Primary Records 19
Airport Standard Instrument Departures (SIDs) Section (P), Subsection (D) 7
Airport Standard Terminal Arrival Routes (STARs) Section (P), Subsection (E) 7
Airport TAA (PK) 35
Airport TAA Primary Records 35
Airport Terminal Arrival Altitude Continuation Records 35
Airport Terminal Waypoints Section (P), Subsection (C) 7
Airport Waypoint 133
Airport Waypoint 140
Airport/Heliport Elevation (ELEV) 80
Airport/Heliport Identifier (ARPT/HELI IDENT) 56
Airport-Related Waypoints 140
Airway Minimum Altitudes and Required Navigation Performance (RNP) 170
Airway Restriction Start/End Date (START/END DATE) 106
Airways Marker Continuation Records 24
Airways Marker Primary Records 23
Airways Marker Records (EM) 23
Along Track Distance (ATD) 121
 ARINC SPECIFICATION 424 – Page 261
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Alternate Distance (ALT DIST) 89

Alternate Primary Records 34
Alternate Record (RA) 34
Alternate Record Type (ART) 124
Alternate Type (ALT TYPE) 125
Altitude (ALT) 123
Altitude Description (ALT DESC) 71
Altitude Limitation (ALT LIMIT) 116
Altitude/Minimum Altitude 71
Application of CRC for Integrity Protection of Straight & Advanced Landing Approach Operations 131
Approach Performance Designator (APD) 125
Approach Procedure Rules Valid For All Procedure Types 203
Approach Route Identifier (APPROACH IDENT) 60
Approach Transition Route Coding Rules 206
Approach Type Identifier (ATI) 126
Arc Bearing (ARC BRG) 97
Arc Distance (ARC DIST) 97
ARC Radius (ARC RAD) 115
ATA/IATA Designator (ATA/IATA) 95
ATC Identifier (ATC ID) 122
ATC Indicator (ATC) 88
ATC Weight Category (ATC WC) 122
Azimuth Coverage Sector Right/Left (AZ COV RIGHT/LEFT)Back Azimuth Coverage Sector Right/Left (BAZ COV 109
RIGHT/LEFT)
Azimuth Proportional Angle Right/Left (AZ PRO RIGHT/LEFT) Back Azimuth Proportional Angle Right/Left (BAZ 108
PRO RIGHT/LEFT)
Beginning And Ending Leg Types 175
Bit Density 130
Block Indicator (BLOCK IND) 114
Boundary Code (BDY CODE) 67
Boundary Via (BDRY VIA) 97
Call Sign (CALL SIGN) 94
Center Fix (CENTER FIX) 103
Channel 108
Chronology and Bibliography 255
Circle-to-Land Approach Procedure Coding 212
Coding 130
Coding Rules Applicable To All Procedures 183
Communication Altitude (COMM ALTITUDE) 111
Communications Distance (COMM DIST) 111
Communications Frequency (COMM FREQ) 93
Communications Type (COMM TYPE) 92
Company Route and Alternation Destination Section (R) 9
Company Route Ident 86
Company Route Primary Records 22
Company Route Records (R) 21
Company Route Section (R), Subsection (Blank) 9
Component Affected Indicator (COMP AFFTD IND) 115
Component Elevation (GS ELEV, EL ELEV, AZ ELEV, BAZ ELEV) 85
Continuation Record Application Type (APPL) 90
Continuation Record Number (CONT NR) 63
Controlled Airspace Center (ARSP CNTR) 117
Controlled Airspace Classification (ARSP CLASS) 118
Controlled Airspace Continuation Records 31
Controlled Airspace Indicator (CTLD ARSP IND) 118
Controlled Airspace Name (ARSP NAME) 118
Controlled Airspace Primary Records 31
Controlled Airspace Records (UC) 31
Controlled Airspace Section (U), Subsection (C) 10

cclxi
ARINC SPECIFICATION 424 – Page 262
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Controlled Airspace Type (ARSP TYPE) 117

Controlling Agency 102
Cost Index 90
Course FROM/TO 101
Course Width at Threshold (CRSWDTH) 120
Coverage of Flight Planning Needs 1
Coverage of Flight Simulator Needs 1
Coverage of Helicopter Operation Needs 2
CRC – Generator Polynomial, G(x) 132
CRC Calculations 130
Cruise Altitude 89
Cruise Level From/To 101
Cruise Table Identifier (CRSE TBL IDENT) 101
Cruising Table Primary Records 24
Cruising Table Section (T) 10
Cruising Tables Records (TC) 24
Cruising Tables Section (T), Subsection (C) 10
Customer/Area Code (CUST/AREA) 55
Cycle Date (CYCLE) 72
Data Block Structure, M(x) 131
Data Format Standardization Philosophy 1
Data Processing Terms 4
Datum Code (DATUM) 113
Daylight Time Indicator (DAY TIME) 110
Decision Height (DH) 108
Direction Restriction 96
Distance Description (DIST DESC) 111
Distance Limitation (DIST LIMIT) 116
Distance To Alternate (DTA) 124
DME Elevation (DME ELEV) 77
DME Identifier (DME IDENT) 76
Duplicate Identifier (DUP IND) 96
Elevation Angle Span (EL ANGLE SPAN) 108
Ellipsoidal Height 120
End-of-File Trailer Label (EOF) 130
End-of-Volume Trailer Label (EOV) 130
Enroute Airway Marker Section (E), Subsection (M) 6
Enroute Airways Continuation Records 17
Enroute Airways Flight Planning Continuation Records 17
Enroute Airways Flight Planning Continuation Records 17
Enroute Airways Primary Records 16
Enroute Airways Records (ER) 16
Enroute Airways Restriction Altitude Exclusion Continuation Records 28
Enroute Airways Restriction Altitude Exclusion Primary Records 26
Enroute Airways Restriction Cruising Table Replacement Continuation Records 28
Enroute Airways Restriction Cruising Table Replacement Primary Records 28
Enroute Airways Restriction Note Restriction Continuation Records 27
Enroute Airways Restriction Note Restriction Primary Records 27
Enroute Airways Restriction Seasonal Closure Primary Records 27
Enroute Airways Restrictions Section (E), Subsection (U) 6
Enroute Airways Restrictive Records (EU) 26
Enroute Airways Section (E), Subsection (R) 6
Enroute Alternate Airport (EAA) 105
Enroute Communications Continuation Records 30
Enroute Communications Continuation Records 30
Enroute Communications Primary Records 29
Enroute Communications Records (EV) 29
Enroute Communications Section (E), Subsection (V) 6
Enroute Section 6
Enroute Waypoint Section (E), Subsection (A) 6
ENRT TRANS 89
EU Indicator (EU IND) 107
 ARINC SPECIFICATION 424 – Page 263
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Exclusion Indicator (EXC IND) 114

Facility Characteristics (FAC CHAR) 90
Facility Elevation (FAC ELEV) 90
Figure of Merit (MERIT) 105
File Record Number (FRN) 72
Final Approach Path Coding – Circle-to-Land Procedures 231
Final Approach Path Coding – GNSS-Based Procedure 231
Final Approach Path Coding – Helicopter Approach Procedures 231
Final Approach Path Coding – Localizer-Based Procedures 229
Final Approach Path Coding – NDB-Based Procedures 230
Final Approach Path Coding – VOR-Based Procedures 229
Final Approach Segment 227
Final Approach Segment DATA CRC Remainder (FAS CRC) 121
FIR/RDO Identifier (FIR/RDO) 112
FIR/UIR Address (ADDRESS) 106
FIR/UIR ATC Reporting Units Altitude (RUA) 98
FIR/UIR ATC Reporting Units Speed (RUS) 98
FIR/UIR Entry Report (ENTRY) 98
FIR/UIR Identifier (FIR/UIR IDENT) 96
FIR/UIR Indicator (IND) 97
FIR/UIR Name 98
FIR/UIR Primary Records 24
FIR/UIR Records (UF) 24
FIR/UIR Section (U), Subsection (F) 9
First Leg of Missed Approach Procedure 251
Fix Identifier (FIX IDENT) 62
Fix Identifiers 133
Fix Related Transition Code (FRT Code) 123
Fixed Radius Transition Indicator (FIXED RAD IND) 125
Flight Planning Arrival/Departure Data Record Section (P), Subsection (R) 9
Flight Planning Arrival/Departure Data Records (PR) 32
Flight Planning Continuation Records 33
Flight Planning Continuation Records 33
Flight Planning Primary Records 32
Flow Diagram 144
FMS and GPS Procedure Coding 213
Frequency Protection Distance (FREQ PRD) 105
Frequency Units (FREQ UNIT) 94
From/To - Airport/Fix 86
Gate Identifier (GATE IDENT) 80
General Rules, Applicable To All Approach Route Coding 204
Generator Polynomials 131
Geographical Entity (GEO ENT) 118
Geographical Reference Table Continuation Records 32
Geographical Reference Table Identifier (GEO REF TBL ID) 118
Geographical Reference Table Primary Records (TG) 32
Geographical Reference Table Records (TG) 32
Geographical Reference Table Section (T), Subsection (G) 10
Geographical Routings 143
Glide Path Angle (GPA) 120
Glide Slope Angle (GS ANGLE) Minimum Elevation Angle (MIN ELEV ANGLE) 80
Glide Slope Beam Width (GS BEAM WIDTH) 92
Glide Slope Position (GS FR RW THRES) Elevation Position (EL FR RW THRES) 79
GLS Channel 123
GLS Continuation Records 34
GLS Precision Approach Procedure Coding 228
GLS Primary Records 34
GLS Record (PT) 34
GLS Station Identifier 123

cclxiii
ARINC SPECIFICATION 424 – Page 264
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

GNSS Landing System (GLS) Section (P), Subsection (T) 9

Government Source (SOURCE) 91
GPS/FMS Indicator (GPS/FMS IND) 119
Grid MORA 102
Grid MORA Primary Records 25
Grid MORA Records (AS) 25
Group Repetition Interval (GRI) 112
Guard/Transmit (G/T) 110
H24 Indicator (H24) 110
HAL 126
Header 1 Label (HDR 1) 130
Header 2 Label (HDR 2) 130
Header Record 1 129
Header Record 2 130
Helicopter Procedure Coding 213
Helicopter Procedure Course (HPC) 127
Heliport (TAA) 40
Heliport Approaches Section (H), Subsection (F) 10
Heliport Communications Continuation Records 39
Heliport Communications Continuation Records 40
Heliport Communications Primary Records 39
Heliport Communications Records (HV) 39
Heliport Communications Section (H), Subsection (V) 11
Heliport Continuation Records 35
Heliport Flight Planning Continuation Records 36
Heliport Flight Planning Continuation Records 36
Heliport MSA (MS) 38
Heliport MSA Continuation Records 39
Heliport MSA Primary Records 39
Heliport MSA Section (H), Subsection (S) 10
Heliport Primary Records 35
Heliport Records 35
Heliport Section (H), Subsection (A) 10
Heliport SID/STAR/Approach (HD/HE/HF) 37
Heliport SID/STAR/Approach Continuation Records 38
Heliport SID/STAR/Approach Flight Planning Continuation Records 38
Heliport SID/STAR/Approach Flight Planning Continuation Records 38
Heliport SID/STAR/Approach Primary Records 37
Heliport Standard Instrument Departures (SIDs) Section (H), Subsection (D) 10
Heliport Standard Terminal Arrival Routes (STARs) Section (H), Subsection (E) 10
Heliport TAA Primary Records 40
Heliport Terminal Arrival Area Continuation Records 40
Heliport Terminal Arrival Area Section (H), Subsection (K) 11
Heliport Terminal Waypoint Continuation Records 36
Heliport Terminal Waypoint Flight Planning Continuation Records 36
Heliport Terminal Waypoint Flight Planning Continuation Records 37
Heliport Terminal Waypoint Primary Records 36
Heliport Terminal Waypoint Records (HC) 36
Heliport Terminal Waypoints Section (H), Subsection (C) 10
High Precision Latitude (HPLAT) 127
High Precision Longitude (HPLONG) 127
High/Low (HIGH/LOW) 95
Holding Pattern Continuation Records 16
Holding Pattern Records (EP) 15
Holding Patterns (E), Subsection (P) 6
Holding Primary Records 16
Holding Speed (HOLD SPEED) 109
ICAO Code (ICAO CODE) 63
IFR Capability (IFR) 95
ILS/DME Bias 90
ILS/MLS/GLS Category (CAT) 88
Inbound Holding Course (IB HOLD CRS) 81
 ARINC SPECIFICATION 424 – Page 265
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Inbound Magnetic Course (IB MAG CRS) 70

Initial/Terminus Airport/Fix 112
Jointly and Specifically Used Sections/Subsections 10
Labels 130
Landing Threshold Elevation (LANDING THRES ELEV) 82
Latitude (LATITUDE) 75
Leg Data Fields 182
Leg Length (LEG LENGTH) 81
Leg Sequencing 176
Leg Time (LEG TIME) 81
Leg Type Code (LTC) 122
Leg Type Descriptions 177
Length Offset (OFFSET) 125
Level (LEVEL) 67
Local Horizontal Reference DATUM Name, Datum Code, and Ellipsoid List 146
Localizer Based Approach Procedure Coding 208
Localizer Bearing (LOC BRG) 79
Localizer Frequency (FREQ) 78
Localizer Position (LOC FR RW END Azimuth/Back Azimuth Position (AZ/BAZ FR RW END) 79
Localizer Width (LOC WIDTH) 79
Localizer/Azimuth Position Reference (@, +, -) 79
Localizer/MLS/GLS Identifier (LOS, MLS, GLS IDENT) 78
Longest Runway (LONGEST RWY) 80
Longest Runway Surface Code (LRSC) 124
Longitude (LONGITUDE) 75
Loran Coding Rules Deleted by Supplement 14 212
Lower/Upper Limit 97
Magnetic Variation (MAG VAR, D MAG VAR) 76
Magnetic/True Indicator (M/T IND) 107
Marker Code (MARKER CODE) 95
Marker Ident (MARKER IDENT) 95
Marker Shape (SHAPE) 95
Marker Type (MKR TYPE) 92
Master Airline User File 12
Master Airline User File Content 6
Master Helicopter User File (HA) 35
Master Helicopter User File Content 10
Maximum Altitude (MAX ALT) 98
Minimum Descent Height (MDH) 108
Minor Axis Bearing (MINOR AXIS TRUE BRG) 92
Missed Approach Point 251
Missed Approach Procedure Rules Valid For All Procedure Types 251
MLS Approach Procedure Coding 209
MLS Approach Procedure Coding 228
MLS Azimuth Bearing (MLS AZ BRG) MLS Back Azimuth Bearing (MLS BAZ BRG) 108
Modulation (MODULN) 113
MORA Section (A), Subsection (S) 10
MSA Section (P), Subsection (S) 9
Multiple Approach Procedure Coding 203
Multiple Code (MULTI CD) 100
Multiple Files, One Reel 130
Multiple Routes - Geographical 143
Multiple Routes - Off Load 143
Multiple Routes - Overfly 142
Multiple Routes - Same Fix 142
Multiple Routes - Same Points/Areas/Regions 142
Name (NAME) 81
Name Field 85
Name Format Indicator (NAME IND) 113

cclxv
ARINC SPECIFICATION 424 – Page 266
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Named RNAV Waypoints, Intersections, and Reporting Points 133

Named Waypoints 139
Narrative 111
NAVAID Class (CLASS) 73
Navaid Limitation Code (NLC) 115
NAVAID Related Leg Types 174
NAVAID Section (D) 6
Navaid Waypoint 133
Navaid Waypoint 140
Navigation Data/File Data Relationship 154
NDB Approach Procedure Coding 211
NDB NAVAID Continuation Records 14
NDB NAVAID Flight Planning Continuation Records 14
NDB NAVAID Flight Planning Continuation Records 14
NDB NAVAID Primary Records 14
NDB NAVAID Record (DB or PN) 13
NDB Navaid Section (D), Subsection (B) 6
NDB NAVAID Simulation Continuation Records 14
Nominal Elevation Angle (NOM ELEV ANGLE) 109
Non-Directional Beacons (NDB) 133
Non-precision Approach Procedure Coding 229
North American Routes 142
NOTAM 101
Notes (Continuation Records) (NOTES) 81
Number of Engines Restriction (NOE) 121
Number of Tape Tracks 129
Off Load Route 143
One File, Multiple Reels 130
One File, One Reel 130
Operations Type (OPS TYPE) 120
Organization of this Document 2
Orthometric Height (ORTH HGT) 120
Other Missed Approach Procedure Considerations 252
Outbound Magnetic Course (OB MAG CRS) 70
Pad Dimensions 109
Pad Identifier (PAD IDENT) 110
Parity Convention 130
Path and Termination (PATH TERM) 67
Path and Termination Related Rules Valid For All Procedure Types 184
Path and Terminator 173
Path Point Continuation Records 34
Path Point Primary Records 33
Path Point Records (PP) 33
Path Point TCH 126
Precision Approach Path Point Cyclic Redundancy Check (CRC) Overview 130
Precision Approach Procedure Coding 227
Precision RNAV Terms 5
Preferred or Preferential Overfly Routings 142
Preferred or Preferential Routes 142
Preferred Route Continuation Records 31
Preferred Route Continuation Records (ET) 31
Preferred Route Identifiers 142
Preferred Route Use Indicator (ET IND) 119
Preferred Routes Primary Records 30
Preferred Routes Records (ET) 30
Preferred Routes Section (E), Subsection (T) 10
Preferred Weekday/Weekend 143
Primary and Additional Alternate Identifier (ALT IDENT) 125
Procedure Category (PRO CAT) 123
Procedure Description (PROC DESC) 122
Procedure Turn (PROC TURN) 127
Procedure Type (PROC TYPE) 121
 ARINC SPECIFICATION 424 – Page 267
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Public/Military Indicator (PUB/MIL) 109

Purpose of this Document 1
Radar (RADAR) 93
Radius Limit 105
Recommended NAVAID (RECD NAV) 67
Record Type (S/T) 55
Reel-File Relationship 130
Reference Documentation 2
Reference Path Data Selector (REF PDS) 125
Reference Path Identifier (REF ID) 125
Region Code (REGN CODE) 77
Remote Facility (REM FAC) 114
Remote Site Name 112
Reporting Code (RPT) 122
Reporting Positions Defined by Coordinates 133
Required Navigation Performance (RNP) 117
Restriction Altitude (REST ALT) 107
Restriction Identifier (REST IDENT) 106
Restriction Notes 107
Restriction Record Type (REST TYPE) 114
Restrictive Airspace Continuation Records 25
Restrictive Airspace Designation 100
Restrictive Airspace Flight Planning Continuation Records 25
Restrictive Airspace Link Continuation (LC) 109
Restrictive Airspace Name 98
Restrictive Airspace Primary Records 25
Restrictive Airspace Records (UR) 24
Restrictive Airspace Section (U), Subsection (R) 9
Restrictive Airspace Type (REST TYPE) 100
Rho (RHO) 70
RNAV – GPS/GLS Approach Procedure Path Point Data Field Bits 131
RNAV Flag (RNAV) 122
Route Distance From, Holding Distance/Time (RTE DIST FROM, HOLD DIST/TIME) 70
Route Identifier (ROUTE IDENT) 59
Route Indicator (RTE IND) 120
Route Type (RT TYPE) 58
Runway Continuation Records 20
Runway Description (RUNWAY DESCRIPTION) 81
Runway Gradient (RWY GRAD) 117
Runway Identifier (RUNWAY ID) 79
Runway Length (RUNWAY LENGTH) 81
Runway Magnetic Bearing (RWY BRG) 81
Runway Primary Records 20
Runway Records (PG) 20
Runway Simulation Continuation Records 20
RUNWAY TRANS 89
Runway Width (WIDTH) 95
SBAS Service Provider Identifier (SBAS ID) 125
Section Code (SEC CODE) 55
Sector Altitude (SEC ALT) 105
Sector Bearing (SEC BRG) 105
Sector Facility (SEC FAC) 111
Sector From/Sector To (SECTR) 115
Sectorization (SECTOR) 111
Sequence End Indicator (SEQ END) 117
Sequence Number (SEQ NR) 62
Service Indicator (SER IND) 94
Service Volume Radius 123
SID/STAR Procedure Identifiers 140

cclxvii
ARINC SPECIFICATION 424 – Page 268
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

SID/STAR Route Identifier (SID/STAR IDENT) 60

SID/STAR/App/AWY (S/S/A/AWY) SID/STAR/Awy (S/S/AWY) 88
Signal Emission (SIG EM) 114
Special Navigation Terms 4
Special Use Airspace Section (U) 9
Speed Limit (SPEED LIMIT) 85
Speed Limit Altitude 85
Speed Limit Description 126
Standard Instrument Departure (SID) Coding Rules 188
Standard Terminal Arrival Route (STAR) Coding Rules 198
Start/End Date 106
Start/End Indicator (S/E IND) 106
Starting Latitude 102
Starting Longitude 102
Station Declination (STN DEC) 82
Station Elevation WGS84 124
Station Type 124
Step Climb Indicator (STEP) 107
Stopway 88
Straight-In Criteria 259
Subject Index 260
Subsection Code (SUB CODE) 55
Summary of Tape Data Layout 130
TAA IAF Waypoint 128
TAA Sector Identifier 127
TAA Sector Radius 128
TACAN Approach Procedure Coding 211
Tape Marks 130
TCH Units Indicator 127
TCH Value Indicator (TCHVI) 127
TDMA Slots 124
TDZE Location (LOCATION) 92
Terminal Procedure Flight Planning Leg Distance (LEG DIST) 126
Terminal Waypoints 136
Terminal/Alternate Airport (TERM/ALT ARPT) 89
The Alternate Record Section (R), Subsection (A) 9
Theta (THETA) 70
Threshold Crossing Height (TCH) 82
Threshold Displacement Distance (DSPLCD THR) 85
Time Code (TIME CD) 100
Time Indicator (TIME IND) 102
Time of Operation 112
Time Zone 110
To FIX 89
Touchdown Zone Elevation (TDZE) 92
Transition Altitude/Level (TRANS ALTITUDE/LEVEL) 80
Transition Identifier (TRANS IDENT) 61
Transition Identifiers 143
Triad Stations (TRIAD STA) 112
True Bearing (TRUE BRG) 91
Turboprop/Jet Indicator (TURBO) 121
Turn (TURN) 81
Turn Direction (TURN DIR) 67
Turn Direction Valid (TDV) 67
Unit Indicator (UNIT IND) 101
Units of Altitude (UNIT IND) 107
Unnamed Waypoints 133
Unnamed Waypoints 139
User File Organization 6
VAL 126
Vertical Angle (VERT ANGLE) 85
Vertical Navigation Path (VNAV Path) or Descent Gradient Considerations 231
 ARINC SPECIFICATION 424 – Page 269
APPENDIX 3
SUBJECT INDEX

SUBJECT PAGE

Vertical Path of Missed Approach Procedure 251

Vertical Separation 101
VFR Waypoints 140
VHF NAVAID Continuation Records 12
VHF NAVAID Flight Planning Continuation Records 13
VHF NAVAID Flight Planning Continuation Records 13
VHF NAVAID Limitation Continuation Record 13
VHF NAVAID Primary Records 12
VHF NAVAID Record (D) 12
VHF Navaid Section (D), Subsection (Blank) 6
VHF NAVAID Simulation Continuation Records 13
VIA Code 86
VNAV Coding of Non-Precision Approach Procedures with Missed Approach Points – Other Than Landing 232
Threshold
Volume Header Label (VOL) 130
VOR, VORDME, VORTAC and RNAV Approach Procedure Coding 210
VOR, VORDME, VORTAC, TACAN, and Non-Directional Beacons (NDB) 133
VOR/NDB Frequency (VOR/NDB FREQ) 73
VOR/NDB Identifier (VOR IDENT/NDB IDENT) 72
Waypoint Continuation Records 15
Waypoint Description Code (DESC CODE) 63
Waypoint Flight Planning Continuation Records 15
Waypoint Flight Planning Continuation Records 15
Waypoint Name/Description 139
Waypoint Name/Description (NAME/DESC) 78
Waypoint Primary Records 15
Waypoint Record (EA) or (PC) 14
Waypoint Type (TYPE) 77
Waypoint Usage 88
Weekday/Weekend 143

cclxix
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 1

TO

ARINC SPECIFICATION 424

(AREA) NAVIGATION SYSTEM DATA BASE

Published: September 8, 1980

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: June 17, 1980

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 1.3 Organization of this Document

This Supplement overhauls and extends the coverage of Second paragraph of section deleted to reflect deletion of
Specification 424 to enable the data base defined therein ADEU card standards from the Specification by this
to support the navigation functions of ARINC 702 and Supplement.
similar flight management computers.
ORIGINAL TEXT FOLLOWS
B. ORGANIZATION OF THIS SUPPLEMENT
(Second paragraph of 1.3)
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced The document closes with a consideration of the
into the Specification by this Supplement. The second standards applicable to the data cards employed with
part consists of replacement white pages for the airborne Automatic Data Entry Units (ADEUs).
Specification modified to reflect these changes. The
modified and added material on each replacement page is 1.4 Reference Documents
identified with c-1 symbols in the margins.
ARINC Characteristic 702, “Flight Management
Existing copies of Specification 424 may be updated by Computer System” added to list of navigation systems
inserting the replacement white pages where necessary with which the Specification 424 data base may be used.
and destroying the pages they displace. The goldenrod
pages should be inserted inside the rear cover of the 2.1 Data Processing Terms
Specification.
Definition for “card” deleted. Definition for “subsection”
Copies of the Specification bearing the number 424-1 modified.
already contain this Supplement and thus do not require
revisions by the reader. ORIGINAL TEXT FOLLOWS

C. CHANGES TO ARINC SPECIFICATION 424 Card A data storage medium in the form of a thin
INTRODUCED BY THIS SUPPLEMENT flexible board on which information is
encoded magnetically, by a pattern of
This Section presents a complete tabulation of the punched holes, by a pattern of visible marks
changes and additions to the Specification introduced by or by other means.
this Supplement. Each change or addition is entitled by
the section number and title currently employed in the Subsection A collection of records of functionally
Specification, or by the section number and title that will similar RNAV data items. The records for
be employed when the Supplement is eventually high level enroute airways form a
incorporated. In each case there is included a brief subsection of the data base.
description of the addition or change and, for other than
very minor revisions, any text originally contained in the 3.2.3 Navaid Section (D) NDB Subsection (DB)
Specification is reproduced for reference.
New section introduced by this Supplement to introduce
TITLE AND CHAPTER HEADINGS new master file subsection.

Title of document changed from “Area Navigation 3.2.4 Enroute Section (E)
System Data Base” to “Navigation System Data Base.”
“RNAV” changed to “Navigation” in chapter headings Section 3.2.3 of Specification 424 amended to include
and in text. holding patterns and a new approach to airways
classification. original Section 3.2.4 deleted.
1.2 Data Format Standardization Philosophy
ORIGINAL TEXT FOLLOWS
Final two sentences of third paragraph of section
amended to refer to new format standards for tailored 3.2.3 Enroute Section (E)
company route data introduced into the document by this
Supplement. Commentary added following first The Enroute section of the master airline user file should
paragraph. contain:
(i) all waypoints for EB, EH and EL airways,
ORIGINAL TEXT FOLLOWS
(ii) all government-designated airways.
(Final two sentences of third paragraph of 1.2)
3.2.4 Holding Pattern Section (H)
A tailored record may contain data for which formatting
rules may be found in this document, or data for which no The Holding Pattern section of the master airline user file
such rules have been established. In the latter case, an should contain all holding patterns designated by
arbitrary format will be used. governments for charting.
 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 3

3.2.8 Airport Section (P) – Standard Instrument final approach fix (FAF) and require a course reversal are
Departures (SIDs) Subsection (PD) not included.

Second and third sentences of paragraph deleted. 3.2.11 Airport Section (P) – Runways Subsection (PG)

ORIGINAL TEXT FOLLOWS Section revised to call for runway records to be included
in the master airline user file.
(Second and third sentences of 3.2.8)
ORIGINAL TEXT FOLLOWS
Evaluation and conventional SIDs are not included in the
master airline user file. They are, however, available in Runway records are not included in the master airline
data banks in standard record format for those airlines user file since they are not required for basic RNAV
that desire them. system operation. If needed for other operations, runway
information is available in standard file and record
3.2.9 Arrival Section (P) – Standard Terminal Arrival format, and may be ordered by those persons needing it.
Routes (STARs) Subsection (PE)
3.2.13 Company Route Section (R)
Second and third sentences of paragraph deleted.
Section amended to delete statement that company route
ORIGINAL TEXT FOLLOWS information is not included in the master airline user file.

Second and third sentences of 3.2.9) ORIGINAL TEXT FOLLOWS

Evaluation and conventional STARs are not included in Company route information is available only as tailored
the master airline user file. They are, however, available records, and thus will not be included in the master
in data banks in standard record format for those airlines airline user file. Formats for these tailored records are not
that desire them. specified in this document.

3.2.10 Airport Section (P) – Approach Routes 4.1 General

Subsection (PF)
Section paragraph amended to indicate that the standard
Section revised. Referenced figure (3-2) deleted. record length is increased from 108 to 132 columns.

ORIGINAL TEXT FOLLOWS ARINC STAFF NOTE: This record length increase
affects every record layout description in Chapter 4. Also,
The Approach Route subsection of the master airline user changes in Chapter 5 introduced by this Supplement, yet
file should contain all published RNAV approach routes to be described, further affect many of them. We are
to the airports referenced in Section 3.2.5 of this therefore presenting the whole of the original Chapter 4
document. As illustrated in Figure 3-2, an approach route as “ORIGINAL TEXT” for reference, marked “Obsolete
starts at the intermediate fix (IF) waypoint and ends at the – do not use.”
missed approach holding waypoint. The published
waypoints between these two waypoints are included, 4.12 Company Route Records
except for step-down fixes. Transitions from the enroute
structure that proceed to the intermediate fix are included. New section added by this Supplement.
Transitions from the enroute structure that proceed to the
SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 4

3.0 RNAV DATA – ORGANIZATION AND CONTENT (cont’d)

 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 5

4.0 RNAV DATA – RECORD LAYOUT

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 6

4.0 RNAV DATA – RECORD LAYOUT (cont’d)

 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 7

4.0 RNAV DATA – RECORD LAYOUT (cont’d)

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 8

4.0 RNAV DATA – RECORD LAYOUT (cont’d)

 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 9

4.0 RNAV DATA – RECORD LAYOUT (cont’d)

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 10

4.0 RNAV DATA – RECORD LAYOUT (cont’d)

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 11
SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 12
 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 13

5.5 Subsection Code (SUB CODE) SID/STAR Records

“Holding patterns” deleted from list of records in which SID/STAR Route Type Field Content
the subsection code appears. Code definition table SID Runway Transition 1
revised. SID 2
SID Enroute Transition 3
ORIGINAL TEXT FOLLOWS STAR Enroute Transition 4
STAR 5
(Code definition table only) STAR Runway Transition 6
Section Section Name Subsection Subsection Name Approach Route Records
Code Code
D VHF NAVAID Approach Route Type Field Content
Back Course B
E Enroute A Waypoint ILS I
B Both Level Airways* Localizer L
H High Level Airways RNAV R
L Low Level Airways NDB N
H Holding Transition T
Patterns VOR V
P Airport A Reference Point MLS M
B Airline Gates
C Terminal Waypoints 5.9 SID/STAR Route Identifier (SID/STAR IDENT
D SIDs
E STARs “MONTH6” added to list of examples.
F Approach Routes
G Runways 5.11 Transition Identifier (TRANS IDENT)
I ILS NAV Data
R Company Transition identifier field content table revised.
Routes
ORIGINAL TEXT FOLLOWS
*Airways not designated as either high level or low level.
(Table only)
Table (i)
Section and Subsection Encoding Record “Route Type” “Transition Identifier”
Scheme Field Content Field Content
SID/STAR 1 SID runway transition
5.7 Route Type (RT TYPE) identifier
2 Blank
Code definition table revised. 3 SID enroute transition
identifier
ORIGINAL TEXT FOLLOWS 4 STAR enroute transition
identifier
(Code definition table only.) 5 Blank
6 STAR runway transition
Source/Content: identifier
Approach T Waypoint identifier of
Enroute Airways Records Routes first waypoint of transition
All other Blank
Airway Type Field Content possible entries
Control C
Direct D Table (ii)
High Level H Transition Identifier Field Content
Jet J
Low Level L
NDB N 5.12 Sequence Number (SEQ NR)
RNAV R
Victor V Company route records added to the list of records in
which the sequence number field is used. Three-character
Note: Additional codes may be defined in the future. field length specified for this application.
SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 14

5.13 Waypoint Identifier (WAYPOINT IDENT)

End of Continuous Airway E
Restriction of use of VHF NAVAID identifier as Gateway Waypoint G
waypoint identifier to enroute records only is removed. Non-essential Waypoint* R
Company Route records added to “Used On” list. Transition Essential Waypoint* T
VOR, VORDME, VORTAC V
ORIGINAL TEXT FOLLOWS * See Chapter 2 for definitions.
(Definition/Description paragraph only.) Table (iii)
Waypoint Description Codes
Definition/Description: The “Waypoint Identifier” field
contains the five-character name, or other series of 5.19 LEVEL
characters, with which the waypoint is identified. Enroute
records can also contain the VHF NAVAID identifier New section introduced by this Supplement. Previous
(see paragraph 5.21) in this field. Section 5.19 deleted.
5.15 File Code (D/E/P) ORIGINAL TEXT FOLLOWS
Definition/Description amended to apply file code to all 5.19 Forward Change-Over Point (To) (FWD COP
route records. (TO))
“Source/Content” table modified to reflect new Definition/Description: Change-over points (COPs are
arrangement of master file Terminal Section and to add the locations at which the onboard navigation sensor
reference to use on company route records. receivers are turned to a new ground facility. The
“Forward Change-Over Point (To)” field contains the
ORIGINAL TEXT FOLLOWS distance in nautical miles from the previous change-over
point on the route segment to the waypoint identified in
Definition/Description: The record for a waypoint the record.
identified in an enroute airway, SID/STAR or Approach
Route record may reside in one of a number of major Source/Content: Official government-source COP data
sections of the data base. The “File Code” field permits will be entered when available. See Attachment 3 for
the section in which a particular waypoint record will be further information.
found to be identified.
Used On: Enroute Airways, SID/STAR and
Source/Content: Approach Route records.
Code Waypoint Record Source Length: 3 characters
D NAVAID Section (Waypoint is a NAVAID) Character Type: Numeric
Enroute Waypoint Section Examples: 064, 130, 000
E Terminal Waypoint Section (SID/STAR &
P Approach Route records only). 5.20 Turn Direction

Used on: Enroute Airways, SID/STAR, New section introduced by this Supplement. Previous
Approach Route and Holding Pattern Section 5.20 deleted.
records.
Length: 1 character ORIGINAL TEXT FOLLOWS
Character Type: Alpha
5.20 Backward Change-Over (From) (BWD COP
(FROM))
5.17 Waypoint Description Code (DESC CODE)
Definition/Description: Change-over points (COPs) are
The Note in “source/content” paragraph was deleted. the locations at which the onboard navigation sensor
“Source/content” code definition table replaced. receivers are tuned to a new ground facility. The
“Backward Change-Over Point (From)” field contains the
distance in nautical miles to the next change-over point
ORIGINAL TEXT FOLLOWS on the route segment from the waypoint identified in the
record.
(“Source/content paragraph and coding table.)
Source/Content: Official government-source COP data
Source/Content: See Table (iii). Note that an entry is will be entered when available. See Attachment 3 for
always made in column 38 of the record. The entry may further information.
or may not be supplemented with entries in columns 39
and 40 of the record. When it is not, these columns will Used On: Enroute Airways records
be left blank. When a holding pattern is available for a fix Length: 3 characters
on a route, the alpha character “H” should be entered in Character Type: Numeric
column 41. This column should be left blank otherwise. Examples: 064, 130, 000
 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 15

5.21 Path and Termination (PATH TERM) Source/Content: The 2-, 3- or 4-character identification
code of the FAA-defined second alternative VHF
New section introduced by this Supplement. Original NAVAID facility to that recommended (see paragraph
Section 5.21 deleted. 5.21) is entered into this field when available.

ORIGINAL TEXT FOLLOWS Used On: Enroute Airways, SID/STAR and

Approach Route records.
5.21 Recommended VHF NAVAID (REC’D VHF) Length: 4 characters max.
Character Type: Alpha/Numeric
Definition/Description: The VHF NAVAID Examples: PHX, SEA, YUL, 6YA, T1KX
recommended for use as the reference facility for the
waypoint specified in the record’s “waypoint identifier” 5.26 Outbound Magnetic Course (OB MAG CRS)
field is identified in the “Recommended VHF NAVAID”
field. Second sentence added to “Definition/Description”
paragraph.
Source/Content: The 2-, 3- or 4-character identification
code of the NAVAID appears in t his field. NAVAIDs 5.27 Route Distance From, Holding Distance/Time
recommended for waypoint reference in official (RTE DIST FROM, HOLD DIST/TIME)
government publications will be used when available.
Section revised to include material relating to holding
Used On: Enroute Airways, SID/STAR and distance and time.
Approach Route records.
Length: 4 characters max. ORIGINAL TEXT FOLLOWS
Character Type: Alpha/Numeric
Examples: DEN, RTM, LAX, 6YA, T1KX 5.27 Route Distance From (ROUTE DIST FROM)
5.22 Turn Direction Valid (TDY) Definition/Description: “Route Distance From” is the
distance in nautical miles from the waypoint identified in
New section introduced by this Supplement. Original the record’s “waypoint identifier” field to the next
Section 5.22 deleted. waypoint of the route.

ORIGINAL TEXT FOLLOWS Source/Content: The field contains distance in nautical

miles and tenths of a nautical mile, with the decimal point
5.22 First Reserved VHF NAVAID (RES’D VHF) suppressed. Values from official government sources will
be used when available.
Definition/Description: In the event that the
recommended VHF NAVAID (see paragraph 3.21) Used On: Enroute Airways, SID/STAR and
cannot be used, reference to an alternative facility may be Approach Route records.
possible. The most preferred of such alternative facilities Length: 4 characters
is identified in the “First Reserved VHF NAVAID” field. Character Type: Numeric
Examples: 1076, 0282
Source/Content: The 2-, 3- or 4-character identification
code of the FAA-defined first alternative VHF NAVAID 5.29 Altitude Descript (ALT DESC)
facility to that recommended (see paragraph 5.21) is
entered into this field when available. Code “C” added to field content table. Note qualifying
the “C” entry added below the table.
Used On: Enroute Airways, SID/STAR and
Approach Route records. 5.30 Altitude (ALTITUDE)
Length: 4 characters max.
Character Type: Alpha/numeric Notation added to example to indicate that NESTB
Examples: PHX, SEA, YUL, 6YA, T1KX example applies only to enroute airways.

5.23 Recommended VHF NAVAID (REC’D VHF) 5.32 Cycle Date (CYCLE)

New section introduced by this Supplement. Original Final sentence of “source/content” paragraph expanded to
Section 5.23 deleted. indicate that 14 cycles will be necessary in some years.

5.33 VOR/NDB Identifier (VOR IDEINT/NDB IDENT)

ORIGINAL TEXT FOLLOWS
Section expanded to include NDB facility identification.
5.23 Second Reserved VHF NAVAID (RES’D VHF)
ORIGINAL TEXT FOLLOWS
Definition/Description: In the event that the
recommended VHF NAVAID (see paragraph 3.21) 5.33 VOR IDENTIFIER (VOR IDENT)
cannot be used, reference to an alternative facility may be
possible. The second most preferred of such alternative Definition/Description: The “VOR Identifier” field
facilities is identified in the “Second Reserved VHF identifies the VOR, VORTAC or VOR/DME facility
NAVAID” field. defined in the record.
SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 16

Source/Content: The field contains the official 5.37 Longitude (LONGITUDE)

government 2-, 3- or 4-character facility defined in the
record. “Used On” paragraph amended to remove “VHF”
qualifier from “NAVAID” thus indicating that longitude
Used On: VHF NAVAID records may appear in all navaid type records. NDB entry added
Length: 4 characters max. to table. Note 1 amended to change column 26 to 28 (two
Character Type: Alpha/Numeric places). Note 2 amended to add “I” to the group codes
Examples: DEN, 6YA, PPI, TIKX listed and to change column 27 reference to column 29
(two places).
5.34 VOR/NDB Frequency (VOR/NDB FREQ)
ORIGINAL TEXT FOLLOWS
Section expanded to include material related to NDB
frequencies. Definition/Description: The Longitude field contains the
longitude of the geographic position of the navigational
ORIGINAL TEXT FOLLOWS feature identified in the record.

5.34 VOR Frequency (VOR FREQ) Source/Content: Geographic positions whose longitudes
must be included in the data base are defined during route
Definition/Description: The “VOR Frequency” field design, many of them in official government
specifies the VHF frequency of the NAVAID identified publications. The field is constructed as follows. The first
in the “VOR Identifier” field of the record. character position will contain the alpha character “E” or
“W,” indicating whether the longitude is east or west of
Source/Content: VOR Frequencies are derived from the prime (zero degree) meridian. For longitudes falling
official government sources and entered into the field in on the 0 to 180 degree meridians, “E” is entered. The
increments of 50 kHz. The decimal point following the following nine numeric characters define the longitude in
unit MHz entry is suppressed. degrees, minutes, seconds, tenths of seconds and
hundredths of seconds. Degree, minute and second
Used On: VHF NAVAID records symbols and the decimal point are suppressed.
Length: 5 characters
Character Type: Numeric Note: Some RNAV system users may elect to round
Examples: 11630, 10820, 1795 off longitude values to resolutions of less than
one hundredth of a second prior to the entry of
5.35 NAVAID Class (CLASS) these data into the airborne computer.

“Source/Content” table modified to include coding for The navigation reference points to be defined by latitude
L/MF navaids. and longitude coordinates are listed in Table (vi).

Used On: VHF NAVAID, Waypoint, ILS,

ORIGINAL TEXT FOLLOWS Airport, Gate and Runway records.
Length: 10 characters
(Table only) Character Type: Alpha/Numeric
Examples: W104450794
Record Column
Facility Record File LAT/LONG Field Location Defined
26 27 28 29 30
VOR V VHF NAVAID VOR (See Note 1) VOR Antenna
TACAN Frequency Paired T VHF NAVAID DME (See Note 2) DME Antenna
with VOR Waypoint Waypoint Waypoint
ILS Localizer Localizer Antenna
TACAN Channels 1 –16 M ILS Glide Slope Glide Slope
and 60-69 Antenna
DME D Airport Airport Airport Reference
ILS/DME I Point
Terminal T See Gate Gate Gate
Low Altitude L Note Runway Runway Runway Threshold
High Altitude H
Scheduled Weather B Note 1: The VOR latitude and longitude fields are filled
Broadcast when the “NAVAID Class” field contains the
No Voice on NAVAID W letter “V” in column 26 of the record. If column
Frequency 26 is blank, these fields are blank also.
Automatic Transcribed A
Weather Broadcast Note 2: The DME latitude and longitude fields are filled
when the “NAVAIDI Class” field contains the
letters “D,” “M” or “T” in column 27 of the
5.36 Latitude (LATITUDE) record. If column 27 is blank, these fields are
blank also.
“Used On” paragraph amended to remove “VHF”
qualifier from “NAVAID,” thus indicating that latitude Table (vi)
may appear in all navaid type records. Latitude/Longitude Location Definitions
 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 17

5.38 DME Identifier (DME IDENT) 5.44 Localizer Identifier (LOC IDENT)

“Source/Content” paragraph amended to add “I” to the Runway records added to “Used On” list.
list of referenced codes and to change the column number
from 27 to 29 (two places).
5.51 Localizer Width (LOC WIDTH)
ORIGINAL TEXT FOLLOWS
Erroneous examples corrected.
(“Source/Content” paragraph only.)
Source/Content: This field is blank when column 27 of 5.53 Transition Altitude (TRANS ALTITUDE)
the NAVAID class field (see paragraph 3.35) is blank or
the VOR and DME identification codes are identical. Approach Route records added to the list of records in
When the NAVAID class field contains the entry “D,” which this field is used.
“M” or “T” in column 27, this field contains the
government-source 2-, 3- or 4-character identification
code of the DME component. 5.60 Notes (Primary Records) (NOTES)

5.39 Magnetic Variation (MAG VAR) Airport records deleted from the list of “Used On”
records. 24-character length restriction on holding pattern
“Source/Content” paragraph amended to delete reference records removed. Example revised.
to “E” entry for zero degree variations. NDB Navaids
added to list of “Used On” records.
ORIGINAL TEXT FOLLOWS
ORIGINAL TEXT FOLLOWS
Definition/Description: The “Notes” field provides space
(“Source/Content” paragraph only.) in the record for information supplementary to that
contained in the encoded part of the record.
Source/Content: Magnetic variations are obtained from
basic geographical data sources. The field contains the Source/Content: Appropriate contents for the field will
alpha character “E” or “W” in its first column to indicate be determined when the record is assembled.
whether the variation is east or west of the True North.
“E” is entered for zero degree variations. The succeeding Used On: Airport, Gate and Holding Pattern
columns contain the value of the variation in degrees and records.
tenths of a degree, with the decimal point suppressed. Length: 25 characters max. (24 characters max.
on Holding Pattern records.)
5.41 Region Code (REGN CODE) Character Type: Alpha/Numeric
Examples: LOS ANGELES INTL
“Source/Content” paragraph amended to delete words
“four-character ICAO” as qualifiers for the airport
identification code used in this field for terminal area 5.61 Notes (Continuation Records) (NOTES)
waypoints.
“Used On” list amended to show all records except
ORIGINAL TEXT FOLLOWS Company Route records. Constant 70-character field
length specified.
(“Source/Content” paragraph only.)

Source/Content: The field contains the alpha characters ORIGINAL TEXT FOLLOWS
ENRT for enroute waypoints. For terminal area
waypoints, the four-character ICAO Airport identification Definition/Description: The “Notes” field (continuation
code appears in the field. record) is provided to accommodate any information that
cannot be entered in the primary record.
5.42 Waypoint TYPE (TYPE)
Source/Content: Appropriate contents for the field will be
“Source/Content” table modified. determined at the time the primary record is assembled.

ORIGINAL TEXT FOLLOWS Used On:: Enroute Airways, SID/STAR,

(Table only) Approach Route, NAVAID and ILS
continuation records.
Code Waypoint Type Code Waypoint Type Length: 79 characters max. for ILS continuation
A Airport reference Point O Outer marker records, 43 characters max. for Enroute
F Off-airway Floating Waypoint Airways, SID/STAR and Approach
I Unnamed Intersection R Named intersection Route continuation records and 20
L Runway Threshold W RNAV Waypoint characters max. for all other
M Middle Marker continuation records.
N NDB Character Type: Alpha/Numeric
Example: EASTBOUND PREFERRED
Note: Field format to be determined. 0900Z/2300Z
SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 18

5.66 Station Declination (STN DEC) 5.76 Company Route Ident

Second sentence of “Source/Content” paragraph modified New section added by this Supplement.
to address true north orientations in areas in which local
variation is not zero. Third sentence deleted. ILS records 5.77 Via Identifier (VIA IDENT)
deleted from “Used On” list.
New section added by this Supplement.
ORIGINAL TEXT FOLLOWS
5.78 Company Route Description
(“Source/Content” paragraph only.)
New section added by this Supplement.
Source/Content: Station declinations are derived from
official government sources. The field contains the alpha 5.79 Stopway
character “E” or “W” in its first column to indicate
whether the declination is east or west of true north. “E” New section added by this Supplement.
is entered for zero degree declinations. The succeeding
columns contain the value of the declination in degrees 5.80 ILS Category (CAT)
and tenths of a degree with the decimal point suppressed.
New section added by this Supplement.
5.67 Threshold Crossing Height (TCH)
5.81 ATC Indicator (ATC)
Section renamed and revised completely.
New section added by this Supplement.
ORIGINAL TEXT FOLLOWS
6.3 Bit Density
5.67 Glide Slope Height at Landing Threshold (TCH)
Specified encoded data bit density changed form 800 bits
Definition/Description: The “Glide Slope Height at per inch to 1600 bits per inch.
Landing Threshold” field specifies the height of the ILS
reference point above landing threshold for the ILS 6.7.3 Header 2 Label (HDR 2)
facility described in the record.
Decimal number defining maximum number of
Source/Content: Glide slope height at landing threshold characters in a block changed from 01944 to 01980.
data derived from official government sources is entered Decimal number defining the maximum number of
into this field in feet with a resolution of one foot. characters in a fixed-length record changed from 0108 to
0132.
Used On: ILS records
Length: 2 characters 7.0 RNAV System ADEU Card Standards
Character Type: Numeric
Example: 50 Chapter deleted. Original text, marked “Obsolete—Do
Not Use,” may be found on page 19 of this Supplement.
5.69 Threshold Displacement Distance (DISPLCD THR)
Attachment 1 – Flow Diagram
New section added by this Supplement.
Legends contained in flow diagram boxes changed to
5.70 Vertical Angle (VERT ANGEL) reflect modern terminology. Original note 3 indicating
that standards for company route data formatting do not
New section added by this Supplement. exist deleted and replaced with note addressing fact that
tapes may not be the only storage media used by airborne
5.71 Name Field navigation systems.

New section added by this Supplement. Attachment 2 – Waypoint Identifiers

5.72 Speed Limit (SPEED LIMIT) B-3 Phonetic Letter Names

New section added by this Supplement. “Plus” sign changed to “minus” sign in line no. 2 and in
the examples. Section G added.
5.73 Speed Limit Altitude
Attachment 4 – Airway, Minimum Altitude
New section added by this Supplement.
Original material of this attachment (“Runway
5.74 Glide Slope Elevation (G.S. ELEV) Description”) moved from Attachment 4 to Figure 5-6.
No change to content. New Attachment 4, “Airway
New section added by this Supplement. Minimum Altitude” added by this Supplement.

5.75 From/To Airport Fix Attachment 5 – Path and Terminator

New section added by this Supplement. New attachment introduced by this Supplement.
 SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 19

7.0 RNAV SYSTEM ADEU CARD STANDARDS

SUPPLEMENT 1 TO ARINC SPECIFICATION 424 – Page 20
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 2

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: February 5, 1982

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: December 9, 1981

SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 3.2.12 Airport Section (P) – ILS NAV DATA
Subsection (PI)
This Supplement corrects typographical and editorial
errors in Specification 424-1 and introduces a number of Sentence added to existing text. Commentary added.
clarifying amendments.
4.4.1 Primary Records
B. ORGANIZATION OF THIS SUPPLEMENT
Columns 30 and 31 (previously blank for spacing
The first part of this document, printed on goldenrod reasons) assigned to “Waypoint Usage” coding described
paper, contains descriptions of the changes introduced in Section 5.82. Figure 4-1 amended to reflect this
into the Specification by this Supplement, and where change.
appropriate, extracts from the original text for
comparison purposes. The second part consists of 5.7 Route Type (RT TYPE)
replacement white pages for the Specification modified to
reflect these changes. The modified and added material Line added to Enroute Airways Record table defining
on each replacement page is identified with c-2 symbols field content “B” and “Both (High/Low)” airway type.
in the margins.
STAR Record table amended to add word “Transition” to
Existing copies of Specification 424-1 may be updated by “Profile Descent Enroute” entry.
inserting the replacement white pages where necessary
and destroying the pages they displace. The goldenrod 5.10 Approach Route Identifier (APPROACH IDENT)
pages should be inserted inside the rear cover of the
Specification, following Supplement 1. Field length reduced from 5 characters max. to 4
characters max. Example “B8R” changed to “B08R.”
C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT 5.11 Transition Identifier (TRANS IDENT)

This Section presents a complete tabulation of the Table (ii) revised completely.
changes and additions to the Specification introduced by
this Supplement. Each change or addition is identified Example “TRAIL” changed to “RW08R.”
using the section number and title currently employed or
the section number and title that will be employed when ORIGINAL TEXT FOLLOWS
the Supplement is eventually incorporated. In each case
there is included a brief description of the addition or Record “Route Type” “Transition Identifier”
change. Field Content Field Content
SID/STAR 1 or 4 SID runway transition
1.2 Data Format Standardization Philosophy identifier
2 or 5 Blank/RWY/All/Other
Commentary added. 3 or 6 SID Enroute transition
identifier
2.2 Special Navigation Terms 1, 4, or 7 STAR enroute
transition identifier
The words “terminal structure” are substituted for the 2, 5, or 8 Blank/RWY/All/Other
words “approach structure” in definition for Transition 3, 6, or 9 STAR runway
Essential Waypoints. transition identifier
Approach A Waypoint identifier of
3.2.2 VHF NAVAID Section (D) Routes first waypoint of
transition
New sentence added to existing text. All other Blank
possible entries
3.2.5 Airport Section (P) – Airport Reference Point
Subsection (PA) Table (ii)
Transition Identifier Field Content
Runway length and instrument approach restriction
deleted.
ORIGINAL TEXT FOLLOWS

3.2.5 Airport Section (P) – Airport Reference Point

Subsection (PA)

The Airport Reference Point Subsection of the master

airline user file should contain reference points for all
airports having at least one hard-surfaced runway of 4000
feet length or greater, for which an approved instrument
approach procedure is published.
 SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 3

5.17 Waypoint Description Code (DESC CODE) ORIGINAL TEXT FOLLOWS

Table (iii) modified. 5.54 Airport Class (CLASS)

ORIGINAL TEXT FOLLOWS Definition/Description: The “Airport Class” field permits

airports to be classified on the basis of available runway
Record Column Content length.
Waypoint Description
40 41 42 43
Airport W/P A Source/Content: The first character of the field is selected
Essential W/P* E from the following table. The second character position is
Off-Airway W/P* F blank.
Runway W/P G
Non-Essential W/P* R Available Runway Field Entry
Transition Essential W/P* T 6000 feet and over A
VOR, VORDME, VORTAC V 5000 to 5999 feet B
End of Continuous Airway E 4000 to 4999 feet C
Overfly** Y
ATC Compulsory W/P* C Used On: Airport records
Gateway Fix G Length: 2 characters max.
First Leg of Missed Approach M Character Type: Alpha
Holding Fix H
5.64 Leg Length (LEG LENGTH)
* See Chapter 2 for definitions.
Definition/Description revised to define leg length
** Fix must be overflown before turning. (distance) as the distance between the point at which the
airport rolls out on the inbound leg and the fix at which
Note: Column 40 may be blank on some the holding pattern is defined. Figure 5-4 amended to
SID/STAR/APPROACH records. reflect this change.

Table (iii) ORIGINAL TEXT FOLLOWS

Waypoint Description Codes
Definition/Description: The “Leg Length” field specifies
5.22 Turn Direction Valid (TDV) the diagonal distance from the holding waypoint to the
end of the outbound leg of a holding pattern.
Definition/Description amended.
5.66 Station Declination (STN DEC)

ORIGINAL TEXT FOLLOWS “G” entry added to Source/Content description.

Definition/Description: This field is used to indicate that 5.70 Vertical Angle (VERT ANGLE)
a turn is required prior to executing the Path Term
defined in a terminal procedure. Definition/Description and Source/Content paragraphs
modified. Figure 5-5 revised to increase range of vertical
5.23 Recommended VHF NAVAID (REC’D VHF) angle and to correct formula for vertical angle
computation.
Note added after “Definition/Description” paragraph.
ORIGINAL TEXT FOLLOWS
5.29 Altitude Descript (ALT DESC)
5.70 Vertical Angle (VERT ANGLE)
Field contents “G” and “I” and their associated waypoint
crossing definitions added to Source/Content table. Definition/Description: “Vertical Angle” will be
Second sentence added to first note. specified on the runway waypoint of approaches. The
angle should cause the aircraft to fly level, then descend.
5.32 Cycle Data (CYCLE)
Source/Content: Values from official government
Two sentences added to “Definition/Description” sources will be used when available. The value may be
paragraph. computed from the FAF to a point 50 feet above the
runway threshold. The range shall be 2.40 to 3.77 degrees
5.35 NAVAID Class (CLASS) (3.00 degrees nominal), with decimal point suppressed.
(See Figure 5-5.)
Sentence added to note under table (v).
Used On: Approach Routes records, STAR
5.54 Airport Class (CLASS) records, Runway records
Length: 4 characters
Definition/Description paragraph and Source/Content Character Type: Numeric
table revised. Examples: -250, -300, 360
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 4

5.70 Vertical Angle (VERT ANGLE) (cont’d)

Note: Vertical angle will be included in runway

records only when runway has published
straight-in landing minimums.

5.82 Waypoint Usage

New section added by this Supplement.

Attachment 2 – Waypoint Identifiers

Back course marker prefix in Section F1 changed from

“SM” to “BM.”

Attachment 3 – Navigation Chart/File Date Relationship

New version of computer print-out of the master user

tape file data equivalent to the chart examples in this
attachment substituted for that existing.

ARINC STAFF NOTE: Since this material is illustrative

only, we are not reproducing the original version for
reference in this Supplement.

Attachment 5 – Path and Terminator

New version of this attachment introduced by this

Supplement. The pages of the original version of
Attachment 5 follow, marked “Obsolete – Do Not Use.”
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 5
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 6
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 7
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 8
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 9
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 10
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 11
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 12
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 13
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 14
SUPPLEMENT 2 TO ARINC SPECIFICATION 424 – Page 15
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 3

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: January 17, 1983

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 4, 1982
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT ORIGINAL TEXT FOLLOWS

This Supplement restructures the format of the company Note 2: The second altitude field (columns 90 through
route record, adds guidance on coding VOR approaches 94) will be filled only when the Altitude
in Attachment 5 and corrects previously undiscovered Descript field contains the entry “B.” Section
editorial and typographical errors. Additionally, it 5.20 of this document refers.
introduces a small number of clarifying amendments into
the Specification. 4.10.1 Primary Records

B. ORGANIZATION OF THIS SUPPLEMENT “Vertical Angle (4)” field in columns 78 through 81

changed to “Blank (Spacing) (4)” and reference to
The first part of this document, printed on goldenrod Section 5.70 deleted.
paper, contains descriptions of the changes introduced
into the Specification by this Supplement, and where 4.12 Company Route Records (R)
appropriate, extracts from the original text for
comparison purposes. The second part consists of This section revised completely.
replacement white pages for the Specification modified to
reflect these changes. The modified and added material ORIGINAL TEXT FOLLOWS
on each replacement page is identified with c-3 symbols
in the margins. 4.12 Company Route Records (R)

Existing copies of Specification 424-2 may be updated by This file contains company tailored route information.
inserting the replacement white pages where necessary
and destroying the pages they displace. The goldenrod 4.12.1 Primary Records
pages should be inserted inside the rear cover of the
Specification, following Supplement 2. Column Field Name (Length) Reference
1 Record Type (1) 5.2
C. CHANGES TO ARINC SPECIFICATION 424 2 thru 4 Customer/Area Code (3) 5.3
INTRODUCED BY THIS SUPPLEMENT 5 Section Code (1) 5.4
6 Reserved (Spacing) (1)
This Section presents a complete tabulation of the 7 thru 11 From Airport/Fix (5) 5.75
changes and additions to the Specification introduced by 12 thru 13 ICAO Code (2) 5.14
this Supplement. Each change or addition is identified 14 File Code (1) 5.15
using the section number and title currently employed or 15 thru 19 To Airport/Fix (5) 5.75
the section number and title that will be employed when 20 thru 21 ICAO Code (2) 5.14
the Supplement is eventually incorporated. In each case 22 File Code (1) 5.15
there is included a brief description of the addition or 23 thru 27 Company Route Identifier (5) 5.76
change. 28 thru 31 Reserved (4) Note 1
32 thru 36 Via Identifier (5) 5.77
37 thru 39 Sequence No. (3) 5.12
2.2 Special Navigation Terms 40 thru 123 Company Route Description 5.78
(84)
The term “Off-Airway Floating Waypoint” changed to 124 thru 128 File Record No. (5) 5.31
“Off-Route Floating Waypoint” because such waypoints 129 thru 132 Cycle Date (4) 5.32
may exist in terminal areas as well as in the enroute
environment. Note 1: Although the Company Route Identifier field is
five characters in length, some users envisage
4.2.1 Primary Records (VHF NAVAIDS) the need for nine characters in certain cases.
These reserved columns will permit this usage.
New field “DME Bias (2)” added in columns 86 and 87.
“Reserved (Expansion) (8)” field in columns 86 through ARINC STAFF NOTE: The foregoing changes in
98 changed to “Reserved (Expansion) (6)” columns 88 Chapter 4 necessitated revisions in Figure 4-1 in
through 93. Reference to Section 5.90 added for “DME Specification 424-2.
Bias (2)” field.
5.3 Customer/Area Code
4.6.1 Primary Records Enroute Airways (ER)
New sentence added to Source/Content paragraph to
“Blank (Spacing) (4)” field in columns 22 through 25 describe use of Area Code on Company Route records.
changed to “Blank (Spacing) (6)” in columns 20 through
25. “Route Type (1)” moved from column 20 to column 5.11 Transition Identifier (TRANS IDENT)
45. “Level (B) (L) (H) (I)” moved from column 21 to
column 46. Each occurrence of “type 1” in Note 1 replaced with
“type 1 or 4” and each occurrence of “type 2” replaced
4.9.1 Primary Records with “type 2 or 5.” Note 3 added.
“Inbound Magnetic Course (4)” field in columns 79 5.17 Waypoint Description Code (DESC CODE)
through 82 changed to “Blank (Spacing) (4).” Reference
to Note 2 for “Altitude field in columns 90 through 94 “Uncharted Airway Intersection +,.” with corresponding
deleted. Note 2 deleted. “U” in column 41, and “Missed Approach Point ++,”
 SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 3

with corresponding “M” in column 43, added to table 5.66 Station Declination (STN DEC)
(iii). “+” and “++” notes added below table (iii).
New final sentence added to “Source/Content” paragraph.
5.24 Theta (THETA) “T000” and “G000” added to examples. Commentary
added.
New final sentence added to “Definition/Description
paragraph. 5.70 Vertical Angle (VERT ANGLE)

5.26 Outbound Magnetic Course (OB MAG CRS) “Definition/Description” and “Source/Content”
paragraphs revised completely. “Runway records”
New final sentence added to “Definition/Description” deleted from “Used on” list and “360” from examples.
paragraph. Note deleted.

5.27 Route Distance From, Holding Distance/Time ORIGINAL TEXT FOLLOWS

New material added to “Definition/Description” 5.70 Vertical Angle (VERT ANGLE)

paragraph to describe use of “Route Distance From” in
path terminator codes. Definition/Description: “Vertical Angle” will be
specified on the runway waypoint of approaches. The
5.28 Inbound Magnetic Course (IB MAG CRS) angle should cause the aircraft to fly level, then descend.
A 0° vertical angle should cause the aircraft to descend
New final sentence added to Definition/Description” and then fly level. On runway records, the vertical angle
paragraph. is used to define the glideslope angle for the ILS defined
in the LOC IDENT field.
5.35 NAVAID Class (CLASS)
Source/Content: Values from official government sources
“Biased DME” added to VHF Navaid section of table (v) will be used when available. On runway records thru
with corresponding “D” entry in column 31. “Longitude” range is –2.00° through –4.00° inclusive. On approach
changed to “longitudes” in second line of note. records the range is 0.00° and –2.00° through –4.00°
except for the runway waypoint where the range is –2.00°
5.42 Waypoint Type (TYPE) through -4.00°. For semi-precision approaches the
vertical angle may be computed from the FAF altitude
“Unnamed Intersection” entry in table changed to constraint to 50 feet above the runway threshold using a
“Unnamed, Charted Intersection,” “Speed Limit Point” minimum value of –3.00°.
and entry “S” in column 27 deleted, “Off-Airway
Intersection” entry changed to “Off-Route Intersection” Used On: Approach Routes records, STAR
and “Uncharted Airway Intersection,” with “U” entry in records, Runway records
column 27, added. Length: 4 characters
Character Type: Numeric
5.53 Transition Altitude (TRANS ALTITUDE) Examples: -250, -300, 360
“Definition/Description” paragraph revised completely. Note: Vertical angle will be included in runway
“18,000” deleted from examples. records only when runway has published
straight-in landing minimums.
ORIGINAL TEXT FOLLOWS
ARINC STAFF NOTE: Vertical Angle limits also
5.53 Transition Altitude (TRANS ALTITUDE) changed from “2.00° thru 4.00°” to “–3.00° to –3.77°” on
Figure 5-5.
Definition/Description: The “Transition Altitude” field
defines the altitude at which the altimeter barometric 5.76 Company Route Ident
setting is changed from 1012.25 mb (29.92 ins of
mercury) to the local value for the airport identified in the Length changed from 5 characters to 10 characters. Note
record. explaining provisions for extension from 5 characters to 9
characters deleted.
Source/Content: Transition altitudes are derived from
official government sources. 5.77 Via Identifier (VIA IDENT)

Used On: SID/STAR, Approach Route records Section revised completely.

Length: 5 characters
Character Type: Numeric ORIGINAL TEXT FOLLOWS
Examples: 18000, 05000, 23000
5.77 Via Identifier (VIA IDENT)
5.63 Turn (TURN)
Definition/Description: The “Via Identifier” field, is used
“Source/Content” paragraph added. to further define the company route.
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 4

5.77 Via Identifier (VIA IDENT) (cont’d) CPR 29 CPR 29B

Source/Content: This field is determined by the F. Terminal Waypoints
customer.
1. Airport-Related Waypoints
Used On: Company Route records
Length: 5 characters Prefix “CF Final Approach Course Fix” added
Character Type: Alpha/Numeric to list.
5.78 SID/STAR/App/Awy 3. Bearing/Distance Waypoints
Section renamed and revised completely. Title changed (was “DME Arc Waypoints”) and
subsection “d” added.
ORIGINAL TEXT FOLLOWS
Attachment 3 – Navigation Chart/File Data Relationship
5.78 Company Route Description
Pages 50 through 59 re-ordered to present file data in
Definition/Description: The “Company Route record order.
Description” field is a flight plan type route description
of airways and fixes from point of origin to destination. Attachment 5 – Path and Terminator
SIDs, STARs, and Runway information may also be
included. General Rule B: “IF (route type 2 or 5 only)” added
to “Ending Leg” list for SID/STAR
Source/Content: This field is determined by the customer, Runway Transition procedure.
and each route may contain more than one record. (See
Figure 5-6). Note following VI Ending Leg
descriptor for Approach Transition
Used On: Company Route Records procedure expanded from “(LOC
Length: 84 characters only).”
Character Type: Alpha/Numeric
Table I: “+” added at CF row/DF column
5.83 To Fix intersection on diagram. “+” note
added below diagram and “+” note
New section added by this Supplement. revised. (Original Words:
Sequence permitted only if altitude
5.84 Runway Transition of IF leg is different than leg
termination altitude.)
New section added by this Supplement.
General Rule G: Second and third sentences added.
5.85 Enroute Transition
General Rule I: Second paragraph added.
New section added by this Supplement.
General Rule N: Revised completely. (Original
5.86 Cruise Altitude Words: The turn and turn direction
valid fields will be used to force a
New section added by this Supplement. particular turn direction whenever
the track/heading change exceeds
5.87 Terminal/Alternate Airport 135°. These two fields are used
together to indicate that a turn in
New section added by this Supplement. the specified direction must be
executed prior to intercepting the
5.88 Alternate Distance path defined in the record.
New section added by this Supplement. Table 3: Path Length designator “P” added
to legend. “P” substituted for “D”
5.89 Cost Index in DIST/TIME column of table at
CF, CI, FC and PI row
New section added by this Supplement. intersections.
5.90 DME Bias General Rule AA: New material added by this
Supplement.
New section added by this Supplement.
General Rule BB: New material added by this
Figure 5-6 - Company Route Record Example Supplement.
Figure revised completely. See page 5 of this Supplement STAR Coding Rule E: Route types “2 or 5” added.
for the original (now obsolete) figure.
Approaches and
Attachment 2 - Waypoint Identifiers Approach Transitions: This section extensively revised.
See pages 5-7 of this Supplement
E. Duplicate Identifiers for the original (now obsolete)
material.
Words “or letter” added to end of first sentence.
Example “SHAWNEE (FLA)” changed to
“SHAWNEE (CAL).” Following examples added:
CPR 29 CPR 29A
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 5
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 6
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 7
SUPPLEMENT 3 TO ARINC SPECIFICATION 424 – Page 8
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 4

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: November 10, 1983

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 12, 1983

SUPPLEMENT 4 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 4.2.3 Simulation Continuation Records

This Supplement extends the scope of Specification 424 New section added by this Supplement.
to cover the navigation data base needs of airline flight
simulators and introduces a number of corrections for 4.3.1 Primary Records
typographical and other minor errors.
Columns 75 through 79 – field name changed from
B. ORGANIZATION OF THIS SUPPLEMENT “Station Declination” to “Magnetic Variation” and
reference changed from 5.66 to 5.39.
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced 4.3.2 Continuation Records
into the Specification by this Supplement, and where
appropriate, extracts from the original text for Identical change to that described above for Section
comparison purposes. The second part consists of 4.2.2.
replacement white pages for the Specification modified to
reflect these changes. The modified and added material 4.3.3 Simulation Continuation Records
on each replacement page is identified with c-4 symbols
in the margins. New section added by this Supplement.

Existing copies of Specification 424-3 may be updated by 4.5.2 Continuation Records

inserting the replacement white pages where necessary
and destroying the pages they displace. The goldenrod Column 40 – reassigned from “Notes” to “Reserved
pages should be inserted inside the rear cover of the (Spacing).” Subsequent “Notes” field reduced in length
Specification, following Supplement 3. by one character. Note added below table describing
reason for Column 40 reservation.
C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT 4.6.2 Continuation Records

This Section presents a complete tabulation of the Identical change to that described above for Section
changes and additions to the Specification introduced by 4.5.2.
this Supplement. Each change or addition is identified
using the section number and title currently employed or 4.7.1 Primary Records
the section number and title that will be employed when
the Supplement is eventually incorporated. In each case Columns 14 through 16 – reassigned from “Blank
there is included a brief description of the addition or (Spacing)” to “ATA/IATA Designator” and 5.107
change. reference added. Columns 17 through 18 – reassigned
from “Blank (Spacing)” to “Reserved (Expansion).”
1.1.1 Coverage of Flight Simulator Needs Column 30 – reassigned from “Blank (Spacing)” to “IFR
Capability” and 5.108 reference added.
New section added by this Supplement.
4.7.2 Continuation Records
3.2.14 Airport Section (P) – ILS Markers Subsection
(PM) Identical change to that described above for Section
4.2.2.
New section added by this Supplement.
4.8.2 Continuation Records
3.2.15 Airport Section (P) – Airport Communication
Subsection (PV) Identical change to that described above for Section
4.2.2.
New section added by this Supplement.
4.9.2 Continuation Records
3.2.16 Enroute Section (E) – Airways Marker
Subsection (EM) Identical change to that described above for Section
4.5.2.
New section added by this Supplement.
4.10.1 Primary Records

4.2.1 Primary Records Columns 52 through 59 – reassigned from “Reserved

(Electronic Chart System Use)” to “Blank (Spacing).”
Columns 86 through 87 – field name changed from Columns 61 through 66 – reassigned from “Reserved
“DME Bias” to “ILS/DME Bias.” (Electronic Chart System Use)” to “blank (Spacing).”
Columns 78 through 80 – reassigned from “Blank
(Spacing)” to “Runway Width” and 5.109 reference
4.2.2 Continuation Records added.

Column 23 – reassigned from “Notes” to “Reserved 4.10.2 Continuation Records

(Spacing).” Subsequent “Notes” field reduced in length
by one character. Note added below table describing Identical change to that described above for Section
reason of column 23 reservation. 4.2.2.
 SUPPLEMENT 4 TO ARINC SPECIFICATION 424 – Page 3

4.10.3 Simulation Continuation Records Source/Content: The content of this field should be
derived from ICAO Document No. 7910, “Location
New section added by this Supplement. Indicators.”

4.11.2 Continuation Records Used On: SID/STAR, Approach Route, ILS,

Airport, Gate, Runway and Terminal
Identical change to that described above for Section Waypoint (PC) records
4.2.2. Length: 4 characters
Character Type: Alpha/numeric
4.11.3 Simulation Continuation Records Examples: KJFK, KMIA, 9V9, CYUL, EDDF

New section added by this Supplement. 5.26 Outbound Magnetic Course (OB MAG CRS)

4.13 ILS Marker (PM) Character type changed from “Numeric” to

“Alpha/Numeric.” Example “194T” added.
New section added by this Supplement.
5.28 Inbound Magnetic Course (IB MAG CRS)
4.13.1 Primary Records
SID/STAR and Approach Route records deleted from
New section added by this Supplement. “Used On” list. Character type changed from “Numeric”
to “Alpha/Numeric.” Example “194T” added.
4.14 Airport Communication Records (PV)
5.32 Cycle Date (CYCLE)
New section added by this Supplement.
“Definition/Description” amended to exclude changes in
4.14.1 Primary Records continuation record number and file record numbers from
requiring a cycle data change.
New section added by this Supplement.
ORIGINAL TEXT FOLLOWS
4.14.2 First Simulation Continuation Record
Definition/Description: The “Cycle Date” field identifies
New section added by this Supplement. the calendar period in which the record was added to the
file or last revised. A change in any ARINC 424 field
4.14.3 Additional Continuation Records requires a cycle date change. The cycle date will not
change if there is no change in the data.
New section added by this Supplement.
5.34 VOR/NDB Identifier (VOR IDEINT/NDB IDENT)
4.15.1 Primary Records
ILS Marker records added to the “Used On” list.
New section added by this Supplement.
5.35 NAVAID Class (CLASS)
ARINC STAFF NOTE: The foregoing changes in
Chapter 4 necessitated revisions to Figure 4-1 in Table (v) revised to add class of locators at markers and
Specification 424-3. an indicator in column 32 for non-collocated facilities.
“Biased DME” facility type changed to “Biased
5.5 Subsection Code (SUB CODE) ILS/DME.”
Subsection code “M-Airways Markers” added in Section 5.36 Latitude (LATITUDE)
Code “E” part of Table (i). Subsection codes “M-ILS
Markers” and “V-Airport Communications” added in ILS Marker, Airways Marker and Airport
Section Code “P” of Table (i). Communications records added to “Used On” list.

5.6 Airport Identifier (ARPT IDENT) 5.37 Longitude (LONGITUDE)

Text amended and rearranged for improved clarity. ILS Marker, Airways Marker and Airport
Communications records added to “Used On” list.
ORIGINAL TEXT FOLLOWS
5.39 Magnetic Variation (MAG VAR)

5.6 Airport ICAO Identifier (ARPT IDENT) “Used On” list changed from Airport and NDB NAVAID
records.”
Definition/Description: The “Airport ICAO Identifier”
field contains the ICAO identification code of the airport 5.46 Runway Identifier (RUNWAY IDENT)
to which the data contained in the record relates.
ILS Marker records added to “Used On” list.
Note: ICAO airport identifier codes differ from the
perhaps more familiar ATA/IATA airport 5.71 Name Field
designators. ATA/IATA codes are not employed
in this field. Enroute Marker records added to “Used On” list.
SUPPLEMENT 4 TO ARINC SPECIFICATION 424 – Page 4

5.77 VIA 5.105 Call Sign (CALL SIGN)

Note added describing the purpose of Figure 5-6. New section added by this Supplement.

5.80 ILS Category (CAT) 5.106 Additional Service (ADDL SERVICE)

“Source/Content” paragraph expanded to describe use of New section added by this Supplement.
0 in this field.
5.107 ATA/IATA Designator (ATA/IATA)
5.90 ILS DME Bias
New section added by this Supplement.
Section title changed from “DME Bias.” No other
changes. 5.108 IFR Capability (IFR)

5.91 Continuation Record Application Type (APPL) New section added by this Supplement.

New section added by this Supplement. 5.109 Runway Width (WIDTH)

5.92 Facility Elevation (FAC ELEV) New section added by this Supplement.

New section added by this Supplement. 5.110 Marker Ident (MARKER IDENT)

5.93 Facility Characteristics (FAC CHAR) New section added by this Supplement.

New section added by this Supplement. 5.111 Marker Code (MARKER CODE)

5.94 True Bearing (TRUE BRG) New section added by this Supplement.

New section added by this Supplement. 5.112 Marker Shape (SHAPE)

5.95 Government Source (SOURCE) New section added by this Supplement.

New section added by this Supplement. 5.113 High/Low (HIGH/LOW)

5.96 Glide Slope Beam Width (GS BEAM WIDTH) New section added by this Supplement.

New section added by this Supplement.

5.97 Touchdown Zone Elevation (TDZE)

New section added by this Supplement.

5.98 TDZE Location (LOCATION)

New section added by this Supplement.

5.99 Marker Type (MKR TYPE)

New section added by this Supplement.

5.100 Minor Axis (MINOR AXIS)

New section added by this Supplement.

5.101 Communication Type

New section added by this Supplement.

5.102 Radar (RADAR)

New section added by this Supplement.

5.103 Communications Frequency (COMM FREQ)

New section added by this Supplement.

5.104 Modulation (MODLN)

New section added by this Supplement.

 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 5

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: March 18, 1985

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 10, 1984

SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 4.2.1 Primary Records VHF NAVAIDS

This Supplement extends the scope of Specification 424 Columns 6 through 13 reassigned from “Blank
to cover the navigation data base needs of automated (Spacing).” “Reserved” status removed from column 85
flight planning and introduces a number of corrections for assignments and Note 1 deleted. Columns 88 through 93
typographical and other minor errors. reassigned from “Reserved (Expansion).”

B. ORGANIZATION OF THIS SUPPLEMENT ORIGINAL TEXT FOLLOWS

The first part of this document, printed on goldenrod Note 1: “NAVAID Figure of Merit No.” has no
paper, contains descriptions of the changes introduced navigation function. Should official approval be
into the Specification by this Supplement, and where forthcoming; however, for the use of
appropriate, extracts from the original text for NAVAID’s beyond ranges specified in the class
comparison purposes. The second part consists of field, this field could indicate the limitations of
replacement white pages for the Specification modified to such use.
reflect these changes. The modified and added material
on each replacement page is identified with c-5 symbols 4.2.4 Flight Planning Continuation Records
in the margins.
This section is added.
Existing copies of Specification 424-4 may be updated by
inserting the replacement white pages where necessary 4.2.5 Flight Planning Continuation Records
and destroying the pages they displace. The goldenrod
pages should be inserted inside the rear cover of the This section is added.
Specification, following Supplement 4.
4.3.1 Primary Records
C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT Length “(l)” is added to Column 6 Subsection Code.

This Section presents a complete tabulation of the 4.3.4 Flight Planning Continuation Records
changes and additions to the Specification introduced by
this Supplement. Each change or addition is identified This section is added.
using the section number and title currently employed or
the section number and title that will be employed when 4.3.5 Flight Planning Continuation Records
the Supplement is eventually incorporated. In each case
there is included a brief description of the addition or This section is added.
change.
4.4 Waypoint Records (EA OR PC)
2.2 Special Navigation Terms
A sentence has been added to clarify why waypoints are
The definition of ATC Compulsory Reporting Point is stored in the EA section.
changed, and two new definitions are added.
4.4.1 Primary Records
ORIGINAL TEXT FOLLOWS
Column 19 reassigned from “Reserved (6th Char. W.P.)”
ATC A waypoint which normally would and columns 52 through 98 reassigned from “Reserved
Compulsory be classified as nonessential might be (Expansion).” Length “(2)” is added to columns 30 and
Reporting Point a waypoint at which ATC requires 31. Note 3 is deleted.
the pilot to make a communications
report. Waypoints falling into this ORIGINAL TEXT FOLLOWS
category are classified as ATC
Compulsory Reporting Points. Note 3: The standard length for the waypoint identifier
field is 5 characters. Some users envisage the
3.2 Master Airline User File Content need for 6 characters in certain cases. This
reserved column will permit this usage.
The paragraphs in this section are renumbered to reflect
the hierarchical structure of the master data file. 4.4.3 Flight Planning Continuation Records

4.2 VHF NAVAID Record This section is added.

The wording of the last sentence of the paragraph is 4.4.4 Flight Planning Continuation Records
changed to clarify the handling of duplicate VOR and
TACAN idents. This section is added.

4.5.1 Primary Records

ORIGINAL TEXT FOLLOWS
Columns 27 through 29 reassigned from “Blank
For non-frequency paired VOR and TACAN stations (Spacing)” and columns 30 through 35 reassigned from
having the same identifier, the TACAN is stored unless “Waypoint Identifier” (30-34) and “Reserved (6th Char.
the VOR is used for enroute airways. of Waypoint Ident) (35).” Note 1 deleted.
 SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 3

ORIGINAL TEXT FOLLOWS 4.9.4 Flight Planning Continuation Records

Note 1: The standard length of the Waypoint Identifier This section is added.
field is five characters. Some users envisage the
need for a six-character field in certain cases. 4.11 ILS (Localizer and Glide Slope) Records
This revision column will permit this usage.
This section is revised to permit blank fields in the glide
4.6 Enroute Airways Records (ER) slope information fields when the data for them is not
available.
The last sentence in this section is deleted.
4.11.1 Primary Records
ORIGINAL TEXT FOLLOWS
Length of “(1)” is added to fields 1 and 6.
4.6 Enroute Airways Records (ER)
4.12.1 Primary Records
The Enroute Airways file will contain the sequential
listing of airways by geographic areas. This file may also Columns 6 through 12 reassigned from “Reserved
contain enroute off-airway waypoints by geographic area, (Spacing)” (16) and “From Airport/Fix” (7-12). Column
without sequence numbers of airway idents. 22 reassigned from “To Airport./Fix.” Columns 91
through 94 reassigned from “Reserved (Expansion).”
4.6.1 Primary Records (ER)
4.13.1 Primary Records
Column 35 reassigned from “Reserved” and Note 1
revised. Columns 46 through 49 reassigned from “Blank The field name and length for columns 14 through 17 is
(Spacing).” Columns 84 through 85 reassigned from added (previously “Blank (Spacing)).”
“Altitude” and Columns 89 through 123 reassigned from
“Reserved (Expansion).” 4.16 Cruising Tables Records (TC)

ORIGINAL TEXT FOLLOWS This section is added.

Note 1: The standard lengths for the Route Identifier and 4.16.1 Primary Records
the Waypoint Identifier fields are each five
characters. Some users envisage the need for This section is added.
six-character fields in certain instances. These
reserved columns will permit this usage. 4.17 FIR/UIR Records (UF)

4.7.1 Primary Records This section is added.

Columns 28 through 32 reassigned from “Airport Class” 4.17.1 Primary Records
(28-29) “IFR Capability” (30) and “Blank (Spacing)”
(31-32). Columns 65 through 70 reassigned from This section is added.
“Reserved (Expansion).”
4.18 Restrictive Airspace Records (UR)
4.7.3 Flight Planning Continuation Records
This section is added.
This section is added.
4.18.1 Primary Records
4.7.4 Flight Planning Continuation Records
This section is added.
This section is added.
4.18.2 Continuation Records
4.9.1 Primary Records
This section is added.
Columns 21 through 25 reassigned from
“Transition/RWY No. or Blank.” Columns 26 and 35 4.19 Grid MORA Records (AS)
reassigned from “Blank (Reserved).” Note 1 revised.
This section is added.

ORIGINAL TEXT FOLLOWS 4.19.1 Primary Records

Note 1: The Transition Identifier and the Waypoint This section is added.
Identifier fields are five characters each. Some
users envisage the need for six-character fields 4.20 MSA (Minimum Safe Altitude Records) (PS)
in certain cases. These reserved columns will
permit this usage. This section is added.

4.9.3 Flight Planning Continuation Records 4.20.1 Primary Records

This section is added. This section is added.

SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 4

4.20.1 Primary Records (cont’d) STAR Records (PE)

ARINC STAFF NOTE: The foregoing changes in Route Type Field Content
Chapter 4 necessitated revisions to Figure 4-1 in STAR Enroute Transition 1
Specification 424-5. STAR 2
STAR Runway Transition 3
5.3 Customer/Area Code (CUST/AREA) RNAV STAR Enroute Transition 4
RNAV STAR 5
“Examples” are changed. RNAV star Runway Transition 6
Profile Descent Enroute Transition 7
5.5 Subsection Code (SUB CODE) Profile Descent 8
Profile Descent Runway 9
“Used On” has been revised to read “All records.” New
sections are added to the chart. Approach Route Records (PF)
Figure 5-1 Geographical Area Codes Route Type Field Content
Approach Transition A
This figure is revised to correct USA coverage to the East Back Course B
and change boundary between SAM and AFR. ILS I
Localizer L
5.6 Airport Identifier (ARPT IDENT) RNAV R
NDB N
“Used On” section revised to include VHF NAVAID VOR V
(ILS/DME only) and Airport Communications records. MLS M
5.7 Route Type (RT TYPE) Used On: Enroute Airways, SID/STAR and
Approach Route records
Enroute Airways Records Source/Content Table changed. Length: 1 character
Character Type: Alpha/Numeric
ORIGINAL TEXT FOLLOWS
5.12 Sequence Number (SEQ NR)
5.7 Route Type (RT TYPE)
Source/Content is revised to include “Enroute airways
Definition/Description: The “Route Type” field defines should be sequenced in order that sequence numbers are
the type of enroute airway, SID/STAR or approach route not duplicated regardless of area covered.”
of which the record is an element.
“Used On” is revised to include Cruise Table, FIR/UIR,
Source/Content: and Restrictive Airways records.
Enroute Airway Records (ER) “Length” is revised to read “F Characters (Enroute
Airways FIR/UIR and Restrictive Airspace, 3 Characters
Airway Type Field Content (SID/STAR/Approach and Company Route, 1 Character
Airline A (Cruise Table).”
Both (High/Low) B
Control C 5.13 Waypoint Identifier (WAYPOINT IDENT)
Direct D
high Level H “Used On” section is revised to remove “Company Route
Jet J records.” “Examples” section is revised to include
Low Level L RW27L. KGRR.
NDB N
RNAV R 5.15 File Code (D/E/P)
Victor V
The source/content table is revised to more accurately
SID Records (PD) define the types of records to which the codes apply.
Route Type Field Content ORIGINAL TEXT FOLLOWS
SID Runway Transition 1
SID 2 5.15 File Code (D/E/P)
SID Enroute Transition 3
RNAV SID Runway Transition 4 Definition/Description The records for a waypoint
RNAV SID 5 identifier in a route record may reside in one of the
RNAV Enroute Transition 6 number of major sections of the data base. The “File
Code” field permits the section in which a particular
waypoint record will be found to be identified.
 SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 5

Source/Content: ORIGINAL TEXT FOLLOWS

Code Waypoint Record Source Record File LAT/LONG Field Location Defined
D NAVAID Section (Waypoint is NAVAID) VHF NAVAID VOR (See Note 1) VOR Antenna
E Enroute Waypoint Section VHF NAVAID DME (See Note 2) DME Antenna
P Terminal Section (SID/STAR/APP and Waypoint Waypoint Waypoint
Company Route records) ILS Antenna Localizer Localizer
ILS Glide Slope Glide Slope Antenna
Used On: Enroute Airways, SID/STAR/APP, Airport Airport Airport Ref. Point
Holding Pattern and Company Route Gate Gate Gate
records Runway Runway Runway Threshold
Length: 1 character NDB NAVAID NDB NDB Antenna
Character Type: Alpha
5.39 Magnetic Variation (MAG VAR)
5.16 Continuation Record Number (CONT NR)
The Source/Content section’s first sentence is revised to
“Used On” is revised to add Cruise Table, Grid MORA, clarify the sources for magnetic variations.
and MSA records.
5.42 Waypoint Type (TYPE)
5.19 Level (LEVEL)
The table is expanded to clarify those codes allowed on
Source/Content for “B” is changed to “All Altitudes” Enroute Waypoints and Terminal Waypoints, and two
(was Both Level Airways (not designated as high level or new codes are added.
love level)).
5.44 Localizer Identifier (LOC IDENT)
5.23 Recommended VHF NAVAID (REC’D VHF)
“Used On” is changed to read “ILS, Runway and ILS
This paragraph is reworded to accommodate the addition marker receives.”
of the Recommended VHF NAVAID to the airport
record. 5.46 Runway Identifier (RUNWAY IDENT)

Two notes are added. Source/Content section is rewritten.

5.27 Route Distance From, Holding Distance/Time ORIGINAL TEXT FOLLOWS

(RTE DIST FROM, HOLD DIST/TIME)
Source/Content: The two letters RW precede runway
A sentence is added to the end of the Source/Content identifications derived from official government sources.
section.
5.53 Transition Altitude (TRANS ALTITUDE)
5.30 Altitude (ALTITUDE)
Definition/Description last sentence is replaced.
In the examples, the usage of UNKNN and NESTB on
enroute records is clarified. ORIGINAL TEXT FOLLOWS

5.31 File Record Number (FRN) If the transition altitude is 18,000 feet, it may be omitted.

Source/Content is revised to add that if the file reaches 5.54 Airport Class (CLASS)
99999, the next record number will start over with 00000.
The name of this section is changed to Longest Runway
5.35 NAVAID Class (CLASS) (LONGEST RWY).

Table (v) is revised. (“U” in column 30 defined as In Definition/Description section, “Airport Class” is
“Undefined NAVAID. “I,” “M” were incorrectly shown changed to “Longest Runway.” “Character Type” is
in column 29. “M” was used to code Navaid power up to changed from “Alpha” to “Numeric.” “Examples” are
50 watts.) Note 3 added. added.

5.37 Longitude (LONGITUDE) 5.64 Leg Length (LEG LENGTH_

Table (vi) is revised. “See Figure 5-4” is added at the end of the
Definition/Description section.
SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 6

5.66 Station Declination (STN DEC) 5.116 FIR/UIR Identifier (FIR/UIR IDENT)
5.117 FIR/UIR Indicator (IND)
ILS records added to the “Used On” list. 5.118 Boundary VIA (BORY VIA)
5.119 Arc Distance (ARC DIST)
5.70 Vertical Angle (VERT ANGLE) 5.120 Arc Bearing (ARC BRG)
5.121 Lower/Upper Limit
“Character Type” is changed from “Numeric” to 5.122 FIR/UIR ATC Reporting Units Speed (RUS)
“Alpha/Numeric.” “Examples” are added. 5.123 FIR/UIR ATC Reporting Units Altitude (RUA)
5.124 FIR/UIR Entry Report (ENTRY)
5.72 Speed List (SPEED LIMIT) 5.125 FIR/UIR Name
5.126 Restrictive Airspace Name
Sentence added to the Source/Content section to cover 5.127 Maximum Altitude (MAX ALT)
placing the Speed Limit in the Airport Record. 5.128 Restrictive Airspace Type (REST TYPE)
5.129 Restrictive Airspace Designation
5.75 From/To – Airport/Fix 5.130 Multiple Code (MULTI CD)
5.131 Time Code (TIME CD)
This section is revised to delete “airport reference point” 5.132 NOTAM
and “NAVAID.” 5.133 Unit Indicator (UNIT IND)
5.134 Cruise Table Identifier (CRSE TBL IDENT)
ORIGINAL TEXT FOLLOWS 5.135 Magnetic Track From/To (MAG TRACK
FM/TO)
Definition/Description: The “From Airport/Fix” is the 5.136 Cruise Level From/To
airport reference point, the Navaid or Waypoint from that 5.137 Vertical Separation
the company route originates. The “To Airport/Fix” is the 5.138 Time Indicator (TIME IND)
airport reference point, the Navaid or waypoint that the 5.139 Time Group
company route terminates. 5.140 Controlling Agency
5.141 Starting Latitude
5.79 Stopway 5.142 Starting Longitude
5.143 MORA
“The length of an” is added to the first sentence of the 5.144 MSA Center
Definition/Description section. 5.145 Radium Limit
5.146 Sector Bearing (SEC BRG)
5.81 ATC Indicator (ATC) 5.147 Sector Altitude (SEC ALT)
5.148 Enroute Alternate Airport (EAA)
The Source/Content section is revised to distinguish 5.149 Figure of Merit (MERIT)
between the two different conditions for the use of this 5.150 Frequency Protection Distance (FREQ PRO)
field. 5.151 FIR/UIR Address (ADDRESS)
5.152 Start/End Indicator (S/E IND)
ORIGINAL TEXT FOLLOWS 5.153 Start/End Date

Source/Content: This field will be used when official

government source states that the altitude can be 6.7.2 Header 1 Label (HDR 1)
modified or assigned by ATC and will contain the alpha
character “A.”
In order to identify the cycle during which a tape is
5.82 Waypoint Usage created, the Generation Number field is changed to
contain the cycle date.
“Terminal Use Only” is added to Source/Content section.

5.88 Alternate Distance (ALT DIST) ATTACHMENT 2 – WAYPOINT IDENTIFIERS

“…from the destination airport/fix to the alternate CPR29, CPR29A, CPR29, CPR29B are removed from
airport” added to the last line of the Source/Content Section E.
section.

5.89 Cost Index Examples are changed to read OM25L, MM09, IM23,
RW04, MA18L in Section F.
Definition/Description section is revised.
ORIGINAL TEXT FOLLOWS ATTACHMENT 5 – PATH AND TERMINATOR

Definition/Description: The Cost Index field is used to Section added.

define the cost of different Company Routes between the
same city pairs. A family of path types is added based on track legs that
are terminated as appropriate.
The following new Sections added by this Supplement:
A new sentence is added in Rule N. Rule W is revised.
5.114 Duplicate Identifier
5.115 Direction Restriction Rule AA is deleted and a new rule AA is incorporated.
 SUPPLEMENT 5 TO ARINC SPECIFICATION 424 – Page 7

ORIGINAL TEXT FOLLOWS

When a SID or STAR route is repeated with different

TRANSITION ID fields, it shall be defined as a runway
or enroute transition route type.

SIDE CODING RULES

SID Rule 1 is revised.

ORIGINAL TEXT FOLLOWS

I. A SID which consists of a runway transition only

shall be coded as a route type 2.

SID Rule K is added.

STAR CODING RULES

Rule E is revised.

ORIGINAL TEXT FOLLOWS

E. A STAR which consists of a runway transition only

will be coded as a route type 2, 5, or 8.

Rule F is added.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 6

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: January 31, 1986

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: November 7, 1985

SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT ORIGINAL TEXT FOLLOWS

This Supplement incorporates airway restriction records 4.4.2 Continuation Records

into ARINC 424. Changes to ARINC 424 are also
included to improve the operational utility of the Column Field Name (Length) Reference
navigation data base. New rules or clarifications to 1 thru 21 Fields as on Primary Records
existing rules are provided by this Supplement. Editorial 22 Continuation Record No. (1) 5.16
changes are also made by this Supplement. 23 thru 92 Notes (70) 5.61
93 thru 123 Reserved (Expansion) (34)
B. ORGANIZATION OF THIS SUPPLEMENT 124 thru 128 File Record No. (5) 5.31
129 thru 132 Cycle Date (4) 5.32
The first part of this document, printed on goldenrod
paper, contains descriptions of the changes introduced 4.5.1 Primary Records
into the Specification by this Supplement, and where
appropriate, extracts from the original text for Added new field.
comparison purposes. The second part consists of
replacement white pages for the Specification modified to ORIGINAL TEXT FOLLOWS
reflect these changes. The modified and added material
on each replacement page is identified with c-6 symbols 4.5.1 Primary Records
in the margins.
Column Field Name (Length) Reference
Existing copies of Specification 424-5 may be updated by 1 Record Type (1) 5.2
inserting the replacement white pages where necessary 2thru 4 Customer/Area Code (3) 5.3
and destroying the pages they displace. The goldenrod 5 Section Code (1) 5.4
pages should be inserted inside the rear cover of the 6 Subsection Code (1) 5.5
Specification, following Supplement 5. 7 thru 10 Region Code (4) 5.41
11 thru 27 Blank (Spacing) (17)
C. CHANGES TO ARINC SPECIFICATION 424 28 thru 29 Duplicate Identifier (2) 5.114
INTRODUCED BY THIS SUPPLEMENT 35 Blank (Spacing) (17)
36 thru 37 ICAO Code (2) 5.14
This Section presents a complete tabulation of the 38 File Code (1) 5.15
changes and additions to the Specification introduced by 39 Continuation Record No. (1) 5.16
this Supplement. Each change or addition is identified 40 thru 43 Inbound Holding Course (4) 5.62
using the section number and title currently employed or 44 Turn Direction (1) 5.63
the section number and title that will be employed when 45 thru 47 Leg Length (3) 5.64
the Supplement is eventually incorporated. In each case 48 thru 49 Leg Time (2) 5.65
there is included a brief description of the addition or 50 thru 54 Altitude (5) 5.30
change. 55 thru 98 Reserved (Expansion) (44)
99 thru 123 Notes (25) 5.60
124 thru 128 File Record No. (5) 5.31
3.2.2.1 VHF NAVAID Section (D) – Subsection (D) 129 thru 132 Cycle Date (4) 5.32
Reference to Section 3.2.5 added. 4.6.3 Flight Planning Continuation Records
3.2.3.1 Enroute Waypoints Section (E) – Subsection Added new section.
(EA)
4.6.4 Flight Planning Continuation Records
Reference to Section 3.2.3.2 deleted. Reference to
Section 3.2.3.4 added. Added new section.
3.2.3.5 Enroute Airways Restrictions Section (P) 4.14.1 Primary Records
Subsection (PV)
Added new field.
New section added.
ORIGINAL TEXT FOLLOWS
3.2.4.11 Airport Communications Section (P) Subsection
(PV) 4.14.1 Primary Records
New text for airports referenced in Subsection 3.2.4.1 Column Field Name (Length) Reference
added. 1 Record Type (1) 5.2
2 thru 4 Customer/Area Code (3) 5.3
4.3 NDB NAVAID Record (DB) 5 Section Code (1) 5.4
6 Blank (Spacing) (1)
Clarify text to specify “LF and MF” NDBs and delete 7 thru 10 Airport Identifier/Blank (4) 5.6
obsolete table accidentally included in Supplement 6. 11 thru 12 ICAO Code/Blank (2) 5.14
13 Blank (Spacing) (1)
4.4.2 Continuation Records 14 thru 16 Communication Type (3) 5.101
17 thru 19 Service (3) 5.106
Add new field. 20 Radar Service (1) 5.102
 SUPPLEMENT 6 ARINC SPECIFICATION 424 – Page 3

Column Field Name (Length) Reference ORIGINAL TEXT FOLLOWS

21 Blank (Spacing) (1)
22 Continuation Record No. (1) 5.16 4.16.1 Primary Records
23 thru 29 Primary Comm Freq (7) 5.103
30 Modulation (1) 5.104 Column Field Name (Length) Reference
31 thru 32 Blank (Spacing) (2) 1 Record Type (1) 5.2
33 thru 41 Facility Latitude (9) 5.36 2 thru 4 Blank (Spacing) (3)
42 thru 51 Facility Longitude (10) 5.37 5 Section Code (1) 5.4
52 thru 56 Magnetic Variation (5) 5.39 6 Subsection Code (1) 5.5
57 thru 61 Facility Elevation (5) 5.92 7 thru 8 Cruise Table Identifier (2) 5.134
62 thru 68 Comm Freq 5.103 9 Sequence Number (1) 5.12
69 Modulation (1) 5.104 10 thru 28 Blank (Spacing) (19)
70 thru 76 Comm Freq (7) 5.103 29 thru 32 Magnetic Track From (4) 5.135
77 Modulation (1) 5.104 33 thru 36 Magnetic Track To (4) 5.135
78 thru 84 Comm. Freq (7) 5.103 37 thru 39 Blank (Spacing) (3)
85 Modulation (1) 5.104 40 thru 44 Cruise Level From (5) 5.136
86 thru 92 Comm Freq (7) 5.103 45 thru 49 Vertical Separation (5) 5.137
93 Modulation (1) 5.104 50 thru 54 Cruise Level To (5) 5.136
94 thru 100 Comm Freq (7) 5.103 55 thru 59 Cruise Level From (5) 5.136
101 Modulation (1) 5.104 60 thru 64 Vertical Separation (5) 5.137
102 thru 108 Comm Freq (7) 5.103 65 thru 69 Cruise Level To (5) 5.136
109 Modulation (1) 5.104 70 thru 74 Cruise Level From (5) 5.136
110 thru 116 Comm Freq (7) 5.103 75 thru 79 Vertical Separation (5) 5.137
117 Modulation (1) 5.104 80 thru 84 Cruise Level To (5) 5.136
118 thru 123 Reserved (Expansion) (6) 85 thru 89 Cruise Level From (5) 51.36
124 thru 128 File Record No. (5) 5.31 90 thru 94 Vertical Separation (5) 5.137
129 thru 132 Cycle Date (4) 5.32 95 thru 99 Cruise Level To (5) 5.136
100 thru 123 Reserved (Expansion) (24)
124 thru 128 File Record No. (5) 5.31
4.15.1 Primary Records 129 thru 132 Cycle Date (4) 5.32

Added new field. 4.17.1 Primary Records

Added new field.

ORIGINAL TEXT FOLLOWS
ORIGINAL TEXT FOLLOWS
4.15.1 Primary Records 4.17.1 Primary Records

Column Field Name (Length) Reference Column Field Name (Length) Reference
1 Record Type (1) 5.2 1 Record Type 91) 5.2
2 thru 4 Customer/Area Code (3) 5.3 2 thru 4 Customer/Area Code (3) 5.3
5 Section Code (1) 5.4 5 Section Code (1) 5.4
6 Subsection Code (1) 5.5 6 Subsection Code (1) 5.5
7 thru 13 Blank (Spacing) (7) 7 thru 10 FIR/UIA Identifier (4) 5.116
14 thru 17 Marker Ident 5.110 11 thru 12 FIR/UIR Address 5.151
18 thru 19 Blank (Spacing) 13 FIR/UIR Indicator (1) 5.117
20 thru 21 ICAO Code (2) 5.14 14 thru 17 Sequence Number (4) 5.12
22 Continuation Record No. (1) 5.16 18 Continuation Record No. (1) 5.16
23 thru 26 Marker Code (4) 5.11 19 thru 22 Adjacent FIR Identifier (4) 5.11
27 Blank (Reserved/Spacing) (1) 23 thru 26 Adjacent UIR Identifier (4) 5.11
28 Marker Shape (1) 5.112 27 Reporting Units Speed (1) 5.122
29 Marker Power (1) 5.113 28 Reporting Units Altitude (1) 5.123
30 thru 33 Blank (Spacing) (4) 29 Entry Report (1) 5.124
34 thru 41 Marker Latitude (9) 5.36 30 Blank (Spacing) (3)
42 thru 51 Marker Longitude (10) 5.37 31 thru 32 Boundary Via (2) 5.118
52 thru 55 Minor Axis (4) 5.100 33 thru 41 FIR/UIR Latitude (9) 5.36
56 thru 74 Blank (Reserved) (19) 42 thru 51 FIR/UIR Longitude (10) 5.37
75 thru 79 Magnetic Variation (2) 5.39 52 thru 60 Arc Origin Latitude (9) 5.36
80 thru 84 Facility Elevation (5) 5.92 61 thru 70 Arc Origin Longitude (10) 5.37
85 thru 93 Blank (Reserved) (9) 71 thru 74 Arc Distance (4) 5.119
94 thru 123 Marker Name (30) 5.71 75 thru 78 Arc Bearing (4) 5.120
124 thru 128 File Record No. (5) 5.31 79 thru 83 FIR Upper Limit (5) 5.121
129 thru 132 Cycle Date (4) 5.32 84 thru 88 UIR Lower Limit (5) 5.121
89 thru 93 UIR Upper Limit (5) 5.121
4.16.1 Primary Records 94 thru 123 FIR/UIR Name (30) 5.125
124 thru 128 File Record No. (5) 5.31
Added new field. 129 thru 132 Cycle Date (4) 5.32
SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 4

4.19.1 Primary Records 4.21 Enroute Airways Restriction Records (EU)

Added new field. New section added.

ORIGINAL TEXT FOLLOWS 4.21.1 Primary Records

Column Field Name (Length) Reference New record table added.

1 Record Type (1) 5.2
2 thru 4 Blank (Spacing) (3) 4.21.2 Continuation Records
5 Section Code (1) 5.4
6 Subsection Code (1) 5.5 New record table added.
7 thru 13 Blank (Spacing) (7)
14 thru 16 Starting Latitude (3) 5.141 4.21.3 Continuation Records
17 thru 20 Starting Longitude (4) 5.142
21 thru 30 Blank (Spacing) (3) New record table added.
31 thru 33 MORA (3) 5.143
34 thru 36 MORA (3) 5.143 Table 4.1 Record Format
37 thru 39 MORA (3) 5.143
50 thru 42 MORA (3) 5.143 New records and new fields added to reflect changes in
43 thru 45 MORA (3) 5.143 Section 4.
49 thru 51 MORA (3) 5.143
52 thru 54 MORA (3) 5.143 ORIGINAL TEXT FOLLOWS
55 thru 57 MORA (3) 5.143
58 thru 60 MORA (3) 5.143 Table 4.1 Record Format (see Pgs. 5-10)
61 thru 63 MORA (3) 5.143
64 thru 66 MORA (3) 5.143 5.3 Customer/Area Code (SUB CODE)
67 thru 69 MORA (3) 5.143
70 thru 72 MORA (3) 5.143 Added new examples.
73 thru 75 MORA (3) 5.143
76 thru 78 MORA (3) 5.143 5.5 Subsection Code (SUB CODE)
79 thru 81 MORA (3) 5.143
82 thru 84 MORA (3) 5.143 Add new subsection code to section code E for airway
85 thru 87 MORA (3) 5.143 restrictions (U).
88 thru 90 MORA (3) 5.143
91 thru 93 MORA (3) 5.143 5.17 Waypoint Description Code (DESC CODE)
94 thru 96 MORA (3) 5.143
97 thru 99 MORA (3) 5.143 Expansion of note “++.”
100 thru 102 MORA (3) 5.143
103 thru 105 MORA (3) 5.143 ORIGINAL TEXT FOLLOWS
106 thru 108 MORA (3) 5.143
109 thru 111 MORA (3) 5.143 ++ Not used in combination with “G” in column 40.
112 thru 114 MORA (3) 5.143
115 thru 117 MORA (3) 5.143 Figure 5-2 7 SUBDIVISIONS FOR UNITED STATES
118 thru 120 MORA (3) 5.143
121 thru 123 Reserved (Expansion) (3) Figure replaced with a clearer reproduction with the
124 thru 128 File Record No. (5) 5.31 names of states included.
129 thru 132 Cycle Date (4) 5.32
5.23 Recommended VHF NAVAID REC’D VHF)
4.20.1 Primary Records
Expansion of reference for final approach note to indicate
Added new field. referenced NAVAID.

ORIGINAL TEXT FOLLOWS ORIGINAL TEXT FOLLOWS

4.20.1 Primary Records For Localizer based Approach Transitions ending in an

intercept of the localizer or course to Final Approach
Column Field Name (Length) Reference Course Fix and the Final Approach path, the
1 Record Type (1) 5.2 Recommended VHF NAVAID must be the referenced
2 thru 4 Customer/Area Code (3) 5.3 Localizer. For VOR Approach the final approach path
5 Section Code (1) 5.4 must be the referenced VOR.
6 Blank (Spacing) (1)
7 thru 10 Airport (ICAO) Identifier (4) 5.6 5.30 Altitude (ALTITUDE)
11 thru 12 ICAO Code (2) 5.5
14 thru 18 MSA Center (5) 5.144 Expand title and text (new paragraph) to include
19 thru 20 ICAO Code (2) 5.14 minimum altitude. Delete reference to Attachment 4.
21 File Code (1) 5.15
22 Subsection Code (1) 5.5
23 thru 24 Radius Limit (2) 5.145
25 thru 27 Sector Bearing (3) 5.146
SUPPLEMENT 6 ARINC SPECIFICATION 424 – Page 5
SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 6
SUPPLEMENT 6 ARINC SPECIFICATION 424 – Page 7
SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 8
 SUPPLEMENT 6 ARINC SPECIFICATION 424 – Page 9

5.35 NAVAID Class (CLASS) 5.118 Boundary Via (BDRY VIA)

VHF NAVAID Table is expanded to include Definition/Description: The “Boundary Via” field
ILS/TACAN installations. Note 4 is added. defines the path of the boundary from the position
identified in the record to the next position.
ORIGINAL TEXT FOLLOWS
Source/Content: The path of the boundary will be
Record Column determined from official government sources and the
Facility “Boundary Via” selected from the following table:
28 29 30 31 32
VHF Navaid
VOR V Column 1 Column 2 Description
TACAN Channels 17-50 T A Arc by edge
and 70-117 C Circle
TACAN Channels 1-16 M E End of description, return to
and 60-69 original point
DME D G Great Circle
ILS/MDE I H Rhumb Line
Biased ILS/DME D L Counter Clockwise Arc
Terminal T See R Clockwise Arc
Low Altitude L Note
High Altitude H 1 Note: Special Use Airspace designated as following
Unrestricted (see Note 3) U rivers, country boundaries or other political
boundaries will be averaged using a straight line
5.39 Magnetic Variation so that no path will be greater than two nautical
miles from the actual boundary.
Delete “Airport Magnetic Variation” from Terminal
Waypoint record. Used On: FIR/UIR, Restrictive Airspace records
Length: 2 characters
5.54 Longest Runway (LONGEST RWY) Character Type: Alpha
Table deleted. Runway field entry was changed from 5.119 Arc Distance (ARC DIST)
alpha characters to numerical length in Supplement 5.
Add “C” to the Arc Distance field content list in Source
ORIGINAL TEXT FOLLOWS Content paragraph.

Available Runway Field Entry 5.121 Lower/Upper Limit

6000 feet and over A
5000 to 5999 feet B Delete “control airspace” from Definition/Description
4000 to 4999 feet C paragraph.
3000 to 3999 feet D
Less than 3000 feet E 5.127 Maximum Altitude (MAX ALT)

Figure 5-3 RUNWAY PLAN AND PROFILE Definition/Description: The “Maximum Altitude” field is
used to indicate the maximum altitude allowed.
More comprehensive figure replaced previous figure.
Source/Content: Maximum altitudes should be derived
from official government publications describing the
5.115 Direction Restriction upper limit of the airway in feet or flight level.

New text encompasses use of direction restriction for Used On: Enroute Airway records
airway restriction records. Length: 5 characters
Character Type: Alpha/Numeric
Examples: 18000, FL100, FL460
ORIGINAL TEXT FOLLOWS
Figure 5-6 FIR/UIR AND RESTRICTIVE AIRSPACE
Definition/Description: The “Direction Restriction” field
will be used to indicate the direction an Enroute Airway Revised figure added expanding detail to include
is to be flown when such restrictions apply. shoreline.

Source/Content: One Way direction restrictions should be ORIGINAL TEXT FOLLOWS

derived from official government sources.
F= One Way in direction Route is coded.
B= One Way in opposite direction Route is coded.
Blank = No restriction on direction.
Used On: Enroute Airways records
Length: 1 character
Character Type: Alpha
SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 10

5.131 Time Code (TIME CD) 5.135 Magnetic TRACK FROM/TO ((MAG TRACK
FM/TO)
Clarification added stating that the time code field will be
blank wen the active times are only given by NOTAMs. Text modified to change “magnetic track” to “course.”
ORIGINAL TEXT FOLLOWS
5.134 Cruise Table Identifier (CRSE TBL IDENT)
Definition/Description: The “Magnetic Track From” field
Table modified for new field coding. Text modified to is used to indicate the lowest track for which a block of
include course as either true or magnetic, rather than cruising levels are prescribed. The “Magnetic Track To”
magnetic only. field is used to indicate the highest magnetic track for
which a block of cruising levels are prescribed.
ORIGINAL TEXT FOLLOWS Source/Content: The Magnetic Tracks will be derived
from official government sources in degrees and tenths of
Field Entry Description degree with the decimal point suppressed.
00 ICAO standard cruise table
0A Exception to ICAO cruise table 5.136 Cruise Level From/To
10 Modified cruise table
1A Exception to modified cruise Definition/Description revised to complement the use of
table course in place of magnetic track in Section 5.135.
 SUPPLEMENT 6 ARINC SPECIFICATION 424 – Page 11

ORIGINAL TEXT FOLLOWS 5.165 Magnetic/True Indicator (M/T IND)

Definition/Description: The “Cruise Level From” field is New field added to define airway restriction record.
used to indicate the lowest cruising level prescribed for ATTACHMENT 2 – WAYPOINT IDENTIFIERS
use within the Magnetic Track From/To fields. The
“Cruise Level To” field is used to indicate the highest B. NAMED RNAV Waypoints, Intersections and
cruising level prescribed for use within the Magnetic Reporting Points
Track From/To fields.
The description, addressing only the United States, has
5.139 Time Group been expanded to describe rules covering the naming of
points worldwide.
Examples expanded to include references to sunrise and
sunset. ORIGINAL TEXT FOLLOWS
5.151 FIR/UIR Address (ADDRESS) B. NAMED RNAV Waypoints, Intersections and
Reporting Points.
Source/Content revised to define two letter designators to
be used when addressing ATS messages. In the United States, these waypoints will be assigned
unique 5-character names by the FAA. As the FAA
ORIGINAL TEXT FOLLOWS assigns names to new or established waypoints, the
identifier will be the same as the name. For all other
Source/Content: Addresses of FIR/UIR will be derived waypoints, identifiers should be developed using the
from official government sources and entered in this following rules sequentially until 5-character (or fewer)
field. groups emerge.
5.154 Restriction Identifier (REST IDENT) B.3 Phonetic Letter Names
New field added to define airway restriction record. The use of the minus (-) sign is deleted from this section.
5.155 Airway Restriction Note Indicator (NOTE IND) ORIGINAL TEXT FOLLOWS
New field added to define airway restriction record. 3. Phonetic Letter Names
5.156 Active Indicator (ACT IND) When an ICAO phonetic alpha character is used as a
waypoint name (Alpha, Bravo, Charlie, etc.), use the
New field added to define airway restriction record. equivalent letter (A, B, C, etc.) followed by a minus (-)
sign and the two-letter ICAO code for the country in
which the waypoint is located to produce a 4-character
5.157 Airway Restriction Start/End Date identification code. When more than one waypoint in a
(START/END DATE) country has the same phonetic name, obtain uniqueness
by adding a numeric character after ICAO country code.
New field added to define airway restriction record.
D. Un-Named Turn Points and Intersections
5.158 Airway Restriction Start/End Time This section is expanded to include bearing/distance
(START/END TIME) waypoints.
New field added to define airway restriction record. F. Terminal Waypoints
5.159 Weekly Frequency (WEEKLY FREQ) F.2 Turn Points
New field added to define airway restriction record. This section deleted. Section F.3 renumbered F.2.
5.160 Units of Altitude (UNIT IND)
ORIGINAL TEXT FOLLOWS
New field added to define airway restriction record.
F. Terminal Waypoints
5.161 Restriction Altitude (REST ALT)
2. Turn Points
New field added to define airway restriction record.
Special turn points required to establish a procedural turn
5.162 Step Climb Indicator (STEP) should be assigned identifiers in numerical sequence. The
number should be preceded by the characters “TP.”
New field added to define airway restriction record. Examples: TP1, TP2, TP3.
5.163 Restriction Notes ATTACHMENT 3 – NAVIGATION CHART/FILE
DATA RELATIONSHIP
New field added to define airway restriction record.
These figures showing examples are unnecessarily
5.164 EU Indicator (EU IND) complex. These figures have been replaced with
simplified “generic” examples. The old text is not
New field added to define airway restriction record. included in this Supplement.
SUPPLEMENT 6 TO ARINC SPECIFICATION 424 – Page 12

ATTACHMENT 4 – AIRWAY MINIMUM Rule V.

ALTITUDES
Delete CI.
Text and figures showing examples are obsolete. These
figures have been replaced with simplified “generic” ORIGINAL TEXT FOLLOWS
examples which will not require updating. The old text is
not included in this Supplement. V. When a CI or TI leg is followed by an AF leg, the
“course” or “track to” must be to the DME which defines
ATTACHMENT 5 – PATH AND TERMINATOR the AF arc.
The first paragraph is expanded to indicate the Rule W.
precedence of specific rules over general rules for path
terminator assignments. Add subsection AC, AD and AE.
The first two sentences of the second paragraph are ATTACHMENT 5 – PATH AND TERMINATORS
expanded to clarify the selection and use of path SID CODING RULES
terminators.
Rule A.
ORIGINAL TEXT FOLLOWS
Revise Rule A to clarify text on CA, VA and FA coding
PATH AND TERMINATOR and to state that course legs are preferred over heading
legs as a first leg of a SID transition.
Path Terminators are assigned to all
SID/STAR/Approach records in accordance with the ORIGINAL TEXT FOLLOWS
rules set forth in this attachment. The general intent of the
Path Terminator concept is to permit the coding of SID CODING RULES
standard terminal are procedures without proliferating the
number of named waypoints required to support the A. If on take-off there is a turn greater than 15° without
procedures. an altitude specified before the turn, a course from or a
heading to an altitude (CA, FA or VA) leg will be coded
To avoid proliferation of leg types to be implemented before the turn, using runway heading for the VA leg
within any given system, it is desirable that systems be terminating at 400 feet above the airport elevation. This
designed to accept either VX or CX leg types, but not altitude may vary with local controlling agency
necessarily both. Selection could then be made by system requirements.
type or area of operation, and the relevant data base
coded accordingly. In order to achieve this and to ATTACHMENT 5 – PATH AND TERMINATOR
ultimately simplify the path/terminator matrix currently APPROACHES AND APPROACH TRANSITIONS
required to define present-day terminal area procedures, it
is in the interest of all user airlines to prevail upon their A. General
government agencies and ATC authorities to: (1) permit
FMS-equipped airplanes to fly tracks instead of Add paragraph 10.
procedural headings, and (2) design terminal area
procedures to be compatible with the capabilities of B. VOR Approach
increasing number of FMS-equipped airplanes entering
service. Revise Rule 2 to indicate government specified, non-
FMS procedures.
5. Intercept Angles
ORIGINAL TEXT FOLLOWS
Add new section.
B. VOR Approach Coding
ATTACHMENT 5 – PATH AND TERMINATOR
GENERAL RULES 2. The recommended VHF will be the procedure
specified NAVAID.
Rule A.
ATTACHMENT 5 – Rule G paragraph 2
CI coding is deleted. CD and CR coding is added.
Revised to indicate the preference of a course leg over a
ORIGINAL TEXT FOLLOWS heading leg as the first leg of a missed approach.
GENERAL RULES ORIGINAL TEXT FOLLOWS
A. The following leg types are NAVAID oriented and G. Missed Approaches
the defining parameters will be found in the RECD, VHF,
RHO, THETA, OB MAG CRS, and WAYPINT IDENT 2. The first leg of the missed approach will contain an
fields: altitude to command a climb. If a turn in excess of 15°
from runway heading is required, then a CA, VA or FA
AF CI FC FM VD leg on the runway heading to 400 feet above the airport
CF FA FD PI VR elevation will be the first leg of the missed approach
followed by the required turn.
Rule N.
The rule is expanded to state that turn direction will be
indicated if the turn equals or exceeds 90 degrees.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7645 USA

SUPPLEMENT 7
TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: January 14, 1987

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 8, 1986
SUPPLEMENT 7 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS SUPPLEMENT

This Supplement incorporates microwave landing system

(MLS) records into ARINC 424. Changes to ARINC 424
are also included to improve the operational utility of the
navigation data base. New rules or clarifications to existing
rules are provided by this Supplement.

B. ORGANIZATION OF THIS SUPPLEMENT

The first part of this Supplement printed on goldenrod
colored paper, contains descriptions of the changes
introduced into the Specification by this Supplement. The
second part consists of replacement white pages for the
Specification modified to reflect these changes. The
modified and added material on each replacement page is
identified with c-7 symbols in the margins.

Existing copies of Specification 424-6 may be updated by

inserting the replacement pages where necessary and
destroying the pages they displace. The goldenrod colored
Supplement should be inserted inside the rear cover of the
Specification following Supplement 6.

C. CHANGES TO ARINC SPECIFICATION 424

INTRODUCED BY THIS SUPPLEMENT

This Section presents a complete tabulation of the changes

and additions to the Specification introduced by this
Supplement. Each change is identified using the Section
number and title that will be employed when the Supplement
is incorporated. In each case there is included a brief
description of the addition or change and, for other than very
minor revisions, any text originally contained in the
Specification is reproduced for reference.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 8
TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: October 15, 1989

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: February 26, 1989
SUPPLEMENT 8 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS SUPPLEMENT 4.3.1 Primary Records

This Supplement incorporates revision of the current Airport Add the Airport Identifier and Airport ICAO fields to the
Communications record and the addition of Enroute 424. NDB NAVAID Primary record.
Changes to ARINC Specification 424 are also included to
improve the operational utility of the navigation data base. 4.3.4 Flight Planning Continuation Records
New rules or clarifications to existing rules are provided by
this Supplement Add the UIR Identifier field to the NDB NAVAID Flight
Planning Continuation record.

B. ORGANIZATION OF THIS SUPPLEMENT 4.4.3 Flight Planning Continuation Records

The first part of this Supplement printed on goldenrod Add the UIR identifier field to the Waypoint Flight
colored paper, contains descriptions of the changes Planning Continuation record.
introduced into the Specification by this Supplement. The
second part consists of replacement white pages for the 4.6.1 Primary Records (ER)
Specification modified to reflect these changes. The
modified and added material on each replacement page is Deleted the reference paragraph number shown for Column
identified with c-8 symbols in the margins. 83. Note under box to read Note 1.
Existing copies of Specification 424-7 may be updated by 4.7.1 Primary Records (PA)
inserting the replacement pages where necessary and
destroying the pages they displace. The goldenrod colored New fields added.
Supplement should be inserted inside the rear cover of the
Specification following Supplement 7. 4.7.3 Flight Planning Continuation Records

Add the UIR Identifier field to the Airport Flight Planning

C. CHANGES TO ARINC SPECIFICATION 424 Continuation record.
INTRODUCED BY THIS SUPPLEMENT
4.9.1 SID/STAR/Approach Primary Records
This Section presents a complete tabulation of the changes
and additions to the Specification introduced by this Column 124 through 128 revised to read File Record
Supplement. Each change is identified using the Section Number (5).
number and title that will be employed when the Supplement
is incorporated. In each case there is included a brief 4.12.1 Primary Records (R)
description of the addition or change and, for other than very
minor revisions, any text originally contained in the Columns 15, 16, 25, 26, 60, 61 and 82 through 83 revised.
Specification is reproduced for reference.
4.14 Airport Communications Records (PV)
2.2 Special Navigation Terms
Replaced Airport Communications Records Section.
Editorial correction of EA to ER in the Enroute Airway to
Restrictive Airspace Link definition. 4.20.1 Primary Records

3.2.2.1 VHF NAVAID Columns 21 and 73 through 123 revised.

MLS DMEs added to descriptive paragraph. 4.23 Enroute Communications Records (EV)
3.2.3.6 Enroute Communication Section New Enroute Communications record added.

Add new section. 4.24 Heliport Records (HA)

3.2.4.6 Airport Approach Section (P) New Heliport record added.

New table added after first paragraph. Table 4-1 Record Format
3.2.4.11 MSA Section (P) New records and new fields added to reflect changes in
Section 4.
Statement paragraph revised.
5.5 Subsection Code
3.2.9 Heliport Section (H)
New Subsection Code for Enroute Communications added.
Add new section.
5.6 Airport Identifier (ARPT IDENT)
4.2.4 Flight Planning Continuation Records
Title revised to Airport/Heliport Identifier (ARPT/HELI
Add the UIR Identifier field to the VHF NAVAIDS Flight IDENT). Used On revised to contain Airport and Heliport
Planning Continuation record. Identifier categories. NDB Navaid Records added to Used
 SUPPLEMENT 8 TO ARINC SPECIFICATION 424 - Page 3

On Airport Identifier category. Heliport Records added to 5.66 Station Declination

Used On Heliport Identifier category.
Examples revised.
5.15 File Code
5.71 Name Field
New file code added for Approach records. Deleted File
code for Company Route records. Heliport records added to Used On.

5.17 Waypoint Description Code 5.72 Speed Limit

New Waypoint Description for NDB Navaids added. Heliport records added to Used On.

5.23 Recommended NAVAID 5.73 Speed Limit Altitude

Definition/Description, Used On and Table 5-1 revised. Heliport records added to Used On.

5.24 Theta 5.92 Facility Elevation

Definition/Description and final note revised. Added new Enroute Communications records added to Used On.
example.
5.94 True Bearing
5.25 Rho
ILS records revised to read ILS Continuation records in
Added new example. Used On.

5.29 Altitude Descript 5.101 Communications Type

First note and Used On revised. Enroute Communications records added to Source/Content
table and Used On.
5.30 Altitude/Minimum Altitude
5.102 Radar
Source/Content revised.
Enroute Communications records added to Source/Content
5.36 Latitude table and Used On.
Enroute Communication and Heliport records added to Used 5.103 Communications Frequency
On.
Section revised to include Enroute Communications
5.37 Longitude records.
Enroute Communication and Heliport records added to Used 5.104 Modulation
On. New Heliport entry added to table.
Enroute Communications records added to Source/Content
5.39 Magnetic Variation table and Used On.
Enroute Communication and Heliport records added to Used 5.105 Call Sign
On.
Section revised to include Enroute Communications
5.42 Waypoint Type records.

Enroute Waypoint Table revised. Used On, Length and 5.106 Additional Service (ADDL SERVICE)
Character Type added.
Title revised to Service Indicator (SER IND). Entire section
5.44 Localizer/MLS Identifier (LOC IDENT) (MLS revised.
IDENT)
5.108 IFR Capability (IFR)
Editorial correction to title.
Heliport records added to Definition/Description and Used
5.53 Transition Altitude/Level (TRANS On.
ALTITUDE/LEVEL)
5.115 Direction Restriction
Heliport records added to Source/Content and Used On
paragraphs. Source/Content revised with editorial correction.

5.55 Airport Elevation (ELEV) 5.116 FIR/UIR Identifier

Title revised to Airport/Heliport Elevation (ELEV). Added text to Source/Content. Heliport records added to
Definition/Description, Source/Content and Used On revised Used On.
to include Heliports.
SUPPLEMENT 8 TO ARINC SPECIFICATION 424 - Page 4

5.117 FIR/UIR Indicator ATTACHMENT 2 - WAYPOINT IDENTIFIERS

Enroute Communications records added to Used On. Rule D.1.

5.127 Maximum Altitude Text added to define unnamed turn points, intersections and
bearing/distance waypoints of distance equal to or greater
Added new example. than 100 nautical miles.
5.130 Multiple Code Rule D.3.
Source/Content revised. Reporting positions defined by coordinates paragraphs a.
and b. revised.
5.151 FIR/UIR Address
ATTACHMENT 5 - PATH AND TERMINATOR
Enroute Communications records added to Used On. GENERAL RULES
5.152 Start/End Indicator (S/E IND) Rule B.

Heliport records added to Used On. Table under Rule B revised to allow for IF ending leg for
STAR Route Type 2, 5 or 8 if there is only one leg.
5.153 Start/End Date
Rule C.
Heliport records added to Used On.
Table 1 - Leg Sequence
The following Sections added by this Supplement:
Revised due to the removal of the TI leg.
5.176 Pad Dimensions
Rules O. through AB.
5.177 Public/Military Indicator (PUB/MIL)
Inserted due to editorial omission in Supplement 7.
5.178 Time Zone
Table 2 - Leg Type Illustrations
5.179 Daylight Time Indicator (DAY TIME)
Illustrations revised due to the removal of the TI leg.
5.180 PAD Identifier (PAD IDENT)
Table 3 - Leg Data Fields
5.181 H24 Indicator (H24)
Revised due to the removal of the TI leg.
5.182 Guard/Transmit (G/T)
ATTACHMENT 5 - PATH AND TERMINATOR
5.183 Sectorization (SECTOR)
APPROACHES AND APPROACH TRANSITIONS
5.184 Communication Altitude (COMM ALTITUDE)
Rule H.3.a.
5.185 Associated Facility (ACCOS FAC)
Range for vertical angle revised to -3.00 through -3.77
5.186 Narrative degrees.
5.187 Distance Description (DIST DESC)

5.188 Communications Distance (COMM DIST)

5.189 Remote Site Name

5.190 FIR/RDO Identifier (FIR/RDO)

6.7 Labels
Add paragraph clarifying the use of the EOV label type.

6.9 Summary of Tape Data Layout

Add new section.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 9
TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: March 2, 1990

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: October 26, 1989

SUPPLEMENT 9 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS SUPPLEMENT 4.2.1 Primary Record VHF NAVAIDS

This Supplement incorporates the definition of Preferred Delete editorial text prior to record definition.
Routes, LORAN based approach procedures and Non-
Precision VOR based approach procedures into ARINC 4.3 NDB NAVAID Record (DB)
Specification 424. Changes to ARINC Specification 424 are
also included to improve the operational utility of the Title revised to NDB NAVAID Record (DB or PN).
navigation data base. New rules or clarifications to existing Statement paragraph revised.
rules are provided by this Supplement.
4.4 Waypoint Records (EA or PC)
B. ORGANIZATION OF THIS SUPPLEMENT Statement paragraph revised.

The first part of this Supplement printed on goldenrod 4.4.1 Primary Records
colored paper, contains descriptions of the changes
introduced into the Specification by this Supplement. The Revise Waypoint Record to add Name Format Identifier to
second part consists of replacement white pages for the the Primary records.
Specification modified to reflect these changes. The
modified and added material on each replacement page is 4.5 Holding Pattern Records (EP)
identified with c-9 symbols in the margins.
Statement paragraph revised.
Existing copies of Specification 424-8 may be updated by
inserting the replacement pages where necessary and 4.5.1 Primary Records (EP)
destroying the pages they displace. The goldenrod colored
Supplement should be inserted inside the rear cover of the Revise Holding Pattern Primary records to add
Specification following Supplement 8. Section/Subsection code in place of File Code. Delete File
Code.

C. CHANGES TO ARINC SPECIFICATION 424

INTRODUCED BY THIS SUPPLEMENT 4.6.1 Primary Records (ER)

This Section presents a complete tabulation of the changes Revise Enroute Airway Primary records to add
and additions to the Specification introduced by this Section/Subsection code in place of File Code. Delete File
Supplement. Each change is identified using the Section Code.
number and title that will be employed when the Supplement
is incorporated. In each case there is included a brief 4.8.2 Continuation Records
description of the addition or change and, for other than very
minor revisions, any text originally contained in the Revise Gate Continuation record. Editorial correction to
Specification is reproduced for reference. length field.

1.1.2 Coverage of Flight Planning Needs 4.9.1 Primary Records

Add new section. Revise SID/STAR/Approach Primary records to add

Section/Subsection code in place of File Code. Delete File
3.2.2.1 VHF NAVAID Section (D) - Subsection (D) Code.
Statement paragraph revised. 4.9.2 SID/STAR/Approach Continuation Records

3.2.2.2 Enroute NDB NAVAID Section (D) – Add fields for encoding of LORAN data.
Subsection (DB)
4.13 ILS Marker (PM)
Statement paragraph revised.
Statement paragraph revised.
3.2.4.6 Airport Approaches Section (P) - Subsection (PF)
4.14.3 Additional Continuation Records
Statement paragraph revised.
Add Airport Communication Additional Continuation
3.2.4.13 Airport Terminal NDB Section (P) - record to permit use of Time of Operation field.
Subsection (PN)
4.17.1 Primary Records
Add new section.
Revise the FIR/UIR record to change the FIR/UIR Address
3.2.10 Preferred Routes Section (E) - Subsection (ET) from 2 to 4 characters. Data contained after column 12
through 98 is moved 2 columns to accommodate the
Add new section. revision.
 SUPPLEMENT 9 TO ARINC SPECIFICATION 424 - Page 3

4.18.2 Continuation Records 5.8 Route Identifier (ROUTE IDENT)

Revise Restrictive Airspace Continuation record to permit Section revised for accommodation of Preferred Routes.
use of Time of Operation field.
5.9 SID/STAR Route Identifier (SID/STAR IDENT)
4.18.3 Flight Planning Continuation Record
Revise Definition/Description to reference new Chapter 7.0
Add Restrictive Airspace Flight Planning Continuation NAMING CONVENTIONS.
record to provide Start/End Indicator and Date for Time of
Operation field contained in 4.18.2 Continuation Records. 5.10 Approach Route Identifier (APPROACH IDENT)
4.20.1 Primary Records Revise Source/Content and Examples for accommodation
of Circling Approaches.
Revise MSA (Minimum Sector Altitude) Primary records to
add Section/Subsection code in place of File Code. Delete 5.12 Sequence Number (SEQ NR)
File Code.
Revise Length to add Preferred Routes.
4.21.1 Primary Records
5.15 File Code
Revise Enroute Airways Restriction Primary records to add
Section/Subsection code in place of File Code. Delete File The File Code is being removed from all records. Revise
Code. title to Intentionally left blank and delete remaining text.
4.23 Enroute Communications Records (EV) 5.17 Waypoint Description Code (DESC CODE)
Revise FIR/UIR Address from 2 to 4 characters. Revise Add Runway Centerline Fix entry to Table (iii) Waypoint
Remote Site Name length from 30 to 25 characters to Description Codes to add Non-Precision VOR based
accommodate the revision. approach procedures.

4.23.2 Continuation Records 5.18 Boundary Code (BDY CODE)

Enroute Communications Continuation record revised for Revise South Pacific Area Boundary Code “I” to “1.”
definition of Time of Operation.
5.19 Level (LEVEL)
4.23.3 Continuation Records
Revise Used On to add Preferred Routes and Restrictive
Enroute Communications Continuation record added for Airspace records.
definition of Time of Operation.
5.23 Recommended Navaid (RECD NAV)
4.25 Preferred Routes (ET)
Revise section to add Non-Precision VOR based approach
Add new section. procedures.

4.25.1 Primary Records 5.26 Outbound Magnetic Course (OB MAG CRS)

Add new record. Revise Definition/Description and Source/Content.

4.25.2 Continuation Records 5.28 Inbound Magnetic Course (IB MAG CRS)

Add new record. Revise Definition/Description and Source/Content.

Table 4-1 ARINC 424-9 RECORD FORMAT 5.29 Altitude Descript (ALT DESC)
Table revised to reflect changes introduced in Supplement 9. Add “R” descriptor to Source/Content table to add encoding
of Non-Precision VOR based procedures.
5.5 Subsection Code
5.30 Altitude/Minimum Altitude
Revise Definition/Description. Add Preferred Routes and
Airport Terminal NDBs to table (i) Section and Subsection Revise Definition/Description, Source/Content and Used
Encoding Scheme. On to add Preferred Routes.

5.7 Route Type (RT TYPE)

5.39 Magnetic Variation (MAG VAR)
Revise Definition/Description. Add Preferred Route
Records (ET) table under Source/Content. Revise Approach Revise Source/Content to add records which are oriented to
Route Records (PF) table. TRUE North.
SUPPLEMENT 9 TO ARINC SPECIFICATION 424 - Page 4

5.43 Waypoint Name/Description (NAME/DESC) 5.151 FIR/UIR Address (ADDRESS)

Revise Source/Content to reference new Chapter 7.0 Revise section to incorporate ICAO Document 8585 four
NAMING CONVENTIONS. Revise Examples. character addressing scheme. Revised Used On to include
Enroute Communications records.
5.47 Localizer Bearing (LOC BRG)
5.189 Remote Site Name
Revise Source/Content and Examples to add use of localizer
courses charted with true courses. Revise Length to 25 characters.
5.58 Runway Magnetic Bearing (RWY BRG) The following new Sections added by this Supplement:
Revise Source/Content and Examples to add use of runway 5.191 Triad Stations (TRIAD STA)
bearings charted with true bearings.
5.192 Group Repetition Interval (GRI)
5.62 Inbound Holding Course (IB HOLD CRS)
5.193 Additional Secondary Phase Factor (ASF)
Revise Source/Content and Examples to add use of holding
courses charted with true bearings. 5.194 Initial/Terminus Airport/Fix
5.77 VIA 5.195 Time of Operation

Revise section to add Preferred Routes. 5.196 Name Format Indicator (NAME IND)

5.78 SID/STAR/App/Awy (S/S/A/AWY) 6.3 Bit Density

Revise title to SID/STAR/App/Awy (S/S/A/AWY) Revise text to add 6250 bits per inch bit density capability.
SID/STAR/Awy (S/S/AWY) Add text requiring external reel label to identify bit density
used.
Revise section to add Preferred Routes.
6.4 Coding
5.83 To Fix
Revise text to permit encoding of data using American
Revise section to add Preferred Routes. Standard Code for Information Interchange (ASCII)
capability. Add text requiring external reel label to identify
5.106 Service Indicator (SER IND) encoding standard used.

Revise title to Service Indicator (SERV IND). Delete 7.0 NAMING CONVENTIONS
Source/Content Airport Communications Records Terminal
Control Area Group I and II coding. Add new chapter.

5.114 Duplicate Identifier ATTACHMENT 2 - WAYPOINT IDENTIFIERS

Revise Source/Content and Examples to add Holding Pattern Revise title to ATTACHMENT 2 - INTENTIONALLY
Types. LEFT BLANK. Delete Attachment. Material previously
contained in Attachment 2 is now located in Chapter 7.0
5.127 Maximum Altitude (MAX ALT) Naming Conventions.
Revise Used On to add Preferred Routes. ATTACHMENT 5 - PATH AND TERMINATOR
GENERAL RULES
5.131 Time Code (TIME CD)
Revise the table under Rule B to permit "FM" and "VM" as
Revise to permit use of Time of Operation field. an ending leg for STAR Runway Transition (Route Type 3,
6 or 9).
5.138 Time Group
ATTACHMENT 5 - PATH AND TERMINATOR
Revise Used On to include Restrictive Airspace Continuation APPROACHES AND APPROACH TRANSITIONS
and Preferred Route Continuation records only.
A. GENERAL

5.139 Time Group Revise Rule 2 for Circling Approaches.

The Time Group field is being replaced by Section 5.195 Revise Rule 5 to clarify use of Approach Step-Down Fixes.
Time of Operation. Revise title to Intentionally left blank
and delete remaining text. Add Rule 11 to permit use of ILS procedures for design of
MLS approach.
 SUPPLEMENT 9 TO ARINC SPECIFICATION 424 - Page 5

Add Rule 12 for Non-Precision VOR based approaches.

B. VOR, VORDME, VORTAC AND TACAN Approach

Procedure Coding

Add Rule 1.e for Non-Precision VOR based approaches.

Add Rule 1.f for Circling Approaches.
Add Rule 2.e for Non-Precision VOR based approaches.

Add Rule 2.f for Circling Approaches.

Revise Rule 3.a for Non-Precision VOR based approaches.

Add Rule 3.c for Circling Approaches.

C. RNAV and LORAN Approach Procedures Coding
Revise Section C to include LORAN approach procedures.

D. Localizer and Back Course Approach Procedure Coding

Revise Rule 5 to remove vertical limits. Specify only that a
vertical angle will be contained in the last point in the final
approach fix.
H. NDB Approach Procedure Coding

Add Rule 1.e for Non-Precision VOR based approaches.

Add Rule 1.f for Circling Approaches.

Add Rule 2.e for Non-Precision VOR based approaches.

Add Rule 2.f for Circling Approaches.

Revise Rule 3.a for Non-Precision VOR based approaches.

Add Rule 3.c for Circling Approaches.

 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 10
TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: August 20, 1993

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: August 16, 1993

SUPPLEMENT 10 TO ARINC SPECIFICATION 424 - Page 2

A PURPOSE OF THIS DOCUMENT 4.2.4 Flight Planning Continuation Records

This Supplement introduces changes to ARINC 424 to Section revised.

improve the operational utility of the navigation data base.
4.3 NDB NAVAID Record
B. ORGANIZATION OF THIS DOCUMENT
Section revised.
The first part of this Supplement printed on goldenrod
colored paper, contains descriptions of the changes 4.3.1 Primary Records
introduced into the Specification by this Supplement. The
second part consists of replacement white pages for the Added Datum Code.
Specification modified to reflect these changes. The
modified and added material on each replacement page is 4.3.4 Flight Planning Continuation Records
identified with c-10 symbols in the margins.
Section revised. FIR/UIR Identifier revised to FIR
Existing copies of Specification 424-9 may be updated by Identifier.
inserting the replacement pages where necessary and
destroying the pages they displace. The goldenrod colored 4.4.1 Primary Records
Supplement should be inserted inside the rear cover of the
Specification following Supplement 9. Added references to Note 1 and Note 2. Added Datum
Code. Note 2 revised.
C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT 4.4.3 Flight Planning Continuation Records

This section presents a complete tabulation of the changes Section revised.

and additions to the Specification to be introduced by this
Supplement. Each change or addition is defined by the 4.5 Holding Pattern Records (EP)
section number and the title that will be employed when the
Supplement is eventually incorporated. In each case a brief Section revised.
description of the change or addition is included.
4.5.1 Primary Records
2.2 Special Navigation Terms
Added ICAO Code following Region Code. Added
Definition for Localizer added. references to Note 1. Added Note 1.
3.2.2.1 VHF NAVAID Section (D) - Subsection (D) 4.7.1 Primary Records

Section revised. Added Magnetic/True Indicator and Datum Code.

3.2.3.3 Enroute Holding Patterns Section (E) - Subsection 4.7.3 Flight Planning Continuation Records
(EP)
Section revised.
Section renamed Holding Patterns (E) - Subsection (EP).
Section revised. 4.11 ILS (Localizer and Glide Slope) Records (PI)

3.2.4.8 Airport ILS Section (P) - Subsection (PI) Section renamed Localizer and Glide Slope Records (PI).
Section renamed Airport Localizer Section (P) - Subsection Section revised.
(PI). Section revised.
4.11.2 Continuation Records
3.2.4.10 Airport ILS Markers Section (P) - Subsection
(PM) Removed Note (i). Renamed Note (ii) to Note (i).
Section renamed Airport Localizer Markers Section (P) - 4.13 ILS Marker (PM)
Subsection (PM). Section revised.
Section renamed Localizer Marker (PM). Section revised.
3.2.4.13 Airport Terminal NDB Section (P) - Subsection
(PN) 4.14.1 Primary Records
Section revised. Added Frequency Units, Signal Emission, Sector Facility,
Remote Facility, ICAO Code, Section Code and
4.2 VHF NAVAID Record (D) Subsection Code. Revised Call Sign length.
Section revised. 4.15.1 Primary Records

Added Datum Code.

4.2.1 Primary Records
4.17 FIR/UIR Records (UF)
Added Datum Code.
Section Revised.
 SUPPLEMENT 10 TO ARINC SPECIFICATION 424 - Page 3

4.17.1 Primary Records 5.3 Customer/Area Code (CUST/AREA)

Editorial corrections. Section revised.

4.20.1 Primary Records 5.5 Subsection Code

Added Magnetic/True Indicator. Section revised.

4.21 Enroute Airways Restriction Records (EU) 5.6 Airport/Heliport Identifier (ARPT/HELI IDENT)
Section revised. Section revised.

4.21.1 Primary Records 5.7 Route Type (RT TYPE)

Added provisions for new Enroute Airways Restriction Section revised.
Record types.
5.11 Transition Identifier (TRANS IDENT)
4.21.1 AAltitude Exclusion Record (AE)
Section revised.
Added new record.
5.13 Fix Identifier (FIX IDENT)
4.21.2 AAE Continuation Records
Section revised.
Added new record.
5.14 ICAO Code (ICAO CODE)
4.21.1B Note Restriction Record (NR)
Section revised.
Added new record.
5.16 Continuation Record Number (CONT NR)
4.21.2B NR Continuation Record
Section revised.
Added new record.
5.20 Turn Direction (TURN DIR)
4.21.1C Seasonal Closure Record (SC)
Section revised.
Added new record.
5.27.1 Route Distance From, Holding Distance/Time
4.21.1D Cruising Table Replacement Record (TC) (RTE DIST FROM, HOLD DIST/TIME)

Added new record. Section revised.

4.21.2D TC Continuation Record 5.29 Altitude Descript (ATL DESC)

Added new record. Section revised.
4.21.3 Continuation Records 5.30 Altitude/Minimum Altitude
Record removed. Section revised.

4.23.1 Primary Records 5.33 VOR/NDB Identifier (VOR IDENT/NDB IDENT)

Added Frequency Units and Signal Emission. Renamed Section revised.
Associated Facility to Remote Facility.
5.34 VOR/NDB Frequency (VOR/NDB FREQ)
4.24.1 Primary Records
Section revised.
Added Datum Code and Magnetic/True Indicator.
5.35 NAVAID Class (CLASS)
4.26 Heliport Communiations Records (HV)
Section revised.
Added new record and associated continuation records.
5.37 Longitude (LONGITUDE)
Table 4-1 ARINC 424-10 RECORD FORMAT
Section revised.
Table revised to reflect changes introduced in Supplement
10. 5.38 DME Identifier (DME IDENT)

5.1 General Section revised.

Section revised.
SUPPLEMENT 10 TO ARINC SPECIFICATION 424 - Page 4

5.39 Magnetic Variation (MAG VAR) 5.114 Duplicate Indicator (DUP IND)

Section revised. Section revised.

5.41 Region Code (REGN CODE) 5.116 FIR/UIR Identifier (FIR/UIR IDENT)

Section revised. Section revised.

5.42 Waypoint Type (TYPE) 5.131 Time Code (TIME CD)

Section revised. Section revised.

5.46 Runway Identifier (RUNWAY IDENT) 5.137 Vertical Separation

Section revised. Section revised.

5.69 Threshold Displacement Distance (DSPLCD THR) 5.138 Time Indicator (TIME IND)

Section revised. Section revised.

5.144 MSA Center

5.72 Speed Limit (SPEED LIMIT)
Section revised.
Section revised.
5.151 FIR/UIR Address (ADDRESS)
5.77 VIA Code
Section revised.
Section revised.
5.155 Airway Restriction Note Indicator (NOTE IND)
5.83 To FIX
Section removed.
Section revised.
5.156 Active Indicator (ACT IND)
5.90 ILS/DME Bias
Section removed.
Section revised.
5.157 Airway Restriction Start/End Date (START/END
5.99 Marker Type (MKR TYPE) DATE)

Section revised. Section revised.

5.100 Minor Axis Bearing (MINOR AXIS TRUE BRG) 5.158 Airway Restriction Start/End Time (START/END
TIME)
Section revised.
Section removed.
5.101 Communications Type (COMM TYPE)
5.159 Weekly Frequency (WEEKLY FREQ)
Section revised.
Section removed.
5.102 Radar (RADAR)
5.165 Magnetic/True Indicator (M/T IND)
Section revised.
Section revised.
5.103 Communications Frequency (COMM FREQ)
5.167 MLS Azimuth Bearing (MLS AZ BRG)
Section revised.
Section revised.
5.104 Modulation (MODLN)
5.172 Azimuth Coverage Sector (Right/Left) (AZ COV
Section renamed Frequency Units (FREQ UNIT). Section RIGHT/LEFT)
revised.
Back Azimuth Coverage Sector (Right/Left) (BAZ
5.105 Call Sign (CALL SIGN) COV RIGHT/LEFT)
Section revised. Editorial correction.
5.106 Service Indicator (SERV IND) 5.178 Time Zone

Section revised. Section revised.

 SUPPLEMENT 10 TO ARINC SPECIFICATION 424 - Page 5

5.185 Associated Facility (ACCOS FAC) 6.5 Parity Convention

Section renamed Sector Facility (SEC FAC). Section Section revised.

revised.
6.6 Reel-File Relationship
5.187 Distance Description (DIST DESC)
Section revised.
Section revised.
6.7.1 Volume Header Label (VOL)
5.188 Communications Distance (COMM DIST)
Section revised.
Section revised.
6.9.1 One File, One Reel
5.191 Triad Stations (TRIAD STA)
Added section.
Section revised.
6.9.2 One File, Multiple Reels
5.192 Group Repitition Interval (GRI)
Added section.
Section revised.
6.9.3 Multiple Files, One Reel
5.193 Additional Secondary Phase Factor (ASF)
Added section.
Section revised.
7.2.6 Terminal Waypoints
5.194 Initial/Terminus Airport/Fix
Section revised.
Section revised.
7.4 SID/STAR Procedure Identifiers
5.197 Datum Code (DATUM)
Section revised.
Added section.
7.6 Transition Identifiers
5.198 Modulation (MODULN)
Added section.
Added section.
ATTACHMENT 2 - LOCAL HORIZONTAL
5.199 Signal Emission (SIG EM) REFERENCE DATUM NAME, DATUM CODE AND
ELLIPSOID LIST
Added section.
Added attachment.
5.200 Remote Facility (REM FAC)
ATTACHMENT 3 - NAVIGATION CHART/FILE DATA
Added section. RELATIONSHIP
5.201 Restriction Record Type (REST TYPE) Charts removed. Attachment revised to reflect changes
introduced in Supplement 10.
Added section.
ATTACHMENT 4 - AIRWAY MINIMUM ALTITUDES
5.202 Exclusion Indicator (EXC IND)
Attachment revised.
Added section.
ATTACHMENT 5 - PATH AND TERMINATOR
5.203 Block Indicator (BLOCK IND)
Attachment revised.
Added section.
Figure 5-6 Company Route Record (R) Field Content
Renamed Figure 5-7.

6.1 General
Section revised.
6.2 Number of Tape Tracks

Section revised.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 11

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: August 20, 1993

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: August 16, 1993

SUPPLEMENT 11 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS DOCUMENT 5.144 MSA Center

This Supplement introduces changes necessary to Section renamed Center Fix (CENTER FIX). Section
implement curved path approaches. revised.
B. ORGANIZATION OF THIS DOCUMENT 5.204 ARC Radius (ARC RAD)
The first part of this Supplement printed on goldenrod Added section.
colored paper, contains descriptions of the changes
introduced into the Specification by this Supplement. The 7.2.6.d Terminal Waypoints
second part consists of replacement white pages for the
Specification modified to reflect these changes. The Added section.
modified and added material on each replacement page is
identified with c-11 symbols in the margins. ATTACHMENT 5 PATH AND TERMINATION

Existing copies of Specification 424-9 (Supplement 10 Section revised.

changes are being added simultaneously) may be updated
by inserting the replacement pages where necessary and 1.3 Leg Sequencing
destroying the pages they displace. The goldenrod colored
Supplement should be inserted inside the rear cover of the Section revised. Added "RF" leg type.
Specification following Supplement 9.
1.4 Leg Type Description
C. CHANGES TO SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT Added RF Leg Type.

This section presents a complete tabulation of the changes 1.5 Leg Data Fields
and additions to the Specification to be introduced by this
Supplement. Each change or addition is defined by the Section revised. Table revised.
section number and the title that will be employed when the
Supplement is eventually incorporated. In each case a brief 3.0 PATH AND TERMINATOR RELATED RULES
description of the change or addition is included. VALID FOR ALL PROCEDURE TYPES

2.2 Special Navigation Terms Added rules.

Definition for Precision ARC added.
4.9 SID/STAR/Approach (PD, PE and PF)

Section revised.
4.9.1 Primary Records

Added ARC Radius. Revised MSA Center to Center Fix.

5.24 Theta (THETA)
Section revised.
5.25 Rho (RHO)
Section revised.

5.26 Outbound Magnetic Course

Section revised.
5.27 Route Distance From, Holding Distance Time (RTE
DIST HOLD DIST/TIME)

Section Revised.
5.42 Waypoint Type (TYPE)

Section Revised.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 12
TO
ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: September 15, 1994

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: May 17, 1994

SUPPLEMENT 12 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS DOCUMENT 5.12 Sequence Number (SEQ NR)

This Supplement introduces changes to ARINC This section is revised to support the new VHF Navaid
Specification 424 to improve the operational utility of the Limitation Continuation record.
navigation data base.
5.17 Waypoint Description Code
B. ORGANIZATION OF THIS DOCUMENT
This section is revised to add additional waypoint types.
The first part of this Supplement printed on goldenrod
colored paper, contains descriptions of the changes 5.23 Recommended NAVAID (RECD NAV)
introduced into the Specification by this Supplement. The
second part consists of replacement white pages for the This section is revised based on the Navaid type.
Specification modified to reflect these changes. The
modified and added material on each replacement page is 5.24 Theta
identified with c-12 symbols in the margins.
This section is revised based on the Recommended Navaid.
Existing copies of Specification 424-11 may be updated by
inserting the replacement pages where necessary and 5.25 Rho (RHO)
destroying the pages they displace. The goldenrod colored
Supplement should be inserted inside the rear cover of the This section is revised based on the Recommended Navaid.
Specification following Supplement 11.
5.26 Outbound Magnetic Course
C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS DRAFT SUPPLEMENT This section is revised to reflect changes in the coding rules.

This section presents a complete tabulation of the changes

and additions to the Specification to be introduced by this 5.29 Altitude Description
Supplement. Each change or addition is defined by the
section number and the title that will be employed when the This section is revised to support the new VHF Navaid
Supplement is eventually incorporated. In each case a brief Limitation Continuation record.
description of the change or addition is included.
5.39 Magnetic Variation
2.2 Special Navigation Terms
This section is revised to support Epoch Year Variation.
This section is revised to add definitions for Initial
Approach Fix, Intermediate Approach Fix, Gateway Fix 5.42 Waypoint Type
and Precision Final Approach Fix. In the addition, the
definitions for Final Approach Course Fix and Final This section is revised to add additional enroute and
Approach Fix have been revised. terminal waypoints.

4.2.6 Limitation Continuation Record 5.70 Vertical Angle (VERT ANGLE)

This record is added to code signal limitations of VHF This section, along with Figure 5-11, is revised to reflect
Navaids. changes in the coding rules.

4.9 SID/STAR/Approach (PD, PE and PF)

5.74 Glide Slope Elevation (G.S. ELEV), EL Elevation
This record is revised to add provisions for RNP, and to (EL ELEV)
identity Recommended Navaid Section and Subsection.
This section has been renamed Component Elevation (G.S.
4.11.3 Localizer Simulation Continuation Record ELEV, EL ELEV, AZ ELEV, BAZ ELEV). The text has
been revised for MLS coding.
This record is revised to add Approach Route Identifier.
5.187 Distance Description
5.6 Airport/Heliport Identifier (ARPT IDENT) (HEL
IDENT) This section is revised to support the new VHF Navaid
Limitation Continuation record.
This section is revised to provide for coding where no
officially published ICAO code is available.
5.205 Navaid Limitation Code
5.7 Route Type
This section is added to support the new VHF Navaid
This section is revised to add additional SID, STAR and Limitation Continuation record.
Approach route types.
5.206 Component Affected Indicator
5.10 Approach Route Identifier
This section is added to support the new VHF Navaid
This section is revised to add the capability for coding of Limitation Continuation record.
multiple approach procedures.
 SUPPLEMENT 12 TO ARINC SPECIFICATION 424 - Page 3

5.207 Sector From/Sector To

This section is added to support the new VHF Navaid

Limitation Continuation record.
5.208 Distance Limitation
This section is added to support the new VHF Navaid
Limitation Continuation record.
5.209 Altitude Limitation (ALT LIMIT)
This section is added to support the new VHF Navaid
Limitation Continuation record.
5.210 Sequence End Indicator (SEQ END)

This section is added to support the new VHF Navaid

Limitation Continuation record.
7.2.6.a Terminal Waypoints

This is is revised to add FMS, GPS,. Heliport, NDB CTL

and MLS approach types.

ATTACHMENT 2 - LOCAL HORIZONTAL

REFERENCE DATUM NAME, DATUM CODE AND
ELLIPSOID LIST

This section is revised to add additional datum.

ATTACHMENT 5 - PATH AND TERMINATION

1.2 Beginning and Ending Leg Type

This section is revised to allow FMS and GPS Approach

Procedures. In addition, the use of TF legs is expanded to
allow coding for final approach segments.
1.3 Leg Sequencing

This section is revised to allow leg DF-DF, IF-HA, IF-HM

and IF-PI leg combinations

3.0 Path and Termination Related Rules Valid for Al

Procedure Types
This section is revised to allow DF-DF leg types.

4.0 Standard Instrument Departure (SID) Coding

Rules
This section is revised to prevent unanticipated turns on
departure.

6.0 Approach Procedure Rules Valid for All

Procedure Types
This section is revised to add the coding of FMS, GPS, and
MLS. In addition, revisions are introduced to add TF legs.

APPENDIX 2 - SUBJECT INDEX

This appendix is added to facilitate easier use of ARINC
Specification 424.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 13
TO
ARINC SPECIFICATION 424
NAVIGATION SYSTEM DATA BASE

Published: December 31, 1995

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: May 23, 1995

SUPPLEMENT 13 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS DOCUMENT 4.24 Heliport Records (HA)

This Supplement introduces changes to ARINC 4.24.3 Flight Planning Continuation Records
Specification 424 to improve the operational utility of the
navigation data base. This section is revised to add an indication if the airport
defined in the Primary Record is associated with Controlled
Airspace.
B. ORGANIZATION OF THIS DOCUMENT
4.25 Preferred Route Record (ET)
This Supplement introduces a major rework of ARINC
Specification 424. The normal practice of publishing a This section is revised to permit expansion of the Route
separate supplement to update the existing document has Identifier beyond five characters. In addition, fields are
not been followed. The extensiveness of the changes added to support Aircraft Use Group, Direction Restriction
introduced by Supplement 13 has resulted in the and Altitude Description.
impracticality of producing a separate set of replacement
pages. Supplement 13 is therefore available only as an 4.25.3 Continuation Record (ET)
integral part of ARINC Specification 424-13. The modified
and added material on each page is identified with c-13 This section is added to support the Preferred Route Record
symbols in the margins. Continuation Record.

4.27 Controlled Airspace Records (UC)

C. CHANGES TO ARINC SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT This section is added to support the encoding of controlled
airspace.
This section presents a complete tabulation of the changes
and additions to the Specification to be introduced by this 4.28 Geographical Reference Tables (TG)
Supplement. Each change or addition is defined by the
section number and the title. In each case a brief This section is added to support Preferred Routes.
description of the change or addition is included.
5.3 Customer/Area Code (CUST/AREA)

2.2 Special Navigation Terms This section is revised so that Preferred Route Records and
Geographical Reference Table Records are indicated as
This section is revised to add the definition for Phantom having no area code.
Waypoint.
5.5 Subsection Code
3.2.7 Tables Section (T)
This section is revised to include the new Controlled
This section was previously titled Cruising Table Section Airspace Record.
(T) - Subsection (TC). Sections 3.7.2.1 and 3.7.2.2 have
been added to identify previously include cruising table 5.6 Airport/Heliport Identifier (ARPT/HELI IDENT)
information and added geographical reference table
information. This section is revised to support non-officially published
identifiers.
4.6 Enroute Airway Records (ER)
5.7 Route Type (RT TYPE)
This section is revised to add provisions for Required
Navigation Performance (RNP). Note 1 is revised to This section is revised so that Preferred Route Records have
describe the use of Column 19 for ATS Route Service. an expanded Route Type capability and SID Route Types
are presented in the correct order.
4.7 Airport Records (PA)
5.8 Route Identifier
4.7.3 Flight Planning Continuation Records
This section is revised to expand the Preferred Route
This section is revised to add an indication if the airport Records to 10 characters. Six characters were defined in
defined in the Primary Record is associated with Controlled previous versions of this Specification.
Airspace.
5.10 Approach Route Identifier (APPROACH IDENT)

4.10 Runway Records (PG) This section is revised to support Helicopter Approach
Procedures.
This section is revised to add runway gradient. In addition,
to support MLS, Localizer is revised to Localizer/MLS. 5.11 Transition Identifier (TRANS IDENT)
The record now permits the coding of a second
Localizer/MLS. This section is revised to support RNAV SID, FMS SID,
RNAV STAR and FMS STAR route types.
 SUPPLEMENT 13 TO ARINC SPECIFICATION 424 - Page 3

5.12 Sequence Number (SEQ NR) 5-12 Controlled and Restrictive Airspace and FIR/UIR
Boundaries is completely revised.
This section is revised to support Controlled Airspace and
Geographical Reference Table records. 5.119 Arc Distance (ARC DIST)

5.17 Waypoint Description Code (WAY DESC) This section is revised to support Controlled Airspace
Records.
This section is completely revised.
5.120 Arc Bearing (ARC BRG)
5.19 Level (LEVEL)
This section is revised to support Controlled Airspace
This section is revised to support Controlled Airspace Records.
Records.
5.121 Lower/Upper Limit
5.23 Recommended Navaid (RECD NAV)
This section is revised to support Controlled Airspace
This section is revised to support Un-Biased ILSDME and Records.
Localizer Markers.
5.130 Multiple Code (MULTI CD)
5.29 Altitude Description (ALT DESC)
This section is revised to support Controlled Airspace
This section is revised to support Preferred Route Records. Records.

5.30 Altitude/Minimum Altitude

5.131 Time Code (TIME CD)
This section is revised to describe the application of
minimum and maximum altitude as it relates to Preferred This section is revised to support Controlled Airspace
Route Records. Records.

5.36 Latitude (LATITUDE) 5.132 NOTAM

This section is revised to include Controlled Airspace This section is revised to support Controlled Airspace
Records. Records.

5.37 Longitude (LONGITUDE) 5.133 Unit Indicator (UNIT IND)

This section is revised to include Controlled Airspace This section is revised to support Controlled Airspace
Records. Records.

5.42 Waypoint Type (TYPE) 5.138 Time Indicator (TIME IND)

This section is revised to add the arc center fix waypoint to This section is revised to support Controlled Airspace
the Terminal Waypoints table. Records.

5.44 Localizer/MLS Identifier (LOC IDENT), (MLS 5.140 Controlling Agency

IDENT)
This section is revised to support Controlled Airspace
This section is revised to encode multiple localizers Records.
associated with a single runway.

5.77 VIA Code 5.149 Figure of Merit (MERIT)

This section is revised to provide Preferred Route Records This section is revised to add range values to the
with two new fix related capabilities. descriptions and to designate out of service VHF
NAVAIDS.
5.80 Localizer/MLS Category/Classification
(CAT/CLASS) 5.195 Time of Operation (TIME OF OPERATION)

This section was previously titled ILS Category. This This section is revised to support Controlled Airspace
section is completely revised. Records.

5.115 Direction Restriction 5.211 Required Navigation Performance (RNP)

This section is revised to support Preferred Route Records. This section is added to provide provision for support of
RNP.
5.118 Boundary VIA
5.212 Runway Gradient (RWY GRAD)
This section is revised to add application rules and to
provide support for the Controlled Airspace Record. Figure This section is added to support Runway records.
SUPPLEMENT 13 TO ARINC SPECIFICATION 424 - Page 4

5.213 Controlled Airspace Type (ARSP TYPE) 5.0 Standard Terminal Arrival Route (STAR) Coding
Rules
This section is added to support Controlled Airspace
records. This section is revised to add a rule for Expect Altitudes.

5.214 Controlled Airspace Center (ARSP CNTR) 6.0 Approach Procedure Rules Valid for All Procedure
Types
This section is added to support Controlled Airspace
records. This section is revised to includes a number of proposals to
modify the Approach Procedure Coding.
5.215 Controlled Airspace Classification (ARSP CLASS)
7.0 Missed Approach Procedure Rules Valid for All
This section is added to support Controlled Airspace Procedure Types
records.
This section is revised to includes a number of proposals to
5.216 Controlled Airspace Name (ARSP NAME) modify the Missed Approach Procedure Rules.

This section is added to support Controlled Airspace APPENDIX 2 - STRAIGHT-IN CRITERIA

records.
This appendix is added using material previously contained
5.217 Controlled Airspace Indicator (CTLD ARSP IND) in Attachment 5, Sections 6.2.7 and 6.2.8.

This section is added to support Airport Flight Planning APPENDIX 3 - SUBJECT INDEX
Continuation records.
Previously Appendix 2, this appendix is renumbered
5.218 Geographical Reference Table Identifier Appendix 3.
(GEO REF TBL ID)

This section is added to support Geographical Reference

Table records.

5.219 Geographical Entity (GEO ENT)

This section is added to support Geographical Reference

Table records.

5.220 Preferred Route Use Indicator (ET IND)

This section is added to support Preferred Route and

Geographical Reference Table Records.

5.221 Aircraft Use Group (ACFT USE GP)

This section is added to support Preferred Route records.

7.5 Preferred Route Identifiers

This section is completely revised to clearly define and

expand the naming conventions.

ATTACHMENT 5 - PATH AND TERMINATION

1.2 Beginning and Ending Leg Type

This section is revised to allow FMS and GPS approach

procedures.

1.3 Leg Sequencing

This section is revised to allow the leg IF/RF combination.

3.0 Path and Termination Related Rules Valid for All

Procedure Types

This section is revised to add rules for RF legs and Phantom

Waypoints.
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 14
TO
ARINC SPECIFICATION 424
NAVIGATION SYSTEM DATA BASE

Published: February 11, 2000

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: August 25, 1999

SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 2

A. PURPOSE OF THIS SUPPLEMENT 3.2.3.5 Enroute Airways Restriction Section (E),

Subsection (U)
This Supplement introduces revisions and additions to the
body and Attachments of ARINC Specification 424. The Text was revised to be consistent with Section
These changes include revisions to Path Point Concept, 3.2.3.6.
GLS Record, and DGPS Record and Modification to
Paths and Terminators. 3.2.4.2 Airport Gates Section (P), Subsection (B)
B. ORGANIZATION OF THIS DOCUMENT This section was expanded to include Standard data for
airport gates.
The material in Supplement 14 is integrated into ARINC
Specification 424 to form an updated version of the 3.2.4.6 Airport Approaches Section (P), Subsection (F)
standard.
Text was added for clarification.
The changes introduced by Supplement 14 have been
identified using change bars and are labeled in the margin 3.2.4.8 Airport And Heliport Localizer/Glide Slope
by a “c-14” indicator. Section (P), Subsection (I)

C. CHANGES TO SPECIFICATION 424 This section was revised to support Heliport records.
INTRODUCED BY THIS SUPPLEMENT
3.2.4.9 Airport and Heliport MLS Section (P),
This section presents a complete tabulation of the changes Subsection (L)
and additions to the Specification introduced by this
Supplement. Each change or addition is defined by the This section was revised to support Heliport records.
section number and the title that will be employed. In
each case a brief description of the change or addition is 3.2.4.10 Airport and Heliport Marker/ Locator Section
included. (P), Subsection (M)

1.3.1 Coverage of Helicopter Operation Needs This section was revised to support Heliport records.

New section was added. 3.2.4.13 Airport and Heliport Terminal NBD Section(P),
Subsection (N)
2.2 Special Navigation
Section 3.3.5, 3.3.6, 3.3.7, and 3.3.8 were added to
The Final Approach Course Fix definition was revised. support Heliport records.

The “Final End Point definition” was added. 3.2.4.14 Airport and Heliport Path Point Section (P),
Subsection (P)
2.3 Precision RNAV Terms
This section was added.
This section was added.
3.2.4.15 Flight Planning Arrival / Departure Data Record
ALL TITLES IN SECTIONS 3 WERE MODIFIED TO Section (P), Subsection (R)
ONE-LETTER CHARACTERS IN THE
SUBSECTIONS This section was added.

3.1 User File Organization 3.2.4.16 GNSS Landing System (GLS) Section (P),
Subsection (T)
The second paragraph was added by Supplement 14.
This section was added.
3.2.1 General
3.2.5 Company Route and Alternation Destination
Last sentence in first paragraph was modified for clarity. Section (R)

3.2.2.1 VHF Navaid Section (D), Subsection (blank) The title was revised to “Company Route and Alternation
Destination Section (R).”
Sections 3.3.5, 3.3.6, 3.3.7, and 3.3.8 were added.
3.2.5.1 Company Route Section (R) Subsection (Blank)
3.2.2.2 NDB Navaid Section (D), Subsection (B)
The text was revised to support Alternate Destination
Sections 3.2.10, 3.3.5, 3.3.6, 3.3.7 and 3.3.8 were added. Record.
3.2.5.2 The Alternate Record Section (R) Subsection (A)
3.2.3.1 Enroute Waypoint Section (E), Subsection (A)
This Section was added to support Alternate Destination
Sections 3.2.10, 3.3.5, 3.3.6, and 3.3.7 were added. Records.
 SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 3

3.2.6.2 FIR/UIR Section (U), Subsection (F) 4.0.1 General

Existing text was modified for clarity. Was numbered 4.1 prior to 424 -14.

3.2.6.3 Controlled Airspace Section (U), Subsection (C) Descriptive paragraph was revised to include Helicopter
user file.
This section was added.
3.2.7.2 Geographical Reference Table Section (T), 4.1 Master Airline User File
Subsection (G)
This section title added.
The reference to Section 3.3.10 was revised to 3.2.9.
4.1.2 VHF NAVAID Record (D)
3.2.9 Preferred Routes Section (E), Subsection (T)
Was numbered 4.2 prior to 424.14.
This section was numbered 3.2.10 prior to 424-14. It was
renumbered without change when the former 3.2.9, 4.1.2.1 VHF NAVAID Primary Records
Heliport Section was moved to the Master Helicopter
User File Section 3.3. Was numbered 4.2.1 prior to 424-14.
3.3 Master Helicopter User File Content 4.1.2.2 VHF NAVAID Continuation Records

This section was added. Was numbered 4.2.2 prior to 424-14.

3.3.1 General 4.1.2.3 VHF NAVAID Simulation Continuation Records

This section was added. Was numbered 4.2.3 prior to 424-14.

3.3.2 Jointly and Specifically used Section / Subsection 4.1.2.4 VHF NAVAID Flight Planning Continuation
Records
This section was added.
Was numbered 4.2.4 prior to 424-14.
3.3.3 Heliport Section (H), Subsection (A)
4.1.2.5 VHF NAVAID Flight Planning Continuation
This section was added. Records

3.3.4 Heliport Terminal Waypoints Section (H), Was numbered 4.2.5 prior to 424-14.
Subsection (C)
4.1.2.6 VHF NAVAID Limitation Continuation Records
This section was added.
Was numbered 4.2.6 prior to 424-14.
3.3.5 Heliport Standard Instrument Departures (SIDs)
Section (H), Subsection (D) 4.1.3 NDB NAVAID Record (DB) or (PN)

This section was added. Was numbered 4.3 prior to 424-14.

3.3.6 Heliport Standard Terminal Arrival Routes 4.1.3.1 NDB NAVAID Primary Records
(STARs) Section (H), Subsection (E)
Was numbered 4.3.1 prior to 424-14.
This section was added.
4.1.3.2 NDB NAVAID Continuation Records
3.3.7 Heliport Approaches Section (H), Subsection (F)
Was numbered 4.3.2 prior to 424-14.
This section was added.
4.1.3.3 NDB NAVAID Simulation Continuation Records
3.3.8 Heliport MSA Section (H), Subsection (S)
Was numbered 4.3.3 prior to 424-14.
This section was added.
4.1.3.4 NDB NAVAID Flight Planning Continuation
Records
3.3.9 Heliport Communications Section (H), Subsection
(V) Was numbered 4.3.4 prior to 424-14.

This section was added.

4.1.3.5 NDB NAVAID Flight Planning Continuation
SECTION 4 HAS BEEN RENUMBERED TO Records
ACCOMMODATE THE INTRODUCTION OF
ROTOR-WING RECORDS Was numbered 4.3.5 prior to 424-14.
SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 4

4.1.4 Waypoint Record (EA) or (PC) 4.1.7.1 Airport Primary Records

Was numbered 4.4 prior to 424-14. Was numbered 4.7.1 prior to 424-14 and the title was
changed to “Airport Primary Records.”
Text was added to support Helicopter Enroute and
Terminal Waypoints Columns 32 and 69 through 132 were revised.

4.1.4.1 Waypoint Primary Records 4.1.7.2 Airport Continuation Records

Was numbered 4.4.1 prior to 424-14. Was numbered 4.7.2 prior to 424-14 and the title was
changed to “Airport Continuation Records.”
Text was added to support Helicopter Records.
4.1.7.3 Airport Flight Planning Continuation Records
4.1.4.2 Waypoint Continuation Records
Was numbered 4.7.3 prior to 424-14 and the title was
Was numbered 4.4.2 prior to 424-14. changed to “Airport Flight Planning Continuation
Records.”
4.1.4.3 Waypoint Flight Planning Continuation Records
4.1.7.4 Airport Flight Planning Continuation Records
Was numbered 4.4.3 prior to 424-14.
Was numbered 4.7.4 prior to 424-14 and the title was
4.1.4.4 Waypoint Flight Planning Continuation Records changed to “Airport Flight Planning Continuation
Records.”
Was numbered 4.4.4 prior to 424-14.
4.1.8 Airport Gate Records (PB)
4.1.5 Holding Pattern Records (EP)
Was numbered 4.8 prior to 424-14 and the title was
Was numbered 4.5 prior to 424-14. changed to “Airport Gate Records (PB).”
4.1.5.1 Holding Pattern Primary Records 4.1.8.1 Airport Gate Primary Records

Was numbered 4.5.1 prior to 424-14. Was numbered 4.8.1 prior to 424-14 and the title was
changed to “Airport Gate Primary Records.”
Note 1 was revised to support Helicopter Records.
4.1.8.2 Airport Gate Continuation Records
4.1.5.2 Holding Pattern Continuation Records
Was numbered 4.8.2 prior to 424-14 and the title was
Was numbered 4.5.2 prior to 424-14. changed to “Airport Gate Continuation Records.”

4.1.6 Enroute Airway Records (ER) 4.1.9 Airport SID/STAR/APPROACH Records (PD, PE,
and PF)
Was numbered 4.6 prior to 424-14.
Was numbered 4.9 prior to 424-14 and the title was
Text was added to support Helicopter Records. changed to “Airport SID/STAR/APPROACH Records
PD, PE, and PF).
4.1.6.1 Enroute Airways Primary Records
Was numbered 4.6.1 prior to 424-14. 4.1.9.1 SID/STAR/Approach Primary Records

4.1.6.2 Enroute Airways Continuation Records Was numbered 4.9.1 prior to 424-14.

Was numbered 4.6.2 prior to 424-14. Columns 117 through 123 were revised.

4.1.6.3 Enroute Airways Flight Planning Continuation Notes 1 and 2 were added.
Records

Was numbered 4.6.3 prior to 424-14. 4.1.9.2 Airport SID/STAR/APPROACH Continuation

Records
4.1.6.4 Enroute Airways Flight Planning Continuation
Records Was numbered 4.9.2 prior to 424-14 and the title was
changed to “Airport SID/STAR/APPROACH
Was numbered 4.6.4 prior to 424-14. Continuation Records.”

4.1.7 Airport Records (PA) Columns 73 through 132 were revised.

Was numbered 4.7 prior to 424-14. Notes 1, 2 and 3 were added.

 SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 5

4.1.9.3 Airport SID/STAR/APPROACH Flight Planning 4.1.13 Airport and Heliport Localizer Marker
Continuation Records Records(PM)

Was numbered 4.9.3 prior to 424-14 and the title was Was numbered 4.13 prior to 424-14 and the title was
changed to “Airport SID/STAR/APPROACH Flight changed to “Airport and Heliport Localizer Marker
Planning Continuation Records.” Records(PM).”

4.1.9.4 Airport SID/STAR/APPROACH Flight Planning 4.1.13.1 Airport and Heliport Localizer Marker Primary
Continuation Records Records

Was numbered 4.9.4 prior to 424-14 and the title was Was numbered 4.13.1 prior to 424-14 and the title was
changed to “Airport SID/STAR/APPROACH Flight changed to “Airport and Heliport Localizer Marker
Planning Continuation Records.” Primary Records.”

4.1.10 Runway Records (PG) 4.1.14 Airport Communications Records (PV)

Was numbered 4.10 prior to 424-14. Was numbered 4.14 prior to 424-14.

4.1.10.1 Runway Primary Records 4.1.14.1 Airport Communications Primary Records

Was numbered 4.10.1 prior to 424-14 and the title was Was numbered 4.14.1 prior to 424-14 and the title was
changed to “Runway Primary Records.” changed to “Airport Communications Primary Records.”

Section was revised to support GLS records. 4.1.14.2 Airport Communications Continuation Records

4.1.10.2 Runway Continuation Records Was numbered 4.14.2 prior to 424-14 and the title was
changed to “Airport Communications Continuation
Was numbered 4.10.2 prior to 424-14 and the title was Records.”
changed to “Runway Continuation Records.”
4.1.14.3 Airport Additional Communications
4.1.10.3 Runway Simulation Continuation Records Continuation Records

Was numbered 4.10.3 prior to 424-14 and the title was Was numbered 4.14.3 prior to 424-14 and the title was
changed to “Runway Simulation Continuation Records.” changed to “Airport Additional Communications
Continuation Records.”
4.1.11 Airport and Heliport Localizer and Glide Slope
Records (PI) 4.1.15 Airways Marker Records (EM)
Was numbered 4.11 prior to 424-14 and the title was Was numbered 4.15 prior to 424-14.
changed to “Airport and Heliport Localizer and Glide
Slope Records (PI).” 4.1.15.1 Airways Marker Primary Records

4.1.11.1 Airport and Heliport Localizer and Glide Slope Was numbered 4.15.1 prior to 424-14 and the title was
Primary Records changed to “Airways Marker Primary Records.”

Was numbered 4.11.1 prior to 424-14 and the title was 4.1.16 Cruising Tables Records (TC)
changed to “Airport and Heliport Localizer and Glide
Slope Primary Records.” Was numbered 4.16 prior to 424-14.

4.1.11.2 Airport and Heliport Localizer and Glide Slope 4.1.16.1 Cruising Tables Primary Records
Continuation Records
Was numbered 4.16.1 prior to 424-14 and the title was
Was numbered 4.11.2 prior to 424-14 and the title was changed to “Cruising Tables Primary Records.”
changed to “Airport and Heliport Localizer and Glide
Slope Continuation Records.” 4.1.17 FIR/UIR Records (UF)
4.1.11.3 Airport and Heliport Localizer and Glide Slope Was numbered 4.17 prior to 424-14.
Simulation Continuation Records
4.1.17.1 FIR/UIR Primary Records
Was numbered 4.11.3 prior to 424-14 and the title was
changed to “Airport and Heliport Localizer and Glide Was numbered 4.17.1 prior to 424-14 and the title was
Slope Simulation Continuation Records.” changed to “FIR/UIR Primary Records.”

4.1.12 Company Route Records (R) 4.1.18 Restrictive Airspace Records (UR)

Was numbered 4.12 prior to 424-14. Was numbered 4.18 prior to 424-14.
SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 6

4.1.18.1 Restrictive Airspace Primary Records 4.1.21C.2 Cruising Table Replacement Continuation
Records
Was numbered 4.18.1 prior to 424-14 and the title was
changed to “Restrictive Airspace Primary Records.” Was numbered 4.21C.2 prior to 424-14.
4.1.18.2 Restrictive Airspace Continuation Records 4.1.22 Airport and Heliport MLS (Azimuth, Elevation
and Back Azimuth) Records
Was numbered 4.18.2 prior to 424-14 and the title was
changed to “Restrictive Airspace Continuation Records.” Was numbered 4.22 prior to 424-14 and the title was
changed to “Airport and Heliport MLS (Azimuth,
4.1.18.3 Restrictive Airspace Flight Planning Elevation and Back Azimuth) Records.”
Continuation Records
4.1.22.1 Airport and Heliport MLS Primary Records
Was numbered 4.18.3 prior to 424-14 and the title was
changed to “Restrictive Airspace Flight Planning Was numbered 4.22.1 prior to 424-14 and the title was
Continuation Records.” changed to “Airport and Heliport MLS Primary Records.”
4.1.19 Grid MORA Records (AS) 4.1.22.2 Airport and Heliport MLS Continuation Records

Was numbered 4.19 prior to 424-14. Was numbered 4.22.2 prior to 424-14 and the title was
changed to “Airport and Heliport MLS Continuation
4.1.19.1 Grid MORA Primary Records Records.”

Was numbered 4.19.1 prior to 424-14 and the title was 4.1.23 Enroute Communications Record (EV)
changed to “Grid MORA Primary Records.”
Was numbered 4.23 prior to 424-14.
4.1.20 Airport MSA (Minimum Sector Altitude) Records
(PS) 4.1.23.1 Enroute Communications Primary Records
Was numbered 4.20 prior to 424-14 and the title was Was numbered 4.23.1 prior to 424-14 and the title was
changed to “Airport MSA (Minimum Sector Altitude) changed to “Enroute Communications Primary Records.”
Records (PS).”
4.1.23.2 Enroute Communications Continuation Records
4.1.20.1 Airport MSA Primary Records
Was numbered 4.23.2 prior to 424-14 and the title was
Was numbered 4.20.1 prior to 424-14 and the title was changed to “Enroute Communications Continuation
changed to “Airport MSA Primary Records.” Records.”
4.1.20.2 Airport MSA Continuation Records 4.1.23.3 Enroute Communications Continuation Records

Was numbered 4.20.2 prior to 424-14. Was numbered 4.23.3 prior to 424-14 and the title was
changed to “Enroute Communications Continuation
4.1.21 Enroute Airways Restriction Records (EU) Records.”

Was numbered 4.21 prior to 424-14. 4.1.24 Preferred Route Records (ET)

4.1.21.1 Altitude Exclusion Primary Records Was numbered 4.25 prior to 424-14.

Was numbered 4.21.1 prior to 424-14. 4.1.24.1 Preferred Route Primary Records
4.1.21.2 Altitude Exclusion Continuation Records Was numbered 4.25.1 prior to 424-14.

Was numbered 4.21.2 prior to 424-14. 4.1.24.2 Preferred Route Continuation Records

4.1.21A.1 Note Restriction Primary Records Was numbered 4.25.2 prior to 424-14 and the title was
changed to “Preferred Route Continuation Records.”
Was numbered 4.21A.1 prior to 424-14.
4.1.24.3 Preferred Route Continuation Records
4.1.21A.2 Note Restriction Continuation Records
Was numbered 4.25.3 prior to 424-14 and the title was
Was numbered 4.21A.2 prior to 24-14. 4 changed to “Preferred Route Continuation Records.”
4.1.21B.1 Seasonal Closure Primary Records 4.1.25 Controlled Airspace Records (UC)

Was numbered 4.21B.1 prior to 424-14. Was numbered 4.27 prior to 424-14.

4.1.21C.1 Cruising Table Replacement Primary Records The following text was added to this section:

Was numbered 4.21C.1 prior to 424-14.

 SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 7

It includes controlled airspace associated with Airports 4.2.1 Heliport Records

and Heliports.
Was numbered 4.24 prior to 424.14
4.1.25.1 Controlled Airspace Primary Records
4.2.1.1 Heliport Primary Records
Was numbered 4.27.1 prior to 424-14.
Was numbered 4.24.1 prior to 424-14 and the title was
4.1.25.2 Controlled Airspace Continuation Records changed to “Heliport Primary Records.”

Was numbered 4.27.2 prior to 424-14 and the title was 4.2.1.2 Heliport Continuation Records
changed to “Controlled Airspace Continuation Records
Was numbered 4.24.2 prior to 424-14 and the title was
4.1.26 Geographical Reference Table Records (TG) changed to “Heliport Continuation Records.”

Was numbered 4.28 prior to 424-14. 4.2.1.3 Heliport Flight Planning Continuation Records

4.1.26.1 Geographical Reference Table Primary Records Was numbered 4.24.3 prior to 424-14 and the title was
changed to “Heliport Flight Planning Continuation
Was numbered 4.28.1 prior to 424-14 and the title was Records.”
changed to “Geographical Reference Table Primary
Records.” 4.2.1.4 Heliport Flight Planning Continuation Records

4.1.27 Flight Planning Arrival/Departure Data Record Was numbered 4.24.4 prior to 424-14 and the title was
(PR) changed to “Heliport Flight Planning Continuation
Records.”
This section was added.
The Following Sections Have Been Added To Support
4.1.27 Flight Planning Arrival / Departure Data Rotor-Wing Records:

This section was added. 4.2.2 Heliport Terminal Waypoint Record (HC)

4.1.27.1 Primary Record 4.2.2.1 Primary Records

This section was added. 4.2.2.2 Continuation Records

4.1.27.2 Continuation Records 4.2.2.3 Flight Planning Continuation Records

This section was added. 4.2.2.4 Flight Planning Continuation Records

4.1.27.3 Continuation Records 4.2.3 Heliport SID/STAR / Approach (HD/HE/HF)

This section was added. 4.2.3.1 Heliport SID/STAR/Approach Primary Records

4.1.28 Path Point Records (PP) 4.2.3.2 Heliport SID/STAR/Approach Continuation

Records
This section was added.
4.2.3.3 Heliport SID/STAR/Approach Flight Planning
4.1.29 GLS Record (PT) Continuation Records

This section was added. 4.2.3.4 Heliport SID/STAR/Approach Flight Planning

Continuation Records
4.1.29.1 Primary Records
4.2.4 Heliport MSA (HS)
This section was added.
4.2.4.1 Primary Records
4.1.30 Alternate Record (RA)
4.2.4.2 Continuation Records
This section was added.
4.2.5 Heliport Communications Records (HV)
4.1.30.1 Primary Record
Was numbered 4.26 prior to 424-14.
This section was added.
4.2.5.1 Heliport Communications Primary Records
4.2 Master Helicopter User file (HA)
Was numbered 4.26.1 prior to 424-14 and the title was
This section was added. change to “Heliport Communications Primary Records.”
SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 8

4.2.5.2 Heliport Communications Continuation Records 5.20 Turn Direction (TURN DIR)

Was numbered 4.26.2 prior to 424-14 and the title was The “Used On” text was revised to support Heliport
changed to “Heliport Communications Continuation Approach Record.
Records.”
5.21 Path and Termination (PATH TERM)
4.2.5.3 Heliport Communications Continuation Records
The “Used On” text was revised to support Heliport
Was numbered 4.26.3 prior to 424-14 and the title was Approach Record.
changed to “Heliport Communications Continuation 5.22 Turn Direction Valid (TDV)
Records.”
The “Used On” text was revised to support Heliport
5.5 Subsection Code (SUB CODE) Approach Record.

Section was revised to support Heliport and GLS 5.23 Recommended Navaid (RECD NAV)
encoding schemes and the Alternate Record.
Descriptive paragraph was revised to support Heliport.
5.6 Airport/Heliport Identifier (ARPT/HELI IDENT)
Item “c” was revised to support GLS navaid.
The “Used On” text was expanded to identify airport and
heliport identifiers. Item “g” was revised for clarity.

5.7 Route Type (RT TYPE): Item “h” and “i” were added were added by Supplement
14.
Section was revised to support Heliport and GLS Route
types. The “Used On” text was revised to support Heliport
Approach Record
5.8 Route Identifier (ROUTE IDENT)
5.24 Theta (THETA)
The existing text was modified to support heliport
records. The “Used On” text was revised to support Heliport
Approach Records.
5.9 SID/STAR Route Identifier (SID/STAR IDENT)
5.25 Rho (RHO)
The “Used On” text was revised to support Heliport
Records. The “Used On” text was revised to support Heliport
Approach Records.
5.10 Approach Route Identifier (APPROACH IDENT)
5.26 Outbound Magnetic Course (OB MAG CRS)
This section was revised to support Heliport Approach
Records. The “Used On” text was revised to support Heliport
Approach Records.
5.11 Transition Identifier (TRANS IDENT)
5.27 Route Distance From, Holding Distance/Time
This section was revised to support Heliport records and (RTE DIST FROM, HOLD DIST/TIME)
the text was modified for clarity.
The “Used On” text was revised to support Heliport
5.12 Sequence Number (SEQ NR) Approach Records.

The “Used On” text was revised to support Heliport 5.28 Inbound Magnetic Course (IB MAG CRS)
Approach Record.
Section was revised to include a paragraph describing the
5.13 Fix Identifier (FIX IDENT) use of “HX” group of Path Terminator codes.

The “Used On” text was revised to support Heliport 5.29 Altitude Description (ALT DESC)
Approach Record.
The last sentence of the Definition/Description paragraph
5.17 Waypoint Description Code (DESC CODE) was revised to include “at or above to at or below.”

Text and waypoint description was revised to support Identifiers “H,” “J” and “V” were added to the altitude
Heliport records. description table and identifier “R” was remove.

Note 16 was revised to support Final End Point. Identifiers B, G, and I of the Waypoint Description
Crossing was revised for clarity.
Note 19 was added by this Supplement.
5.30 Altitude/Minimum Altitude

This section revised to support Heliport records.

 SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 9

5.36 Latitude (LATITUDE) 5.58 Runway Magnetic Bearing (RWY BRG)

The “Used On” text was revised to support Heliport Character type was changed to Alpha/Numeric.
Records.
5.62 Inbound Holding Course (IB HOLD CRS)
5.37 Longitude (LONGITUDE)
Character type was changed to Alpha/Numeric.
The “Used On” text was revised to support Heliport
Records. 5.67 Threshold Crossing Height (TCH)
5.38 DME Identifier (DME IDENT)
The “Used On” text was revised to support Heliport
The existing text was modified for clarity. Records.

5.39 Magnetic Variation (MAG VAR, D MAG VAR) 5.70 Vertical Angle (VERT ANGLE)

The “Used On” text was revised to support GLS Records. The “Used On” text was revised to support Heliport
Records.
5.42 Waypoint Type
Figure 5-11 and the note on angle constraints were
“U” and “V” added to Enroute Waypoints. deleted.

“P” added to the Terminal Waypoints. 5.72 Speed Limit (SPEED LIMIT)

The “Used On” text was revised to support Heliport Section revised to support Heliport records.
Records
5.74 Component Elevation (GS ELEV, EL ELEV, AZ
5.43 Waypoint Name/Description (NAME/DESC) ELEV, BAZ ELEV, GLS ELEV)

The “Used On” text was revised to support Heliport Section revised to support GLS elevation.
Records.
Character type was changed to Alpha/Numeric.
5.44 Localizer/MLS/GLS Identifier (LOC, MLS, GLS
IDENT) 5.75 From/To-Airport/Fix

Section revised to support GLS. Section revised to support Alternate Destination Record.

5.45 Localizer Frequency (FREQ) 5.77 VIA Code

The “Used On” text was revised to included Airport and The note was revised to refer to Figure 5-14.
Heliport.
5.80 ILS Category (CAT)
5.46 Runway Identifier (RUNWAY ID)
Section revised to support GLS.
The “Used On” text was revised to support Heliport
Records. 5.81 ATC Indicator (ATC)

5.47 Localizer Bearing (LOC BRG) The “Used On” text was revised to support Airport and
Heliport Records.
Character type was changed to Alpha/Numeric.
5.101 Communication Type (COMM TYPE)
5.52 Glide Slope Angle (GS ANGLE) Minimum
Elevation Angle (MIN ELEV ANGLE) Terminal (TML) was added to the Source/Content.

Section revised to support GLS. Airport Comm only column changed to Airport Heliport
Comm only.
5.53 Transition Altitude/Level (TRANS
ALTITUDE/LEVEL. 5.103 Communication Frequency (COMM FREQ)

Section revised to support Heliport records. Source/Content revised to support UHF frequencies.

5.54 Longest Runway (LONGEST RWY) 5.106 Service Indicator (SERV IND)

The Source/Content paragraph was modified to further The column content table header for Enroute
define the longest runway. Communication Record was changed to 57, 58, and 59.
5.57 Runway Length (RUNWAY LENGTH) 5.114 Duplicate Indicator (DUP IND)

The Source/Content paragraph was modified further to Note 1, editorial correction were made.
define runway length.
SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 10

5.115 Directional Restriction 5.191 Triad Station (TRIAD STA)

This section is revised to support Preferred Route Records Deleted by Supplement 14.

5.130 Multiple Code (MULTI CD) 5.192 Group Repetition Interval (GRI)

The “Used On” text was revised to support Airport and Deleted by Supplement 14.
Heliport Records.
5.193 Additional Secondary Phase Factor (ASF)
5.131 Time Code (TIME CD)
Deleted by Supplement 14.
The descriptive paragraph revised for clarity.
5.196 Name Format Indicator (NAME IND)
Primary and Continuation Records were added when used
on Enroute and Airways. D, I, and N were added to the table.

5.134 Cruise Table Identifier (CRSE TBL IDENT) Notes 1 and 2 were added.

The “Used On” text was revised reflect Flight Planning The “Used On” text was revised to support Airport and
and Arrival/Departure Data records. Heliport Records.

5.138 Time Indicator (TIME IND) 5.197 Datum Code (DATUM)

Greenwich Mean Time was changed to Universal The “Used On” text was revised to support Terminal
Coordinated Time. NDB and GLS Transmitted Records.

5.144 Center Fix (CENTER FIX) 5.211 Required Navigation Performance (RNP)

This section revised to support Heliport records. Text was rewritten to include ICAO Annex 15 and/or
State published rules.
5.145 Radius Limit
The Following Sections Have Been Added By
The “Used On” text was revised to support Airport and Supplement 14:
Heliport Records.
5.222 GPS/FMS Indicator (GPS/FMS IND)
5.146 Sector Bearing (SEC BRG)
5.223 Operations Type (OPS TYPE)
The “Used On” text was revised to support Airport and
Heliport Records. 5.224 Approach Indicator (APP IND)

5.147 Sector Altitude (SEC ALT) 5.225 Ellipsoidal Height

The “Used On” text was revised to support Airport and 5.226 Glide Path Angle (GPA)
Heliport Records.
5.227 Orthometric Height (ORTH HGT)
5.161 Restriction Altitude (RSTR ALT)
5.228 Unit of Height (UNIT)
The title of this section was changed.
5.229 Path Point Data CRC (CRC)
5.165 Magnetic/True Indicator (M/T IND)
5.230 Procedure Type (PROC TYPE)
The “Used On” text was revised to support Heliport
Records. 5.231 Along Track Distance (ATD)

5.170 Decision Height (DH) 5.232 Number of Engines Restriction (NOE)

The “Used On” text was revised to support Airport and 5.233 Turboprop/Jet Indicator (TURBO)
Heliport Records.
5.234 RNAV Flag (RNAV)
5.171 Minimum Descent Height (MDH)
5.235 ATC Weight Category (ATC WC)
The “Used On” text was revised to support Airport and
Heliport Records. 5.236 ATC Identifier (ATC ID)

5.180 PAD Identifier (PAD IDENT) 5.237 Procedure Description (PROC DESC)

Section revised to support Heliport Records. 5.238 Leg Type Code (LTC)

5.239 Reporting Code (RPT)

 SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 11

5.240 Altitude (ALT) 7.3.4 Navaid Waypoint

5.241 Fix Related Transition Code (FRT Code) This section was added.

5.242 Procedure Category (PROC CAT) 7.3.5 Airport Waypoint

5.243 GLS Station Identifier This section was added.

5.244 GLS Channel ATTACHMENT 5 PATH AND TERMINATOR

5.245 Service Volume Radius Descriptive introductory paragraph revised to clarify the
meaning for “must” and “will” and to support rotor-wing
5.246 TDMA Slot procedures.

5.247 Station Type 1.2 Beginning and Ending Leg Types

5.248 Station Elevation WGS84 A Note was added to support rotor-wing procedures.

5.249 Longest Runway Surface Code (LRSC) 1.3 Leg Sequencing

5.250 Alternate Record Type (ART) Note “&” was expanded to include FC/DF sequences.

5.251 Distance To Alternate (DTA) 1.4 Leg Type Descriptions

5.252 Alternate Type (ALT TYPE) Illustrated Leg Types were revised.

5.253 Primary and Additional Alternate Identifier (ALT 1.5 Leg Data fields
IDENT)
Legend “B” was added to leg Data Fields.
6.10 CRC Calculations
2.0 CODING RULES APPLICABLE TO ALL
6.10.1 Precision Approach Path Point Cyclic PROCEDURE TYPES
Redundancy Check (CRC) Overview
This section was revised to clarify the meaning for “must”
6.10.2 Generator Polynomials: and “will” as defined in the introduction of Attachment 5.

6.10.3 32 Bit CRC Calculation Rule 2.3 was expanded to code Termination Altitude to
include column 95.
6.11 Application of CRC for Integrity Protection of
Straight & Advanced Landing Approach 3.0 PATH AND TERMINATION RELATED RULES
Operations VALID FOR ALL PROCEDURES TYPES

6.11.2 RNAV GPS/GLS Approach Procedure Path Point This section was revised to clarify the meaning for “must”
Data Field Bits and “will” as defined in the introduction of Attachment 5.

6.11.3 CRC - Generator Polynomial, G(x) Rule 3.1 the following sentence was added:

7.2.2.1 Navaid Waypoint For distance terminations, the overfly parameters must be
set, otherwise the combination is not permitted.
7.2.2.2 Airport Waypoint
4.0 STANDARD INSTRUMENT DEPARTURE
7.2.2.3 Named RNAV Waypoint, Intersections, and (SID)CODING RULES
Reporting Points
This section was revised to clarify the meaning for “must”
Phonetic Letter Subsection, “County” was changed to and “will” as defined in the introduction of Attachment 5.
“Country.”
Text revised to support rotor-wing procedures.
7.2.5 Reporting Positions Defined by Coordinates
5.0 STANDARD TERMINAL ARRIVAL ROUTE
The section was modified to provide a comprehensive (STAR) CODING RULES
definition of reporting positions by coordinates.
This section was revised to clarify the meaning for “must”
7.2.6 Terminal Waypoint and “will” as defined in the introduction of Attachment 5.

Subsection “A” and “B” was expanded to provide a 6.0 APPROACH PROCEDURE RULES VALID FOR
comprehensive definition of waypoint identifiers. ALL PROCEDURE TYPES
Subsection “E” and “F” were added.
SUPPLEMENT 14 TO ARINC SPECIFICATION 424 - Page 12

This section was revised to clarify the meaning for “must”

and “will” as defined in the introduction of Attachment 5.

This section was modified to replace “runway” with

“runway or helipad” and replace the term “threshold”
with “threshold or alighting point.”

Rule 6.9, Loran Procedure Coding and Subsection were

deleted by Supplement 14.

This section was revised to add rules for GLS Approach

Procedure Coding.

The entire section was modified to support Step-down

fixes for approach procedures.

7.0 PRECISION APPROACH PROCEDURES

CODING

This section was added.

8.0 NON-PRECISION APPROACH PROCEDURE

CODING

This section was added.

9.0 MISSED APPROACH PROCEDURE RULES
VALID FOR ALL PROCEDURE

Previously Section 7, prior to Supplement 14.

This section was revised to clarify the meaning for “must”

and “will” as defined in the introduction of Attachment 5.

This section was modified to replace “runway” with

“runway or helipad” and replace the term “threshold”
with “threshold or alighting point.”
 AERONAUTICAL RADIO, INC.
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 15
TO
ARINC SPECIFICATION 424
NAVIGATION SYSTEM DATA BASE

Published: February 11, 2000

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: January 12, 2000

SUPPLEMENT 15 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT ATTACHMENT 5 PATH AND TERMINATOR

This Supplement introduces revisions and additions to

the body and Attachments of ARINC Specification 424. 7.0 PRECISION APPROACH PROCEDURES
These changes include revisions to Final Approach Fix CODING
record and additions to the Missed Approach
Procedures. Rule 7.1.7 was modified to describe that the vertical
angle must be coded in both the Final Approach Fix
B. ORGANIZATION OF THIS DOCUMENT (FAF) and the fix which carries the Missed Approach
Point (MAP) coding.
The material in Supplement 15 is integrated into
ARINC Specification 424 to form an updated version Rule 7.1.8 was added by this Supplement.
of the standard.
9.0 MISSED APPROACH PROCEDURE RULES
The changes introduced by Supplement 15 have been VALID FOR ALL PROCEDURE
identified using change bars and are labeled in the
margin by a “c-15” indicator. The following text was added to Rule 9.0:

C. CHANGES TO SPECIFICATION 424 Identification of multiple missed approach procedures,

INTRODUCED BY THIS SUPPLEMENT when coded, will be accomplished through the coding
of a specific Transition Identifier which closely aligns
This section presents a complete tabulation of the with published information.
changes and additions to the Specification introduced
by this Supplement. Each change or addition is defined Rule 9.3.1.4 was added by this Supplement.
by the section number and the title that will be
employed. In each case a brief description of the Rule 9.3.1.5 was previously 9.3.1.4, additionally 9.3.1.5
change or addition is included. was modified to clarify the first leg of the missed
approach.
1.4 Reference Documentation

The reference to applicable ARINC Standards was

updated.

5.7 Route Type (RT TYPE)

The Airport Approach (PF) and Heliport Approach
(HF) Records were revised to included Missed
Approach, field identifier “Z.”

Note 3 were revised to support Qualifiers “P” and “S.”

5.11 Transition Identifier (TRANS IDENT)

The Transition Identifier Filed Content was revised to

included Missed Approach.

Note 4 was added for Missed Approach Transition.

5.29 Altitude Description (ALT DESC)

Identifiers “G” and “H” were revised for clarity.

The following text was added to this section:

The “V” content will only appear in Approach Route

Coding and only for those fixes that are stepdown fixes
in the vertical path of the procedure.

5.30 Altitude/Minimum Altitude

The second paragraph of the Source/Content was

revised to include the altitude field identifiers.

5.70 Vertical Angle (VERT ANGLE)

The Definition/Description paragraph was revised to

clarify the Vertical Angle field.
 AERONAUTICAL RADIO, INC
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 16

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: August 30, 2002

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: April 8, 2002

SUPPLEMENT 16 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 3.2.4.5 Airport Standard Terminal Arrival

Routes (STARs) Section (P), Subsection (E)
This supplement introduces revisions and additions to
the body and Attachments of ARINC Specification Section title was revised.
424. These changes improve the operational utility of
the navigation data base 3.3.4 Heliport Terminal Waypoints Section (H),
Subsection (C)
B. ORGANIZATION OF THIS DOCUMENT
The section was revised to include VFR Waypoints.
This document, printed on goldenrod paper, contains
descriptions of changes introduced into ARINC 4.1.2.1 VHF NAVAID Primary Records
Specification 424 by this supplement. The material in
Supplement 16 is integrated into ARINC Specification DME Longitude was revised to columns 65 thru 74.
424 to form an updated version of the standard.
4.1.4 Waypoint Record (EA) or (PC)
Historically, the changes introduced by each
supplement are annotated by using a change bar and The section was revised to include VFR Waypoints.
labeling in the margin with a symbol associated with
the supplement number. In preparing this supplement 4.1.4.1 Waypoint Primary Records
for the latest adoption, Supplement 16, the practicality
of identifying all past changes in this manner was Section title was revised.
determined to be impractical.
4.1.5.1 Holding Pattern Primary Records
Therefore, this supplement will only indicate the latest
changes by use of change bars without numeration. The RNP and ARC radius fields were added (column 63
thru 71).
C. CHANGES TO SPECIFICATION 424
INTRODUCED BY THIS SUPPLEMENT The Notes field (columns 99 thru 123) was changed to
Name.
This section presents a complete tabulation of the
changes and additions to the Specification introduced 4.1.6.1 Enroute Airways Primary Records
by this Supplement. Each change or addition is defined
by the section number and the title that will be Columns 99 thru 101 were revised to Fixed Radius
employed. In each case a brief description of the Transitions Indicator. Section 5.254 was added to support
change or addition is included. Fixed Radius Transition Indicators in the ER Airway file.

1.2 Data Format Standardization Philosophy 4.1.8.1 Airport Gate Primary Record

The second paragraph was revised for clarity. The Notes field was changed to Name, Section 5.60.

2.2 Special Navigation Terms 4.1.9.3 Airport SID/STAR/Approach Flight Planning

Continuation Records
Editorial corrections were made with no change of
intent. Columns 75 thru 78 was revised to Leg Distance Section
5.260.
2.3 Precision RNAV Terms
4.1.12.1 Company Route Primary Records
The Landing Threshold Point/Fictitious Threshold
Point (LTP/FTP), Flight Path Control Point, Flight Path Section title was revised.
Alignment Point, Glide Path Angle, and Final
Approach Segment (FAS) CRC were revised to support 4.1.20.1 Airport MSA
the Path Point concept for precision GNSS Approach
Procedures. Multiple radius fields were added to this record.

3.2.3.1 Enroute Waypoint Section (E), Subsection (A) 4.1.21.1 Enroute Airways Restriction Altitude Exclusion
Primary Records
The section was revised to include VFR Waypoints.
Column 123 was changed from blank to Block Indicator.
3.2.4.3 Airport Terminal Waypoints Section (P)
Subsection (C) Section title was revised.

The section was revised to include VFR Waypoints 4.1.21.2 Altitude Exclusion Continuation Records
excluding the landing threshold as a fix (waypoint).
Column 123 was changed from blank to Block Indicator.
3.2.4.4 Airport Standard Instrument Departures
SIDs) Section (P), Subsection (D) Section title was revised.

Section title was revised.

 SUPPLEMENT 16 TO ARINC SPECIFICATION 424 – Page 3

4.1.21A.1 Enroute Airways Restriction Note 4.2.2.3 Heliport Terminal Waypoint Flight Planning
Restriction Primary Records Continuation Records

Section title was revised. Section title was revised.

4.1.21A.2 Enroute Airways Restriction Note 4.2.2.4 Heliport Terminal Waypoint Flight Planning
Restriction Continuation Records Continuation Records

Section title was revised. Section title was revised.

4.1.21B.1 Enroute Airways Restriction Seasonal Closure 4.2.4.1 Heliport MSA Primary Records
Primary Records
Multiple radius fields were added to this record.
Section title was revised.
Section title was revised.
4.1.21C.1 Enroute Airways Restriction Cruising Table
Replacement Primary Records 4.2.4.2 Heliport MSA Continuation Records
Section title was revised. Section title was revised.
4.1.21C.2 Enroute Airways Restriction Cruising 5.7 Route Type (RT TYPE)
Table Replacement Continuation Records
Section title was revised. Deleted the Note 2 from Route Type “J.”

4.1.27.1 Flight Planning Primary Record Deleted Route Type E.

Section title was revised. The Qualifier columns were separated from the Route Type
Description into a separate table to aid in clarity.
4.1.27.2 Flight Planning Continuation Records
Added Qualifiers Field 1 codes E, F, G, J, R, and V.
Section title was revised
Added Qualifiers Field 2 codes A, B, and E.
4.1.27.3 Flight Planning Continuation Records
Primary and Secondary Missed Approach codes were
Section title was revised. changed form Qualifier 1 P and S to Qualifier 2 A and B
respectively.
4.1.28.1 Path Point Primary Record
Note 1 was revised for clarity.
The Path Point Record was revised from columns 27
through 115 to support the Path Point concept for Note 6 was added.
precision GNSS Approach Procedures.
The Approach examples were revised.
The Note was revised to remove obsolete text and to
support the Path Point Record description. 5.10 Approach Route Identifier

4.1.29.1 GLS Primary Records Converted the text information into a table to make the
information more readable.
Section title was revised.
5.17 Waypoint Description Code (DESC CODE)
4.1.30.1 Alternate Primary Records
Note 6 was revised for clarification, no change of intent.
Section title was revised.
5.18 Boundary Code (BDY CODE)
4.2.2 Heliport Terminal Waypoint Records(HC)
The asterisk Note was added to refer to Figure 5-2.
The section was revised to include VFR Waypoints.
5.23 Recommended NAVAID (RECD NAV)
4.2.2.1 Heliport Terminal Waypoint Primary Records
The Procedure Use Figure, 5-7 was updated to be consistent
Section title was revised. with Attachment 5, Leg Data Fields.

4.2.2.2 Heliport Terminal Waypoint Continuation 5.29 Altitude Description (ALT DESC)
Records
Modified to allow coding of both minimum and VNAV
Section title was revised. path altitudes from government source or as calculated by
the data supplier.
Note was added for Field Content V.
SUPPLEMENT 16 TO ARINC SPECIFICATION 424 – Page 4

5.30 Altitude/Minimum Altitude 5.144 Center Fix (CENTER FIX)

The third paragraph of the Definition/Description was The Source/Content paragraph was revised to support
modified to reflect the revised Altitude Description Airport Reference Point for MSA Center Fix.
Code V.
5.146 Sector Bearing (SEC BRG)
5.35 NAVAID Class (CLASS)
This section was revised to support beginning and ending
The Navaid Class tables were revised for clarity. Notes bearing as well as multiple radii fields.
6 and 7 were deleted as they clarified in the table.
5.180 Pad Identifier (PAD IDENT)
Code “U” was changed to Undefined from
Unrestricted. The character length was changed to 5 characters max.

5.42 Waypoint Type (TYPE) 5.200 Remote Facility (REM FAC)

VFR Waypoint was added to both the Enroute and The text was revised to support that Remote Facility could
Terminal Waypoint tables. be a navaid through which the Communication Service is
transmitted, using the navaid frequency, or the Remote
Note 4 was added to support VFR Waypoints. could be an airport that the Communication Service is
transmitted from on unique frequencies.
5.60 Name (NAME)
5.204 ARC Radius (ARC RAD)
The section title and text were revised to more
accurately reflect the implementation of the record. The definition/description paragraph and Used On
paragraph were revised to support holding patterns for RNP
5.70 Vertical Angle (VERT ANGLE) Holding.
The text was modified to allow indicating published 5.211 Required Navigation Performance (RNP)
VNAV Angle where appropriate.
The entire section was revised to support RNP and
5.80 ILS/MLS/GLS Category examples were added to Attachments 4 and 5 to support
RNP.
Section title was revised to include GLS
5.223 Operation Types (OPS TYPE)
5.82 Waypoint Usage
This section was revised to support the Path Point concept
The term Airway was removed from the text and table. for precision GNSS Approach Procedures.

5.101 Communications Type (COMM TYPE) 5.224 Route Indicator (RTE IND)

Enroute Comm Only (EFS) and Ground Comm Outlet The title and text was revised to support the Path Point
(GCO) were added as communication types. concept for precision GNSS Approach Procedures.

5.103 Communication Frequency (COMM FREQ) 5.225 Ellipsoid Height

The text was modified to explain that it contains either The text was revised to remove the reference to feet as the
a frequency or channel to support 8.33 kHz VHF path point concept is only in meters.
Communication.
5.226 Glide Path Angle (GPA)
5.104 Frequency Units (FREQ UNIT)
Text referring to the illustration on Precision Approach Path
Text was added to include a code that indicates Points was added.
“channel” rather than frequency.
Figure 5-15 on Precision Approach Path Points was added
5.106 Service Indicator (SERV IND) by this Supplement.

The service one indicator of “E” for EFAS was deleted. 5.227 Orthometric Height (ORTH HGT)

5.114 Duplicate Indicator (DUP IND) The text was revised to remove the reference to feet as the
path point concept is only in meters.
New Duplicate Code of 8 was added for “All
Altitudes” under multiple holding patterns. 5.228 Course Width at Threshold (CRS WDTH)

5.118 Boundary Via (BDRY VIA) The title and text was revised to support the Path Point
concept for precision GNSS Approach Procedures.
The “arc by edge” option was deleted.
 SUPPLEMENT 16 TO ARINC SPECIFICATION 424 – Page 5

5.229 Final Approach Segment data CRC Remainder 6.7.5 End-of-Volume Trailer Label (EOV)
(FAS CRC)
The label format was updated to 132 bit character format.
The title and text was revised to support the Path Point
concept for precision GNSS Approach Procedures. 6.10.2 Generator Polynomials

5.254 Fixed Radius Transitions Indicator (FIXED The CRC–32Q polynomial was revised to correlate with
RAD IND) Section 6.11.3.

This Section 5.254 was added to support constant 7.3.6 VFR Waypoints
Fixed Radius Transition Indicators in the ER Airway
file. This section was added to support the inclusion of VFR
Waypoints.
5.255 SBAS Service Provider Identifier (SBAS ID)
ATTACHMENT 2 LOCAL HORIZONTAL REFERENCE
This section was added to support the Path Point DATUM NAME, DATUM CODE, AND ELLIPSOID
concept for precision GNSS Approach Procedures. LIST

5.256 Reference Path Data Selector (REF PDS) The Local Horizontal Reference Datum code and Ellipsoid
list was updated.
This section was added to support the Path Point
concept for precision GNSS Approach Procedures. ATTACHMENT 4 AIRWAY MINIMUM ALTITUDE
AND REQUIRED NAVIGATION PERFORMANCE
5.257 Reference Path Identifier (REF ID) (RNP)

This section was added to support the Path Point Coding Examples for RNP were added.
concept for precision GNSS Approach Procedures.
ATTACHMENT 5 PATH AND TERMINATOR
5.258 Approach Performance Designator (APD)
Introductory Section
This section was added to support the Path Point
concept for precision GNSS Approach Procedures. A commentary was added for XA legs.

5.259 Length Offset (OFFSET) 1. The title was changed to Distance to Calculation from
Speed.
This section was added to support the Path Point
concept for precision GNSS Approach Procedures. 2. The definition of Bank Angle was revised to state the
ground speed of 250 knots.
5.260 Terminal Procedure Flight Planning Leg
Distance (LEG DIST) 4. The title was changed to Outbound Leg from Teardrop
Procedures.
This section was added to define the segment distance
along the track. 5. The Intercept Angle, items “A” and “C” were revised to
support approach transitions to intercept the localizer
6.7 Labels approach path.
The label format was updated to 132 bit character 1.2 Beginning and Ending Leg Types
format.
A “TF” leg was added to the Beginning Leg column for
6.7.1 Volume Header Label (VOL) Missed Approach.

The label format was updated to 132 bit character A “IF” leg was added to the Beginning Leg column for SID
format. Runway Transition and SID with a note that it be proceeded
by the runway as an “IF.”
6.7.2 Header 1 Label (HDR 1)
RF path terminators were added to each Ending Leg
The label format was updated to 132 bit character column accept Approach Transition.
format.
The Note, “When Approach Transition is for GPS
6.7.3 Header 2 Label (HDR 2) Approach Procedure” was deleted.

The label format was updated to 132 bit character 1.3 Leg Sequencing
format.
An ampersand was added to the square for “TF/DF” and
6.7.4 End-of-File Trailer Label (EOF) the corresponding Note was revised to include an “TF/DF”
sequence.
The label format was updated to 132 bit character
format.
SUPPLEMENT 16 TO ARINC SPECIFICATION 424 – Page 6

The # symbol and the corresponding Note were 7.0 Precision Approach Coding
deleted.
The following sentence was added to Rule 7.1.7:
2.0 Coding Rules Applicable to All Procedures
“If the altitude 1 and 2 constraints for the FAF are “at” (G)
Rule 2.9 was added to support RNP. and equal to the FACF altitude with an altitude description
of “I”, the vertical angel is omitted from the FAF record.”
5.0 Standard Terminal Arrival Route(STAR) Coding
Rules Rule 7.1.8, the Notes were revised for clarity, no change of
intent.
The following text replaced wording after Approach
Transition in Rule 5.7 line 2: 8.0 Non-Precision Approach Procedure Coding

“both the Arrival Route and the Approach Transition Rule 8.1.1 was revised in correlation with Section 5.29.
will be coded in their entirety in accordance with
source documentation.” The first sentence of Rule 8.3.2 was revised for
clarification.
6.0 Approach Procedure Rules Valid For All
Procedure Types Rule 8.3.5.3 the first sentence was revised as follows:

Rule 6.2.1 was revised in correlation with Section 5.29. “The recommended navaid is not required unless specified
by the state, or if required by leg type. The recommended
Rule 6.2.5 the text was added by this Supplement. Rule navaid, must be prior procedure reference VORDME or
6.2.5.2 was previously Rule 6.2.5. VORTAC.”

Rule 6.2.5.1 was added by this Supplement. The first sentence of rule 8.6 was revised as follows:

Rule 6.2.5.2 was previously Rule 6.2.5 before Rule “Procedures which are Circle-To-Land may be included in
6.2.5.1 and 6.2.5.2 were added. the data base.”

Rule 6.2.5.3 was added to support VNAV coding of Rule 8.6.4 was revised to include the Final End Point.
approach procedures where the MAP is not at the LTP.
9.0 Missed Approach Procedures Rules Valid For All
The following text was deleted from Rule 6.2.9.3: Procedures Types

“in cases where the final approach course was designed Rule 9.3.1.4 “if not specified by source” was added to end
to cross over the runway threshold.” of the first sentence.

The following clause was deleted from Rule 6.2.9.4:

“or the published Missed Approach Point is abeam the

runway threshold.”

Rule 6.2.10.1 was revised in correlation with Section

5.29.

The first sentence of Rule 6.2.10.2.d was revised for

clarification.

Rule 6.2.10.3 was revised in correlation with Section

5.29.
Rule 6.3.4.was deleted by Supplement 16.

Rule 6.3.6.4, the following text was added: “angles

between 10 and 90 degrees may be coded as required.”

Rule 6.6.3.2 was revised to recommend the VORDME

RNAV approaches will be the procedure VORDME
 AERONAUTICAL RADIO, INC
2551 Riva Road
Annapolis, Maryland 21401-7465 USA

SUPPLEMENT 17

TO

ARINC SPECIFICATION 424

NAVIGATION SYSTEM DATA BASE

Published: August 31, 2004

Prepared by the Airlines Electronic Engineering Committee

Adopted by the Airlines Electronic Engineering Committee: May 5, 2004

SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 2

A. PURPOSE OF THIS SUPPLEMENT 2.1 Data Processing Terms

This Supplement introduces revisions and additions to The term Alpha was revised to describe any letter of the
the body and Attachments of ARINC Specification alphabet (A through Z); any punctuation; or any printable
424. These changes remove obsolete text, allow using character, other than a numeric, including space.
Airport Records as the “TO FIX” in Enroute Airways
and improve the operational utility of the navigation The term Cassette was deleted.
data base for RNP Procedures.
2.2 Special Navigation Terms
B. ORGANIZATION OF THIS DOCUMENT
The Mandatory Hold definition was added.
This document, printed on goldenrod paper, contains
descriptions of changes introduced into ARINC 3.1 User File Organization
Specification 424 by this Supplement. The material in
Supplement 17 is integrated into ARINC Specification The obsolete terms Tapes and Cassettes were removed and
424 to form an updated version of the standard. revised text was added.

The changes introduced by Supplement 17 have been 3.2.4.1 Airport Reference Points Section (P), Subsection
identified using change bars. (A)

This section was updated to specifically allow using Airport

C. CHANGES TO SPECIFICATION 424 Records as the “TO FIX” in Enroute Airways.
INTRODUCED BY THIS SUPPLEMENT
3.2.4.17 Airport Terminal Arrival Altitude Section (P),
This section presents a complete tabulation of the Subsection (K)
changes and additions to the Specification introduced
by this Supplement. Each change or addition is defined New section added to support Terminal Arrival Altitudes.
by the section number and the title that will be
employed. In each case a brief description of the 3.3.10 Heliport Terminal Arrival Area Section (H),
change or addition is included.
Subsection (K)

1.1 Purpose of this Document New section added to support Terminal Arrival Altitudes.

The obsolete terms Tapes and Cassettes were removed Figure 3-1 Data Sorting Necessary to Achieve Step 1 of
and new text was added. FDSU File Production Process

A statement was included that ARINC 424 is to be an The Figure title was revised to remove the outdated term
enabling document and enables database suppliers, tape.
avionics systems, and other users of the databases to
flight plan and fly procedures as prescribed by procedure 4.1.2.2 VHF NAVAID Continuation Records
designers.
Application Type field was added and the Application Note
1.2 Data Format Standardization Philosophy was deleted.

The obsolete terms Tapes and Cassettes were removed 4.1.2.5 VHF NAVAID Flight Planning Continuation
and revised text was added. Records

The first Commentary on clarifying the term Cassette A Note was added explaining that Flight Planning
was deleted. continuation records cannot have an Application Type
column.
1.3 Organization of the Document
4.1.2.6 VHF NAVAID Limitation Continuation Record
The obsolete terms Tapes and Cassettes were removed
and revised text was added. The Application Type field was added.
4.1.3.2 NDB NAVAID Continuation Records
1.3.1 Coverage of Helicopter Operation Needs
Application Type field was added and the Application Note
Editorial corrections were made. was deleted.

Figure 1-1 ARINC Specification 424 Information 4.1.3.5 NDB NAVAID Flight Planning Continuation
Presentation Records

The obsolete terms Tapes and Cassettes were removed A Note was added explaining that Flight Planning
and revised text was added. continuation records cannot have an Application Type
column.
 SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 3

4.1.4.2 Waypoint Continuation Records 4.1.9.4 Airport SID/STAR Flight Planning Continuation
Records
Application Type field was added and the Application
Note was deleted. A Note was added explaining that Flight Planning
continuation records cannot have an Application Type
4.1.4.4 Waypoint Flight Planning Continuation Records column.
A Note was added explaining that Flight Planning 4.1.10.1 Runway Primary Records
continuation records cannot have an Application Type
column. TCH Value Indicated filed was added to support Altitude
description in ILS coding.
4.1.5.2 Holding Pattern Continuation Records
4.1.10.2 Runway Continuation Records
Application Type field was added and the Application
Note was deleted. Application Type field was added and the Application Note
was deleted.
4.1.6.2 Enroute Airways Continuation Records
4.1.11.1 Airport and Heliport Localizer and Glide Slope
Application Type field was added and the Application
Note was deleted. A set of supporting facilities to contain Section, Subsection
ID, and ICAO identifier to support MLS DME was added.
4.1.6.4 Enroute Airways Flight Planning Continuation
Records 4.1.11.2 Airport and Heliport Localizer and Glide Slope
Continuation Records
A Note was added explaining that Flight Planning
continuation records cannot have an Application Type Application Type field was added and the Application Note
column. was deleted.
4.1.7 Airport Records (PA) 4.1.13.2 Airport and Heliport Localizer Continuation
Records
This section was updated to specifically allow using
Airport Records as the “TO FIX” in Enroute Airways. The Continuation Records was added to be consistent with
the philosophy of addressing a new industry standard for
4.1.7.2 Airport Continuation Records providing primary data beyond the 132 character Primary
record.
Application Type field was added and the Application
Note was deleted. 4.1.14.2 Airport Communications Continuation Records
4.1.7.4 Airport Flight Planning Continuation Records The Application Type field was added.
A Note was added explaining that Flight Planning 4.1.14.3 Airport Additional Continuation Records
continuation records cannot have an Application Type
column. The Application Type field was added.
4.1.8.2 Airport Gate Continuation Records 4.1.15.2 Airways Marker Continuation Records
Application Type field was added and the Application The Continuation Records was added to be consistent with
Note was deleted. the philosophy of addressing a new industry standard for
providing primary data beyond the 132 character Primary
4.1.9.1 Airport SID/STAR/Approach Primary Record record.
Speed Limit Description field was added, column 118. 4.1.17.2 FIR/UIR Continuation Records
A TAA Procedure Turn and TAA Sector identifier The Continuation Records was added to be consistent with
field was added. the philosophy of addressing a new industry standard for
providing primary data beyond the 132 character Primary
Note 3 was added to support columns 107-116. record.
4.1.9.2 Airport SID/STAR/Approach Continuation 4.1.18.2 Restrictive Airspace Continuation Record
Records
The Application Type field was added.
The Application Type field was added and the record
was modified to incorporate the procedure TCH and 4.1.18.3 Restrictive Airspace Flight Planning Continuation
the Altitude three requirements. Record
Note 1 was deleted on Application Type. The Application Type field was added.
SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 4

4.1.20.2 Airport MSA Continuation Records

The Application Type field was added.

4.1.28.1 Path Point Primary Record
4.1.22.1 Airport and Heliport MLS Primary Records
The record was updated to be congruent with RTCA DO-
A set of supporting facilities to contain Section, 229C.
Subsection ID, and ICAO identifier to support MLS
DME was added. 4.1.28.2 Path Point Continuation Records

4.1.21.2 Enroute Airways Restriction Altitude Exclusion New section added by this supplement.
Continuation Records
4.1.29.2 GLS Continuation Records
The Application Type field was added.
The Continuation Records was added to be consistent with
4.1.21A.2 Enroute Airways Restriction Note Restriction the philosophy of addressing a new industry standard for
Continuation Records providing primary data beyond the 132 character Primary
record.
The Application Type field was added.
4.1.31 Airport TAA (PK)
4.1.21C.2 Enroute Airways Restriction Cruising Table
Replacement Continuation Records New section added to support Terminal Arrival Altitudes.

The Application Type field was added. 4.1.31.1 Airport TAA Primary Records
4.1.22.2 Airport and Heliport MLS Continuation New section added to support Terminal Arrival Altitudes.
Records
4.1.31.2 Airport Terminal Arrival Area Continuation
The Application Type field was added. Records
4.1.23.2 Enroute Communications Continuation New Section added to support Terminal Arrival Altitudes.
Records
4.2.1.2 Heliport Continuation Records
The Application Type field was added.
The Application Type field was added.
4.1.23.3 Enroute Communications Continuation
Records 4.2.1.4 Heliport Flight Planning Continuation Records
The Application Type field was added. The Application Type field was added.
4.1.24.2 Preferred Route Continuation Records 4.2.2.2 Heliport Terminal Waypoint Continuation Records
The Application Type field was added. Application Type field was added and the Application Note
was deleted.
4.1.24.3 Preferred Route Continuation Record (ET)
4.2.3.1 Heliport SID/STAR/Approach Primary Records
The Application Type field was added.
Speed Limit Description field was added.
4.1.25.2 Controlled Airspace Continuation Records
A TAA Procedure Turn and TAA Sector identifier field
The Application Type field was added. was added.
4.1.26.2 Geographical Reference Table Continuation Note 2 added to support Columns 119-120.
Records
Note 2 added to support Columns 107-116.
The Continuation Records was added to be consistent
with the philosophy of addressing a new industry 4.2.3.2 Heliport SID/STAR/Approach Continuation
standard for providing primary data beyond the 132 Records
character Primary record.
Application Type field was added and the record was
4.1.27.1 Flight Planning Primary Records modified to incorporate the procedure TCH and the Altitude
three requirements.
Speed Limit Description field was added.
Note 1 was deleted on Application Type.
4.1.27.2 Flight Planning Continuation Records

The Application Type field was added.

 SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 5

4.2.3.4 Heliport SID/STAR/Approach Flight Planning Note 1 and 3 were revised to support the Qualifier Fields.
Continuation Records
Commentary on GLS was added.
A Note was added explaining that Flight Planning
continuation records cannot have an Application Type The Approach examples were revised for clarity.
column.
5.10 Approach Route Identifier (APPROACH IDENT)
4.2.4.2 Heliport MSA Continuation Records
This section was updated to support TAA.
Application Type field was added and the Application
Note was deleted. 5.12 Sequence Number (SEQ NR)

4.2.5.2 Heliport Communications Continuation Records This section was updated to support TAA.

Application Type field was added. 5.17 Waypoint Description Code (DESC CODE)

4.2.5.3 Heliport Communications Continuation Records This section was updated to specifically allow using Airport
Records as the “TO FIX” in Enroute Airways.
The Application Type field was added.
5.23 Recommended NAVAID (RECD NAV)
4.2.6.1 Heliport TAA Primary Records
This section was updated to include TACAN.
New section added to support Terminal Arrival
Altitudes. 5.29 Altitude Description (ALT DESC)

4.2.6.2 Heliport Terminal Arrival Area Continuation Text was added to address Altitude Description in ILS
coding for Altitude three.
Records
Field content X and Y was added along with a supporting
New section added to support Terminal Arrival Note.
Altitudes.
5.30 Altitude/Minimum Altitude
5.5 Subsection Code (SUB CODE)
Text was added to address Altitude Description in ILS
This section was updated to support TAA. coding for Altitude three.
5.6 Airport/Heliport Identifier (ARPT/HELI IDENT) 5.33 VOR/NDB Identifier (VOR IDENT/NDB IDENT)
This section was updated to specifically allow using Airport and Heliport Localizer, and Airport and Heliport
Airport Records as the “TO FIX” in Enroute Airways. MLS records were added to the Used On section.
Text was added to support TAA. 5.36 Latitude (LATITUDE)
5.7 Route Type (RT TYPE) Path Point Record was removed from the Used On text.
The “H” identifier of the Qualifier 2 Field and the 5.37 Longitude (LONGITUDE)
supporting Note 5 were deleted.
Path Point Record was removed from the Used On text.
The Airport Approach (PF) and Heliport Approach
(HF) Records – Route Type table was revised to 5.42 Waypoint Type (TYPE)
include the following new or revised Approach Route
Types:
New codes were added to column 28 to support the FAA
VORDME Approach High Altitude redesign.
GNSS Landing System (GLS) Approach
Non-Directional Beacon + DME (NDB+DME) 5.67 Threshold Crossing Height (TCH)
Approach
VOR Approach using VORDME/VORTAC The text was revised to clearly identify the data in the
Runway record and Commentary was added noting that the
The Airport Approach (PF) and Heliport (HF) Records single TCH value provided on the Runway Record may be
– Route Type table was revised to include the different from the Approach Continuation Record.
following new or revised Route Types:
5.70 Vertical Angle (VERT ANGLE)
GBAS Procedure
RNAV, Sensor Not Specified The vertical angle paragraph was revised to address the
SBAS Procedure Localizer Only Vertical Angle.
SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 6

5.72 Speed Limit (SPEED LIMIT) 5.225 Ellipsoidal Height

The Definition/Description and the Source/Content The resolution was changed to a tenth of a meter.
were revised to designate whether the speed limit
coded at the fix in a terminal procedure is mandatory, 5.227 Orthometric Height (ORTH HGT)
minimum or maximum.
The resolution was changed to a tenth of a meter.
5.91 Application Type (USER)
5.228 Course Width At Threshold (CRS WDTH)
User Application A, C, E, L, N, T, U, V, and Q were
added. The width was revised to meters and ends in a resolution of
0.25 meters, and when the procedure is a helicopter
5.101 Communication Type (COMM Type) alighting point, the value is 38 meters.
Automatic Surface Observing System (ASO) 5.244 GLS Channel
communication typed was added.
The section was revised to clearly identify Channel
Air to Air communication type was added. numbers for GBAS and SBAS.
Aerodrome Weather Information Services (AWIS) 5.259 Length Offset (OFFSET)
communication type was added.
The Length Offset value was revised meters.
Military Frequency communication type was added.
5.261 Speed Limit Description
Pilot Activated Lighting (PAL) communication type
was added along with a supporting Note. New section added to designate whether speed limit coded
at a fix in a terminal procedure is mandatory, minimum or
5.106 Service Indicator (SERV IND) maximum speed.
Air/Air service indicator was added. 5.262 Approach Type Identifier (ATI)
5.143 Grid MORA New section added to support the Path Point Record.
A Commentary was added that indicates some MORA 5.263 HAL
values are provided as a representation of government
source. New section added to support the Path Point Record.
5.146 Sector Bearing (SEC BRG) 5.264 VAL
This section was updated to support TAA. New section added to support the Path Point Record.
5.147 Sector Altitude (SEC ALT) 5.265 Path Point TCH
This section was updated to support TAA. New section added to support the Path Point Record.
5.149 Figure of Merit (MERIT) 5.266 TCH Units Indicator
Section was revised to allow a method to identify those New section added to support the Path Point Record.
TACANs that are part of the National Air Space (NAS)
and those that are not. 5.267 High Precision Latitude (HPLAT)
5.165 Magnetic/True Indicator (M/T IND) New section added to support the Path Point Record.
This section was updated to support TAA. 5.268 High Precision Longitude (HPLONG)
5.204 ARC Radius (ARC RAD) New section added to support the Path Point Record.
Text was added stating that the ARC Radius field is 5.269 Helicopter Procedure Course (HPC)
also used to specify the turn radius of RNP holding
patterns included in SID, STAR, and Approach Records New section added to support the Path Point Record.
as HA, HF, and HM legs.
5.270 TCH Value Indicator (TCHVI)
5.222 GPS/FMS Indicator (GPS/FMS IND)
The section was added to address Altitude Description in
Section was modified to update the flagging procedures ILS Coding to address “Altitude Three.
for WAAS.
 SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 7

5.271 Procedure Turn (PROC TURN) 6.7.2 Header 1 Label (HDR 1)

This section was added to support TAA. This section was deleted and replaced by Section 6.2.1 and
6.2.2.
5.272 TAA Sector Identifier
6.7.3 Header 2 Label (HDR 2)
This section was added to support TAA.
This section was deleted and replaced by Section 6.2.1 and
5.273 TAA IAF Waypoint 6.2.2.

This section was added to support TAA. 6.7.4 End-of-File Trailer Label (EOF)

5.274 TAA Sector Radius This section was deleted and replaced by Section 6.2.1 and
6.2.2.
This section was added to support TAA.
6.7.5 End-of-Volume Trailer Label (EOV)
Figure 5-7 Procedure Use
This section was deleted and replaced by Section 6.2.1 and
Figure was updated to support TACAN. 6.2.2.

6.1 General 6.8 Tape Marks

The section was revised to remove the outdated This section was deleted and replaced by Section 6.2.1 and
references to magnetic tape formats. 6.2.2.

6.2 Header Record 6.9 Summary of Tape Data Layout

Title and the section were revised to remove the This section was deleted and replaced by Section 6.2.1 and
obsolete references to magnetic tape formats. 6.2.2.

6.2.1 Header Record 1 6.9.1 One File, One Reel

New section added by this supplement. This section was deleted and replaced by Section 6.2.1 and
6.2.2.
6.2.2 Header Record 2
6.9.2 One File, Multiple Reels
New section added by this supplement.
This section was deleted and replaced by Section 6.2.1 and
6.3 Bit Density 6.2.2.

This section was deleted and replaced by Section 6.2.1 6.9.3 Multiple Files, One Reel
and 6.2.2.
This section was deleted and replaced by Section 6.2.1 and
6.4 Coding 6.2.2.

This section was deleted and replaced by Section 6.2.1 6.11 Application of CRC for Integrity Protection of
and 6.2.2. Straight & Advanced Landing Approach Operations

6.5 Parity Convention Text was added to refer RTCA DO-229C for Final
Approach Segment Data Block and CRC standards.
This section was deleted and replaced by Section 6.2.1
and 6.2.2. 6.11.1 Data Block Structure,M(x)

6.6 Reel-File Relationship This section was deleted when Section 6.11 was revised to
refer to RTCA DO-229C.
This section was deleted and replaced by Section 6.2.1
and 6.2.2. 6.11.2 RNAV-GPS/GLS Approach Procedure Path Point
Data Fields Bits
6.7 Labels
This section was deleted when Section 6.11 was revised to
This section was deleted and replaced by Section 6.2.1 refer to RTCA DO-229C.
and 6.2.2.
6.11.3 CRC – Generator Polynomial G(x)
6.7.1 Volume Header Label (VOL)
This section was deleted when Section 6.11 was revised to
This section was deleted and replaced by Section 6.2.1 refer to RTCA DO-229C.
and 6.2.2.
SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 8

ATTACHMENT 1 FLOW DIAGRAM Rule 4.3 and Rule 4.4 was revised in correlation with
Section 1.2, Beginning and Ending Leg Types to allow a
The obsolete terms Tapes and Cassettes were removed single VM leg for a SID.
and revised text was added.
6.0 APPROACH PROCEDURE RULES VALID FOR
The Notes were revised to remove obsolete text. ALL PROCEDURE TYPES
ATTACHMENT 5 PATH AND TERMINATOR The following text was added to Rule 6.2.3:

1.2 Beginning and Ending Leg Types “When a VORDME or VORTAC is coded as the
recommended Navaid in approach procedure coding, the
SID Runway Transition, removed flag Note 1 from FM Navaid will be within 40 NM of the fix in which it is coded.
and VM. GPS approach procedures do not include a recommended
Navaid. GLS approach procedures will reference the GLS
SID, Beginning Leg List, removed flag note 1 from FM facility. For specific rules on recommended Navaid for
and VM, and flag note 3 from VM. Ending Leg, added NDB + DME Approach Procedures, see Rule 6.8.1.4.b of
FM and VM. this Attachment.”

1.3 Leg Sequencing Rule 6.2.5 was revised to specify what approach procedure
coding will include a Final Approach Course Fix.
FA/IF leg combination was changed to a valid leg
combination. Rules 6.2.5.1, 6.2.5.2, 6.2.5.3, and 6.2.5.4 were revised to
support the FACF coding.
1.4 Leg Type Description
Rule 6.2.10.2.d was modified to require an altitude in the
Revised the text for HA, HF, and HM in the leg from FEP to MAP.
description block.
Rule 6.5.3.2 was revised to remove the reference to the
1.5 Leg Data Field overfly bit.

HA, HF, and HM leg in the “HLD” column was Rule 6.3.6.1 was revised to support FACF coding.
changed to invalid. AF, CF, DF, IF, RF, and TF
changed to optional. Rule 6.3.6.2 was revised to include TACAN

HA, HF, and HM legs in the TD field changed to Rule 6.3.6.3 was deleted.
required from optional.
Rule 6.3.6.3.4 was revised to state if the angles between 10
HA, HF, and HM in the Overfly column changed to and 90 degrees may be coded as required by source
optional, and TF leg was changed to “B.” documentation, provide the resulting intercept is within the
reception area of the localizer.
RF in the MAP field was changed to Optional.
Rule 6.3.6.5 and 6.4.2.1 were revised to include FACF.
AF, IF, RF, and TF field was changed to Optional.
Rule 6.5.3.2 was revised to remove obsolete text.
RF in the THETA field changed to I and Legend I was
added for inbound tangential track. The following text was added to Rule 6.6.1.2.b:

VD in the TM/DST field changed to DME Distance. “The final approach will include a FACF when one is
required by Rule 6.2.5.”
Legend T and I were added.
Rule 6.6.3.1 was revised to include missed approach point.
3.0 Path and Termination Related Rules Valid For
All Procedure Types The following text was added to Rule 6.6.3.3:

Rule 3.5 and 3.6 were revised to include RF. “RF legs may be used in the final approach segment of
RNAV approaches.”
Rule 3.14 was revised to exclude leg combination
IF/RF, RF/RF or Hx. Rule 6.7, 6.7.1, 6.7.1.1, and 6.7.1.2 were deleted and Rules
6.7.2, 6.7.2.1, and 6.7.2.2 were renumbered to 6.7, 6.7.1
4.0 STANDARD INSTRUMENT DEPARTURE and 6.7.2.
(SID) CODING R.ULES
The following text was added to Rule 6.7.2.2:
Rule 4.1 was revised so that RNAV Departure
Procedure requires an initial turn is excess of 15 “The final approach will include a FACF when one is
degrees unless certain conditions are met. required by Rule 6.2.5.”
 SUPPLEMENT 17 TO ARINC SPECIFICATION 424 – Page 9

Rule 6.8.1.1.was deleted as it is redundant with Rule Rule 9.5.2 was revised in its entirety that the reference
6.2.5.2. Navaid must be used as the Recommended Navaid when
required.
The following text was added to Rule 6.8.1.2:
Rule 9.5.2.2 was deleted.
“The final approach will include a FACF when one is
required by Rule 6.2.5.” Rule 9.5.2.4 was added to so that when the first leg if a
Missed Approach Procedure is coded as HA or HM leg the
Rule 6.8.1.3 was revised to include “or FACF when coding will also include a government source provided
coded.” altitude.

Rule 6.8.1.4 was revised to include FACF when coded.

7.0 Precision Approach Procedure Coding

Rule 7.4.3.2 was added for RF legs.

8.0 NON-PRECISION APPROACH PROCEDURE

CODING

Rule 8.1.1 was revised to refer to Rule 6.2.5.2.

Rule 8.1.2 was added to indicated that all must be
coded in the Missed Approach Point (MAP).

Rule 8.3.2 was revised to refer to Rule 6.2.5.

The following text was added to Rule 8.3.4.2:

“The final approach will include a FACF when one is

required by Rule 6.2.5.”

Rules 8.3.6, 8.3.6.1, 8.3.6.2, and 8.3.6.3 were deleted.

Rule 8.4.2 was deleted as 6.2.5.2 was revised and the
rule is now redundant.

The following text was added to Rule 8.4.3:

“The final approach will include a FACF when one is

required by Rule 6.2.5.”

Rule 8.7.1 was revised to support approach transition

can end in a leg to the FAF and that the FACF fix is
required only on Localizer based procedures and
optional when provided by source as FACF or IF.

Rule 8.9.1.1 was added to support TCH.

Rule 8.9.9 was added to support step-down fix coding.

Rule 8.10, 8.10.1, 8.10.2, 8.10.3, and the associated

VNAV Approach Coding examples 14, 15, A, B, C,
and C were added by this supplement.

9.0 Missed Approach Procedure Rules Valid For All

Procedure Types

Rules 9.3.1.2, 9.3.1.3, 9.3.1.4, and 9.3.1.5 were revised

in their entirety to clarify the coding of first leg of
Missed Approach coding.

Ruled 9.4, 9.4.1, 94.1.1, 9.4.1.2, 9.4.1.3, 9.4.1.4, and

9.4.1.5 were deleted.
 ARINC Standard – Errata Report

1. Document Title
ARINC Specification 474-17: Navigation System Data Base, Published: August 31, 2004

2. Reference
Page Number: Section Number: Date of Submission:

3. Error
(Reproduce the material in error, as it appears in the standard.)

4. Recommended Correction
(Reproduce the correction as it would appear in the corrected version of the material.)

5. Reason for Correction

(State why the correction is necessary.)

6. Submitter (Optional)
(Name, organization, contact information, e.g., phone, email address.)

Note: Items 2-5 may be repeated for additional errata. All recommendations will be evaluated by
the staff. Any substantive changes will require submission to the relevant subcommittee for
incorporation into a subsequent supplement.

Please return comments to fax +1 410-266-2047 or [email protected]

 ARINC Project Initiation/Modification
09/03/04

ARINC IA Project Initiation/Modification (APIM)

Guidelines for Submittal

1. ARINC Industry Activities Projects and Work Program

A project is established in order to accomplish a technical task approved by one or
more of the committees (AEEC, AMC, FSEMC) Projects generally but not
exclusively result in a new ARINC standard or modify an existing ARINC
standard. All projects are typically approved on a calendar year basis. Any
project extending beyond a single year will be reviewed annually before being re-
authorized. The work program of Industry Activities (IA) consists of all projects
authorized by AEEC, AMC, or FSEMC (The Committees) for the current
calendar year.
The Committees establish a project after consideration of an ARINC Project
Initiation/Modification (APIM) request. This document includes a template which
has provisions for all of the information required by The Committees to determine
the relative priority of the project in relation to the entire work program.
All recommendations to the committees to establish or reauthorize a project,
whether originated by an airline or from the industry, should be prepared using
the APIM template. Any field that cannot be filled in by the originator may be
left blank for subsequent action.

2. Normal APIM Evaluation Process

Initiation of an APIM

All proposed projects must be formally initiated by filling in the APIM template.
An APIM may be initiated by anyone in the airline community, e.g., airline,
vendor, committee staff.
Staff Support

All proposed APIMs will be processed by committee staff. Each proposal will be
numbered, logged, and evaluated for completeness. Proposals may be edited to
present a style consistent with the committee evaluation process. For example,
narrative sentences may be changed to bullet items, etc. When an APIM is
complete, it will be forwarded to the appropriate Committee for evaluation.
The committee staff will track all ongoing projects and prepare annual reports on
progress.
Committee Evaluation and Acceptance or Rejection

The annual work program for each Committee is normally established at its
annual meeting. Additional work tasks may be evaluated at other meetings held
during the year. Each committee (i.e., AMC, AEEC, FSEMC) has its own
schedule of annual and interim meetings.

07_APIM-VerJ.doc Page 1
 ARINC Project Initiation/Modification
09/03/04

The committee staff will endeavor to process APIMs and present them to the
appropriate Committee at its next available meeting. The Committee will then
evaluate the proposal. Evaluation criteria will include:
• Airline support – number and strength of airline support for the project,
including whether or not an airline chairman has been identified
• Issues – what technical, programmatic, or competitive issues are
addressed by the project, what problem will be solved
• Schedule – what regulatory, aircraft development or modification,
airline equipment upgrade, or other projected events drive the urgency
for this project
Accepted proposals will be assigned to a subcommittee for action with one of two
priorities:
• High Priority – technical solution needed as rapidly as possible
• Routine Priority – technical solution to proceed at a normal pace
Proposals may have designated coordination with other groups. This means that
the final work must be coordinated with the designated group(s) prior to submittal
for adoption consideration.
Proposals that are not accepted may be classified as follows:
• Deferred for later consideration - the project is not deemed of sufficient
urgency to be placed on the current calendar of activities but will be
reconsidered at a later date
• Deferred to a subcommittee for refinement – the subcommittee will be
requested to, for example, gain stronger airline support or resolve
architectural issues
• Rejected – the proposal is not seen as being appropriate, e.g., out of
scope of the committee

3. APIM Template
The following is an annotated outline for the APIM. Proposal initiators are
requested to fill in all fields as completely as possible, replacing the italicized
explanations in each section with information as available. Fields that cannot be
completed may be left blank. When using the Word file version of the following
template, update the header and footer to identify the project.

07_APIM-VerJ.doc Page 2
 ARINC Project Initiation/Modification
09/03/04

ARINC IA Project Initiation/Modification (APIM)

Name of proposed project APIM #: _____

Name for proposed project.
Suggested Subcommittee assignment
Identify an existing group that has the expertise to successfully complete the
project. If no such group is known to exist, a recommendation to form a new
group may be made.
Project Scope

Describe the scope of the project clearly and concisely. The scope should
describe “what” will be done, i.e., the technical boundaries of the project.
Example: “This project will standardize a protocol for the control of printers.
The protocol will be independent of the underlying data stream or page
description language but will be usable by all classes of printers.”
Project Benefit

Describe the purpose and benefit of the project. This section should describe
“why” the project should be done. Describe how the new standard will improve
competition among vendors, giving airlines freedom of choice. This section
provides justification for the allocation of both IA and airline resources.
Example: “Currently each class of printers implements its own proprietary
protocol for the transfer of a print job. In order to provide access to the cockpit
printer from several different avionics sources, a single protocol is needed. The
protocol will permit automatic determination of printer type and configuration to
provide for growth and product differentiation.”
Airlines supporting effort

Name, airline, and contact information for proposed chairman, lead airline, list
of airlines expressing interest in working on the project (supporting airlines), and
list of airlines expressing interest but unable to support (sponsoring airlines). It
is important for airline support to be gained prior to submittal. Other
organizations, such as airframe manufacturers, avionics vendors, etc. supporting
the effort should also be listed.
Issues to be worked

Describe the major issues to be addressed by the proposed ARINC standard.

Recommended Coordination with other groups
Draft documents may have impact on the work of groups other than the
originating group. The APIM writer or, subsequently, The Committee may
identify other groups which must be given the opportunity to review and comment
upon mature draft documents.

07_APIM-VerJ.doc Page 3
 ARINC Project Initiation/Modification
09/03/04

Projects/programs supported by work

If the timetable for this work is driven by a new airplane type, major avionics
overhaul, regulatory mandate, etc., that information should be placed in this
section. This information is a key factor in assessing the priority of this proposed
task against all other tasks competing for subcommittee meeting time and other
resources.
Timetable for projects/programs

Identify when the new ARINC standard is needed (month/year).

Documents to be produced and date of expected result

The name and number (if already assigned) of the proposed ARINC standard to
be either newly produced or modified.
Comments

Anything else deemed useful to the committees for prioritization of this work.
Meetings

The following table identifies the number of meetings and proposed meeting days
needed to produce the documents described above.
Activity Mtgs Mtg-Days
# of mtgs # of mtg days
Document a
# of mtgs # of mtg days
Document b

For IA staff use

Date Received___________ IA staff assigned: __________________________________
Potential impact: ____
(A. Safety B. Regulatory C. New aircraft/system D. Other)
Forward to committee(s) (AEEC, AMC, FSEMC): _________ Date Forward:___________
Committee resolution: ____
(0. Withdrawn 1. Authorized 2. Deferred 3. More detail needed 4. Rejected)
Assigned Priority: ____ Date of Resolution:___________________
A. – High (execute first) B. – Normal (may be deferred for A.)

Assigned to SC/WG ________________________________________

07_APIM-VerJ.doc Page 4