Radar Vectors
FAA Order Cancelled Issued Sep 17, 2020 AFS-400 544 pages Copy saved Nov 18, 2026

Order 8260.3E United States Standard for Terminal Instrument Procedures (TERPS) including Change 1

This order prescribes standardized methods for designing andevaluating IFPs prescribed under Title 14, Code of Federal Regulations (14 CFR) Part 95 andPart 97. It also contains design guidance related to other IFPs and Air Traffic Control (ATC)charts not specified under Parts 95 or 97. It is to be used by all personnel responsible for thepreparation, approval, and promulgation of IFPs. The criteria contained within this order arepredicated on normal aircraft operations and performance. This order contains guidance that ispertinent to 14 CFR Part 97.

This document is cancelled. Cancelled by 8260.3F. Check the official source before relying on it.

Official source ↗ Open PDF

FAA Order 8260.3E CHG 1 › Change Page

(1) Added instrument flight procedures (IFPs) at instrument flight rules (IFR) heliports to eligibility, including statement to defer application pending development of applicable IFR heliport design standards.

(2) Added reference to heliports for minimum approval standards.

(3) Added procedure naming standards for point-in-space (PinS) procedures.

(4) Added identification information for Air Traffic Service (ATS) routes.

(1) Added helicopter sloping obstacle clearance surface (OCS) evaluation information for climbing on departure or missed approach.

(2) Added information to consider aircraft on a standard terminal arrival (STAR) decelerating to restricted airspeeds below Class B airspace when determining segment lengths.

(3) Added COPTER as an authorized approach category for helicopter-only approaches.

(4) Added minimum safe altitude (MSA) positional information for PinS procedures.

(5) Added PinS evaluation information for establishment of visual descent points (VDPs) and evaluation of visual guidance surfaces (VGSs).

CHANGE U.S. DEPARTMENT OF TRANSPORTATION ORDER 8260.3E CHG 1 FEDERAL AVIATION ADMINISTRATION

Effective Date: National Policy 03/08/2022

SUBJ: United States Standard for Terminal Instrument Procedures (TERPS)

1. Purpose. This change incorporates general design criteria for helicopter instrument approaches and departures, transferring that criteria from Order 8260.42B (Change 2), U.S. Standard for Helicopter Area Navigation. Furthermore, it adds evaluation criteria for climb-inhold at missed approach point type missed approaches. 2. Who this change affects. All personnel who are responsible for IFP development and/or evaluation.

3. Disposition of Transmittal Paragraph. Significant areas of new direction, guidance, policy, and criteria as follows:

a. Chapter 1.

b. Chapter 2.

Distribution: Electronic only Initiated By: AFS-400

(6) Added evaluation criteria for climb-in-hold at the missed approach point (MAP) missed approach areas.

(1) Added PinS approaches to evaluation standards for determination of minimum altitudes/heights.

(2) Revised evaluation of remote altimeter setting source (RASS) adjustments related to PinS procedures.

(3) Modified visual area evaluation criteria to include evaluation for helicopter approaches to runways and heliports.

(4) Added helicopter minimums to standard civil takeoff minimums table.

(1) Specified types of procedures allowed for helicopter approaches.

(2) Added criteria guidance for PinS proceed visual and proceed VFR approaches.

e. Chapter 13, added criteria for helicopter departures.

(1) Added acronyms for the following to Table A-1: final approach and takeoff area (FATO), fictitious helipoint (FHP), GNSS azimuth reference point (GARP), heliport departure reference point (HDRP), initial departure fix (IDF), IFR to VFR heliport (IVH), landing helipoint (LHP), minimum vectoring altitude (MVA), obstacle departure procedure (ODP), touchdown and lift-off area (TLOF), visual segment climb angle (VSCA), visual segment descent angle (VSDA), visual segment descent point (VSDP), and visual segment reference line (VSRL).

(2) Changed the acronym definitions for the following in Table A-1: height above landing area elevation (HAL) becomes height above landing; and heliport crossing height (HCH) becomes helipoint crossing height.

(1) Added information for heliports to departure reference point information.

(2) Added definitions for: fictitious helipoint, heliport departure reference point, heliport elevation, heliport reference point, initial departure fix, proceed VFR, proceed visual, and unmarked landing area.

(3) Revised definitions for: common route, en route transition, helipoint, helipoint crossing height, runway transition, and touchdown and lift-off area.

c. Chapter 3.

d. Chapter 12.

f. Appendix A.

g. Appendix B.

FAA Order 8260.3E CHG 1 › Page Control Chart

h. Appendix E. Removed requirement to chart Global Positioning System (GPS) notes on simultaneous independent approaches due to redundancy with procedure type, and charting requirements contained in Order 8260.19, Flight Procedures and Airspace.

i. Appendix G. Added new appendix, transferred content from Order 8260.42B (Change 2) U.S. Standard for Helicopter Area Navigation (RNAV).

PAGE CHANGE CONTROL CHART

Remove Pages Dated Insert Pages Dated i through xviv 09/17/20 i through xx 03/08/22 1-5 through 1-8 09/17/20 1-5 through 1-8 03/08/22 1-11 through 1-14 09/17/20 1-11 through 1-14 03/08/22 2-3 through 2-16 09/17/20 2-3 through 2-16 03/08/22 2-47 through 2-58 09/17/20 2-47 through 2-58 03/08/22 2-77 through 2-92 09/17/20 2-77 through 2-92 03/08/22 3-5 through 3-16 09/17/20 3-5 through 3-16 03/08/22 3-19 through 3-26 09/17/20 3-19 through 3-26 03/08/22 3-29 (through 3-30) 09/17/20 3-29 (through 3-30) 03/08/22 10-27 through 10-30 09/17/20 10-27 through 10-30 03/08/22 12-1 through 12-24 09/17/20 12-1 through 12-28 03/08/22 13-1 through 13-47 09/17/20 13-1 through 13-50 03/08/22 14-13 through 14-14 09/17/20 14-13 through 14-14 03/08/22 15-3 through 15-4 09/17/20 15-3 through 15-4 03/08/22 15-15 through 15-16 09/17/20 15-15 through 15-16 03/08/22 16-19 through 16-20 09/17/20 16-19 through 16-20 03/08/22 A-1 through A-4 09/17/20 A-1 through A-4 03/08/22 B-1 through B-12 09/17/20 B-1 through B-13 03/08/22 D-3 through D-4 09/17/20 D-3 through D-4 03/08/22 E-7 through E-8 09/17/20 E-7 through E-8 03/08/22 E-19 through E-22 09/17/20 E-19 through E-22 03/08/22 E-27 through E-28 09/17/20 E-27 through E-28 03/08/22 G-1 through G-5 03/08/22

4. Distribution. This change is distributed electronically only.

Robert C. Carty Acting Executive Director, Flight Standards Service

ORDER

8260.3E

National Policy Effective Date:

09/17/2020

SUBJ: United States Standard for Terminal Instrument Procedures (TERPS) This order prescribes standardized methods for designing and evaluating instrument flight procedures (IFPs) in the United States and its territories. It is to be used by all personnel responsible for the preparation, approval, and promulgation of IFPs. These criteria are predicated on normal aircraft operations and performance.

FAA Order 8260.3E

Rick Domingo Executive Director, Flight Standards Service

Distribution: Electronic Distribution Initiated By: AFS-400

03/08/2022 Order 8260.3E CHG

Table of Contents

Chapter 1. Administrative … 1-1

Section 1-1. Scope … 1-1

1-1-1. Purpose of This Order … 1-1 1-1-2. Audience … 1-1 1-1-3. Where To Find This Order … 1-1 1-1-4. What This Order Cancels … 1-1 1-1-5. Explanation of changes … 1-1 1-1-6. Types of Procedures … 1-4 1-1-7. Word Meanings … 1-5 1-1-8. Formulas … 1-5 1-1-9. Geospatial Standards … 1-5 Section 1-2. Eligibility, Approval, and Retention … 1-6

FAA Order 8260.3E › Table of Contents

1-2-1. Eligibility … 1-6 1-2-2. Requests for Procedures … 1-6 1-2-3. Approval … 1-6 1-2-4. Cancellation of Procedures … 1-7 Section 1-3. Responsibility and Jurisdiction … 1-8

1-3-1. Responsibility … 1-8 1-3-2. Jurisdiction … 1-8 Section 1-4. IFP Establishment … 1-9

1-4-1. Formulation … 1-9 1-4-2. Nonstandard IFPs … 1-9 1-4-3. Amendments … 1-9 Section 1-5. Coordination … 1-10

1-5-1. Coordination … 1-10 1-5-2. Coordination Conflicts … 1-10 Section 1-6. Identification of IFPs … 1-11

1-6-1. General … 1-11 1-6-2. Straight-in Approach Procedures … 1-11 1-6-3. Circling Approach Procedures … 1-13 1-6-4. Combined Charting of Approach Procedures … 1-13 1-6-5. Non-part 97 Approach Procedure Naming … 1-13 1-6-6. Departure Procedure Identification … 1-14 1-6-7. En Route Procedure Identification … 1-14 1-6-8. Standard Terminal Arrival Identification … 1-14

i

Section 1-7. IFP Publication … 1-15

1-7-1. Submission … 1-15 1-7-2. Issuance … 1-15 1-7-3. Effective Date … 1-15 Chapter 2. General Criteria … 2-1

Section 2-1. Common Information … 2-1

2-1-1. Scope … 2-1 2-1-2. Required Obstacle Clearance (ROC) … 2-1 2-1-3. Level OCS … 2-1 2-1-4. Sloping OCS … 2-2 2-1-5. Units of Measurement … 2-5 2-1-6. Positive Course Guidance (PCG) … 2-6 2-1-7. Approach Categories … 2-6 2-1-8. Procedure Construction … 2-6 2-1-9. Continuous Descent Approach (CDA) … 2-7 2-1-10. Aircraft Speed … 2-7 Section 2-2. Standard Terminal Arrival Procedures … 2-8

2-2-1. Standard Terminal Arrival … 2-8 2-2-2. Origination and Termination … 2-8 2-2-3. Routes and Transitions … 2-8 2-2-4. Alignment … 2-9 2-2-5. Area … 2-9 2-2-6. Obstacle Clearance … 2-9 2-2-7. Altitudes … 2-9 2-2-8. Descent Gradient (DG) … 2-11 2-2-9. Speed Restrictions … 2-13 2-2-10. Deceleration … 2-14 Section 2-3. Feeder Routes/Emergency Areas … 2-16

2-3-1. Feeder Routes … 2-16 2-3-2. Minimum Safe Altitude (MSA) … 2-16 2-3-3. Emergency Safe Altitude (ESA) … 2-17 Section 2-4. Initial Approach … 2-18

2-4-1. Initial Approach Segment … 2-18 2-4-2. Altitude Selection … 2-18 2-4-3. Initial Approach Segments Based on Straight Courses and Arcs with PCG … 2-18 2-4-4. Initial Approach Segment Based on DR … 2-21 2-4-5. Initial Approach Segment Based on a PT … 2-24 2-4-6. Initial Approach Based on High Altitude Teardrop Turn … 2-28 2-4-7. Initial Approach Course Reversal Using Noncollocated Facilities … 2-31

ii

Section 2-5. Intermediate Approach … 2-37

2-5-1. Intermediate Approach Segment … 2-37 2-5-2. Altitude Selection … 2-37 2-5-3. Intermediate Approach Segment Based on Straight Courses … 2-38 2-5-4. Intermediate Approach Segment Based on an Arc … 2-39 2-5-5. Intermediate Approach Segment Within a PT … 2-40 Section 2-6. Final Approach … 2-49

2-6-1. Final Approach Segment … 2-49 2-6-2. Glidepath Angle (GPA) and Vertical Descent Angle (VDA) … 2-49 2-6-3. GPA … 2-49 2-6-4. VDA … 2-49 2-6-5. Visual Descent Point (VDP) … 2-53 2-6-6. Vertical Guidance Surface (VGS) … 2-55 Section 2-7. Circling Approach and Sidestep Maneuvers … 2-59

2-7-1. Circling Approach Area … 2-59 2-7-2. Restricted Circling Area … 2-60 2-7-3. Sidestep Maneuvers … 2-64 Section 2-8. Missed Approach … 2-66

2-8-1. Missed Approach Segment … 2-66 2-8-2. Missed Approach Alignment … 2-66 2-8-3. MAP … 2-66 2-8-4. Straight Missed Approach Area … 2-66 2-8-5. Straight Missed Approach Obstacle Clearance … 2-67 2-8-6. Turning Missed Approach Area … 2-69 2-8-7. Turning Missed Approach Obstacle Clearance … 2-76 2-8-8. Combination Straight and Turning Missed Approach Area … 2-79 2-8-9. Climb-in-Hold at the MAP Missed Approach Area … 2-81 2-8-10. End of Missed Approach … 2-82 Section 2-9. Terminal Area Fixes … 2-83

2-9-1. General … 2-83 2-9-2. Fixes Formed By Intersection … 2-83 2-9-3. Course/Distance Fixes … 2-83 2-9-4. Fixes Formed By Radar … 2-84 2-9-5. Fix Displacement Area … 2-84 2-9-6. Intersection Fix Displacement Factors … 2-84 2-9-7. Other Fix Displacement Factors … 2-86 2-9-8. Satisfactory Fixes … 2-87 2-9-9. Using Fixes for Descent … 2-89 2-9-10. Obstacles Close to a PFAF or a Final Approach Segment SDF … 2-92

