Radar Vectors
FAA Order Cancelled Issued Dec 30, 2002 AFS-400 64 pages Copy saved Nov 18, 2026

Order 8260.51 U.S. Standard for Required Navigation (RPN) Instrument Approch

This document is cancelled. Cancelled by 8260.54A. Check the official source before relying on it.

Official source ↗ Open PDF

Text read by OCR from a scanned file (10 of 64 pages). Check the original, as some words may be misread.

ORDER

UNITED STATES STANDARD

for

Required Navigation Performance (RNP)

Instrument Approach Procedure

Construction

December 30,2002

U. S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

Distribution: A-W(AS/ND/AT/AF/FS)-3; AVN- lOO(150CY S); AMA-200 (80 CYS) Initiated By: AFS-420 A-X(FS/AF/AT/AS)-3; Special Military and Public Addressees

FAA Form 1320-5 SUPERSEDES PREVIOUS EDITION

FAA Form 1320-5 SUPERSEDES PREVIOUS EDITION

CHANGE

TO BASIC

SUPPLEMENTS

OPTIONAL USE

CHANGE

TO

BASIC

SUPPLEMENTS

i

I

I

I

I I

I

I

i

r

i

I

I

I

OPTIONAL USE

These criteria are the Federal Aviation Administration (FAA) standard for developing instrument approach procedures based on required navigation performance (RNP) using area navigation (RNAV) avionics systems. Criteria are specified for approach procedures based on minimal mandatory equipage enabling the largest possible population of users to realize the benefits of RNP. tAdditionally, criteria are provided for more sophisticated procedures requiring higher levels of equipage, and associated operational requirements to achieve special authorization for use. This order, a proposed 90-series Advisory Circular (AC),.and a proposed 20-series AC provide the foundation for RNP instrument flight rule (I FR) operations.

OPTIONAL USE

RNP is an emerging tool for the development of more efficient airspace and operations. An aircraft area navigation system developed for RNP operations provides reliable, repeatable, and predictable performance through specific RNP RNAV capabilities and features. One of the key attributes is what will be defined as RNP RNAV containment. RNP RNAV provides a means to meet the requirements of RNP airspace and operations.

The concept of RNP is a significant enhancement in airspace design, use, and management relating to navigation. It was developed by the International Civil Aviation Organization (ICAO) Special Committee on Future Air Navigation Systems (FANS) and is an integral part of the communication, navigation, surveillance, and air traffic management (CNS/ATM) plan envisioned by the Special Committee. Area navigation systems have historically been developed based upon criteria specifying positioning accuracy, cross track deviation accuracy, flight technical error (FTE), airborne sensor error, and ground equipment error for a specific total system error. RNP, as envisaged by ICAO in the Manual for RNP, is a concept of navigation performance where a navigation performance accuracy value is expected to be achieved 95 percent of the time by the population of aircraft operating in the airspace. The 95 percent navigation performance accuracy is based upon the total error consisting of navigation system error, RNAV computation error, display system error, course selection error, and FTE.

James J. Ballough kv* Director, Flight Standards

Service

Page i (and ii)

TABLE OF CONTENTS

Page CHAPTER 1. GENERAL

Purpose … … 1-1 Distribution -------------------------- ---------------------------------------------------- 1-1 Effective Date ----------------------- ------------------F-w------------------------------- 1-1 Background ------------------------------------ ---- --------------- --- ---- --------------- 1-1 General --------------------------------- -------------------------------------------------- 1-1 Formulae Used in RN P Criteria ---------------------------------------------------- 1-2 Critical Comments … ---- ----- ---- 1-2 Risk assessmentNalidation of RNP Obstacle Clearance Surfaces ------- 1-2 Definitions ------------------------------------------------------------------- --- ------ --- 1-2 Approach Surface Baseline (ASBL) --------- - -------- - ----- ---- ------ ---- ----- ---- 1-2

TABLE OF CONTENTS

Decision Altitude (DA) ------- - ----- ---- ---- ------ ---- ----- ---- ----- ---- ----- 1-2 Distance of Turn Anticipation (DTA) ------ ---- ----- ------------- ----- ----- ----- ---- 1-3 Final Approach Segment (FAS) ---- - -------- -- … 1-3 Flight Path Control Point (FPCP) --- ------ ---- ----- ---- -------- - ------------------ - 1-3 Glidepath Angle (G PA) ---- ----------.----- ------ --- ------- --- ------- -- 1-3 Ground Point of 1 ntercept (G PI) … ----- ----- ---- ----- 1-4 Glidepath Quaiif ication Surface (GQS) --------.------ ----- ---- -------- -- ------- -- 1-4 Height Above Touchdown (HAT)--------------------7------------------------------ 1-4 Landing Threshold Point (LTP) ------ --------- - … 1-5 Obstacle Clearance Surface (OCS) ----- ----- ------ --- -------- - ------------------- 1-5 Precision Final Approach Fix (PFAF) … 1-5 Required Navigation Performance (RNP) … 1-5 Required Obstacle Clearance (ROC) ----- ---- ----- ---- ------------------- 1-5 Runway Threshold (RWT) ---- ----- -------- - ------------------- 1-6 Special Aircraft and Aircrew Authorization Required (SAAAR) ------------- 1-6 Visual Glide Slope Indicator (VGSI) … --------- 1-6

1 nf ormation Update … ------ --- ------------------- 1-6

CHAPTER 2. GENERAL CRITERIA

Policy Directives ----------------------------- ----- … --------------- 2-1 Data Resolution … ------------ 2-1 Documentation Accuracy --------------------------------------------------- --------- 2-1 Mathematics Convention … -- 2-2 RNP Segment Construction General Information------------------------------ 2-3 Segment Width -------------------------------- --------- --------------------------- ---- 2-3 Segment ROC -------------------------------------------------------------------------- 2-4 Segment Leg Types ---- ----- … … -- 2-6 Calculation of Descent Gradient … 2-6 Determining Turning Flight Track Radius -------7-.------- ----------------------- 2-8 Fly-By Fix Turn Inner Boundary Expansion, Outer Boundary Construction ---------- ----- -------------------------------------------------------------- 2-8 Joining Segments of Differing RNP-Levels------------------------ -------------- 2-10

CHAPTER 2. GENERAL CRITERIA

Page iii

CHAPTER 3.

CHAPTER 4.

CHAPTER 5

TABLE OF CONTENTS (Continued)

INITIAL AND INTERMEDIATE SEGMENTS

Page g ?

Initial and Intermediate Segments … 3-1 Alignment -------------------------------------------------------------------------------- 3-1 Length --------- … ----- --- --------------- ---- --------------- 3-1 Width ------------------------------------------------------------------------------------- 3-2 Required Obstacle Clearance (ROC) --------------------------------------------- 3-3 Descent AngleIGradient ------------------------------------------------------------- 3-3

FINAL APPROACH SEGMENT (FAS)

FINAL APPROACH SEGMENT (FAS)

BASIC … ---------- --- … 4- 1 ADVANCED … ----------- ----- ------------------ 4- 1 Determining Precision Final Approach FixIFinal Approach Fix (PFAF/FAF) Coordinates … 4- 1 Determining Glidepath Altitude at a Fix ------------------------------------------ 4-2 Threshold Crossing Height (TCH) … 4-2 Glidepath Angle (G PA) ---------------------------------- ------ -------- --------------- 4-3 Glidepath Qualification Surface (GQS) ------------------------------------------ 4-3 Area--------------------------------------------------------------------------------------- 4-3 Final Segment -------------------------------------------------------------------------- Length and Alignment ----------------------------- ---- ----------------- -------------- Width -------- -------------------------------------- --------- ------ … :," 7 4-5 _I Obstruction Clearance---------------------------------------------------------------- 4-5 ADVANCED Final Segment Vertical Surfaces. RESERVED. ------------- 4-1 0

Minimums … ----- -------------------- ----------- 4-1 0

MISSED APPROACH SEGMENT (MAS)

MISSED APPROACH SEGMENT (MAS)

General … ----------------------------------------------------------- 5- 1 Segment Width --------------------------------------------- ----------------- ---- ------ 5- 1 BASIC -------------------------- -------------------- - ------------------------------------- 5- 1 ADVANCED ------------------- -------------------- - ------------------------------------- 5-2 Straight Missed Approach Construction ------------------ ----------------------- 5-2 Turning Missed Approach -- ------------------- ------------ -------------------------- 5-2 Level OCS … ------------------ - ------------------------------------- 5-3 Length and Width -------------- ------------------ - … 5-3 MA Level Surface Obstacle Clearance ------------------------------------------- 5-4 40: 1 Surface … - … 5-4 Length -------- -------------- … - ------------------------------------- 5-4 Obstacle Clearance … 5-4 Missed Approach Clearance Limit Altitude -------------------------------------- 5-4 . . Straight Missed Approach Procedures … 5-4 Combination Straightfrurning Missed Approach Procedures ---------------

5-4 ?

Page iv

TABLE OF CONTENTS (Continued)

Page

APPENDIX 1 FORMULAE USED IN RNP CRITERIA (4 pages) … 1

