Radar Vectors
FAA Order Cancelled Issued Jun 29, 2020 AFS-400 431 pages Copy saved Nov 18, 2026

Order 8260.19I Flight Procedures and Airspace

This order provides guidance to all FAA personnel for theadministration and accomplishment of the FAA Flight Procedures and Airspace Program. Additionally, this order provides guidance for the military and other government agencies to usewhen interacting with the FAA regarding instrument flight procedures. This order containsguidance that is pertinent to 14 CFR parts 71, 91, 95, 97, 121, and 135.

This document is cancelled. Cancelled by 8260.19J. Check the official source before relying on it.

Official source ↗ Open PDF

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

SUBJ: Flight Procedures and Airspace

Distribution: Electronic Distribution Initiated By: AFS-400

Effective Date: National Policy

SUBJ: Flight Procedures and Airspace

This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program.

The development of effective and efficient flight procedures is closely related to facility establishment and airport programs. These procedures require active participation by Flight Standards, the applicable Air Traffic Organization (ATO) Service Area, and office of Airports personnel in the planning, programming, and budgeting of navigation facilities and airport development plans. Instrument procedures often determine the alignment and location of navigation facilities as well as the location, marking, and lighting of airport landing and maneuvering areas. Title 14 Code of Federal Regulations (14 CFR) part 95 establishes minimum en route altitude (MEA), minimum reception altitude (MRA), maximum authorized altitude (MAA), minimum obstruction clearance altitude (MOCA), minimum crossing altitude (MCA), and changeover point (COP) are established by the Federal Aviation Administration for instrument flight along Federal airways.

General information and responsibilities are contained in Chapter 1 and guidelines and procedures that are common to all instrument flight procedures are in Chapter 2. Chapter 3 and 4 contain specific guidelines and procedures for en route and terminal instrument flight procedures, respectively. Chapter 5 contains information concerning airspace - obstruction evaluation (OE); designation of controlled airspace; airport airspace analysis; restricted areas; and establishment, relocation, or discontinuance of radio navigation aids. Chapter 6 provides information concerning Military procedures. Chapter 7 contains planning standards; airway, terminal, and airport planning; safety analysis; private aid, and facilities and equipment (F&E) support. Chapter 8 provides information on instrument approach procedures data transmittal systems as well as the use and preparation of forms.

Rick Domingo Executive Director, Flight Standards Service

06/29/2020

This document was signed by Robert C. Carty.

Table of Contents

Chapter 1. General Information … 1-1 Section 1-1. General … 1-1

1-1-1. Purpose of This Order … 1-1 1-1-2. Audience … 1-1 1-1-3. Where You Can Find This Order … 1-1 1-1-4. What This Order Cancels … 1-1 1-1-5. Explanation of Changes … 1-1 1-1-6. Effective Date … 1-5 Section 1-2. Responsibilities … 1-6

1-2-1. Flight Standards Service … 1-6 1-2-2. Flight Technologies and Procedures Division … 1-6 1-2-3. Air Traffic Organization, Flight Program Operations … 1-7 1-2-4. Air Traffic Organization, Mission Support Services (AJV-0) … 1-9 1-2-5. Individual … 1-12

Chapter 2. General Procedures … 2-1

Section 2-1. General … 2-1

2-1-1. Requests for Public-use IFPs … 2-1 2-1-2. Air Traffic Letters of Agreement (LOAs) … 2-1 2-1-3. Airport Lighting and Visual Aids … 2-1 Section 2-2. Aeronautical Charts … 2-3

2-2-1. Use of Maps and Charts … 2-3 2-2-2. Aeronautical Charts and Publications … 2-3 Section 2-3. Environmental Requirements … 2-5

2-3-1. Noise Abatement … 2-5 2-3-2. Environmental Impacts … 2-5 Section 2-4. Facility Utilization and Monitoring … 2-6

-2-4-1. Frequency Service Volumes … 2-6 2-4-2. ATC Usable Distance and Altitude Limitations … 2-6 2-4-3. Requests for Expanded Service Volumes … 2-6 2-4-4. Utilization of Localizers … 2-7 2-4-5. Monitoring of Navigation Facilities … 2-7 2-4-6. Utilization of Monitoring Categories … 2-7 2-4-7. Utilization of 75 MHz Markers … 2-8 Section 2-5. Implementing Epoch Year Magnetic Variation (MV) … 2-9

2-5-1. General … 2-9 2-5-2. Responsibilities … 2-9 2-5-3. Guidelines for Magnetic Variation Revisions … 2-14 Section 2-6. Notices to Airmen (NOTAMs) … 2-17

2-6-1. General … 2-17 2-6-2. United States NOTAM System … 2-17 Section 2-7. Quality/Standardization of Instrument Flight Procedures … 2-18

2-7-1. Aeronautical Information Services’ Action … 2-18 2-7-2. Flight Technologies and Procedures Division’s Action … 2-18

Section 2-8. Periodic Review of Instrument Flight Procedures … 2-19

2-8-1. General … 2-19 2-8-2. Frequency of Periodic Reviews … 2-19 2-8-3. Conducting Periodic Reviews … 2-20 2-8-4. Documentation of Periodic Reviews … 2-21 2-8-5. Reviewing Organization Responsibilities … 2-21 Section 2-9. Communications and Weather … 2-22

2-9-1. Communications Requirements … 2-22 2-9-2. Use of Universal Integrated Communications (UNICOM) … 2-22 2-9-3. Automatic Altimeter Setting and Weather Reporting Systems … 2-22 Section 2-10. Navigational Fixes … 2-24

2-10-1. General … 2-24 2-10-2. Reporting Points … 2-24 2-10-3. Unplanned Holding at Compulsory Reporting Points … 2-24 2-10-4. Requests for Navigational Fixes … 2-24 2-10-5. Naming Navigational Fixes … 2-25 2-10-6. Documenting Navigational Fixes … 2-27 2-10-7. Correlation of Navigational Fixes and Changeover Points … 2-27 2-10-8. Minimum Reception Altitudes … 2-28 2-10-9. Flight Inspection … 2-28 2-10-10. Maximum Authorized Altitudes … 2-29 Section 2-11. Obstacle Data … 2-30

2-11-1. General … 2-30 2-11-2. Obstacle Application and Data Sources … 2-30 2-11-3. Obstacle Data Accuracy Standards … 2-31 2-11-4. Accuracy Standards Application … 2-32 2-11-5. Controlling Obstacles … 2-33 2-11-6. Datums … 2-38 Section 2-12. Waiver of Standards/Approval Requests … 2-40

2-12-1. General … 2-40 2-12-2. Waiver Processing … 2-40 2-12-3. Waivers for Special Instrument Approach Procedures … 2-41 2-12-4. Safety Management System (SMS) Requirements … 2-41 2-12-5. Periodic Review of Waivers … 2-42 2-12-6. Cancellation … 2-42

Chapter 3. Route Procedures … 3-1

Section 3-1. General … 3-1

3-1-1. General … 3-1 3-1-2. Publication … 3-1 Section 3-2. Criteria Application and Development … 3-2

3-2-1. Criteria Application … 3-2 3-2-2. Development of Criteria … 3-2 Section 3-3. Establishment of En Route Airspace … 3-3

3-3-1. Relationship of COPs to Airspace Dimensions … 3-3 3-3-2. Relationship of MEAs to Controlled Airspace Floors … 3-3 Section 3-4. Substitute En Route Flight Procedures … 3-4

3-4-1. General … 3-4 3-4-2. Format … 3-4

3-4-3. Facilities Used … 3-4 3-4-4. Controlled Airspace … 3-4 3-4-5. Flight Inspection … 3-4 3-4-6. Planning and Coordination … 3-5 3-4-7. Processing … 3-8 3-4-8. Periodic Review … 3-8 3-4-9. Distribution … 3-8 Section 3-5. Off-Airway Routes … 3-10

3-5-1. Establishment … 3-10 3-5-2. Listing … 3-10 3-5-3. Off-airway Data … 3-10 3-5-4. Processing Data to Aeronautical Information Services … 3-11 Section 3-6. New or Revised National Airspace System Routes … 3-12

3-6-1. Definition - Route … 3-12 3-6-2. Coordination Procedures … 3-12 3-6-3. Publication of Procedural Data … 3-12 Section 3-7. Minimum Vectoring Altitude (MVA) and Minimum IFR Altitude (MIA) Charts ... 3-13

3-7-1. Chart Preparation … 3-13 3-7-2. Obstacle Clearance … 3-13 3-7-3. Controlled Airspace … 3-13 3-7-4. Chart Review and Approval … 3-13 3-7-5. Emergency Obstruction Video Map (EOVM) … 3-14

Chapter 4. Terminal Procedures … 4-1

Section 4-1. General … 4-1

4-1-1. General … 4-1 4-1-2. Categories of Instrument Approach Procedures … 4-1 4-1-3. Airspace Requirements … 4-1 4-1-4. Contractual Use of Private Facilities … 4-2 4-1-5. TERPS Application … 4-2 4-1-6. Sidestep Maneuvers … 4-3 4-1-7. Temporary Displaced Threshold Procedures … 4-4 Section 4-2. Standard Instrument Approach Procedures (SIAP) … 4-5

4-2-1. General … 4-5 4-2-2. Coordination of Terminal Instrument Procedures … 4-5 4-2-3. Radar Instrument Approach Procedures … 4-5 Section 4-3. Category II and III ILS … 4-6

4-3-1. General … 4-6 4-3-2. Action … 4-7 4-3-3. NOTAM Requirements … 4-8 Section 4-4. Departure Procedures (DP) … 4-9

4-4-1. General … 4-9 4-4-2. Diverse Vector Area (DVA) … 4-9 Section 4-5. Standard Terminal Arrival (STAR) … 4-10

4-5-1. General … 4-10 4-5-2. STAR Development and Charting … 4-10 4-5-3. RNAV STARs … 4-13 4-5-4. Procedure Depiction and Processing … 4-14 4-5-5. Waivers/Approval Requests … 4-15

4-5-6. STAR NOTAMs … 4-15 4-5-7. STAR Amendments … 4-15 4-5-8. Reviews … 4-16 4-5-9. Cancellation … 4-16 4-5-10. Military STAR Procedures … 4-16 4-5-11. Roles and Responsibilities … 4-17 4-5-12. Preparation of Form 8260-17.1, Standard Terminal Arrival (STAR) … 4-20 4-5-13. Preparation of Form 8260-17.2, STAR (Data Record) … 4-43 Section 4-6. RNAV Procedure Development … 4-52

4-6-1. General … 4-52 4-6-2. RNAV Approach Procedure Design … 4-52 4-6-3. Developing RNAV Waypoint … 4-54 4-6-4. RNAV Leg Types … 4-56 4-6-5. RNAV Leg Type Descriptions … 4-56 4-6-6. Final Approach Segment (FAS) Data … 4-57 4-6-7. Remote Altimeter Setting for Baro-VNAV … 4-57 4-6-8. Critical Temperature … 4-57 4-6-9. DME/DME Screening Model … 4-57 4-6-10. Additional documentation with Baro-VNAV … 4-58 Chapter 5. Airspace … 5-1

Section 5-1. Obstruction Evaluation (OE) … 5-1

5-1-1. General … 5-1 5-1-2. Responsibility and Processing of Form 7460-1 … 5-1 5-1-3. Review of Notices … 5-1 5-1-4. Adjustments to Instrument Flight Procedures … 5-1 Section 5-2. Designation of Controlled Airspace … 5-2

5-2-1. General … 5-2 5-2-2. Air Traffic Responsibility … 5-2 5-2-3. Aeronautical Information Services Action … 5-2 5-2-4. Terminal Airspace … 5-3 Section 5-3. Airport Airspace Analysis … 5-39