iii

Chapter 3. Takeoff and Landing Minimums … 3-1

Section 3-1. General Information … 3-1

3-1-1. Application … 3-1 3-1-2. Establishment … 3-1 Section 3-2. Establishing Minimum Altitudes/Heights … 3-6

3-2-1. Establish minimum altitudes/heights … 3-6 3-2-2. Adjustments to Minimum Altitudes/Heights … 3-8 Section 3-3. Visibility Minimums … 3-17

3-3-1. Visibility Minimums Authorization … 3-17 3-3-2. Establishing Straight-in Visibility Minimums … 3-17 3-3-3. Establishing Circling Visibility Minimums … 3-26 3-3-4. Establishing Sidestep Visibility Minimums … 3-28 3-3-5. Fly Visual to Airport … 3-28 Section 3-4. Alternate Airport Minimums … 3-29

3-4-1. Establishing Alternate Minimums … 3-29 Section 3-5. Takeoff Minimums … 3-31

3-5-1. Civil Standard Takeoff Minimums … 3-31 Chapter 4. On-Airport VOR (No PFAF) … 4-1

Section 4-1. General Information … 4-1

4-1-1. General … 4-1 Section 4-2. Low Altitude Procedures … 4-2

4-2-1. Feeder Routes … 4-2 4-2-2. Initial Approach Segment … 4-2 4-2-3. Intermediate Segment … 4-2 4-2-4. Final Approach Segment … 4-2 4-2-5. Missed Approach Segment … 4-8 Section 4-3. High Altitude Teardrop Turn … 4-9

4-3-1. Feeder Routes … 4-9 4-3-2. Initial Approach Segment … 4-9 4-3-3. Intermediate Segment … 4-9 4-3-4. Final Approach Segment … 4-9 4-3-5. Missed Approach Segment … 4-11

iv

Chapter 5. TACAN, VOR/DME, and VOR with PFAF … 5-1

Section 5-1. General Information … 5-1

5-1-1. General … 5-1 Section 5-2. VOR with PFAF … 5-2

5-2-1. Feeder Routes … 5-2 5-2-2. Initial Approach Segment … 5-2 5-2-3. Intermediate Approach Segment … 5-2 5-2-4. Final Approach Segment … 5-2 5-2-5. Missed Approach Segment … 5-8 Section 5-3. TACAN and VOR/DME … 5-10

5-3-1. Feeder Routes … 5-10 5-3-2. Initial Segment … 5-10 5-3-3. Intermediate Segment … 5-10 5-3-4. Final Approach Segment … 5-10 5-3-5. Missed Approach Segment … 5-12 Chapter 6. NDB Procedures On-Airport Facility (No PFAF) … 6-1

Section 6-1. General Information … 6-1

6-1-1. General … 6-1 Section 6-2. Low Altitude Procedures … 6-2

6-2-1. Feeder Routes … 6-2 6-2-2. Initial Approach Segment … 6-2 6-2-3. Intermediate Segment … 6-2 6-2-4. Final approach segment … 6-2 6-2-5. Missed Approach Segment … 6-4 Section 6-3. High Altitude Teardrop Turn … 6-5

6-3-1. Feeder Routes … 6-5 6-3-2. Initial Approach Segment … 6-5 6-3-3. Intermediate Segment … 6-5 6-3-4. Final Approach Segment … 6-5 Chapter 7. NDB with PFAF … 7-1

Section 7-1 … 7-1

7-1-1. General … 7-1 7-1-2. Feeder Routes … 7-1 7-1-3. Initial Approach Segment … 7-1 7-1-4. Intermediate Approach Segment … 7-1 7-1-5. Final Approach Segment … 7-1 7-1-6. Missed Approach Segment … 7-4

v

Chapter 8. Localizer (LOC) and Localizer Type Directional Aids (LDA) … 8-1

Section 8-1 … 8-1

8-1-1. Feeder Routes, Initial Approach, and Intermediate Segments … 8-1 8-1-2. Final Segment … 8-1 8-1-3. Area … 8-1 8-1-4. Obstacle Clearance … 8-2 8-1-5. Vertical Descent Angle … 8-2 8-1-6. Minimum Descent Altitude … 8-2 8-1-7. Missed Approach Segment … 8-2 Chapter 9. Simplified Directional Facilities (SDF) Procedures … 9-1

Section 9-1 … 9-1

9-1-1. General … 9-1 9-1-2. Feeder Routes, Initial Approach, and Intermediate Segments … 9-1 9-1-3. Final Segment … 9-1 9-1-4. Missed Approach Segment … 9-2 Chapter 10. Precision Approach and LDA with Glide Slope … 10-1

Section 10-1. General Information and Criteria … 10-1

10-1-1. Purpose … 10-1 10-1-2. Background … 10-1 10-1-3. MSA, Feeder, Initial, and Intermediate Segments … 10-1 10-1-4. General Requirements … 10-4 Section 10-2. Final Approach Segment … 10-6

10-2-1. Final Segment … 10-6 10-2-2. OCS Slope … 10-7 10-2-3. “W” OCS … 10-8 10-2-4. “X” OCS … 10-11 10-2-5. “Y” OCS … 10-12 10-2-6. DA and Height Above Touchdown (HAT) … 10-13 10-2-7. Raising GPA for OCS penetrations … 10-13 10-2-8. Adjustment of DA for Final Approach OCS Penetrations … 10-14 Section 10-3. CAT I Missed Approach Segment … 10-17

10-3-1. General Information … 10-17 10-3-2. Section 1 … 10-17 10-3-3. Section 2 … 10-21 10-3-4. Missed Approach Climb Gradient … 10-23 Section 10-4. Special Authorization (SA) CAT I ILS Missed Approach … 10-25

10-4-1. General Information … 10-25 10-4-2. Final Approach Segment … 10-25

vi

10-4-3. Approach Minimums … 10-25 10-4-4. Missed Approach Evaluation … 10-25 Section 10-5. CAT II/III ILS Evaluation … 10-27

10-5-1. General Information … 10-27 10-5-2. Final Approach Segment … 10-27 10-5-3. Approach Light Area … 10-27 10-5-4. Approach Minimums … 10-27 10-5-5. Missed Approach Segment … 10-27 10-5-6. Requirements for CAT III ILS … 10-35 Section 10-6. PA and APV Obstacle Assessment … 10-36

10-6-1. Acceptable Obstacles … 10-36 10-6-2. Aircraft and Ground Vehicles as Obstacles … 10-36 Chapter 11. Radar Approach Procedures and Vectoring Charts … 11-1

Section 11-1. General Information … 11-1

11-1-1. General … 11-1 Section 11-2. Radar Approaches … 11-2

11-2-1. General … 11-2 11-2-2. Feeder Routes and Initial Approach Segments … 11-2 11-2-3. Intermediate Approach Segment … 11-3 11-2-4. PAR Final Approach Segment … 11-4 11-2-5. ASR FAS … 11-5 11-2-6. Missed Approach Segment … 11-6 Section 11-3. Minimum Vectoring Altitude Charts … 11-8

11-3-1. Minimum Vectoring Altitude Chart (MVAC) … 11-8 11-3-2. Sectors … 11-10 11-3-3. Obstacle Clearance … 11-16 11-3-4. Adverse Assumption Obstacle (AAO) considerations … 11-17 11-3-5. Airspace … 11-17 11-3-6. Altitude Selection … 11-17 Chapter 12. Helicopter Procedures … 12-1

Section 12-1. Administrative … 12-1

12-1-1. General … 12-1 12-1-2. Type of Procedure … 12-1 Section 12-2. General Criteria … 12-3

12-2-1. Application … 12-3 12-2-2. PinS Approach … 12-3

vii

12-2-3. Approach Categories … 12-4 12-2-4. Procedure Construction … 12-4 12-2-5. Descent Gradient/Vertical Descent Angle … 12-6 12-2-6. Initial Approach Segments Based on Straight Courses and Arcs … 12-6 12-2-7. Initial Approach Based on Procedure Turn … 12-7 12-2-8. Intermediate Approach Segment Based On Straight Courses … 12-8 12-2-9. Intermediate Approach Segment Based on an Arc … 12-8 12-2-10. Intermediate Segment within a Procedure Turn Segment … 12-8 12-2-11. Final Approach … 12-8 12-2-12. Missed Approach Point … 12-9 12-2-13. Straight Missed Approach Area … 12-9 12-2-14. Straight Missed Approach Obstacle Clearance … 12-9 12-2-15. Turning Missed Approach Area … 12-9 12-2-16. Turning Missed Approach Obstacle Clearance … 12-9 12-2-17. Combination Straight and Turning Missed Approach … 12-9 12-2-18. Holding … 12-9 Section 12-3. Takeoff and Landing Minimums … 12-11

12-3-1. Application … 12-11 12-3-2. Altitudes … 12-11 12-3-3. Visibility … 12-11 12-3-4. Visibility Credit … 12-12 12-3-5. Takeoff Minimums … 12-12 Section 12-4. On-Airport/Heliport VOR (No PFAF) … 12-14

12-4-1. General … 12-14 12-4-2. Initial and Intermediate Segments … 12-14 12-4-3. Final Approach Segment … 12-14 Section 12-5. TACAN, VOR/DME, and VOR with PFAF … 12-15

12-5-1. Final Approach Segment … 12-15 12-5-2. Missed Approach Point … 12-15 12-5-3. Arc Final Approach Segment … 12-15 Section 12-6. On-Airport/Heliport NDB, No PFAF … 12-16

12-6-1. General … 12-16 12-6-2. Final Approach Segment … 12-16 Section 12-7. NDB Procedures with PFAF … 12-17

12-7-1. General … 12-17 12-7-2. Final Approach Segment … 12-17 12-7-3. Missed Approach Point … 12-17

viii

Section 12-8. Localizer and LDA Procedures … 12-18

12-8-1. Localizer and LDA … 12-18 Section 12-9. ILS Procedures … 12-19

12-9-1. General … 12-19 12-9-2. Intermediate Approach Segment … 12-19 12-9-3. Final Approach Segment … 12-19 12-9-4. Missed Approach Area … 12-19

Section 12-10. Precision Approach Radar (PAR) … 12-20

12-10-1. Intermediate Approach Segment … 12-20 12-10-2. Final Approach Segment … 12-20 12-10-3. Final Approach Alignment … 12-20 12-10-4. Final Approach Area … 12-20 12-10-5. Final Approach Obstacle Clearance Surface … 12-20 12-10-6. Transitional Surfaces … 12-22 12-10-7. Obstacle Clearance … 12-22 12-10-8. Glide Slope … 12-23 12-10-9. Relocation of the Glide Slope … 12-23 12-10-10. Adjustment of DH … 12-23 12-10-11. Missed Approach Obstacle Clearance … 12-23 12-10-12. Straight Missed Approach Area … 12-24 12-10-13. Turning Missed Approach Area … 12-26 12-10-14. Combination Straight And Turning Missed Approach Area … 12-27 Section 12-11. Airport Surveillance Radar (ASR) … 12-30

12-11-1. Initial Approach Segment … 12-30 12-11-2. Intermediate Approach Segment … 12-30 12-11-3. Final Approach Segment … 12-30 12-11-4. Missed Approach Point … 12-30 Chapter 13. Departure Procedure Construction … 13-1

Section 13-1. General Criteria … 13-1

13-1-1. General … 13-1 13-1-2. Departure Criteria Application … 13-1 13-1-3. Departure OCS Application … 13-1 13-1-4. Climb Gradients … 13-3 13-1-5. Ceiling and Visibility … 13-6 13-1-6. Initial Climb Area (ICA) … 13-6 Section 13-2. Diverse Departure Assessment … 13-8

13-2-1. General … 13-8 13-2-2. Departure Sectors … 13-13 13-2-3. Sector Limitations … 13-15

ix

Section 13-3. Departure Routes … 13-18

13-3-1. Straight Route Departure Segments … 13-18 13-3-2. DR Departure … 13-18 13-3-3. Positive Course Guidance (PCG) Departure, 15 Degrees or less … 13-19 13-3-4. Turning Segment Construction … 13-22 13-3-5. Turn to PCG … 13-23 13-3-6. Multiple Turns … 13-24 13-3-7. Evaluation of Multiple Turn Areas … 13-30 Section 13-4. Visual Climb Over Airport (VCOA) … 13-34

13-4-1. General … 13-34 13-4-2. Basic Area … 13-34 13-4-3. VCOA Assessment … 13-35 13-4-4. Ceiling and Visibility … 13-37 13-4-5. Published Annotations … 13-37 Section 13-5. Diverse Vector Area (DVA) Assessment … 13-39

13-5-1. General … 13-39 13-5-2. Initial Departure Assessment … 13-39 13-5-3. Select a DVA Method … 13-39 13-5-4. Climb Gradients … 13-47 Section 13-6. Obstacle Clearance Requirements for SID Containing ATC Altitude Restrictions … 13-48

13-6-1. Maximum Altitude Restrictions … 13-48 13-6-2. Minimum Altitudes … 13-51 Section 13-7. Helicopter Point-in-Space (PinS) Departures … 13-52

13-7-1. General … 13-52 13-7-2. Procedure Design Standards … 13-52 13-7-3. Obstacle Evaluation Area (OEA) … 13-53 Chapter 14. En Route Criteria … 14-1

Section 14-1. VHF Obstacle Clearance Areas … 14-1

