8260.19C CHG 3 7/14/03 

Appendix 5 

Page 4 

Figure A5-2 
7/14/03 8260.19C CHG 3 

 Appendix 5 

 Page 5 

Figure A5-3 
8260.19C CHG 3 7/14/03 

Appendix 5 

Page 6 

Figure A5-4 
7/14/03 8260.19C CHG 3 

 Appendix 5 

 Page 7 

Figure A5-5 
8260.19C CHG 3 7/14/03 

Appendix 5 

Page 8 

Figure A5-6
7/14/03 8260.19C CHG 3 

 Appendix 6 

 Page 1 (and 2) 

APPENDIX 6. RADAR - STANDARD 

INSTRUMENT APPROACH PROCEDURE, 

FAA FORM 8260-4 
7/14/03 8260.19C CHG 3 

 Appendix 6 

 Page 3 

Figure A6-1 
8260.19C CHG 3 7/14/03 

Appendix 6 

Page 4 

Figure A6-2 
7/14/03 8260.19C CHG 3 

 Appendix 7 

 Page 1 (and 2) 

APPENDIX 7. STANDARD 

INSTRUMENT APPROACH PROCEDURE, 

FAA FORM 8260-5 
7/14/03 8260.19C CHG 3 

 Appendix 7 

 Page 3 

Figure A7-1 
8260.19C CHG 3 7/14/03 

Appendix 7 

Page 4 

Figure A7-2 
7/14/03 8260.19C CHG 3 

 Appendix 7 

 Page 5 

Figure A7-3 
8260.19C CHG 3 7/14/03 

Appendix 7 

Page 6 

Figure A7-4 
7/14/03 8260.19C CHG 3 

 Appendix 8 

 Page 1 (and 2) 

 

APPENDIX 8. 

SPECIAL INSTRUMENT APPROACH PROCEDURE, 

FAA FORM 8260-7 
7/14/03 8260.19C CHG 3 

 Appendix 8 

 Page 3 

Appendix A8-1
8260.19C CHG 3 7/14/03 

Appendix 8 

Page 4 

Figure A8-2
7/14/03 8260.19C CHG 3 

 Appendix 8 

 Page 5 

Figure A8-3
8260.19C CHG 3 7/14/03 

Appendix 8 

Page 6 

Figure A8-4 
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 1 (and 2) 

APPENDIX 9. 

STANDARD INSTRUMENT APPROACH 

PROCEDURE DATA RECORD,

FAA FORM 8260-9
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 3 

Figure A9-1 
8260.19C CHG 3 7/14/03

Appendix 9 

Page 4 

Figure A9-2 
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 5 

Figure A9-3 
8260.19C CHG 3 7/14/03

Appendix 9 

Page 6 

Figure A9-4 
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 7 

Figure A9-5 
8260.19C CHG 3 7/14/03

Appendix 9 

Page 8 

Figure A9-6 
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 9 

Figure A9-7 
8260.19C CHG 3 7/14/03

Appendix 9 

Page 10 

Figure A9-8 
7/14/03 8260.19C CHG 3 

 Appendix 9 

 Page 11 

Figure A9-9 
8260.19C CHG 3 7/14/03

Appendix 9 

Page 12 

Figure A9-10 
7/14/03 8260.19C CHG 3 

 Appendix 10

 Page 1 (and 2) 

APPENDIX 10. 

STANDARD INSTRUMENT APPROACH PROCEDURE 

CONTINUATION SHEET, 

FAA Form 8260-10
7/14/03 8260.19C CHG 3 

 Appendix 10 

 Page 3 

Figure A10-1 
8260 19C CHG 3 7/14/03 

Appendix 10 

Page 4 

Figure A10-2 
7/14/03 8260.19C CHG 3 

 Appendix 11 

Page 1 (and 2) 

APPENDIX 11. 

FINAL APPROACH SEGMENT DATA BLOCK 