5-3-1. General … 5-39 5-3-2. Service Area OSG-FPT/Flight Standards Inputs … 5-39 5-3-3. Flight Standards Performs Flight Safety Review of Airport Proposals … 5-39 5-3-4. Service Area OSG-FPT is Responsible for Evaluation and Comment … 5-39 5-3-5. Alterations of Airports or Heliports … 5-40 5-3-6. Deactivation of Airports or Heliports … 5-40 5-3-7. Assistance in Zoning Problems … 5-41 Section 5-4. Restricted Areas … 5-42

5-4-1. General … 5-42 5-4-2. Letter of Procedures … 5-42 Section 5-5. Establishment, Relocation, or Discontinuance of Radio Navigation Aids … 5-43

5-5-1. Criteria and Guidelines … 5-43 5-5-2. OSG-FPT Action … 5-43 5-5-3. Flight Standards Action … 5-43

Chapter 6. Military Procedures … 6-1

6-1-1. General … 6-1 6-1-2. Review and Coordination … 6-1 6-1-3. FAA Acceptance … 6-1 6-1-4. Assistance … 6-1

Chapter 7. Planning … 7-1

Section 7-1. General … 7-1

7-1-1. General … 7-1 Section 7-2. Planning Standards … 7-2

7-2-1. Planning Standards … 7-2 7-2-2. Determination of Operational Benefits/Improvements … 7-2 Section 7-3. Safety Analysis … 7-4

7-3-1. Performing a Safety Analysis … 7-4 Section 7-4. Airway Planning … 7-7

7-4-1. General … 7-7 Section 7-5. Terminal Planning … 7-8

7-5-1. General … 7-8 7-5-2. Requirements for Outer Compass Locators … 7-8 Section 7-6. Airport Planning … 7-13

7-6-1. General … 7-13 Section 7-7. Private Aid … 7-14

7-7-1. General … 7-14 Section 7-8. Facilities and Equipment (F&E) Support … 7-15

7-8-1. Support … 7-15

Chapter 8. Instrument Approach Procedures Data Transmittal System … 8-1

Section 8-1. General … 8-1

8-1-1. General … 8-1 Section 8-2. FAA Form Use and Preparation … 8-2

8-2-1. Use of FAA Forms … 8-2 8-2-2. FAA Form preparation … 8-3 8-2-3. Course and Distance Information … 8-4 8-2-4. Communications Data … 8-5 8-2-5. Terminal Routes - General … 8-5 8-2-6. Terminal Fixes … 8-9 Section 8-3. Certification, Processing, and Review … 8-11

8-3-1. General … 8-11 8-3-2. Certification and Processing of SIAPs … 8-11 8-3-3. Cancellation/Suspension of Instrument Approach Procedures … 8-11 8-3-4. Revisions to IFPs … 8-12 8-3-5. Aeronautical Information Services Review of SIAPs and Charts … 8-16 8-3-6. Processing … 8-17 8-3-7. Distribution … 8-17 8-3-8. Special Procedures Printing and Distribution … 8-17

Section 8-4. Flight Procedures Standards Waiver, FAA Form 8260-1 … 8-21

8-4-1. Preparation of Form 8260-1, Flight Procedures Standards Waiver … 8-21 Section 8-5. Radio Fix and Holding Data Record, FAA Form 8260-2 … 8-24

8-5-1. Introduction … 8-24 8-5-2. Preparation of Form 8260-2 … 8-24 Section 8-6. Completion of FAA Forms 8260-3/4/5/7A … 8-35

8-6-1. General … 8-35 8-6-2. Basic Information … 8-35 8-6-3. Terminal Arrival Area (TAA) … 8-38 8-6-4. Terminal Routes … 8-40 8-6-5. Radar Terminal Area Maneuvering Sectors and Altitudes … 8-43 8-6-6. Missed Approach … 8-43 8-6-7. Profile - Lines 1 through 8 … 8-48 8-6-8. Equipment and PBN Requirements Notes … 8-54 8-6-9. Notes … 8-58 8-6-10. Additional Flight Data … 8-66 8-6-11. Minimums … 8-71 8-6-12. Changes and Reasons … 8-83 8-6-13. Coordinated With … 8-84 8-6-14. Submitted By … 8-84 8-6-15. Flight Checked By … 8-85 8-6-16. Developed By … 8-85 8-6-17. Recommended By … 8-85 8-6-18. Approved By … 8-85 8-6-19. FAS Data Block Information … 8-86 Section 8-7. Standard Instrument Approach Procedure Data Record, FAA Form 8260-9 … 8-87

8-7-1. Preparation of Form 8260-9 … 8-87 Section 8-8. Transmittal of Airways/Route Data Record, FAA Form 8260-16 … 8-97

8-8-1. Preparation of Form 8260-16 … 8-97 Section 8-9. Simultaneous Close Parallel (SCP) and Simultaneous Offset Instrument Approach

(SOIA) Procedure Attention All Users Page (AAUP) … 8-120 8-9-1. Attention All Users Page … 8-120 8-9-2. Site Implementation Team … 8-120 8-9-3. AAUP Preparation … 8-120 8-9-4. AAUP Processing … 8-120 8-9-5. AAUP Publication … 8-120 8-9-6. Forms Processing … 8-121 8-9-7. Title Line … 8-121 8-9-8. Text … 8-121 8-9-9. Administrative Information … 8-124

Appendix A. Administrative Information … A-1

Appendix B. Flight Procedures References … B-1

Appendix C. Obstacle Accuracy Standards, Codes, and Sources … C-1

Appendix D. FAA Form 8260-2, Data Worksheet … D-1

Appendix E. Radio Fix and Holding Data Record Form … E-1

Appendix F. ILS/RNAV Standard Instrument Approach Procedure Form … F-1

Appendix G. Radar – Standard Instrument Approach Procedure Form … G-1

Appendix H. Standard Instrument Approach Procedure Form … H-1

Appendix I. Special Instrument Approach Procedure / Special Authorization … I-1

Appendix J. Standard Instrument Approach Procedure Form … J-1

Appendix K. FAS Data Block Requirements … K-1

Appendix L. FAS Data Block Requirements for Helicopter Operations … L-1

Appendix M. Instrument Flight Procedures (IFP) Lifecycle … M-1

Chapter 1. General Information

Section 1-1. General

1-1-1. Purpose of This Order. This order provides guidance to all FAA personnel for the administration and accomplishment of the FAA Flight Procedures and Airspace Program. Additionally, this order provides guidance for the military and other government agencies to use when interacting with the FAA regarding instrument flight procedures. This order contains guidance that is pertinent to 14 CFR parts 71, 91, 95, 97, 121, and 135.

1-1-5. Explanation of Changes. › a. General.

1-1-2. Audience. The primary audience for this order is the Air Traffic Organization (ATO) Mission Support Services (MSS) (hereafter referred to as “AJV”), all service providers (as defined in Appendix A), and elements of the Armed Forces described in Title 10 of the United States Code (hereafter referred to as “military”) who have the responsibility to develop instrument flight procedures (IFPs). The secondary audience includes all other Air Traffic organizations, Flight Standards Service, and other organizations who have responsibilities related to IFP development.

Note: Users of this order can refer to Appendix A for an alphabetical listing of frequently used acronyms and abbreviations.

1-1-3. Where You Can Find This Order. You can find this order on the FAA’s web site.

1-1-4. What This Order Cancels. Order 8260.19H, Flight Procedures and Airspace, dated 07/20/2017, is canceled.

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

a. General.

(1) Incorporated changes to reflect recent organizational restructuring within the Flight Standards Service’s Flight Technologies and Procedures Division.

(2) Removed all references to All Weather Operations (AWO) to reflect organizational changes within Flight Standards Service’s Flight Technologies and Procedures Division.

(3) Removed all references to “Regional Airspace and Procedures Team” and its acronym, “RAPT.” This term was removed from the latest edition of Order 8260.43, Flight Procedures Management Program. The term “IFP Validation Team” replaced references to RAPT throughout the order.

(4) Removed all references to “National Flight Data Center” and “NFDC” and replaced with either “Aeronautical Information Services” or “Aeronautical Information Group.”

(5) Removed any references and policies related to RNAV (VOR/DME) approach procedures since these no longer exist.

1-1-5. Explanation of Changes. › c. Chapter 2.

(6) Removed the requirement to provide and document a “recommended NAVAID” to support coding of SID/STARs that incorporate course-to-fix (CF) and/or fix-to-manual (FM) legs.

(7) Amended FAA Forms 8260-3, 8260-4, and 8260-5 sample forms removing the airport names.

(8) Removed references to the “RNAV-Pro” DME/DME screening software and replaced with “DME/DME coverage prediction tool.”

b. Table of Contents. Updated to coincide with the pages changed.

c. Chapter 2.

(1) Paragraph 2-2-2.b. Corrected the primary usage of the U.S. Aeronautical Information Publication is by non-U.S. operators (vice U.S. operators).

(2) Paragraph 2-4-2. Removed specific listings and graphic depictions of navigation aid (NAVAID) standard service volumes. The most current listings of service volumes can be found in Order 6050.32, Spectrum Management Regulations and Procedures Manual.

(3) Paragraph 2-4-3.b. Removed ambiguous language regarding flight inspector authorization to use facility files to approve expanded service volume requests provided data was taken within last five years. Removed language directing a flight inspection if data was not available.

(4) Paragraph 2-5-3.c. Corrected magnetic variation tolerance for VOR and NDB facilities at CAT II/III airports. Included SA CAT I airports as those that must be maintained within one degree of the computed magnetic variance.

(5) Section 2-8. Revised (editorially) the periodic review section.

(6) Paragraph 2-8-2.b. Changed start date for determining the frequency of periodic reviews for original and full amendments from the “approved by” date to the “effective date.”

(7) Paragraph 2-10-2.a. Removed unnecessary language for a reporting point to be able to be identified at the lowest operational altitude.

(8) Paragraph 2-10-3. Replaced requirement to always evaluate for unplanned holding at all designated reporting points with a requirement to only evaluate holding at compulsory reporting points when specifically requested by ATC.

(9) Paragraph 2-10-3. Changed “designated reporting points” to “compulsory reporting points” for consistency with paragraph 2-10-2, Order 7110.65, and the Aeronautical Information Manual.

(10) Paragraph 2-10-4.b. Added language to prevent the establishment of a new waypoint over a stand-alone DME facility.

1-1-5. Explanation of Changes. › f. Chapter 8.

(11) Paragraph 2-11-2.c. Removed “manually” from first sentence for clarity.

(12) Paragraph 2-11-3.b(4). Added clarification that an obstacle accuracy value of 500 feet horizontal and 125 feet vertical is applicable to missed approach segments when determining the minimum missed approach obstruction altitude.

d. Chapter 4.

(1) Paragraph 4-1-3.d. Deleted “B” (signifying Class B airspace) from the first sentence.

(2) Paragraph 4-5-3. Expanded requirements for the charting of PBN navigation and sensor requirements for RNAV STARs.

(3) Paragraph 4-5-6. Added language related to STAR NOTAMs being limited to 224-days as currently described within Order 7930.2, Notices to Airmen (NOTAM), and the need to submit timely amendments.

(4) Paragraph 4-5-12.f. Revised communication documentation requirements to reflect ATIS frequencies will be charted automatically.

(5) Paragraph 4-6-10.h. Deleted requirements for annotating RF requirements since these requirements are now contained within paragraph 8-6-8.b.

e. Chapter 5. Paragraph 5-2-1. Removed reference to Order JO 7400.2 as a basis for a 300-foot buffer when establishing controlled airspace.

f. Chapter 8.

(1) Paragraph 8-2-2.a. Revised instructions for labeling forms for military procedures to be consistent with paragraph 8-6-1.

(2) Paragraph 8-2-5.e(1). Added policy to encourage the placement of feeder fixes at locations on airways that will allow entry from both directions.