14-1-1. En Route Obstacle Clearance Areas … 14-1 14-1-2. Primary Areas … 14-1 14-1-3. Secondary Areas … 14-2 14-1-4. Turning Area … 14-2 14-1-5. Application of Turning Area Criteria … 14-5 14-1-6. Turn Area Template … 14-5 14-1-7. Changeover Points (COPs) … 14-9 14-1-8. Course Change Effect … 14-11 14-1-9. Minimum En Route IFR Altitudes … 14-12 14-1-10. Protected En Route Areas … 14-12

x

Section 14-2. VHF Obstacle Clearance … 14-13

14-2-1. Obstacle Clearance, Primary Area … 14-13 14-2-2. Obstacle Clearance, Secondary Areas … 14-13 Section 14-3. Altitudes … 14-16

14-3-1. Minimum Crossing Altitude (MCA) … 14-16 14-3-2. En Route Minimum Holding Altitudes … 14-18 Section 14-4. Navigational Gaps … 14-19

14-4-1. Navigational Gap Criteria … 14-19 Section 14-5. Low Frequency Airways or Routes … 14-21

14-5-1. LF Airways or Routes … 14-21 Section 14-6. Minimum Divergence Angles … 14-24

14-6-1. General … 14-24 14-6-2. VHF Fixes … 14-24 14-6-3. LF or VHF/LF Fixes … 14-24 Chapter 15. Simultaneous Approach Operations … 15-1

Section 15-1. Simultaneous Independent Approaches Spaced at Least 4300 Feet Apart … 15-1

15-1-1. Purpose … 15-1 15-1-2. General Guidance … 15-1 15-1-3. Types of Approaches … 15-1 15-1-4. Approach Design … 15-1 15-1-5. Final Approach Design … 15-1 15-1-6. Missed Approach Design … 15-1 15-1-7. Charting … 15-2 15-1-8. Coordination and Approval … 15-2 Section 15-2. Simultaneous Close Parallel (SCP) Approaches Spaced at Least 3000 Feet Apart but Less Than 4300 Feet Apart … 15-3

15-2-1. Purpose … 15-3 15-2-2. General Guidance … 15-3 15-2-3. Types of Approaches … 15-3 15-2-4. Approach Design … 15-3 15-2-5. Final Approach Design … 15-4 15-2-6. Missed Approach Design … 15-4 15-2-7. Procedure Naming and Charting … 15-5 15-2-8. Coordination and Approval … 15-6

xi

Section 15-3. Simultaneous Offset Instrument Approach (SOIA) Runways Spaced at Least 750 Feet Apart but Less Than 3000 Feet Apart … 15-7

15-3-1. Purpose … 15-7 15-3-2. General Guidance … 15-7 15-3-3. Types of Approaches … 15-7 15-3-4. Approach Design … 15-7 15-3-5. Final Approach Segment Design … 15-7 15-3-6. Missed Approach Design … 15-11 15-3-7. Procedure Naming and Charting … 15-13 15-3-8. Coordination and Approval … 15-13 Section 15-4. Breakout Obstacle Assessment for Simultaneous Independent Parallel Instrument Approach Operations … 15-15

15-4-1. Scope … 15-15 15-4-2. Assessment … 15-15 15-4-3. Obstacle Penetration Mitigations … 15-15 15-4-4. Periodic Review … 15-15 Section 15-5. Simultaneous Independent Procedures Considered Established on a PBN Segment of a Published Instrument Approach … 15-16

15-5-1. Purpose … 15-16 15-5-2. Approach Design … 15-16 15-5-3. Track Separation … 15-16 15-5-4. Alignment … 15-18 Chapter 16. Basic Holding Criteria … 16-1

Section 16-1. Pattern Design Assumptions … 16-1

16-1-1. Development Concept … 16-1 16-1-2. Turn Effect … 16-1 16-1-3. NAVAID Ground and Airborne System Tolerance … 16-1 16-1-4. Effect of Wind … 16-1 16-1-5. Development … 16-1 16-1-6. Application in the National Airspace System (NAS) … 16-1 16-1-7. Uncharted holding … 16-2 16-1-8. Air Traffic Operations … 16-2 Section 16-2. Pattern Components … 16-3

16-2-1. Area … 16-3 16-2-2. Outbound Leg Length … 16-3 16-2-3. Maximum Holding Airspeed … 16-3 16-2-4. Obstacle Clearance for Level Holding … 16-4 16-2-5. Communications … 16-4 16-2-6. Intersection Fix … 16-4

xii

Section 16-3. Primary Area Size Determination … 16-5

16-3-1. Size and Numbering … 16-5 16-3-2. Pattern Numbers … 16-5 16-3-3. Altitude Levels … 16-5 16-3-4. Fix-to-NAVAID Distances … 16-7 16-3-5. Pattern Applicability … 16-7 16-3-6. Pattern Selection … 16-8 Section 16-4. DME Applications with Slant-Range … 16-9

16-4-1. Slant-Range Effect … 16-9 16-4-2. Determining VOR/DME Distances … 16-9 16-4-3. No-Course-Signal Zone … 16-9 16-4-4. Fix Distance Variances … 16-9 16-4-5. Holding Toward/Away from the NAVAID … 16-12 16-4-6. Distance Based Holding Leg Lengths … 16-13 16-4-7. Reduction in Area Size … 16-13 16-4-8. VOR/DME Example Problems … 16-13 Section 16-5. Template Tracing … 16-15

16-5-1. Template Usage … 16-15 16-5-2. Basic Perimeter … 16-15 Section 16-6. Manual Construction of Patterns … 16-16

16-6-1. Requirement … 16-16 16-6-2. Basic Primary Area Construction … 16-16 Section 16-7. Climb-in-Hold … 16-19

16-7-1. Climb-in-Hold Evaluations … 16-19 16-7-2. Climb-in-Hold Airspeed Determination … 16-19 16-7-3. Climb-in-Hold Obstacle Evaluation … 16-20 Section 16-8. Descend-in-Hold Patterns … 16-22

16-8-1. Descend-in-Hold … 16-22 16-8-2. Descend-in-Hold Airspeed Determination … 16-22 16-8-3. Descend-in-Hold Criteria … 16-22 Section 16-9. Operational Applications … 16-23

16-9-1. Establishing Fixes … 16-23 16-9-2. Pattern Alignment … 16-23 16-9-3. VOR/DME Leg Length Selection … 16-23 16-9-4. VOR/DME Holding Direction … 16-23 16-9-5. Establishing MHAs … 16-23 16-9-6. Holding Patterns on or Adjacent to ILS Courses … 16-23

xiii

Section 16-10. RNAV Holding Patterns … 16-25

16-10-1. General Information … 16-25 16-10-2. Criteria Development … 16-25 16-10-3. Restrictions … 16-25 16-10-4. RNAV Holding Patterns … 16-25 16-10-5. RNAV Leg Length Determination … 16-25 Section 16-11. Helicopter Holding Patterns … 16-26

16-11-1. Helicopter (Copter) Holding … 16-26 16-11-2. Copter Holding Procedures … 16-26 Section 16-12. Increased Airspeed Holding Pattern Operations … 16-27

16-12-1. Turbulent Air Operation … 16-27 16-12-2. Maximum Holding Speed in Turbulent Air Conditions … 16-27 16-12-3. Operational Use … 16-27 Section 16-13. VOR/DME Leg Length Determination … 16-29

16-13-1. General … 16-29 Section 16-14. Formulas for Holding Pattern Placement … 16-36

16-14-1. General … 16-36

Appendix A. Administrative Information … A-1 1. Distribution … A-1 2. Acronyms and Abbreviations … A-1 3. Related Publications … A-5 4. Forms and Reports … A-6 5. Information Update … A-6 Appendix B. Definitions … B-1

3-Dimension … B-1 2. Air Traffic Service route … B-1 3. Airport reference point … B-1 Along-track distance … B-1 5. Along-track tolerance … B-1 Angle of divergence (Minimum) … B-1 APT waypoint … B-1 Area navigation … B-1 Authorization required … B-1 Average coldest temperature … B-1 Barometric altitude … B-1 Baseline … B-2 Circling approach area … B-2

xiv

Clearway … B-2 Climb gradient … B-2 Common route … B-2 Controlling obstacle … B-2 Course … B-2 Course change … B-2 Course-to-a-fix … B-2 Course-to-an-altitude … B-2 Course-to-an-intercept … B-2 Cross-track tolerance … B-2 Dead reckoning … B-2 Decision altitude … B-2 Departure end of runway … B-2 Departure reference line … B-3 Departure reference point … B-3 Departure route … B-3 Departure sector … B-3 Direct-to-a-fix … B-3 Descent gradient … B-3 Distance of Turn Anticipation … B-3 Distance Measuring Equipment Arc … B-3 DME distance … B-3 Diverse Vector Area … B-3 Early Turn Point … B-3 En Route Transition … B-3 Fictitious Helipoint … B-4 Fictitious Threshold Point … B-4 Final Approach and Takeoff Area … B-4 Final Approach Course … B-4 Final Approach Segment … B-4 Fix … B-4 Fix displacement tolerance … B-4 Fix-to-NAVAID … B-4 Flight control computer … B-4 Flight management system … B-4 Flight path alignment point … B-4 Flight path control point … B-5 Final roll-out point … B-5 Fly-by fix … B-5 Fly-over fix … B-5 Glidepath angle … B-5 Global azimuth reference point … B-5 Global Navigation Satellite System … B-5 Gradient … B-5 Ground point of intercept … B-5 Heading-to-an-altitude … B-5

xv

Heading-to-an-intercept … B-5 Height above landing … B-5 Height above surface … B-5 Height above touchdown … B-5 Helipoint … B-6 Helipoint crossing height … B-6 Heliport … B-6 Heliport departure reference point … B-6 Heliport elevation … B-6 Heliport reference point … B-6 Initial climb area … B-6 ICA baseline … B-6 ICA end-line … B-6 Initial approach fix … B-6 Initial departure fix … B-6 Instrument Landing System … B-6 Intermediate fix … B-7 International standard atmosphere … B-7 Knots indicated airspeed … B-7 Landing area as used in helicopter operations … B-7 Landing area boundary … B-7 Landing threshold point … B-7 Lateral navigation … B-7 Lateral/Vertical Navigation … B-7 Leg … B-7 Localizer … B-7 Localizer performance … B-7 Localizer type directional aid … B-8 Minimum descent altitude … B-8 Minimum en route altitude … B-8 Minimum obstruction clearance altitude … B-8 Non-directional beacon airborne automatic direction finder … B-8 Non-VOR/DME RNAV … B-8 Obstacle … B-8 Obstacle clearance … B-8 Obstacle clearance surface … B-8 Obstacle evaluation area … B-8 Obstacle identification surface … B-9 Obstacle positions (OBSX,Y,Z) … B-9 Operational advantage … B-9 Point-in-space approach … B-9 Positive course guidance … B-9 Precipitous terrain … B-9 Precise final approach fix … B-9 Proceed VFR … B-9 Proceed Visual … B-9

xvi

Primary area … B-9 Radio altimeter height … B-9 Radius to fix leg … B-10 Reduced takeoff runway length … B-10 Reference datum point … B-10 Reference facility … B-10 Reference fix … B-10 Reference line … B-10 Reference NAVAID … B-10 Required Navigation Performance … B-10 Required Obstacle Clearance … B-10 Runway Threshold … B-10 Runway Transition … B-10 Runway WP … B-11 Secondary area … B-11 Segment … B-11 Service volume … B-11 Slant-range … B-11 Slant-range/geographical distance … B-11 Start end of runway … B-11 Standard instrument departure … B-11 Standard terminal arrival … B-11 Start of climb … B-11 Take-off distance available … B-11 Take-off run available … B-11 Tangent point … B-11 Tangent point distance … B-12 Threshold crossing height … B-12 Touchdown and lift-off area … B-12 Touchdown zone … B-12 Touchdown zone elevation … B-12 Track to fix leg … B-12 Transition level … B-12 True airspeed … B-12 Turn anticipation … B-12 Turn fix … B-12 Turn initiation area … B-12 Turn WP … B-12 Unmarked landing area … B-12 Vertical descent angle … B-12 Vertical error budget … B-12 Visual climb area … B-13 Visual climb over airport … B-13 Visual descent point … B-13 Vertical guidance surface … B-13 Visual glide slope indicator … B-13

xvii

Visual segment … B-13 WP … B-13 WP displacement area … B-13 Wide Area Augmentation System … B-13

Appendix C. Precipitous Terrain Algorithms … C-1

Precipitous Terrain Equations, Parameters, Interests, and Adjustment Values … C-1 Precipitous Point Value Methodology … C-4 PPV adjustment values … C-6

Appendix D. Mathematics Convention … D-1

Mathematical Functions and Constants … D-1 Operational Precedence … D-2 Conversions by Unit Factors … D-2 Other Conversions … D-3 Common Equation Terms … D-4

Appendix E. Simultaneous Approach Operations … E-1

Section 1. General Information about Simultaneous Approaches … E-1

Purpose … E-1 Background … E-1 Overview … E-3 Safety Studies and Tests … E-3 Terms, Concepts and Implementation Considerations … E-3 Related Documentation … E-5

Section 2. Additional Information for Simultaneous Independent Approaches Spaced at Least 4300 Feet Apart … E-6

Purpose … E-6 Vertical Guidance … E-6 ATC Operations Concept … E-6 NTZ … E-6 Normal Operating Zone (NOZ) … E-6 Design Guidelines … E-7