DATA REQUIREMENTS 
7/14/03 8260.19C CHG 3 

 Appendix 11 

Page 3 

APPENDIX 11. FINAL APPROACH SEGMENT (FAS) DATA BLOCK 

CYCLIC REDUNDANCY CHECK (CRC) REQUIREMENTS 

Content of the FAS Data Block. Each FAS data block contains 20 elements (fields) that include the 

CRC remainder. The specific order and coding of the fields must be followed rigorously to ensure 

avionics compatibility. Until the process for electronic transmittal of this data is developed by AVN, 

the following FAS Data Block information must be documented on FAA Form 8260-10, Continuation 

Sheet, especially prepared for that purpose (see figures A11-1 and 2). This form will comprise the 

protected data pending development of an internal CRC process, and will be forwarded to the charting 

agencies for further processing and CRC protection. 

1. Fields needed for the Final Approach Segment (FAS) Data Block record for approaches using 

WAAS (LPV minima) and are included in the CRC wrap: 

Data Field Field Size Data Type

Operation Type 2 characters Unsigned Integer 

SBAS Service Provider Identifier 2 characters Unsigned Integer 

Airport Identifier 4 characters Alphanumeric 

Runway 5 characters Alphanumeric 

Approach Performance Designator 1 character Unsigned Integer 

Route Indicator 1 character Alpha 

Reference Path Data Selector 2 characters Unsigned Integer 

Reference Path Identifier (Approach ID) 4 characters Alphanumeric 

LTP/FTP Latitude 11 characters Alphanumeric 

LTP/FTP Longitude 12 characters Alphanumeric 

LTP/FTP Ellipsoidal Height 6 characters Signed Integer 

FPAP Latitude 11 characters Alphanumeric 

FPAP Longitude 12 characters Alphanumeric 

Threshold Crossing Height (TCH) 7 characters Alphanumeric 

TCH Units Selector (meters or feet used) 1 character Feet or Meters 

Glidepath Angle (GPA) 4 characters Unsigned Integer 

Course Width at Threshold 5 characters Unsigned Integer 

Length Offset 4 characters Unsigned Integer 

Horizontal Alert Limit (HAL) 3 characters Numeric 

Vertical Alert Limit (VAL) 3 characters Numeric 

2. Fields needed for integrity monitoring, and calculated using binary representation of FAS Data 

Block (as described in RTCA/DO-229C, Minimum Operational Performance Standards for Global 

Positioning System/Wide Area Augmentation System Airborne Equipment and as amended by 

TSO-C146A). 

Data Field Field Size Data Type

Precision Approach Path Point 

Data CRC Remainder 8 characters Hexadecimal 
8260.19C CHG 3 7/14/03 

Appendix 11 

Page 4 

3. Fields not included in the FAS Data Block, but needed for the Precision Approach Path Point 

record, and which are not CRC wrapped. 

Data Field Field Size Data Type

ICAO Code 2 characters Alphanumeric 

LTP Orthometric Height 6 characters Signed Integer 

FPAP Orthometric Height 6 characters Signed Integer 

4. Explanation of data field entries (in the general order they appear in the FAS Data Block): 

 a. Operation Type. A number from 0 to 15 that indicates the type of the final approach 

segment. 

 

Example: 0 is coded for a straight-in approach procedure. (Codes for other procedures are 

reserved for future definition.) 

 b. SBAS Service Provider Identifier. A number from 0 to 15 that associates the approach 

procedure to a particular satellite based approach system service provider. For GBAS applications, 

this data is ignored. 

 

Example: 0 (WAAS) 

 c. Airport Identifier. The four-character ICAO location identifier assigned to an airport. 

Where there is a national airport identifier but no ICAO location identifier, the three- or 

four-character national identifier is used. Where only three characters are provided, the trailing space 

is to be left blank. 

 

Example: KDEN, YSSY, NZWN, FAEL, 3SL_, OH23 