(3) Paragraph 8-2-5.e(2). Added policy to permit the use of an arrival holding pattern at the beginning of a feeder route.

(4) Paragraph 8-3-2.a.(3). Added policy specifying that changes to GBAS FAS data fields included within CRC wrap require a hard effective date. Policy also added to allow hard dates to be used for navigational aid (NAVAID) commissioning or decommissioning projects.

(5) Paragraph 8-3-3.b. Removed language pertaining to the periodic inspection of suspended procedures (to include the note). Added clarification that periodic review requirements are still valid for suspended procedures.

(6) Paragraph 8-3-4.b.(1). Removed requirement to amend an approach procedure when the airport name is changed.

(7) Paragraph 8-3-4.b.(23). Added requirement to amend an approach procedure when any change is made to a data field of a FAS data block included within the CRC wrap.

(8) Table 8-3-1. Revised to reflect changes made to paragraph 8-3-4.

(9) Paragraph 8-5-2.h.(2)(f). Clarified what inbound course to enter of a Form 8260-2 for non-RNAV holding.

(10) Paragraph 8-6-4.a.(6). Revised terminal route documentation requirements to be consistent with current forms in use.

(11) Paragraph 8-6-6.g. Removed last two sentences that described documentation requirements when charting of missed approach holding patterns wasn’t required by ATC.

(12) Paragraph 8-6-7.d. Revised subparagraphs and notes removing the requirement to annotate stepdown fixes as applying to LOC or LNAV only. For procedures with a final segment stepdown fix that requires an altitude adjustment for secondary remote altimeter, an option was added to permit the inclusion of the necessary adjustment within the stepdown fix altitude (as opposed to a note).

(13) Paragraph 8-6-7.g(3). Added new requirement to indicate that the 34:1 is not clear when flight validation determines that a VDA/TCH cannot be published due to obstacles.

(14) Paragraph 8-6-8. Revised the annotation of equipment and PBN requirement notes significantly.

(15) Paragraph 8-6-9.f.(7)(a). Paragraph indicating an ASOS/AWOS-3 (or better) must be installed and commissioned removed due to being unneeded since systems transmitting on WMSCR must be commissioned.

(16) Paragraph 8-6-9.g. Deleted the requirement to annotate a chart note regarding the availability of ASR and/or PAR approaches; charting will annotate this information according to charting specifications.

(17) Paragraph 8-6-9.k. Chart note for non-paired DME revised for clarity.

(18) Paragraph 8-6-9.n. Removed annotation requirements related to DME/DME RNP 0.3.

(19) Paragraph 8-6-9.o.(2). Added vertical descent angle (VDA) policy to align with the intent of Order 8260.3.

(20) Paragraph 8-6-10.k. Deleted the requirement to annotate a chart note regarding the availability of ASR and/or PAR approaches; charting will annotate this information according to charting specifications.

(21) Paragraph 8-6-11.i(4). Expanded examples contained within Note 1 for situations where RNP 0.30 cannot be achieved.

Section 1-1. General › 1-1-6. Effective Date.

(22) Paragraph 8-6-11.k(1). Added policy and a new note format to prohibit the use of RVR 1800 when using a secondary altimeter.

(23) Paragraph 8-6-11.m(1). Revised note format for SA CAT I by removing the requirement to specify use of HUD to DH.

(24) Paragraph 8-6-11.m(2). Revised note format for SA CAT II by removing the requirement to specify use of HUD to DH.

(25) Paragraph 8-6-11.m(5). Specified use of the lowest RVR value from the CAT III checklist.

(26) Paragraph 8-6-11.o(6). For runways without a full length parallel taxiway, added a new note requirement to increase visibility when control tower is closed.

(27) Paragraph 8-7-1.b(7). Added an allowance to omit the sequential numbering of controlling obstructions on Form 8260-9, provided maps submitted to Flight Inspection include a description of the controlling obstruction, its height, and the affected segment.

(28) Paragraph 8-7-1.b(15). Deleted “VEB” as an adjustment code for use on Form 8260-9.

(29) Paragraph 8-7-1.d(1). Expanded documentation requirements for waivers and added requirement to document approvals.

(30) Paragraph 8-9-6. Removed “RNAV (RNP) PRM” from last sentence.

(31) Paragraph 8-9-8.b. Removed “RNAV (RNP) PRM RWY 28L from example in first sentence.

(32) Paragraph 8-9-8.d(4). Removed “RNAV (RNP) PRM” from Note 1.

(33) Paragraph 8-9-8.d(5)(a). Removed “RNAV (RNP) PRM.”

g. Appendix K, paragraph 4.w. Specified the HAL for LP procedures is fixed at 40 meters.

1-1-6. Effective Date. This order and subsequent changes are effective on the dates shown in the upper left corner of each page. Implementation of changes must commence no later than 24 months from the published effective date. Previous editions may be used until implementation has commenced, not to exceed 24 months from the new effective date.

1-2-2. Flight Technologies and Procedures Division. › b. Flight Operations Group. This group is the principal element of the…

Section 1-2. Responsibilities

Note: Applicable FAA 1100-series directives address organizational responsibilities and functions. Responsibilities specified in this section are provided for information only and for the purpose of assisting instrument procedure developers in knowing whom to contact for assistance and/or information in the performance of their duties. Do not interpret this section as a substitute or supplement to any other FAA directive.

1-2-1. Flight Standards Service.

a. Flight Standards Service is responsible for the use of air navigation facilities, appliances, and systems by aircraft operating in established environments and the National Airspace System (NAS). Responsibilities includes governing policy and oversight of manual and automated development and maintenance of terminal and en route flight procedures. The executive director has final authority to issue, amend, and terminate rules and regulations relating to instrument procedures, minimum en route altitudes, flight procedures, operational weather minimums, and minimum equipment requirements.

b. Responsibility for the overall management of the Flight Procedures and Airspace Program is vested in the Flight Technologies and Procedures Division. This order is primarily concerned with those offices having direct responsibility for the accomplishment of the Flight Procedures and Airspace Program. The following is a brief description of their activities.

1-2-2. Flight Technologies and Procedures Division.

a. This division is the principal element of the Flight Standards Service governing policies, criteria, and standards for establishing and maintaining terminal and en route flight procedures, and for using air navigation facilities and systems. This office is designated as the final authority to issue, amend, and appeal minimum en route instrument flight rules (IFR) altitudes and associated flight data under 14 CFR part 95; and standard instrument approach procedures and obstacle departure procedures under 14 CFR part 97.

b. Flight Operations Group. This group is the principal element of the division with respect to concepts, policies, systems, and programs associated with the operational and flight technical aspects of all-weather operations. The Flight Operations Group’s responsibilities include but are not limited to:

(1) Developing concepts for design, evaluation, and approval of category (CAT) I, II, and III approach and landing operations, as well as lower than standard takeoff minimums.

(2) Developing and issuing Form 8260-7B, Special Instrument Procedure Authorization, as required, through the Procedures Review Board (PRB).

(3) Providing specific Operations Specification (OpsSpec) language and inspector guidance regarding low visibility operations (CAT II/III) procedures and minima.

1-2-3. Air Traffic Organization, Flight Program Operations. › a. Flight Program Operations is the principal element directly…

(4) Developing performance based navigation (PBN) concepts, policies, standards, criteria, requirements, specifications, and limitations for new aircraft and new and existing airborne, ground-based and space-based systems used in instrument flight operations.

(5) Developing concepts, programs, and system requirements necessary to implement PBN and procedures necessary to implement futuristic communications and surveillance capabilities for oceanic, remote area, domestic en route, and terminal area operations, and for nonprecision and precision instrument approaches.

c. Flight Procedures and Airspace Group. This group is the principal element within the division with respect to the rulemaking process of the flight procedures program and to FAA and Flight Inspection policy oversight. This group serves as the focal point within Flight Standards for matters relating to airspace, instrument flight procedures (IFP), Notices to Airmen (NOTAMs), and is the primary interface for industry on matters relating to instrument procedures criteria. The Flight Procedures and Airspace Group’s responsibilities include but are not limited to:

(1) Developing national policies and directives pertinent to the design and maintenance of IFPs and charted visual flight procedures (CVFP).

(2) Coordinating non-government procedure developer NOTAM authority and access to the Federal NOTAM System (FNS) with ATO Mission Support Services, Aeronautical Information Services.

(3) Developing policy and providing oversight of the IFP development process for non- FAA Service Providers.

(4) Managing the program’s review and approval of all special IFPs and approval/waiver requests of procedure design standards.

(5) Managing and directing air carrier, general aviation, and all weather operations programs for a specified local area.

d. Flight Research and Analysis Group. This group is the principal element within the division providing simulation and human-in-the-loop analysis of new, emerging, or modified Communications, Navigation, and Surveillance (CNS) technologies and procedures in support of flight safety. This group analyzes and quantifies the levels of risk probabilities associated with the implementation of new, emerging, and modified flight operational concepts and navigation systems. Furthermore, this group manages the Flight Operations Simulation Laboratory comprised of flight simulators and ATC controller stations that can be linked to provide real time pilot/controller interface and data collection to meet the safety studies’ and risk analyses’ data requirements.

1-2-3. Air Traffic Organization, Flight Program Operations.

a. Flight Program Operations is the principal element directly responsible for the flight inspection of electronic signals-in-space from ground-based navigational aids, and/or flight validation that support aircraft departure, en route, and arrival flight procedures in the NAS.

Flight procedures are also evaluated for accuracy, aeronautical data, human factors flyability, and obstacle clearance; this includes the evaluation of avionics database code which represents the IFP in the Flight Management System (FMS). Flight Program Operations’ responsibilities include but are not limited to:

1-2-3. Air Traffic Organization, Flight Program Operations. › c. Aircraft Operations is the principal element within Flight Program…

(1) Supporting flight inspection for the Department of Defense (DoD) on foreign navigational facilities that have been designated as essential to the defense of the United States.

(2) Inputting (when solicited) to the Air Traffic Technical Operations Service Areas Facilities and Equipment (F&E) budget submission with respect to terminal air navigation aids (other than radar) and visual approach aids.

b. Flight Program Operations, Flight Inspection Scheduling is responsible for scheduling flight inspections. Flight Inspection Scheduling maintains liaison with Aeronautical Information Services, as well as other FAA offices, civil and military interests, to ensure consideration of all requirements relating to the procedural use of navigation facilities. Flight Inspection Scheduling’s responsibilities include but are not limited to:

(1) Issuing NOTAM D in accordance with Order 8200.1, United States Standard Flight Inspection Manual.

(2) Managing, processing, and coordinating flight inspection procedure packages.

(3) Scheduling special requests for flight inspections.

(4) Maintaining suitable record system reflecting the status of each flight.

(5) Managing the requirements and technology for Flight Inspection Report System, Flight Operations Management System, and Flight Management Daily Flight Log.

(6) Acting as the focal point for all PBN Policy and Support Office generating machinereadable form files as well as the Knowledge System Network (KSN) Distance Measuring Equipment (DME)/DME directory.

(7) Providing Flight Inspection Reports (FIR) containing data pertinent to the AIRNAV database and resolving AIRNAV data discrepancies.

(8) Ground evaluation (validation) of coded IFPs.

(9) Initiating and completing investigative remedial action with respect to any deficiency or reported hazard, including restrictions or emergency revisions to procedures.

c. Aircraft Operations is the principal element within Flight Program Operations responsible for flight inspection of navigation aids (NAVAIDs) and instrument flight procedures in support of the NAS. Flight Program Operations has multiple facilities that support the flight inspection mission.

1-2-4. Air Traffic Organization, Mission Support Services (AJV-0). › a. Aeronautical Information Services is directly responsible for…

1-2-4. Air Traffic Organization, Mission Support Services (AJV-0).