Section 3. Additional Information for Simultaneous Close Parallel (SCP) Approaches … E-9

SIT … E-9 Concepts, Terms and Implementation … E-9 Approach Design Considerations … E-11 Authorized Lines of Minimums … E-13

Section 4. Additional Information for Simultaneous Offset Instrument Approach (SOIA) … E-14

Concept … E-14 Design Considerations for Identical Approaches … E-15

xviii

Staggered Runway Thresholds … E-16 SOIA SIT … E-17 AAUP … E-18 SOIA Design Program … E-18 NTZ … E-19 Ceiling for SOIA Operations … E-19 Wake Turbulence Requirements and Considerations … E-19 Crosswind Limits for SOIA … E-20 ATC/Flight Crew Coordination … E-20 SOIA Implementation … E-21

Section 5. Simultaneous Independent Procedures Considered Established on a PBN Segment of a Published Instrument Approach … E-22

Roles/Responsibilities and Approval Process … E-22 Conclusions … E-22 Key Findings … E-22

Section 6. Obstacle Assessment Surface Evaluation for Simultaneous Independent Parallel Instrument Approach Operations … E-24

Background … E-24 Parallel Approach Obstruction Assessment … E-25

Appendix F. Geospatial Standard … F-1

Section 1. General … F-1

Algorithms and methods … F-1 Algorithm format and definitions … F-1 Ellipsoidal formulas … F-2 Spherical Approximations … F-3 Accuracy … F-3 Geodetic processes … F-3

Section 2. Useful Functions … F-5

Calculate angular arc extent … F-5 Converting geodetic latitude/longitude to ECEF coordinates … F-6 Signed azimuth difference … F-6 Approximate fixed radius arc length … F-6

Section 3. Basic Calculations … F-8

Iterative approach … F-8 Starting solutions … F-8 Tolerances … F-12 Geodesic oriented at specified angle … F-12 Determine if point lies on geodesic … F-14 Determine if point lies on arc … F-16

xix

Calculate length of fixed radius arc … F-18 Find distance from defining geodesic to locus … F-21 Determine if point lies on locus … F-23 Compute course of locus … F-24

Section 4. Projections … F-27

Project point to geodesic … F-27 Project point to locus from point on defining geodesic … F-31 Project point to locus nearest given point … F-32 Tangent projection from point to arc … F-35 Project arc to geodesic … F-37

Section 5. Intersections … F-40

Intersection of two geodesics … F-40 Intersection of two arcs … F-44 Intersections of arc and geodesic … F-47 Arc Tangent to two geodesics … F-51 Intersections of geodesic and locus … F-54 Intersections of arc and locus … F-57 Intersections of two loci … F-60 Arc tangent to two loci … F-63

Appendix G. Conditions and Assumptions for IFR to VFR Heliport (IVH) (Proceed Visual) Approach Procedures … G-1

Acceptable onsite evaluation of the heliport … G-1 Acceptable evaluation of the visual segment … G-2 IVH Analysis … G-2

xx

b. Chapter 2. › (4) Added graphic departures to procedures requiring a published…

Chapter 1. Administrative

Section 1-1. Scope

1-1-1. Purpose of This Order. This order prescribes standardized methods for designing and evaluating IFPs prescribed under Title 14, Code of Federal Regulations (14 CFR) Part 95 and Part 97. It also contains design guidance related to other IFPs and Air Traffic Control (ATC) charts not specified under Parts 95 or 97. It is to be used by all personnel responsible for the preparation, approval, and promulgation of IFPs. The criteria contained within this order are predicated on normal aircraft operations and performance. This order contains guidance that is pertinent to 14 CFR Part 97.

1-1-2. Audience. All personnel who are responsible for IFP development and/or evaluation.

1-1-3. Where To Find This Order. You can find this order on the Federal Aviation Administration’s (FAA) web site.

1-1-4. What This Order Cancels. Order 8260.3D, United States Standard for Terminal Instrument Procedures (TERPS), dated February 16, 2018.

1-1-5. Explanation of changes. Significant areas of new direction, guidance, policy, and criteria as follows:

a. Chapter 1.

(1) Changed references from "Regional Airspace and Procedures Team (RAPT)" to "IFP Validation Team," “National Airspace and Procedures Team (NAPT)" to "IFP Oversight Committee," and "Flight Procedure Implementation and Oversight Branch" to "Flight Procedures and Technologies Division.”

(2) Specified suffixes required for non-Part 97 approach procedure naming.

(3) Removed all references to area navigation (very high frequency omnidirectional range/distance measuring equipment) (RNAV) (VOR/DME) procedures.

b. Chapter 2.

(1) Added requirement of positive course guidance for all legs of a conventional standard terminal arrival (STAR).

(2) Added requirement for Flight Standards approval for a STAR termination fix without a termination altitude.

(3) Added requirement that a STAR termination altitude may be no lower than the minimum altitude of any approach procedure fix that will be flown following the STAR.

(4) Added graphic departures to procedures requiring a published minimum safe altitude (MSA).

d. Chapter 10. › (3) Removed immediately turning missed approach paragraph to clarify…

(5) Modified allowance for dead reckoning (DR) initial segment intercept angle to be less than 45 degrees only when DME is required for the approach and is used to identify the intermediate fix (IF).

(6) Changed all threshold crossing height (TCH) references from “design TCH” and “visual TCH” to be simply “TCH.”

(7) Removed all references to nonprecision approaches, minimum descent altitudes, visual descent points, and visual descent angles from the visual guidance surface evaluation.

(8) Clarified elevation rounding used to determine heights above touchdown zone elevation (TDZE) and airport to specify rounding of TDZE and airport elevation to the nearest foot.

(9) Removed references to “Z” markers; there are no longer any installed in the National Airspace System (NAS).

(10) For establishing missed approach surface delay due to excessive precise final approach fix (PFAF) error, clarified that the requirement would only be necessary when timing is used to identify the missed approach point.

c. Chapter 3.

(1) Changed all references from “published TCH” to “TCH.”

(2) Clarified that precipitous point value (PPV) adjustments were applicable to both the missed approach obstruction altitude evaluation and the missed minimum holding altitude evaluation.

(3) Revised remote altimeter setting source (RASS) final adjustment criteria to include information for calculation of landing minima for a secondary altimeter source, and adjustment with multiple adjustment sources, and incorporated examples.

(4) Added allowance for offset visual area construction for approaches with a final approach course that do not go through the landing threshold point (LTP).

d. Chapter 10.

(1) Changed all references from “published TCH” to “TCH” and added definition of TCH for purposes of the chapter.

(2) Removed 1200-ft limit for decision altitude (DA) to runway centerline (RCL) for offset instrument landing system (ILS) and defined DA point in this context.

(3) Removed immediately turning missed approach paragraph to clarify where section 2 begins based on a fixed section 1 length for consistency with TARGETS and to harmonize with LPV missed approach criteria. Moved necessary criteria for evaluation of a straight and turning missed approach to the applicable section.

1-1-5. Explanation of changes. › j. Chapter 17.

(4) Clarified elevation rounding used to determine heights above TDZE to specify rounding of elevation to the nearest foot.

(5) Revised missed approach zone 2 evaluation criteria to clarify the zone 2 obstacle clearance surface (OCS) starting height was equivalent to the end OCS elevation of the straight portion of section 2, less any RASS and precipitous terrain adjustments for the final segment.

(6) Removed precipitous terrain adjustment from calculation of missed approach climb gradient and climb gradient termination altitudes, leaving only RASS adjustments.

(7) Changed reference to 14 CFR Part 77.13(a)(3) obstacle height data to Order 8260.19 Section 2-11, Obstacle Data.

e. Chapter 12.

(1) Revised general section to clarify that combinations of fixed-wing and helicopter criteria could be used for helicopter-only procedures, including the option to use only fixed-wing aircraft criteria.

(2) Updated helicopter minimum allowable visibility from ¾ statute miles (SM) to ¾ SM day / 1 SM night.

(3) Clarified elevation rounding used to determine heights above landing area to specify rounding of landing area elevation to the nearest foot.

f. Chapter 13. Deleted chapter due to elimination of all RNAV (VOR/DME) procedures from the NAS. Shifted numbering of all subsequent chapters forward.

g. Chapter 14.

(1) Becomes Chapter 13.

(2) Clarified elevation rounding used to determine heights above departure end of runway (DER) elevation to specify rounding of DER elevation to the nearest foot.

h. Chapter 15. Becomes Chapter 14.

i. Chapter 16.

(1) Becomes Chapter 15.

(2) Changed references from “Flight Systems Laboratory Branch” to “Flight Research and Analysis Group.”

(3) Removed all references to RNAV required navigation performance (RNP) approaches from Simultaneous Close Parallel (SCP) and Simultaneous Offset Independent Approach (SOIA) procedures since these do not have Flight Operations Group approval.

j. Chapter 17.

1-1-6. Types of Procedures. › c. Nonprecision approach (NPA). An instrument approach based on a…

(1) Becomes Chapter 16.

(2) Deleted paragraph specifying waiver action is required for establishment of 175 knots indicated airspeed (KIAS) holding patterns when not meeting the requirements necessary for establishment.

k. Appendix A. Added acronym for final roll-out point (FROP) to Table A-1.

l. Appendix E.

(1) Changed references from “Flight Systems Laboratory Branch” to “Flight Research and Analysis Group.”

(2) Removed all references to RNAV (RNP) approaches from SCP and SOIA procedures since these do not have Flight Operations Group approval.

(3) Changed references from “Flight Operations Branch” to “Flight Operations Group.”

m. Appendix F.

(1) Deleted existing content due to full replacement of legacy automation system for development and evaluation of ILS procedures.

(2) Added content of geospatial standard appendix from Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.

1-1-6. Types of Procedures. Criteria are provided for the following types of IFPs:

a. Precision approach (PA). An instrument approach based on a navigation system that provides course and glidepath deviation information meeting the precision standards of International Civil Aviation Organization (ICAO) Annex 10 is considered a PA procedure. Precision Approach Radar (PAR) and Instrument Landing System (ILS) are examples of PA procedures.

b. Approach with vertical guidance (APV). An instrument approach based on a navigation system that is not required to meet the PA standards of ICAO Annex 10 but provides course and glidepath deviation information is considered an APV procedure. Localizer performance with vertical guidance (LPV), lateral navigation/vertical navigation (LNAV/VNAV), and localizer type directional aid (LDA) with glidepath, are examples of APV procedures.

c. Nonprecision approach (NPA). An instrument approach based on a navigation system that provides course deviation information, but no glidepath deviation information is considered an NPA procedure. Very high frequency omnidirectional range (VOR), tactical air navigation (TACAN), very high frequency omnidirectional radio range collocated with tactical air navigational aid (VORTAC), LNAV, localizer performance (LP), nondirectional radio beacon (NDB), localizer (LOC), and airport surveillance radar (ASR) approaches are examples of NPA procedures.

Section 1-1. Scope › 1-1-9. Geospatial Standards.

(NDB), localizer (LOC), and airport surveillance radar (ASR) approaches are examples of NPA procedures.

d. Departure procedures (DP). Procedures designed to provide obstacle clearance during instrument departures.

e. Standard terminal arrival (STAR). A procedure that provides obstacle clearance and routing from the en route structure to a fix in the terminal area.

f. En route Air Traffic Service (ATS) routes. Routes including VOR and L/MF-based airways, which provide obstacle clearance.

1-1-7. Word Meanings. Word meanings as used in this order:

a. Must. This means that application of the criteria is mandatory.

b. Should. This means that application of the criteria is recommended.

c. May. This means that application of the criteria is optional.

1-1-8. Formulas. Refer to Appendix D, Mathematics Convention, for definitions and abbreviations of formula inputs that are commonly used throughout this document.

1-1-9. Geospatial Standards. IFPs may be evaluated geodetically (see Appendix F). Design criteria is stipulated in this order; however, actual construction of obstacle evaluation areas (OEAs) and connection of segments may vary due to constraints within automated software. For precise construction parameters, refer to the software documentation for the appropriate automated software.

1-2-3. Approval. › d. Navigation facilities. All instrument and visual navigation…

Section 1-2. Eligibility, Approval, and Retention

1-2-1. Eligibility.

a. Military airports. IFPs at military airports must be established as required by the directives of the appropriate military service.

b. Civil airports. IFPs at civil airports are established as required by Order 8260.43, Flight Procedures Management Program.

c. Joint-use airports (civil and military). IFPs at joint-use airports are established as specified in paragraph 1-2-1.a when the military is responsible for IFP development, and as specified in paragraph 1-2-1.b when the FAA is responsible for IFP development.

d. Instrument flight rules (IFR) heliports. IFPs at IFR heliports (not applicable to point-inspace (PinS) procedures) are deferred pending development of applicable IFR heliport design standards.

1-2-2. Requests for Procedures. Refer to Order 8260.43 and Order 8260.19, Flight Procedures and Airspace.

1-2-3. Approval. The following minimum standards must be met to approve a request for an IFP:

a. An airport or heliport airspace analysis conducted under Order JO 7400.2, Procedures for Handling Airspace Matters, or appropriate military directives, as applicable must find the airport or heliport acceptable for IFR operations. Acceptability for IFR operations is not required at landing areas for PinS procedures.

