Order 8260.58B United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design
This order provides guidance for the design and evaluation of Performance Based Navigation (PBN) Instrument Flight Procedures (IFPs). For the purposes of this order, PBN IFPs are those based on Area Navigation (RNAV) or Required Navigation Performance (RNP) to include transitions to an Instrument Landing System (ILS) or Ground Based Augmentation (GBAS) Landing System (GLS) final segment (see Appendix C and Order 8260.19, Flight Procedures and Airspace, Section 4–6 and Chapter 8 paragraph “Equipment requirements notes”). This order contains guidance that is pertinent to 14 CFR part 95 and 97.
This document is cancelled. Cancelled by 8260.58C. Check the official source before relying on it.
Order 8260.58B
U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
National Policy
ORDER
8260.58B
Effective Date:
08/24/2020
SUBJ: United States Standard for Performance Based Navigation (PBN) Instrument
Procedure Design
This order prescribes standardized methods for designing and evaluating Performance Based Navigation (PBN) instrument flight procedures (IFPs) in the United States and its territories.
Performance Based Navigation (PBN) describes an aircraft's capability to navigate using performance standards and is comprised of Area Navigation (RNAV) and Required Navigation Performance (RNP). RNAV enables aircraft to fly on any desired flight path within the coverage of ground or space based navigation aids, the limits of the capability of the self-contained systems, or a combination of both capabilities. RNP is RNAV with the addition of onboard performance monitoring and alerting capability. A defining characteristic of RNP operations is the ability of the aircraft navigation system to monitor the navigation performance it achieves and inform the crew if the requirement is not met during an operation. The performance requirements of PBN are conveyed to the users through navigation specifications.
This order is to be used by all personnel responsible for the preparation, approval, and promulgation of PBN IFPs.
Rick Domingo Executive Director, Flight Standards Service
Main Page Footer: Distribution - Electronic Only; Initiated By - AFS400
Order 8260.58B › Table of Contents
Table of Contents
Chapter 1. General Information … 1–1
Section 1-1. Purpose … 1–1
1-1-1. Purpose of This Order … 1–1 1-1-2. Audience … 1–1 1-1-3. Where You Can Find This Order … 1–1 1-1-4. What This Order Cancels … 1–1 1-1-5. Explanation of Changes … 1–1
Section 1-2. Basic Criteria … 1–5
1-2-1. General … 1–5 1-2-2. Formulas/Calculations … 1–5 1-2-3. Geospatial Standards … 1–5 1-2-4. PBN Concept … 1–5 1-2-5. Obstacle Evaluation Area (OEA) and Flight Path Construction … 1–7
Section 1-3. Common Criteria … 1-28
1-3-1. Common Criteria … 1-28
Chapter 2. En Route, Standard Terminal Arrivals, Feeder Routes, and Terminal Arrival Areas (TAA) … 2–1
Section 2-1. En Route … 2–1
2-1-1. Air Traffic Service (ATS) Q/T/TK Routes … 2–1 2-1-2. ATS RNP 0.3 Routes (Helicopter only) … 2–1
Section 2-2. Standard Terminal Arrival (STAR) … 2–3
2-2-1. PBN STAR … 2–3
Section 2-3. Feeder Routes … 2–4
2-3-1. Feeder Route … 2–4
Section 2-4. Terminal Arrival Area (TAA) … 2–5
2-4-1. General … 2–5 2-4-2. Approach Procedure … 2–5 2-4-3. Arrival Areas … 2–7 2-4-4. Feeder Route … 2–13
Chapter 3. RNAV (GPS) Approach … 3–1
Section 3-1. General Criteria … 3–1
3-1-1. Applicability … 3–1 3-1-2. Feeder Segment … 3–1 3-1-3. Initial … 3–1 3-1-4. Intermediate … 3–1 3-1-5. Final … 3–6
Section 3-2. General Non-Vertically Guided Final Segment … 3–8
3-2-1. General … 3–8 3-2-2. Alignment … 3–8
i
3-2-3. Area … 3–8 3-2-4. Obstacle Clearance … 3–12 3-2-5. Minimum Descent Altitude … 3–12
Section 3-3. Lateral Navigation with Vertical Guidance Final Segment … 3–13
3-3-1. General … 3–13 3-3-2. Alignment … 3–13 3-3-3. Area … 3–14 3-3-5. Decision Altitude … 3–21 3-3-6. Raising GPA or Adjusting TCH for Penetrating Obstructions … 3–21
Section 3-4. LPV/GLS Final … 3–22
3-4-1. General … 3–22 3-4-2. Alignment … 3–22 3-4-3. Area … 3–22 3-4-4. Obstacle Clearance Surface … 3–23 3-4-5. Decision Altitude … 3–28 3-4-6. Raising GPA for OCS Penetrations … 3–30 3-4-7. Adjusting TCH to Reduce/Eliminate OCS Penetrations … 3–31
Section 3-5. Missed Approach General … 3–33
3-5-1. General … 3–33 3-5-2. Course-to-Altitude (CA) Leg … 3–33 3-5-3. MA Climb Gradient Termination … 3–33
Section 3-6. Missed Approach Section 1 … 3–35
3-6-1. Non-vertically Guided … 3–35 3-6-2. LNAV/VNAV … 3–38 3-6-3. LPV/GLS … 3–40
Section 3-7. Missed Approach Section 2 … 3–43
3-7-1. General … 3–43 3-7-2. Straight Missed Approach … 3–44 3-7-3. Turning Missed Approach … 3–44 3-7-4. Obstacle Clearance Surface … 3–60
Chapter 4. RNAV (RNP) Approach … 4–1
Section 4-1. General Criteria … 4–1
4-1-1. Concept and Design … 4–1 4-1-2. Feeder Segment … 4–2 4-1-3. Initial Segment … 4–2 4-1-4. Intermediate Segment … 4–2
Section 4-2. Final Approach Segment (FAS) … 4–3
4-2-1. General … 4–3 4-2-2. Alignment … 4–5 4-2-3. Area … 4–5 4-2-4. Obstacle Clearance … 4–6
Section 4-3. Missed Approach Segment (MAS) … 4–12
ii
4-3-2. Default MAS OEA Construction … 4–12 4-3-3. RNAV MAS OEA Construction … 4–15 4-3-4. Reduced RNP MAS … 4–16 4-3-5. OCS Evaluation … 4–16
Chapter 5. Departure Procedures … 5–1
Section 5-1. General Criteria … 5–1
5-1-1. General … 5–1
Section 5-2. Straight Departure … 5–3
5-2-1. Straight Departure … 5–3
Section 5-3. Turning Departures … 5–5
5-3-1. Turning Departure … 5–5
Section 5-4. Obstacle Evaluation … 5–29
5-4-1. Obstacle Evaluations … 5–29
Section 5-5. Climb Gradient … 5–36
5-5-1. Climb Gradient … 5–36
Section 5-6. Vector SID … 5–37
5-6-1. General … 5–37 5-6-2. SID Starting with Vector Leg … 5–37 5-6-3. SID Including Vector Legs … 5–37
Appendix A. Use of Historical Wind Studies for Determining Tailwind … A-1
1. Purpose … A-1 2. Acceptable Source … A-1 3. Use of Directional Wind Speeds … A-1
Appendix B. DF Leg Feasibility Analysis … B-1
1. Purpose … B-1 2. Applicability … B-1 3. Analysis … B-1
Appendix C. PBN Transition to ILS/GLS/LPV Final … C-1
1. Purpose … C-1 2. Transition to ILS/GLS/LPV Final … C-1
Appendix D. Vector SID Implementation … D-1
1. Purpose … D-1 2. Vector SID Authorization … D-1 3. Vector SID Application … D-1
iii
a. Chapter 1. › (9) Paragraph 1-3-1.b. Directed use of the most adverse result when…
Chapter 1. General Information
Section 1-1. Purpose
1-1-1. Purpose of This Order. This order provides guidance for the design and evaluation of Performance Based Navigation (PBN) Instrument Flight Procedures (IFPs). For the purposes of this order, PBN IFPs are those based on Area Navigation (RNAV) or Required Navigation Performance (RNP) to include transitions to an Instrument Landing System (ILS) or Ground Based Augmentation (GBAS) Landing System (GLS) final segment (see Appendix C and Order 8260.19, Flight Procedures and Airspace, Section 4–6 and Chapter 8 paragraph “Equipment requirements notes”). This order contains guidance that is pertinent to 14 CFR part 95 and 97.
1-1-2. Audience. All personnel who are responsible for IFP development and/or evaluation.
1-1-3. Where You Can Find This Order. You can find this Order on the FAA Web site.
1-1-4. What This Order Cancels. Order 8260.58A titled “United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design” dated 03/14/2016.
1-1-5. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. Chapter 1.
Table 1-2-1. Greyed out NavSpec blocks that are not used.
Table 1-2-1, Footnote 6. Reworded to match A-RNP selectable values.
Table 1-2-1, Footnote 9. Added Flight Standards approval for using XTT less than 1 for STAR/Feeder/TAA.
Paragraph 1-2-4. Spelled out Navigational Aid for first use of NAVAID.
Paragraph 1-2-5.c(3)(a) and 1-2-5.c(3)(b). Added allowance for rounding to the nearest foot value.
Paragraph 1-2-5.c(3)(b)2. Increased RF with RNP less than 1.0 NM design bank from 20 to 25.49 degrees.
Paragraph 1-2-5.d(3). Deleted restriction for an RF leg radius being less than OEA ½ width. Added a case 2 and multiple steps necessary to construct an OEA for an RF leg radius less than OEA ½ width.
Figure 1-2-11. Added figure depicting new OEA case with an RF radius less than OEA ½ width.
Paragraph 1-3-1.b. Directed use of the most adverse result when computing secondary rise and the obstacle is perpendicular to multiple boundaries.
c. Chapter 3. › (9) Figure 3-4-1. Replaced to support 1200-ft removal.
Paragraph 1-3-1.e(2). Added authorization for an intermediate segment length to exceed 15 NM while within 15 NM of the ARP.
Paragraph 1-3-1.f(2)(b). Removed the word “published” from “published TCH.”
Paragraph 1-3-1.g(3)(c)(1 and 2). Added language to support using wind spiral methodology to ‘turn as soon as practicable’ construction.
Paragraph 1-3-1.h. Limited A-RNP turns to RF legs when using an RNP value less than 1.0 NM.
b. Chapter 2.
Paragraph 2-1-2. Changed Copter to Helicopter.
Paragraph 2-2-1. Added requirement for Flight Standards approval to use an A-RNP 0.3 NM lateral accuracy on a STAR. Removed “/Feeder/TAA” from flight phase.
Paragraph 2-2-1.b. Clarified analysis of joining routes to STARs.
Paragraph 2-3-1. Removed “/STAR/TAA” from flight phase.
Paragraph 2-4-1. Corrected wording from “PBN” to “NavSpec.”
Paragraph 2-4-1. Removed “/STAR/Feeder” from flight phase.
c. Chapter 3.
Paragraph 3-1-2. Removed “/STAR/TAA” from flight phase.
Paragraph 3-1-4.a. Reworded for clarity.
Paragraphs 3-1-4.b(2) and 3-1-4.b(3). Pointed ILS/GLS/LPV to Appendix C for hot temperature capture alignment criteria.
Paragraph 3-1-4.c(2). Clarified RF to LPV/GLS PFAF construction.
Paragraph 3-2-2. Limited LNAV MAP placement to LTP/FTP when combined with an LNAV/VNAV.
Formula 3-3-2. Added definition of OMSL.
Paragraph 3-3-4.b. Added “(89 ft above TDZE)” to describe the level surface.
Paragraph 3-4-2. Removed upper limit of 1200 ft for offset LPV/GLS alignment criteria.
Figure 3-4-1. Replaced to support 1200-ft removal.
e. Chapter 5. › (7) Paragraph 5-4-1.b(4). Added allowance for rounding to the nearest…
Formula 3-4-3. Added definition of OMSL.
Formula 3-5-1. Added definition of OMSL.
Paragraph 3-5-2.a(1). Added allowance for rounding to the nearest foot value.
Paragraph 3-5-2.b. Replaced ‘coded’ with ‘specified’ and added allowance for rounding to the nearest foot value and helicopter PinS criteria.
Paragraph 3-6-1 and 3-6-1.a(2). Added allowance for rounding to the nearest foot value.
Formula 3-6-8. Added definition of OMSL.
Paragraph 3-7-1.b(1). Clarified section 2 start altitude.
d. Chapter 4.
Paragraph 4-1-1. Deleted TF preference and made RF legs the preferred leg type.
Paragraph 4-1-1.c(1). Added language for clarity.
Paragraph 4-2-2. Added instructions to use Formula 4-2-3 to determine minimum FROP distance.
Paragraph 4-2-2.b. Added allowance for rounding to the nearest foot value.
Paragraph 4-2-3. Added language to clarify intent.
Paragraph 4-3-4. Added allowance for rounding to the nearest foot value.
Formula 4-3-6. Added definition of OMSL.
e. Chapter 5.
Paragraph 5-1-1.a(1). Added allowance for rounding to the nearest foot value.
Paragraph 5-1-1.c(2). Added allowance for rounding to the nearest foot value.
Paragraph 5-2-1.a(1). Added allowance for rounding to the nearest foot value.
Paragraph 5-3-1.a(1)(b) Added allowance for rounding to the nearest foot value.
Paragraph 5-3-1.a(1)(b)2. Added allowance for rounding to the nearest foot value.
Paragraph 5-3-1.a(1)(c)1. Added allowance for rounding to the nearest foot value.
Paragraph 5-4-1.b(4). Added allowance for rounding to the nearest foot value.
1-1-5. Explanation of Changes. › f. Appendix E.
Paragraph 5-6-2.a. Added allowance for rounding to the nearest foot value.
f. Appendix E. Deleted Geospatial Standard appendix. The Geospatial Standard will be published in Order 8260.3E.
Section 1-2. Basic Criteria
1-2-1. General.
Order 8260.19, Flight Procedures and Airspace,
Order 8260.42, United States Standard for Helicopter Area Navigation (RNAV), and
a. Navigation Specification (NavSpec). › (1) Performance.
Order 8260.46, Departure Procedures (DP) Program.
c. Scope. This chapter contains only that information common to all PBN IFPs. Criteria which do not have general application are located in the chapter’s specific to the flight phase, navigation type, or application.
1-2-2. Formulas/Calculations. Formulas in this directive use degree calculations. The examples provided use only two decimal places; therefore, the answers are approximate values. Actual calculations must use the maximum number of values after the decimal place for each step. Rounding of the final result should be for documentation purposes only. For the purposes of this order, the term “r” represents the mean radius of the earth used in spherical calculations and is equal to 20890537 feet. For mathematics convention and other common equation terms see Order 8260.3.
1-2-3. Geospatial Standards. PBN IFPs must be evaluated geodetically (see Order 8260.3).
1-2-4. PBN Concept. The PBN concept is m ade up of three interrelated elements: the navigation specification, the Navigational Aid (NAVAID) infrastructure, and the navigation application. These three elements define the minimum required aircraft/system performance used as the basis for the obstacle evaluation areas described in this order.
a. Navigation Specification (NavSpec). The NavSpec is a set of aircraft/aircrew certification and operational approval requirements that support a navigation application within a defined airspace concept. NavSpecs which require on-board performance monitoring and alerting are termed RNP specifications. Those that do not require on-board performance monitoring and alerting are termed RNAV specifications. The NavSpec defines the performance required by an RNAV or RNP system as well as any functional requirements (e.g., ability to conduct curved path legs). See current version of AC 90–100, AC 90–101, AC 90–105, and AC 90–107 for definitions. NavSpecs include:
Performance. The performance required in terms of accuracy, integrity, and continuity.
1-2-4. PBN Concept. › c. Navigation application.
Functions. The functions available to achieve the required performance.
Navigation sensors. The navigation sensors that may be used to achieve the required performance.
Procedures. Flight crew and other procedures to achieve the required performance.
b. NAVAID infrastructure. NAVAID infrastructure relates to space or ground-based NAVAIDS addressed in the NavSpec.
c. Navigation application. Also referred to as flight phase. A navigation application is the operation in which a specific NavSpec and associated performance requirements applies (e.g., Air Traffic Service (ATS) route, IFP segment, etc.).
Table 1–2–1. Navigation Accuracy by NavSpec/Flight Phase
Navigation Specification
Flight Phase En route Domestic
STAR/ Feeder/TAA
Initial Intermediate Final Missed1 Departure
RNAV 2 2 2 2 RNAV 12 1 1 RNP 2 2 RNP 12 1 1 RNP APCH2,3 1 1 0.34/40m5 1
A-RNP2,6, 9 2 or 18 1 or 0.3 0.3 0.3 RNP APCH 0.3 1 or 0.3 RNP AR APCH 1 - 0.1 1 - 0.1 0.3 - 0.1 0.1 - 1 RNP AR DP 0.3 - 1 RNP 0.37 0.3 0.3 0.3 0.3 0.3 0.3
1. Missed approach section 2 only. RNP AR APCH sections 1a and 1b.
2. STAR/Feeder/TAA, departure, initial, intermediate, and missed section 2. Beyond 30 NM from ARP the effective Cross Track Tolerance (XTT)/Along Track Tolerance (ATT) for the purpose of IFP design is 2.
3. RNP APCH part A is enabled by GNSS and baro-VNAV and part B is enabled by SBAS.
4. Part A only.
5. Part B along-track performance is 40 meters; angular performance requirements apply to lateral.
6. A-RNP permits a choice of RNP lateral navigation accuracies in some flight phases. Apply the largest lateral navigation accuracy for the flight phase unless a smaller value is operationally required to achieve the desired ground track.
7. Primarily intended for helicopter operations only. RNP APCH applies to the final flight phase.
8. Remote Continental use 2 (see latest version of AC 90–105 for definition of remote continental).
9. Use of A–RNP STAR/Feeder/TAA or departure XTT less than 1 requires Flight Standards approval.
(1) Length. › (a) Minimum length (fix-to-fix).
1-2-5. Obstacle Evaluation Area (OEA) and Flight Path Construction.
a. Course.
Lateral and longitudinal dimensions. Construct straight-line courses as a geodesic path. Construct parallel and trapezoidal boundary lines as a locus of points measured perpendicular to the geodesic path. Determine OEA lateral boundary relative to course centerline using ellipsoidal calculations.
Vertical dimension (surface elevations). Obstacle clearance evaluation/clearance surfaces are generally defined as either a level or sloping plane relative to a defined origin Mean Sea Level (MSL) elevation. Evaluate the orthometric height above the geoid (MSL) of obstacles and terrain relative to these surfaces.
Alignment. The alignment tolerance is ± 0.03 degrees of all course differentials. The alignment restriction between Track-to-Fix (TF) and Radius-to-Fix (RF) legs is no course change exceeding alignment tolerance. Otherwise, the general alignment restriction at or above Flight Level (FL) 195 is limited to a maximum course change of 70 degrees, while below FL 195 is 90 degrees; however, specific requirements stated in a segment’s chapter/section take precedence. When preceded by a Direct-to-Fix (DF) leg, the alignment restriction applies to both the early and late tracks.
Note: When using pre-established fixes, acceptably small differences in fix coordinates can cause legs to exceed alignment tolerance. The alignment tolerance can be exceeded when the calculated ideal fix coordinates round to match the pre-existing fix coordinates (see Order 8260.19, paragraph 8–5–2).
b. Area dimensions. For IFP design purposes, the term Cross Track Tolerance (XTT) is the larger of basic XTT and the effective XTT associated with a leg. The OEAs defined in this order are the minimum size OEAs authorized; larger OEAs may be developed where operationally advantageous.
Length.
(a) Minimum length (fix-to-fix). Generally, minimum leg length is the lesser of 2 × XTT or 1 Nautical Mile (NM), but where applicable may also be no less than;
1. The sum of the Distance of Turn Anticipation (DTA) for each Fly-by (FB) turn (see Formula 1–2–1).
Note: Not applicable for FB turns of 10 degrees or less.
(1) Length. › (b) RF leg length may be calculated using Formula 1–2–3.
Formula 1–2–1. Distance Turn Anticipation
DTA = R × tan ൬β
2൰
Where: β = magnitude of heading change in degrees R = turn radius
Example:
DTA = 3.52 × tan ൬75
2 ൰
DTA ≈ 2.7
Note: This formula produces a value with the same unit as R.
2. For TF legs following a Fly-over (FO) turn a length sufficient to allow the aircraft to return to course centerline. Determine using Formula 1–2–2.
Formula 1–2–2. TF Minimum Leg Length Following FO Turn
If β < acos൫√3 − 1൯ use:
L=R × sin(β) + 2 × sin ൬acos 1 + cos(β) ൨൰൨ + DTA 2
If β ≥ acos൫√3 − 1൯ use: L = R × ൣsin(β) + 4 −√3 −√3 × cos(β)൧ + DTA
Note: L must not be less than 1 NM
Where: R = turn radius at the first fix β = magnitude of heading change at the first fix DTA = value from Formula 1–2–1 for the second fix
Note: When multiple courses precede the FO fix (e.g., Heading-to-Altitude (VA)–DF legs) use the track resulting in the greatest magnitude of heading change at the first fix.
Example:
L = 5.6 × sin(33) + 2 × sin ൬acos 1 + cos(33) ൨൰൨ + 2.7 2 L ≈ 10.16
Note: This formula produces a value with the same unit as R.
(b) RF leg length may be calculated using Formula 1–2–3. Use in conjunction with Formula 1–2–4 when necessary to calculate an RF leg of a specific length.
Formula 1–2–3. RF Leg Length
L = α × 𝜋𝜋 × R
180 Where: α = degrees of arc R = arc radius
Example:
L = 98.9 × 𝜋𝜋 × 4.2
180 L ≈ 7.25
(1) Length. › (d) Along-Track Tolerance (ATT).
Note: This formula produces a value with the same unit as R.
Formula 1–2–4. Degrees of an Arc
180 × L α = 𝜋𝜋 × R Where: L = arc length R = arc radius
Note: This formula works with any unit so long as L & R share the same unit.
Example:
180 × 7.25 α = 𝜋𝜋 × 4.2 α ≈ 98.90°
(c) Maximum length (fix-to-fix). Maximum Standard Instrument Approach Procedure (SIAP) segment length is as specified in Order 8260.3, Chapter 2. In no case should the length of any PBN leg exceed 500 NM.
(d) Along-Track Tolerance (ATT). OEAs are constructed and evaluated from ATT prior to a leg’s initial fix (early) to ATT past its termination fix (late). ATT is equal to the navigation accuracy associated with the flight phase (see Table 1–2–1). ATT (same or adjacent legs) can overlap when legs meet minimum length requirements.
1. Except where specified otherwise (e.g., intermediate segment) use the ATT specific for the leg being constructed for both early and late ATT.
2. The baseline used for determining early/late ATT area depends on the leg/turn type.
a TF (no turn) and FO turn. ATT is relative to a line perpendicular to the inbound leg at the fix (see Figure 1–2–1).
b FB turn. ATT is relative to the bisector used for OEA construction (see Figure 1–2–2).
c RF. ATT is relative to a line drawn radially from the turn center point. Distance is measured from the fix along the RF arc (see Figure 1–2–3).
Figure 1–2–1. ATT Straight
Figure 1–2–2. ATT Turning
(2) Width. › (b) Width changes.
Figure 1–2–3. ATT RF
Width.
(a) Cross-track tolerance (XTT). The XTT is used to determine the OEA lateral dimensions. The XTT is derived from Table 1–2–1 navigation accuracy for the defined NavSpec and flight phase. Primary area width is 2 × XTT either side of course and secondary area width is 1 × XTT either side of the primary area, if applicable. The XTT for A–RNP and RNP AR is the specified RNP value for the leg being evaluated. Reference to route width is often specified as nautical mile values measured from secondary area edge across the primary area to the secondary edge at the other side. For example, feeder widths may be referred to as “2–4–4–2.”
(b) Width changes. RNP AR APCH, A–RNP, and RNP AR DP width changes occur abruptly at the start fix of a leg with a new RNP. A–RNP width values may only be decreased prior to final and increased on departure and missed approach. For all other IFPs, OEA construction accommodates width changes at the transition to the final approach mode and at the transition to or from the en route mode. See the applicable chapter for width changes at the final approach transition. For the en route transition, legs that cross a point 30 NM from Airport Reference Point (ARP), the OEA primary area width expands or tapers at a rate of 30 degrees relative to course to the appropriate width (see Figure 1–2–4 and Figure 1–2–5). Calculate the total along-track distance required to complete the transition using Formula 1–2–5. Standard Terminal Arrival Route (STAR)/feeder and approach legs designed to cross within 30 NM of the ARP more than once do not change to RNAV 1/RNP 1/A–RNP (terminal mode) until the 30 NM limit is crossed for the last time. A departure or missed approach segment designed to cross a point 30 NM from the ARP more than once changes to RNAV 2/RNP 2/A–RNP (en route mode) and remains expanded when it crosses the boundary the first time. A–RNP width changes for mode transitions at 30 NM from ARP use the 30-degree splay method to/from effective XTT.
1. Non-RF width changes.
a Inbound. The secondary area tapers from en route mode width when the 30-NM point is crossed to terminal mode width abeam the point the primary area is fully tapered. Leg width tapers regardless of fix location within the tapering section unless a turn is associated
with the fix. Delay OEA taper until the turn is complete and normal OEA turn construction is possible.
b Outbound. The secondary area expands from terminal mode width when the 30-NM point is crossed to en route mode width abeam the point the primary area is fully expanded. Leg width expands regardless of fix location within the expansion section unless a turn is associated with the fix. Start the OEA expansion so as to achieve full expansion to en route mode width prior to the turn.
Figure 1–2–4. Non-RF Width Change at 30 NM from ARP
2. RF width changes. Calculate the perpendicular distance from the RF leg track centerline to primary and secondary boundaries at any along-track distance (specified as degrees of RF arc) from the point the track crosses the 30-NM point using Formula 1–2–6 (see Figure 1–2–5). The width transition must be fully contained within a single RF leg.
Formula 1–2–5. RF Width Change Distance at 30 NM from ARP
2 × XTTlarge − 2 × XTTsmall D = tan(30)
Where: XTTlarger = the largest XTT value XTTsmall = the smallest XTT value
Note: This formula works with any unit so long as all XTT values share the same unit.
Example:
D = 2 × 2 − 2 × 1
tan(30) D ≈ 3.46
Formula 1–2–6. RF Leg XTT Change
1ൗ2Widthsmall × Xangle×R×π Boundary= 1ൗ2 Widthlarge D×180
Where: ½ Widthlarge = 2 × largest XTT for primary area or 3 × largest XTT for secondary area ½ Widthsmall = 2 × smallest XTT for secondary or 3 × smallest XTT for secondary area Xangle = angle relative to center point from beginning of taper to point of interest R = arc radius D = along track distance required to complete the XTT change
Note: This formula works with any unit so long as all XTT values share the same unit.
Example:
Boundary=6-
3×10×6.44×π
3.46×180 Boundary≈5.03
Figure 1–2–5. RF Width Change at 30 NM from ARP
c. Turn parameters. For OEA construction, a turn is indicated when the course change exceeds the alignment tolerance of 0.03 degrees (see paragraph 1-2-5.a(3)).
(1) Altitude. › (a) Calculate projected altitude.
Altitude. Calculate the assumed altitude at a turn fix/point as specified below. The calculated assumed altitude need not exceed the maximum anticipated use specified by ATC. For other cases (e.g., Q or T routes, or STAR or Standard Instrument Departure (SID) legs that precede/follow manual termination legs that make it impractical to determine a starting altitude/point) use the highest anticipated altitude at the turn fix based on specified altitudes, airspace, and anticipated use.
Note: Use of the highest anticipated altitude is required even when obstacle clearance is assured for flyability, path repeatability, and airspace/route separation.
(a) Calculate projected altitude. Except for turns inside the Precise Final Approach Fix (PFAF), projected altitudes are calculated using Formula 1–3–8 based on the rise of an assumed vertical path from a specified start point.
1. Final approach segment.
a Turns inside the PFAF. Use the final segment vertical path, i.e., glidepath angle (GPA). Determine the projected altitude by calculating the vertical rise from the Landing Threshold Point (LTP)/Fictitious Threshold Point (FTP) using Formula 1–3–4.
b Turns at the PFAF. There is no projected altitude. Use the specified PFAF altitude.
2. Intermediate and initial approach segments. The vertical path is 250 ft/NM [Category (CAT) A–E] or 400 ft/NM (COPTER). Determine the projected altitude by calculating the vertical path rise fix-to-fix from the start point/altitude to the turn fix. For the first leg, the start point is the PFAF at the specified PFAF altitude. For subsequent legs, start at the end fix of the preceding leg at the assumed fix altitude.
3. Feeder segments and STAR runway transitions that terminate on an Instrument Approach Procedure (IAP). The vertical path is 250 ft/NM (CAT A–E) (COPTER TBD). Determine the projected altitude by calculating the vertical path rise fix-to-fix from the start point/altitude to the turn fix.
a Feeder. For the first leg, start at the Initial Approach Fix (IAF) at the assumed IAF altitude. The start point/altitude for subsequent legs is the end fix at the assumed fix altitude of the preceding leg.
b STARs. For the first leg, start at the IAP fix at the assumed fix altitude. For subsequent legs, start at the end fix preceding leg at the assumed fix altitude. If a STAR transition serves more than one IAP, base the STAR on the IAP with the highest assumed altitude.
4. Missed Approach (MA) and departure (prior to transition route). For MA legs, the vertical path is the higher of 250 ft/NM (CAT A–B), 500 ft/NM (CAT C–E), 400 ft/NM (COPTER), or the specified climb gradient (CG) in effect at the point of interest. For departure legs (all CATs), the vertical path is the higher of 500 ft/NM below 10000 MSL and/or 350 ft/NM 10000 MSL and above (CAT A–E), 400 ft/NM (COPTER) or the specified CG in effect at the point of interest. For MA, the start point for the first leg is the Start-of-Climb (SOC) applicable to the approach type (see applicable chapter). For departures, the start point for the first leg is the Departure End of Runway (DER) at DER elevation.
a Turn-at-altitude. To calculate the highest altitude in the turn used for OEA construction, see paragraph 1-3-1.g(3); otherwise use the specified turn altitude. The start point for subsequent legs is the point along the course centerline where the specified turn altitude is reached. Calculate the vertical rise from the start point measured direct to subsequent fix.
b All other turns. Calculate the projected fix altitude by applying the vertical path rise from the start point/altitude along the course centerline to the subsequent fix/point. For fixes following a DF leg, the course centerline is a direct line from the turn point/fix to the subsequent fix. The start point for subsequent legs is the end fix/point of the preceding leg at the assumed fix/point altitude.
c. Turn parameters. › (2) Airspeed.
(b) Compare to published altitudes. Compare projected altitude(s) to published altitude(s) to include Minimum En route Altitudes (MEAs).
(c) Determine assumed altitude (see Figure 1–2–6). The assumed altitude used for turn construction is:
1. The higher of the projected altitude and any published minimum or mandatory altitude.
2. The lower of the projected altitude and any maximum altitude, to include the overall maximum altitude applicable to the flight phase (e.g., missed approach clearance limit altitude). The maximum altitude at a fix or for the flight phase can also be specified by Air Traffic Control (ATC).
Figure 1–2–6. Assumed Altitudes for OEA Turn Construction
Airspeed. Locate and use the appropriate Knots Indicated AirSpeed (KIAS) from Table 1–2–2. Determine the Knots True AirSpeed (KTAS) for the turn using Formula 1–2–7 based on the assumed altitude at the turn fix/point (see paragraph 1-2-5.c(1)).
(3) Maximum bank angle. › (b) Low altitude transition turns.
Table 1–2–2. Indicated Airspeeds (KIAS)
Flight Phase Indicated Airspeed by CAT
Copter A B C D E At or Above 10000 feet MSL En route, STAR/Feeder/TAA, Initial,
Intermediate, Missed, Departure
150 180 250 300 300 350
Below 10000 feet MSL En route, STAR/Feeder/TAA, Initial,
Intermediate
150 150 180 250 2501 310
Final 90 90 120 140 165 250 Missed Approach (MA), Departure 150 110 150 240 265 310 Minimum Airspeed Restriction Minimum
Airspeed Restriction2
STAR/Feeder/TAA, Initial,
Departure
70 110 140 2003 2103,4 310
Intermediate 70 110 140 180 180 310 Missed Approach 70 100 130 165 185 310 Final 70 Not Authorized
1 Consider using 265 KIAS where heavy aircraft routinely exceed 250 KIAS under 14 CFR § 91.117.
2 Airspeed restrictions may be established at a charted fix to reduce turn radius, avoid obstacles, accommodate ATC request, etc. Use the fewest number of restrictions possible on the same IFP. Especially avoid consecutive restrictions requiring speed changes of less than 20 KIAS in the same or adjoining segments. Flight Standards or military authority approval is required for missed approach restrictions for other than obstacle avoidance.
3 250 at or above 10000 feet MSL except for initial and/or STAR termination fix.
4 200 underlying Class B airspace per 14 CFR § 91.117(c).
Formula 1–2–7. True Airspeed
VKIAS × 171233 × √303 − 0.00198 × alt = VKTAS (288 − 0.00198 × alt)2.628
Where: VKIAS = indicated airspeed for applicable category and segment combination
Example:
165×171233×√303-0.00198×650 VKTAS= (288-0.00198×650)2.628 VKTAS≈170.88
Maximum bank angle.
(a) Bank limited turns (assumed altitude at turn point/fix < 500 feet above airport elevation (rounded to the nearest foot)): 3 degrees.
(b) Low altitude transition turns (assumed altitude at turn point/fix from 500 feet above airport elevation (rounded to the nearest foot) up to and including FL 195):
1. XTT of the leg being constructed ≥ 1.0: 25.49 degrees
2. XTT of the leg being constructed < 1.0: TF turn 20 degrees, RF turn 25.49 degrees
c. Turn parameters. › (5) Turn radius (R).
(c) High altitude transition turns (> FL 195): 5 degrees
(d) FB turns only: The lesser of one-half the track change (five degrees minimum) or the applicable low/high altitude transition bank angle. Where operationally beneficial (e.g., to reduce leg length) an exception to the one-half track change rule is authorized at a fix when the XTT for the outbound leg is not less than 1.0, a succeeding turn fix uses the applicable low/high altitude transition bank angle, and/or the succeeding leg meets minimum length requirements.
Tailwind (VKTW). Calculate the appropriate tailwind for the assumed altitude at the turn fix (see paragraph 1-2-5.c(1)) using Formula 1–2–8. Where operationally advantageous the 99th percentile wind speed values determined from analysis of a five-year locally measured database may be substituted (see Appendix A).
Formula 1–2–8. Assumed Tailwind
VKTW = 0.00198 × alt + 47
Note: If alt – aptelev ≤ 2000, VKTW = 30
Example:
VKTW = 0.00198 × 3400 + 47 VKTW ≈ 53.73
Turn radius (R). The design turn radius value is based on the turn parameters assumed tailwind (see Formula 1–2–8), groundspeed (see Formula 1–2–9), assumed altitude at the turn fix/point (see paragraph 1-2-5.c(1)), and bank angle (see paragraph 1-2-5.c(3)). Calculate R using Formula 1–2–10. For RF turn radius, see paragraph 1-2-5.d(3).
Formula 1–2–9. Groundspeed
If alt >FL 195 use:
0.9941 × alt Vground = lesser of 570 or + 287 100
If alt ≤ FL 195 use:
Vground = lesser of 500 or VKTAS + VKTW
Where: VKTAS = calculated KTAS using alt and applicable KIAS VKTW = calculated or historical tailwind (knots) using alt
Example:
0.9941 × 26500 Vground = + 287 100 Vground ≈ 550.44 knots
d. Turn construction. › (1) Turns at FB fixes.
Formula 1–2–10. Turn Radius
2 Vground R = tan(φ) × 68625.4
For FB turns, if resulting DTA > 20 NM, then:
R = tan(β
20 × 0.5)
Where: β = magnitude of heading change in degrees Vground = ground speed (knots) ϕ = designed bank angle or 5 degrees where > FL 195
Example:
550.442 R = tan(5) × 68625.4 R ≈ 50.46 NM
Formula 1–2–11. RF Bank Angle
2 Vground φ = atan ቆR × 68625.4ቇ
Where: Vground = calculated ground speed (knots) at the highest assumed altitude in the leg R = turn radius (NM)
Example:
550.442 φ = atan ቆ50.46 × 68625.4ቇ
φ ≈ 5.00°
d. Turn construction. When an RNP change is necessary, the construction of the OEA is accomplished using the RNP value of the leg being evaluated extended into the subsequent leg (see Figure 1–2–1, Figure 1–2–2, and Figure 1–2–3).
Turns at FB fixes (see Figure 1–2–7). The following steps detail the construction of the minimum OEA adjacent to a single FB turn fix. The centerlines and/or the lateral boundaries may need to be temporarily extended to achieve tangency with the turn arcs. To complete the OEA for a leg, apply the appropriate construction criteria for the remaining fix in the leg and then truncate and/or connect the components such that the most adverse boundary is created. The following steps detail construction of the minimum OEA for a FB turn fix. An OEA larger than
(2) Turns at FO fixes. › (a) Step 1.
the minimum is acceptable where connecting boundary lines becomes problematic due to turns and leg lengths. Leg lengths must comply with paragraph 1-2-5.b(1).
(a) Step 1. Establish a line through the turn fix that bisects the turn angle. With the origin on the bisector line, scribe an arc that is tangent to the inbound and outbound centerlines using a radius equal to R.
(b) Step 2. Primary area inner boundary. With the origin on the bisector line, scribe an arc that is tangent to the inner primary boundaries of the two legs using a radius equal to R + XTT.
(c) Step 3. Secondary area inner boundary (if applicable). Using the origin from Step 2, scribe an arc that is tangent to the inner secondary boundaries of the two legs using a radius equal to R.
(d) Step 4. Primary area outer boundary. Centered on the turn fix, scribe the primary area outer boundary arc using a radius equal to 2 × XTT.
(e) Step 5. Secondary area outer boundary (if applicable). Centered on the turn fix, scribe the secondary area outer boundary arc using a radius equal to 3 × XTT.
Figure 1–2–7. FB Turn Construction
Turns at FO fixes (see Figure 1–2–8 and Figure 1–2–9).
(a) Step 1. FO turn construction incorporates a delay in start of turn to account for pilot reaction time and roll-in time. Calculate the extension distance using Formula 1–2–12. FO turn construction is not authorized for A-RNP.
(2) Turns at FO fixes. › (f) Step 6.
Formula 1–2–12. Reaction & Roll Distance
VKTAS × 6 Drr = 3600
Where: VKTAS = calculated KTAS using applicable altitude and KIAS combination
Example:
253.62 × 6 = Drr 3600 Drr ≈ 0.42 NM
(b) Step 2. Establish the baseline for construction of the turn expansion area as the line perpendicular to the inbound track at a distance past the turn fix equal to ATT + Drr.
(c) Step 3. Determine R based on bank angle intended for design (see paragraph 1 2-5.c(3)).
(d) Step 4. On the baseline, locate the center points for the primary and secondary turn boundaries. The first is located at a distance R from the non-turning side primary boundary. The second is located at a distance R from the turning side secondary boundary.
(e) Step 5. From these center points construct arcs for the primary boundary of radius R. Complete the secondary boundary by constructing additional arcs of radius R + secondary area width from the same center points.
(f) Step 6. The arcs constructed in Step 5 are tangent to the outer boundary lines of the inbound leg. Construct lines tangent to the arcs based on the first turn point tapering inward at an angle of 30 degrees relative to the outbound track that joins the arc primary and secondary boundaries with the outbound leg primary and secondary boundaries. If the arcs from the second turn point are inside the tapering lines as shown in Figure 1–2–8, then they are disregarded and the expanded area construction is completed. If not, proceed to Step 7.
(2) Turns at FO fixes. › (h) Step 8.
Figure 1–2–8. FO with No Second Arc Expansion
(g) Step 7. If both the inner and outer arcs lie outside the tapering lines constructed in Step 6, connect the respective inner and outer arcs with tangent lines and then construct the tapering lines from the arcs centered on the second center point.
(h) Step 8. The inside turn boundaries are the intersection of the preceding and succeeding leg primary and secondary boundaries.
(3) Radius-to-Fix (RF) Turn. › (b) Step 2.
Figure 1–2–9. FO with Second Arc Expansion
Radius-to-Fix (RF) Turn (see Figure 1–2–10 and Figure 1–2–11). RF legs are used to control the ground track of a turn where obstructions prevent the design of a FB or FO turn, or to accommodate other operational requirements. Incorporation of an RF leg limits IFP availability to some users; therefore, an RNP APCH that requires RF leg capability to fly the procedure requires Flight Standards approval. The RF leg OEA boundaries are parallel arcs. For OEA construction, the RF start point is the radius extended to early ATT and the RF end point is the radius extended to late ATT.
(a) Step 1. Determine the leg R that is required to fit the geometry of the terrain/airspace. Enter this R value into Formula 1–2–11 to verify the calculated bank angle (rounded to the nearest whole degree) is ≤ 25 degrees.
(b) Step 2. Locate the turn center at a perpendicular distance R from the inbound and outbound legs.
(3) Radius-to-Fix (RF) Turn. › (e) Step 5.
(c) Step 3. Construct an arc of radius R from the point on centerline tangent to the inbound leg at the turn fix to point on centerline tangent to the outbound leg at the turn fix. (See paragraph 1-2-5.a(3) for alignment tolerance.)
(d) Step 4. Primary area outer boundary. Construct an arc of radius R + primary area half width from a line originating at the turn center extending radially through the RF start point to a line originating at the turn center extending radially through the RF end point.
(e) Step 5. Secondary area outer boundary (if applicable). Construct an arc of radius R + primary area half width + secondary area width from a line originating at the turn center extending radially through the RF start point to a line originating at the turn center extending radially through the RF end point.
1. Case 1. RF Radius greater than OEA ½ width (primary and secondary if applicable).
a Step 6. Primary area inner boundary. Construct an arc of radius R - primary area half width from a line originating at the turn center extending radially through the RF start point to a line originating at the turn center extending radially through RF end point.
b Step 7. Secondary area inner boundary (if applicable). Construct an arc of radius R - (primary area half width + secondary area width) from a line originating at the turn center extending radially through the RF start point to a line originating at the turn center extending radially through the RF end point.
2. Case 2. RF Radius less than OEA ½ width (primary and secondary if applicable). This construction is authorized for RNP AR APCH, A-RNP, RNP APCH initial and intermediate segments inside 30 NM from ARP, RNP AR DP, and RNP-1 DP prior to 30 NM from ARP.
a Step 6. Construct an angle bisector of the RF leg.
b Step 7. Construct a line tangent to the RF leg at the angle bisector.
c Step 8. Construct an arc with a radius of 3 x XTT that is tangent to the start of the RF and the tangent line at the midpoint of the RF. The centerpoint of this arc is centerpoint 1.
d Step 9. Construct an arc of radius XTT from centerpoint 1.
e Step 10. Construct a line from centerpoint 1 to XTT after the RF end point then radially out from the RF leg centerpoint to the edge of the outer area boundary(s).
f Step 11. Construct an arc with a radius of 3 x XTT that is tangent to the tangent line at the midpoint of the RF and tangent to the end of the RF. The centerpoint of this arc is centerpoint 2.
g Step 12. Construct an arc of radius XTT from centerpoint 2.
h Step 13. Construct a line from centerpoint 2 to XTT prior to the RF start point then radially out from the RF leg centerpoint to the edge of the outer area boundary(s).
i Step 14. Construct a line from centerpoint 1 to centerpoint 2. The area contained within the overlap of the XTT arcs, the line connecting centerpoints 1 and 2 and the RF start and end waypoint ATTs is secondary area. If the XTT arcs don’t overlap, the entirety of the inside turn OEA is primary area.
Figure 1–2–10. RF Turn Construction, Case 1
Figure 1–2–11. RF Turn Construction, Case 2
1-3-1. Common Criteria. › b. Secondary area.
Section 1-3. Common Criteria
1-3-1. Common Criteria. The following common requirements are applicable to PBN IFPs.
a. Descent gradient (DG) calculation. The applicable section of Order 8260.3, Chapter 2 applies, except use Formula 1–3–1 to calculate descent gradient.
Formula 1–3–1. Descent Gradient
r DG = ln ൬r + altb ൰ × r + alte D Where: Altb = beginning altitude (feet) Alte = ending altitude (feet) D = distance (NM) between the points of interest
Example:
DG = ln ൬r + 6500 r r + 3200൰ × 10.36 DG ≈ 318.46 ft/NM
b. Secondary area (when applicable). Obstacles located in secondary areas are subject to less obstacle clearance than those contained in the primary area. Unless otherwise specified, calculate the secondary Required Obstacle Clearance (ROC) using Formula 1–3–2. Where an obstacle requires multiple measurements (e.g., an obstacle is equidistant from multiple primary boundary points, it lies along perpendiculars from multiple primary boundary points, etc.), apply the most adverse result from each of the combined primary/secondary measurements. When the secondary area is less than 1 x XTT per paragraph 1–2–5.d(3)(e)2, Ws for Formula 1–3–2 is equal to 1 x XTT in feet.
(1) Configuration. › (c) Modified T.
Formula 1–3–2. Secondary ROC
dprimary ROCsecondary = (ROCmin + adj) × ቆ1 − ቇ + RASS ws
Where: ROCmin = min. secondary ROC (feet) at primary boundary (see Order 8260.3, Chapter 2) adj = ROC adjustments (feet) such as excessive length of final and precipitous terrain RASS = remote altimeter setting source adjustment (feet) if applicable dprimary = dist. (feet) from primary area boundary to obstacle. Zero (0) if not in secondary ws = secondary area width (feet)
Example:
ROCsecondary = (250 + 74.32) × ൬1 − 405.86
1822.83൰ + 91.69
ROCsecondary ≈ 343.80 feet
c. ATC turns to join initial and intermediate segments. The first leg of an initial and the first leg of an intermediate segment must be a TF that accommodates a 90-degree intercept angle. Use standard turn parameters at the start fix, except a 25-degree bank angle applies. Where a shorter leg is needed, reduce airspeed in increments of not less than five KIAS until the desired length is achieved (see Table 1–2–2).
d. Initial approach segment. Initial approach segments consist of one or more TF or RF legs or a Hold-In-Lieu-of-Procedure Turn (HILPT). Standard length and alignment applies (see paragraph 1-2-5). In some cases, initial segments are optional (see Order 8260.3, paragraph 2-4-1).
Configuration. The default design incorporates a basic T configuration.
(a) Basic T. Two TF leg initial segments intercept the intermediate segment at 90-degree angles.
(b) Course reversal. Basic T configurations normally include a HILPT course reversal initial established at a fix designated as an Intermediate Fix (IF)/Initial Approach Fix (IAF).
(c) Modified T. Where not practical (e.g., maximum DG exceeded) one or both of the T segments and/or the course reversal may be eliminated.
e. Intermediate approach segment. › (1) Alignment.
Figure 1–3–1. Basic T Configuration
Holding pattern. A holding pattern may be incorporated into the initial segment procedure design where an operational benefit can be derived; e.g., arrival holding at an IAF, course reversal pattern at the IF, etc. See Order 8260.3, Chapter 16 for RNAV holding pattern construction guidance.
(a) Arrival holding. Ideally, the holding pattern inbound course should be aligned with the subsequent TF leg (tangent to course at the initial fix of the subsequent RF leg). If the pattern is offset from the subsequent TF leg course, the subsequent leg length must accommodate the resulting DTA requirement. The published holding altitude must be at or above the IAF altitude.
(b) Hold-In-Lieu-of-Procedure Turn. Ideally, establish the minimum holding altitude at the minimum IF fix altitude. In any case, the published holding altitude must result in a suitable descent gradient in the intermediate segment. If the pattern is offset from the subsequent TF leg course, the subsequent leg length must accommodate the resulting DTA requirement.
e. Intermediate approach segment. Intermediate approach segments consist of one or more TF or RF legs. Standard length and alignment rules apply (see paragraph 1–2–5) except as follows for the leg ending at the PFAF (the last leg):
Alignment. Use the smallest amount of course change necessary. No course change is default.
(2) Final segment vertical path. › (b) Threshold crossing height.
Length. For PBN SIAPs, intermediate segment length is independent of the amount of turn at the IF. The default length for CAT A/B is 3 NM. The default length for CAT C/D is 5 NM. The minimum length is as specified in paragraph 1-2-5.b(1). The intermediate segment length may not be greater than 15 NM unless the nominal track of the entire segment is within 15 NM of the ARP. If the intermediate segment exceeds 15 NM and requires a stepdown fix, increase the segment ROC for the segment preceding (as flown) the stepdown fix by five foot per tenth of a track mile between the stepdown fix and the final approach fix. The intermediate segment ROC based on this additive need not exceed 1000 ft. The maximum distance from the stepdown fix to the final approach fix is 15 NM.
f. Final approach segment. SIAPs designed to support Simultaneous Offset Instrument Approaches (SOIA) operations are exempted from standard final segment alignment when compliant with Order 8260.3, paragraph 15–3–5.
Fixes.
(a) Final segment fixes. Establish stepdown fixes and Visual Decent Points (VDPs) as Along-Track Distance (ATD) fixes relative to the Missed Approach Point (MAP).
(b) Obstacles close to a final approach or stepdown fix. Where turns are designed at the PFAF, Order 8260.3, Chapter 2 “General Criteria” applies except for FB turns at the PFAF the 7:1 Obstacle Identification Surface (OIS) starts ATT prior to the angle bisector, and extends 1 NM parallel to the final approach centerline.
Final segment vertical path. By default, PBN IFPs should be designed so that all vertical guidance to the runway is based on common TCH and angles. All vertically-guided PBN approaches charted on the same IFP plate must share common Threshold Crossing Height (TCH) and GPA.
(a) Glidepath Angle (GPA)/Vertical Decent Angle (VDA) (see Order 8260.3, Section 2–6).
(b) Threshold crossing height. The TCH (nearest whole foot) should accommodate the largest aircraft height group normally expected to use the runway and must not be less than the minimum or exceed the maximum TCH. The TCH is based on achieving an acceptable Wheel Crossing Height (WCH). The WCH is the difference between the published TCH and the approximate glidepath-to-wheel height (see Table 1-3-1).
1. The default TCH provides a 30-foot WCH. The minimum WCH is 20 feet and the maximum WCH is 50 feet.
2. Displaced threshold. The TCH over a displaced threshold may result in a WCH of not less than 10 feet provided:
a Pavement equivalent to the strength of the landing runway is present prior to the displaced threshold.
(2) Final segment vertical path. › (c) Vertical path calculations.
b The calculated height of the glidepath over the beginning of the pavement prior to the displaced threshold is within the minimum/maximum TCH values.
(c) Vertical path calculations.
1. Decision Altitude (DA). Calculate the DA distance from the LTP/FTP using Formula 1-3–3. For Localizer Performance with Vertical guidance (LPV)/GLS, see paragraph 3-4-5.
2. PFAF location. To determine the PFAF location, calculate the distance from the LTP/FTP (straight-in aligned procedures) or MAP (circling aligned procedures) to the point the GPA/VDA or design angle intercepts the intermediate segment altitude (see Formula 1 3–3). For straight-in procedures the beginning altitude is LTP/FTP + TCH. For circling aligned procedures, the beginning altitude is the airport elevation + 50.
Table 1-3-1. TCH Requirements
Representative
Aircraft Type
Glidepath-to- Wheel Height
(approximate)
Recommended TCH Remarks
HEIGHT GROUP 1 General Aviation, Small Commuters, Corporate Turbojets, T-38, C-12, C-20, C-21, T-1, Fighter Jets, UC-35, T-3, T-6
10 feet or less 40 feet General Aviation and Reliever airports, which normally include runways <6000 feet long with reduced widths and/or limited weight bearing capability, limiting larger aircraft use. HEIGHT GROUP 2 F-28, B-737, C-9, DC-9, C-130, T-43, B-2
15 feet 45 feet Small Hub and Non-hub commercial service airports with limited air carrier service. HEIGHT GROUP 3 B-727/707/720/757, B-52, C-135, C-141, C-17, E-3, P-3, E-8, C 32
20 feet 50 feet Most primary runways at Medium Hub airports; i.e., runways not normally used by aircraft with glidepathto-wheel heights > 20 feet. HEIGHT GROUP 4 B-747/767/777, DC-10, A-300, B-1, KC-10, E-4, C-5, VC-25
25 feet 55 feet Most primary runways at Large Hub airports.
Note: To determine the minimum allowable TCH, add 20 feet to the glidepath-to-wheel height and to determine the maximum allowable TCH, add 50 feet to the glidepath-to-wheel height.
g. Missed approach and departure. › (1) Sloping Obstacle Clearance Surface (OCS).
Formula 1-3–3. Distance on Baro Glidepath
dBaro = ln ൬r + alte r ൰ × r + altb tan(θ) Where: alte = ending altitude (feet) altb = beginning altitude (feet)
Example:
r + 4500 r dBaro = ln ൬r + 1441.6 + 47൰ × tan(3) dBaro ≈ 57452.70 feet
3. Glidepath altitude. Calculate the altitude of the glidepath at any distance from the LTP/FTP using Formula 1–3–4.
Formula 1–3–4. Altitude on Baro Glidepath
൬d × tan(θ)
r ZBaro = e
൰ × (r + altb) − r
Where: altb = beginning altitude (feet) d = distance (feet) between the points of interest
Example:
൬4708.89 ×tan(3)
r ZBaro = e
൰ × (r + 404.6 + 45) − r
ZBaro ≈ 696.39 feet
g. Missed approach and departure.
Sloping Obstacle Clearance Surface (OCS). The OCS slope is dependent on the starting OCS elevation and a specific obstacle of interest. When calculating the height of the sloping surface, a default slope of 40:1 may be used to determine potential controlling obstructions. The actual OCS slope associated with any given obstacle is calculated using Formula 1-3–5 and the OCS elevation at a point of interest can be found using Formula 1-3–6.
g. Missed approach and departure. › (2) Climb gradient.
Formula 1-3–5. OCS Slope
= OCSslope
ln ቀ r + O
dO
elev ቁ × r r + OCSstart
Where: Oelev = actual or Oadjusted obstacle elevation (feet) OCSstart = starting altitude (feet)of the OCS dO = dist. (feet) from ACstart to obstacle (primary) or point abeam obstacle (secondary)
Example:
6076.12 = OCSslope
ln ቀr + 1152.6
r + 1000.6ቁ × r
OCSslope ≈ 39.98
Formula 1-3–6. OCS Elevation
dOCS r × OCSslope OCSelev = e
൬ ൰ × (r + OCSstart) − r
Where: dOCS = distance (feet)from OCSstart point to the point of interest OCSstart = starting altitude (feet) of the OCS
Example:
OCSelev = eቀ 2591.8
r × 28.5ቁ × (r + 1191.75) − r
OCSelev ≈ 1282.70 feet
Climb gradient. Obstacle clearance in a climbing segment is dependent on the aircraft maintaining a minimum CG to a specified altitude. The minimum CG (also referred to as standard CG) is 200 ft/NM. When one or more obstacle penetrates the default OCS, a single increased CG that provides clearance over all penetrations may be established. A CG greater than 425 ft/NM is not authorized for missed approach. Calculate the minimum climb gradient required to achieve the termination altitude at a given distance using Formula 1–3–7.The aircraft altitude at a point of interest can be found using Formula 1–3–8 and the distance required to achieve an altitude at any CG can be found using Formula 1–3–9.
Formula 1–3–7. Required Climb Gradient
r CG = ln ൬r + CGterm ൰ × r + ACstart DO Where: CGterm = climb gradient termination altitude (feet) ACstart = starting altitude (feet) of the aircraft (e.g., DER elevation or SOC) DO = dist. (NM) from ACstart to obstacle (primary) or point abeam obstacle (secondary)
Example:
CG = ln ൬r + 2626.52 r r + 1402 ൰ × 3.95 CG ≈ 309.98 ft/NM
Formula 1–3–8. Achieved Aircraft Altitude
൬D×Vertpath
r alte = e
൰ × (r + altb) − r
Where: D = distance (NM) between the points of interest Vertpath = aircraft vertical path (ft/NM) altb = beginning altitude (feet)
Example:
alte = eቀ0.76 × 309.98
r ቁ × (r + 320) − r
alte = 555.59 feet
Formula 1–3–9. Climb Distance Between Altitudes
Dclimb = ln ൬r + alte r ൰ × r + altb CG Where: alte = ending altitude (feet) altb = beginning altitude (feet)
Example:
Dclimb = ln ൬r + 3300 r r + 2105൰ × 315 Dclimb ≈ 3.79 NM
(3) Wind Spiral (WS) parameters. › (e) Step 5.
Wind Spiral (WS) parameters. Use the following steps to determine the parameters used in WS construction.
(a) Step 1. Calculate KTAS with using the specified/assumed turn altitude/assumed fix altitude and applicable KIAS. Input this value as the ground speed in Formula 1–2–10 to find the no-wind turn radius.
(b) Step 2. Calculate the Turn Rate (TR) using Formula 1-3–10. Maximum TR is three degrees per second.
Formula 1-3–10. Turn Rate (TR)
180 × VKTAS TR = lesser of 3 or 𝜋𝜋 × R × 3600
Where: VKTAS = KTAS using specified/assumed turn altitude/assumed fix altitude and applicable KIAS R = calculated no-wind turn radius (NM)
Example:
180 × 281.30 TR = 𝜋𝜋 × 4.30 × 3600 TR ≈ 1.04 degrees/second
(c) Step 3. Determine total magnitude of turn.
1. Turn-at-altitude or turn as soon as practicable. Calculate the total turn magnitude by measuring the arc distance (in degrees) along the no-wind turn radius from the course centerline/late-turn baseline intersection to the direct-to-fix line tangent point.
2. Turn at FO fix. Where the next leg is a DF, use turn-at-altitude or turn as soon as practicable methodology. For TF legs, calculate the total turn magnitude by comparing the inbound and outbound tracks.
(d) Step 4. Determine the highest altitude in the turn using the applicable vertical path (see paragraph 1-2-5.c(1)4) starting at the specified/assumed turn altitude/assumed fix altitude plus 1 NM of flight track distance per 12 degrees total turn magnitude.
(e) Step 5. Calculate the wind spiral increase (∆R) relative to the no-wind turn radius for a given incremental turn magnitude using Formula 1–3–11. The incremental turn magnitude is an angular measurement from the wind spiral baseline about the no-wind turn radius center point which ranges from zero to the total turn magnitude.
1-3-1. Common Criteria. › h. A–RNP NavSpec leg usage.
Formula 1–3–11. Wind Spiral ∆R
∆R = VKTW × βincrement
3600 × TR Where:
= incremental turn magnitude at point of interest βincrement VKTW = calculated or historical tailwind (knots) using the highest altitude in the turn TR = calculated turn rate (degrees/second)
Example:
∆R = 51.55 × 35
3600 × 1.04 ∆R ≈ 0.48 NM
Construction baselines. Missed approach/departure construction baselines are commonly identified by the points that they are comprised of, which can be used to mark the beginning, ending, and/or tie-back point for the OEA. When these lines are used to identify tieback points for turn construction, the placement of the point will be in alphabetical order from turn-side to non-turn side. For example, a right turning missed approach with lines C-D and L-L' will have points C and L on the right, while a left turning missed approach will have them on the left.
h. A–RNP NavSpec leg usage. Use of A–RNP legs requires chart note, “Use of FD or AP required.” Except for obstacles excluded by Order 8260.19 paragraph 2–11–4, apply horizontal and vertical accuracy adjustments to obstacles in any segment/leg based on A–RNP. RF turns are the only turn method authorized for turns of greater than 45 degrees when using an RNP value less than 1.0 NM.
b. OEA construction. › (1) Area.
Chapter 2. En Route, Standard Terminal Arrivals, Feeder Routes, and Terminal Arrival Areas (TAA)
Section 2-1. En Route
2-1-1. Air Traffic Service (ATS) Q/T/TK Routes. Q, T, and TK routes may be developed to support en route PBN operations. The NavSpec is RNAV 2 (en route flight phase with associated XTT of 2). Optional NavSpec may be A–RNP (En route flight phase with associated XTT of 2 or 1 as appropriate). Secondary areas apply.
a. General.
Q routes are for use from 18000 feet MSL through FL 450 inclusive.
T/TK routes are for use from as low as 1200 feet Above Ground Level (AGL) up to but not including 18000 feet MSL.
Leg/Fix type. Use TF legs only. Fixes may only be FB waypoints or NAVAIDs.
b. OEA construction.
Area. Except for route termination fixes, apply paragraph 1-2-5. Where applicable, construction is bi-directional.
Construction at route termination fixes. Order 8260.3 paragraph 14–1–2 applies except primary and secondary boundary arcs are centered ATT past the termination fix.
c. Obstacle clearance. Order 8260.3, Section 14–2 applies. Secondary ROC may be calculated as specified in Order 8260.3, Section 14–2 or Formula 1–3–2 (of this order).
d. Altitudes. Order 8260.3, Section 14–3 applies except Minimum Crossing Altitude (MCA) distances are measured from ATT past the fix.
2-1-2. ATS RNP 0.3 Routes (Helicopter only). RNP 0.3 routes may be developed to support en route PBN copter operations. The NavSpec is RNP 0.3 (En route flight phase with associated XTT of 0.3). Secondary areas apply.
a. General.
RNP 0.3 routes are for use from as low as 1200 feet AGL up to but not including 18000 feet MSL.
Leg/Fix type. Use TF legs only. Fixes may only be FB waypoints or NAVAIDs used as FB waypoints.
b. OEA construction.
Area. Except for route termination fixes, apply paragraph 1-2-5. Where applicable, construction is bi-directional.
2-1-2. ATS RNP 0.3 Routes. › d. Altitudes.
Construction at route termination fixes. Order 8260.3 paragraph 14–1–2 applies except primary and secondary boundary arcs are centered ATT past the termination fix.
c. Obstacle clearance. Order 8260.3, Section 14–2 applies. Secondary ROC may be calculated as specified in Order 8260.3, Section 14–2 or Formula 1–3–2 (of this order).
d. Altitudes. Order 8260.3, Section 14–3 applies except MCA distances are measured from ATT past the fix.
2-2-1. PBN STAR. › c. Obstacle clearance.
Section 2-2. Standard Terminal Arrival (STAR)
2-2-1. PBN STAR. A PBN STAR may be established to transition from the en route environment to the terminal environment. The NavSpec is RNAV 1 (STAR flight phase with associated XTT of 1). Optional NavSpec may be RNP 1 or A–RNP (STAR flight phase with associated XTT of 1 [or 0.3 with Flight Standards approval]). For STARs that serve multiple airports, use the most conservative distance to determine where the effective XTT is 2 (see Table 1–2–1 footnote 2). Secondary areas apply, except for A–RNP. Order 8260.3, Section 2–2 applies in conjunction with the following PBN specific criteria.
a. General.
Leg type. Use TF or RF legs, except a heading to a manual termination (VM) or from a fix to a manual termination (FM) leg may be established at the STAR termination.
Fixes.
(a) All fixes prior to the termination fix must be FB.
(b) The termination fix may be either FB or FO depending on whether the STAR connects to a SIAP, the attributes of the common fix, and leg type. For this purpose, the first coded fix of the SIAP (i.e., the start of the SIAP “IF” leg) is considered a FB fix.
1. When the termination fix is a common fix followed by an FM or VM leg, the termination fix attribute must be FO and the SIAP fix should be FB.
2. For other cases, common fix attributes must be identical.
3. When the termination is not at a common fix, the STAR must terminate with a VM or FM leg at a FO fix.
Note: When more than one transition/common route terminates at the same fix, more than one of the above can apply simultaneously. In those cases, the waypoint attribute must be the same on each of the common routes/runway transitions.
b. Area. Apply paragraph 1-2-5 for area construction and alignment. Construction and alignment in paragraph 1-2-5 also applies to the intersection between initial routing of the STAR and the ATS route where it begins.
Note: When the STAR terminates at a fix on a SIAP, paragraph 1-2-5 applies between the last leg of a STAR and the first leg of SIAP. When a STAR terminates in a VM or FM leg ensure the fix altitude is at or above the Minimum Vectoring Altitude (MVA)/Minimums IFR Altitudes (MIA).
c. Obstacle clearance. Apply Order 8260.3, paragraph 2–2–1. Alternatively, Formula 1–3–2 (of this order) may be used to calculate secondary ROC.
2-3-1. Feeder Route. › c. Obstacle clearance.
Section 2-3. Feeder Routes
2-3-1. Feeder Route. A feeder route may be developed as an optional transition from the en route environment to the terminal structure (see Order 8260.19, paragraph 4–6–2). Use TF and/or RF legs. The NavSpec is RNAV 1 (Feeder flight phase with associated XTT of 1). Optional NavSpec may be RNP 1 or A–RNP (Feeder flight phase with associated XTT of 1 or 0.3 as appropriate). Use an effective XTT of 2 where applicable per Table 1–2–1 footnote 2. Secondary areas apply, except for A–RNP.
a. General. Apply paragraph 1-2-5 for course alignment.
b. Area. Apply paragraph 1-2-5 for area construction.
c. Obstacle clearance. Apply Order 8260.3, paragraph 2–3–1. Alternatively, Formula 1–3–2 (of this order) may be used to calculate secondary ROC.
2-4-2. Approach Procedure. › c. Missed approach segment.
Section 2-4. Terminal Arrival Area (TAA)
2-4-1. General. A TAA may be established as an optional feeder/arrival transition from the en route structure. It consists of TAA arrival areas developed in conjunction with an approach procedure utilizing RNAV initial segments. In the TAA arrival areas, the NavSpec is RNAV 1 TAA flight phase. Secondary areas are not applied; however, buffers are defined from each area boundary.
2-4-2. Approach Procedure. Design in accordance with the applicable criteria in conjunction with the following guidance:
a. Initial approach segments.
Use TF legs (FB fixes only) in a basic or modified T configuration only (see paragraph 1-3-1.d).
Maximum segment length is 15 NM.
A HILPT initial segment must be established at the IF/IAF at an altitude compatible with the TAA arrival area altitudes (see paragraph 2-4-3.e). The inbound holding course must be aligned with the intermediate segment.
b. Intermediate approach segment. Establish a single dual purpose IF/IAF using TF (FB fixes only) aligned with the Final Approach Segment (FAS).
c. Missed approach segment. Where possible, design missed approach segments to allow a “direct entry” into a missed approach holding pattern (see Figure 2–4–1). If the missed approach routing terminates at a base area IAF, align the missed approach holding pattern with the initial inbound course (see Figure 2–4–2).
Figure 2–4–1. Default Missed Approach Holding Alignment
Section 2-4. Terminal Arrival Area (TAA) › 2-4-3. Arrival Areas.
Figure 2–4–2. Missed Approach Holding Alignment at T IAF
2-4-3. Arrival Areas. A default TAA contains a straight-in area, a right base area, and a left base area. Each area is defined relative to a specific IAF (see Figure 2–4–3). The boundary between the straight-in area and the base areas is defined by extensions of the T initial segment track centerlines. The boundary between the right and left base areas is an extension of the intermediate segment track centerline.
Figure 2–4–3. Default TAA Arrival Areas
2-4-3. Arrival Areas. › b. Right and left base area.
a. Straight-in area. Construct the base area side boundary by extending a 30-NM line from the IF/IAF through each T initial segment IAF. Construct the outside boundary by connecting the base area side boundary lines with a 30-NM arc centered on the IF/IAF (see Figure 2–4–4). Apply a 4-NM obstacle evaluation buffer on the base area side boundary and a 2-NM buffer on the outside boundary.
Figure 2–4–4. Straight-in Area
b. Right and left base area. The straight-in side boundaries are the initial segment track centerlines from IAF/IF to each IAF extended outward 30 NM. The boundary between the right and left base areas (inside boundary) is an extension of the intermediate segment track centerline. Construct the outside boundaries as 30-NM arcs centered on each IAF from the straight-in side boundary in the appropriate direction (clockwise or counter-clockwise) to the intersection of the intermediate segment track centerline extended (see Figure 2–4–5). Apply a 4-NM obstacle evaluation buffer on the straight-in and inside boundaries and a 2-NM buffer on the outside boundary.
c. Area modification. › (1) Stepdown arcs.
Figure 2–4–5. Right Base Area
Figure 2–4–6. Left Base Area
c. Area modification. Modifications to the default TAA design may be necessary to achieve an acceptable descent gradient or to meet operational requirements.
Stepdown arcs. Areas may be sub-divided using a stepdown arc (see Figure 2–4–7). Stepdown arcs are centered on the fix associated with the area and may not be less than 4 NM from the center fix or within 4 NM of the outer boundary. Only one stepdown arc may be established per area/sector. A 2-NM obstacle evaluation buffer applies from the stepdown arc. The altitude at the stepdown arc must not result in an excessive descent gradient in the associated NoPT initial calculated as length plus stepdown arc radius.
c. Area modification. › (2) Radial sectorization.
Figure 2–4–7. Area Modification; Stepdown Arcs
Radial sectorization. The straight in or extended straight-in area (see paragraph 2-4 3.c) may be divided into up to three sectors defined radially by inbound courses to the IF/IAF (see Figure 2–4–8). Radial sectors can be used alone or in conjunction with stepdown arcs (see Figure 2–4–9). The angular size of a sector may not be less than 30 degrees, except a sector with a side defined by a base area boundary that also includes a stepdown arc may not be less than 45 degrees. A 4-NM obstacle evaluation buffer applies to radial sector boundaries.
Figure 2–4–8. Area Modification; Straight-in Area Radial Sectorization
(3) Base area elimination. › (a) Construction.
Figure 2–4–9. Area Modification; Radial Sectorization and Stepdown Arcs
Base area elimination. One or both of the basic T initial approach segments and its associated base area may be eliminated (see Figure 2–4–10 and Figure 2–4–11).
(a) Construction. The straight-in area construction is extended into the area of the eliminated base area(s). Paragraph 2-4-3.b construction applies to a remaining base area. Paragraph 2-4-3.a applies except the outside boundary is a 30-NM arc connecting the base area side boundary line to the intermediate segment track centerline extended. When both base areas are eliminated, the straight-in area is a 30-NM circle centered on the IF/IAF.
(3) Base area elimination. › (b) No procedure (NoPT) exclusion.
Figure 2–4–10. Area Modification; Right Base Area Elimination
Figure 2–4–11. Area Modification; Both Right and Left Base Area Elimination
(b) No procedure (NoPT) exclusion. The sector associated with an eliminated base area must be excluded from a NoPT designation. A NoPT exclusion area may also be extended from an eliminated base area into the straight-in area when required to meet descent gradient standards.
Section 2-4. Terminal Arrival Area (TAA) › 2-4-4. Feeder Route.
Figure 2–4–12. Area Modification; NoPT Exclusion
d. Obstacle clearance (see Order 8260.3, paragraph 2–3–1.c).
e. Altitude selection. A minimum altitude is specified for each area and sub-sector. Where possible establish a common IAF altitude for the right/left base and straight-in areas. Where not possible, area altitudes must permit establishment of a common altitude at the IF/IAF. Except for areas/sub-sectors excluded from a NoPT designation, the associated IAF altitude may not be lower than the applicable area/sub-sector altitude. Order 8260.3, paragraph 2–4–5.e applies to area/sub-sectors excluded from a NoPT designation.
2-4-4. Feeder Route. Normally one of the TAA areas (excluding obstacle evaluation buffers) will overlie an airway. Where this is not the case, at least one feeder route must be established from the en route structure to the TAA boundary. Order 8260.3, paragraph 2–3–1 applies except alignment must be a direct course to the IF/IAF or right/left base IAF depending on the location of the feeder fix (see Figure 2–4–13).
Figure 2–4–13. TAA with Feeder route
3-1-4. Intermediate. › d. Area.
Chapter 3. RNAV (GPS) Approach
Section 3-1. General Criteria
3-1-1. Applicability. This chapter applies to procedures covered by the RNP APCH NavSpec (LPV, LP, LNAV/VNAV, and LNAV). It also applies to PBN legs that transition to an ILS or GLS final. Incorporation of an RF leg limits IFP availability to some users; therefore, an RNAV (GPS) approach that requires use of an RF leg in the missed approach, intermediate, or in all initials requires Flight Standards approval. See Order 8260.19, Chapter 8 paragraph “Minimums” for lines of RNAV minimums.
3-1-2. Feeder Segment. Construct feeder segments as described in Chapter 2 using one or more TF or RF legs. The NavSpec is RNAV 1 (Feeder flight phase with associated XTT of 1). Optional NavSpec may be A–RNP (Feeder flight phase with associated XTT of 1 or 0.3 as appropriate). Use an effective XTT of 2 where applicable per Table 1–2–1 footnote 2. The minimum XTT is the result of Formula 3-1–1 for A–RNP to LP and LPV/GLS. Secondary areas apply, except for A–RNP.
3-1-3. Initial. Construct initial segments as described in Chapter 1 using one or more TF or RF legs. The NavSpec is RNP APCH (Initial flight phase with associated XTT of 1). Optional NavSpec may be A–RNP (Initial flight phase with associated XTT of 0.3). Use an effective XTT of 2 where applicable per Table 1–2–1 footnote 2. The minimum XTT is the result of Formula 3 1–1 for A–RNP to Localizer Performance (LP) and LPV/GLS. Secondary areas apply, except for A–RNP.
3-1-4. Intermediate. Construct intermediate segments as described in Chapter 1 using one or more TF or RF legs. The NavSpec is RNP APCH (Intermediate flight phase with associated XTT of 1). Optional NavSpec may be A–RNP (Initial flight phase with associated XTT of 0.3). Secondary areas apply, except for A–RNP. Paragraph 1-2-5.b(1)(d) applies except the ATT at the PFAF is based on the applicable final approach navigation accuracy from Table 1–2–1.
a. RF leg. Except when joining an ILS/GLS/LPV final (see Appendix C), an RF leg must end at least 2 NM prior to the PFAF.
b. Alignment (maximum course change at the PFAF). Offset alignment is only authorized when the PFAF is a FB fix.
LNAV and LP. Align the intermediate course within 30 degrees of the final approach course.
LNAV/VNAV. Align the intermediate course within 15 degrees of the final approach course.
c. ILS/GLS/LPV. Apply Appendix C for PBN transitions to ILS/GLS/LPV.
d. Area (see Figure 3–1–1 and Figure 3–1–2).
d. Area. › (2) LP and LPV/GLS.
LNAV and LNAV/VNAV. The intermediate segment primary area tapers uniformly from ±2 NM at a point 2 NM prior to the PFAF to the primary boundary 1 NM past the PFAF. The secondary boundary tapers uniformly from 1 NM at a point 2 NM prior to the PFAF to the secondary boundary 1 NM past the PFAF.
LP and LPV/GLS. The intermediate segment primary area tapers uniformly from ±2 NM at a point 2 NM prior to the PFAF to the primary boundary/X OCS outer boundary abeam the PFAF. The secondary boundary tapers uniformly from 1 NM at a point 2 NM prior to the PFAF to the secondary/Y OCS outer boundary abeam the PFAF. When using a reduced XTT value, use the same XTT value throughout the entire intermediate segment and verify that the final segment supports the selected XTT with Formula 3-1–1. Where the selected XTT is less than the minimum, increase the XTT or decrease the length of final. When the PFAF is located more than 50200 feet from LTP, the minimum XTT value is 0.5 NM. The minimum XTT is the result of Formula 3-1–1. When an RF to an LPV/GLS PFAF is used, comply with Appendix C and taper relative to the RF track.
Formula 3-1–1. Minimum XTT
0.3048 × (FASLength × 0.10752 + 678.496) = MinXTT 1852 × 2
Where: FASLength = length (feet) of the final approach segment
Example:
0.3048 × (50201.07 × 0.10752 + 678.496) = MinXTT 1852 × 2 MinXTT = 0.5
Figure 3–1–1. LNAV, LNAV/VNAV Intermediate
d. Area. › (3) Turn at IF or start of aligned leg prior to PFAF.
Figure 3–1–2. LP, LPV/GLS Intermediate
Turn at IF or start of aligned leg prior to PFAF. When the standard FB turn construction results in boundaries outside the normal primary/secondary widths at the point 2 NM prior to the PFAF, the inside (turn side) boundaries may be constructed as straight lines from the tangent points on the turning construction arcs to the applicable final segment boundaries (see Figure 3–1–3 and Figure 3–1–4). Redesign if straight line connections result in an area less than normal primary/secondary area width in the leg prior to PFAF.
(4) Offset construction. › (a) Step 1.
Figure 3–1–3. Turn at IF, Example LNAV, LNAV/VNAV
Figure 3–1–4. Turn at IF, Example LP, LPV/GLS
Offset construction. Where the intermediate course is not an extension of the final course, use the following construction techniques.
(a) Step 1. Construct line A perpendicular to the intermediate course 2 NM prior to the PFAF.
(4) Offset construction. › (f) Step 6.
(b) Step 2. Construct line B perpendicular to the intermediate course extended 1 NM past the PFAF.
(c) Step 3. Construct the inside turn boundaries by connecting the points of intersection of line A with the turn side intermediate segment boundaries with the intersection of line B with the turn side final segment boundaries.
(d) Step 4. This step is dependent on procedure.
1. LNAV and LNAV/VNAV (see Figure 3–1–5). Construct arcs centered on the PFAF of 1 NM and 1.3-NM radius on the non-turn side of the fix.
2. LP and LPV/GLS (see Figure 3–1–6). Connect lines from the point of intersection of line A and the outside primary and secondary intermediate segment boundaries to the final segment primary and secondary final segment lines at a point perpendicular to the final course at the PFAF.
(e) Step 5 (applicable to LNAV and LNAV/VNAV Only). Connect lines from the point of intersection of line A and the outside primary and secondary intermediate segment boundaries to tangent points on the arcs constructed by Step 4.
(f) Step 6 (applicable to LNAV and LNAV/VNAV Only). Connect lines tangent to the arcs created in Step 4 that taper inward at 30 degrees relative to the Final Approach Course (FAC) to intersect the primary and secondary final segment boundaries as appropriate.
Figure 3–1–5. Offset Intermediate, Example LNAV
c. FAS data block. › (2) Length offset.
Figure 3–1–6. Offset Intermediate, Example LPV/GLS
3-1-5. Final. Construct final segments as described in Section 3–2 using one or more TF legs. RF legs and TF turns are not authorized. The NavSpec is RNP APCH Final flight phase (with associated XTT of 0.3 NM for part A [LNAV and LNAV/VNAV] and 40 meters for part B [LP and LPV/GLS]). Secondary areas apply.
a. General. Paragraph 1-3-1.f applies except see paragraph 3-4-1 for LPV/GLS exceptions.
b. The final segment OEA primary and secondary boundaries follow the intermediate segment OEA primary and secondary boundaries from ATT prior to the PFAF to the applicable taper connection point and includes offset intermediate construction (see Figure 3–1–1, Figure 3–1–2, Figure 3–1–3, Figure 3–1–5, and Figure 3–1–6).
c. FAS data block (see Figure 3–1–7). The FAS data block is documentation requirement used to define the lateral and vertical paths unique to SIAPs with LP, LPV, or GLS minimums. FAS data includes the following fields:
Flight Path Alignment Point (FPAP). The FPAP is defined by geodetic coordinates. When the FAC is aligned with the Runway Centerline (RCL), find the FPAP by extending a geodesic line from the LTP toward the DER a distance equal to the greater of the runway length or 9023 feet. For offset procedures, the FPAP is located on the extension of the desired final approach course at a distance from the FTP that provides the appropriate lateral course width.
Length offset. The length offset value is the distance between the departure end of runway and the FPAP, rounded to the nearest eight-meter value. It defines the location where lateral sensitivity changes to missed approach sensitivity. For offset procedures and where the FPAP is located at the departure end of the runway, length offset is zero (0).
(3) Course width at threshold. › (b) LGSA.
Course width at threshold. The course width at threshold is defined by the GNSS azimuth reference point (GARP) and the lateral guidance sector angle (LGSA) using Formula 3– 1–2. Convert the result to meters and round to the nearest 0.25-meter increment.
(a) GARP. The GARP is a point located 1000 feet beyond the FPAP on the extension of the FAC/RCL geodesic line. This point is used by the airborne system as the origin of the lateral guidance sector.
(b) LGSA. The LGSA originates at the GARP and is the angular dimension of lateral guidance relative to the FAC. The LGSA angle ranges from not more than ±2 degrees to not less than ±1.5 degrees.
Figure 3–1–7. FAS Data Block
Formula 3–1–2. Course Width At Threshold
Coursewidth = greater of 350 feet or tan(1.5) × dGARP
Where: dGARP = distance (feet) from the LTP/FTP to the GARP
Example:
Coursewidth = tan(1.5) × 13560.66 Coursewidth ≈ 355.10 feet Coursewidth = 108.25 meters
3-2-3. Area. › a. LNAV.
Section 3-2. General Non-Vertically Guided Final Segment
3-2-1. General. This section contains obstacle evaluation criteria for LNAV and LP nonvertically guided approach procedures. LP is not applicable if straight-in minimums are not authorized (see paragraph 3-2-2.b and Order 8260.3 paragraph 2–6–2). Do not develop a new LP to a runway where an LNAV/VNAV or LPV can be developed for at least one approach CAT, regardless of minima.
3-2-2. Alignment. Optimum non-vertically guided procedure final segment alignment is with the runway centerline extended through the LTP. When published in conjunction with a vertically-guided procedure, alignment must be identical with the vertically guided final segment. TF-TF turns are not allowed in the FAS. The latest point the MAP can be located is LTP/FTP. When an LNAV procedure is combined with an LNAV/VNAV, the MAP must be located at LTP/FTP.
a. Straight-in with offset alignment. When the final course must be offset, it may be offset up to 30 degrees (published separately from vertically guided) when the following conditions are met:
Offset ≤ 5 degrees. Align the course through LTP.
Offset > 5 degrees and 10 ≤ degrees. The course must cross the runway centerline extended at least 1500 feet prior to LTP (5200 feet maximum).
Offset > 10 degrees and ≤ 20 degrees. The course must cross the runway centerline extended at least 3000 feet prior to LTP (5200 feet maximum). For offsets > 15 degrees, CAT C/D minimum published visibility 1 SM, minimum height above touchdown (HAT) of 300 feet.
Offset > 20 to 30 degrees (CAT A/B only). The course must cross the runway centerline extended at least 4500 feet prior to the LTP (5200 feet maximum).
Note: Where offset alignment as specified above cannot be attained and the final course does not intersect the runway centerline or intersects the centerline more than 5200 feet from LTP, and an operational advantage can be achieved, the final may be aligned to lie laterally within 500 feet of the extended runway centerline at a point 3000 feet outward from LTP. For the purposes of OEA construction, use the Final End Point (FEP) as the FTP (see Order 8260.3, paragraph 2–6–2). This option requires Flight Standards approval.
b. Circling. The optimum final course alignment is to the center of the landing area, but may be to any portion of the usable landing surface. The latest point the MAP can be located is the FEP. For the purposes of OEA construction, use the FEP as the FTP.
3-2-3. Area.
a. LNAV.
a. LNAV. › (2) Width.
Length. The OEA begins 0.3 NM prior to the PFAF and ends 0.3 NM past the LTP/FTP. Segment length is the distance from the PFAF location to the LTP/FTP. The maximum length is 10 NM.
Width. The final segment OEA primary and secondary boundaries are coincident with the tapering intermediate segment boundaries from a point 0.3 NM prior to the PFAF to a point 1.0 NM past the PFAF. From this point to 0.3 NM past the LTP/FTP, the primary OEA boundary is ± 0.6 NM from course centerline. A 0.3-NM secondary area is located on each side of the primary area. Determine the primary and secondary area widths in this tapering area using Formula 3–2–1.
Figure 3–2–1. LNAV Final Segment OEA
3-2-3. Area. › b. LP.
Formula 3–2–1. Tapering Area Width
1.4 × Dtaper 1ൗ2 Wp = + 0.6 3
0.7 × Dtaper Ws = + 0.3 3
Where: Dtaper = along track distance (NM) from end of taper in the final segment to the point of interest
Example:
1.4 × 1.3 1ൗ2 Wp = + 0.6 3 1ൗ2 Wp ≈ 1.21NM
0.7 × 1.3 Ws = + 0.3 3 Ws ≈ 0.60 NM
Note: This formula may only be used when the intermediate and final legs are aligned.
b. LP.
Figure 3–2–2. LP Final OEA
(2) Width. › (b) Secondary.
Length. The OEA begins 40 meters prior to the PFAF and ends 40 meters past the LTP/FTP. Segment length is the distance from the PFAF location to the LTP/FTP. The maximum length is 10 NM.
Width.
(a) Primary. The perpendicular distance from the course centerline to the outer boundary of the primary area is a constant 700 feet from a point 40 meters past (inside) the LTP/FTP to a point 200 feet prior to (outside) the LTP/FTP. It expands from this point in a direction toward the PFAF. Calculate primary half width from the 200-foot point to a point 50200 feet from LTP using Formula 3–2–2. The value of primary half width beyond the 50200-foot point is 6076 feet.
Formula 3–2–2. Primary Area Half Width
1ൗ2 wp = 0.10752 × dLTP + 678.496
Where: dLTP = along track distance (feet) from LTP to point of interest
Note: 200 feet ≤ dLTP ≤ 50200 feet
Example:
1ൗ2 wp = 0.10752 × 30308.58 + 678.496 1ൗ2 wp ≈ 3937.27 feet
(b) Secondary. The secondary width is a constant 300 feet from a point 40 meters past (inside) the LTP/FTP to a point 200 feet prior to (outside) the LTP/FTP. It expands from this point in a direction toward the PFAF. Calculate secondary width from the 200-foot point to a point 50200 feet from LTP using Formula 3–2–3. The value of secondary width beyond the 50200-foot point is 2500 feet.
Formula 3–2–3. Secondary Area Width
ws = 0.044 × dLTP + 291.2
Where: dLTP = along track distance (feet) from LTP to point of interest
Note: 200 feet ≤ dLTP ≤ 50200 feet
Example:
ws = 0.044 × 30308.58 + 291.2 ws ≈ 1624.78 feet
Section 3-2. General Non-Vertically Guided Final Segment › 3-2-5. Minimum Descent Altitude.
3-2-4. Obstacle Clearance. The minimum ROC in the primary area is 250 feet. The minimum ROC in the secondary area is 250 feet at the primary boundary, tapering uniformly to zero feet at the outer edge. Order 8260.3, Chapter 3 precipitous terrain, remote altimeter, and excessive length of final adjustments apply. Calculate secondary ROC value in accordance with paragraph 1-3-1.b.
3-2-5. Minimum Descent Altitude. The MDA value is the sum of the controlling obstacle MSL plus the applicable ROC application from paragraph 3-2-4. Round the sum to the next higher 20-foot increment; e.g., 623 rounds to 640. The minimum HAT value is 250 feet.
3-3-2. Alignment. › c. Offset > 10 degrees and ≤ 15 degrees.
Section 3-3. Lateral Navigation with Vertical Guidance (LNAV/VNAV) Final Segment
3-3-1. General. An LNAV/VNAV approach is a vertically-guided approach procedure using baro-VNAV or WAAS VNAV for the vertical guidance. Obstacle evaluation is based on the LNAV OEA dimensions, level surface OCS based on ROC, and a sloping baro-VNAV OCS. ROC adjustments for excessive length of final do not apply.
a. Vertical Path restrictions. The true vertical path provided by baro-VNAV is influenced by temperature variations; i.e., during periods of cold temperature, the effective glidepath may be lower than published and during periods of hot weather, the effective glidepath may be higher than published (see paragraph 3-3-4.a(1) and Order 8260.19 paragraph 4–6–8).
b. Other restrictions. LNAV/VNAV approach procedures at airports where Remote Altimeter Setting Source (RASS) is in use or where the final segment overlies precipitous terrain must be annotated to indicate the approach is not authorized for baro-VNAV systems.
3-3-2. Alignment. Optimum final segment alignment is with the runway centerline extended through the LTP. TF-TF turns are not allowed in the FAS. Where lowest minimums can only be achieved by offsetting the final course, it may be offset up to 15 degrees when the following conditions are met:
a. Offset ≤ 5 degrees. Align the course through LTP.
b. Offset > 5 degrees and ≤ 10 degrees. The course must cross the runway centerline extended at least 1500 feet (5200 feet maximum) prior to LTP.
c. Offset > 10 degrees and ≤ 15 degrees. The course must cross the runway centerline extended at least 3000 feet (5200 feet maximum) prior to LTP.
Note: For paragraphs 3-3-2.b and 3-3-2.c, determine the effective DA distance using Formula 3–3–1. This distance can be used in Formula 1–3–4 to determine the required altitude.
3-3-4. Obstacle clearance surface (OCS). › a. Sloping OCS.
Formula 3–3–1. Offset Alignment Minimum Effective DA distance
VKIAS
2 × tan(aoffset × 0.5) × 1852 dDAeffective = tan(18) × 68625.4 × 0.3048 + dLTP
Where: VKIAS = indicated final approach airspeed (knots) for applicable category aoffset = degrees of offset between the final course and runway centerline extended dLTP = distance (feet) from LTP to the final course and runway centerline extended intersection
Example:
1652 × tan(12.5 × 0.5) × 1852 dDAeffective = + 4300.67 tan(18) × 68625.4 × 0.3048 dDAeffective ≈ 5113.16 feet
3-3-3. Area. Apply paragraph 3-2-3.a.
3-3-4. Obstacle clearance surface (OCS). In the primary area, the elevation of the OCS at any point is the elevation of the OCS at the course centerline abeam it. The OCS in the secondary area is a 7:1 surface sloping upward from the edge of the primary area OCS perpendicular to the flight track (see Formula 3–3–2 and Figure 3–3–1). The controlling obstacle is the obstacle that having penetrated the sloping OCS requires the highest GPA or most adverse DA or an obstacle that penetrates the level OCS that causes the most adverse DA. See latest version of Order 8260.3, Section 10–6 for obstacle assessment.
Formula 3–3–2. Secondary Area Adjusted Obstacle Elevation
OBSY − 1ൗ2 wp Oadjusted = OMSL − 7
Where: OMSL = obstacle MSL elevation OBSY = perpendicular distance (feet) from the final approach centerline to the obstacle 1ൗ2 wp = perpendicular distance (feet) from final approach centerline to primary area boundary
Example:
OBSY − 1ൗ2 wp Oadjusted = OMSL − 7
Oadjusted = 3841.6 − 4253.28 − 3645.67
7 Oadjusted ≈ 3754.80 feet
a. Sloping OCS (see Order 8260.3, paragraph 2–1–4). The primary area OCS slope varies based on critical temperatures and designed glidepath angle.
Figure 3–3–1. LNAV/VNAV Final Segment OCS
Critical temperatures.
(a) Average cold temperature (ACT). In order to determine the critical low temperature, the ACT must first be established.
(1) Critical temperatures. › (a) Average cold temperature (ACT).
1. ACT based on historical temperature data.
a Source. The National Oceanic and Atmospheric Administration (NOAA), National Climatic Data Center (NCDC) is the official government source for historical temperature data.
b Reporting period. Reporting periods are established in calendar years (January through December) and must have a complete temperature record for the airport for the entire period. Ideally use the five full year period prior to the current year. If temperature data is incomplete, use the longest continuous period with complete data starting not more than six years prior to the current year. The minimum reporting period is not less than three full calendar years.
Example: The current date is in calendar year (CY) 2015. The ideal reporting period is January 1, 2010 to December 31, 2014; however, temperature data is only complete up to November 2014. Since the earliest allowable year for ACT determination is 2009, the specialist chooses a reporting period from January 1, 2009 to December 31, 2013.
c Calculate the ACT as follows:
1 Find the coldest month. For each year in the reporting period, find the month with the lowest average temperature. When two or more months have the same average temperature, chose the month with the lowest single day temperature.
Example: Jan 2009: 45.4°F; Dec 2010: 44.7°F; Dec 2011: 43.4°F; Feb 2012: 42.2°F; Jan 2013: 45.0°F.
2 Find the lowest temperature in the coldest month. Find the lowest reported temperature in each of the coldest months.
Example: Jan 2009: 37°F; Dec 2010: 35°F; Dec 2011: 35°F; Feb 2012: 29°F; Jan 2013: 35°F.
3 Average the lowest temperature. When Fahrenheit values are used, convert the result to Celsius. Round the Celsius value to the next warmer whole degree; e.g., -15.00 remains -15; -14.99 becomes -14. The resultant rounded value is the ACT.
Example:
ACT = 37 + 35 + 35 + 29 + 35
5 ACT = 34.20°F ACT = (34.20 - 32)/1.8 ≈ 1.22°C ACT = 2°C
2. ACT based on standard ∆ISA. When historical temperature data is not available, determine ACT using a standard cold temperature deviation below airport ISA (∆ISA).
using Formula 3-3–3:
a Calculate airport ISA. Calculate the airport ISA in degrees Celsius
Formula 3-3–3. Airport ISA
ISAairport = 15 − 0.00198 × aptelev
Example:
ISAairport = 15 − 0.00198 × 5433.8 ISAairport ≈ 4.24°C
b Determine standard ∆ISA. Select the standard ∆ISA for the airport using Table 3–3–1:
Table 3–3–1. Standard ∆ISA Values
Airport Location
Value Below Airport ISA°C
Conus -30°C Alaska -40°C Hawaii and -20°C US territories
c Determine the ACT. Add the standard ∆ISA deviation to the airport ISA value and round the calculated value to the next warmer whole degree; e.g., -15.00 remains -15; -15.01 through -15.99 becomes -15. The resultant rounded value is the ACT.
(1) Critical temperatures. › (b) Determining the critical low and high temperatures.
Example: ACT = −30 + 4.24 ACT ≈−25.76°C ACT = −25°C
(b) Determining the critical low and high temperatures. Normally, the critical low temperature limit is the calculated ACT. Where the ACT results in an effective glidepath of less than 2.5 degrees, the temperature limit is raised to achieve the required glidepath angle. The critical high temperature limit is the temp that yields an effective glidepath of 1.13 times the maximum allowed glidepath angle for the fastest designed category (not to exceed 54 degrees Celsius). Use Formula 3–3–4, Formula 3–3–5, and Formula 3–3–6 to find both the critical low and critical high temperature.
Formula 3–3–4. Temperature Induced DA Deviation
d250×tan(θTemp) ∆DATemp = e r × (r + LTPelev + TCH) − (r + TDZE + 250)
Where: d250 = distance (feet) from LTP to a point 250 feet above touchdown zone elevation (TDZE) using the designed GPA θTemp = 2.5 for low temp deviations or 1.13 × the maximum allowable GPA of the fastest CAT for high temp deviations.
Example:
3805.69×tan(2.5) ∆DATemp = e r × (r + 5321.8 + 55) − (r + 5326.3 + 250)
∆DATemp ≈−33.26 feet
Note: This calculation is accomplished twice. Once for low and once for high temperature deviations.
Formula 3–3–5. ∆ISA Adjusted
∆DATemp × [288 − 0.5 × 0.00198 × (TDZE + 250)] = ∆ISAadjusted 250 −∆DATemp
Where: ∆DATemp = calculated maximum DA deviation if flown at the respective critical temperatures
Example:
−33.30 × [288 − 0.5 × 0.00198 × (5326.3 + 250)] ∆ISAadjusted = 250 + 33.30 ∆ISAadjusted ≈−33.20°C
Note 1: This calculation is accomplished twice. Once for low and once for high temperature deviations.
a. Sloping OCS. › (2) OCS slope.
Formula 3–3–6. Adjusted ACT
ACTadjusted = ISAairport + ∆ISAadjusted
Where: ISAairport = International Standard Atmosphere temperature °C for the airport ∆ISAadjusted = ISA adjustment (°C) required to achieve the respective low or high temp GPA
Example:
ACTadjusted = 4.24 − 33.20 ACTadjusted ≈−28.96° ACTadjusted ≈−28°
Note 1: CriticalLow = warmer of ACT or ACTadjusted rounded to the warmer whole degree.
Note 2: CriticalHigh = colder of 54°C or ACTadjusted rounded to the colder whole degree.
Note 3: ΔISALow = CriticalLow – ISAairport
(c) High temperature descent rate. Use Formula 3–3–7 to determine the maximum expected descent rate at standard and critical high temperatures (see Order 8260.19, paragraph 8–7–1).
Formula 3–3–7. Descent Rate
dr = (VKTAS + 10) × 1852 60 × tan(θ) × 0.3048 3600
Where: VKTAS = KTAS using 250 feet above TDZE and final approach KIAS for fastest CAT θ = either designed GPA or 1.13 × maximum allowable GPA for the fastest CAT
Example:
dr = (184.10 + 10) × 1852 60 × tan(3.50) × 0.3048 3600 dr ≈ 1202.23 feet/minute
OCS slope. The OCS slope and origin are determined using Formula 3–3–8, Formula 3–3–9, and Formula 3–3–10:
൰
Formula 3–3–8. OCS Slope
1 = OCSslope tan(θ) × ൣ0.928 + 0.0038 × (CriticalLow − ISAairport)൧
Where: CriticalLow = calculated temperature (°C) that ensures no less than a 2.5° GPA ISAairport = International Standard Atmosphere temperature (°C) for the airport
a. Sloping OCS. › (4) Sloping OCS DA adjustment.
Example:
1 = OCSslope tan(3) × [0.928 + 0.0038 × (−28.96 − 4.24)] OCSslope ≈ 23.80
Formula 3–3–9. Sloping OCS Origin
TDZE + 250 − (LTPelev + TCH) = dorigin tan(θ)
Example:
5326.3 + 250 − (5321.8 + 55) = dorigin tan(3) dorigin ≈ 3806.69 feet
Formula 3–3–10. Distance from LTP that the Sloping OCS Application Begins
dOCS = dorigin + r × OCSslope × ln ൬TDZE + 89 + r
r + LTPelev
Where: 𝑑𝑑𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜𝑜 = distance (feet) from LTP to OCS origin
Example:
dOCS = 3806.69 + r × 23.80 × ln ൬5326.3 + 89 + r ൰ r + 5321.8 dOCS ≈ 6031.42 feet
Obstacle accuracies/ROC adjustments. If the controlling obstacle is within the sloping OCS area, apply the non-RNP procedure evaluation sequence based on the sloping surface evaluation method (see Order 8260.19, paragraphs 2–11–3 and 2–11–4). Do not apply Order 8260.3, Chapter 3 precipitous terrain and/or RASS adjustments when determining preliminary DA.
Sloping OCS DA adjustment (see Figure 3–3–2). The MSL elevation of the sloping OCS at any distance from LTP (beyond the OCS origin) is determined using Formula 3-3–11.
Continue reading ↓ 120 of 268 passages shown