a. Aeronautical Information Services is directly responsible for managing the agency’s program to provide Aeronautical Information Services to ensure the flow of information necessary for safety, regularity, and efficiency of air navigation. This office is charged with the responsibility for collecting, collating, verifying, maintaining, and disseminating aeronautical data regarding the U.S. and its territories. It is also a source for database accuracy standards, content, and format.

(1) Aeronautical Information Services maintains the National Airspace System Resources (NASR) database and disseminates information relating to the NAS. Aeronautical Information Services is also responsible for maintaining proposed data within the AIRNAV database for the development of instrument flight procedures. Their responsibilities include but are not limited to:

(a) Publishing the daily National Flight Data Digest (NFDD) and 56-day subscriber files to promulgate additions, changes, and deletions to non-regulatory elements of the NAS. Respective changes are also published in Order JO 7340.2, Contractions, and Order JO 7350.8, Location Identifiers.

(b) Conducting pre-publication review of aeronautical data contained in standard instrument approach and departure procedures, standard terminal arrivals, standard instrument departures, military training routes, navigational aids, airport data, and airspace changes submitted for action, and to identify and correct items in non-conformance with applicable directives.

(c) Validating submitted data with the NASR Database and resolving contradictions.

(d) Managing the development and assignment of five-letter fix names and NAVAID/airport identifiers.

(e) Issuing, on a predetermined schedule, amendments to 14 CFR part 95.

(f) Maintaining copies of 8260- and 7100-series forms that support public use standard instrument approach procedures (SIAPs), fixes, airways, standard terminal arrival routes (STARs), and departure procedures (DPs).

(2) Aeronautical Information Services is the principal element responsible for developing, directing, and recommending national policy and criteria for aeronautical information. This group serves as the Mission Support Services focal point for developing and managing Geographic Information Systems for the NAS. They are also responsible for collecting, verifying, and maintaining obstacle data to support instrument flight procedure development including minimum vectoring altitude (MVA) and minimum IFR altitude (MIA) charts as well as minimum safe altitude warning (MSAW) data creation. Responsibilities include but are not limited to:

1-2-4. Air Traffic Organization, Mission Support Services (AJV-0). › b. Aeronautical Information Services (AJV-A) is also responsible for…

(a) Establishing the U.S. position for Aeronautical Information Manual (AIM) and Aeronautical Information Services through the International Civil Aviation Organization (ICAO).

(b) Collecting, validating, verifying, managing, and disseminating as-built obstacle data reported under 14 CFR part 77.

1. Providing the publically-available Digital Obstacle File (DOF), which contains a record of all as-built man-made obstructions that effect domestic aeronautical charting products.

2. Providing Obstacle Repository System (ORS) data to other FAA offices on a timely basis.

(c) Verifying source data for as-built obstacles and assigning accuracy codes that reflect the reliability of the reports obstacle’s vertical and horizontal position depicted as Above Ground Level (AGL) and geographic coordinates.

(d) Managing the verification/validation of airport survey safety critical data.

(e) Managing the requirements and technology to support database needs and infrastructure.

b. Aeronautical Information Services (AJV-A) is also responsible for the development, maintenance, quality assurance, and technical approval of public-use flight procedures, production, and distribution of aeronautical charts and related publications and products. Responsibilities include, but are not limited to, the following:

(1) Development, publication, and maintenance of SIAPs.

(2) Development, publication, and maintenance of obstacle departure procedures (ODPs) and standard instrument departure procedures (SIDs). Development and maintenance of diverse vector areas (DVA).

(3) Development, publication, and maintenance of Air Traffic Service (ATS) routes.

(4) Review and publication of STAR Airport diagrams and special graphics.

(5) Responsible for quality assurance of items produced by Aeronautical Information Services.

(6) Operations support, as requested, for NAS-related products.

(7) Selecting and evaluating source data for final chart compilation.

(8) Validating geographical positions, distances, and bearings of items produced by Aeronautical Information Services.

1-2-4. Air Traffic Organization, Mission Support Services (AJV-0). › d. Service Center, Operational Support Group, Flight Procedures Teams…

(9) Maintaining liaison with elements of FAA to support safe and accurate portrayal of charting data.

(10) Providing civilian charts in support of military requirements.

(11) Providing international charting support to selected foreign countries.

(12) Establishing procedures to ensure operational data are included in the NASR database.

(13) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil, joint-use, and U.S. Army instrument procedures in accordance with current policy.

(14) Promulgating SIAPs, ODPs, and permanent FDC NOTAMs relating to IFPs with assigned effective dates in a bi-weekly transmittal letter and completing necessary requirements for publication in 14 CFR part 97.

c. Air Traffic Standards & Procedures Directorate (AJV-P31) provides support to air traffic operations through policy, procedures, separation standards, equipment, software, and other operations related to air traffic activities across the NAS. AJV-P31 serves as the primary point of contact for the Service Areas, Service Centers and field facilities for Terminal, En Route and Oceanic/Offshore operations, standards, and procedures issues.

d. Service Center, Operational Support Group, Flight Procedures Teams (OSG-FPTs), responsibilities include but are not limited to:

(1) Evaluating and responding to industry and user comments relating to instrument procedures.

(2) Coordinating IFP requests with the respective Air Traffic Service Area and other concerned offices, and conducting instrument procedures feasibility studies.

(3) Coordinating submission by responsible offices of all pertinent data and supporting documents required for procedures development and assignment of priority when further procedures action is required.

(4) Planning and coordinating new or relocated NAS facilities.

(5) Coordinating with applicable Air Traffic Service Areas to select a charting date consistent with priorities and workload when a component of the NAS is to be commissioned, de-commissioned, or altered.

(6) Coordinating the input for the planning and development of regional and Air Traffic Service Area F&E budget submissions and programming actions.

(7) Evaluating regional airport and airspace changes for impact on instrument flight procedures.

Section 1-2. Responsibilities › 1-2-5. Individual.

(8) Determining the necessity for environmental impact studies as required by current policy.

(9) Acting as the focal point for flight inspection issues within the region.

1-2-5. Individual. Personnel working within the Flight Procedures Program are responsible for maintaining professional knowledge in a technical, complex, and specialized field, and for the application of the knowledge to assure safety and practicality in air navigation. Where directives are deficient, each individual must take the initiative to seek an acceptable method of resolution and to inform the responsible office of any recommended change to policy, procedures, etc. that is cost beneficial and/or provides increased operational safety.

2-1-3. Airport Lighting and Visual Aids. › a. Operation of airport lighting and visual aids is contained in the…

Chapter 2. General Procedures

Section 2-1. General

Note: This chapter provides guidelines and procedures that are common to all instrument flight procedures. Specific guidelines and procedures for en route and terminal instrument flight procedures are contained in Chapters 3 and 4, respectively.

2-1-1. Requests for Public-use Instrument Flight Procedures (IFPs).

a. Requests for approval and/or establishment of instrument flight procedures may originate from many different sources (see Order 8260.43). It may be a request from a state, city, airport manager, or an individual. It may also be from an air carrier, air taxi, military, commercial operator, Air Traffic Control (ATC), or Flight Standards’ personnel. General information on the lifecycle process associated with IFPs can be found in Appendix M.

b. Requirements for approval of IFPs are contained in Order 8260.3, U.S. Standard for Terminal Instrument Procedures (TERPS), Chapter 1.

c. Procedures with specific effective dates, and other urgent projects, will be assigned priorities by Aeronautical Information Services. All other projects will be processed as workload permits, by Aeronautical Information Services in order of receipt.

2-1-2. Air Traffic Letters of Agreement (LOAs). When LOAs affect or include flight procedures, they must be coordinated between ATC facilities and Aeronautical Information Services.

a. When these letters are received, Aeronautical Information Services must review them to ensure compatibility with published or planned flight procedures.

b. Copies of LOAs received in Aeronautical Information Services must be made a part of the procedure files, to serve as a reference when developing or amending flight procedures.

c. When the terms of the LOAs and flight procedures are not compatible, or if it is determined that the terms do not comply with criteria, Aeronautical Information Services must return the LOAs to the ATC facility with a memorandum that explains the findings. When appropriate and practical, consideration should be given to adjusting the procedures to accommodate the terms of the agreement.

d. Normally, an LOA is an agreement between two or more ATC facilities. Unless Aeronautical Information Services is a party to the agreement, it is not a signatory and does not approve or disapprove the agreement.

2-1-3. Airport Lighting and Visual Aids.

a. Operation of airport lighting and visual aids is contained in the following orders:

(1) Order JO 7110.10, Flight Services.

2-1-3. Airport Lighting and Visual Aids. › c. Refer to Appendix B, Flight Procedures References, for other…

(2) Order JO 7110.65, Air Traffic Control.

(3) Order JO 7210.3, Facility Operation and Administration.

b. Installation criteria are contained in Order 6850.2, Visual Guidance Lighting Systems.

c. Refer to Appendix B, Flight Procedures References, for other applicable orders and advisory circulars.

2-2-2. Aeronautical Charts and Publications. › d. Aeronautical Information Services is responsible for the accuracy…

Section 2-2. Aeronautical Charts

2-2-1. Use of Maps and Charts.

a. Aeronautical Information Services should maintain an adequate supply of current charts, or electronic equivalent, to support the development of instrument procedures within its area of responsibility. For manual application, the largest scale charts available should be used to develop final, circling, and the first part of the missed approach segment. For precision approach procedures, survey information or an equivalent plan and profile chart is recommended for use. For all approach procedures, the 7 1/2 and 15-minute quadrangle topographic charts (Quads) produced by the U.S. Geological Survey provide an excellent source for determining terrain elevation profiles; alternatively, another excellent source for the most current ground elevation is the USGS National Map, which reflects the most current and accurate elevation data. For efficiency in procedure design and flight inspection, 1:100,000 scale planimetric/topographical (topo) charts are also authorized. Use other data sources such as Digital Obstruction File, AIRNAV database, Aeronautical Information Services Weekly Obstacle Memo, Digital Terrain Elevation Data (DTED), Digital Elevation Model (DEM), etc., in addition to on-site obstacle assessment evaluations, where necessary. The Sectional Aeronautical Chart (scale 1:500,000) and the visual flight rules (VFR) Terminal Area Chart (scale 1:250,000) are good supporting source documents; however, they may not depict all current information because of the extended charting cycle.

b. Map requirements for inclusion in a flight inspection package are determined by Flight Program Operations (see Order JO 8200.44, Coordination of Flight Inspection Procedure Packages).

2-2-2. Aeronautical Charts and Publications.

a. Aeronautical charts used for air navigation are generally of two groups: VFR charts and IFR charts. The VFR charts are the Sectional charts, VFR Terminal Area charts, and the visual navigation chart. IFR charts include the En Route Low and High Altitude and Area charts as well as the Terminal Procedures Publication (TPP), which includes SIAP, textual and graphic DP, STAR, and Charted Visual Flight Procedure (CVFP) charts.

b. The primary publication containing basic flight information related to instrument operations in the NAS, is the AIM. The primary publication serving as a pre-flight and planning guide for use by non-U.S. operators, business, and private aviators flying into or over the U.S., is the U.S. Aeronautical Information Publication (AIP). Flight Technologies and Procedures Division’s personnel should conduct periodic surveillance of the AIM and AIP to verify the accuracy and appropriateness of the information. AIM and AIP discrepancies and errors should be forwarded to the Air Traffic Procedures, Process Support Group (AJV-P31).

c. Aeronautical Information Services personnel should monitor charts or publications released by the FAA that provide informative material, recommended or mandatory, to determine that safe operating practices and conditions are accurately described for aviation users.

d. Aeronautical Information Services is responsible for the accuracy and completeness of flight data submitted by that office for publication. Procedure specialists should review the

2-2-2. Aeronautical Charts and Publications. › g. Any FAA personnel who find or are notified of aeronautical chart…

resulting published U.S. Government charts to ensure correct portrayal. Aeronautical Information Services serves as the focal point for questions regarding the procedural data published on these charts.