d. Runway. Runways are identified by two characters “RW” followed by the runway number. 

The fifth character is used where needed to indicate a left (L), right (R), or center (C). Helicopters are 

indicated by HEL0 without a number (the runway number is 0 as used to calculate the CRC). 

Examples: RW26R, RW08L, RW18C, RW02, HEL0 

 

e. Approach Performance Designator. A number from 0 to 7 that identifies the type of 

approach. An “0” is used to identify an LPV approach procedure and a “1” indicates a Category I 

approach procedure. Other values are reserved for future use. 

 

Example: 0 

f. Route Indicator. A single alpha character (A through Z or blank, omitting I and O) used to 

differentiate between multiple final approach segments to the same runway or heliport. The first 

approach to a runway is labeled “Z.” Additional alpha characters are incrementally assigned. 

 

Example: Z, Y, X, etc. 

g. Reference Path Data Selector (RPDS). A number (0-48) that enables automatic tuning of a 

procedure by LAAS avionics. The number is related to the frequency of the VHF data broadcast and a 
7/14/03 8260.19C CHG 3 

 Appendix 11 

Page 5 

5-digit tuning identifier. The future ICAO SBAS SARPS will provide further information. Always 

"0" for WAAS operations. 

 

Example: 0 

h. Reference Path Identifier. A four-character identifier that is used to confirm selection of the 

correct approach procedure. This identifier is defined with a “W” signifying WAAS, followed by the 

runway number. The last character, beginning with the letter “A”, excluding the letters “C”, “L”, and 

“R”, will be used to define the first procedure, followed by a succeeding letter for each procedure to a 

particular runway. For example, an airport has three parallel runways and the left and right runways 

have both a straight-in procedure and an offset procedure; the center runway has a straight-in 

procedure only. The following (extreme) examples would be applicable: 

 

Example: W09A & W09B would define the 2 unique FAS data blocks to RWY 09L. 

 W09D would be used to define the FAS data block for RWY 09C. 

 W09E & W09F would be used to define the FAS data blocks for RWY 09R. 

NOTE: These suffixes do not have to be in any particular order so as to allow procedures to be 

added at a later time without changing existing FAS data blocks. 

i. Landing Threshold Point (LTP)/Fictitious Threshold Point (FTP) - Latitude. Represents 

the latitude of the threshold defined in WGS-84 coordinates and entered to the ten-thousandth of an 

arc second. The most significant bit is the sign bit: 0 = Positive (Northern Hemisphere); 1 = Negative 

(Southern Hemisphere). However, for documentation purposes, identify the Latitude as follows: 

 Example: 225436.2125N (11 characters) for 22°54'36.2125" N 

 j. Landing Threshold Point (LTP)/Fictitious Threshold Point (FTP) - Longitude. 

Represents the longitude of the threshold defined in WGS-84 coordinates and entered to the tenthousandth of an arc second. The most significant bit is the sign bit: 0 = Positive (Eastern 

Hemisphere); 1 = Negative (Western Hemisphere). However, for documentation purposes, identify 

the Latitude as follows: 

 Example: 1093247.8780E (12 characters) for 109°32'47.8780" E 

 

 k. LTP/FTP Height Above Ellipsoid (HAE). The height expressed in meters reference the 

WGS-84 ellipsoid, obtained from an official government source. This information is identified in the 

ASIS database as “Ellipsoid Elevation” and is in “feet” and must be converted to “meters.” The first 

character is a + or – and the resolution value is in tenths of a meter with the decimal point suppressed. 

 

 Example: +00356 (+35.6m), -00051(-5.1m), +01566 (+156.6m), -00022 (-2.2m) 

 l. Flight Path Alignment Point (FPAP) - Latitude. A point located on a geodesic line or an 

extension of a geodesic line calculated between the LTP and the designated center of the opposite 

runway-landing threshold. It is positioned at a distance from the LTP to support a prescribed 