b. The airport or heliport (not applicable to PinS Proceed VFR procedures) infrastructure must be adequate to accommodate the aircraft expected to use the procedure (see AC 150/5340­ 1, Standards for Airport Markings, and AC 150/5300-13, Airport Design, paragraph 317 and Table 3-4, or AC 150/5390-2, Heliport Design, as appropriate).

c. Limit the addition of category (CAT) E minimums for new IFPs to locations where a military requirement exists.

d. Navigation facilities. All instrument and visual navigation facilities used must successfully pass flight inspection.

e. Obstacle marking and lighting. Obstacles that penetrate 14 CFR part 77 imaginary surfaces are obstructions and; therefore, should be marked and lighted per AC 70/7460-1, Obstruction Marking and Lighting. Those penetrating the 14 CFR part 77 approach and transitional surfaces should be removed or made conspicuous under AC 70/7460-1 (or military equivalent). Do not deny instrument approach procedures due to inability to mark and light or remove obstacles that violate 14 CFR part 77 surfaces (see exception in paragraph 3-3-2.c).

Section 1-2. Eligibility, Approval, and Retention › 1-2-4. Cancellation of Procedures. Refer to Order 8260.43.

f. Weather information. Terminal weather observation and reporting facilities must be available for the airport to serve as an alternate airport. Destination minimums may be approved when a general area weather report is available prior to commencing the approach and approved altimeter settings are available to the pilot prior to and during the approach consistent with communications capability.

g. Communications.

(1) Instrument approach procedure. Air-to-ground communications must be available at the initial approach fix (IAF) minimum altitude and where an aircraft executing the missed approach is expected to reach the missed approach altitude. At lower altitudes, communications are required where essential for the safe and efficient use of airspace.

(2) STAR. Communications with ATC must be available over the entire route at the minimum altitude for each segment.

1-2-4. Cancellation of Procedures. Refer to Order 8260.43.

1-3-2. Jurisdiction. › d. New obstacles or operational uses require a revision to the existing…

Section 1-3. Responsibility and Jurisdiction

1-3-1. Responsibility.

a. Military airports. The military services establish and approve IFPs at airports under their respective jurisdictions. IFPs established in accordance with this order are considered equivalent to 14 CFR part 97 procedures and are normally authorized for civil use. The FAA must be informed when IFPs are canceled (see Order 8260.43). The FAA may accept responsibility for the development and/or publication of military IFPs when requested to do so by the appropriate military service through an interagency agreement.

b. Civil airports. The FAA establishes and approves IFPs for civil airports.

c. Military procedures at civil airports. Where existing FAA IFPs at civil airports do not meet user needs, the military may request the FAA to develop IFPs to meet military requirements. Modification of an existing FAA IFP or development of a new IFP may meet these requirements. The FAA must formulate, coordinate with the military and industry, and publish and maintain such procedures. The military must inform the FAA when such IFPs are no longer required.

1-3-2. Jurisdiction. The military or FAA office having jurisdiction over an airport may initiate action under these criteria to establish or revise IFPs when a reasonable need is identified, or where:

a. New navigation facilities or airport infrastructure are installed.

b. Changes to existing facilities/airport infrastructure necessitate a change to an approved IFP.

c. Additional IFPs are necessary.

d. New obstacles or operational uses require a revision to the existing IFP.

Section 1-4. IFP Establishment › 1-4-3. Amendments.

Section 1-4. IFP Establishment

1-4-1. Formulation. Proposed IFPs are prepared under the applicable chapter of this order as determined by the phase of flight and navigation source. To permit use by aircraft with limited navigational equipment, an IFP should be formulated using a single navigation source whenever possible. The use of multiple navigation sources of the same or different types may be permitted to gain an operational advantage.

1-4-2. Nonstandard IFPs. The standards contained in this order are based on reasonable assessment of the factors which contribute to errors in aircraft navigation and maneuvering. They are designed primarily to assure that safe flight operations for all users result from their application. Every effort must be made to formulate IFPs in accordance with these standards; however, obstacles, navigation information, or traffic congestion may require special consideration where justified by operational requirements. In such cases, nonstandard IFPs that deviate from these criteria may be approved, provided they are documented and an equivalent level of safety exists. A nonstandard IFP is not substandard; it has been approved after special study demonstrated that no derogation of safety is involved.

a. See Order 8260.19 for authority and processing of nonstandard civil IFPs.

b. The U.S. Military Service responsible for procedure development is the approving authority for nonstandard military IFPs; see applicable Military Service directive for approval and processing requirement. Military IFPs that deviate from standards because of operational necessity, and in which an equivalent level of safety is not achieved, must be marked “NOT FOR CIVIL USE.”

1-4-3. Amendments. Process in accordance with Order 8260.19 (or appropriate directives).

Section 1-5. Coordination › 1-5-2. Coordination Conflicts.

Section 1-5. Coordination

1-5-1. Coordination. Coordinate IFPs to avoid conflicts and to protect the rights of all airspace users.

a. ATC facilities. All new or revised IFPs must be coordinated with the affected military or civil ATC facilities and other related airspace users.

b. Airspace. Where action to designate controlled airspace for an IFP is planned, the airspace action should be initiated sufficiently in advance so that effective dates of the IFP and the airspace action will coincide (see Order 8260.19).

c. Notices to Airmen (NOTAMs). See Order 8260.19 and Order JO 7930.2, Notices to Airmen (NOTAMs), for coordination and processing requirements related to IFP NOTAMs.

1-5-2. Coordination Conflicts. Coordination conflicts that cannot be resolved with the FAA organization responsible for IFP development will be submitted to the IFP Validation Team for resolution. Make every effort to thoroughly evaluate the comments/objections, determine the validity and scope of each issue, and if necessary determine the appropriate course of action to resolve the conflict. For issues other than the application and/or interpretation of IFP design criteria, the IFP Validation Team will forward conflicts that cannot be resolved to the IFP Oversight Committee. Conflicts concerning the application and/or interpretation of IFP design criteria should be forwarded to Flight Technologies and Procedures Division for resolution. Take parallel actions through military channels if a problem involves a military procedure.

1-6-2. Straight-in Approach Procedures. › b. Exception. High altitude approaches, prefix the navigation system…

Section 1-6. Identification of IFPs

1-6-1. General. IFPs must be uniquely identified to permit differentiation on charts/publications, airborne equipment displays, and during ATC communications. This section specifies IFP identification (procedure naming) only and is not intended for other uses.

1-6-2. Straight-in Approach Procedures. Identification includes the following elements (as applicable) in the following sequence:

a. Navigation system. The first element is the navigation system (and area navigation (RNAV) sensor in some cases) used to provide lateral navigation guidance within the final approach segment.

(1) Non-RNAV. Identify the applicable ground-based system and use the applicable abbreviation, such as, ASR, PAR, NDB, VOR, TACAN, LOC, LDA, or ILS. For localizer back course (BC) procedures, identify as “LOC BC.”

Examples: ASR RWY 17, ILS RWY 17, LOC RWY 27, LOC BC RWY 31

(2) RNAV.

(a) Procedures with LNAV, LP, LNAV/VNAV, or LPV minimums use “RNAV (GPS).”

(b) Required Navigation Performance (RNP) procedures with Authorization Required (AR) use “RNAV (RNP).”

(c) Ground Based Augmentation System (GBAS) Landing System (GLS) procedures, use “GLS.”

Examples: RNAV (GPS) RWY 17, RNAV (RNP) RWY 17, GLS RWY 17

b. Exception. High altitude approaches, prefix the navigation system with “HI-.” This prefix does not eliminate the requirement to use an alphabetical suffix when more than one procedure uses the same navigational guidance to the same runway (see paragraph 1-6-2.d).

Examples: HI-TACAN RWY 31, HI-ILS X RWY 13

c. Precision runway monitor (PRM) modifier. This element is applicable to ILS, GLS, RNAV (GPS), and LDA procedures authorized for closely spaced parallel approach operations including Simultaneous Offset Instrument Approach (SOIA) operations. Include “PRM” following the navigation system (and RNAV sensor if applicable) when requested by ATC to support closely spaced parallel operations.

Examples: ILS PRM RWY 35L, RNAV (GPS) PRM RWY 35L, LDA PRM RWY 28R, GLS PRM RWY 17

1-6-2. Straight-in Approach Procedures. › e. Runway numbers which the final approach course (FAC) is aligned and…

d. Alphabetical suffix. When more than one procedure to the same runway uses the same type of navigation system for lateral guidance within the final approach segment, differentiate each procedure by adding a non-repeating alphabetical suffix using the letters “S” through “Z.” Suffixes are normally assigned in reverse order starting with “Z,” but may be assigned as needed to meet operational needs (for example, all RNAV (RNP) approaches at an airport assigned “Z” suffix, all RNAV (GPS) approaches assigned “Y” suffix, etc.).

Examples: ILS Z RWY 17, ILS Y RWY 17, COPTER ILS X RWY 17

(1) “V” suffix. “V” is reserved for ILS, RNAV, and GLS procedures designated to support simultaneous converging approach operations.

(2) Category I ILS, Special Authorization (SA) Category I ILS, Category II ILS, SA Category II ILS, and/or Category III ILS approaches to the same runway with the same ground tracks, altitudes (landing minimums excluded), and missed approach instructions are not considered duplicates of each other and do not require separate alphabetical identification suffixes. For example, no suffix is required for either the “ILS RWY 16R” or “ILS RWY 16R (SA CAT I)”, but if the CAT I ILS has a suffix, then assign the same suffix to the SA ILS, for example, “ILS Y RWY 16R” and “ILS Y RWY 16R (SA CAT I).”

(3) PRM. Assign the same identification suffix to the PRM approach as is assigned to the non-PRM approach it is based on. For example, title the PRM, “RNAV (GPS) PRM Y RWY 28L” when based on the “RNAV (GPS) Y RWY 28L.” Do not assign a suffix if the non-PRM approach is published without one. For example, title the PRM, “ILS PRM RWY 17” when based on the “ILS RWY 17.”

(4) RNAV (GPS) and RNAV (RNP). Alphabetical suffixes are required for each procedure with “RNAV” in the title when there are two or more such procedures to the same runway.

Examples: RNAV (GPS) Z RWY 28L, RNAV (GPS) Y RWY 28L, RNAV (RNP) X RWY 28L High altitude procedures and other procedures using the same final approach guidance to the same runway require a suffix unless all tracks and altitudes are identical. For example, title the high ILS as, “HI-ILS Z RWY 32” and the low ILS as, “ILS Y RWY 32.”

e. Runway numbers, which the final approach course (FAC) is aligned and to which straight-in minimums are authorized. Describe as “RWY” followed by the runway designator(s).

Examples: ILS RWY 17, RNAV (GPS) RWY 18L, HI-TACAN Y RWY 13. Where approaches meet straight-in alignment criteria to more than one runway: VOR RWY 14L/R, VOR RWY 5/7.

f. PinS procedures apply the type of navigation followed by the published final approach course.

Examples: ILS OR LOC 353, RNAV (GPS) 025, COPTER RNAV (GPS) 247, VOR 221, COPTER VOR 243

Section 1-6. Identification of IFPs › 1-6-4. Combined Charting of Approach Procedures.

g. Helicopter procedures to IFR heliports apply PinS naming.

1-6-3. Circling Approach Procedures. When the approach does not meet criteria authorizing straight-in landing minimums, identification includes the following elements:

a. The navigation system (and sensor when applicable) as specified in paragraph 1-6-2.a.

b. A non-repeating alphabetical suffix assigned sequentially.

(1) The first approach established uses the suffix “A” even though there may be no intention to establish additional procedures. Only suffixes “A” through “H” may be used.

(2) Do not duplicate the alphabetical suffix where there are multiple circling procedures at the same airport, even when the procedures use different navigation systems; if additional procedures are established, they must be identified alphabetically in sequence. A revised approach procedure will use its original identification.

Examples: NDB-A, VOR-B, LDA-C

(3) The alphabetical suffix must not be duplicated at airports with identical city names within the same state, regardless of the airport name/navigation system guidance.

Example:

State GA GA GA

City Atlanta Atlanta Atlanta

Airport

KFTY KCCO KPDK

Procedure name

VOR-A NDB-B LDA-C

1-6-4. Combined Charting of Approach Procedures. A VOR approach may be combined with a TACAN approach if they share common tracks, fixes, fix altitudes, and missed approach instructions. An ILS approach may be combined with a LOC approach if they share common tracks, fixes and fix altitudes (excluding the precise final approach fix (PFAF), missed approach point (MAP) and any final segment step down fixes), and missed approach instructions. Identify as specified in paragraph 1-6-2, except the runway number element (single suffix for circling) is included only with the last approach listed, and identifications are connected by the word “or.”

Examples: ILS or LOC RWY 36L, VOR or TACAN RWY 31, ILS Z or LOC Z RWY 18, ILS Z or LOC RWY 36, ILS Z or LOC Y RWY 28, VOR or TACAN-A

1-6-5. Non-part 97 Approach Procedure Naming. Non-part 97 straight-in approach procedures will be designated with the suffixes “M,” “N,” “P,” or “Q.” Circling-only approach procedures will be designated with the suffixes “J” or “K.”

a. The first approach established uses the suffix “M” (or “J” if circling-only) even though there may be no intention to establish additional procedures.

e. Non-part 95 routes are identified by their usage. › (2) Helicopter RNAV routes are identified by a letter supplemented with…

b. Do not duplicate the alphabetical suffix where there are multiple non-part 97 approach procedures at the same airport, even when the procedures use different navigation systems; if additional procedures are established, they must be identified alphabetically in sequence. A revised approach procedure will use its original identification.