e. Aeronautical Information Services is responsible for ensuring that U.S. Government Aeronautical Charts conform to Interagency Air Cartographic Committee (IACC) specifications.

f. Aeronautical Information Services serves as the focal point for questions regarding other non-procedural data; e.g., airport/runway data, frequencies, etc. Aeronautical Information Services will resolve questions through the appropriate data source steward.

g. Any FAA personnel who find or are notified of aeronautical chart discrepancies and/or errors should send notification through the Aeronautical Information Portal to [email protected].

Section 2-3. Environmental Requirements › 2-3-2. Environmental Impacts.

Section 2-3. Environmental Requirements

2-3-1. Noise Abatement. The establishment of noise abatement procedures is the responsibility of the ATO. However, the Flight Standards Service has an input from an aircraft operational standpoint. These procedures should be coordinated between the appropriate Flight Technologies and Procedures Division representative and the OSG-FPT. The Flight Technologies and Procedures Division representative must review noise abatement procedures for aircraft performance characteristics and operational safety considerations. The OSG-FPT must review these procedures for practicality and adherence with applicable criteria, and has the primary responsibility for resolving conflicts between IFR procedures and existing or proposed noise abatement procedures.

2-3-2. Environmental Impacts. Compliance with the following directives: Order 1050.1, Policies and Procedures for Considering Environmental Impacts, and Order JO 7400.2, Chapter 32 is required to meet the environmental compliance requirements of the Agency under the National Environmental Policy Act (NEPA).

2-4-3. Requests for Expanded Service Volumes. › e. For holding patterns, process an ESV request for the holding fix.…

Section 2-4. Facility Utilization and Monitoring

2-4-1. Frequency Service Volumes. In establishing instrument flight procedures, consideration must be given to the type of navigation facilities available and to their limitations.

a. All electronic navigation facilities are installed in accordance with frequency separation specified in distances and altitudes. Specific frequency protected service volumes are contained in Order 6050.32, Spectrum Management Regulations and Procedures Manual. The Regional Frequency Management Officer (RFMO) primarily uses this order. Order 6050.32 also contains information to facilitate understanding and coordination of operational considerations associated with expanded service volumes.

b. Operational service volume includes the standard service volume (SSV) and expanded service volumes (ESVs). The operational service volume must not extend outside the frequency protected service volume on any radial, at any distance, or at any altitude.

2-4-2. ATC Usable Distance and Altitude Limitations. When flight procedures are developed which reach outside of the standard service volumes (lateral and/or vertical) cited within Order 6050.32, the submission and processing of an ESV Request, is mandatory. Flight check measurements must not be used as a substitute for an approved ESV.

2-4-3. Requests for Expanded Service Volumes.

a. When necessary, submit an ESV request with a description of the flight procedure requiring it. The Frequency Management Officer (FMO) first reviews this request. The FMO applies the criteria contained in Order 6050.32. If the FMO disapproves the request, it is returned to the originator without further action. FMO-approved or restricted ESVs are then reviewed by Aeronautical Information Services.

b. Aeronautical Information Services is responsible for accuracy, clarity, and practicality of the data. If the ESV request is unclear, or if the FMO-approved request has restrictions or restrictive comments, it may be necessary to coordinate changes with the FMO and/or the originating office. FAA flight inspection determines if the facility supports the procedure.

c. The procedures specialist when developing an instrument procedure may determine a requirement for an ESV; e.g., the instrument procedure is proposed beyond SSV. In this case, the procedures specialist processes an ESV electronically via the Expanded Service Volume Management System (ESVMS website) to obtain the FMO and, in turn, flight inspection approval. An ESV request must not be used as a substitute for proper instrument procedure design.

d. Facility rotation due to magnetic variation change should have no effect on coverage; however, radials used will change. Aeronautical Information Services initiates a change action via the spectrum management web site (ESVMS) on the date the rotation is effective.

e. For holding patterns, process an ESV request for the holding fix. Describe holding fix by radial, distance, altitude.

f. An ESV is prepared and processed electronically via the ESVMS via the FAA Intranet web site. An ESV can be placed on any very high frequency omnidirectional range (VOR), instrument landing system–distant measuring equipment (ILS-DME), or tactical air navigation (TACAN). When a DME or TACAN and VOR are paired, both must have identical ESVs for safety reasons [except in those cases where the DME ESV supports DME/DME area navigation (RNAV) operations]. ESVs may be added to any class of NAVAID facilities, including NDBs.

2-4-6. Utilization of Monitoring Categories. › a. Category 1 facilities may be used for instrument flight procedures…

2-4-4. Utilization of Localizers.

a. A localizer must not be used for lateral course guidance on an ATS route. However, a localizer may serve as a crossing facility to define a fix on an ATS route where it is essential to air traffic control.

b. A localizer must not be used for lateral course guidance within a missed approach segment, except a localizer may be used that utilizes a straight-ahead course which crosses over the localizer antenna and then outbound on the localizer back course, provided that a back course is available.

2-4-5. Monitoring of Navigation Facilities.

a. Monitors. It is FAA policy to provide a monitoring system for all electronic navigation facilities used in support of instrument flight procedures. Internal monitoring is provided at the facility through the use of executive monitoring equipment that causes a facility shutdown when performance deteriorates below established tolerances. A remote status indicator may also be provided through the use of a signal-sampling receiver, microwave link, or telephone circuit. VOR, VORTAC, and ILS facilities as well as new NDBs and marker beacons installed by the FAA, are provided with an internal monitoring feature. Older FAA NDBs and some non-Federal NDBs do not have the internal feature and monitoring is accomplished by other means.

b. Monitoring categories. Navigational facilities are classified in accordance with the manner in which they are monitored.

(1) Category 1. Internal monitoring plus a status indicator installed at control point. Reverts to a temporary category 3 status when the control point is unmanned/monitoring not available.

(2) Category 2. Internal monitoring with status indicator at control point inoperative, but pilot reports indicate the facility is operating normally. This is a temporary situation that requires no procedural action.

(3) Category 3. Internal monitoring only.

(4) Category 4. Internal monitor not installed. Remote status indicator provided at control point. This category is applicable only to nondirectional beacons.

2-4-6. Utilization of Monitoring Categories.

a. Category 1 facilities may be used for instrument flight procedures without limitation.

2-4-7. Utilization of 75 MHz Markers. › e. DP turn points. The 75 MHz markers must not be used to identify turn…

b. Category 2 is a temporary condition not considered in instrument procedure development. The ATO is responsible for issuing NOTAMs on these out-of-service facilities when pilot reports indicate facility malfunction.

c. Category 3 facilities may be used in accordance with the following limitations:

(1) Alternate minimums must not be authorized if facility provides final approach course (FAC) guidance; is required for procedure entry; is used to define the final approach fix (FAF); or is used to provide missed approach guidance [see also paragraph 8-6-11.b].

(2) Consider denying or adjusting terminal routes that require reception of succeeding category 3 facilities to avoid obstacles.

(3) Dogleg airways or routes must not be predicated on these facilities.

(4) Navigational fixes developed from crossing radials of category 3 facilities must not be used to break a MEA to higher MEA (can be used as a break to a lower MEA).

d. Category 4 facilities may be used in accordance with the following limitations:

(1) Alternate minimums may be authorized when the remote status indicator is located in an FAA ATC facility, and then only during periods the control point is attended.

(2) If the control point is other than an FAA facility, a written agreement must exist whereby an ATC facility is notified of indicated changes in facility status.

Note: Failure of this category 4 status indicator or closure of the control point will render the facility and the approach procedure unusable during the outage.

2-4-7. Utilization of 75 MHz Markers. The 75 MHz markers may be used as the sole source of identification with the following limitations:

a. Missed approach point (MAP). Markers may be authorized as missed approach points for nonprecision approaches, provided a remote status indicator (RSI) is installed at an ATC facility.

b. Final approach fix. As a non-precise final approach fix, the marker must be monitored if alternate minimums are authorized. The marker need not have an RSI if collocated with a compass locator with a remote status indicator.

c. Course reversals. Procedure turns and holding must not be authorized from a 75 MHz marker.

d. Breaks in MEAs. The 75 MHz markers must not be used to define the point where an en route climb to a higher altitude is required (may be used as a break to a lower altitude).

e. DP turn points. The 75 MHz markers must not be used to identify turn points on departure procedures. See Order 8260.46, Departure Procedure (DP) Program, paragraph 2-1-1.d.

2-5-2. Responsibilities. › a. Aeronautical Information Services.

Section 2-5. Implementing Epoch Year Magnetic Variation (MV)

2-5-1. General. This section establishes the MV program, identifies participating offices, assigns responsibilities, and provides guidelines for accomplishing the tasks necessary for implementing, maintaining, and systematically updating epoch year MV values.

a. Background. The National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), and the National Geodetic Survey (NGS), for all areas of the U.S. and its territories for application to navigation charts and maps, is the source for MV information and tools for establishing MV. Changing values for MV are tabulated and published on a five-year epoch basis; e.g., 00, 05, 10, 15, 20, etc. In order to assist in stabilizing the NAS, a fixed value of MV is assigned to each NAVAID and airport as the MV of record. This value is applied to true directions to obtain the magnetic values for radials, courses, bearings, and headings published in instrument flight procedures. Periodic updating of the MV assigned to navigation facilities is required to maintain reasonable proximity of alignment with the earth’s ever-changing magnetic field. It is possible that the magnetic course displayed by the aircraft's RNAV system is different than the magnetic course portrayed on the IFP chart.

Note: RNAV systems, unlike IFP designs, generally apply the MV value stored in their navigational database, though other values are sometimes applied. As such, it is entirely possible that the MV applied by the RNAV system is different than the MV used by the procedure designer when the IFP chart was last updated. Thus, the magnetic course displayed by the RNAV system may not match the magnetic course charted on the IFP plate. Despite this difference, an RNAV system should still navigate properly as these systems use true north for navigation and only display magnetic course for pilot reference.

b. Participating offices. Management and control of epoch year MV values require action by the following offices:

(1) Aeronautical Information Services,

(2) Military organizations,

(3) Western, Central, and Eastern Technical Operations,

(4) Western, Central, and Eastern OSG-FPTs, and

(5) Regional Airports Divisions.

2-5-2. Responsibilities.

a. Aeronautical Information Services.

(1) Publish isogonic lines or segments on appropriate aeronautical charts based on current epoch year values.

(2) Revise en route aeronautical charts and Chart Supplements to reflect revised MV assignments to navigation facilities in accordance with information published in the NFDD.

(3) Revise en route charts to apply yearly MV change values to RNAV (“Q” and “T”) route Magnetic Reference Bearings (MRB) during the first airspace charting cycle of each calendar year.

(4) Function as the focal point for all information relating to application of MV to the following elements of the NAS: NAVAIDs, airports, instrument flight procedures; and for coordination and liaison between Aeronautical Information Services and the applicable Air Traffic Service Center OSG-FPTs.

(5) Function as the focal point for FAA and all NAS Facilities Flight Inspection coordination. Terminal facilities (other than VOR, VOR/DME, TACAN, VORTAC, and radar systems) do not require flight inspection of MV changes.

(6) Determine whether NOTAM action is necessary when required procedural adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.

(7) For FAA and all NAS facilities, assign and maintain MVs of record for navigational facilities and airports in whole degree increments. MVs of record are available in the AIRNAV facility database. For new or relocated facilities, and new or revised instrument procedures, apply the appropriate MV. Analyze each facility identified as a candidate for revised MV assignment to determine if facility rotation and/or re-designation of radials are required.

(8) Establish a process to record the assigned magnetic variation and epoch year of NAVAIDs and airports by geographical location and the projected MV for the next epoch year. The process must also include the ability to identify those candidate navigational aids and airports with a difference of two degrees or more between the MV of record and the nearest future epoch year value.