APPENDIX 3 RISK ASSESSMENTNALIDATION OF RNP OBSTACLE ----------------- 1 CLEARANCE SURFACES (6 pages)

Page v (and vi)

CHAPTER 1. GENERAL

PURPOSE.

These criteria are the Federal Aviation Administration (FAA) standard for developing instrument approach procedures based on required navigation performance (RNP) using area navigation (RNAV) avionics systems. Criteria are specified for approach procedures based on minimal mandatory equipage enabling the largest possible population of users to realize the benefits of

CHAPTER 1. GENERAL

RNP. Additionally, criteria are provided for more sophisticated procedures requiring higher levels of equipage, and associated operational requirements to achieve special authorization for use. This order, a proposed 90-series Advisory Circular (AC), and a proposed 20-series AC will provide the foundation for RNP instrument flight rule (IFR) operations.

DISTRIBUTION.

This order is distributed in Washington headquarters to the branch level in the Off ices of Airport Safety and Standards and Communications, Navigation, and Surveillance Systems; to Air Traffic, Airway Facilities, and Flight Standards Services; to the National Flight Procedures Office and the Regulatory Standards Division at the Mike Monroney Aeronautical Center; to branch level in the regional Flight Standards, Airway Facilities, Air Traffic, and Airports Divisions; special mailing list ZVS-827, and to special military and public addressees.

EFFECTIVE DATE. March 3,2003

BACKGROUND.

The concept of RNP is a significant enhancement to navigable airspace design, use, and management. It was developed by the International Civil Aviation Organization (ICAO) Special Committee on Future Air Navigation Systems (FANS) and is an integral part of the communication, navigation, surveillance, and air traffic management (CNSIATM) plan envisioned by the Special Committee. RNP levels address obstacle protection associated with RNP accuracy values. The RNP level (RNP x, where x=0.3, 1, 2, etc.), when applied to instrument procedure obstacle evaluation areas, is a variable used to determine a segment primary area half-width value; i.e., total width is + a multiple of the value used to identify the level.

GENERAL.

Criteria exploiting mandatory avionics features for RNP certification (such as track-to-fix capability) are considered BASIC criteria and are available for application in any RNP approach procedure. Criteria exploiting features that are not mandatory (such as radius-to-fix leg type capability) are considered ADVANCED criteria applicable only to approach procedures that require special authorization for use. Minimums based on application of ADVANCED criteria must be published under the " Special Aircraft and Aircrew

Par 1.0 Page 1-1

Authorization Required" format similar in depption to category 1111 11 approach procedures. Some drawings in this order are not to scale. All possible construction scenarios cannot be anticipated land addressed in this order; therefore, sound judgment and common sen$e based on procedure development experience is necessary in some construction scenarios.

Formulae Used in RNP Criteria.

1

Formulae are numbered for easy reference. Ip complete list of the formulas is located in appendix 1.

Critical Comments.

An explanatory comment is indicated as a nu+bered footnote (like this example(3)) referring the reader to a like numtiered comment located in appendix 2.

Risk AssessmentNalidation of RNP Obstable Clearance Surfaces.

This report (appendix 3) will provide supportiqg material justifying values used for determining obstacle clearance zones for certain RNP operations defined in this Order - including straight, level flight; fl -by turns between two legs of the same RNP; and straight flight through a tr nsition from a higher RNP to a lower one. P

DEFINITIONS.

For the purposes of this document, the following definitions apply:

Approach Surface Baseline (ASBL).'')

A line aligned to the runway centerline (RCL) hat lies in a plane parallel to a tangent to the orthometric geoid (WGS-84 elli b soid for Wide Area Augmentation SystemlLocal Area Augmentatipn System (WAASILAAS)) at the runway threshold. It is used as a baselin reference for vertical measurement of the height of the glidepath d obstruction clearance surfaces (see figure 1-3)

Decision Altitude (DA).

A specified barometric altitude at which a missed approach must be initiated if the required visual references to continue the approach have not been established.

Par 1.4

1.5.3 Distance of Turn Anticipation (DTA).

The distance from (prior to) a fly-by fix that an aircraft is expected to start a turn to intercept the course of the next segment (see figure 1-1). Since there is an along-track fix displacement value associated with a fix, this value is added to DTA to assure initiation of the turn will occur in a timely manner.

Figure 1-1. DTA

ATRK Fix Displacement

1.5.4 Final Approach Segment (FAS).

The FAS begins at the final approach fix (FAF) and ends at the landing threshold point (LTP). For obstacle evaluation purposes, the FAS begin at the along-track fix displacement value prior to the FAF and ends at the LTP. The FAS is typically aligned with the runway centerline extended.

1.5.5 Flight Path Control Point (FPCP).

The FPCP is a 3D point defined by the LTP latitudellongitude position, MSL elevation, and a threshold crossing height (TCH) value. The FPCP is in the vertical plane of the final approach course and is used to relate the glidepath angle of the final approach track to the landing runway. It is sometimes referred to as the TCH point or reference datum point (RDP) (see figure 1-3).

1.5.6 Glidepath Angle (GPA).

The GPA is the angle of the specified final approach descent path relative to the ASBL (see figure 1-2). In this order, the glidepath angle is represented in formulas and figures as the Greek symbol 8.

Par 1.5.3 Page 1-3

Figure 1-2. FPCP, GPA, GRI

ASBL

parillel

f lines tan (0) I I

Ground Point of Intercept (GPI).

The glidepath intercepts the ASBL at the GPI. The GPI is expressed as a distance in feet from the LTP. GPI = - TCH (see figure 1 -2). tan (0)

Glidepath Qualification Surface (GQS).

The GQS is a narrow inclined plane centered on the runway centerline that limits the height of obstructions between the DA and LTP.

Height Above Touchdown (HAT).

The HAT is the height of the DA above the highest point in the first 3,000 feet of the landing runway (touchdown zone elevation). See figure 1-3

Runway 1

Figure 1-3. HAT

DA

Glidepath HAT // --------- 1 -

ASBL -

Page 1-4 Par 1.5.6

1.5.1 0 Landing Threshold Point (LTP).

The point where the runway centerline (RCL) intersects the runway threshold

(RWT) is known as the LTP. It is defined by WGS 84lNAD 83 latitude, longitude, and orthometric height (MSL elevation). See figure 1-4.

Figure 1-4. LTP

RCL LTP

RCL LTP

1.5.1 1 Obstacle Clearance Surface (OCS).

The OCS is an inclined surface with a slope ratio dependent on the glidepath angle of a precision approach or an approach procedure with vertical guidance (APV). The separation between this surface and the glidepath at any given distance from GPI defines the MINIMUM required obstruction clearance at that point.

1.5.12 Precision Final Approach Fix (PFAF).

A 2-dimensional (2D) point located on the final approach col~rse at the point the glidepath intercepts the intermediate segment altitude (glidepath intercept altitude). The PFAF marks the beginning of the precision FAS (see figure 1-5).

Figure 1-5. PFAF

PFAF p Intermediate

I Segment Altitude

Glidepath /I I I I I I

Distance from

PFAF to LTP

1.5.1 3 Required Navigation Performance (RNP).

RNP is a statement of the navigational performance required to maintain flight within a given airspace.

1.5.1 4 Required Obstacle Clearance (ROC).

ROC is the MINIMUM amount (in feet) of vertical clearance that must exist between aircraft and ground obstructions at a specific point in an instrument procedure. ROC is provided through application of level and sloping OCS's.

Par 1 5 . 1 0 Page 1-5

Runway Threshold (RWT).

The RWT marks the beginning of the portion of the runway usable for landing (see figure 1-6). It extends the full width of the runway. The LTP geographic coordinates identify the point the runway centerline crosses the RWT.

Figure 1-6 Threshold

RWT

Special Aircraft and Aircrew Authorization Required (SAAAR).

It is possible to equip aircraft beyond the minimum standard and to train aircrews to achieve a higher level of performance. These higher levels of equipage and overall performance are the basis of expanded RNP capability. Procedures that incorporate this expanded capability will contain a minima line that requires special authorization for use.

Visual Glide Slope Indicator (VGSI).

The VGSI is an airport lighting aid that provides the pilot a visual indication of the aircraft position relative to a specified glidepath to a touchdown point on the runway.

INFORMATION UPDATE.

For your convenience, FAA Form 1320-1 9, Directive Feedback Information, is included at the end of this order to note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this order. When forwarding your comments to the originating office for consideration, please use the "Other Comments" block to provide a complete explanation of why the suggested change is necessary.

Page 1-6 Par 1.5.15

CHAPTER 2. GENERAL CRITERIA

CHAPTER 2. GENERAL CRITERIA

POLICY DIRECTIVES.

Orders 8260.3, United States Standard for Terminal Instrument Procedures (TERPS); 8260.19, Flight Procedures and Airspace; 8260.38, Civil Utilization of Global Positioning System (GPS); 8260.44, Civil Utilization of Area Navigation (RNAV) Departure Procedures; 8260.45, Terminal Arrival Area (TAA) Design Criteria; and 71 30.3, Holding Pattern Criteria, apply unless specified otherwise in this order. The final and missed approach criteria described in this order supersede the other publications listed above, except as noted.

