Order 8260.3F United States Standard for Terminal Instrument Procedures (TERPS)
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.
This document is cancelled. Cancelled by 8260.3G. Check the official source before relying on it.
Order 8260.3F
Distribution: Electronic Distribution Initiated By: AFS-400
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.
Wesley L. Mooty Acting Deputy Executive Director, Flight Standards Service
Effective Date:
09/07/2023
National Policy
SUBJ: United States Standard for Terminal Instrument Procedures (TERPS)
ORDER
8260.3F
Order 8260.3F › Table of Contents
i
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-1 1-1-7. Word Meanings … 1-2 1-1-8. Formulas … 1-2 1-1-9. Geospatial Standards … 1-2
Section 1-2. Eligibility, Approval, and Retention … 1-3
1-2-1. Eligibility … 1-3 1-2-2. Requests for Procedures … 1-3 1-2-3. Approval … 1-3 1-2-4. Cancellation of Procedures … 1-4
Section 1-3. Responsibility and Jurisdiction … 1-5
1-3-1. Responsibility … 1-5 1-3-2. Jurisdiction … 1-5
Section 1-4. IFP Establishment … 1-6
1-4-1. Formulation … 1-6 1-4-2. Nonstandard IFPs … 1-6 1-4-3. Amendments … 1-6
Section 1-5. Coordination … 1-7
1-5-1. Coordination … 1-7 1-5-2. Coordination Conflicts … 1-7
Section 1-6. Identification of IFPs … 1-8
1-6-1. General … 1-8 1-6-2. Straight-in Approach Procedures … 1-8 1-6-3. Circling Approach Procedures … 1-10 1-6-4. Combined Charting of Approach Procedures … 1-10 1-6-5. Non-part 97 Approach Procedure Naming … 1-10 1-6-6. DP Identification … 1-11 1-6-7. En Route Procedure Identification … 1-11 1-6-8. Standard Terminal Arrival Identification … 1-11
Section 1-7. IFP Publication … 1-12
1-7-1. Submission … 1-12 1-7-2. Issuance … 1-12 1-7-3. Effective Date … 1-12
ii
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 … 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 … 2-5 2-1-7. Approach Categories … 2-5 2-1-8. Procedure Construction … 2-6 2-1-9. Continuous Descent Approach … 2-6 2-1-10. Aircraft Speed … 2-6 Section 2-2. Standard Terminal Arrival Procedures … 2-7
2-2-1. Standard Terminal Arrival … 2-7 2-2-2. Origination and Termination … 2-7 2-2-3. Routes and Transitions … 2-7 2-2-4. Alignment … 2-8 2-2-5. Area … 2-8 2-2-6. Obstacle Clearance … 2-8 2-2-7. Altitudes … 2-8 2-2-8. Descent Gradient … 2-10 2-2-9. Speed Restrictions … 2-12 2-2-10. Deceleration … 2-13 Section 2-3. Feeder Routes/Emergency Areas … 2-15
2-3-1. Feeder Routes … 2-15 2-3-2. Minimum Safe Altitude … 2-15 2-3-3. Emergency Safe Altitude … 2-16 Section 2-4. Initial Approach … 2-17
2-4-1. Initial Approach Segment … 2-17 2-4-2. Altitude Selection … 2-17 2-4-3. Initial Approach Segments Based on Straight Courses and Arcs with PCG … 2-17 2-4-4. Initial Approach Segment Based on DR … 2-20 2-4-5. Initial Approach Segment Based on a PT … 2-23 2-4-6. Initial Approach Based on High Altitude Teardrop Turn … 2-26 2-4-7. Initial Approach Course Reversal Using Noncollocated Facilities and a Turn of 120 Degrees or Greater to Intercept the Inbound Course … 2-30 Section 2-5. Intermediate Approach … 2-35
2-5-1. Intermediate Approach Segment … 2-35 2-5-2. Altitude Selection … 2-35 2-5-3. Intermediate Approach Segment Based on Straight Courses … 2-36 2-5-4. Intermediate Approach Segment Based on an Arc … 2-37 2-5-5. Intermediate Approach Segment Within a PT … 2-38
iii
Section 2-6. Final Approach … 2-47
2-6-1. Final Approach Segment … 2-47 2-6-2. Glidepath Angle and Vertical Descent Angle … 2-47 2-6-3. Glidepath Angle … 2-47 2-6-4. Vertical Descent Angle … 2-47 2-6-5. Visual Descent Point … 2-51 2-6-6. Vertical Guidance Surface … 2-53 Section 2-7. Circling Approach and Sidestep Maneuvers … 2-57
2-7-1. Circling Approach Area … 2-57 2-7-2. Restricted Circling Area … 2-58 2-7-3. Sidestep Maneuvers … 2-62 Section 2-8. Missed Approach … 2-64
2-8-1. Missed Approach Segment … 2-64 2-8-2. Missed Approach Alignment … 2-64 2-8-3. Missed Approach Point … 2-64 2-8-4. Straight Missed Approach Area … 2-64 2-8-5. Straight Missed Approach Obstacle Clearance … 2-65 2-8-6. Turning Missed Approach Area … 2-67 2-8-7. Turning Missed Approach Obstacle Clearance … 2-74 2-8-8. Combination Straight and Turning Missed Approach Area … 2-77 2-8-9. Climb-in-Hold at the MAP Missed Approach Area … 2-79 2-8-10. End of Missed Approach … 2-81 Section 2-9. Terminal Area Fixes … 2-82
2-9-1. General … 2-82 2-9-2. Fixes Formed By Intersection … 2-82 2-9-3. Course/Distance Fixes … 2-82 2-9-4. Fixes Formed By Radar … 2-83 2-9-5. Fix Displacement Area … 2-83 2-9-6. Intersection Fix Displacement Factors … 2-83 2-9-7. Other Fix Displacement Factors … 2-85 2-9-8. Satisfactory Fixes … 2-86 2-9-9. Using Fixes for Descent … 2-88 2-9-10. Obstacles Close to a PFAF or a Final Approach Segment Stepdown Fix … 2-91 Chapter 3. Landing and Takeoff Minimums … 3-1
Section 3-1. Landing Minimums 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 for Each Authorized Approach Category … 3-6 3-2-2. Adjustments to Minimum Altitudes/Heights … 3-8
iv
Section 3-3. Visibility Minimums … 3-15
3-3-1. Visibility Minimums Authorization … 3-15 3-3-2. Establishing Straight-in Visibility Minimums … 3-15 3-3-3. Establishing Circling Visibility Minimums … 3-24 3-3-4. Establishing Sidestep Visibility Minimums … 3-26 3-3-5. Fly Visual to Airport … 3-26 Section 3-4. Alternate Airport Minimums … 3-27
3-4-1. Establishing Alternate Minimums … 3-27 Section 3-5. Takeoff Minimums … 3-29
3-5-1. Civil Standard Takeoff Minimums … 3-29 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 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
v
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 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
vi
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 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 CG … 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 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
vii
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-7 Section 11-3. Minimum Vectoring Altitude Charts … 11-8
11-3-1. Sectors … 11-8 11-3-2. Minimum Vectoring Altitude Chart … 11-14 11-3-3. Obstacle Clearance … 11-16 11-3-4. Adverse Assumption Obstacle 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-2
12-2-1. Application … 12-2 12-2-2. PinS Approach … 12-2 12-2-3. Approach Categories … 12-3 12-2-4. Procedure Construction … 12-3 12-2-5. Descent Gradient/Vertical Descent Angle … 12-6 12-2-6. Initial Approach Segments Based on Straight Courses and Arcs with Positive Course Guidance … 12-6 12-2-7. Initial Approach Based on Procedure Turn … 12-6 12-2-8. Intermediate Approach Segment Based On Straight Courses … 12-7 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-8 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
viii
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-13
12-4-1. General … 12-13 12-4-2. Initial and Intermediate Segments … 12-13 12-4-3. Final Approach Segment … 12-13 Section 12-5. TACAN, VOR/DME, and VOR with PFAF … 12-14
12-5-1. Final Approach Segment … 12-14 12-5-2. Missed Approach Point … 12-14 12-5-3. Arc Final Approach Segment … 12-14 Section 12-6. On-Airport/Heliport NDB, No PFAF … 12-15
12-6-1. General … 12-15 12-6-2. Final Approach Segment … 12-15 Section 12-7. NDB Procedures with PFAF … 12-16
12-7-1. General … 12-16 12-7-2. Final Approach Segment … 12-16 12-7-3. Missed Approach Point … 12-16 Section 12-8. Localizer and LDA Procedures … 12-17
12-8-1. Localizer and LDA … 12-17 Section 12-9. ILS Procedures … 12-18
12-9-1. General … 12-18 12-9-2. Intermediate Approach Segment … 12-18 12-9-3. Final Approach Segment … 12-18 12-9-4. Missed Approach Area … 12-18 Section 12-10. Precision Approach Radar … 12-19
12-10-1. Intermediate Approach Segment … 12-19 12-10-2. Final Approach Segment … 12-19 12-10-3. Final Approach Alignment … 12-19 12-10-4. Final Approach Area … 12-19 12-10-5. Final Approach Obstacle Clearance Surface … 12-19 12-10-6. Transitional Surfaces … 12-21 12-10-7. Obstacle Clearance … 12-21 12-10-8. Glide Slope … 12-22 12-10-9. Relocation of the Glide Slope … 12-22 12-10-10. Adjustment of DH … 12-22 12-10-11. Missed Approach Obstacle Clearance … 12-22
ix
12-10-12. Straight Missed Approach Area … 12-23 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 … 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. Helicopter Departures … 13-1 13-1-3. Departure Criteria Application … 13-1 13-1-4. Departure OCS Application … 13-1 13-1-5. Climg Gradients … 13-3 13-1-6. Ceiling and Visibility … 13-5 13-1-7. Initial Climb Area … 13-5 Section 13-2. Diverse Departure Assessment … 13-7
13-2-1. General … 13-7 13-2-2. Departure Sectors … 13-10 13-2-3. Sector Limitations … 13-12 Section 13-3. Departure Routes … 13-14
13-3-1. General Information … 13-14 13-3-2. Straight DP Segments … 13-14 13-3-3. Turning DP Segments … 13-21 13-3-4. Multiple PCG Turn Segments … 13-31 13-3-5. Routed Departure Obstacle Evaluation … 13-39 13-3-6. Connecting Terminal Departure to the En Route Structure … 13-45 Section 13-4. Visual Climb Over Airport … 13-46
13-4-1. General … 13-46 13-4-2. Basic Area … 13-46 13-4-3. VCOA Assessment … 13-47 13-4-4. Ceiling and Visibility … 13-49 13-4-5. Published Annotations … 13-49 Section 13-5. Diverse Vector AreaAssessment … 13-51
13-5-1. General … 13-51 13-5-2. Initial Departure Assessment … 13-51 13-5-3. Select a DVA Method … 13-51 13-5-4. Climb Gradients … 13-59
x
Section 13-6. Obstacle Clearance Requirements for SID Containing ATC Altitude Restrictions … 13-60
13-6-1. Maximum Altitude Restrictions … 13-60 13-6-2. Minimum Altitudes … 13-63 Section 13-7. Helicopter Point-in-Space Departures … 13-64
13-7-1. General … 13-64 13-7-2. Procedure Design Standards … 13-64 13-7-3. Obstacle Evaluation Area … 13-65 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 … 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 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 … 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
xi
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. 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 Section 15-3. 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
xii
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 … 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 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-8 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
xiii
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 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
Appendix B. Definitions … B-1
Appendix C. Precipitous Terrain Algorithms … C-1
Appendix D. Mathematics Convention … D-1
Appendix E. Simultaneous Approach Operations … E-1
xiv
Appendix F. Geospatial Standard … F-1
Appendix G. Conditions and Assumptions for IVH Approach Procedures … G-1
Appendix H. Fix Location Adjustment for High Temperature Compensation … H-1
Section 1-1. Scope › 1-1-6. Types of Procedures.
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.3E, United States Standard for Terminal Instrument Procedures (TERPS), dated September 17, 2020.
1-1-5. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. Updated administrative changes throughout the document.
b. Updated page and paragraph numbers in the Table of Contents.
c. Added a process and calculations to compensate for high-temperature effects in a new appendix.
d. Removed criteria for the evaluation of the initial climb area (ICA) when clearways are established.
e. Updated criteria in chapter 13, Departure Procedure (DP) Construction:
(1) Added criteria for the evaluation of changeover points (COP).
(2) Updated and added criteria for determination of turn radii.
(3) Added criteria for inside and outside turn protection.
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.
Section 1-1. Scope › 1-1-9. Geospatial Standards.
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. Non-precision 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.
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.
Section 1-2. Eligibility, Approval, and Retention › 1-2-3. Approval.
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-in-space (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 instrument flight rules (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/53401, 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.
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.
Section 1-3. Responsibility and Jurisdiction › 1-3-2. Jurisdiction.
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 Air Missions (NOTAM). See Order 8260.19 and Order JO 7930.2, Notices to Air Missions (NOTAM), 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.
Section 1-6. Identification of IFPs › 1-6-2. Straight-in Approach Procedures.
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
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. Point-in-space (PinS) procedures apply the type of navigation followed by the published final approach course.
Examples: LOC 353, RNAV (GPS) 025, COPTER RNAV (GPS) 247, VOR 221, COPTER VOR 243
Section 1-6. Identification of IFPs › 1-6-5. Non-part 97 Approach Procedure Naming.
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 City Airport Procedure name GA Atlanta KFTY VOR-A GA Atlanta KCCO NDB-B GA Atlanta KPDK 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.
Section 1-6. Identification of IFPs › 1-6-8. Standard Terminal Arrival Identification.
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. DP 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.”
(2) High altitude (FL 180 through FL 450) RNAV routes are identified by the letter “Q.”
(3) Helicopter RNAV routes are identified by a letter supplemented with a suffix: “TK.”
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.
Section 2-1. Common Information › 2-1-3. Level OCS.
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).
Section 2-1. Common Information › 2-1-4. Sloping OCS.
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.
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 DP 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 (CG). The CG 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 CG that will provide adequate ROC in the climb segment is 200 ft/nautical mile (NM) (400 ft/NM for helicopters), also referred to as the “standard CG.” A higher gradient may be specified as defined in this order.
(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 CG expressed in ft/NM.
(a) The minimum ROC supplied by the standard 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) Helicopter minimum ROC supplied by the standard CG of 400 ft/NM is 96 ft (0.24 × 400 =96). Since 96 of the 400 feet gained in 1 NM is ROC, the OCS height at that point
1 1852
152 /0.3048 ≈39.97, rounded to 40.
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).
Figure 2-1-4. Climb Segment
(2) Where an obstruction penetrates the sloping OCS, a CG greater than standard CG is required to provide adequate ROC. Departure CGs greater than standard will have ROC greater than 48 ft/NM (96 ft/NM for helicopters) since ROC is equal to 24% of the CG. The ROC expressed in ft/NM can be calculated using formula 2-1-1. However, instead of calculating the ROC value, the required CG is normally calculated directly using formula 2-1-2. Refer to chapter 10 for ILS missed approach CGs.
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 CG
𝐶𝐶𝐶𝐶= ℎ (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
2 1852
304 /0.3048 ≈19.99, rounded to 20.
Section 2-1. Common Information › 2-1-7. Approach Categories.
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.
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 CG 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
Section 2-1. Common Information › 2-1-10. Aircraft Speed.
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 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).
Section 2-2. Standard Terminal Arrival Procedures › 2-2-3. Routes and Transitions.
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.
Section 2-2. Standard Terminal Arrival Procedures › 2-2-7. Altitudes.
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.
(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.
Section 2-2. Standard Terminal Arrival Procedures › 2-2-8. Descent Gradient (DG).
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
(𝐴𝐴𝐴𝐴𝐴𝐴1 −𝐴𝐴𝐴𝐴𝐴𝐴2) + 318
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.
(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
Section 2-2. Standard Terminal Arrival Procedures › 2-2-9. Speed Restrictions.
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
Section 2-2. Standard Terminal Arrival Procedures › 2-2-10. Deceleration.
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. A deceleration evaluation is required prior to any fix with a speed restriction or when required for 14 CFR part 91.117 (a) or (c). STARs not meeting the requirements of this paragraph may be authorized with Flight Standards approval unless required for 14 CFR part 91.117 (a) or (c) (see paragraph 1-4-2).
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 [14 CFR part 91.117 (a)]. 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) When an altitude restriction exists at a fix that could place an aircraft below Class B airspace [14 CFR part 91.117 (c)] a deceleration evaluation is required to ensure sufficient
distance for the aircraft to comply with the 200 KIAS airspeed restriction even though it is not charted.
(5) 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).
Section 2-3. Feeder Routes/Emergency Areas › 2-3-2. Minimum Safe Altitude (MSA).
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.
Section 2-3. Feeder Routes/Emergency Areas › 2-3-3. Emergency Safe Altitude (ESA).
(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 DPs 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 DPs, 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.
Section 2-4. Initial Approach › 2-4-3. Initial Approach Segments Based on Straight Courses and Arcs with PCG.
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).
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).
Figure 2-4-2. Straight/Arc Initial Segment Minimum ROC
Formula 2-4-1. Straight/Arc Initial Segment Minimum Secondary ROC
𝑅𝑅𝑅𝑅𝑅𝑅𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠= 500 × ൬1 −
𝑑𝑑𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝
𝑊𝑊𝑠𝑠
൰
Where: dprimary = Perpendicular distance (feet) from primary area edge WS = Total width of the secondary area (feet)
d. Descent gradient. The optimum descent gradient in the initial approach is 250 ft/NM. Where a higher descent gradient is necessary, the maximum gradient is 500 ft/NM. The optimum descent gradient for high altitude procedures is 800 ft/NM. Where a higher descent gradient is necessary, the maximum gradient is 1000 ft/NM. When an arc of less than 15 NM is used in high altitude procedures, the descent gradient along the arc must not exceed the values in table 2-4-1 (values may be interpolated).
Table 2-4-1. Descent Gradient on High Altitude Procedure Arcs 15 NM and Less
ARC RADIUS (NM) MAX FEET/NM
≥15 1000 14 720 13 640 12 560 11 480 10 400 9 320 8 240 7 160
Section 2-4. Initial Approach › 2-4-4. Initial Approach Segment Based on DR.
2-4-4. Initial Approach Segment Based on DR.
a. Alignment. Each DR course must intercept the extended intermediate course. For low altitude procedures, the intercept point must be at least 1 NM from the IF for each 2 NM of DR flown. For high altitude procedures, the intercept point may be 1 NM for each 3 NM of DR flown. The intercept angle must:
(1) Not exceed 90 degrees.
(2) Not be less than 45 degrees except when DME is required for the approach and is used to identify the IF, or the DR distance is 3 NM or less.
b. Area. The maximum length of the DR portion of the initial segment is 10 NM (except paragraph 2-4-3.b applies for high altitude procedures where DME is available throughout the DR segment). Where the DR course begins, the width is 6 NM on each side of the course, expanding by 15 degrees outward until joining the points shown in figure 2-4-3 through figure 2- 4-7.
c. Obstacle clearance. The minimum ROC in the DR initial approach segment is 1000 feet. There is no secondary area. Adjustments for precipitous terrain must be applied as specified in paragraph 3-2-2 (see also paragraph 2-4-2).
d. Descent gradient. The optimum descent gradient in the initial approach is 250 ft/NM. Where a higher descent gradient is necessary, the maximum permissible gradient is 500 ft/NM. The optimum descent gradient for high altitude procedures is 800 ft/NM. Where a higher descent gradient is necessary, the maximum permissible gradient is 1000 ft/NM.
Figure 2-4-3. Example DR Segment
Figure 2-4-4. Example DR Segment
Figure 2-4-5. Example DR Segment
Figure 2-4-6. Example DR Segment
Figure 2-4-7. Example DR Segment
Section 2-4. Initial Approach › 2-4-5. Initial Approach Segment Based on a PT.
2-4-5. Initial Approach Segment Based on a PT. Establish a PT when it is necessary to reverse direction to establish the aircraft on an intermediate or FAC, except as specified in paragraph 2-4-5.e. A PT begins by overheading a facility, or a fix which meets either the criteria for a holding fix (see paragraph 2-9-8.b) or for a PFAF (see paragraph 2-9-8.c). A PT must not be established over a 75 MHz marker beacon. The procedure must specify the PT fix, the outbound and inbound courses, the distance within which the PT must be completed, and the direction of the PT. When a teardrop turn is used, the angle of divergence between the outbound courses and the reciprocal of the inbound course must be a minimum of 15 degrees or a maximum of 30 degrees (see paragraph 2-4-6.a for high altitude teardrop turn). When the beginning of the intermediate or final approach segment associated with the PT is not marked by a fix, the segment is deemed to begin on the inbound PT course at the maximum distance specified in the procedure. Where neither segment is marked by a fix, the final segment begins at the maximum distance specified in the procedure.
a. Alignment. When the inbound course of the PT becomes the intermediate course, it must meet the intermediate course alignment criteria (see paragraph 2-5-3.a). When the inbound course becomes the FAC, it must meet the FAC alignment criteria (see paragraph 2-6-1). The wider side of the PT area must be oriented in the same direction as that prescribed for the PT.
b. Area. The PT areas are depicted in figure 2-4-8. The minimum PT distance is 10 NM when CAT B, C, or D minimums are authorized. Decrease this distance to 5 NM where only CAT A aircraft or helicopters are to be operating, and increase to 15 NM to accommodate operational requirements, or as specified in paragraph 2-4-5.d. No extension of the PT is permitted without a PFAF. When a PT is authorized for use by approach CAT E aircraft, use a 15-NM PT distance. The PT segment is made up of the entry and maneuvering zones. The entry zone terminates at the inner boundary which extends perpendicular to the PT inbound course at the PT fix. The remainder of the PT segment is the maneuvering zone. The entry and maneuvering zones are made up of primary and secondary areas. The PT primary area dimensions are based on the highest authorized PT entry altitude or the highest feeder route altitude, whichever is greater. To allow additional maneuvering area as the true airspeed increases at higher altitudes, the dimensions of the PT primary area increase; see table 2-4-2 through table 2-4-4. The PT secondary area is 2 NM on the outside of the primary area.
Figure 2-4-8. PT Area (See table 2-4-2 to Determine Radius Values)
Table 2-4-2. PT Variables (NM) by Altitude ≤ 6000
PT LENGTH OFFSET R1 R2 R3 R4 5 2 4 6 5 7 >5-10 2 5 7 6 8 >10-15 a - 4 5 7 a a + 2 Where: 𝑎𝑎= 0.1 × (𝑏𝑏−10) + 6 b = Specified PT length
Table 2-4-3. PT Variables (NM) by Altitude > 6000 to ≤ 10000
PT Length Offset R1 R2 R3 R4 5 2 4 6 5 7 >5-10 2 6 8 7 9 >10-15 a - 5 6 8 a a + 2
Where: 𝑎𝑎= 0.1 × (𝑏𝑏−10) + 7 b = Specified PT length
Table 2-4-4. PT Variables (NM) by Altitude > 10000
PT Length Offset R1 R2 R3 R4 5 2 4 6 5 7 >5-10 2 7 9 8 10 >10-15 a - 6 7 9 a a + 2
Where: 𝑎𝑎= 0.1 × (𝑏𝑏−10) + 8 b = Specified PT length
c. Obstacle clearance. Apply paragraph 2-4-3.c. In addition, the primary and secondary areas determine obstacle clearance in both the entry and maneuvering zones. The use of entry and maneuvering zones provides further relief from obstacles. The entry zone is established to control the obstacle clearance prior to proceeding outbound from the PT fix/facility. The maneuvering zone is established to control obstacle clearance after proceeding outbound from the PT fix/facility (see figure 2-4-9).
Figure 2-4-9. PT Initial Approach Area
d. Descent gradient. The optimum descent gradient in the initial approach is 250 ft/NM. Where a higher descent gradient is necessary, the maximum permissible gradient is 500 ft/NM. Where a PT is established over a PFAF, the PT completion altitude should be as close as possible to the PFAF altitude. The difference between the PT completion altitude and the altitude over the PFAF must not be greater than those shown in table 2-4-5. If greater differences are required for
Section 2-4. Initial Approach › 2-4-6. Initial Approach Based on High Altitude Teardrop Turn.
a 5-NM or 10-NM PT, the PT distance limits and maneuvering zone must be increased at the rate of 1 NM for each 200 feet of required altitude.
Table 2-4-5. PT Completion Altitude Difference
Type of PT Altitude Difference
15 NM PT from PFAF ≤ 3000 feet over PFAF altitude
10 NM PT from PFAF ≤ 2000 feet over PFAF altitude
5 NM PT from PFAF ≤ 1000 feet over PFAF altitude
15 NM PT, no PFAF Not Authorized
10 NM PT, no PFAF ≤ 1500 feet over MDA
5 NM PT, no PFAF ≤ 1000 feet over MDA
e. Elimination of PT. A PT is not required when an approach can be made direct from a specified IF to the PFAF provided the alignment of the initial segment complies with paragraph 2-4-3.a. A PT need not be established when an approach can be made from a properly aligned holding pattern (see paragraph 16-9-2). In this case, the holding pattern in lieu of a PT must be established over a final or intermediate approach fix and the following conditions apply:
(1) If the holding pattern is established over the PFAF (not applicable to RNAV procedures), an intermediate segment is not constructed. Ideally, establish the minimum holding altitude at the PFAF altitude. In any case, the published holding altitude must not be more than 300 feet above the PFAF altitude.
(2) If the holding pattern is established over the IF, the minimum holding altitude (MHA) must permit descent to the PFAF altitude within the descent gradient tolerances prescribed for the intermediate segment (see paragraph 2-5-3.d).
2-4-6. Initial Approach Based on High Altitude Teardrop Turn. A high altitude teardrop turn consists of departure from an IAF on an outbound course, followed by a turn toward and intercepting the inbound course at or prior to the IF or point used in lieu of an IF when no IF exists (see paragraph 2-4-6.c). Its purpose is to permit an aircraft to reverse direction and lose considerable altitude within reasonably limited airspace. Where no IF is available to mark the beginning of the intermediate segment, it must be assumed to commence at a point 10 NM prior to the PFAF. When the facility is located on the airport, and no fix is available to mark the beginning of the final approach segment, the criteria in paragraph 4-3-4 apply.
a. Alignment. The outbound course must be between 18 and 26 degrees to the left or right of the reciprocal of the inbound course. The actual angular divergence between the courses will vary inversely with the distance from the facility at which the turn is made (see table 2-4-6).
b. Area.
(1) Size. The size of the turn area must be sufficient to accommodate both the turn and the altitude loss required by the procedure. The turn distance must not be less than 20 NM from the facility. The turn distance depends on the altitude to be lost in the procedure and the point at
which the descent is started (see table 2-4-6). The aircraft should lose half the total altitude or 5000 feet, whichever is greater, outbound prior to starting the turn. The turn area has a width of 6 NM on both sides of the flight track up to the IF (or point used in lieu of the IF), and must encompass all the areas within the turn (see figure 2-4-10).
(2) Turn distance table. Use table 2-4-6 to compute the desired course divergence and turn distances which apply when a specific altitude loss outbound is required. It is assumed that the descent begins at the plotted position of fix. When the procedure requires a delay before descent of more than 5 NM, add the distance in excess of 5 NM to the distance the turn commences. Then adjust the course divergence and teardrop turn distance to correspond to the adjusted turn distance. Extrapolations may be made from the table.
(3) Primary and secondary areas. All of the turn area, except the outer 2 NM of the 6-NM obstacle clearance area on the outer side of the turn teardrop track is primary area (see figure 2-4-10). The outer 2 NM is secondary area. The outer 2 NM on both sides of the inbound course should be treated as secondary area (see figure 2-4-12).
Table 2-4-6. High Altitude Turn Distance/Divergence
ALT to be Lost Prior to
Commencing Turn
(feet)
Distance Turn Commences (NM)
Course Divergence
(Degrees)
Specified Turn Distance
(NM)
12000 24 18 28 11000 23 19 27 10000 22 20 26 9000 21 21 25 8000 20 22 24 7000 19 23 23 6000 18 24 22 5000 17 25 21 5000 16 26 20
Figure 2-4-10. Typical High Altitude Teardrop Turn Initial Approach Area
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-11). The minimum ROC at any given point in the secondary area is determined by formula 2-4-2. Adjustments for precipitous terrain must be applied as specified in paragraph 3-2-2. Where no IF is available, a 10-NM intermediate segment is assumed and intermediate segment ROC is applied (see paragraph 2-5-3.c). The controlling obstacle, as well as the minimum altitude selected for the intermediate segment, may depend on the availability of an IF (see figure 2-4-12).
Figure 2-4-11. High Altitude Teardrop Initial Segment Secondary ROC
Formula 2-4-2. PT Initial Segment Secondary ROC
𝑅𝑅𝑅𝑅𝑅𝑅𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠= 500 × ൬1 −
𝑑𝑑𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝
𝑊𝑊𝑠𝑠
൰
Where: dprimary= Perpendicular distance (feet) from primary area edge WS = Total width of the secondary area (feet)
Figure 2-4-12. High Altitude Teardrop Turn Initial Approach Obstacle Clearance
d. Descent gradient. The optimum descent gradient is 800 ft/NM. The maximum gradient is 1000 ft/NM.
Section 2-4. Initial Approach › 2-4-7.
e. Turn altitude. When an IF is not provided, the turn completion altitude must not be more than 4000 feet above the PFAF altitude.
2-4-7. Initial Approach Course Reversal Using Noncollocated Facilities and a Turn of 120 Degrees or Greater to Intercept the Inbound Course. See figure 2-4-13, figure 2-4-14, and figure 2-4-15.
a. Common criteria.
(1) A turn point fix must be established as shown in the figures. The fix error must meet section 2-9 criteria and must not exceed ± 2 NM.
(2) A flight path radius (R) of 2.8 NM must be used for procedures where the altitude at the turn point fix is at or below 10000 feet, or 4 NM for procedures where the altitude at the turn point fix is above 10000 feet MSL.
(3) Construct the primary boundary (and secondary if applicable) of the turn by swinging an arc(s) from the intersection of the bisector line and the turn point’s fix error line.
(4) Descent gradient. Apply criteria in paragraph 2-4-3.d.
(5) Obstacle clearance. Apply criteria in paragraph 2-4-6.c.
(6) When the course reversal turn intercepts the extended intermediate course, or when the course reversal turn intercepts a straight segment prior to intercepting the extended intermediate course, the minimum distance between the rollout point and the PFAF is 10 NM.
(7) ROC reduction. No reduction of secondary ROC is authorized in the course reversal area unless the turn point fix is DME.
b. Figure 2-4-13 and figure 2-4-14. The rollout point must be at or prior to the IF/point.
(1) Select the desired rollout point on the inbound course.
(2) Place the appropriate flight path arc tangent to the rollout point.
(3) From the outbound facility, place the outbound course tangent to the flight path arc. The point of tangency must be the turn point fix.
Figure 2-4-13. Example Initial Approach Course Reversal Using Noncollocated Facilities and Turn Greater than 120 Degrees
Figure 2-4-14. Example Initial Approach Course Reversal Using Noncollocated Facilities and Turn Greater than 120 Degrees
c. Figure 2-4-15.
(1) The point of intersection must be at or prior to the IF/point (paragraph 2-5-3 applies). The angle must be 90 degrees or less.
(2) The distance between the roll-out point and the point of intersection must be no less than the distance shown in table 2-4-7.
Figure 2-4-15. Example Initial Approach Course Reversal Using Noncollocated Facilities and Turn Greater than 120 Degrees
Table 2-4-7. Minimum Distance from Roll Out Point to Point of Intersection
Angle "a" (Degrees)
NM
0 - 15 1 >15 - 30 2 >30 - 45 3 >45 - 60 4 >60 - 75 5 >75 - 90 6 Note: For high altitude procedures, use paragraph 2-4-6 and table 2-4-7 up to the point of intersection of the two inbound courses.
(3) Select the desired point of intersection. From the outbound facility draw a line through the point of intersection.
(4) At the outbound facility, measure the required number of degrees course divergence (may be either side of the line through the point of intersection) and draw the outbound course out the required distance. Connect the outbound course and the line through the point of intersection with the appropriate arc.
(5) Determine the desired rollout point on the line through the point of intersection.
(a) Place the appropriate flight path arc tangent to the rollout point.
(b) From the outbound facility draw the outbound course tangent to the flight path arc. The point of tangency is the turn point fix.
Section 2-5. Intermediate Approach › 2-5-2. Altitude Selection.
Section 2-5. Intermediate Approach
2-5-1. Intermediate Approach Segment. This is the segment which blends the initial approach segment into the final approach segment. It is the segment in which aircraft configuration, speed, and positioning adjustments are made for entry into the final approach segment. The intermediate segment begins at the IF (or point used in lieu of) and ends at the PFAF. There are two types of intermediate segments; the “radial” or “course” intermediate segment, and the “arc” intermediate segment. In either case, PCG must be provided. For typical approach segments, see figure 2-5-1.
2-5-2. Altitude Selection. Minimum altitudes in the intermediate 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 height plus ROC and adjustments equals 701, round up to 800 feet. The altitude selected for arrival over the PFAF must be low enough to permit descent from the PFAF to the airport for a straight-in landing whenever possible. In addition, the altitude selected for the PFAF must not be lower than the highest straight-in or circling MDA (CMDA).
Figure 2-5-1. Typical Approach Segments
Section 2-5. Intermediate Approach › 2-5-3. Intermediate Approach Segment Based on Straight Courses.
2-5-3. Intermediate Approach Segment Based on Straight Courses.
a. Alignment. The course to be flown in the intermediate segment must be the same as the FAC, except when the PFAF is the navigation facility and it is not practical for the courses to be identical. In such cases, the intermediate course must not differ from the FAC by more than 30 degrees.
b. Area.
(1) Length. The length of the intermediate segment is measured along the course to be flown. Where the initial segment joins the intermediate segment at angles up to and including 96 degrees, the minimum length is 5 NM for CAT A/B and 6 NM for CAT C/D/E (see chapters 8, 10, 11, and 12 for exceptions). Table 2-5-1 lists the minimum segment length where the initial approach course joins the intermediate course at angles greater than 96 degrees. The maximum segment length is 15 NM. The optimum length is 10 NM. A distance greater than 10 NM should not be used unless an operational requirement justifies a greater distance.
(2) Width. The width of the intermediate segment is the same as the width of the segment it joins. When the intermediate segment is aligned with initial or final approach segments, the width of the intermediate segment is determined by joining the outer edges of the initial segment with the outer edges of the final segment. When the intermediate segment is not aligned with the initial or final approach segments, the resulting gap on the outside of the turn is a part of the preceding segment and is closed by the appropriate arc (see figure 2-5-1). For obstacle clearance purposes, the intermediate segment is divided into a primary and a secondary area.
Table 2-5-1. Minimum Intermediate Course Length
Angle (Degrees)
Minimum Length (NM) based on CAT
A/B C/D/E
0 - 96 5 6 > 96 - 102 6 7 >102 - 108 6 8 >108 - 114 6 9 >114 - 120 7 10
c. Obstacle clearance. The minimum ROC in the primary area is 500 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-5-2). The minimum ROC at any given point in the secondary area is determined by formula 2-5-1. Apply adjustments as specified in paragraph 3-2-2.
Section 2-5. Intermediate Approach › 2-5-4. Intermediate Approach Segment Based on an Arc.
Figure 2-5-2. Intermediate Segment Secondary ROC
Formula 2-5-1. Intermediate Segment Secondary ROC
𝑅𝑅𝑅𝑅𝑅𝑅𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠𝑠= 500 × ቀ1 −
𝑑𝑑𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝𝑝
𝑊𝑊𝑆𝑆ቁ
Where: dprimary = Perpendicular distance (feet) from primary area edge
WS = Total width of the secondary area (feet)
d. Descent gradients. Because the intermediate segment is used to prepare the aircraft speed and configuration for entry into the final approach segment, the gradient should be as flat as possible. A descent gradient no greater than 150 ft/NM is optimum. The maximum gradient between the IF and the PFAF is 318 ft/NM. When one or more stepdown fixes are established, ensure the gradient from each stepdown fix to the PFAF does not exceed 318 ft/NM. Higher gradients resulting from arithmetic rounding are permissible.
2-5-4. Intermediate Approach Segment Based on an Arc. DME Arcs with a radius of less than 7 NM or more than 30 NM from the navigation facility must not be used. Arc courses must be predicated on DME collocated with a facility providing omnidirectional course information.
Continue reading ↓ 120 of 892 passages shown