(9) Notify Aeronautical Information Services of changes to assigned MV and the effective date of those changes for publication in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected must allow sufficient time for procedures processing in accordance with established schedules. MV changes, which affect only terminal instrument procedures, may have an effective date concurrent with publication of a specific procedural amendment.

(10) Amend instrument flight procedures as required, predicated on NAVAIDs or airports undergoing a change of MV of record. Conduct a thorough review survey to determine the full impact the MV change will have on any instrument procedures. Such reviews must include high and low altitude ATS routes, direct routes, air carrier off-airway routes, fixes in both high and low altitude structures, terminal routes and fixes, ODPs, SIDs, STARs, and any other application to instrument flight procedures. Use the MV of record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the airport diagram chart or similar product being used.

(11) VOR, VOR/DME, and VORTAC facilities supporting the en route structure (which may or may not have instrument procedures predicated on them):

2-5-2. Responsibilities. › b. United States Air Force (USAF).

(a) Modify all fixes and instrument approach procedures (IAPs). Modify all 14 CFR part 95 direct and off-airway (non-14 CFR part 95) routes with documented radial(s) or bearing(s). Change ESVs. Make all modifications to meet an effective date that coincides with the en route change cycle.

Note: A listing of affected fixes, holding patterns, DPs, SIDs, STARs, military training routes, preferred routes, and ATS routes may be obtained from Aeronautical Information Services.

(b) Coordinate changes with the OSG-FPT (OSG-FPTs are expected to coordinate with the applicable ARTCC and/or approach control) in an attempt to eliminate routes, fixes, and instrument procedures that are no longer required.

(12) NAVAIDs not supporting en route structure:

(a) Initiate implementation of the nearest future epoch year MV in accordance with paragraph 2-5-3.a, whenever any instrument procedure is established or amended. The nearest future epoch year MV will become effective concurrent with publication of the amendment [see paragraphs 8-6-2.k and 8-6-2.l].

(b) Amend and process multiple instrument procedures to simultaneously become effective concurrent with the instrument procedure specified in the MV change notification to Aeronautical Information Services.

(c) Submit revisions of all affected fixes with the instrument procedure(s). Change ESVs.

(d) Amend radar procedures when the airport MV of record is changed.

(13) Army facilities.

(a) Accomplish MV changes for U.S. Army facilities in the same manner as for civil facilities; however, obtain the installation commander’s prior approval.

(b) Notify the appropriate military representatives, in writing, when the need to change the MV of other military facilities is identified.

b. United States Air Force (USAF).

(1) Function as the focal point for all USAF applications of MV for USAF facilities within and outside the NAS to include; NAVAIDs, airports, instrument flight procedures.

(2) Function as the focal point for USAF non-NAS facility flight inspection requirements and coordination. Terminal facilities (other than VOR, VOR/DME, TACAN, VORTAC, and radar systems) do not require flight inspection of MV changes.

(3) Determine whether NOTAM action is necessary when required procedural adjustment action or MV change is not accomplished by the effective date of amended instrument procedures or revised en route charts.

(4) Assign and maintain MVs of record for USAF non-NAS navigational facilities and airports in whole degree increments. For new or relocated facilities, and for new or revised instrument procedures, apply the appropriate MV. Analyze each facility identified as a candidate for revised MV assignment to determine if facility rotation and/or re-designation of radials are required.

(5) Maintain a listing/record of USAF navigational aids and airports by geographical location. Indicate the currently assigned MV of record and the projected MV for the next epoch year. For the purpose of planning and implementation, maintain a current listing of those candidate navigational aids and airports with a difference of two degrees or more between the MV of record and the nearest future epoch year value.

(6) Notify Aeronautical Information Services of changes to USAF non-NAS facilities assigned MV and the effective date of those changes in order to generate a letter for publication in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected must allow sufficient time for procedures processing in accordance with established schedules. MV changes, which affect only terminal instrument procedures, must have an effective date concurrent with publication of a specific procedural amendment.

(7) Amend instrument flight procedures as required, predicated on navigational aids or airports undergoing a change of MV of record. Conduct a thorough survey to determine the full impact the MV change will have on any instrument procedure. Such surveys must include high and low altitude airways/jet routes, direct routes, air carrier off-airway routes, fixes in both high and low altitude structures, terminal routes and fixes, ODPs, SIDs, STARs, ESV’s, and any other application to instrument flight procedures. Use the MV of record (or as officially changed) to develop instrument flight procedures - regardless of the MV shown on the airport diagram or similar product being used.

(8) USAF navigational facilities within the NAS:

(a) Maintain official listing of USAF facilities that are part of the NAS.

(b) Notify Aeronautical Information Services when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary.

(9) USAF navigational facilities not within the NAS:

(a) Initiate implementation of the nearest future epoch year MV, as per paragraph 2-5-3.a, whenever any instrument procedure is established or amended. The nearest future epoch year MV must become effective concurrent with publication of the amendment [see paragraphs 8-6-2.k and 8-6-2.l].

(b) Amend and process multiple instrument procedures to simultaneously become effective concurrent with the instrument procedure specified in the MV change notification to Aeronautical Information Services.

2-5-2. Responsibilities. › d. OSG-FPT.

(c) Submit revisions of all affected fixes with the instrument procedure(s). Change ESVs, as required.

(d) Amend all procedures as, required, when the airport MV of record is changed.

c. United States Navy.

(1) Contact Aeronautical Information Services to obtain the MV of record or MV assignments for new or relocated facilities to be applied to navigational aids or airports under U.S. Navy jurisdiction.

(2) Coordinate with Aeronautical Information Services to determine impact of MV changes for both military and public facilities.

(3) U.S. Navy flight procedure development work generally follows the same requirements as Aeronautical Information Services’ flight procedure development work as outlined in paragraphs 2-5-2.b(3) through 2-5-2.b(9). Aeronautical Information Services will remain the office of primary responsibility for paragraphs 2-5-2.b(1), 2-5-2.b(2), 2-5-2.b(4), and 2-5-2.b(5) functions.

(4) Notify Aeronautical Information Services of changes to U.S. Navy, non-NAS facilities, assigned MV and the effective date of those changes in order to allow Aeronautical Information Services to publish them in the NFDD; notify other concerned offices having related responsibilities to ensure timely implementation of necessary actions. The effective date selected must allow sufficient time for procedures processing in accordance with established schedules. MV changes, which affect only terminal instrument procedures, must have an effective date concurrent with publication of a specific procedural amendment.

(5) U.S. Navy navigational facilities within the NAS:

(a) Maintain official listing of U.S. Navy facilities that are part of the NAS.

(b) Notify Aeronautical Information Services when MV changes are required. Allow sufficient time for modification of FAA fixes and IAPs as necessary. Aeronautical Information Services will publish a notice of change in the NFDD when the MV of Record changes. An effective date of change must be included in the NFDD.

d. OSG-FPT.

(1) Notify Aeronautical Information Services of MV changes when informed by non- FAA service providers maintaining instrument procedure(s) they are responsible for.

(2) The OSG-FPTs will coordinate with the regional airports and Air Traffic offices with respect to matters pertaining to change in navigational aid or airport MV of record and its effect on instrument flight procedures.

2-5-3. Guidelines for Magnetic Variation Revisions. › b. Standard MV limits for airports and NAVAIDs. When the difference…

e. Western (AJW-W), Central, (AJW-C), and Eastern (AJW-E) Technical Operations. Coordinate with the respective OSG-FPT to obtain the appropriate MV of record for assignment to newly installed or relocated navigational aids.

f. Regional Airports Division/Airports District Office (ADO). Upon notification from the airport operator, coordinate with the applicable OSG-FPT prior to establishing or revising runway designator numbers for an airport having one or more instrument approach or departure procedures, to determine the appropriate MV to be applied to the runway true bearing. Determination of the runway designator number should be a matter of joint agreement with Aeronautical Information Services, and be accomplished sufficiently in advance to allow for procedural amendments. Take appropriate NOTAM action if repainting of an affected runway has not been accomplished on the required date.

2-5-3. Guidelines for Magnetic Variation Revisions. The identification and selection of NAVAIDs or airports as candidates for revision of MV of record requires careful consideration and evaluation of a number of factors as the impact of MV changes can be considerable. The applicable Air Traffic Service Area Office may have to initiate or revise published air traffic procedures. The Technical Operations Service (AJW-0) is directly involved in NAVAIDs/radar rotations and requires proper coordination. The Airports Division, or appropriate military authority, may have to arrange for repainting of runway designator numbers [see paragraph 8-3- 4.b(5)].

Note: Guidelines pertaining to runway designation marking relative to magnetic changes can be found in AC 150/5340-1, Standards for Airport Markings.

a. MV versus epoch year value. The NOAA World Magnetic Model (WMM) is used to determine the current MV at a location and to calculate the future MV for use in procedure design and publication. The model estimates the MV at any location and day within the five-year validity window of the model. For example, the WMM released in December 2009 provides MV values for all locations for January 1, 2010 through December 31, 2014. The nearest future epoch year value calculated using that model would be specified as 2015, and the MV based on the December 31, 2014 value, except as indicated in paragraph 2-5-3.c. The assigned MV is listed as using the 2015 epoch year even when the value is associated with a date earlier in the validity period of the model.

b. Standard MV limits for airports and NAVAIDs. When the difference between the MV of record and the nearest future epoch year value of any NAVAID, or the assigned airport MV of record, will exceed three (3.0) degrees [five (5.0) degrees for VORs and VORTACs], the MV of record must be changed to the nearest future epoch year value and applied to airport reference point (ARP) and all on-airport NAVAIDs. Consider implementing the change earlier in cases where revisions of multiple procedures are required for other reasons, such as when other nearby airports are being updated or when weather, or other factors, would preclude the change being accomplished at the time the MV would actually exceed three (3.0) degrees. Off-airport NAVAIDs must be maintained within three (3.0) degrees [five (5.0) degrees for VORs and VORTACs], especially when they support instrument procedures.

2-5-3. Guidelines for Magnetic Variation Revisions. › g. Standard rules for applying MV to true radials, bearings, courses,…

c. MV limits for airports with SA CAT I, SA CAT II, or CAT II/III approach procedures. The intent is to keep the NAVAID and procedure MV closely aligned with the actual (as predicted by the WMM) MV at the airport. Maintain the assigned MV value for these airports, NAVAIDs, and procedures within ±1 degree of the current computed airport MV. At these airports, do not apply future epoch year MV values that would create a rounded whole number MV of record that exceeds one (1.0) degree of the current, computed airport MV. The onedegree tolerance effectively applies to the airport MV, the MV for NAVAIDs on the airport, and the MV for all RNAV procedures required to use the aerodrome MV as indicated in paragraph 2- 5-3.g(2). An “on airport” VOR or NDB at CAT II/III airports may exceed the one-degree tolerance, but must not exceed five (5.0) degrees from the airport MV of record.

d. Runway magnetic azimuth must be based on the assigned MV of record for the airport.

Note: Runway headings and MV are published on airport diagrams to allow pilots to obtain a compass bearing check during runway line-up. These values may differ from the airport MV of record, and are not used in procedure design.

e. MV for RADAR facilities. The ARP MV of record at the designated controlling airport may be used in determining the MV applied to all airports, NAVAIDs, and RADARs serving the terminal areas.

f. Coordination of MV updates. MV updates are coordinated by the OSG-FPT. Factors to consider include when the MV will exceed the required tolerance, whether the navigational aid is isolated, or in close proximity to one or more other NAVAIDs, whether on-airport or off-airport, and the impact on instrument flight procedures.

g. Standard rules for applying MV to true radials, bearings, courses, and headings.

(1) Ground-based NAVAIDs and radar.

(a) Utilize the NAVAIDs MV of record to determine magnetic tracks, and courses.

(b) Runways that have SA CAT II or CAT II/III approach procedures must have the charted final course conforming to the runway heading updated when the difference is greater than one (1.0) degree.