DATA RESOLUTION.

Perform calculations using at least 0.01 unit of measure accuracy. Use double precision (calculation accuracy to at least 13 decimal places) where calculation is accomplished by automated means. The following list specifies the minimum accuracy standard for documentinq data expressed numerically. This standard applies to the documentation of final results only; e.g., a calculated adjusted glidepath angle of 3.04178" is documented as 3.05". The standard does not apply to the use of variable values during calculation. Use the most accurate data available for variable values.

*Do not round intermediate results. Round only the final result of calculations for documentation purposes.

Documentation Accuracy:

a. WGS-84/NAD-83 latitudes and longitudes to the nearest one hundredth (0.01) arc second;

b LTP MSL elevation to the nearest foot,

c. LTP height above ellipsoid (HAE) to the nearest tenth (0.1) meter;

d. Course width at threshold to the nearest quarter (0.25) meter;

e. Glidepath angle to the next higher one hundredth (0.01) degree;

f. Courses to the nearest one hundredth (0.01) degree; and

g. Distances to the nearest hundredth (0.01) unit.

*Use the documented rounded values in paragraphs 2.1. l a through f in calculations.

Par 2.0 Page 2-1

Mathematics Convention.

a. Definition of Mathematical Functions.

a+ b indicates addition a- b indicates subtraction

a x b or ab indicates multiplication

a i; or % or a + b indicates division

(a- b) indicates the result of the process within the parenthesis I a- bl indicates absolute value

E: indicates approximate equality & indicates the square root of quantity "a" a* indicates ax a tan(a) indicates the tangent of "a" degrees

tan-'(a) indicates the arc tangent of "a"

sin(a) indicates the sine of "a" degrees

sin-'(a) indicates the arc sine of "a"

C O S ( ~ ) indicates the cosine of "a" degrees

cos-l(a) indicates the arc cosine of "a"

b. Operation Precedence (Order of Operations).

First: Grouping Symbols: parentheses, brackets, braces, fraction bars, etc. Second: Functions: Tangent, sine, cosine, arcsine and other defined

functions Third: Exponentiations: powers and roots Fourth: Multiplication and Division: products and quotients Fifth: Addition and subtraction: sums and differences e-g,

5 - 3 x 2 = -1 because multiplication takes precedence over subtraction (5 - 3 ) ~ 2 = 4 because parentheses take precedence over multiplication

6* - = 12 because exponentiation takes precedence over division 3 ,/9+16 = 5 because the square root sign is a grouping symbol fi + a = 7 because roots take precedence over addition sin (30") - = 1 because functions take precedence over division 0.5

sin(30Xe5) = 0.8660254 because parentheses take precedence over functions

Note on calculator usaae: Most calculators are programmed with these rules of precedence. When possible, let the calculator maintain all of the available digits of a number in memory rather than re-entering a rounded number. For highest accuracy from a calculator, any rounding that is necessary should be done at the latest opportunity.

Page 2-2 Par 2.1.2

5 2.2 RNP SEGMENT CONSTRUCTION GENERAL INFORMATION.

if- Parallel lines normally bound obstruction clearance areas associated with RNP (see figures 2-1 A and 2-1 8). Turns are normally accomplished at fly-by fixes. Turns are limited to 120" or less at and below flight level 190, 70" or less above flight level 190.

Segment Width.

See table 2-1 for applicable RNP-levels.

a. BASIC. Primary area: $widthpha, = 2x RNP , Secondary area: Width-, = I x RNP . (see figure 2-1 A).

Figure 2-1A BASIC RNP Segment Width

b. ADVANCED. Primary area: * ~ i d t h ~ , , , ~ , = 2x RNP . There are no secondary areas (see figure 2-1 B).

Figure 2-1 B. ADVANCED RNP Segment Width

Par 2.2 Page 2-3

Segment ROC.

The ROC varies according to segment type (initial, intermediate, etc.). See figures 2-2A and 2-28 and table 2-1.

Table 2-1. Typical BASIC RNP-level? and ROC values'

I SEGMENT 1 RNP-LEVEL I ROCVALUE I PRIMARY I

I SEGMENT 1 RNP-LEVEL I ROCVALUE I PRIMARY I

En Route

I Final 1 0.3 I ** 1 1.2 NM (k0.6) I

Initial Intermediate

Missed 4pproach 1 .O I ** ( 4.0 NM (k2.0) 1 L O O 0 in designated mountain& terrain. Volume I , paragraph 1720 applies

(NM)

2.0

** Variable for final descent and missed approach climb, see appropriate section.

1 .O 1 .O

a. BASIC. Minimum altitude determination using primary and secondary ROC (see figure 2-2A).

1 OOO*

1 OOO*

NOTE: The secondary transitional surface 7: 1 rise varies with RNP- level. For instance, the surface rises 260.4 feet for an RNP-Ievel of 0.3, and 868 feet for an RNP-level of 1.0.

AREA WIDTH 8.0 NM (k4.0) 1 OqO 500

Figure 2-2A. RNP Segment RUC

Segment Cross Section

4.0 NM (k2.0) 4.0 NM k2.0)

1 RNP

Enlarged View of Secondary

Page 2-4 Par 2.2.2

a. (1) Primary area. Determine the minimum altitude (A) value prior to

rounding using formula 2.1 :

Minimum Altitude Calculation

Where h MSL height of obstade (or equivalent height from 2.2.242)) ROC = ROC vdw *om table 2-1

a t TERPS Volume 1, paragtaph 323 adjustrnentt9 (if appropriate)

a. (2) Secondary arm. Use formula 2.2 to reduce the height of a secondary obstacle to en equivalent height applicable to the primary area. If evaluating the obstacle with ROC, use the equivalent height value for h in formula 2.1. If evaluating the final segment secondary area, apply the equivalent height of the obstacle as value h in paragraph 4.5.3.

where d, = distance from edge of primary measured

perpendicular to-course

b. ADVANCED. Minimum altitude determination using primary ROC (see figure 2-28).

Figure 2-28. RNP Segment ROC

Segment Cross Section

Enlarged View of I Edge

Determine the minimum altitude (A) value prior to rounding using formula 2.1 above.

Par 2.2.2a(1) Page 2-5

Segment Leg Types. i

RNP procedures are constructed by connectin segment legs together. A segment is identified by the method used to d P fine the lateral path and how the segment terminates. There are several leg types available for RNAV operations. Five leg types are identified below; however, only one will be utilized in the first edition of these criteria. ~d4itional leg types will be implemented in future changes to this order. l@g types are often identified by a two-letter acronym. These acronyms are a et of defined codes referred to as Path Terminators. Each code defines a sp ", cific type of flight path and a specific type of termination of flight path. For a TF leg is a great circle track between two known fixes and term a fix, while a VA (Heading-to-Altitude) or HA (Hold-to-Altitude) t s at an altitude.

l

a. BASIC. I