procedure design angular splay and course width, as well as functionality associated with an aircraft. 

It is used in conjunction with the LTP to determine the lateral alignment of the vertical plane 

containing the path of the RNAV final approach segment. On shorter runways, the FPAP may be 

located off the departure end of the landing runway. The latitude of the runway FPAP is defined in 

WGS-84 coordinates and entered to the ten-thousandth of an arc second. The most significant bit is 
8260.19C CHG 3 7/14/03 

Appendix 11 

Page 6 

the sign bit: 0 = Positive (Northern Hemisphere); 1 = Negative (Southern Hemisphere). However, for 

documentation purposes, identify the Latitude as follows: 

 Example: 225436.2125N (11 characters) for 22°54'36.2125" N 

m. FPAP - Longitude. The longitude of the runway FPAP is defined in WGS-84 coordinates 

and entered to the ten-thousandth of an arc second. The most significant bit is the sign bit 0 = Positive 

(Eastern Hemisphere); 1 = Negative (Western Hemisphere). However, for documentation purposes, 

identify the Latitude as follows: 

 Example: 1093247.8780E (12 characters) for 109°32'47.8780" E 

n. Threshold Crossing Height (TCH). The designated crossing height of the flight path angle 

above the LTP (or FTP). The allowable range of values is defined in TERPS table 18A. 

 

Example: 00055.0 (55.0 feet); 00042.0 (42.0 feet) 

o. TCH Units Selector. This character defines the units used to describe the TCH. 

 Example: F = feet M = meters 

p. Glidepath Angle. The angle of the approach path (glidepath) with respect to the horizontal 

plane defined according to WGS-84 at the LTP/FTP. It is specified in degrees. 

 

Example: 02.75 (2.75°), 06.20 (6.20°), 03.00 (3.00°) 

q. Course Width at Threshold. The semi-width (in meters) of the lateral course at the 

LTP/FTP, defining the lateral offset at which the receiver will achieve full-scale deflection. In 

combination with the distance to the FPAP, the course width defines the sensitivity of the lateral 

deviations throughout the approach. The allowable range varies from 80m to 143.75m. See 

Order 8260.50, Table 2-3 to determine course width. 

NOTE: When the runway number is set to 00 (for circling approaches or Helicopter procedures), 

then the course width field is ignored and the course width is 38 meters. 

 

 Example 106.75 

 r. Length Offset. The distance from the stop end of the runway to the FPAP. It defines the 

location where lateral sensitivity changes to the missed approach sensitivity. The value is in meters 

with the limits being 0 to 2032m. This distance is rounded to the nearest 8-meter value. If the FPAP 

is located at the designated center of the opposite runway end, the distance is zero. 

 

Example: 0000, 0424 

s. Precision Approach Path Point CRC Remainder. An 8-character hexadecimal 

representation of the calculated remainder bits used to determine the integrity of the FAS Data Block 

data during transmission and storage. This information will be computed electronically with use of the 

electronic transmittal software and documented on Form 8260-10 (see figures A11-1 and A11-2). 

 Example CRC Remainder: E104FC14 
7/14/03 8260.19C CHG 3 

 Appendix 11 

Page 7 (and 8) 

 

t. ICAO Code. The first two designators of the ICAO location identifier, as identified in ICAO 

Doc 7910. In the Continental United States, the country code will begin with the letter “K” followed 

by a numeric character obtained from figure A11-3. Alaska, Hawaii, and U.S. Possessions will be as 

described in the ICAO Doc 7910. 

 

Example: K1, K7, PH, PA, MM, ER 

u. Orthometric Height. The height of the LTP or FPAP, as related to the geoid, and presented 

as an MSL elevation defined to a tenth of a meter resolution with the decimal point suppressed. For 

the purpose of documenting this in the “Additional Path Point Record Information,” the LTP and 

FPAP orthometric height will be the same and based on the LTP elevation. The value is preceded by a 