(2) RNAV.

(a) Instrument approach procedures (IAPs)/DPs/STARs, including GLS. MV is applied to any track/course used in an RNAV instrument procedure and it must be the MV of the aerodrome of intended landing or departure. When a SID/STAR serves multiple airports, a primary airport must be selected for the MV that will be used. For STARs, see paragraphs 4-5-12 and 4-5-13 for documentation requirements.

(b) Holding on RNAV IAPs/DPs/STARs. To determine the magnetic track/course, apply the published MV of the aerodrome, or the en route VOR or NDB assigned

variation when proceeding “to” the NAVAID used as part of a procedure/holding pattern fix to the procedure true track/course.

(c) Holding on RNAV routes or stand-alone. For RNAV only holding patterns not associated with an instrument procedure or a VOR or NDB used as the holding fix, determine the MV by using the magnetic declination (variation) for the holding fix latitude/longitude. This information may be calculated using the WMM.

(3) Diverse Vector Area (DVA). Use airport MV of record when defining DVA heading limitations.

Section 2-6. Notices to Airmen (NOTAMs) › 2-6-2. United States NOTAM System.

Section 2-6. Notices to Airmen (NOTAMs)

2-6-1. General. NOTAMs provide timely knowledge to flyers and other aviation interests regarding information or conditions which are essential to safety of flight. NOTAMs pertaining to IFPs are effective upon issuance and must remain in effect until the pertinent aeronautical charts are amended or the condition requiring the NOTAM ends. Management and operational guidance is contained in Order JO 7930.2, Notices to Airmen (NOTAMs).

2-6-2. United States NOTAM System. The United States NOTAM System (USNS) has been established to provide aviators with the current status of the NAS. This system is under the purview of FAA’s Air Traffic Organization, Vice President of Mission Support Services, Aeronautical Information Services (AJV-A). The following describes the use of FDC NOTAMs and related issues due to IFP changes, NAVAID outages, and government aeronautical chart corrections.

a. FDC NOTAMs are normally used to disseminate safety of flight information relating to regulatory material as well as to all IFPs and are issued through the United States NOTAM Office (USNOF). See Order JO 7930.2, Chapter 7, for specific FDC NOTAM policy.

b. NOTAM Ds. See Order JO 7930.2, Chapter 4, for NOTAM D policy.

2-7-2. Flight Technologies and Procedures Division’s Action. › b. Preliminary reviews may be conducted by the Flight Technologies and…

Section 2-7. Quality/Standardization of Instrument Flight Procedures

2-7-1. Aeronautical Information Services’ Action.

a. Aeronautical Information Services is responsible for the accuracy of instrument flight procedures it develops, and for establishing and conducting a system of quality control that ensures such procedures conform to applicable criteria, standards, and policy.

b. Aeronautical Information Services’ system of quality control must ensure that all flight procedures and NOTAMs are of a professional quality that will not require corrections or changes following release.

c. When unusual circumstances exist, for which policy is not clear or is nonexistent, request a policy determination from the Flight Technologies and Procedures Division prior to submission for publication. Appropriate instructions will be issued as necessary.

d. Instrument charts produced by Aeronautical Information Services must be reviewed for variations from information submitted for publication and for clarity of the graphic portrayal. Charting errors detected must be immediately corrected by NOTAM [see Section 2-6]. Charts that do not clearly portray the procedure(s) as designed should be referred to the Flight Technologies and Procedures Division and Aeronautical Information Services, Quality Assurance and Standards Team, with recommendations for charting improvements.

2-7-2. Flight Technologies and Procedures Division’s Action.

a. The Flight Technologies and Procedures Division is responsible for providing oversight of non-FAA service provider's Quality Assurance (QA) process to determine conformance with applicable criteria, standards, and policy.

b. Preliminary reviews may be conducted by the Flight Technologies and Procedures Division upon request of a non-FAA Service Provider.

2-8-2. Frequency of Periodic Reviews. › c. The frequency requirement for a periodic review is considered…

Section 2-8. Periodic Review of Instrument Flight Procedures

2-8-1. General. Conduct periodic reviews of all IFPs to ensure requirements for obstacle clearance, navigational guidance, safety, and practicality are met. Use reviews to determine if amendments to IFPs are needed to comply with changes to design criteria and policy. These changes include, but are not limited to, such items as obstacle assessment areas (to ensure proper OE actions are being administered), procedure naming, requirements to add/remove/modify chart notes, etc. Consideration must also be given to the impact of OEs, F&E, and AIP projects pertinent to the procedure review process. When directed by Flight Standards, immediately comply with changes to criteria.

2-8-2. Frequency of Periodic Reviews.

a. Review IFPs at least once every two or four years as applicable. Refer to Table 2-8-1 to determine the applicable frequency.

Table 2-8-1. Frequency of Periodic Review

Procedure Type Frequency IAP – final (including visual area), circling, and missed approach segments 2 years IAP – All other segment/areas not subject to 2 year review 4 years ODP 2 years DVA 2 years SID 4 years STAR 4 years Airways, airways segments, routes 4 years

b. Periodic reviews must be completed within the specified frequency from the most recent of the following:

(1) The “EFFECTIVE DATE” indicated on the applicable 8260-series form of an original procedure. Special procedures documented on Form 8260-7A utilizes the signatureapproved date. The date is the trigger for periodic maintenance.

(2) The “EFFECTIVE DATE” indicated on the applicable 8260-series form for the most recent full amendment of a procedure. Do not use abbreviated amendment dates or P-NOTAM dates for calculating periodic review requirements. Special procedures documented on Form 8260-7A utilizes the signature-approved date. The date is a trigger date from periodic maintenance.

(3) The documented completion date for the most recent periodic review.

(4) When deemed necessary, and in the interest of safety or for other proper justification, make more frequent reviews.

c. The frequency requirement for a periodic review is considered satisfied if it occurs in the period from one month prior to one month after the month in which the periodic review is due. For example, if the periodic review is due in July, the window is June 1 to August 31. If the window is met, the month it is due remains unchanged. However, if the periodic review occurs

2-8-3. Conducting Periodic Reviews. › n. Fixes.

outside of the specified window, the next review is due in the month in which the review was actually completed.

2-8-3. Conducting Periodic Reviews.

a. Review for any changes required, including procedure naming, an adjustment to visibility minimums, a flight altitude, descent gradient, and/or climb gradient.

b. Ensure approach/departure minimums meet criteria.

c. When applying the new circling area to a given procedure, evaluate all IAPs at the airport to ensure uniformity of circling minima. New circling criteria dimensions may require a revision to controlled airspace boundaries.

d. Verify the adequacy of an approach procedure’s minimum safe altitude (MSA). Do not make an IFP amendment solely to correct an MSA unless the MSA provides less than 950 feet of obstacle clearance.

e. When reviewing ODPs, ensure all SIDs to the same runways are also reviewed for any impact due to ODP changes.

f. When reviewing SIDs, ensure the takeoff minimums are consistent with other SIDs from the same runway when the initial routings prior to a turn are identical.

g. Airways, airway segments, and routes. Verify controlling obstacles and ensure that authorized altitudes meet obstacle clearance requirements. Use current en route charts as airway checklists.

h. Ensure procedures are contained within controlled airspace as prescribed in Chapter 5.

i. Review facility restrictions to determine impact to associated flight procedures. Take particular care to evaluate unpublished procedures such as off-airway, direct, and substitute routes.

j. Verify current magnetic variation values.

k. Review IFP forms for conformance to current standards. Check published IFP charts and text for correct portrayal of source data.

l. Verify the validity of existing waivers and cancel waivers no longer required.

m. To avoid proliferation of conflicting data on IFPs at an airport, all other procedures at the airport must be considered for possible impact and revision(s).

n. Fixes.

(1) Review all fixes in conjunction with the associated IFPs, airways, or routes [see Section 2-10]. Ensure that Form 8260-2, Radio Fix and Holding Data Record, entries for facility type,

2-8-5. Reviewing Organization Responsibilities. › c. If the results of the review indicate a need to amend an IFP,…

class, radial/course/bearing, distances, and charting requirements are correct. Verify holding requirements and controlling obstructions.

(2) Cancel fixes and holding which are no longer needed.

2-8-4. Documentation of Periodic Reviews.

a. Document periodic reviews to show the date when the review was conducted.

b. Document a synopsis of review results based on items mentioned in paragraph 2-8-3, specifying what action, if any, was taken.

c. Document all required changes, including criteria/policy and how they affect the current procedure during the review.

d. The method (spreadsheet, memorandum, etc.) used to document the periodic review is at the discretion of the procedure development authority.

Example: NEED TO APPLY CURRENT RULE OF VEGETATION/AAO TO ALL RUNWAYS. RWY 4: REQUIRES A TEXTUAL DEPARTURE PROCEDURE CLIMB HEADING 040.51 TO 1500 BEFORE TURNING LEFT DUE TO NEW OBSTRUCTION IN DIVERSE A AREA 55- 000821. RWY 22: SATISFACTORY. RWY 9: SATISFACTORY. RWY 27: PREVIOUSLY DOCUMENTED ICA OBSTRUCTION IS NOT IN THE DATA BASE. MAP STUDY SHOWS IT APPEARS TO BE STILL THERE AND ORS TEAM CONTACTED. OBS EVALUATED AT 4D, WHICH REQUIRES NEW CLIMB GRADIENT. TRUE COURSE ON AIRNAV APPEARS TO BE INCORRECT AND EMAIL SENT TO FPT TO VALIDATE. NOTAM ISSUED FOR RWY 4 DIVERSE DEPARTURE AND RWY 27 CLIMB GRADIENT. 2-8-5. Reviewing Organization Responsibilities.

a. Establish and maintain a system of control to ensure that reviews are accomplished.

b. Take remedial action by NOTAM or revised 8260-series form.

c. If the results of the review indicate a need to amend an IFP, coordinate proposed changes (including Notices to Airmen) in advance with the applicable OSG-FPT. The FPT will coordinate with airport management, the IFP Validation Team, and servicing air traffic control facility when application of new or revised criteria raises minimum procedure altitudes and/or increases takeoff/landing minimums. The FPT must be provided a copy of the documentation required by paragraph 2-8-5.

2-9-2. Use of Universal Integrated Communications (UNICOM). › d. Weather information. Only if there is no FAA control tower or Flight…

Section 2-9. Communications and Weather

2-9-1. Communications Requirements. Order 8200.1, Chapter 8, defines communication tolerances and flight inspection procedures. Even though gaps in navigation course guidance may be approved, reliable communications coverage over the entire airway or route segment at minimum en route IFR altitudes must be available.

a. MEAs or MAAs are predicated upon continuous approved communications capability for the entire designated segment. All available resources must be explored before restricting the use of altitudes of an airway or route due to a lack of acceptable communications coverage. Coordination must be effected with ATC for determination of the acceptability of communications coverage in a particular area.

b. Mandatory communications with the appropriate ARTCC are not required; communications with other ATC facilities are allowable. Where necessary, in order to provide direct communications with a center, appropriate recommendations for a peripheral site should be made.

c. Communications requirements for non-14 CFR part 95 routes certified for a particular air carrier are the responsibility of appropriate Flight Technologies and Procedures Division representative.

2-9-2. Use of Universal Integrated Communications (UNICOM). UNICOM may be used to satisfy the communications requirements of Order 8260.3, Chapter 1; however, there are limitations on its use that must be considered. According to Federal Communications Commission (FCC) rules and regulations, part 87, Subpart C, UNICOM stations are not authorized for ATC purposes other than the relay of the following information between the pilot and controller:

a. Revision of proposed departure time.

b. Time of takeoff, arrival, or flight plan cancellation.

c. ATC clearances provided a LOA is consummated by the licensee of the advisory station (UNICOM) with the FAA.