a (1) Straight Route Segment [track to a (TF) leg]. A straight flight path between two fixes. The first fix is either leg termination fix or the initial (first) fix of a procedure (see figure

Figure 2-3. Track to a Fix (TF) 'Leg Type

I b. ADVANCED

b. (1) Radius to Fix (RF) Segment. RESE~VED

b. (2) Hold to Fix (HF) Route Segment. R~SERVED

b. (3) Hold to Altitude (HA) Route Segment. RESERVED

b. (4) Hold to Manual (HM) Terminal Route Segment. RESERVED

Calculation of Descent ~radient'~).

a. Calculating Descent Distance (D). Where a turn is required at the IF, calculate the initial and intermediate segment descent distances as depicted in figure 2-4. Refer to formula 2.5 to calculate turn radius (R) values.

Page 2-6 Par 2.2.3

Figure 2-4. Calculating Descent Distance (D)

D = DINI or DIM as appropriate in NM

L = LINI or LINT as appropriate in NM

8 = Degrees of heading change

EXAMPLE L=6 NM 8=60° Alt=6000 CAT D/E

R=1.49 (See formula 2.5)

~ = 6 - [I .49tm (6%)] D=5.14 NM

2.2.4 b. Calculating Descent Gradient (DG). Determine total altitude lost between the plotted positions of the IAF and IF or IF and FAF in feet as appropriate. Determine the distance (D) in NM available for descent (see formula 2.3). Divide the total altitude lost by D to determine the segment descent gradient (see formula 2.4 and figure 2-5).

Figure 2-5. Calculating Descent Gradient

IF

Example

Par 2.2.4a Page 2-7

8260.5 1 I

2.2.5 Determining Turning Flight Track ~adius(~!

Calculate the flight track turn radius using formula 2.5:

Using the following indicated airspeeds in the specified segments (convert to true airspeed using formula 2.5 above):

Final Approach Seament Cat A-90, Cat 8-120, Cat C-140, Cat D-165, Cat E->I65 (specify)

InitiaVintermediate Segments Cat A-1 50, Cat 8-180, Cat C-240, Cat D/E-250

NOTE: Use the highest published category for the procedure.

2.2.6 Fly-By Fix Turn Inner Boundary Expansion, Outer Boundary Construction.

2.2.6 a. BASIC. See figure 2-6A.

RNAV turns are usually accomplished at fly-by or fly-over fixes. Fly-over fixes are not recommended in RNP segments. Turns at fly-by fixes require an expanded area on the inside of the turn to protect the ground track inside the fix. Construct the expanded inner boundary using the steps:

STEP 1: Draw a line bisecting the turn angle. The origin of all arc radii will be on this line. Using the appropriate turn radius (R) from formula 2.5, draw an arc tangent to the course to and from the turn fix.

STEP 2: Using the turn fix as the origin, draw an arc of radius 2 RNP tangent to the outer boundary lines of the preceding and succeeding segments.

STEP 3: Using the turn fix as the origin, draw an arc of radius 3 RNP tangent to the secondary area boundary lines of the preceding and succeeding segments.

STEP 4: Using a radius of R+RNP, draw an arc tangent to the inner boundary line of the preceding and succeeding segments.

STEP 5: Using the arc origin from step 4, draw an arc of radius R tangent to the secondary area boundary lines of the preceding and succeeding segments.

Page 2-8 Par 2.2.5

1 2/30/02

Figure 2-6A. Inside Turn Expansion at Fly-By Fixes

/

b. ADVANCED. See figure 2-6B.

STEP 1: Draw a line bisecting the turn angle. The origin of all arc radii will be on this line. Using the appropriate turn radius (R) from formula 2.5, draw an arc tangent to the course to and from the turn fix.

STEP 2: Using the turn fix as the origin, draw an arc of radius 2 RNP tangent to the outer boundary lines of the preceding and succeeding segments.

STEP 3: Using a radius of R+RNP, draw an arc tangent to the inner boundary line of the preceding and succeeding segments.

Par 2.2.6a Page 2-9

Figure 2-68. Inside Turn Expansion Ct Fly-By Fixes

2.2.7 Joining Segments of Differing RNP-L~V~IS(~).

Page 2-1 0

A lower RNP level may yield lower segment altitudes since the obstacle evaluation area is smaller thus contains fewer obstacles, but the controlling obstacle is often close to the course line. Therefore, use the largest appropriate level possible in the intermediate and final approach segments consistent with desired minimums in order ta curtail construction of ground obstructions in the vicinity of the final approach course. Design procedures

requiring RNP-level changes between the IAF and MAP to change levels in straight segments. The location of the fix marking RNP-level reduction should be based on the point where the lower RNP4evet is required. Locate the fix distance (d) from this point to assure appropriate alerting can be provided prior to the time that the lower RNP-level is needed considering the along- track error of the larger of the 2 segments (IxRNP), maximum latency (L) of

RNP alerting messages, maximum ground speed, crew response time (RJ, and distance (E) required to clear obstacles immediately beyond the fix (see figure 2-7 and table 2-2).

Par 2.2.6b

Figure 2-7. Changing to Smaller RNP-levels

Minimum Altitude E - 9

--.--.- -------.- ------------..

A 2 RNP 4 … -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.--.-.- 1 2 RNP

The distance required to clear an obstruction is determined by applying a 40:l OCS starting at a height equal to the preceding segment minimum altitude minus the required ROC including adjustments. Determine distance E (NM) using formula 2.6.

A 2 RNP 4 … -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.--.-.- 1 2 RNP

----

t

t.fl.?o*.~-. ,, *r+

RNP Change

2 RNP

ace

-.---..--.-.----- .-.- -

B = ~inimum segment Altitude C = ROC plus adjustments of succeeding segment OMSL = MSL elevation of obstacle

Example 3*200 - 500 = 2.700 (a)

Table 2-2. Minimum Fix Distance (d) Variables

(Use values for the largest published category)

Category I Latency(L) ( Rmction(R,,) I

Par 2.2.7

A B C D E

Page 2-1 1

in seconds

15 15 15 15 15

in seconds-

25 25 25 25 25 .

Determine d using formula 2.7

Page 2-1 2

Since L and R. are consistent for each category, the equation may be reduced to formula 2.8 for simplicity.

Par 2.2.7

1 2/30/02

CHAPTER 3. INITIAL AND INTERMEDIATE SEGMENTS

CHAPTER 3. INITIAL AND INTERMEDIATE SEGMENTS

3.0 INITIAL AND INTERMEDIATE SEGMENTS.

An RNP approach procedure is a series of segment legs.

3.0.1 Alignment. .

The geometry of the approach design is very flexible, allowing the RNAV "T" design configuration (see Order 8260.45), any GPS style configuration (see Order 8260.38A), or use of conventional instrument approach configuration (VOR, ILS, etc.) within the limitation of installed equipment.

a. BASIC Alignment Limitations. The MAXIMUM initiawinterrnediate segment intercept angleis 120". The angle of intercept affects the MINIMUM intermediate segment length (see paragraph 3.0.2). The intermediate segment is an extension of the final approach course; i.e., a turn is not permitted at the FAF.

3.0.1 b. ADVANCED Alignment Limitations. RESERVED

3.0.2 Length.

3.0.2 a. Initial Segment. The length of the INITIAL segment must accommodate the descent required within the segment.

3.0.2 b. Intermediate Segment. The MINIMUM length of the INTERMEDIATE segment is dependent on, at least the following factors:

The distance required to accommodate any change in RNP value between the initial segment width and the final segment width (see para- graph 2.2.7).

The change (in degrees) from the initial course to the intermediate course

(see table 3-1 ).

The amount of altitude loss required in the segment (see para- graph 3.0.5b).

Table 3-1. MINIMUM INTERMEDIATE COURSE LENGTH

Par 3.0

ANGLE (DEGREES)

ANGLE (DEGREES)

90 - 96 >96 - 102 >I02 -108 >I08 -1 14 > I 14 - 120

MINIMUM LENGTH (MILES)

CAT CIDIE

5 6 6 7 6 8 6 9 7 10

3.0.3 Width. See paragraph 2.2.1

3.0.3 a. BASIC Intermediate connection with pqecision final segment. Connect the intermediate segment to the final segment as shown in figure 3-1~).@)

CAT CIDIE

STEP 1. From a point 2 NM prior to the PFAF, connect the intermediate area primary boundary to the "X" surface boundary line abeam the PFAF.

STEP 2. From a point 2 NM prior to the PFAlf, connect the transition area outer boundary to the 'Y" surface boundary lirhe abeam the PFAF.

Figure 3-1 A. BASIC Intermediate hnnection

to Precision Final Segment

(Example RNP-Level 1.0 with intermediate segment secondary areas)

h e z a rl

+ t

3 N

- - - t-

- -

3 N

c i Example: RNP = 1 3

3.0.3 b. ADVANCED Intermediate connection with precision final segment. STEP 1. From a point 2 NM prior to the PFAF, connect the intermediate area primary boundary to the "X" surface boundary line abeam the PFAF (see figure 3-1 8). STEP 2. From this point, draw a line splaying outward 15"

relative to the final course to intersect the outer boundary of the Y surface.

Page 3-2 Par 3.0.3

Figure 3-1 B. ADVANCED lntermediate Connection

to Precision Final Segment

(Example No intermediate segment secondary areas)

IC Example: RNP = 1

3.0.4 Required Obstacle Clearance (ROC).

Establish the MINIMUM altitudes in the en route, feeder, initial, and intermediate segments by adding ROC and adjustments to the obstruction elevation. The resulting value may be rounded up or down to the nearest

100-foot increment if the rounded value provides at least MINIMUM ROC; i.e., 1,749 feet may round to 1,700 feet, and 1,750 feet may round to 1,800 feet. If a value is rounded down and the resulting value does not provide MINIMUM ROC, then the original value must be rounded up.

3.0.4 a. Initial Segment ROC. MINIMUM ROC is 1,000 feet plus adjustments required by TERPS Volume I, paragraph 323.

3.0.4 b. Intermediate Segment ROC. MINIMUM ROC is 500 feet plus adjustments required by TERPS Volume I, paragraph 323.

3.0.5 Descent AngleIGradient.

The following OPTIMUM and MAXIMUM descent gradients apply. The flexibility offered by MAXIMUM and MINIMUM values may adversely affect the flyability of the approach procedure. Therefore, do not apply MAXIMUM descent gradients in segments of MlNlMUM length.

3.0.5 a. Initial Segment.

OPTIMUM 250 FTINM (for high altitude penetrations 800) MAXIMUM 500 FTINM (for high altitude penetrations 1,000)

Par 3.0.3b

b. Intermediate ~egment.'~)

OPTIMUM 150 FTINM May require deceleration segment 2 240 FTINM MAXlMUM318FTINM

c. Deceleration Segment (applicable ONLY where minimums are published for category "C" or faster aircraft and a deceleration segment is deemed necessary). Where the intermediate segment descent gradient exceeds 240 ft/NM because of terrain or obstacles, a deceleration segment may be constructed in the initial segment. The MINIMUM deceleration length is dependent on segment descent gradient and magnitude of turn at the IF. The

MAXIMUM allowable descent gradient in the deceleration segment is 150 WNM. Refer to table 3-2 to determine the minimum deceleration segment length (see figure 3-2 for examples).

Table 3-2. Minimum Deceleration Segment Length

Figure 34. Example of Deceleration Segment

Segment Descent

Gradient (MUM)

0 75 150

DG=500 WNM

Final Final to lower gradient

Par 3.0.5b

Turn at IF s 45" Minimum Length

2 3 5

Turn at IF >45O Minimum Length

4 4 5

CHAPTER 4. FINAL APPROACH SEGMENT (FAS)

CHAPTER 4. FINAL APPROACH SEGMENT (FAS)

GENERAL.

BASIC. Vertical obstacle protection is based on the standard for baro-VNAV in TERPS Volume 3.

ADVANCED. Vertical obstacle protection based on variable vertical error budget. RESERVED.

DETERMINING PRECISION FINAL APPROACH FIXFINAL APPROACH FIX (PFAFJFAF) COORDINATES (see figure 4-1).

Figure 4-1. Determining PFAF Distance to LTP

Desired Bearing from LTP to PFAF (Ideally

the Reciprocal of the Be- from LTP to the opposite m a y end).

Geodetically calculate the latitude and longitude of the PFAF using the true bearing from the landing threshold point (LTP) to the PFAF and the horizontal distance (DPFAF) from the LTP to the point the glidepath intercepts the intermediate segment altitude.

Determine DPFAF using formulas 4.1 and 4.2:

Step 1 : Example: 1 537.70 = 21 00 - 56230

{includes earth curvature)

Par 4.0 Page 4-1

Example

20,890,537 x sin (90 + 3) 1,537.7 + 20,890,537

DPFAF = 364,609 87 - sin- 1 20,861,9072451 50 [ ( 20,892,074.70 )] -

Where: A = FAF Altitude (example 21 00)

F = LTP elevation (example 562.30) 8 = Glidepath angle (example 3.00")

Determining Glidepath Altitude at a FIX.

Calculate the altitude (ZZ) of the glidepath at any distance (4) from the ground point of intercept (GPI) using formula 4.3: {includes earth curvature)

Example 20,890,537 x sin (90 + 3) 22 = 562.30 + sin 90-3- 28,95603) - 209890'537 ( 364,609

Where: 8 = Glidepath angle (example 3.00") D = Distance in feet from GPI to fix LTP = Threshold elevation (MSL)

Z = Glidepath MSL altitude at fix

THRESHOLD CROSSING HEIGHT (TCH).

Select the appropriate TCH from table 4-1. Publish a note indicating the visual glide slope indicator (VGSI) is not coincident with the RNP procedure glidepath angle (GPA) when the difference between VGSI angle and the procedure GPA is more than 0.2" or the difference between the VGSI TCH and the procedure's TCH is more than 3 feet.

Page 4-2 Par 4.1

NOTE: If an instrument landing system (ILS) setves the runway, use the ILS TCH and glidepath angle.

Table 4-1. TCH Requirements

Note 1 : To determine the minimum allowable TCH, add 20 feet to the glidepath-to-wheel height. Note 2: To determine the maximum allowable TCH, add 50 feet to the glidepath-to-wheel height.

Representative Aircraft Type

HEIGHT GROUP 1 General Aviation, Small Commuters, Corporate Turbojets, T-37, T-38, C-12, C-20, C-21, T-1 , Fighter Jets HEIGHT GROUP 2 F-28, CV-340/440/580, 8-737, C-9, DC-9, C-130, T-43, 0-2, S-3

HEIGHT GROUP 3 0-727/707/720/757, 8-52, C-135, C-141, C-17, E-3, P-3, E-8

HEIGHT GROUP 3 0-727/707/720/757, 8-52, C-135, C-141, C-17, E-3, P-3, E-8

HEIGHT GROUP 4 8-747/767/777, L- 1 01 1, DC-1 0, A-3001320, B-1,

KC-1 0, E-4, C-5, VC-25

4.3 GLIDEPATH ANGLE (GPA) (see table 4-2).

Table 4-2. Allowable Range of Glidepath Angles

Approximate Glidepath to Wheel Height

10 Feet or less

10 Feet or less

15 Feet

20 Feet

25 Feet

OPTIMUM 3.0' MINIMUM 2.75" 292 MAXIMUM 3.5" 371

Par 4.2

Recommended TCH k 5 Feet

40 Feet

45 Feet

50 Feet

55 Feet

GLIDEPATH QUALIFICATION SURFACE (GQS).

Remarks

Many runways less than 6,000 feet long with reduced widths and/or restricted weight bearing which would normally prohibit landings by larger aircraft.

55 Feet

Regional airport with limited air carrier service.

Primary runways not normally used by aircraft with ILS glidepath-to-wheel heights exceeding 20 feet.

Most primary runways at major airports.

The GQS extends from the runway threshold along the runway centerline extended to the decision altitude (DA) point. It limits the height of obstructions between DA and runway threshold (RWT). When obstructions exceed the height of the GQS, an approach procedure with positive vertical guidance is not authorized (see figure 4-2).

Area.

a. Length. The GQS extends from the runw4y threshold to the DA point.

I b. Width. The GQS originates 100 feet from the runway edge at LTP.

Figure 4-2. GQS

b. (I) % Width at DA (X W, o DA)." Calculate the half-width of the GQS from the runway centerline extended at the DA point using formula 4.4:

Where: DDA = the distance (ft) measured along RCL extended

from LTP to the DA point % Wp = half-width (ft) of GQS area

b. (2) % Width at any distance. Calculate the half-width of the GQS at any distance "d" from RWT using formula 4.5 (see figure 4-2):

Where: DDA = distance (ft) from LTP to the DA point

d = desired distance (ft) measured along RCL

extended from LTP w = GQS half-width at distance d W, @ DA = GQS half-width at DA from paragraph 4.4.1 b(1)

RWT width + , 00 k = 2

Page 4-4 Par 4.4.1 a

c. OCS. Obstructions must not penetrate the GQS. Calculate the height of the GQS above the approach surface baseline (ASBL) at any distance "d" measured from RWT along the runway centerline (RCL) extended to a point abeam the obstruction (see figure 4-2) using formula 4.6:

Where d = distance from LTP (ft)

8 = glidepath angle

FINAL SEGMENT.

Length and Alignment.

The obstruction evaluation area begins at the along-track fix displacement value prior to the PFAF and extends to the LTP or missed approach point (MAP), whichever is encountered last (see figure 4-3). Align the final approach segment

(FAS) with the runway centerline extended. Offset alignment is not authorized.

a. ADVANCED. Turns within Final Segment. RESERVED.

Figure 4-3. Final Approach Segment

LTP FAF -).-- -..-..-.-..-..-..-..-.--.-..-..- … * ..-..-..-..-..

' I I R

N Final Length - 1 p Obstacle Clearance Area - 4

4.5.2 Width.

Segment width is dependent on the RNP value (see paragraph 2.2.1 for width requirements).

4.5.3 0 bstruction Clearance.

Obstacle clearance is achieved by applying required obstacle clearance (ROC) or sloping obstacle clearance surfaces (OCS's) to the height of obstructions (or equivalent height if dealing with secondary areas per paragraph 2.2.2a(2)). See figure 4-4.

Par 4.4.1 c. Page 4-5

Figure 4-4. Final Segmenp OCS's

*

FAF

ASBL

Distance to point "cw (Dc)

FAF ATRK Displacement

LTP

Level -+

h / Inner Surface I " -" … .... -.-.-...*.- .-.. ---.-.------- - -----.-.-- -------- ASBL *+-+I

a. Level Surface.

The longitudinally level OCS overlies the area between the LTP and the point the glidepath reaches 250 feet above ASBL (di~tan~e'D~~~''). See figures 4-4 and 4-5. Calculate distance "D2< in feet from the LTP using formula 4.7:

Example

Figure 45. ROC Inside the 250 Feet Above ASBL Point

MAP

Cross Section

a. (1) Preliminary DA (pDA). Determine the pDA by adding 250 feet ROC value to the MSL elevation of the highest obstacle (h) in the level surface area

(see paragraph 2.2.2).

Page 4-6 Par 4.5.3

* 4.5.3 b. Sloping Surfaces.

4.5.3 b. (1) Inner Sloping Surface (see figure 4-4). The inner surface begins at the point on the ASBL corresponding to the location of the 250 feet above ASBL point and extends to point "C". The standard temperature deviation from airport ISA temperature is -30" for the contiguous 48 states, -40" for Alaska, and -20" for Hawaii. If you use the standard deviation, skip to step 3. Othewise, take the following steps to determine the value (SI) of the inner slope:

STEP 1: Obtain the mean low temperature of the coldest month of the year for the last five years of data. If the data is given in Fahrenheit (OF), convert the temperature to Celsius ("C). Use formulas 4.8 and 4.9 to convert between Celsius and Fahrenheit temperatures:

Example

P- 76 - 32 -24.440~ 1 8

Example (1.8 x 24.44) + 32 = 75.9Q°F

STEP 2: Convert the mean temperature into a deviation from International Standard Atmosphere (ISA) using formula 4.10, rounding to the lower whole degree:

Example

STEP 3: Use this deviation or -15OC, whichever is lower, and the GPA to find the slope value from table 4-3.

STEP 4: Determine the Celsius temperature below which the procedure will not be authorized (TNA) (see formula 4.1 1). Round the value to the nearest whole degree.

Par 4.5.3.b Page 4-7

Table 4-3. Sv Considerina GPA and ISA ~erherature Deviation

1)

4.5.3 b. (2) Outer Sloping Surface. The outer s begins at point 'C" and ends at the along-track fix displacement value prior PFAF can be received (see figure 4-4).

STEP 1 : Outer Surface Slope Ratio (s). dalculate the slope of the outer surface using formula 4.12:

STEP 2: Calculate the distance (Dc) from LTP to point C using formula 4.13: $9

Where DZ5() = Distance from LTP to OCS

origin from formula 4.7. Sw = Slope of outer surface

Sv = Slope from table 4-3

8 = Glidepath Angle

c. Calculating the height of the OCS.

c. (1) Inner OCS. Calculate the height (13 above ASBL of the inner surface using formula 4.14:

Where Do = the distance (ft) from RWT to the obstacle

= the distance (ft) from the RWT to the inner surface origin (see paragraph 4.5.3a)

Par 4.5.3b(I)

4.5.3 c. (2) Outer OCS. Calculate the height (03 above ASBL of the outer OCS using formula 4.1 5:

d. OCS Penetrations.

Obstructions should not penetrate the OCS. If the OCS is clear, publish the pDA value. If the height '(h) of the evaluated obstacle is greater than IZ or Oz as appropriate, the OCS is penetrated. Take one of the following actions. These actions are listed in order of preference.

ACTION 1 : Remove or adjust the obstruction location andlor height.

ACTION 2: Raise glidepath angle.

ACTION 3: Adjust DA.

'or equivalent height if in secondary transitional surface (see para- graph 2.2.2a(2)).

e Adjustment of DA for Penetration of INNER SURFACE.

CASE 1 : If the MSL elevation (h) of the obstacle is less than the elevation of point C (C d8vBtion): Use formulas 4.1 6 and 4.17.

Where 8 = glidepath angle

Do = distance (ft) to obstacle from LTP measured parallel to FAC Dc = distance (ft) from LTP to point C (see formula 4.1 3)

p = amount of penetration (ft) Sv = slope of inner surface from table 4-3 LTPE = LTP elevation (ft)

Par 4.5.3c(2) Page 4-9

CASE 2: If h is equal to or greater than the elevation of point C (see formula 4.1 8):

Where h = obstacle MSL elevation

c = elevation (MSL) of point C Sw = Slope of outer surface (see formula 4.12)

f. Adjustment of DA for penetration of OUTER SURFACE (see formulas 4.19 and 4.20 and figure 4-6).

Where DAsdjusted = Adjusted DA (MSL)

Figure 46. DA ADJUSTMENT DA

ADVANCED FINAL SEGMENT VERTICAL SURFACES. RESERVED.

MINIMUMS.

BASIC.

TERPS Volume 1, chapter 3 applies. Use table 9 as applied for localizer final to determine minimum visibility values.

4.7.2

Page 4-1 0

ADVANCED. RESERVED.

Par 4.5.38

CHAPTER 5. MISSED APPROACH SEGMENT (MAS)

CHAPTER 5. MISSED APPROACH SEGMENT (MAS)

The MAS extends from the DA point to the missed approach clearance limit (an airway fix or a holding pattern from which an en route transition may be accomplished). Evaluate obstacles by application of a level surface containing the DA, followed by a 40:1 inclined surface (see figure 5-1). Height loss is assumed after DA. The fix marking the beginning of MAS RNP-level is normally located at the LTP. The fix may be located prior to the LTP to accommodate early turns.(8) Locate the fix identifying the start of the MAS RNP-level change at a point that is at least the along-track fix error value subsequent to the line (see figure 5-1).

5.1 SEGMENT WIDTH.

5.1 .I BASIC.

Segment width splays uniformly from FAS width to MAS width from the a line (figure 5-1) to the MAS RNP-level at 15" relative to course (this takes 7.84 NM for a change from RNP 0.3 to RNP 1.0). For coding purposes, the LTP is assumed to mark the starting point of the MA RNP-level. If a turn is necessary before the splay is complete, expand the splay so it is complete RNP+DTA prior to the turn waypoint. The portion of the expanded splay on the side away from the turn is not evaluated (see turning area in figure 5-1). Locate the turn fix at least a distance equal to RNP+DTA after the line.

Figure 5-1. Missed Approach Area

Initial fix of TF leg. PCG starts here for straight MA. Normally 7.84 NM for chanae from 0.3 to 1 .O

Par 5.0

Angle Bisector \

ADVANCED. Maintaining final segment RNP-bevel in missed approach segment. RESERVED.

STRAIGHT MISSED APPROACH CONSTRUaTION.

Straight missed approach segments are constrpcted using TF leg segments. Secondary areas apply when positive course gjlidance is assured at the initial fix of the TF leg. In figure 5-1, this is the LTP. If the initial fix is not the LTP, it must be located within 5 NM of the & line.

TURNING MISSED APPROACH.

The missed approach route is a series of segments. Turns are accomplished through application of TF segments connected at fly-by fixes (see figure 5-2).

Figure 5-2. Turning Missed Approach Surfaces

(Fly-By Fix)

Page 5-2 Par 5.1.2

LEVEL OCS.

Length and Width.

A level surface overlies the area between @ and (see figure 5-3). The level surface accounts for possible along-track errors inherent with LNAVNNAV. Calculate the distance (Dd) from the LTP to the line, and the distance (Dab) from LTP to the end of the level surface line), using formulas 5.1 and 5.2.

Figure 59. Level MA Surface

I Plan View I

Dab Fix identifying MAS RNP Level change

/ Glidepath

1 250' + adjustments

I I

L v A Level Missed Approach Surface a

Par 5.4 Page 5-3

5.4.2 MA Level Surface Obstacle Clearance.

A MA level OCS overlies the area. The MSL height of the OCS (hlevelws) is

d

determined by formula 5.3.

Where h ~ ~ c s = MSL height of OCS Adjustments = TERPS Volume 1, paragraph 323 adjustments

If the OCS is penetrated, raise the DA the amount of the penetration. Round the result to the next higher 20-foot increment.

5.5 40:1 SURFACE.

5.5.1 Length.

The 40:l surface begins at the & line. Calculate ,surface rise to the obstruction position based on the shortest distance from the obstruction to the aJ line (see figure 5-2).

5.5.1 a. If the clearance limit is reached before the 40:l OCS terminates, continue a climb-in-hold evaluation at the clearance limit.

5.6 OBSTACLE CLEARANCE.

Where obstructions penetrate the OCS, identify the obstruction with the greatest penetration. Increase the DA by the value (D&djusrment) calculated by applying formula 5.4.

Where p = amount of penetration in feet

5.7 MISSED APPROACH CLEARANCE LIMIT ALTITUDE.

5.7.1 Straight Missed Approach Procedures.

Use TERPS Volume 1, paragraphs 2741, and d to establish the charted missed approach clearance limit altitude. Use TERPS Volume 1, paragraph 274c to determine if a climb-in-holding evaluation is required.

5.7.2 Combination Straightfrurning Missed Approach Procedures.

Use TERPS Volume 1, paragraphs 27761 and f to establish the charted missed approach clearance limit altitude. Use TERPS Volume 1, paragraph 277e to determine if a climb-in-holding evaluation is required. 3

Page 5-4 Par 5.4.2

8260.51 Appendix 1

* APPENDIX 1. FORMULAE USED IN RNP CRITERIA r' Para BASIC Primary Area.

Para Secondary Area.

. Calculating Descent Distance (D).

Para . Calculating Descent Gradient (DG).

Para light Track Radius. p

Paragraph 4.1. DETERMINING PRECISION FINAL APPROACH FIXIFINAL APPROACH FIX IPFAWFAF) COORDINATE.

Formula 4.1 F l

8260.51 Appendix 1

Paragraph 4.4.1 b(1). 92 Width at DA (Xw, o DA).

Para at any distance.

Paragraph 4.4.1 c. OCS.

Para vel Surface.

Paragraph 4.5. Inner Sloping Surfaces.

STEP 1

STEP 2

STEP 4

Paragraph 4.5. I - Outer Sloping Surface.

STEP 1

8260.51 Appendix 1

STEP 2

Para 1). Inner OCS.

Para Outer OCS.

Paragraph 4.5.3e. Adjustment of DA for Penetration of INNER SURFACE.

CASE 1

CASE 2

Paragraph 4.5.3f. Adjustment for Penetration of OUTER SURFACE.

Paraara~h 5.4.1. Level OCS Lenath and Width.

Paragraph 5.4.2. MA Level Surface Obstacle Clearance.

8260.51 12/30/02 Appendix 1

Paragraph 5.6. Obstacle Clearance. Formula 5.4 (40×p)×θ DAadjustment = 102

APPENDIX 2. CRlTERlAL COMMENTS

APPENDIX 2. CRlTERlAL COMMENTS

8260.51 Appendix 2

1. Paragraph 1 3.1. Approach Surface Baseline (ASBL). With very few, if any exceptions, tangency to the orthometric geoid mean sea level (MSL) and tangency to the WGS-84 ellipsoid does not result in coincident lines. Therefore, measurements based on ASBL for instrument landing systemlmicrowave landing system (ILSIMLS) may not exactly match the same measurements based on ASBL for WAASILAAS systems to the same runway. The differences, however, are small enough to be considered insignificant (see ICAO Obstacle Clearance Panel working paper 67, Tangent Differences between the Realization of the WGS-84 Ellipsoid and the Geoid).

2. Paragraph 2.2.4. Calculation of Descent Gradient. The point that aircraft begin descent during a turn to a new course has been discussed at length at the TERPS portion of the Aeronautical Charting Forum (ACF). The NBAA, RAA, ALPA, AOPA, DoD, etc., failed to arrive at a consensus opinion. Therefore, for purposes of this document, the worse-case scenario is assumed: Aircraft begin descent when they are established on course. Descent is not considered during the actual turn maneuver. The portion of the initial and intermediate segments available for descent varies with the amount of heading change required at the IF. If the intermediate segment is a continuation of the initial course (no heading change), then D is equal to the distance (L) between the plotted positions of the fixes involved. Where a turn is required at the IF, a portion (X) of the distance from the IAF to the IF, and from the IF to the FAF, is dedicated to turn initiation and regaining course alignment instead of descent.

3. Paragraph 2.2.5. Determining Turning Flight Track Radius - Assumption: Worse case predictable turn radius results from standard rate turns. The formula to calculate turn radius (R) is:

where 4 = bank angle required for standard rate turn, VKIAS= indicated airspeed in knots, and VKTAS= true airspeed in knots. The formula to convert from indicated to true airspeed is:

altitude v,,=0.02( 1 , 000 )VIUI+V,

reduces to ~,,=o.o0002(altitude)~, + V,

The formula to calculate standard rate bank angle (4) is:

+ = tan" (o.o0275~,)

Therefore by substitution:

which reduces to:

R = V , , X 0.005305

* I 8260.51 1 2/30/02 Appendix 2

* 4. Paragraph 2.2.7. Joining Segments of Differing RNR-Levels. The latency values (L) in table 2-2 are estimates. The FAA has not surveyed thg differing equipment suites for latency values. The reaction time of 25 seconds was obtbined from data obtained from past flight test scenarios. Transitions to smaller RNP-levels can require large anticipation distances and warrant consideration of establishing the final segment RNP- level at the IAF.

5. Paragraph 3.0.3a. BASIC lntermediate connection with precision final segment Figure 3-IA assumes the intermediate RNP-level is 1 .O. The width is tapered to the final width over 2 NM. This is possible since the localizer should be captured by this point. If the RNP-level is 0.3, there is no taper, the intermediate segment ends at the PFAF at full width.

6. Paragraph 3.0.5b. lntermediate Segment. Implementation of LNAVNNAV approach procedures has proven the traditional intermediate segment 31 8 fVNM descent gradient limit does not support a seamless transition to a VNAV final segment. A lesser gradient is required to accommodate deceleration.

7. Paragraph 4.4.1 b(1) % Width at DA (XW, s DA). The width of the GQS at DA is equal to the width of the precision "W" surface at DA; therefore, the "W" surface width formula from precision criteria is used.

8. Paragraph 5.0. General. If a fix is located prior to the LTP for early turns, the fix becomes an FTP. Locate the FPCP above the FTP at an elevation that would result in a normal TCH over the actual LTP. For example: TCH=53', GPA=3.1 O, FTP is 1,500' prior to LTP. The FPCP would be located 53'+tan (3.1 ")XI ,500i=134.24 feet above the FTP. Glidepath guidance will not be available after the FTP. The missed approach RNP will be larger than the RNP required for final approach to account for the possibility of a navigation error alert causing the missed approach initiation.

8260.5 1 Appendix 3

RISK ASSESSMENTNALIDATION OF RNP

RISK ASSESSMENTNALIDATION OF RNP

OBSTACLE CLEARANCE SURFACES

Page 1 (and 2)

O

O

RISK ASSESSMENTNALIDATION OF RNP

OBSTACLE CLEARANCE SURFACES

8260.51 Appendix 3

1 .O INTRODUCTION.

The concept of Required Navigation Performance (RNP) is a significant enhancement to navigable airspace design, use, and management. It was developed by the International Civil Aviation Organization (ICAO) Special Committee on Future Air Navigation Systems (FANS) and is an integral part of the communication, navigation, surveillance, and air traffic management (CNSIATM) plan envisioned by the Special Committee. RNP levels address obstacle protection associated with RNP accuracy values. The RNP level (RNP x, where x=0.3, 1,2, etc.), when applied to instrument procedure obstacle evaluation areas, is a variable used to determine a segment primary area half-width value; i.e., total width is * a

OBSTACLE CLEARANCE SURFACES

multiple of the value used to identify the level. Order 8260.51, a proposed Advisory Circular (AC) 90-series, and a proposed AC 20-series, will provide the requirements to ensure safe operations on RN P procedures.

The RNP level is based on the total system error (TSE) allowed in the horizontal dimension-- lateral and longitudinal (cross-track and along-track). For the lateral dimension, the TSE is assumed to be the difference between the true position of the aircraft and the centerline of the route of flight programmed in the NAV system. The TSE is a combination of the navigation system error (which includes area navigation (RNAV) computation error and display system error as well as navigation signal discrepancies) and the flight technical error (FTE). A single accuracy value expresses RNP types in nautical miles. For example, for RNP-1, the TSE is not to exceed 1.0 NM for 95 percent of the flight time on any portion of any single flight. RNP can apply from takeoff to landing with each phase of flight requiring a different RNP type.

At this time, there are no regulations defining requirements for RNP systems operating in the

U.S. National Airspace System (NAS). ICAO has formalized certain standards in ICAO Doc 961 3-ANl397, "Manual on Required Navigation Performance (RNP)". RTCA, a private industry-government supported federal advisory committee, has published a Minimum Aviation System Performance Standards (MASPS) for RNP systems (and has even updated

it once) DO-236A. But there are no binding definitions as to what is and what isn't an RNP airplane in the NAS. This paper assumes certain basic capabilities are inherently part of Required Navigation Performance based systems.

1. The navigation system is capable of locating the aircraft within 1 RNP of its true position 95.0% of the time. (This requirement drives infrastructure requirements in most cases as well as database requirements - see item 6.)

2. Integrity of the positioning accuracy is better than 99.999% per flight hour at 2 x RNP as is integrity against misleading navigation information.

3. Continuity of the required position accuracy is better than 99.99%.

4. The service is available at the required levels more than 99.999% of the time. r' 5. There is some means for the pilot to monitor the navigation system performance of the aircraft. (This information ma$ be on a secondary screen on the FMS but it must

8260.51 Appendix 3

be accessible. The optimal system would combine tqe NAV performance with the current Flight Technical Error (FTE) and display the ibformation in the pilot's primary visual field. But in most cases there must be additiodal training or information available to the pilot for guidance in combining the ndvigation system performance information with the current FTE situation so that the pilot can evaluate the RNP status.)

6. Database standards and processes are in place to ensure that position information on fixes, runways, etc., does not compromise the navigation capabilities of the RNP system.

The risk evaluations presented in section 2 of this paper assume the system is available and that any continuity problems during the operation are not of significant duration. It further assumes that all combinations of misinformation (integrity, database issues, and navigation service performance) are sufficiently small that they do not cause the system to exceed the containment requirements.

RNAV is the primary means of meeting RNP requirements. RNAV operations, within the RNP concept, permit flight in any airspace within prescribed accuracy tolerances without the need to fly directly over ground-based navigation facilities. Any type of navigation system can be used to provide RNP, provided that it meets the required navigation performance

requirements. RNAV equipment operates by automatically determining the aircraft position using inputs from one source, or a combination of sources such as DME, INS, and GPS (with or without augmentation). The primary means for achieving RNP is by the use of RNAV equipment.

RNP extends the capabilities of modern airplane navigation systems by providing real-time estimates of navigation uncertainty, assurance of performance through its containment concepts, and features that ensure the repeatability and predictability of airplane navigation. This precise characterization of airplane performance is key to designing more efficient airspace routes and procedures.

Current RNP system requirements were developed to ensure consistency of flight paths and operations across the fleet. For example, the types of flight plan legs that could make up

RNP route segments were limited and standardized to ensure that all similarly equipped airplanes fly consistent and repeatable paths over the ground for a given airway or procedure. The system also must have available a real-time display of the estimated navigation system accuracy. With an explicit display of the estimated accuracy, the flight crew can monitor trends while the navigation system automatically checks current performance against required performance (i.e., the RNP necessary for the operation). Full RNP systems provide alerts to the flight crew when performance is inadequate for the current operation. Lesser systems may require the crew to monitor the estimated position of uncertainty (EPU) or actual navigation performance (ANP) and determine when that value, combined with the FTE the crew is capable of maintaining, is no longer safe.

This report will provide supporting material justifying values used for determining obstacle clearance zones for certain RNP operations defined in Order 8260.51, including straight, level flight; fly-by turns between two legs of the same RNP; and straight flight through a transition from a higher RNP to a lower one. The supporting arguments assume that the certification process ensures that the systems do meet the RNP requirements.

8260.5 1 Appendix 3

Familiarity with the figures and text in the order is assumed and some references are implied rather than explicitly stated.

2.0 RNP CONTAINMENT ANALYSES.

The analyses cover the basic segment construction and joining guidance contained in the subject order that is employed to construct an RNP approach procedure. They assume navigation service availability and that continuity and integrity problems are not significant enough to affect containment.

2.1 Straight and Level Flight.

Paragraph 2.2.1 of subject order defines the segment width of the RNP primary and secondaryltransition surfaces. A common interpretation of the 95 percent containment requirement for RNP assumes that the aircraft must be within I x RNP of the desired lateral position (intended flight track) at least 95 percent of the time for the entire flight. Assuming a Gaussian distribution of the TSE, the 95 percent requirement would support 99.991 % lateral containment at 2 x RNP and 99.9999996% at 3 x RNP. Most RNP definitions, however, imply that the containment includes longitudinal (along-track) variations as well, so that the 95% containment is in a circular or at least elliptical plane parallel to the ground. This interpretation is complicated by the fact that the longitudinal errors do not include flight technical error (at least, not in the traditional way). But to maintain 95% total containment, the lateral containment must be greater than 95% and the resultant risk of exceeding the 2 or 3 x RNP distances from centerline reduced. If the extreme case of zero FTE is examined, so that the distribution is circular, the lateral containment at 1 x RNP is 98.6%; at 2 x RNP, it is 99.9999%; and at 3 x RNP, it is greater than 99.99999999% (ten 9's) (again assuming Gaussian). In either case, the 3 x RNP surface appears to significantly exceed the 10-7 protection levels provided by conventional systems if the assumption of Gaussian TSE is correct.

Historically, aviation TSE data has been shown to be non-Gaussian with a tendency toward thicker tails, meaning a higher probability of being outside a given boundary. Quantification of just how much higher is a non-trivial process requiring test data that does not yet exist for most RNP type systems. On the other hand, the ability to monitor the current navigation system performance and/or receive an alarm if the TSE approaches an unacceptable level should provide a significant mitigation that will be increasingly important as more RNP systems become available and familiarity with system operation increases.

For Special Aircraft and Aircrew Authorization Required (SAAAR) operations, the 2 x RNP surface does not of itself provide adequate obstacle protection. Depending on the requirements applied and even if the Gaussian assumption is supported, the 2 x RNP surface is either a 99.99% or a 99.9999% surface, both short of conventional safety standards. To compensate for this, additional crew training and/or aircraft equipage is required to obtain the special authorization. This may take the form of training to minimize FTE, setting tighter alarm limits than normal, or other methods that the certifying authority feels provides the additional safety margins to achieve equivalency.

2.2 Fly-by Turns Between Segments With Equal RNP Levels.

8260.51 Appendix 3

IC Paragraph 2.2.6 of subject order addresses the construction of obstacle protection areas for aircraft executing fly-by turns over a junction connecting two segments with equal RNP requirements. Proper execution of a fly-by turn involves initiating the turn sufficiently in advance of the turn waypoint that when the turn is completed, the aircraft will roll out on the outbound course with little or no overshoot. The lead distance (or turn anticipation distance) at which the turn must be initiated is determined by the angle of the turn, the speed of the aircraft, and the bank angle used. A less important but still significant factor in the turn anticipation calculation is the roll rate which the aircraft uses to achieve that bank angle. Notification to the pilot of arrival at the turn anticipation point is provided by visual andlor audible signals that vary from system to system. Guidance wound part or all of the turn is usually available. Normal execution of this maneuver will take the flight track inside the turn waypoint. For large angle turns at high speed, the distance inside can be substantial. Subsequently, the inner boundary must be expanded to accommodate this effect.

The outer boundaries, which are constructed with 2 x RNP and 3 x RNP arcs connecting tangent points on the two segment boundaries, provide prote tion equivalent to the straight segment for aircraft that fly right up to the turn waypoint and i! en turn (such as helicopters). There is no apparent extra protection for aircraft that overshoot the outbound course.

The inner boundaries are determined by calculating a radius of turn, r, (based on the factors discussed above) and constructing arcs of radius rand r + 1 x RNP to connect the inner 3 x RNP and 2 x RNP boundaries, respectively. This produces an increased obstacle clearance area on the inside of the turn, i.e. more than 2 x RNP in the primary and more than 3 x RNP in the secondary. This, in turn, allows additional protection for early turns and compensates for the lack of consideration of roll-in and rollout on the turns. The more severe the turn, the greater is the additional protection.

While protection areas appear to generally provide the same pr greater protection than the straight course, the absence of any apparent overshoot provi$ions may require a higher level of complexity in RNP navigation systems. They must provide compensation for acceleration and strong tail-wind components, both of which tend to produce overshoots on turns. The additional inside protection should provide adequate protectiop for deceleration and head- winds. Additional checks on the capabilities of various syste4s turn algorithms should be considered to ensure a minimal probability of producing overshoots.

The last point is especially significant with regards to SAAAR systems, which do not have a secondary/transition area to provide climb out protection if thd RNP level is exceeded while in a turn. However, SAAAR operations may include RF segmlent capabilities that would provide a fixed course to fly around turns and would substantially mitigate this problem.

2.3 Straight Flight from a Greater to a Lesser RNP Level,

RNP systems perform an immediate transition when passing from a segment of larger RNP value to one of smaller RNP. A common situation would be tve transition from an RNP 1.0 segment to an RNP 0.3 segment on an approach. In this case, an aircraft that was a mile off centerline in the higher RNP segment due to a combination of flight technical error and navigation system error would find itself outside the normal sttaight segment protected airspace which only extends to 3 x RNP or 0.9 NM from centelline. To protect the aircraft in this situation, paragraph 2.2.7 defines a fix distance derived from an equipment latency time, a pilot reaction time, and a climb distance for a 40:l gradient to clear the relevant obstacle. The fix distance should allow the pilot to be alerted to the possibility of being outside

b 1 2/30/02 8260.51 Appendix 3 * protected airspace, react to thealert, and climb to a sufficient altitude to clear the obstacle. If f-\ the distance is not adequate to allow this escape maneuver, then the fix must be backed up farther from the critical obstacle.

' >

Calculation of the climb distance is straightforward and explained in the order and by Equation 2.5 in the order. Derivation of the distance due to the latency and reaction times is equally simple based on the maximum speeds appropriate for the category of aircraft that may be performing the operation.

Unfortunately, no equipment latency time is defined for RNP systems. In fact, some systems that will likely be approved for these operations do not give an alert; therefore, pilot monitoring of the estimated navigation performance and awareness of the current FTE must accomplish this function. The latency time of 10 seconds included in the order is intended to represent a conservative estimate based on experiences with a wide range of navigation systems.

Pilot reaction time data exists from a multitude of test programs, but the variability in alerting methods (or lack thereof) in RNP systems makes selecting a single data set difficult. "Untrained" times in the range of 20 to 25 seconds have been observed in pilot responses to air traffic controller directions. Response times to TCAS alerts have been measured in the

15 to 18 second range. A response time allowance of 25 seconds should represent a conservative value that can be reduced if significant experience with the system shows the reduction to be appropriate.

2.4 Additional Analyses.

As new operations or transitions are defined or clarifications requested, additional paragraphs may be added to this document.

3.0 CONCLUSIONS.

RNP operations as defined in the Order 8260.51 appear to maintain acceptable risk levels in terms of containment provided the certification process ensures compliance with defined RNP requirements. SAAAR operations must be examined carefully to ensure that training or equipage offered as mitigations to decreased coqtainment margins is sufficient compensation for the two or three orders of magnitude increase in containment risk.

The apparent absence of overshoot protection in the fly-by turn dictates that special care also be exercised in consideration of turn algorithms and turn anticipation determination logic. This is particularly true for the SAAAR operations that do not include the secondary1 transition zone.

Page 7 (pnd 8)

U.S. Department of Transportation

Federal Aviation Adminlst ration

Directive Feedback Information

Please submit any written comments or recommendations for improving this directive, or suggest new items or subjects to be added to it. Also, if you find an error, please tell us about it.

Subject: Order 8260.5 1, United States Standard for Required Navigation Performance (RNP)

Instrument Approach Procedure Construction

To: DOT/FAA Flight Procedure Standards Branch, AFS-420 P.O. Box 25082 Oklahoma City, OK 73 125

(Please check all appropriate line items)

An error (procedural or typographical) has been noted in paragraph on page -.

Recommend paragraph on page - be changed as follows: (attach separate sheet $necessary)

In a future change to this directive, please include coverage on the following subject: (briefly describe what you want added):

Other comments:

I would like to discuss the above. Please contact me.

Submitted by: Date:

k I FTS Telephone Number: Routing Symbol: !

FAA Form 1320-1 9 (8-89)

O