c. The alphabetical suffix must not be duplicated at airports with identical city names within the same state, regardless of the airport name/navigation system guidance.

Examples: ILS M or LOC M RWY 36L, VOR N RWY 31, NDB-J

1-6-6. Departure Procedure Identification. For named departures, see Order 8260.46, Departure Procedures (DP) Program.

1-6-7. En Route Procedure Identification. ATS routes are identified with names or letter designators associated with specific route types.

a. Low/Medium Frequency (L/MF) routes are identified by color names: Amber, Blue, Green, or Red.

b. VOR routes are identified by the letter “V.”

c. Jet routes (Flight Level (FL) 180 through FL 450) are identified by the letter “J.”

d. RNAV routes are identified by their usage.

(1) Low altitude (below FL 180) RNAV routes are identified by the letter “T.”

“Q.”

(2) High altitude (FL 180 through FL 450) RNAV routes are identified by the letter

“TK.”

(3) Helicopter RNAV routes are identified by a letter supplemented with a suffix:

e. Non-part 95 routes are identified by their usage.

(1) Low altitude (below FL 180) RNAV routes are identified by the letter “Z.”

(2) Helicopter RNAV routes are identified by a letter supplemented with a suffix: “ZK.”

1-6-8. Standard Terminal Arrival Identification. See Order 8260.19.

Section 1-7. IFP Publication › 1-7-3. Effective Date.

Section 1-7. IFP Publication

1-7-1. Submission. IFPs must be submitted by the approving authority on forms provided by the originating agency. IFPs must be routed under current orders or directives of the originating agency.

1-7-2. Issuance. The FAA Administrator (or designee) is responsible for issuing civil instrument procedures. The military approving authorities are responsible for issuing military instrument procedures.

1-7-3. Effective Date. See Orders 8260.19 and 8260.26, Establishing Submission Cutoff Dates for Civil Instrument Flight Procedures, or applicable military directive(s). FAA policy does not permit the issuance of complete civil instrument approach procedures by NOTAM.

2-1-3. Level OCS. › a. This method of applying ROC results in a horizontal band of airspace…

Chapter 2. General Criteria

Section 2-1. Common Information

2-1-1. Scope. This chapter contains only that information common to all types of TERPS. Criteria, which do not have general application, are located in the individual chapters concerned with the specific types of facility, navigation source, or application.

2-1-2. Required Obstacle Clearance (ROC). This order specifies the minimum measure of obstacle clearance considered by the FAA to supply a satisfactory level of vertical protection. The validity of the protection is dependent, in part, on assumed aircraft performance. In the case of TERPS, it is assumed that aircraft will perform within certification requirements.

a. These criteria are predicated on normal aircraft operations for considering obstacle clearance requirements. Normal aircraft operation means all aircraft systems are functioning normally, all required navigation systems are performing within flight inspection parameters, and the pilot is conducting instrument operations utilizing IFPs based on the TERPS standard to provide ROC.

b. While the application of TERPS criteria indirectly addresses issues of flyability and efficient use of navigation systems, the major safety contribution is the provision of obstacle clearance standards. This facet of TERPS allows aeronautical navigation in instrument meteorological conditions (IMC) without fear of collision with unseen obstacles. ROC is provided through application of level and sloping obstacle clearance surface (OCS).

2-1-3. Level OCS. The level OCS concept is applicable to “level flight” segments. These segments are level flight operations intended for en route, STAR, feeder, initial, intermediate, and NPA final approach segments. A single ROC value is applied over the length of the segment. These values were determined through testing and observation of aircraft and pilot performance in various flight conditions. Typical ROC values are: 1000 feet (2000 over designated mountainous terrain) for en route, STAR, and feeder segments, 1000 feet for initial segments, 500 feet for intermediate segments, and 250-500 feet for final segments.

a. This method of applying ROC results in a horizontal band of airspace that cannot be penetrated by obstacles. The bottom surface of the ROC band is mathematically placed on top of the highest obstacle within the segment. The depth (ROC value) of the band is added to the obstacle height to determine the minimum altitude authorized for the segment. The bottom surface of the ROC band is referred to as the level OCS. Therefore, level flight segments are evaluated by the level OCS application standard (see Figure 2-1-1).

2-1-4. Sloping OCS. › a. Descending on a PA/APV glidepath. The obstacle evaluation method for…

Figure 2-1-1. Minimum Segment Altitude

2-1-4. Sloping OCS. The method of applying ROC, in segments dedicated to descending on a glidepath or climbing in a departure or missed approach segment, requires a different obstacle clearance concept than the level OCS because the ROC value must vary throughout the segment. The value of ROC near the runway is relatively small and increases throughout the segment.

Note: While slope ratios are normally expressed in terms of rise over run in engineering and professional technical jargon, TERPS has traditionally expressed slope ratios in terms of run over rise; for example 34:1, 40:1 (see Figure 2-1-2).

Figure 2-1-2. TERPS Slope Ratio

a. Descending on a PA/APV glidepath. The obstacle evaluation method for descent on a glidepath is the application of a descending OCS below the glidepath. The vertical distance between the glidepath and the OCS is the ROC; thus ROC = (glidepath height) - (OCS height). The ROC decreases with distance from the PFAF as the OCS and glidepath are converging towards the landing surface (see Figure 2-1-3). The OCS slope and glidepath angle (GPA) values are interdependent: OCS Slope = 102/GPA; or GPA = 102/OCS slope.

b. Climbing on departure or missed approach. The concept of providing… › (1) The obstacle evaluation method for a climb segment is the…

Figure 2-1-3. PA/APV Glidepath Descent

(1) If the OCS is penetrated, the OCS slope may be adjusted upward, thereby increasing the glidepath angle. The glidepath angle would increase because it is dependent on the required slope.

(2) Descent on an ILS/LPV glidepath and descent on other types of glidepaths such as barometric vertical navigation (baro-VNAV) provide ROC through application of a descending sloping surface based on standards using differing formulas, but the concept is the same.

b. Climbing on departure or missed approach. The concept of providing obstacle clearance in the climb segment of an IFP is based on the aircraft maintaining a minimum climb gradient. The climb gradient must be sufficient to increase obstacle clearance along the flight path so that the minimum ROC for the subsequent segment is achieved prior to leaving the climb segment. The minimum climb gradient that will provide adequate ROC in the climb segment is 200 ft/nautical mile (NM) (400 ft/NM for helicopters), unless a higher gradient is specified.

(1) The obstacle evaluation method for a climb segment is the application of a rising OCS below the minimum climbing flight path. Whether the climb is for departure or missed approach is immaterial. The vertical distance between the climbing flight path and the OCS is ROC. ROC for a departure segment is defined as ROC = 0.24 × CG. This concept is often called the “24 percent rule.” Altitude gained is dependent on climb gradient (CG) expressed in ft/NM.

(a) For other than helicopters, the minimum ROC supplied by the 200 ft/NM CG is 48 ft/NM (0.24 × 200 = 48). Since 48 of the 200 feet gained in 1 NM is ROC, the OCS height at that point must be 152 feet (200 − 48 = 152), or 76% of the CG (152/200 = 0.76). The slope of a surface that rises 152 feet over 1 NM is 40:11 (see Figure 2-1-4).

(b) Helicopters utilize ROC = 0.24 × CG to achieve 96 ft/NM of ROC with a 400 ft/NM CG. Since 96 of the 400 feet gained in 1 NM is ROC, the OCS height at that point is 304 feet (400 − 96 = 304), or 76% of the CG (304/400 = 0.76). The slope of a surface that rises 304 feet over 1 NM is 20:12 (see Figure 2-1-4).

1 1852 /0.3048 ≈ 39.97, rounded to 40 152 2 1852 /0.3048 ≈ 19.99, rounded to 20 304

b. Climbing on departure or missed approach. The concept of providing… › (2) Where an obstruction penetrates the sloping OCS, a climb gradient…

Figure 2-1-4. Climb Segment

(2) Where an obstruction penetrates the sloping OCS, a climb gradient greater than 200 ft/NM (400 ft/NM for helicopters) is required to provide adequate ROC. Departure climb gradients greater than standard will have ROC greater than 48 ft/NM (96 ft/NM for helicopters) since ROC is equal to 24% of the climb gradient. The ROC expressed in ft/NM can be calculated using Formula 2-1-1. However, instead of calculating the ROC value, the required climb gradient is normally calculated directly using Formula 2-1-2. Refer to Chapter 10 for ILS missed approach climb gradients.

Formula 2-1-1. Departure Sloping Segment ROC

(0.24 × ℎ) 𝑅𝑅𝑅𝑅𝑅𝑅 = (0.76 × 𝐷𝐷) Where: ℎ = Height of obstacle above the altitude from which the climb is initiated 𝐷𝐷 = Distance in NM from the initiation of the climb to the obstacle

Formula 2-1-2. Departure Climb Gradient

ℎ 𝑅𝑅𝐶𝐶 = (0.76 × 𝐷𝐷) Where: ℎ = Height of obstacle above the altitude from which the climb is initiated 𝐷𝐷 = Distance in NM from the initiation of the climb to the obstacle

c. In the case of an instrument departure, the sloping OCS is applied during the climb until en route ROC is attained. The OCS begins at the departure end of runway, at the elevation of the runway end. ROC is zero at the runway end, and increases along the departure route until the appropriate ROC value is attained to allow en route flight to commence.

Section 2-1. Common Information › 2-1-7. Approach Categories.

d. In the case of a missed approach procedure, the climbing flight path starts at the height of the minimum descent altitude (MDA) or decision altitude (DA) minus height loss. The OCS starts approximately at the MAP/DA at an altitude of MDA/DA minus the final segment ROC and adjustments (see paragraph 3-2-2). Therefore, the final segment ROC is assured at the beginning of the OCS and increases as the missed approach route progresses. The OCS is applied until at least the minimum en route or holding value of ROC is attained (as appropriate).

e. Extraordinary circumstances, such as a mechanical or electrical malfunction, may prevent an aircraft from achieving the minimum climb gradient assumed by TERPS. In these cases, adequate obstacle clearance may not be provided by published IFPs. Operational procedures contained outside TERPS guidelines are required to cope with these abnormal scenarios.

2-1-5. Units of Measurement. Units of measurement must be expressed as set forth below:

a. Bearings, courses, and radials. Bearings and courses must be expressed in degrees magnetic. Radials must also be expressed in degrees magnetic, and must further be identified as radials by prefixing the letter “R” to the magnetic bearing from the facility. For example, R-027 or R-010.

b. Altitudes. The unit of measure for altitude in this publication is feet. Published heights below the transition level (18000 feet) must be expressed in feet above mean sea level (MSL); for example, 17900 feet. Published heights at and above the transition level (18000 feet) must be expressed as flight levels; for example, FL 180, FL 190, etc.

c. Distances. Develop all distances in NM and hundredths, except where feet are required (1 NM = 1852/0.3048 feet). When applied to visibilities, distances must be expressed in statute miles (SM) (5280 feet/SM) and the appropriate fractions thereof (see Section 3-3). Runway visual range (RVR) must be expressed in feet.

d. Speeds. Aircraft speeds must be expressed in knots indicated airspeed (KIAS).

2-1-6. Positive Course Guidance (PCG). PCG is achieved where pilots receive a continuous display of navigation data, which enable the aircraft to be flown along a specific course line or track. For courses based on a ground-based navigation facility, PCG is possible only within the standard or expanded service volume of the facility. PCG must be provided for feeder routes, initial (except as provided for in paragraph 2-4-4), intermediate, and final approach segments.

2-1-7. Approach Categories. Aircraft performance differences have an effect on the airspace and visibility needed to perform certain maneuvers. Because of these differences, aircraft manufacturer/operational directives assign an alphabetical category to each aircraft (see 14 CFR part 97). The categories used and referenced throughout this order are CAT A, B, C, D, and E. For helicopter-only approaches, COPTER is an authorized category. The authorized CAT must be used to determine OEAs for circling and missed approaches and used to establish landing minimums.

2-1-8. Procedure Construction. An instrument approach procedure (IAP) may have as many as four separate segments. They are the initial, intermediate, final, and missed approach segments. In addition, an area for circling the airport under visual conditions is considered when circling is

Section 2-1. Common Information › 2-1-9. Continuous Descent Approach (CDA).

authorized. An approach segment begins and ends at the plotted position of the fix; however, under some circumstances certain segments may begin at specified points where no fixes are available. The fixes are named to coincide with the associated segment. For example, the intermediate segment begins at the intermediate fix (IF) and ends at the PFAF. The order in which this chapter discusses the segments is the same order in which the pilot would fly them in a completed procedure; that is from an initial, through an intermediate, to a final approach. In constructing the procedure, the FAC should be identified first because it is the least flexible and most critical of all the segments. Then establish the other segments to produce an orderly maneuvering pattern responsive to the local traffic flow and to conserve controlled airspace to the maximum extent possible (see Figure 2-1-5).

Figure 2-1-5. Segments of an Approach Procedure

2-1-9. Continuous Descent Approach (CDA). CDA is a procedure that optimizes the aircraft approach from the beginning of its descent to touch-down. With CDA, noise and emission levels are substantially reduced and significant fuel cost savings can be realized by participating aircraft. CDA procedures do not require special instrument approach design criteria; they can be flown using existing instrument approach procedures where “at or above” altitudes are established based on the minimum ROC required for the segment. This allows pilots to descend at the optimum profile for their aircraft while maintaining a safe altitude. Mandatory and/or maximum altitude restrictions severely restrict the use of CDA and should only be implemented where absolutely necessary.