d. Weather information. Only if there is no FAA control tower or Flight Service Station, or during periods when an FAA unit is not in operation. Direct transmission of approved altimeter setting to the pilot is authorized provided the procedure states an alternate course of action if UNICOM is not contacted.

Note: FCC regulation places the responsibility for the LOA on the licensee, but Order JO 7210.3 suggests that an ATC facility prepare the agreement. A communication capability between the UNICOM station and ATC is necessary to meet requirements of Order 8260.3, Chapter 1.

Section 2-9. Communications and Weather › 2-9-3. Automatic Altimeter Setting and Weather Reporting Systems.

2-9-3. Automatic Altimeter Setting and Weather Reporting Systems. Approved devices for automatically reporting altimeter settings and weather may be used to satisfy the requirements of Order 8260.3, Chapter 1. Special notes will be required on the approach charts. Examples of standard notes can be found in paragraph 8-6-11.h.

2-10-3. Requests for Navigational Fixes. › a. Form 8260-2 is the vehicle used to transmit requests for the…

Section 2-10. Navigational Fixes

2-10-1. General. Criteria for navigational fixes are contained in Order 8260.3, Chapters 2 and 15. When using a VORTAC or VOR/DME, fixes should be defined by DME from the facility providing course guidance in addition to radials or course intersections.

2-10-2. Reporting Points. Reporting points are established for use by the ATO in the movement and separation of aircraft. Reporting points are divided into two categories, which are:

a. Compulsory reporting points are designated by regulation and; therefore, require rulemaking action. It is the ATO’s responsibility to initiate airspace rule making action for the designation of compulsory reporting points.

b. Non-compulsory reporting points may be established by the ATO without the requirement for rule making action.

2-10-3. Requests for Navigational Fixes.

a. Form 8260-2 is the vehicle used to transmit requests for the establishment, revision, or cancellation of navigational fixes, holding patterns, and/or reporting points. All fix requests must be processed to Aeronautical Information Services, AJV-A3, for publication in the NFDD. See Section 8-5 and Appendix D for guidance on filling out Form 8260-2 and requesting additions/deletions to existing fixes that are under the control of a different office of primary responsibility (OPR).

(1) Aeronautical Information Services is responsible to initiate and maintain Form 8260-2 for those navigational fixes that are required for the development of all 14 CFR part 95 routes and those 14 CFR part 97 FAA-developed and maintained instrument procedures for which they are responsible.

(2) The requesting ATC facility is responsible for initiating and maintaining (i.e., update the form and process changes when they occur) a Form 8260-2 on those ATC operationally required navigational fixes including CVFPs. The requesting ATC facility is responsible for coordinating with adjacent ATC facilities as deemed necessary, and then processing the form through the appropriate Service Center OSG-FPT to Aeronautical Information Services. A Form 8260-2 is submitted with a request for area navigation visual flight procedures (RVFPs) also require OSG-FPT approval and submission to Aeronautical Information Services.

(3) “Service Providers,” also referred to as “non-FAA Service Providers,” of instrument flight procedures are responsible for initiating and maintaining the Form 8260-2 for those fixes that will not be used by the FAA on other instrument or air traffic procedures. These Form 8260-2s must be submitted to the Flight Technologies and Procedures Division with the instrument procedure package, prior to forwarding to Aeronautical Information Services. See Appendix D for processing guidelines when using an existing fix that has an FAA OPR.

(4) The military is responsible for initiating and maintaining the Form 8260-2 for those fixes that are for military operations that are not a part of a 14 CFR part 95 route and/or 14 CFR part 97 instrument flight procedures.

2-10-4. Naming Navigational Fixes. › a. All navigational fixes must be named except as noted below. Named…

(5) Transferring OPR to Aeronautical Information Services is required when a fix used solely for ATC purposes or in a non-FAA Service Provider-developed procedure, or military fix is re-designated for use in an FAA-developed instrument flight procedure. When this occurs, Aeronautical Information Services will first coordinate with the current OPR, then generate a new Form 8260-2 showing them as the OPR for that fix.

(6) All OPRs are responsible for coordinating any fix/holding pattern changes with all organizations that are responsible for procedures identified under “Fix Use.” In order to prevent extensive, costly, and time consuming procedure changes, fix movement and/or changes to holding patterns, or cancelations must not occur until all affected fix users have agreed to the change.

Note: When establishing effective dates for changes of a Form 8260-2 that also affects Special IFPs, consideration must be given to processing times required to update and distribute these revised procedures to the users/operators. The processing time for Special IFPs is considerably longer than the time required for processing the same change that affects public IFPs due to the special procedure approval and operator authorization processes. If Aeronautical Information Services is the OPR, they must coordinate the effective date of an amended Form 8260-2 utilized in special instrument procedures with the appropriate Flight Technologies and Procedures Division representative, prior to processing through Aeronautical Information Services, to minimize the impact on the users/operators.

b. Every effort should be made to use established fixes or NAVAIDs wherever possible in lieu of creating new fixes. Do not create a new waypoint over an existing fix or NAVAID (including a stand-alone DME facility). Do not use any VOR/DME or VORTAC where the VOR coordinates and DME source coordinates are not identical to 0.01 second in RNP AR procedures. Additionally, when establishing new fixes that will be placed on Victor Airways or Jet Routes solely to support RNAV instrument procedures, define them using crossing radials or a DME fix. Additionally, if ATC uses an existing fix for ATC purposes, Form 8260-2 must be updated accordingly [see paragraph 8-5-2.j].

2-10-4. Naming Navigational Fixes. In order to satisfy the requirements of the FMS, the following applies for all procedures:

a. All navigational fixes must be named except as noted below. Named fixes collocated with a facility retain the same name as the facility [see Order JO 7400.2]. Navigational fix names consist of a five-letter combination and are obtained from Aeronautical Information Services. Unless otherwise stated in this section, “fix” means a non-RNAV fix, RNAV waypoint, or computer navigation fix (CNF). Determine fix names as follows:

(1) Fixes not to be named.

(a) VDPs.

(b) Radar fixes used on ASR and/or PAR procedures.

(c) MAP at LTP (e.g., DME used at the MAP, FAF to MAP timing where the MAP is the LTP).

2-10-4. Naming Navigational Fixes. › b. Coordinate with Aeronautical Information Services and the…

(d) Lead radials or lead bearings.

(e) COPTER RNAV. PinS approach annotated “PROCEED VISUALLY”: Any ATD fix located between the MAP and visual segment descent point.

(2) Pronounceable fix names. Except as stated in paragraph 2-10-5.a(3), all fix names serving any IFP must be pronounceable. Additionally, a non-RNAV Glidepath Intercept Point (GPIP) located prior to the non-precision FAF on the same chart, by one nautical mile (NM) or greater, must be a pronounceable five-letter name. This naming requirement also applies to the GPIP of a stand-alone vertically-guided procedure absent of non-precision minima on the same chart. These instances do not require documentation of fix makeup in the facility block(s) on the Form 8260-2.

(3) Non-pronounceable fix names. The following fixes should be non-pronounceable:

(a) Fixes located between the FAF and MAP and No-FAF stepdown fixes. Exception: RADAR fix names must be pronounceable.

(b) MAP. Where the MAP is not at the LTP and FAF to MAP timing is not used.

(4) Computer navigation fixes. These are non-pronounceable fix names used solely to aid in computer navigation. CNFs are not used in ATC communications, are not flight-inspected, and do not employ any type of fix makeup. CNFs are charted in parentheses and must begin with the letters “CF” followed by three-consonants; e.g., “(CFWBG)”, except the letter “Y” is not used. Use a CNF for the following fixes:

(a) Non-RNAV MAP not at the LTP. Establish the MAP as a CNF only if FAF to MAP timing is used.

(b) RF center fixes.

(c) En route dog leg changeover points when required by paragraph 8-8-1.h.

Note: Earlier versions of CNF's include any combination of five-letter non-pronounceable fix names. Currently “charted” CNF’s that do not meet the “CFXXX” naming methodology must be converted to meet this standard when identified at the next periodic review or scheduled amendment, whichever occurs first.

(5) VFR waypoints. These are five-letter names beginning with “VP.” Do not use fixes beginning with the letters “VP” for flight procedures and/or routes.

Example: VPXYZ

b. Coordinate with Aeronautical Information Services and the appropriate ARTCC when a fix name change is required. Document the change on Form 8260-2. Canceled fix names must be reserved again at Aeronautical Information Services and cannot be re-used until six months after cancellation.

Section 2-10. Navigational Fixes › 2-10-6. Correlation of Navigational Fixes and Changeover Points.

c. When a fix must be moved, refer to Order JO 7400.2 for guidance on whether the five-letter name may be retained or must be changed.

2-10-5. Documenting Navigational Fixes.

a. All named civil and military fixes must be documented and approved on Form 8260-2. Chapter 8 of this order contains instructions for entering data and submitting Form 8260-2.

b. Military fixes are also maintained in the national database and are used to support the air traffic system. Therefore, the requirement to document and flight inspect military fixes must receive the same priority as the fixes that support civil procedures.

2-10-6. Correlation of Navigational Fixes and Changeover Points. The designation of navigational fixes should be directly related to COPs. Care should be taken to avoid designating navigational fixes that require the use of a facility beyond the COP. Figure 2-10-1 is an example of the proper and the improper method of designating a navigational fix in relation to COPs.

Note: These diagrams illustrate a problem encountered when handling intersections and changeovers. Make certain the entire complex is reviewed to prevent establishing procedures that are in conflict with the usability of the facilities involved.

Figure 2-10-1. Proper and Improper Method of

Section 2-10. Navigational Fixes › 2-10-8. Flight Inspection.

Designating a Navigational Fix

2-10-7. Minimum Reception Altitudes. At certain navigational fixes, VOR reception from an off course facility may not be adequate at the lowest MEA associated with the route segment. In such cases when the MRA at the fix is higher than the MEA for instrument flight, the MRA must be established for the fix and indicated on Forms 8260-2 and 8260-16. Once established, an MRA will not be revised unless the reception altitude is changed by 200 feet or more [see paragraph 8-5-2.g(3)(j)]. MEAs at each designated compulsory reporting point must not be lower than the MRA for the fix. Where necessary, dual MEAs may be utilized to meet this requirement.

2-10-8. Flight Inspection. After completion of required coordination, flight inspection personnel must confirm facility performance at the proposed operational altitudes. Where

Section 2-10. Navigational Fixes › 2-10-9. Maximum Authorized Altitudes.

possible, determinations are to be predicated on current facility performance records; otherwise, a flight check must be accomplished.

2-10-9. Maximum Authorized Altitudes. MAAs are procedural limits that might be determined by technical limitations or such other factors as limited airspace or compatibility with other procedures. Where MAAs are required in connection with the publication of flight procedures, they are included on Forms 8260-2 and 8260-16, or worksheets used to process the data [see also paragraph 8-5-2.g(3)(k)].

2-11-2. Obstacle Application and Data Sources. › c. Determine obstacle height additives required for traverse ways when…

Section 2-11. Obstacle Data

2-11-1. General. The primary purpose of obstacle evaluation is to determine how an object will affect instrument flight procedures. The evaluations provide accurate, consistent, and meaningful results and determinations only if procedure specialists apply the same rules, criteria, and processes during development, review, and revision phases. Do not conduct an obstacle evaluation for instrument flight procedure operations above 18,000 feet in the contiguous United States (CONUS) or above 23,000 feet for Alaska and Hawaii. This section also provides basic information regarding obstacle data sources; establishes the minimum accuracy standards for obstacle data and its application in the development, review, or revision of instrument procedures; and provides information on the application of the minimum accuracy standards. The minimum standards, regardless of the data source, are to be applied by instrument procedure specialists in all instrument procedure obstacle evaluations. See Order 8260.3 for obstacle definition.

Continue reading ↓ 120 of 862 passages shown