“+” or “-”. 

 Example: +00362 (+36.2m), +02478 (+247.8m), -00214 (-21.4m) 

 v. Horizontal Alert Limit (HAL). The HAL is the radius of a circle in the horizontal plane (the 

local plane tangent to the WGS-84 ellipsoid), with its center being at the true position, that describes 

the region which is required to contain the indicated horizontal position with the required probability 

for a particular navigation mode assuming the probability of a GPS satellite integrity failure being 

included in the position solution is less than or equal to 10-4 per hour. The range of values is 0 to 

50.8m with a 0.2 resolution. The HAL for LPV procedures developed using 

Order 8260.50 is a fixed value at 40.0 meters. 

 Example: HAL 40.0 

w. Vertical Alert Limit (VAL). The VAL is half the length of a segment on the vertical axis 

(perpendicular to the horizontal plane of the WGS-84 ellipsoid), with its center being at the true 

position, that describes the region which is required to contain the indicated vertical position with a 

probability of 1-10-7 per approach, assuming the probability of a GPS satellite integrity failure being 

included in the position solution is less than or equal to 10-4 per hour. The range of values is 0 to 

50.8m with a 0.2 resolution. The VAL for LPV procedures developed using Order 8260.50 is a fixed 

value at 50.0 meters. When future Precision WAAS becomes available, the VAL fixed value is 

planned to be 12 meters for these types of procedures. 