2-1-10. Aircraft Speed. Do not establish speed restrictions that require an aircraft to exceed the restrictions in 14 CFR part 91.117 (a) and (c).

2-2-3. Routes and Transitions. › a. En route transitions. En route transitions are established prior to…

Section 2-2. Standard Terminal Arrival Procedures

2-2-1. Standard Terminal Arrival. A STAR is a preplanned route designed to facilitate the transition from the en route environment to the terminal environment for landing at one or more airports.

2-2-2. Origination and Termination.

a. A STAR must originate from a fix (see Appendix B). The distance between the origination fix and any airport served by the STAR should not exceed 200 NM.

b. A STAR must terminate at a fix. The fix may be:

(1) A point-in-space.

(2) A fix that is also charted on an IAP.

(a) When charted on an instrument approach procedure, the termination fix must be a feeder fix, IAF, or IF. The termination fix must be the first fix that is common to both the STAR and the IAP (the STAR and the IAP must not share more than one common fix, and that fix must be the last fix on the STAR).

(b) When charted as an IAF or IF on an IAP and the approach procedure contains a course reversal, the approach segment following the STAR termination fix must be designated as “no procedure turn” (NoPT).

c. Specify a heading or course to fly after the termination fix when requested by ATC.

2-2-3. Routes and Transitions. A STAR serving a single airport consists of a common route, with optional en route and/or runway transitions. A STAR without a common route (such as a STAR with only a common point) may also be established if it contains at least two en route transitions or at least two runway transitions. STARs serving multiple airports may consist of separate common routes to each airport; however, all common routes must begin at a fix that serves all airports.

a. En route transitions. En route transitions are established prior to the first fix of a common route. An en route transition must terminate at a fix common to all en route transitions on the same STAR.

b. Runway transitions. Runway transitions may only be established for a single airport served by the STAR. They are established between the last fix of a common route and a fix that serves a runway (or multiple runways at the same airport).

c. Positive course guidance. Positive course guidance is required for all segments of a conventional (non-RNAV) STAR from origination to the termination fix.

2-2-4. Alignment.

a. The angle of intersection between the initial routing of a ground-based STAR and the ATS route where it begins (if applicable) must not exceed 120 degrees. For RNAV STARs, apply Order 8260.58, United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.

2-2-7. Altitudes. › d. En route transitions.

b. When a STAR terminates at a fix located on an approach procedure, the maximum angle of intersection is 90 degrees.

c. The approach procedure segment following a STAR termination fix must meet the minimum length standards required for the magnitude of turn necessary to transition from the STAR.

2-2-5. Area. For routes based on a ground-based navigational aid (NAVAID), apply Chapter 14. For RNAV routes, apply Order 8260.58.

2-2-6. Obstacle Clearance. Apply criteria in Chapter 14.

2-2-7. Altitudes.

a. Minimum en route altitudes (MEAs) and published altitudes must:

(1) Provide at least the minimum ROC. ROC must be provided from each fix with an altitude restriction to the previous altitude restriction except maximum altitude restrictions.

(2) Meet communication and navigational facility requirements.

(3) Be established in 100-foot increments; when necessary round to the next higher 100-foot increment (for example, when obstacle elevation plus ROC equals 3001, round up to 3100).

b. Altitude restrictions above FL 200 should only be published to support an operational requirement.

c. When altitude restrictions are necessary, establish in the following order of preference (see exceptions in paragraphs 2-2-7.e and 2-2-7.f):

(1) Minimum altitudes. Example: AT/ABOVE 9000

(2) Block altitudes. Example: AT/ABOVE 9000 AT/BELOW 12000

(3) Mandatory altitudes. Example: AT 6000. Exception: A mandatory altitude is the first preference for the last fix on a STAR if the fix is not shared with an approach procedure.

(4) Maximum altitudes. Example: AT/BELOW 12000

d. En route transitions.

2-2-7. Altitudes. › f. STAR termination altitude.

(1) Establish an MEA between fixes on the transition.

(2) Establish a minimum obstruction clearance altitude (MOCA) between fixes on a transition.

(3) Do not apply minimum crossing altitude (MCA) criteria. An MEA or a MOCA must not be higher than the previous MEA or MOCA (as applicable); increase previous MEAs/MOCAs as necessary to comply.

(4) Do not raise an MEA to support ATC operational requirements. An altitude restriction must be used if ATC has an operational requirement for an altitude higher than the MEA.

e. Common route and runway transitions. Establish a mandatory, minimum or block altitude restriction at a fix that represents the lowest altitude authorized by the STAR or STAR runway transition.

(1) Establish additional altitudes as required for obstacle clearance or to support an ATC operational requirement.

(2) When a maximum altitude restriction is established, also establish a minimum altitude at the same fix (a block altitude) or at a subsequent fix to ensure obstacle clearance. The subsequent minimum altitude (or minimum altitude of a block) must also provide obstacle clearance to the previous fix(es) with a maximum altitude. For example, publishing a maximum altitude at CHRLY (as shown in Figure 2-2-1) requires the addition of a minimum altitude at CHRLY or the minimum altitude at DELTA must provide obstacle clearance back to the previous minimum altitude (in this example, the minimum altitude of a block) at BRAVO.

(3) Do not establish MEAs or MOCAs for common routes or runway transitions.

f. STAR termination altitude.

(1) An altitude restriction must be established at the termination fix of the STAR if the same fix is charted on an approach procedure. If the approach procedure fix has an altitude restriction associated with it, then the STAR termination altitude restriction must be identical to it. For example, if the approach procedure’s fix is a mandatory altitude, then the STAR must end with an identical mandatory altitude. If the approach procedure’s fix is a minimum altitude, then the STAR must end with an identical minimum altitude.

(2) If the STAR authorizes radar vectors after the termination fix, an altitude is required at the termination fix and that altitude must be at or above the minimum vectoring altitude (MVA) and/or minimum IFR altitude (MIA) (as applicable). If the STAR authorizes radar vectors after the termination fix and does not join an approach, then the altitude authorized at the termination fix should be a mandatory altitude. Flight Standards approval is required if no altitude is established due to an operational need (see paragraph 1-4-2).

(3) If the STAR termination fix will be authorized for either joining an approach or for radar vectors, the altitude must be above the MVA/MIA and comply with paragraph 2-2-7.f(1).

(4) A STAR termination altitude may be no lower than any instrument approach procedure fix altitude to be flown after the STAR termination. If the approach procedure has no altitude charted at that approach procedure fix, the STAR termination altitude may be no lower than any approach procedure minimum segment altitude following that fix.

a. The maximum DG (see Figure 2-21) is based on altitude, deceleration,… › (3) When a STAR contains a descent between fixes that passes through…

2-2-8. Descent Gradient (DG). Calculate DGs between fixes with an altitude restriction by using the guidance in this paragraph and the calculation methods in Section 2-9. When deceleration is required, also use paragraphs 2-2-9 and 2-2-10. The DG past the termination fix of the STAR is not calculated as part of the STAR design; the overall airspace design should optimize the location and altitude for the STAR termination fix and that becomes an input to the STAR design.

a. The maximum DG (see Figure 2-2-1) is based on altitude, deceleration, and airspeed constraints, as follows:

(1) The maximum permissible DG 10000 feet MSL and above is 330 ft/NM (approximately 3.11 degrees).

(2) The maximum permissible DG below 10000 feet MSL is 318 ft/NM (approximately 3.0 degrees).

(3) When a STAR contains a descent between fixes that passes through 10000 feet MSL, the maximum permissible DG is between 318 ft/NM and 330 ft/NM and is in proportion to the amount of the altitude change that is below/above 10000 feet MSL. Use Formula 2-2-1 to determine the maximum DG (DGmax) between fixes that contain a descent that passes through 10000 feet MSL.

Formula 2-2-1. Maximum DG Passing Through 10000 Feet MSL (ft/NM)

(𝐴𝐴𝐴𝐴𝐴𝐴1 − 10000) × 12 𝐷𝐷𝐶𝐶𝐷𝐷𝐷𝐷𝐷𝐷 = + 318 (𝐴𝐴𝐴𝐴𝐴𝐴1 − 𝐴𝐴𝐴𝐴𝐴𝐴2) Where: 𝐴𝐴𝐴𝐴𝐴𝐴1 = Altitude at the fix prior to crossing 10000 feet MSL 𝐴𝐴𝐴𝐴𝐴𝐴2 = Altitude at the fix after crossing 10000 feet MSL

Example 1: From BRAVO to CHRLY in Figure 2-2-1, the altitude of 11000 minimum at BRAVO and 9000 maximum at CHRLY, will have 1/2 of the gradient at 330 ft/NM and 1/2 at 318 ft/NM, Maximum DG = (11000 – 10000) × 12 / (11000 – 9000) + 318 = 324.

Example 2: In the previous example if there were no altitude restrictions at BRAVO, the gradient applies from ALPHA to CHRLY. Maximum DG = (19000 – 10000) ×

12 / (19000 – 9000) + 318 = 328.8.

Example 3: From GOLFF to HOTEL in Figure 2-2-2, the mandatory altitude of 15000 at GOLFF and a mandatory altitude of 4000 at HOTEL, will have 5/11 of the gradient at 330 ft/NM and 6/11 at 318 ft/NM, Maximum DG = (15000 – 10000) × 12 / (15000 – 4000) + 318 = 323.45.

Note: Descent below 10000 feet MSL requires a deceleration calculation unless an airspeed restriction of 250 KIAS or less exists prior to the point where the descent below 10000 feet MSL occurs.

2-2-8. Descent Gradient (DG). › d. Figure 2-21 and Figure 2-22 illustrate examples of STAR design.…

(4) Gradient after deceleration to 220 KIAS. After a speed restriction of 220 KIAS or less is used, for subsequent fixes along the route of the STAR the maximum permissible descent gradient is 250 ft/NM (approximately 2.36 degrees).

(5) Evaluation of a fix with no altitude restriction. The evaluation is done from the previous fix that has an altitude restriction to the subsequent fix that has an altitude restriction using the overall distance between the fixes with the restrictions.

(6) If more than one of paragraphs 2-2-8.a(1) through 2-2-8.a(5) applies, use the lower of the resulting values for the maximum DG.

Figure 2-2-1. Altitude Restrictions and Maximum Descent Gradient

b. When a gradient exceeds the maximum DG allowed in paragraph 2-2-8.a, the STAR requires approval (see paragraph 1-4-2).

c. The descent gradient between any two consecutive fixes with an altitude restriction should be at least 150 ft/NM (approximately 1.41 degrees). Descent gradients of less than 150 ft/NM (or no descent as depicted between HOTEL and INDIA in Figure 2-2-2) should not be used except to support an operational requirement.

d. Figure 2-2-1 and Figure 2-2-2 illustrate examples of STAR design. Figure 2-2-1 shows different flight paths to illustrate the recommended design of allowing some flexibility in the

2-2-9. Speed Restrictions. › d. If a STAR terminates at a fix charted on an instrument approach…

descent, preferably through the use of minimum altitudes. Figure 2-2-1 shows the recommended design of all altitude constraints being on or above the 150 ft/NM line; an ATC and/or airspace requirement is shown in Figure 2-2-2 with no descent between HOTEL and INDIA. The solid blue line, depicting the maximum descent gradient, depicts the upper design limit for fixes prior to an altitude constraint. As shown in Figure 2-2-2, the use of mandatory altitude constraints reduces the range of altitudes allowed at previous fixes and may result in an inefficient descent for aircraft on the STAR.

Figure 2-2-2. Altitude Restrictions With Mandatory Altitudes

2-2-9. Speed Restrictions. Minimize the use of speed restrictions as much as practicable. Optimum values are 280 KIAS at 10000 feet MSL or above and 240 KIAS below 10000 feet MSL.

a. Speed restrictions above FL 200 should only be published to support an operational requirement. When published, the restriction must allow for Mach transition (see Order 8260.19, Chapter 4).

b. Do not establish more than one speed restriction per fix (for example, one speed applicable to jets and one applicable to props).

c. If a STAR terminates at a fix charted on an approach procedure, and the fix has a charted speed restriction, then establish a speed restriction on the STAR with the same numerical airspeed value. The STAR’s speed restriction must be a mandatory (“at”) speed restriction and the approach procedure must be a maximum (“at or below”) speed restriction. For example, if the approach procedure’s speed restriction is a maximum airspeed of 210 KIAS, then the STAR’s speed restriction at the same fix must indicate a mandatory airspeed of 210 KIAS.

d. If a STAR terminates at a fix charted on an instrument approach procedure, and the fix does not have a speed restriction, then verify if the approach procedure contains a speed

2-2-10. Deceleration. › b. When descent is permitted, the descent gradient leading to the fix…

restriction located prior to the fix. If the approach procedure contains a speed restriction, then establish a mandatory speed restriction with the same numerical airspeed at or prior to the termination of the STAR.

e. For the portion of a STAR underlying a Class B airspace area, do not establish a speed restriction that requires aircraft to exceed 200 KIAS.

2-2-10. Deceleration. Sufficient distance and a reduced descent gradient are required prior to any fix with a speed restriction. STARs not meeting the requirements of this paragraph may be authorized with Flight Standards approval (see paragraph 1-4-2). When an altitude restriction exists at a fix that could place an aircraft below Class B airspace, consideration should be given for deceleration for the aircraft to comply with the 200 KIAS airspeed restriction.

