Order 8260.19J 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. 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.
This document is cancelled. Cancelled by 8260.19K. Check the official source before relying on it.
Text read by OCR from a scanned file (103 of 472 pages). Check the original, as some words may be misread.
FAA Order 8260.19J › TOC
Distribution: Electronic Distribution Initiated By: AFS-400
Effective Date:
06/01/2023
ORDER 8260.19J ORDER 8260.19J
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 Center, 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.
Caitlin Locke Acting Deputy Executive Director, Flight Standards Service
Table of Contents
ii
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-8
Section 1-2. Responsibilities … 1-9
1-2-1. Flight Standards Service … 1-9 1-2-2. Flight Technologies and Procedures Division … 1-9 1-2-3. Air Traffic Organization, Flight Program Operations … 1-10 1-2-4. Air Traffic Organization, Mission Support Services … 1-12 1-2-5. Individual … 1-15
Chapter 2. General Procedures … 2-1
Section 2-1. General … 2-1
2-1-1. Requests for Public-use Instrument Flight Procedures … 2-1 2-1-2. Air Traffic Letters of Agreement … 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 … 2-10
2-5-1. General … 2-10 2-5-2. Responsibilities … 2-10 2-5-3. Guidelines for Magnetic Variation Revisions … 2-15
Section 2-6. Notices to Air Missions … 2-18
2-6-1. General … 2-18 2-6-2. United States NOTAM System … 2-18
Section 2-7. Quality/Standardization of Instrument Flight Procedures … 2-19
2-7-1. Aeronautical Information Services’ Action … 2-19 2-7-2. Flight Technologies and Procedures Division’s Action … 2-19
iii
Section 2-8. Periodic Review of Instrument Flight Procedures … 2-20
2-8-1. General … 2-20 2-8-2. Frequency of Periodic Reviews … 2-20 2-8-3. Conducting Periodic Reviews … 2-21 2-8-4. Documentation of Periodic Reviews … 2-22 2-8-5. Reviewing Organization Responsibilities … 2-22
Section 2-9. Communications and Weather … 2-23
2-9-1. Communications Requirements … 2-23 2-9-2. Use of Universal Integrated Communications … 2-23 2-9-3. Automatic Altimeter Setting and Weather Reporting Systems … 2-24
Section 2-10. Navigational Fixes … 2-25
2-10-1. General … 2-25 2-10-2. Reporting Points … 2-25 2-10-3. Requests for Navigational Fixes … 2-25 2-10-4. Naming Navigational Fixes … 2-26 2-10-5. Documenting Navigational Fixes … 2-28 2-10-6. Correlation of Navigational Fixes and Changeover Points … 2-28 2-10-7. Minimum Reception Altitudes … 2-29 2-10-8. Flight Inspection … 2-29 2-10-9. Maximum Authorized Altitudes … 2-30
Section 2-11. Obstacle Data … 2-31
2-11-1. General … 2-31 2-11-2. Obstacle Application and Data Sources … 2-31 2-11-3. Obstacle Data Accuracy Standards … 2-32 2-11-4. Accuracy Standards Application … 2-33 2-11-5. Controlling Obstacles … 2-34 2-11-6. Datums … 2-39
Section 2-12. Waiver of Standards/Approval Requests … 2-41
2-12-1. General … 2-41 2-12-2. Waiver Processing … 2-41 2-12-3. Waivers for Special Instrument Approach Procedures … 2-42 2-12-4. Safety Management System Requirements … 2-42 2-12-5. Periodic Review of Waivers … 2-42 2-12-6. Cancellation … 2-43 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
iv
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-9
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 and Minimum IFR Altitude 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 … 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 … 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 … 4-9
4-4-1. General … 4-9 4-4-2. Diverse Vector Area … 4-9
Section 4-5. Standard Terminal Arrival … 4-10
4-5-1. General … 4-10 4-5-2. STAR Development and Charting … 4-10 4-5-3. PBN STARs … 4-13 4-5-4. Procedure Depiction and Processing … 4-15
v
4-5-5. Waivers/Approval Requests … 4-16 4-5-6. STAR NOTAMs … 4-16 4-5-7. STAR Amendments … 4-16 4-5-8. Reviews … 4-17 4-5-9. Cancellation … 4-17 4-5-10. Military STAR Procedures … 4-17 4-5-11. Roles and Responsibilities … 4-18 4-5-12. Preparation of Form 8260-17.1, Standard Terminal Arrival … 4-21 4-5-13. Preparation of Form 8260-17.2, STAR … 4-49
Section 4-6. RNAV Procedure Development … 4-59
4-6-1. General … 4-59 4-6-2. RNAV Approach Procedure Design … 4-59 4-6-3. Developing RNAV Waypoint … 4-61 4-6-4. RNAV Leg Types … 4-62 4-6-5. RNAV Leg Type Descriptions … 4-63 4-6-6. Final Approach Segment Data … 4-64 4-6-7. Remote Altimeter Setting for Baro-VNAV … 4-64 4-6-8. Critical Temperature … 4-64 4-6-9. DME/DME Screening Model … 4-64 4-6-10. Additional Documentation (Baro-VNAV, GBAS, and/or WAAS IAPs) … 4-65 Chapter 5. Airspace … 5-1
Section 5-1. Obstruction Evaluation … 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. Service Provider Actions … 5-2 5-2-4. Terminal Airspace … 5-3
Section 5-3. Airport Airspace Analysis … 5-42
5-3-1. General … 5-42 5-3-2. Service Center OSG FPT/Flight Standards Input (Airports and Heliports) … 5-42 5-3-3. Flight Standards Performs Flight Safety Review (Airport Proposals) … 5-42 5-3-4. Service Center OSG FPT Evaluation/Comment on Airport Proposals … 5-42 5-3-5. Alterations of Airports or Heliports … 5-43 5-3-6. Deactivation of Airports or Heliports … 5-43 5-3-7. Assistance in Zoning Problems … 5-44
Section 5-4. Restricted Areas … 5-45
5-4-1. General … 5-45 5-4-2. Letter of Procedures … 5-45
Section 5-5. Establishment, Relocation, or Discontinuance of Radio Navigation Aids … 5-46
5-5-1. Criteria and Guidelines … 5-46 5-5-2. OSG FPT Action … 5-46 5-5-3. Flight Standards Action … 5-46
vi
Chapter 6. Military Procedures … 6-1
Section 6-1. … 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 for New ILS Installations … 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 Support … 7-15
7-8-1. Support … 7-15
Section 7-9. Heliport Planning … 7-16
7-9-1. General … 7-16 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 Instrumen Approach Procedures … 8-11 8-3-4. Revisions to IFPs … 8-12
vii
8-3-5. Aeronautical Information Services Review of SIAPs and Charts … 8-17 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 … 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 … 8-25
8-5-1. Introduction … 8-25 8-5-2. Preparation of Form 8260-2 … 8-26
Section 8-6. Completion of FAA Forms 8260-3/4/5/7A … 8-36
8-6-1. General … 8-36 8-6-2. Basic Information … 8-36 8-6-3. Terminal Arrival Area … 8-39 8-6-4. Terminal Routes … 8-41 8-6-5. Radar Terminal Area Maneuvering Sectors and Altitudes … 8-44 8-6-6. Missed Approach … 8-44 8-6-7. Profile - Lines 1 through 8 … 8-49 8-6-8. PBN Requirements Notes … 8-55 8-6-9. Equipment Requirements Notes … 8-59 8-6-10. Notes … 8-60 8-6-11. Additional Flight Data … 8-71 8-6-12. Minimums … 8-76 8-6-13. Changes and Reasons … 8-92 8-6-14. Coordinated With … 8-92 8-6-15. Submitted By … 8-93 8-6-16. Flight Checked By … 8-93 8-6-17. Developed By … 8-93 8-6-18. Recommended By … 8-93 8-6-19. Approved By … 8-93 8-6-20. FAS Data Block Information … 8-94
Section 8-7. Standard Instrument Approach Procedure Data Record … 8-95
8-7-1. Preparation of Form 8260-9 … 8-95
Section 8-8. Transmittal of Airways/Route Data Record … 8-106
8-8-1. Preparation of Form 8260-16 … 8-106
Section 8-9. SCP and SOIA Procedure Attention All Users Page … 8-131
8-9-1. Attention All Users Page … 8-131 8-9-2. Site Implementation Team … 8-131 8-9-3. AAUP Preparation … 8-131 8-9-4. AAUP Processing … 8-131 8-9-5. AAUP Publication … 8-131 8-9-6. Forms Processing … 8-132 8-9-7. Title Line … 8-132 8-9-8. Text … 8-133 8-9-9. Administrative Information … 8-133 Appendix A. Administrative Information … A-1
Appendix B. Flight Procedures References … B-1
viii
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 … E-1
Appendix F. ILS and RNAV Standard Instrument Approach Procedure … F-1
Appendix G. Radar Standard Instrument Approach Procedure … G-1
Appendix H. Standard Instrument Approach Procedure … H-1
Appendix I. Special Instrument Approach Procedure and Authorization … I-1
Appendix J. Standard Instrument Approach Procedure … J-1
Appendix K. FAS Data Block Cyclic Redundancy Check Requirements … K-1
Appendix L. Instrument Flight Procedures Lifecycle … L-1
1-1-5. Explanation of Changes. › b. Table of Contents.
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-2. Audience. All personnel who are responsible for Instrument Flight Procedure (IFP) development and/or evaluation.
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.19I, Flight Procedures and Airspace, dated 06/29/2020, is canceled.
1-1-5. Explanation of Changes. Significant areas of new direction, guidance, policy, and criteria as follows:
a. General.
(1) Updated references to Order “JO” 7930.2 changing to “Order” 7930.2 in all references.
(2) Updated gender-neutrality references throughout the document.
(3) Changed Notice to Airmen (NOTAM) to Notices to Air Missions (NOTAM) throughout the document.
(4) Updated references to Aeronautical Information Services to “service provider(s)” to be inclusive of non-FAA service provider(s) where both the FAA service provider and the non-FAA service providers are to accomplish instrument flight procedure (IFP) coordination and other tasks relating to National Airspace System (NAS) requirements and procedures processing. Requires all service providers (FAA and non-FAA) to accomplish coordination to ensure aeronautical databases, airspace, chart publications and other aeronautical procedural data and information are provided in a timely manner and aligns procedure data with NAS publication dates, database, and charting requirements. Aeronautical Information Services is considered a service provider.
(5) Updated FAA procedure forms, documentation and examples removing airport name field from forms to reduce the number of amendments generated by airport name changes.
b. Table of Contents. Updated page and paragraph numbers.
c. Chapter 2.
(1) Paragraph 2-2-2. Updated reference to Aeronautical Information Publication (AIP) to avoid confusion with Airport Improvement Program.
d. Chapter 4. › (7) Paragraph 4-5-3.
(2) Paragraph 2-5-2.a(3). Added “e.g.,” to RNAV ATS route examples for route maintenance activities.
(3) Paragraph 2-8-2.c. Clarified and simplified periodic review requirements.
(4) Paragraph 2-11-2.c. Removed “Additional Flight Data” and replaced it with “General Remarks” section, to correct an error in previous versions.
(5) Paragraph 2-11-3.b(2). Added helicopter PinS initial departure fix (IDF) flat surface area to accuracy evaluation standard.
(6) Paragraph 2-11-3.b(3). Added helicopter PinS departure area beyond IDF flat surface area to accuracy evaluation standard.
(7) Paragraph 2-11-6. Added Lateral Performance (LP) procedure to list of procedures, which require FAS data block information, inadvertently left off in previous versions.
d. Chapter 4.
(1) Paragraph 4-1-3.a. Clarified procedural airspace requirements and documentation applicable to all procedures.
(2) Paragraph 4-1-3.d. Combined all details into one sentence and added a Note for publishing some private special procedures prior to obtaining the optimum configuration of controlled airspace, on a case-by-case basis with Flight Standards approval.
(3) Paragraph 4-1-3.e. Removed reference to special procedures as airspace is required to be studied and the FAA will issue a determination if airspace will be designated or not. Clarified when note is used.
(4) Paragraph 4-1-7.c. Corrected reference to Order 8260.3 Table 10-1-1. Added reference to paragraph 8-3-4.f(2) parameters.
(5) Figures 4-5-1 through Figure 4-5-5. Replaced obsolete versions of forms. Removed the airport name and replaced with the airport ID field. Under communications, removed airport name and replaced with the airport ID.
(6) Paragraph 4-5-2.v. Added example of procedural data note “CROSS BUFLO AT 250 KIAS.”
(7) Paragraph 4-5-3. Standardized all STAR PBN Requirements Notes, Equipment Requirements Notes and Procedural Data Notes to align with Order 8260.46, Departure Procedures
g. Chapter 8. › (4) Paragraph 8-3-4.d(2). Removed names of airports from notes,…
(DP) Program, and Standard Instrument Approach Procedures to provide information for adding/documenting PBN requirements on charts.
(8) Paragraph 4-5-4.a. Added instruction for the service provider to add turn expansion areas if not depicted by automation.
(9) Paragraph 4-5-12.f. Added approach control to communications for automatic charting, no need to document as it has become part of chart process.
(10) Paragraph 4-5-12.g. Removed airport names, only using Airport identifier (ID) (LOCATION ID) and ICAO ID, when available. No longer requires airport name(s) on STARs Forms to prevent amendments for only airport ID changes.
(11) Paragraph 4-5-13. Removed text, it was mistakenly inserted and a duplicate of previous paragraph and now part of paragraph 4-5-12.j.
e. Chapter 5.
(1) Paragraph 5-2-1. Removed “special” reference since special procedures require airspace study in accordance with Order JO 7400.2.
(2) Paragraph 5-2-3. Changed many references to Aeronautical Information Services and renamed to include all service providers to conduct airspace coordination.
(3) Paragraph 5-2-4.k. Added clarification for amendments with airspace changes.
f. Chapter 7.
(1) Section 7-9. Added Heliport Planning requirements section.
(2) Paragraph 7-9-1. Added section for helicopter planning. Outlined requirements for heliport development plan for Airport Improvement Projects, heliports, and landing areas. This clarifies procedural requirements for approaches at certain types of airports.
g. Chapter 8.
(1) Paragraph 8-2-1.a. Added reference to Order 8260.26, Establish Cutoff Dates for Submission of Instrument Flight Procedures.
(2) Paragraph 8-2-4.b(3). Added remote location ID in notes, shorting the need for the whole airport name to be in the chart note.
(3) Paragraph 8-3-4. Removed “JO” from Order 7930.2.
(4) Paragraph 8-3-4.d(2). Removed names of airports from notes, replaced with Location Identifier. (updated associated Table 8-3-1 entry). Shortened notes, improved understanding of specific location.
g. Chapter 8. › (18) Paragraphs 8-6-10.e and 8-6-10.f. Changed “LOCATION” in several…
(5) Paragraph 8-4-1.b. Removed the airport name and replaced with the airport identifier (LOCATION ID) and ICAO ID field.
(6) Figure 8-4-1, Form 8260-1 Item 1. Removed the airport name and replaced with the airport identifier (LOCATION ID) and ICAO ID field if required.
(7) Paragraph 8-5-2.t. Added coordination requirements for changing Form 8260-2, outlining required coordination with subsequent users.
(8) Paragraph 8-5-2.u. Updated Distribution field with alternate options for electronic distribution. Removed Army distribution per request.
(9) Paragraph 8-6-2.a. Removed the former paragraph a (all paragraph letters changed) which was inadvertently missed when the airport names were removed from the forms. Added requirements for adding ICAO ID, when available for locations outside contiguous United States.
(10) Paragraph 8-6-2.f(3). Added Copter PinS heliport clarifications for multiple heliports and heliport identification (IDs). Removed heliport names (using heliport ID) to avoid proliferation of obsolete data and amendments of procedures based solely on airport name changes. Added clarification that a Proceed Visual procedure may not serve multiple heliports.
(11) Paragraph 8-6-4.a(6)(c). Added reference to MAP for helicopter procedures, in lieu of LTP.
(12) Paragraph 8-6-4.a(6)(d) Note. Reworded to standardize chart requirements for multiple uses of FB and FO at the same fix.
(13) Paragraph 8-6-6.d(7). Removed the word “operations” to standardize.
(14) Paragraph 8-6-6.f. Changed wording, “rotary wing” to “helicopter.”
(15) Paragraphs 8-6-8 and 8-6-9. Reconfigured to standardize PBN Requirements Notes and Equipment Requirements notes.
(16) Paragraph 8-6-9. Combined the ILS/LOC (conventional procedure) notes with the required PBN notes to prevent repeating the same notes. Added note for feeder segment documentation for critical DMEs to equipment requirement notes.
(17) Paragraphs 8-6-9 through 8-6-19. Renumbered to 8-6-10 through 8-6-20 to accommodate the added paragraph for Equipment requirements notes. Updated references and links throughout document.
(18) Paragraphs 8-6-10.e and 8-6-10.f. Changed “LOCATION” in several paragraphs/notes to “LOCATION ID.” For locations inside the contiguous U.S., use the official FAA location identifier (ID) as derived from National Airspace System Resources (NASR) for <LOCATION ID>. For locations outside the contiguous U.S., use both the official FAA location (ID), as derived from NASR and the ICAO identifier (ID). Added example notes.
g. Chapter 8. › (34) Paragraph 8-6-11.k(1) and 8-6-11.k(2). Removed Airport/heliport…
(19) Paragraph 8-6-10.l. Added reference paragraph for copter missed approach notes and segment specific airspeed limitations.
(20) Paragraph 8-6-10.l(3). Added an additional copter speed note.
(21) Paragraph 8-6-10.l(4). Updated Planview note for copter missed approach that cancels speed restriction after a fix.
(22) Paragraph 8-6-10.l(5). Added “or desired airspeed,” to prevent the example of 90 KIAS from defining a limitation. Standardized notes.
(23) Paragraph 8-6-10.q. Removed the word “RNAV” in order to standardize and combine use of both RNAV and conventional copter approach identifications.
(24) Paragraph 8-6-10.q(1). Removed the word “GPS” in order to standardize and reference both RNAV and conventional copter approaches.
(25) Paragraph 8-6-10.q(1)(a). Added conventional approach identifications for copter ILS, LOC, VOR.
(26) Paragraph 8-6-10.q(1)(b). Added Copter PinS Procedure Identification to a heliport for Proceed Visually and Proceed VFR. Added evaluation, documentation, and maintenance requirements.
(27) Paragraph 8-6-10.q(1)(c). Identified documentation requirements and use of only one destination for proceed visually procedures.
(28) Paragraph 8-6-10.q(1)(c)i. Added that all VFR transition penetrations are to be documented. Added examples of required transition notes for descent from MAP.
(29) Paragraph 8-6-10.q(5). Added Additional Flight Data documentation of obstacles where a plan view note defines the difference between the VFR transition surface obstacles and the other surface penetrating obstacles.
(30) Paragraph 8-6-10.t(3). Added VFR procedures to a site that is not at an established airport used intermittently for proceed visually procedures and the required cautionary note, defines as special only procedure.
(31) Paragraph 8-6-11.e. Clarified documentation of the controlling obstacle for the 7:1 evaluation area.
(32) Paragraph 8-6-11.g(1). Added clarification when to use facility offset note.
(33) Paragraph 8-6-11.j(2). Added LP as was previously left out in error.
(34) Paragraph 8-6-11.k(1) and 8-6-11.k(2). Removed Airport/heliport names from Additional Flight Data documentation to prevent having to amend procedures based solely on airport name changes. Allows data alignment with authoritative source. Updated examples.
(35) Paragraph 8-6-11.l. Defined all obstacle penetrations for the VFR transition area are to be documented for Copter PinS procedures.
g. Chapter 8. › (51) Paragraph 8-7-1.c(2). Added airport ID (LOCATION ID) from NASR…
(36) Paragraph 8-6-11.m. Placed previous guidance back into order as VDP documentation for conventional procedures was removed in error.
(37) Paragraph 8-6-11.p. Added title description was added to existing paragraph.
(38) Paragraph 8-6-11.t. Removed and renumbered paragraph and the chart requirement to add circling icon/note.
(39) Paragraph 8-6-12.c. Added copter only procedure clarification for not requiring circling minimums.
(40) Paragraph 8-6-12k(1). Removed the word “splat” from the chart notes which was inadvertently inserted in the last version. Added clarifying language to insert symbol into note.
(41) Paragraph 8-6-12.k(2) Note. Clarified that the helicopter visibility reduction minimums note is not required when visibility results are greater than 1 SM/5000 RVR for the defined circumstances.
(42) Paragraph 8-6-12.m. Removed helicopter specific language.
(43) Paragraph 8-6-12.m(4). Updated language for Copter CAT II ILS Special Authorization Note.
(44) Paragraph 8-6-12.n. Added location ID to application notes to remove airport names and improve the notes.
(45) Paragraph 8-6-12.o(2)(i). Added chart note for heliports and unmarked landing areas without lights, CHART NOTE: “PROCEDURE NA AT NIGHT.”
(46) Paragraph 8-7-1.a. Removed airport name and replaced with LOCATION ID and ICAO ID, when available, outside the contiguous United States.
(47) Paragraphs 8-7-1.d(7) and 8-7-1.d(8). Removed reference to Order 8260.42 Chapter 2, due to pending cancellation.
(48) Paragraph 8-7-1.b(15). Added note clarification for airspace documentation.
(49) Paragraph 8-7-1.b(16). Clarified the airspace adjustment calculation above high terrain, noted here, corresponds with the required airspace adjustment (1000/1500) calculated in paragraph 5-2-4. The use of any adjustment less than required is not permitted, as improper airspace calculations will result.
(50) Paragraph 8-7-1.b(22)(b). Corrected form documentation for OCS slope to be entered into the OCS block vs. ROC.
(51) Paragraph 8-7-1.c(2). Added airport ID (LOCATION ID) from NASR clarification.
m. Appendix L. › (1) Removed the helicopter CRC section, combined with (previous)…
(52) Paragraph 8-7-1.d. Added documentation of VDA/TCH on Form 8260-9 for which procedure was computed when removed procedurally per flight inspection.
(53) Paragraph 8-8-1.c(6). Added paragraph for helicopter routes criteria information and documentation of the RNP value field.
(54) Paragraph 8-8-1.f(2). Removed the Y or N requirement for DMD/DME/IRU (D/D/I) documentation and replaced the D/D/I field on the form with the D/D/I MEA altitude. Clarified when segment remarks are required, added documentation examples.
(55) Paragraph 8-9-7.b. Removed airport name from form and directions to prevent proliferation of amendments solely for airport name changes.
(56) Figure 8-9-1. Removed the airport name and replaced with Airport ID.
h. Appendix A. Updated acronym table. Removed AIP – Aeronautical Information Publication (duplicate of AIP – Airport Improvement Program). Removed RDP – Reference Datum Point (not used in this order).
i. Appendix F. Removed outdated forms containing airport names and replaced them with the newest version.
j. Appendix I, Figure I-2. Removed Airport name field and airport name. Updated examples for Forms 8260-7A and 8260-7B.
k. Appendix J, Figures J-1 and J-2. Removed Airport name and updated examples of Form 8260-9.
l. Appendix K.
(1) Table K-1. Added helicopter specific references to standardize helicopter procedure FAS data information.
(2) Paragraph 4j, 4k, & 4l. Added reference to helipoint (center of TLOF), in lieu of LTP or FTP, as applicable.
(3) Paragraph 4m. Added helipoint and fictitious helipoint (FHP) for helicopter procedures.
(4) Paragraph 4o. Added Helicopter Crossing Height (HCH) for IFR helicopter procedures in lieu of TCH.
(5) Paragraph 4s. Added length offset value for helicopter PinS procedures.
m. Appendix L.
(1) Removed the helicopter CRC section, combined with (previous) Appendix K requirements into instructions for all procedures as needed.
Section 1-1. General › 1-1-6. Effective Date.
(2) Updated appropriate references.
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.
b. Flight Operations Group. This group is the principal element of the… › (3) Providing specific Operations Specification (OpSpec) language and…
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 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 Procedure Authorization, as required, through the Procedures Review Board (PRB).
(3) Providing specific Operations Specification (OpSpec) language and inspector guidance regarding low visibility operations (CAT II/III) procedures and minima.
1-2-3. Air Traffic Organization, Flight Program Operations. › d. Flight Research and Analysis Group. This group is the principal…
(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 Air Missions (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.
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 Air Traffic Control (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). Other 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 Centers 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 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 Program Operations 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 Inspection Tracking 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) 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.
(2) Aeronautical Information Services is the principal element… › (a) Establishing the U.S. position for Aeronautical Information Manual…
1-2-4. Air Traffic Organization, Mission Support Services
a. Aeronautical Information Services is responsible for managing the agency’s program 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.9, 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-series 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:
(a) Establishing the U.S. position for Aeronautical Information Manual (AIM) and Aeronautical Information Services through the International Civil Aviation Organization (ICAO).
b. Aeronautical Information Services is also responsible for the… › (11) Providing international charting support to selected foreign…
(b) Collecting, validating, verifying, managing, and disseminating as-built obstacle data reported under 14 CFR part 77.
1. Providing the publicly-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 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) 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.
(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.
d. Service Center, Operational Support Group, Flight Procedures Teams… › (8) Determining the necessity for environmental impact studies as…
(13) Analyzing obstruction evaluations to determine the effects on current and planned instrument flight operations, minimums, and/or flight altitudes of all civil or joint use.
(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 provides support to air traffic operations through policy, procedures, separation standards, equipment, software, and other operations related to air traffic activities across the NAS. Air Traffic Procedures serves as the primary point of contact for the Service Areas, Service Centers, and field facilities for Terminal, En Route, standards, and procedures issues. Air Traffic Services, Operational Policy and Implementation Directorate serves as the primary point of contact for the Service Areas, Service Centers, and field facilities for operational issues, and is the primary point of contact for Oceanic/Offshore operations, standards, and procedures issues. They work in concert with Air Traffic Procedures for processing and publication of air traffic procedures.
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 appropriate Air Traffic Service Center OSG, Airspace and Procedures 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 Centers 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 Center F&E budget submissions and programming actions.
(7) Evaluating regional airport and airspace changes for impact on instrument flight procedures.
(8) Determining the necessity for environmental impact studies as required by current policy.
e. For airports that are included in the National Plan of Integrated… › (3) Facilitate airport planning processes to identify, in collaboration…
(9) Acting as the focal point for flight inspection issues within the region.
e. For airports that are included in the National Plan of Integrated Airport System, collaborate with Flight Standards and Office of Airports on processes and data needed to fulfil the requirements of this order. Collaboration not limited to the following:
(1) Sharing airport planning information related to likely and expected airport development that is likely to require IFPs, such as runway extensions, new runways, or construction related amendments lasting more than one year.
(2) Coordinating IFP requests with Air Traffic via Order 8260.43, Flight Procedure Management Program, processes, and addressing questions related to airport standards as identified in AC 150/5300-13, Airport Design.
(3) Facilitate airport planning processes to identify, in collaboration with Flight Procedures Teams (FPT), the expected and likely runway designator changes for magnetic variation (MV).
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-2. Air Traffic Letters of Agreement. › d. Unless Aeronautical Information Services is a party to 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.
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, or Flight Standards’ personnel. The general flow of information on the lifecycle process associated with IFPs can be found in Appendix L.
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. When Letters of Agreement 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 Letters of Agreement 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 Letters of Agreement 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 Letters of Agreement 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. 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-2. Air Traffic Letters of Agreement. › 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 JO 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. Service providers should maintain adequate access to 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, Flight Inspection Services Instrument Flight Procedure Coordination].
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. Flight Technologies and Procedures Division’s personnel should conduct periodic surveillance of the AIM and Aeronautical Information Publication to verify the accuracy and appropriateness of the information. AIM and Aeronautical Information Publication discrepancies and errors should be forwarded to the Air Traffic Procedures, Process Support Group.
c. Each service provider should monitor their 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. Each responsible procedure specialist should
review their 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.
2-2-2. Aeronautical Charts and Publications. › g. Aeronautical chart discrepancies and/or errors should be sent…
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. Aeronautical chart discrepancies and/or errors should be sent through the Aeronautical Information Portal to [email protected].
Section 2-3. Environmental Requirements › 2-3-2. Environmental Impacts.
06/01/2023 Order 8260.19I
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, Environmental Impacts: Policies and Procedures, and Order JO 7400.2, Procedures for Handling Airspace Matters, 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 (FMO) 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 inspection 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 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 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. › d. Breaks in MEAs. The 75 MHz markers must not be used to define the…
b. Category 2 is a temporary condition not considered in instrument procedure development. Air Traffic 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-12.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 non-precision 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.
a. Aeronautical Information Services. › (2) Revise en route aeronautical charts and Chart Supplements to…
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 everchanging 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 Office of Airports.
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 (e.g., “Q” and “T”) route Magnetic Reference Bearings (MRB) during the first-full airspace charting cycle of each calendar year.
a. Aeronautical Information Services. › (11) VOR, VOR/DME, and VORTAC facilities supporting the en route…
(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 Program Operations 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):
b. United States Air Force (USAF)/United States Army (USA). › (4) Assign and maintain MVs of record for USAF/USA non-NAS navigational…
(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 Air Route Traffic Control Centers (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.
b. United States Air Force (USAF)/United States Army (USA).
(1) Function as the focal point for all USAF/USA 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/USA 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/USA 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.
(9) USAF/USA navigational facilities not within the NAS: › (d) Amend all procedures as, required, when the airport MV of record is…
(5) Maintain a listing/record of USAF/USA 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/USA 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/USA navigational facilities within the NAS:
(a) Maintain official listing of USAF/USA 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/USA 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.
(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.
(9) USAF/USA navigational facilities not within the NAS: › e. Western (AJW-W), Central, (AJW-C), and Eastern (AJW-E) Technical…
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.
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.
2-5-3. Guidelines for Magnetic Variation Revisions. › c. MV limits for airports with SA CAT I, SA CAT II, or CAT II/III…
f. Regional Office of Airports/Airports District Office (ADO). In collaboration with 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. The need and expected timing for runway designator changes should be identified and coordinated during periodic airport planning efforts and airport layout plan updates in order to avoid delays with updating associated IFPs. 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 is directly involved in NAVAIDs/radar rotations and requires proper coordination. The Office of Airports, 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 2019 provides MV values for all locations for January 1, 2020 through December 31, 2024. The nearest future epoch year value calculated using that model would be specified as 2025, and the MV based on the December 31, 2024 value, except as indicated in paragraph 2-5-3.c. The assigned MV is listed as using the 2025 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.
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
(2) RNAV. › (c) Holding on RNAV routes or stand-alone.
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
(b) Runways that have SA CAT II or CAT II/III approach procedures must… › (3) Diverse Vector Area.
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. Use airport MV of record when defining DVA heading limitations.
Section 2-6. Notices to Air Missions (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 7930.2, Notices to Air Missions (NOTAMs).
2-6-2. United States NOTAM System. › b. NOTAM Ds. See Order 7930.2, Chapter 4, for NOTAM D policy.
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, and Aeronautical Information Services. 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 7930.2, Chapter 7, for specific FDC NOTAM policy.
b. NOTAM Ds. See Order 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 Airport Improvement Program 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 month prior to, or one month after which, the periodic review is due based on Table 2-8-1.
n. Fixes. › (2) Cancel fixes and holding which are no longer needed.
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, 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-5. Reviewing Organization Responsibilities. › c. If the results of the review indicate a need to amend an IFP,…
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 NOTAMs) 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 Letter of Agreement 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 Letter of Agreement 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-12.h.
a. Form 8260-2 is the vehicle used to transmit requests for the… › (4) The military is responsible for initiating and maintaining the Form…
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 Air Traffic 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 Air Traffic’s responsibility to initiate airspace rule making action for the designation of compulsory reporting points.
b. Non-compulsory reporting points may be established by Air Traffic 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, 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) Non-FAA service providers are responsible for initiating and maintaining Form 8260-2s for those fixes that will not be used by the FAA or other service provider 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.
Continue reading ↓ 120 of 917 passages shown