NOTE: A VAL of 00.0 indicates that the vertical deviations should not be used (i.e., a lateralonly {LNAV} approach. 

 Example: VAL 50.0 VAL 12.0
7/14/03 8260.19C CHG 11 

 Appendix 11 

 Page 9 

Figure A11-1 
8260.19C CHG 3 7/14/03 

Appendix 11 

Page 10 

Figure A11-2
7/14/03 8260.19C CHG 3 

 Appendix 11 

 Page 11 (and 12) 

Figure A11-3. ICAO Code Numbers 
7/14/03 8260.19C CHG 3

Appendix 12 

Page 1 (and 2) 

APPENDIX 12. 

ARINC 424 DATABASE CODES 
7/14/03 8260.19C CHG 3 

Appendix 12 

Page 3 

APPENDIX 12. ARINC 424 DATABASE CODES 

1. WAYPOINT DESCRIPTION CODES. The following Waypoint Description Codes are used by 

navigation database developers and documented as described in paragraph 851. 

Figure A12-1. Waypoint Description Codes 

Waypoint Description

Enroute, STAR, APRCH for the line 

“Airport as Waypoint” COL COL COL COL

Type/ Function Used On 40 41 42 43 

Airport as Waypoint STAR, APCH A 

Essential Waypoint1 En route, SID, STAR, APCH E 

Off Airway Waypoint2 En route F 

Runway as Waypoint, Helipad as 

Waypoint 

SID, STAR, APCH 

G 

 

Heliport as Waypoint STAR, APCH H 

NDB NAVAID as Waypoint En route, SID, STAR, APCH N 

Phantom Waypoint3 SID, STAR, APCH P 

Non-Essential Waypoint4 En route R 

Transition Essential Waypoint5 En route T 

VHF NAVAID as Waypoint En route, SID, STAR, APCH V 

Flyover Waypoint, End of SID, 

STAR Route Type, APCH 

Transition or Final Approach6 

SID, STAR, APCH 

 

B 

 

End of En route Airway or 

Terminal Procedure Route Type En route, SID, STAR, APCH 

 

E 

 

Uncharted Airway Intersection7 En route U 

Fly-Over Waypoint8 SID, STAR, APCH Y 

Unnamed Stepdown Fix after Final 

Approach Fix20 APCH 

 

A 

Unnamed Stepdown Fix Before 

Final Approach Fix20 APCH 

 

B 

ATC Compulsory Waypoint9 En route C 

Oceanic Gateway Waypoint10 En route G 

First Leg of Missed Approach 

Procedure11 APCH 

 

M 

Path Point Fix19 APCH P 

Named Stepdown Fix18 APCH S 

Initial Approach Fix12 APCH A 

Intermediate Approach Fix13 APCH B 

Initial Approach Holding Fix APCH C 

Initial Approach Fix with Final 

Approach Course Fix APCH 

 

D 

Final End Point Fix16 APCH E 

Published Final Approach Fix or 

Database Final Approach Fix14

APCH F 

Holding Fix En route, SID, STAR, APCH H 

Final Approach Course Fix15 APCH I 

Published Missed Approach 

Point Fix17 

 

M 

2. WAYPOINT DESCRIPTION CODE DEFINITION/DESCRIPTION: Fixes are located at 

positions significant to navigation in the En route, Terminal Area, and Approach Procedure path 

definitions. The “Waypoint Description Code” field enables that significance or function of a fix at a 

specific location in a route to be identified. The field provides information on the type of fix. As a 

single fix can be used in different route structures and multiple times within a given structure, the field 

provides the function for each occurrence of a fix. Source/Content: Valid contents for the 
8260.19C CHG 3 7/14/03 

Appendix 12 

Page 4 

“Waypoint Description Code” are contained in figure A12-1. The contents of Column 40 provide 

information on the fix type. Column 41 is used to define whether the fix is a “fly-over” or “fly-by” fix 

and to indicate the charting status of some waypoints. Columns 42 and 43 provide the fix function 

information. Column 40, Code “G,” is valid for Runway as Waypoint and Helipad as Waypoint. 

Explanation of superscript notes and other details required to understand figure A12-1: 

1. Any waypoint (not NAVAID, Airport, or Runway) in Terminal Procedures or any 

waypoint (not NAVAID or airport) on En route Airways, required for navigation such as 

a change in bearing, intersection of two airways, beginning or ending of continuous 

segment. 

2. Any waypoint published by government source but not part of any route structure. 

3. A waypoint established during procedure coding on the nominal track. 

4. Any waypoint (not NAVAID or airport) on En route Airways that is not considered 

“Essential” or “Transition Essential.” 

5. Any waypoint (not NAVAID or airport) on En route Airways for the purpose of 

transitioning between the En route and Terminal structures. 

6. A fly-over waypoint (including NAVAID) specified by the procedure: (a) at the end of 

a SID or STAR Route Type; (b) at the end of an Approach Transition for FMS, GPS, or 

MLS/RNAV approach; or (c) at the missed approach point in an Approach Procedure. 

7. Any waypoint (not NAVAID and airport) on En route Airways that has not been 

established by government source. Used only in conjunction with “E” in Column 40. 

8. Any waypoint (including NAVAID and airport) that must be over flown before 

establishing on the following leg. 

9. Any waypoint (including NAVAID and airport) on En route Airways at which a 

“position report” must be made to the appropriate Air Traffic Control unit. 

10. Any waypoint (including NAVAID) designated as the start/end of an oceanic organized 

rack system. 

11. Coded on the first leg after a runway fix or missed approach point fix dependent on 

approach procedure coding rules. The leg may be the first leg of a published missed 

approach procedure or a leg to the published missed approach point. 

12. Any waypoint (including NAVAID) established as an Initial Approach Fix. 

13. Any waypoint (including NAVAID) established as an Intermediate Approach Fix and 

not coded as a Final Approach Course Fix. 

14. Any waypoint (including NAVAID) established as a Final Approach Course Fix. This 

may be a fix published as the Final Approach Fix by a government source or, when no such. 

fix is published, one established by a data supplier
7/14/03 8260.19C CHG 3 

Appendix 12 

Page 5 (and 6) 

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. 

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 nonprecision approach procedures. 

17. Any waypoint (including NAVAID or Runway) established as a Missed Approach Point 

by government source. 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. 

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.