a. Where deceleration is required but descent is not permitted (for example, between two fixes with the same mandatory altitudes) or is not required (for example, between two fixes with the same minimum altitudes), provide a minimum distance of at least 4 NM prior to a fix with a speed reduction of 40 KIAS or less. For deceleration greater than 40 KIAS, allow 1 NM between fixes for every 10 knots of deceleration required. For example, a deceleration of 10, 20, 30, or 40 KIAS requires a minimum length of 4 NM; a deceleration of 50 KIAS requires a minimum length of 5 NM; a deceleration of 60 KIAS requires 6 NM.

b. When descent is permitted, the descent gradient leading to the fix with the speed restriction must be reduced. Apply Formula 2-2-2 to determine the minimum deceleration distance (DecelD) required before the fix; the greater distance leads to a reduced descent gradient.

(1) In determining the applicable formula gradient value, “G,” use 330 ft/NM (approximately 3.11 degrees) when the ending speed restriction is greater than or equal to 250 KIAS; use 318 ft/NM (approximately 3.0 degrees) when the ending speed restriction is less than 250 KIAS but greater than 220 KIAS; use 250 ft/NM (approximately 2.36 degrees) when the ending speed restriction is 220 KIAS or less.

(2) In determining “K,” use 310 KIAS, or the previous speed restriction if less than 310 KIAS, as the reference speed at or above 10000 feet MSL. For the reference speed below 10000 feet MSL, use 250 KIAS or the previous speed restriction if less. For a block altitude, use the minimum altitude when selecting 310 or 250 to use to determine the “K” value.

(3) The first altitude restriction that is below 10000 feet MSL requires a deceleration evaluation unless an airspeed restriction of 250 KIAS or less exists prior to the point where descent below 10000 feet MSL occurs. If no speed is published at the first altitude restriction that is below 10000 feet MSL, then use the lower of 250 KIAS or the previous speed restriction (if applicable). When the first fix that allows descent below 10000 feet MSL has no charted speed restriction and the altitude constraint allows continued flight above 10000 feet MSL, the calculation is extended to the subsequent fix using the total descent and total distance for the applicable fixes.

(4) Some examples are as follows: If deceleration from a fix with no speed restriction to 280 KIAS is required above 10000 feet MSL, then “K” is equal to 3 NM(K = 310-280 / 10).

If an aircraft is decelerating from a fix with a speed restriction of 280 KIAS to a fix with no speed restriction that is below 10000 feet MSL, use 250 KIAS as the reference airspeed; then “K” is equal to 3 NM(K = 280-250 / 10). If an aircraft is decelerating from a fix with no speed restriction that is below 10000 feet MSL, use 250 KIAS as the reference airspeed for the deceleration to the next fix; if the deceleration is to a fix with a speed restriction of 230 KIAS, then “K” is equal to 2 NM(K = 250-230 / 10).

Formula 2-2-2. Minimum Deceleration Distance (NM)

𝐴𝐴𝐴𝐴𝐴𝐴1 − 𝐴𝐴𝐴𝐴𝐴𝐴2 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐴𝐴𝐷𝐷 = + 𝐾𝐾 𝐶𝐶 Where: 𝐴𝐴𝐴𝐴𝐴𝐴1 = Minimum altitude at the fix prior to the speed restriction 𝐴𝐴𝐴𝐴𝐴𝐴2 = Minimum altitude at the fix with the speed restriction 𝐶𝐶 = Applicable gradient value (330/318/250) 𝐾𝐾 = 1 NM for every 10 KIAS of deceleration required

Example 1: If the termination fix has a mandatory altitude of 3000 and a published speed restriction of 210 KIAS and is preceded by a fix with a minimum altitude of 7500 and a published speed restriction at or before that fix of 230 KIAS, the values are: Alt1 - Alt2 = 4500 (7500-3000); G = 250, based on an ending speed of 220 KIAS or less; K = 2 NM (K = 230-210 / 10); 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐴𝐴𝐷𝐷 = 20 NM (𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐴𝐴𝐷𝐷 = 4500/250 + 2) and the resulting descent gradient will be no more than 225.0 ft/NM (DG = 4500 / 20).

Example 2: In example 1, if the preceding fix has no speed restriction, use 250 KIAS based on the altitude of 7500 being below 10000 feet MSL (or previous speed restriction if less than 250 KIAS). The values are: Alt1 - Alt2 = 4500; G = 250, K = 4 NM (K = 250-210 / 10); 𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐴𝐴𝐷𝐷 = 22 NM (𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐷𝐴𝐴𝐷𝐷 = 4500/250 + 4). The resulting descent gradient will be no more than 204.5 ft/NM (DG = 4500 / 22).

Chapter 2. General Criteria › Section 2-3. Feeder Routes/Emergency Areas

Section 2-3. Feeder Routes/Emergency Areas

2-3-1. Feeder Routes. Establish non-radar feeder routes where the IAF is not part of the en route structure and where preferred over other options [for example, radar vectors, terminal arrival area (TAA)]. Limit the number of feeder routes where radar vectoring is provided on a 24-hour basis, but where practical provide at least one route per location to account for radar/communications failure. Feeder routes originate at a navigation facility or named fix on an airway and terminate at another feeder fix or at an IAF. The feeder route must not extend beyond the operational service volume of the facility which provides navigational guidance.

a. Alignment.

(1) The angle of intersection between a ground-based feeder route course and the en route structure must not exceed 120 degrees. For RNAV routes, apply Order 8260.58.

(2) The angle of intersection between a ground-based feeder route course and the next segment (feeder/initial) course must not exceed 120 degrees except when connecting to a course reversal segment. For RNAV routes, apply Order 8260.58.

(3) Do not establish a feeder route that terminate at a course reversal fix if both the angle of intersection between the route and the segment that follows the course reversal fix is 120 degrees or less (90 degrees or less for RNAV), and if the required descent is within initial segment limitations (see paragraph 2-4-3). Under these conditions, the route must be developed as an initial segment based on straight course criteria.

b. Area. For routes based on ground-based NAVAIDs, apply Chapter 14. When connecting to a course reversal segment, the area terminates at a line perpendicular to the feeder course through the course reversal fix. For RNAV routes, apply Order 8260.58.

c. Obstacle clearance. Apply criteria in Sections 14-2 or 14-5 as appropriate. The published minimum feeder route altitude must provide at least the minimum ROC value and must not be less than the altitude established at the IAF. Establish minimum altitudes in 100-foot increments; when necessary round to the next higher 100-foot increment (for example, when obstacle elevation plus ROC equals 3001, round up to 3100).

d. Descent gradient. The optimum descent gradient in the feeder route is 250 ft/NM. Where a higher descent gradient is necessary, the maximum gradient is 500 ft/NM. The optimum descent gradient for feeder routes associated with high altitude procedures is 800 ft/NM. Where a higher descent gradient is necessary, the maximum gradient is 1000 ft/NM.

2-3-2. Minimum Safe Altitude (MSA). Establish an MSA for all approach procedures, graphic obstacle departure procedures (ODPs), and standard instrument departures (SIDs) within a 25-NM radius of a specified point for use during emergency situations (see Figure 2-3-1).

a. Altitude selection. Specify altitudes in 100-foot increments; when necessary round to the next higher 100-foot increment (for example, when obstacle elevation plus ROC equals 1501, round up to 1600).

b. Area.

(1) Non-RNAV procedures. Center the MSA on the omni-directional facility upon which the procedure is based. When the distance from the facility to the airport exceeds 25 NM, extend the radius to include the airport or heliport landing surfaces up to a maximum distance of 30 NM. When the procedure does not use an omnidirectional facility (for example, an ILS or vector SID), use the primary omnidirectional facility in the area. If a graphic OPD or SID utilizes more than one omni-directional facility, use the facility nearest the airport or heliport. If no omni-directional NAVAID is located within 30 NM of the airport landing surfaces, then center the MSA on the airport reference point (ARP) or heliport reference point (HRP). Establish a common area (no sectors) around the facility or ARP/HRP. If necessary to offer relief from obstacles, sector divisions may be established for an MSA based on a facility. Sectors must not be less than 90 degrees in spread.

(2) RNAV procedures. For RNAV straight-in approach procedures, establish a common safe altitude within the specified radius of the runway threshold (preferred) or the MAP waypoint (WP); for RNAV circling and RNAV departure procedures use the airport waypoint (APT WP). For approaches to or departures from a heliport, use the heliport waypoint.

(3) PinS procedures. For PinS approach procedures, establish a common safe altitude within the specified radius of the MAP WP. For PinS departure procedures, use the initial departure fix (IDF).

c. Obstacle clearance. Common safe altitudes and sector altitudes must provide 1000 feet of obstacle clearance to include a 4-NM buffer area beyond the 25-NM radius, and a 4-NM buffer area in any adjacent sector. Sector altitudes should be raised and combined with adjacent higher sectors when the altitude difference is 300 feet or less.

Figure 2-3-1. MSA

2-3-3. Emergency Safe Altitude (ESA). ESAs are applicable to military procedures at the option of the approving authority. Establish ESAs within a 100-NM radius of the navigation facility or WP used as the ESA center, with a common altitude for the entire area. Where ESAs are located in designated mountainous areas, provide at least 2000 feet of obstacle clearance. Paragraph 2-3-2.a applies.

a. Alignment. › (1) Straight courses.

Section 2-4. Initial Approach

2-4-1. Initial Approach Segment. The instrument approach commences at the IAF. In the initial approach, the aircraft has departed the en route phase of flight and is maneuvering to enter an intermediate segment. An initial approach may be made along an arc DME, radial, course, heading, radar vector, or a combination thereof. PCG is required except when dead reckoning (DR) courses can be established over limited distances. Although more than one initial approach may be established for a procedure, the number should be limited to that which is justified by traffic flow or other operational requirements. Where practical, establish at least one initial segment that does not require a course reversal. Where alignment and/or descent gradient cannot be met and/or where otherwise operationally advantageous, initial segments requiring a course reversal may be established such as a procedure turn (PT), holding pattern descent, or high altitude teardrop turn.

a. When the IAF is part of the en route structure, the angle of intersection between the en route structure and a ground-based initial approach segment course must not exceed 120 degrees. For RNAV routes, apply Order 8260.58.

b. When the IF is part of the en route structure, it may not be necessary to establish an initial approach segment. In this case, the fix is designated as an IF/IAF and intermediate segment standards apply (see Section 2-5).

c. When the IAF is collocated with an IF (for example, in the case of a course reversal over the IF), the fix is also designated as an IF/IAF. The course reversal is considered to be the initial segment.

d. Where holding is required prior to entering the initial approach segment, the holding fix and IAF should coincide. When this is not possible, the IAF must be located within the holding pattern on the inbound holding course.

2-4-2. Altitude Selection. Minimum altitudes in the initial approach segment must be established in 100-foot increments. The selected altitude must provide the minimum ROC (plus adjustments as specified by paragraph 3-2-2); for example, when obstacle elevation plus ROC equals 1501, round up to 1600. The altitude selected must not be below the PT altitude where a PT is required. In addition, altitudes specified in the initial approach segment must not be lower than any altitude specified for any portion of the intermediate or final approach segment.

2-4-3. Initial Approach Segments Based on Straight Courses and Arcs with PCG.

a. Alignment.

(1) Straight courses. The angle of intersection between two successive initial approach courses and the angle of intersection between an initial approach course and an intermediate course must not exceed 120 degrees. When the angle between an initial approach course and intermediate course exceeds 90 degrees, a radial or bearing which provides at least 2 NM of lead must be identified to assist in leading the turn onto the intermediate course (see Figure 2-4-1).

(2) Arcs. › c. Obstacle clearance. The minimum ROC in the primary area is 1000…

Figure 2-4-1. Initial Approach Interception Angle Greater than 90 degrees

(2) Arcs. A DME arc may provide course guidance for all or a portion of an initial approach. The minimum arc radius is 7 NM. The radius for high altitude procedures should be at least 15 NM unless a reduced descent gradient is used (see paragraph 2-4-3.d). An arc may join a course at or before the IF. When joining a course at or before the IF, the angle of intersection of the arc and the course must not exceed 120 degrees. When the angle exceeds 90 degrees, a radial which provides at least 2 NM of lead must be identified to assist in leading the turn on to the intermediate course. DME arc courses must be predicated on DME collocated with a facility providing omnidirectional course information.

b. Area. The initial approach segment has no standard length. The length must be sufficient to permit the altitude change required by the procedure and must not exceed 50 NM unless an operational requirement exists. The total width of the initial approach segment is 6 NM on each side of the initial approach course. This width is divided into a primary area, which extends laterally 4 NM on each side of the course, and a secondary area, which extends laterally 2 NM on each side of the primary area (see Figure 2-4-1). When any portion of the initial approach is more than 50 NM from the navigation facility, the criteria for en route airways applies to that portion.

c. Obstacle clearance. The minimum ROC in the primary area is 1000 feet. The minimum ROC in the secondary area is 500 feet at the primary boundary, tapering uniformly to zero feet at the outer edge (see Figure 2-4-2). The minimum ROC at any given point in the secondary area is determined by Formula 2-4-1. Adjustments for precipitous terrain must be applied as specified in paragraph 3-2-2 (see also paragraph 2-4-2).

Continue reading ↓ 120 of 921 passages shown